BT with Scheduler Component and Shelly BLU TRVs via MQTT

[mario-dg]

Hey everybody,

I'm not quite sure where to start, since I just got into the whole smart home space.
I bought 4 Shelly BLU TRVs + 4 Shelly BLU H&T Sensors + Shelly BLU Door/Window sensors for my 4 main rooms.
As far as I am aware, running the 4 Shelly BLU TRVs is not yet compatible with the Shelly BLU Gateway Gen3 and the official Shelly HA integration (forum). Hence I am using the custom mqtt climate entities, that are also described in the forum.
It looks like following:

mqtt:
  - climate:
      name: "Shelly TRV Bedroom"
      unique_id: "Shelly TRV Bedroom"
      current_temperature_topic: "shellyblugwg3-customid/status/bthomesensor:203"
      current_temperature_template: "{{ value_json.value }}"
      max_temp: 30
      min_temp: 4
      temp_step: 0.1
      temperature_state_topic: "shellyblugwg3-customid/status/bthomesensor:202"
      temperature_state_template: "{{ value_json.value }}"
      temperature_command_topic: "shellyblugwg3-customid/rpc"
      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 }}"
      mode_state_topic: "shellyblugwg3-customid/status/bthomesensor:202"
      mode_state_template: "{{ 'off' if value_json.value == 4 else 'heat' }}"
      modes: ["heat", "off"]
      mode_command_topic: "shellyblugwg3-customid/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: "shellyblugwg3-customid/status/blutrv:200"
          value_template: "{%if value_json.rpc%}online{%else%}offline{%endif%}"
      device:
        connections: 
          - - bluetooth
            - 11:22:33:44:55:66
        name: shellyblugwg3-customid
        model: Shelly BLU TRV
        # model_id: SBTR-EU867E
        manufacturer: Allterco Robotics

The other Shelly sensors are running via BLE and the BTHome integration, which seems to work just fine, since my appartment is not that big.
I love the usability of BT, so I hooked those custom climate mqtt entities up with BT, the Shelly H&T Sensor, the Shelly Window sensors and my weather integration to stop heating on opened windows and when my local temperature is above 15°C.

Additionally, I am using the scheduler component to create custom heating schedules for every room, based on the temperature outside. These schedules are setup with the BT climate entities and not the mqtt entities. During the configuration and initial setup of the BT entities, I noticed that the target temperature sometimes spiked up to the max 30°C, but I just manually lowered it to my desired temperature and from that point on, everything seems to work fine.
Looking at the history of the BT for my bedroom, everything also looks like expected to the schedule configured in the scheduler component:

But the whole picture changes when I look at the custom mqtt entity:

I also looked at the mqtt messages that are sent to mosquitto, and they confirmed, that the target temperature is set to 30°C.
How does it happen, that there is no trace of this max temperature in the BT climate entity, but the actual Shelly mqtt entity and the TRV connected to the Gateway, show that the target temp is set to 30°C?
I can also confirm, that the valve of the TRV was not open, only the remaining warm water in the radiator was still generating heat (as expected).
Should I be worried, that something is not working correctly?
Are these custom mqtt climate entities even correctly supported by BT or should I wait until the official Shelly integration catches up to my needs?

I am thankfull for any help, advice or people that have similar setups to mine.

[folfy]

Based on my preliminary analysis, I consider the "AI time based" algorithm flakey at best - Try normal calibration mode instead 😐
If you don't want BT to calibrate the setpoint (to reach the target temperature faster/more accurately) at all, use "no calibration" -> In this mode the TRV just is set to the actual setpoint you set in BT.

If you want us to diagnose why the BT target temperature actually changed to 31°C, please enable debug mode for the BT integration, reproduce the issue (document when you have trouble), and provide the logs afterwards.
HA enabling-debug-logging (disable&download chapter is right after)

[mario-dg]

I replaced my Shelly BLU TRVs with SONOFF Zigbee devices and set the calibration on those as normal and now everything seems to work just fine. My guess is, that working with the Shelly is just a major pain the a** and unless they are officially supported in the Shelly integration (multiple TRVs through one Gateway) it's just not a viable solution. Thanks for your help!