+1 same here
+1 few days ago
Made nothing, but ebusd upgraded well yesterday. And some new control entities were created.
Update to version 23.2.2 works fine
for me on version 23.2.2 still round button RUN… no show me run again and stop… But addon works
Hello,
I have the latest Ebus 5 module and connected it to our Vailland heating (ecoCOMPACT VSC 146/4-5 E VRC700/6). I’m having problems with the correct integration in Home Assistant (Home Assistant OS).
What is actually the difference between @eBUSd and eBUSd Edge during installation?
Is there a good guide?
Any sollution ?
eBUSd Edge takes the source code of ebusd and compiles it on your device when installing the addon. this takes longer, take a lot of write and read on your storage but has the absolute latest features of ebusd (if any)
non edge is pre-compiled and simply downloads a container for your architecture and starts it.
I think edge can be removed from the project as im not aware of anyone needing it.
for what exactly?
is this the same as Stuck in **starting** state · Issue #61 · LukasGrebe/ha-addons · GitHub ? - “stuck in a starting state”
Hello there,
does anyone have a working ebusd configuration (CSV config file) for Vaillant VRC 710 (sensoDirect, one zone, one circuit)?
I’m using HASSIO with ebus-adapter v5 and MQTT. My ecoTEC heating (id 08) is recognized, but my controller (id 15, VRC 710, HW-ID EMM00) is not.
[bus notice] scan 15: ;Vaillant;EMM00;0104;8503
[update notice] store 15 ident: done
[update notice] sent scan-read scan.15 QQ=31: Vaillant;EMM00;0104;8503
[bus notice] scan 15: ;Vaillant;EMM00;0104;8503
[main error] unable to load scan config 15: no file from vaillant with prefix 15 matches ID "emm00", SW0104, HW8503
Any help would be greatly appreciated.
kind regards
Hi kmplng,
do you mind sharing your EBUSD_OPTS and 08.recov.csv?
I managed to read some values from my recovair 260/4, but the connection is unstable and ebusd only detects the recovair with the --loglevel=debug option for some reason. Plus I couldn’t figure out how to set any parameters.
Thank you very much.
Hi,
here it the pull request for the 08.revov.csv I use: Vaillant recoVair 260 by kmplngj · Pull Request #343 · john30/ebusd-configuration · GitHub
I use “–scanconfig=08” as only command line option.
Bye
Jan
1 Like
Hi all!
I’m an absolute beginner in the ebus-world.
I managed to get a the “EBUS to WiFi adapter module v5.2” (created by Daniel Kucera) running.
Also I tried using ebuds in docker and as a home assistant add-on. Both worked “ok”.
I still have many “Unknown MS cmd” in my log but I think that ebusd is loading the correct files
- 08.bai.csv for the Boiler (HW7401 - auroCompact VSC S 196/2-c 200)
- 15.430.csv for the build-in VRC 430
- 50.v61.mc.csv for the VR61 module
However I still have many unknown commands like:
2023-08-10 08:06:32.482 [update notice] received unknown MS cmd: 1050b509040e010000 / 00
2023-08-10 08:06:32.721 [update notice] received unknown MS cmd: 1050b509040e200000 / 00
2023-08-10 08:06:32.988 [update notice] received unknown MS cmd: 1050b5040118 / 06000000600114
2023-08-10 08:06:33.273 [update notice] received update-write bai SetMode QQ=10: auto;0.0;50.0;-;1;0;1;0;0;0
2023-08-10 08:06:34.498 [update notice] received unknown MS cmd: 1050b503020003 / 0affffffffffffffffffff
2023-08-10 08:06:34.735 [update notice] received unknown MS cmd: 1050b505021800 / 00
2023-08-10 08:06:36.476 [update notice] received unknown MS cmd: 1050b505023000 / 0101
2023-08-10 08:06:38.518 [update notice] received read mc currenterror QQ=10: -;-;-;-;-
2023-08-10 08:06:38.785 [update notice] received read bai Status02 QQ=10: off;60;30.0;80;48.0
2023-08-10 08:06:40.498 [update notice] received unknown MS cmd: 1050b5040126 / 070202002901ba01
2023-08-10 08:06:40.757 [update notice] received unknown MS cmd: 1050b5040118 / 06000000600114
2023-08-10 08:06:42.537 [update notice] received unknown MS cmd: 1050b503020003 / 0affffffffffffffffffff
2023-08-10 08:06:42.788 [update notice] received unknown MS cmd: 1050b509040e010000 / 00
2023-08-10 08:06:43.036 [update notice] received unknown MS cmd: 1050b509040e200000 / 00
How can I debug this to read all values from the ebus?
For example I didn’t receive information about the holidayMode times (only temperature)
And the VR61 is missing in total.
Hope to find some input here 
I got my ebusd unit yesterday (Wifi model) and hooked it up. It receives some data and that appears to be valid, but generally doesn’t seem ro recognise m system apart from the VR71 mixer unit.
I get a HMU with a few sensor values, the VR71 with very little data and nothing beyond.
Is there a way to make it “understand” that I am running an Arotherm Plus heat pump, a Unitower hot water tank, the VR921 internet module and the Sensocomfort (VR720) controller?
Update: after playing around with things, downloading a forked ebus config repo and generally messing around I managed to get it working… mostly.
Now what I still need is a way to enable the writable entities…I can’t find the mqtt-hassio file, it’s not in /etc on my system…
I’ve got my ebus adapter talking to my heating system (Arotherm ASHP, VWZ AI controller, sensoCOMFORT thermostat). I already had mosquitto running for my Tasmota devices so once I installed this add-on and provided the host details for the adapter, it auto-magically populated ~160 sensors and the vast majority of them look accurate / align with what I can see on the control unit directly.
However I’m missing some things, mainly water pressure, ability to make changes, polling certain sensors more frequently. All the reading I’ve done on this assumes you have direct command line and file system access to the machine that ebusd is running on to be able to use ebusdctl, update config files in /etc/ebusd, look at the output of --scanconfig, and so on.
However I have not been able to work out how to do this - am I missing something really obvious here?
2 Likes
The mqtt-hassio file isn’t easily accessible in HAOS. I have managed to send either the rw or the filter-name options from the Addon Config, but so far not both. It’s a WIP
It’s possible to put your own copy of the mqtt-hassio.cfg file in your /config directory and tell the add-on to use that, but when I did it broke all my sensors in HA. So clearly there are some options set in the main version inside the container that are missing from the generic version, but we can’t see what they are…
@afiwube is there any possibility to add to this repo the version of the mqtt-hassio.cfg the add-on uses by default, plus any other parameters (eg how does the “auto connection” to mosquitto work?)
The reason being, if the defaults (as installed) don’t work or need to be customized then it’s hard to know what to change!
I had thr same issues with getting the mqqt-hassio to work in a different folder, but I tried again yesterday and it now works. I have write access to some entities now. Not sure how useful that will be and whether it actually works, bur it’s progress
Anybody know how resolve problem that addon still show info running ?
sorry, but there is no “version of the mqtt-hassio.cfg the add-on uses by default”. it gets autogenerated from the esoteric configuration files hosted, and selected from GitHub - john30/ebusd-configuration: ebusd configuration files
no, you’re not missing anything. you can place your own config files in the config folder, but in my opinion they are quite hard to write and understand.
you can ssh tunnel into the supervisor. there you can use docker exec to run a shell on in the add-on’s docker container. then you can use ebusctl as you have direct command line access.
run this in supervisor:
docker exec -it `docker ps | grep ebusd | awk '{print $1}'` /bin/bash
if first uses docker ps (list running containers), then grep ebusd to get the ps output showing your addon container, then awk "the first row" to get the id of the docker container running the ebusd addon. and uses that id in docker exec, followed by /bin/bash to run bash within the ebusd addon docker container.
sorry I’m no expert and “hack this together” to get something that works. feel free to submit a pull request. I have been thinking about adding some sort of comandline tool to ingress to show a comandline console of the container in the home assistant ui, but I’m not sure how to actually get that to work. maybe someone with more addon development experience can help.