You write that it is only possible to use one blu trv with one gateway and now you tell that i can use more. Sorry but what is true?
This really helps to integrate Thermostat for TRVs in our new home project installations. Great to deal with this now. Thank you @Bieniu for your work. Looking forward it to be integrated into the HA Shelly integration.
Both. You can pair multiple TRVs with one gateway and configure they (manually) with HA using MQTT. And Shellies Discovery doesn’t support multiple TRVs with one gateway.
hi,
the first (wifi based) shelly trv also showed a number entity for the value position. is this also possible with the new shelly trv blu ?
i would highly appreciate it as i use the smart thermostat integration and and therefore, for the shelly just want to be able to change the value position without using shelly itself as “active” thermostat (entity).
Thanks!
just as a heads up, I’m now in contact with Shelly support as one of my GW3s went offline and doesn’t want to connect to the cloud at all. Shelly support is saying that this is the 2nd time this happens to their customers and both times this same script was running on the GW.
I’m not writing this to blame the author in any way(i love the ease of setting up the script and generally how it works) Shelly will replace the GW, so no harm was done. I’m just pointing out that there might be some issue killing the GW.
@Bieniu if you wish to debug, I can try to extract some logs for you as i’m able to reach it, if i connect to its local AP.
No. The device doesn’t report valve position.
@Bieniu How to correctly configure multiple BLU TRVs with GW and MQTT?
I got 4 pieces and MQTT explorer shows multiple bthomedevice: and multiple bthomesensor:
In order to correctly fill mqtt climate current_temperature_topic: “shellyblugwg3-34cdb0786ee4/status/bthomesensor:203” man needs to know which bthomesensor is connected to which bthomedevice.
Do you know any rpc command which shows bthomedevice and nested bthomesensors?
This is the biggest problem with the current firmware. It is very difficult to distinguish what is what.
- use
Shelly.GetComponents
with parameteroffset
to get all response pages
http://BLU_GATEWAY_IP/rpc/Shelly.GetComponents?dynamic_only=true&offset=X
- for
blutrv:200
find theconfig.addr
value
- find all
bthomesensors
which have exactly the sameconfig.addr
value
- to make it easier to identify which
bthomesensor
representscurrent_temperature
and which representstarget_temperature
, you can give them names in the BLU Gateway web panel.
@Bieniu I can get bthomedevice values with …/rpc/Shelly.GetComponents? but I how to get bthomesensor values with rpc command?
I did renamed TRVs itself so in order to distinguish between them, but there is no option to rename bthomesensor value. Or am I missing stn?