Error Message ebusd to HA via mqtthass

[tammycutzet]

Hi,

i would like to ask for some guidance on the following. I get the error code from my Wolf Gas Heater every 5min.

For a reason I could not figure out, the Auto Discovery is not catching this value, but all others. I adapted the filter and added "error", but I think im still not on the right track to process the error code that comes in via broadcast.

Has somebody a tip for the right direction?

Thanks!

[Brosius18]

I receive a recurring error code from my Wolf gas heater every 5 minutes via eBUS, but ebusd's auto-discovery does not detect it, while other values are discovered correctly. I want to read and process this error in ioBroker. The value seems to be broadcast-only and does not respond to polling.

First, I used ebusctl monitor -f -m FF to capture broadcast telegrams. After letting it run for a few minutes, I identified the telegram that carries the error code. I then used ebusctl hex -d -n to manually decode the data and confirm the value and position of the error code.

Next, I edited the appropriate CSV file (such as 15.700.csv or bai.csv) and added the following line (adjust the fields according to your telegram and decode result):

ErrorCodeBroadcast;err;read;FF;15;B52400;10;NODP;U8
This defines a custom read-only datapoint named ErrorCodeBroadcast, using the broadcast telegram from device 15, command B52400, starting at byte position 10, and interpreting one byte (U8). NODP is used since the value comes via broadcast and not polling.

After saving the CSV, I restarted ebusd with sudo systemctl restart ebusd and waited for the error broadcast to occur again. Then I checked the value using:

ebusctl read ErrorCodeBroadcast
If the value appears correctly, it will also be available in the ioBroker ebus adapter. I can now use it in scripts, display it, or trigger alerts. If the decode fails or the result is incorrect, I’ll fine-tune the byte position and type, or use CSV options like NTS, STR, or IGN.