Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MQTT Write fails with 24.1.0 image #155

Closed
jabdoa2 opened this issue Jan 8, 2025 · 4 comments
Closed

MQTT Write fails with 24.1.0 image #155

jabdoa2 opened this issue Jan 8, 2025 · 4 comments

Comments

@jabdoa2
Copy link

jabdoa2 commented Jan 8, 2025

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.

@LukasGrebe
Copy link
Owner

seems to me like 2025-01-09 00:21:00.134 [mqtt error] write message bai SetMode not found suggests an "error" with the config csv?

i think 24.1.0 changed how config files are loaded. do you use a local copy or cloud config?

@jabdoa2
Copy link
Author

jabdoa2 commented Jan 8, 2025

i think 24.1.0 changed how config files are loaded. do you use a local copy or cloud config?

Local config. I guessed it would be that. However, hard to check without the ebusctl what it did load.

@jabdoa2
Copy link
Author

jabdoa2 commented Jan 8, 2025

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!

@LukasGrebe
Copy link
Owner

closing this as an ebusd configuration issue, not related to this projects scope of running ebusd in supervisor

@LukasGrebe LukasGrebe closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants