New Shelly TRV BLU integration

[chtannheimer (Christian Tannheimer)]

[Bieniu (Maciek)]

@chtannheimer Do you want to ask something? Or what?

[chtannheimer (Christian Tannheimer)]

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?

[domasist (Home Assistant support in Slovakia)]

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.

[Bieniu (Maciek)]

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.

[LeChuck]

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!

[gu-stera (Neno)]

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.

[LeChuck]

hey @Bieniu, can you enighten me on this a bit ? thank you!

[Bieniu (Maciek)]

@LeChuck

is this also possible with the new shelly trv blu ?

No. The device doesn’t report valve position.

[domasist (Home Assistant support in Slovakia)]

@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?

[Bieniu (Maciek)]

@domasist

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 parameter offset to get all response pages
  http://BLU_GATEWAY_IP/rpc/Shelly.GetComponents?dynamic_only=true&offset=X
• for blutrv:200 find the config.addr value
  
• find all bthomesensors which have exactly the same config.addr value
  
• to make it easier to identify which bthomesensor represents current_temperature and which represents target_temperature, you can give them names in the BLU Gateway web panel.

[domasist (Home Assistant support in Slovakia)]

@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?

[Bieniu (Maciek)]

@domasist

I can get bthomedevice values with …/rpc/Shelly.GetComponents? but I how to get bthomesensor values with rpc command?

Exactly as I wrote, you need to use the offset parameter to get all pages of the GetComponents response. The response is split into pages. Shelly | Shelly Technical Documentation

@domasist

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?

[domasist (Home Assistant support in Slovakia)]

thanks @Bieniu for explanation and clue. As I can say this splitting into pages is strange, because you don’t know on wich offset (page) the exact bthomesensor is and you have to look for on all of them. Or am I doing sth wrong?

If I name sensors with some names, there are not taken into mqtt, why?

[domasist (Home Assistant support in Slovakia)]

If creating Group in GW all the sensors are shown with their bthomesensor: values. So If one gives unique names to all sensors, this could be the way how to distinguish between them in more graphical way.

[Bieniu (Maciek)]

@domasist

Or am I doing sth wrong?

For example, if for offset=0 you get 10 components in the response, you have to repeat the request with the offset value greater by 10. And so on until you get the data of all components (the value of total in the response).

@domasist

If I name sensors with some names, there are not taken into mqtt, why?

Don’t ask me, ask Shelly support.

[domasist (Home Assistant support in Slovakia)]

thank @Bieniu got it. MQTT communication with the broker is even stranger if you restart HA mqtt setup climate entities will not be available if you don’t restart GW itself.

[Bieniu (Maciek)]

@domasist

if you restart HA mqtt setup climate entities will not be available if you don’t restart GW itself

Oh there wa a mistake in the availability configuration, I updated the post with the config.

[domasist (Home Assistant support in Slovakia)]

I changed mqtt climate component with your changes and now it is not available at all. Even restart GW doesn’t help.

Could it be connected with mqtt status online = false (in mqtt explorer)? But all sensors are shown there.

When I put GW into MQTT debug mode it died and I could not reset it. Reset with Shelly recommended “Press and hold for 10 seconds to factory reset the Device.” was not working. I needed to press both pwr and reset buttons for 10s, which works.

[Bieniu (Maciek)]

Show me your config for BLU TRV.