#Shelly BLU TRV gen3 Integration
1 messages · Page 1 of 1 (latest)
Is there any information on how the new Shelly BLU TRV gen3 can be integrated into HA? The BLU Gateway Gen3 appears via the IP address. The HT and DW sensors are integrated via BThome? But what about the TRV itself?
for shelly stuff, i used a relay as a gateway for a door sensor. i had to enable gateway in the relays webui then on the shelly intergration hit configure on the relay i was using as a gateway and enable it as a gateway. once this was enabled i hit the button on the door sensor and it automagically appeared into home assistant.
your setup is different but maybe something i did is simalar?
Yes, that's right. My setup is different. But the realisation is interesting. My question is more about whether there is already a way to integrate the new Shelly BLU TRV gen3 better and more easily into HA. So far, I have only managed to do this by using MQTT to make specific definitions. However, the valve state and many other things are missing. So I only have the pure climate available.
mqtt:
- climate:
name: "BAD Shelly BLU TRV 112233445566"
unique_id: "112233445566"
current_temperature_topic: "bad-shellyblugwg3-e4b323169030/status/bthomesensor:203"
current_temperature_template: "{{ value_json.value }}"
max_temp: 30
min_temp: 4
temp_step: 0.1
temperature_state_topic: "bad-shellyblugwg3-e4b323169030/status/bthomesensor:202"
temperature_state_template: "{{ value_json.value }}"
temperature_command_template: "{{ {'id': 0, 'src': 'homeassistant', 'method': 'BluTRV.Call', 'params': {'id': 200, 'method': 'TRV.SetTarget', 'params': {'id': 0, 'target_C': value | round(1)}}} | to_json }}"
temperature_command_topic: "bad-shellyblugwg3-e4b323169030/rpc"
action_topic: "bad-shellyblugwg3-e4b323169030/status/blutrv:200/rpc"
action_template: "{% if value_json.result.pos | int > 0 %}heating{% else %}idle{% endif %}"
mode_state_topic: "bad-shellyblugwg3-e4b323169030/status/bthomesensor:202"
mode_state_template: "{{ 'off' if value_json.value == 4 else 'heat' }}"
modes: ["heat", "off"]
mode_command_topic: "bad-shellyblugwg3-e4b323169030/rpc"
mode_command_template: "{% set target = 4 if value == 'off' else 21 %}{{ {'id': 0, 'src': 'homeassistant', 'method': 'BluTRV.Call', 'params': {'id': 200, 'method': 'TRV.SetTarget', 'params': {'id': 0, 'target_C': target}}} | to_json }}"
availability:
- topic: "bad-shellyblugwg3-e4b323169030/status/blutrv:200"
value_template: "{%if value_json.rpc%}online{%else%}offline{%endif%}"
device:
connections:
- - bluetooth
- f8:44:77:21:58:37
name: BAD Shelly BLU TRV
model: Shelly BLU TRV
model_id: SBTR-EU867E
manufacturer: Shelly
```
Yes, the story continues. After I found out that zigbee is also supported from firmware 1.1.x, I learnt a TRV in HA by pressing the button three times (on the battery compartment - ZbE display).
The problem with the second TRV is that it keeps finding the same TRV even though I am using a different, second TRV. So I have not yet managed to learn two TRVs. The display sometimes shows "ZbE" + "Zb0" + "ZbI" or "no". After several attempts, the first TRV is then displayed again as being programmed in HomeAssistant ZHA.
Unfortunately, the MQTT variant only works well to a limited extent.
@silk bear I have some of those and have been on the same journey. I got it to "work" in HA through ZHA but Z2M doesn't have support yet. I've opened a ticket for that. https://github.com/Koenkk/zigbee2mqtt/issues/25433
Link https://shellystore.co.uk/product/shelly-blu-trv/ Database entry {"id":3,"type":"EndDevice","ieeeAddr":"0x694f69634762684a","nwkAddr"...