You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I upgraded to the 24.1.0 image and that somehow broke writes (via MQTT) to ebus. I get this line in my log:
2025-01-09 00:21:00.134 [mqtt error] write message bai SetMode not found
I use an automation to publish that:
metadata: {}
data:
qos: "2"
retain: false
topic: ebusd/bai/SetMode/set
payload: >-
{% set Soll =
float(states("sensor.vorlauftemperatur_kurve_soll")) %}
{% set HeaterOn =
bool(states("binary_sensor.heizung_steuersignal_automatisierung")) %}
0;{{ Soll }};0.0;0;{{ 0 if HeaterOn else 1 }};1;1;0;0;0
action: mqtt.publish
Not sure if that change is caused by the addon or some behavior changes in ebus. I downgraded for now as I like my heater to continue to work ;-). Let me know if I can somehow debug this further somehow. Due to #154 I got troubles to see if ebusd properly read my config but it seem to be able to read all other stuff properly.
The text was updated successfully, but these errors were encountered:
Luckily they recently merged my PR with my changes upstream. Probably a good time to retest the upstream config. However, not today. Will try that tomorrow. Thanks for all your work and help!
I upgraded to the 24.1.0 image and that somehow broke writes (via MQTT) to ebus. I get this line in my log:
I use an automation to publish that:
Not sure if that change is caused by the addon or some behavior changes in ebus. I downgraded for now as I like my heater to continue to work ;-). Let me know if I can somehow debug this further somehow. Due to #154 I got troubles to see if ebusd properly read my config but it seem to be able to read all other stuff properly.
The text was updated successfully, but these errors were encountered: