My ebus instance fail to start, just displaying. Uninstalled, rebooted HA and reinsttaled and no change.
Is there anything in the log about progress in starting??
Hi, I’m trying to install the addon, but when starting it I always get
FATAL: No network or USB device defined. Configure a device and restart addon
error message. My ebus shield is running, I can access it through its web interface.
The config is
scanconfig: true
loglevel_all: info
mqtttopic: ebusd
mqttint: /etc/ebusd/mqtt-hassio.cfg
mqttjson: true
commandline_options: "-d=ens:192.168.0.142:9999"
http: true
readonly: true
latency: 10
Where shall I look for the solution?
Ok, I got an idea from my message and now it connects with this config:
scanconfig: true
loglevel_all: info
mqtttopic: ebusd
mqttint: /etc/ebusd/mqtt-hassio.cfg
mqttjson: true
network_device: 192.168.0.142:9999
mode: ens
http: true
readonly: true
latency: 10
After the addon install, there is no network_device and mode options visible. After adding them manually to yaml, they are visible on UI. Maybe it helps someone in the future
If somebody has good or bad experience with Wolf FGB heaters, then would you share them? Thanks
Hi,
Exactly the same here. It restarts at similar intervals (kind of consistently). This is a screenshot of the uptime:
Before it used to be several days (usually until I installed some update to HA or restarted for other reason).
I have checked and both the addon and ebusd device are updated to latest versions.
Regards.
hi, sorry I have no idea where I should start looking. maybe @neeu2 or @losip has an idea of where to look or how to fix this?
Hello,
I install ebusd no error in the log, but I cannot have data, ebusd signal unknow and ebusd scan unknow.
All my boiller entities are unknow also.
What can I do?
There’s an upadate for ebusd don’t find how to do that.
-
I also observe problems starting ebusd addon. I have an automation to stop/start the addon before/after nigthly HA backup (done by Proxmox). So the addon starts, eventually but HA complains in the log.
-
Do you know how to get rid of this warning:
Entity sensor.ebusd_bai_prenergycounthwc1 [...] is using native unit of measurement 'None' which is not a valid unit for the device class ('energy') it is using; expected one of ['MJ', 'Wh', 'GJ', 'MWh', 'kWh'];
I’m sure this warning could be cleared by changing “mqtt-hassio.cfg” but have no idea how (this file scares me! )
Hi,
I created a yaml package with your code replaced with my heatpump mqtt values but I can’t find this cimate entity in home assistant.
Config doesn’t give an error.
Nobody can help me?
Hi, i have the same problem….
Du you have a solution now?
Kind regards,
Alex
Hello all,
i have 2 Problems.
First is, how i can get the newest Version from the addon 23.3? If i delete the addon, i get every time the 23.2.5.
Second Problem is, i had the 720 running very well, now i get a Update to 720/3 and i cant find it.
also in the mqtt explorer, i dont find the VRC 720.
Has someone the solutions?
Kind regards,
Alex
After some checking and debugging, seems that the addon is not crashing at all, but the watchdog feels it has not properly started within a roughly 900 sec interval, and reboots it, although it is running, and takes a couple minutes for actual startup, and feeding values to mqtt. Seems that the ebusd container takes around 20-30 minutes to report itself as running (the buttons to start/stop the addon are shown during this time as if it is not fully started). Therefore, the watchdog is constantly rebooting the addon, as if it wouldn’t properly start.
If I disable the watchdog, it runs flawlessly for 1-2 days until something funny happens with the code or the link with the ebusd device. This is time between acceptable to me, and I am debugging this on my free time.
Is there a way to a) configure the watchdog, so that it considers the start-up time as longer, or else b) the ebusd daemon to report itself as started in a shorter period?
Thanks!
Hey, I’m running the ebusd add-on on my RPi 5 with HomeAssistant. I’m using the Addon for a Wolf CWL 180 Excellent Home Vetilation System and it’s working good except of one thing. The FanMode is polled frequently and the addon shows in the logs that it’s published to mqtt but nothings received there.
Any other values are published correctly to mqtt and shown up.
Hi, I’m trying to setup ebusd addon for a Wolf FGB-24 boiler. The connection seems to be working, but I do not get any values in HA.
Ebusd log shows only these messages:
2024-08-22 16:09:45.505 [update info] received BC cmd: 03fe050308010000005f2f2e3f
2024-08-22 16:09:45.505 [update notice] received update-read broadcast betrd QQ=03: 0;00;0;47.5;47;46;63
In HA I see lots of ebus related entities created by MQTT, all has unknown value.
If I go into ebusd container, then at least I can get the hot water value:
>ebusctl r warmwasser_ist
45.0
What shall I try?
If someone can help how can I access the addon via http, then I guess I can poll the values without mqtt. Not the best, but good enough. I switched on http access in addon config, the http port is the default 8889.
In HA terminal, docker does not show any exposed ports, inside container ebusd command line has the httpport parameter.
@afiwube
I am new to HA and ebusd add-on. therefore please excuse my silly questions.
The addon tries to load vaillant/15.ctlv3.csv At https://upd.ebusd.eu/ there is only vaillant/15.ctlv2.csv. How is the process to create ctlv3 ?
As a workaround I tried to create a local path und use “configpath”. It should be named /config/…
At my installation of “home assistant green” “file editor” shows dirs /homeassitant, /tmp and others. But no /config. Is this path inside of a dogger container ?
How to access the directory /config ?
On “home assistant green” “File editor” the folder “/config/ebusd…” is shown as /homeassistant/ebusd…".
Now my downloaded files are found. But I have not the knowledge to create the missing files “vaillant/15.ctlv3.csv”, “vaillant/76…” and “vaillant/f6…”. At some other files there are some missing entries for the vaillant components installed at my location.
If you want the particular files, which you can also modify, you shall get them from a github repo. Seems that the original csv repo by john30 is not being maintained, and even the files there, may refer to old vaillant equipment software versions. This is the repo I have used lately:
There are also numerous other repos that I have seen, from many people who have taken a lot of efforts to decrypt the codes on their own equipment. There is a myriad of variants and versions, and I am unsure on whether there is a good compilation who may fit all.
This is how the file/folder structure looks on my setup:
Note that files are in a folder labelled vaillant within the ebusd folder, but it is not specified on the config path.
On the config path, in the addon setup, I specified:
/config/ebusd/
I believe that all installations should have at least the _templates.csv file, and the three .inc files.
Hope this helps.
Cheers.