github-actions[bot]
commented
2 months ago This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days
Closed gegges11 closed 1 month ago
github-actions[bot]
commented
2 months ago This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days
What happened?
After switching to zigbee2mqtt and the MQTT broker Mosquitto, the TRV automations practically no longer work. If I set the temperature directly in HA at the device or entity - it works. If I set the temperature at the thermostat within zigbee2mqtt (Details/ Current heating setpoint) - it works. The temperature setting is also transmitted reciprocally. If I create an automation, the temperature is not set there (climat.set_temperature), regardless of whether I address the device or the entity. If I use the "MQTT: "Publish service under Development Tools/Services, the temperature is not set there either (current_heating_setpoint). The same applies if (climat.set_temperature) is executed under Development Tools/Services. The MQTT service is running. Under System/Protocols there are only entries if they are executed directly and not via a service. Summarized: Setting the temperature on the device or in zigbee2mqtt works. If I use a service, it does not work. On the last day of the year, does anyone have any ideas? cheers gegges
What did you expect to happen?
Seamless integration via direct actions (set temperature) or via automation.
How to reproduce it (minimal and precise)
see above
Zigbee2MQTT version
Seamless integration via direct actions (set temperature) or via automation.
Adapter firmware version
EZSP v8 - 6.10.3.0 build 297
Adapter
Zigbee SONOFF ZBDongle-E
Debug log
no error log available - no entry when problem occurs