less data via mqtt

[JBN164]

Hallo Lukas,

thanks for your work.
Unfortunately it doesn't work with my system and I don't know why.

I have the ebusd Adapter v5. It is flashed with Version 2023-09-17.
The adapter is connected with my heating (Wolf CSZ 2 14/300) and the electrical circuit should work 20V DC is measurable.

I installed the HA Addon with the following config:
scanconfig: true loglevel_all: notice mqtttopic: ebusd mqttint: /etc/ebusd/mqtt-hassio.cfg mqttjson: true network_device: ens:192.168.178.21:9999 latency: 10 accesslevel: “*” configpath: https://cfg.ebusd.eu/

The bus appears in my MQTT integration with 2 devices "eBusd" and "ebusd bus device".
The MQTT Explorer shows data (only a few) but they didn't appear in MQTT.

You find my problem also here (in german) --> https://community.simon42.com/t/einrichtung-ebusd-adapter-und-integration/10008/20

Thanks

Jan

[LukasGrebe]

Hi Jan!

Thanks for reaching out and the link to a more in-depth problem description.

As far as I can tell the configuration for your wolf device is not loaded. I assume this is most likely because no such configuration exists. The config files are created by the community but messages by newer devices might not have been reverse engineered yet.
Ebus messages are proprietary by vendor and different by hardware.

here is why I think so:

1. you are seeing logs of ebusd (it’s running) and log entries are „unknown command“ this means the addon started, successfully connected to the adapter wich successfully connected to the bus and is reading messages.
2. MQTT is outputting an outside temperature message - therefore MQTT connection is successfull and sending messages.
3. Because the MQTT outside temp has an error and outside temperature is a fairly well known generic message there appears to be an error in the ebusd config. This is further supported by the „unknown command“ messages in the log of ebusd addon. This log entry means it’s seeing messages in the bus but does not know what they mean.

if you know the wolf device has an associated config file in the ebusd-config repo, then it might be a problem of auto loading them but as the scan option is set they should load automatically.

Please try to find any of „unknown command“ messages in the config repo and let me know if there are any.
If there are, we can debug what it’s not loading them,
If there aren’t any your devices‘ bus messages will most likely need to be reverse engineered.

Feels free to update the linked thread with this info, I’m not registered on that message board.

[cociweb]

I agree with @LukasGrebe. The ha-addon and the ebus-daemon/mqtt module are loaded, and publish towards to the mqtt.
Unfortunatelly, the content (the result of the scan/decode) is improper in your case. So there is nothing to do from ha-addon point of view (excluding your ebusd configuration):
Maybe you can get further support from the the ebusd community to get further hints for your ebusd configuration at:

• https://github.com/john30/ebusd-configuration
• https://github.com/john30/ebusd/discussions

PS: I see a couple of wolf related issues on the above mentioned links. Maybe it's a decoding issue since you get a general E000 error and the manufacturer is recognized. (It is also worth to check your adapter's power supply. Check the recomendations for your adapter: is it high enough)

[GrumpyMeow]

Hi!
In the screenshot i'm able to see that ebusd has detected your Wolf-ebus-device. Ebusd uses these "scan.08" values to determine which configuration-file is needed for your ebus-device. If you didn´t override the "configuration"-path parameter in the ebusd-addon-configuration, ebusd will fetch the ebusd-configuration via internet.
In my case i get this in mqtt:

In your case i think you must do:

1. Clone the ebusd-configuration repository
2. Configure the ebusd-addon to use this custom-configuration
3. Create a folder named "Wolf" next to the folder named "Vaillant" (https://github.com/john30/ebusd-configuration/tree/master/ebusd-2.1.x/en)
4. Create in this "Wolf"-folder a file named "08.csv".
5. In the 08.csv file you must then define the fields which your wolf-devices supports. Unfortunately this last step will take some time.

I hope this helps. My assumption is that the error is caused by that no configuration-file is available for your device.

[cociweb]

Hello @JBN164, were you able to reach some progress? Can we close the issue?