This happened to me yesterday with 2024.2.2. Have no clue how to fix this. Some entities are now lost and others are just fine
this addon only runs ebusd on supervisor. for any further support (eg what values you are seeing and how to change them, please see ebusd (mqtt interface) because I can’t help with that.
please see GitHub - john30/ebusd-configuration: ebusd configuration files or john30/ebusd · Discussions · GitHub
I can’t support with the ebusd configfile configuration.
please see the “documentation” tab of your addon installation:
Custom CSV or MQTT cfg files:
To use custom config files you can use the configpath option. You can create a local copy of GitHub - john30/ebusd-configuration: ebusd configuration files in your “/config” folder and change configpath to e.g. “/config/ebusd-configuration/latest/en”. Custom CSV files must be in the /config folder.
Similarly for MQTT create config file in “/config” folder and link it using the --mqttint=/config/YOUR_FILE_PATH option
a few reasons:
- the core integration assumes a specific set of value names - see source. So if you do not have a
Zone1NightTemperatureor your configuration names it differently, or more important you have other values with names that are not covered by the core integration, they won’t show up. - this addon simply makes the provided ebusd docker container available for use by supervisor. This docker container provides MQTT out of the box see documentation and allows changing value names or the list of values used via a custom MQTT config file
- MQTT supports auto discovery so devices and entities are automatically setup
- MQTT is local push over local polling by the core integration
1 Like
could this be related to how the ebus and devices work?
some values are only set periodically and can not be polled.
for example there are some values (for example energy consumption) that is only sent at midnight by my valiant devices and no one has figured out a way to make the devices send that data any earlier.
other values are only updated every 5 / 20 / x minutes. some of those can and will be polled as defined in the ebusd-configuration files. but especially with heat pumps many messages sent by the devices on the bus are still unknown or unknown how they can be polled and we currently just need to wait for them to update.
could this be the case here?
How I can create a log of the add-on outside of the docker? I tried adding --logfile=/config/ebusd/ebusd.log in “Custom Comand Line Options” but it does not create anything…
I tried to enter into the docker with Advanced SSH and in var/log directory is also empty with the default log configuration.
I only can view the last Log inside the Add-on UI in Home Assistant.
Any help please?
My ebusd adapter had been running without issues for months, but today, after latest HAOS Update, I suddenly lost a whole bunch of entities. No clue why, especially since the others are still reporting just fine…
Update: turns out it was some kind of glitch. Restarting HA didn’t help, but restarting the addon afterwards brought everything back.
The CSV file for Ariston Group (R) eBus compatibile boilers/heat pumps can be found here:
It has been recently updated.
Hello everybody,
can someone show me his configuration for ebusd in yaml style?
I have fixed my problem.
After hours of searching I have to realize that ebusd is not allowed to write logfiles into the config directory.
Of course, this gets in the way of my actual problem, because I only have the scrolling “Log” window, which is constantly overwritten.
How do I get log files from the addon?
A call for help from HaJue
Thx in advance!
Update:
Since today, there is an update, writing S6 Logs into /config
(can be configured directly via AddOn)
Thank You so much!
2 Likes
Hi there,
I have an issue with starting. The Start button keeps the blue circle turning
(a bit of a pain to get to the end of this thread…)
The process seems to run though since the log does show telegrams come in.
What to d0?
I confirm I have the same problem and it seems to be related to the last update of the home assistant, now it works for me:
Core
2024.6.3
Supervisor
2024.06.0
Operating System
12.4
Nevertheless, data flows through MQTT to HA correctly. Interestingly, after turning off the Observer, I finally have information that it has started. Maybe it needs more time to start and when its operation control is turned on, it restarts. This seems to have happened to me today.
Oh, a reply and that fast! I hadn’t updated yet, but will do so. Somehow (over night) the circle went away - plus I had success getting the whole thing to work (almost). It’s just that I seem to get telegrams with 0 degress which seem odd. Would look ok if they were just ignored. Something to investigate…
Just wanted to note that the update seemed to solve the issue. At least when rebooting the service was up immediately. Though a “Save” in the options a bit later kept the circle busy again. Alas, I don’t need to fiddle with them any longer and the system is running otherwise.
On my HA dashboard running eBusd HA deamon add-on with networked eBus Adapter v5 and Mosquito I’m getting ebusd ebusd updatecheck as update available with installed 23.2 and update 23.3. The release announcement points to Xanthophyllum 23.3 does that just mean 23.3 hasn’t been packed into the eBus HA add-on because I can’t seen to get it to actually update. I have updates set to automatic. Cheers, Guy
2 Likes
I get the circle looping once again. Will open an issue on github
I tried adding enablehex to the ebusd start options, but it is not in the run.sh. And changing that file is not possible.
(getting to the very end of this thread is a pain)
My installation of eBUSd has been working well for 9 months but sometime in the last two weeks it has commenced restarting every 15 minutes following receipt of a SIGTERM and graceful shudown via s6-rc. The watchdog then restarts the add-on but meanwhile I lose control of my boiler.
I know very little about LINUX and would be grateful if someone could guide me to the source of the SIGINT. Needless to say, I have tried full power cycle of both HA and the eBUS adapter
Thanks
1 Like