Connect Shelly Blu TRV to Wi-Fi over existing Shelly Gen3/Plus devices

[nevenr]

Hi,

I already have several Shelly Gen3/Plus devices (also acting as BLU gateways) and Shelly BLU devices connected to Shelly cloud (and/or to Home Assistant) and I am satisfied with how it works. In my opinion possibility that existing Gen3/Plus always powered (not battery) Shelly devices can act as Bluetooth gateway is killer feature and this is something that was dragging me back to Shelly devices from other vendors.

Currently, I'm considering buying "Shelly Blu TRV" but from available information I'm not sure it can be connected to Wi-Fi over existing Shelly Gen3/Plus devices (acting as BLU gateways that I already have all over my house) or this "Shelly BLU Gateway Gen3" is required/mandatory.

If for "Shelly Blu TRV" I would need to install in each room "Shelly BLU Gateway Gen3" this would make me wonder should I then install some other gateway and with this open access to much wider number of devices.

Concrete questions:
- Can now or in the near future "Shelly Blu TRV" be connected to Wi-Fi over existing Shelly Gen3/Plus devices acting as BLU gateway?
- Will in the near future "Shelly Blu TRV" have full support in Home Assistant (reading current valve position, reading current temp, reading battery status, setting valve position, setting desired temp, etc ..) like already existing Shelly devices.

Thanks for answers in advance.

Regards,
N.

[calm]

The annoying thing is, that you actually can connect the Shelly Blu TRVs to Gen3 devices (2PM in my case). However it only lets you read the data coming from the TRV's. This makes it kinda feel like an artificial limitation and I wish they would at least let us know the reason behind this, if they actually decide to keep it this way 

[wooly]

that you can read only it is normal, since any BLE normally act only as a beacon, sending its status, but not receiving data, only when get in contact with its paired gateway get from it some information or ion certain cases, establish a persistent connection to receive commands [or possibly software updates].
This allows to use a battery supply, but on the other part completely break the shelly philosophy, where each device is a server, capable of an autonomous life.
So this lead to the necessity of a gateway that "know how to keep on its lash" the BLE device .
Incidentally performance, even when coupled with the gateway are not at the same level than some stand alone "non smart" TRV (even the 20 schedules for certain rooms may be a limit ... think about the dining room in an house where every day you have different schedules, so you need 6 schedules per day (42 switching times per week...);
Some weeks ago I proposed a version that could be fully programmable even from its "console" as the stand alone devices. noone answered ...

[GhostWorks]

I have installed 16 x Shelly BLU TRV, the Shelly BLU Gateway Gen3 has a limitation of 5 units , so had to use multiple Gateways 5 on each, I found that the signal is weak compared to other bluetooth communication devices I have deployed in same building so would be nice if the Shelly 1pm gen3 for example could be used as a repeater or gateway.

 

[GhostWorks]

its been 7 days and still some minor issues, as well as big ones , mainly communication issues , deployed 5 Blu Gateway Gen3 to try cover more ground , some TRV units still not communication properly even 3m away 

even thou my Home assistant can see all my TRV units via Bluetooth and get readings from each ( HA is on the ground floor ) and sees units as high as 2rd floor no units any higher at present, the Gateways seem to not send requests to some 

this product does seem to have been rushed, I'm hoping for a new firmware to sort these issues, as planning to get the rest done but not till all the bugs are sorted out