Hi. Ebusd 22.4 is out. Can you share new version also addon ?
I think it needs to be updated in alpine to be updated as not compiled on your device, ready to use binary.
Yup. As soon as alpine merge my pull request I will release a new version of the addon
Ebusd 22.4 has been merged but Alpine haven’t built it and added to the repo yet. I am not sure how often they do a build run so I will keep an eye and publish once it goes into the repo.
Those who want to use 22.4 and can’t wait should switch to edusd-edge
Ok we are waiting 
Hi,
first, kudos for the nice work so far!
however seems I have a config that is not supported by default (VRC720+Heatpump + VR32 coupler with Recovair 260…
What I understand, VR32 is not supported (yet) properly (Bus coupler/bridge latency · Issue #109 · john30/ebusd · GitHub)
and the easiest workaround is to setup a 2nd instance (possibly with a 2nd adapter?) on the bus of the Recovair (Recovair in ebusd 3.4 manuell einbinden ? · Issue #357 · john30/ebusd · GitHub).
So my question in short:
do you plan to support running multiple instance of ebusd within hassio supervisor with this addon?
It would be a big help for me…
Thanks in advance!
Hi!
This may be me because I don’t understand the protocol correctly, but I two ebusd devices, none of which seems to be “known” devices to ebusde. One is a Saunier Duval all-in-one heatpump (genia set 8 specifically) and the other is a Wolf mechanical ventilation system with heat recuperator.
What exactly would be the process to have ebusd “understand” them? Broadly speaking at least (or links to docs/tutorial). Can any kind of ebus device be supported by ebusd?
Note: I have two ebusd->usb adapters already.
Thanks
I have a “ESERA eBUS Koppler Ethernet”, the IP is 192.168.2.25 and port is 5000. With a telnet client I get all the information.
After that I install the " Home Assistant Add-on: eBUSd" and config is:
But I get no data.
Sorry, can’t help with that one. There is a discussion forum on the ebusd github
Running two instances would be possible. At the moment the add-on is very simple. It just installs ebusd and runs it in the foreground with whatever runtime options you have set.
To run two instances the schema would need to be reworked and the code tweaked to demonise each instance. I am happy to review a pull request but I think this is probably an edge case so not something I plan to implement myself
If I was you I would fork my repo, rename it and clone it to your add-on folder. With some small tweaks to config.yaml you could run this as the second instance.
thats actually a good idea, but wouldn’t it be easier - in terms of updateds / changes, or if anyone else needs it - if you create a separate clone to your repo called like “ebusd (Second instance)”?
Thats how it is done e.g. for Paradox alarm interface (PAI)
(hassio-repository/paradox_alarm_interface_3.x_second at master · ParadoxAlarmInterface/hassio-repository · GitHub)
So no actual development needed on your side and no need to create + add new repo for me… 
I am not creating a separate add-on but you could use try using ebusd-edge as your second instance
I hope this is ok to ask here.
Since the device I’m trying to integrate with ebusd is not one that seems readily supported by ebusd out of the box (it’s a heat recuperator and central ventilation unit), I guess I need to do some detective work.
However, I don’t even know where to begin working. I’m going to paste here some of the logs I’m getting:
2022-10-31 22:25:38.130 [update notice] received unknown MS cmd: 303c40a106000100010000 / 022200
2022-10-31 22:25:41.112 [update notice] received unknown MS cmd: 303c40220101 / 020001
2022-10-31 22:25:50.226 [bus notice] scan 35: ;Wolf; 8;0110;0000
2022-10-31 22:25:50.226 [update notice] store 35 ident: done
2022-10-31 22:25:50.226 [update notice] sent scan-read scan.35 QQ=31: Wolf; 8;0110;0000
2022-10-31 22:25:50.226 [bus notice] scan 35: ;Wolf; 8;0110;0000
2022-10-31 22:25:50.524 [main error] unable to load scan config 35: list files in wolf ERR: element not found
2022-10-31 22:25:50.524 [main error] scan config 35: ERR: element not found
2022-10-31 22:26:04.152 [update notice] received unknown BC cmd: f1fe0800080080333380000000
2022-10-31 22:26:11.473 [update notice] received update-read broadcast datetime QQ=30: -;01:00:10;-.-.-
2022-10-31 22:26:34.207 [update notice] received unknown BC cmd: f1fe0800080080333380000000
2022-10-31 22:26:37.154 [update notice] received unknown MS cmd: 303c40a106000100010000 / 022200
2022-10-31 22:26:40.174 [update notice] received unknown MS cmd: 303c40220101 / 020001
2022-10-31 22:26:42.667 [main error] scan config f6: ERR: read timeout
2022-10-31 22:27:04.236 [update notice] received unknown BC cmd: f1fe0800080080333380000000
2022-10-31 22:27:11.438 [update notice] received update-read broadcast datetime QQ=30: -;01:01:10;-.-.-
2022-10-31 22:27:34.265 [update notice] received unknown BC cmd: f1fe0800080080333380000000
2022-10-31 22:27:36.150 [update notice] received unknown MS cmd: 303c40a106000100010000 / 022200
2022-10-31 22:27:39.190 [update notice] received unknown MS cmd: 303c40220101 / 020001
How do I even begin to understand what these HEX code convey? Is there some guide or youtube video that could help me at least begin to understand whats going on?
its mostly proprietary although there are some standards defined.
the best resource I’ve found so far is HowTos · john30/ebusd Wiki · GitHub
although tooling could be improved I think. I had tried a while back but didn’t find the time to do it.
Hello there,
I have tried to install, but facing some newbie issues.
As you can see, only the status sensors are here, nothing about my goal device.
By the way on my RPi, I can not find any “ebusd” daemon to proceed with any scan or further configuration.
Do you have any ideas on what I’m doing wrong?
Thank you in advance
Hi,
got this error (Home Assistant OS running on Odroid HC4).
ERROR: Got unexpected response from the API: Service not enabled
> ebusd --foreground --mqtthost= --mqttport= --mqttuser= --mqttpass= --scanconfig --mqttjson --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=udp:192.168.1.145:3333 --log=all:notice
/run.sh: line 89: ebusd: command not found
Can you help pls.
It looks like you haven’t configured the add-on properly. The MQTT options are all blank
take a look at the log output in the add-on’s tabs (Settings→ add ons → ebusd → logs)
or via SSH: journalctl | grep ebus
I spotted what was causing this. I will release a new version of ebusd-edge to fix it