Two eBus adapters v3 on one ebusd add-on with HAOS

[astrakhan-dimon]

Hello, is it possible to get eBus messages from two different network devices on ebusd add-on? I use HAOS and 23.2.3 ebusd add-on. There are two network devices: 192.168.1.58:9999 and 192.168.1.78:9999 (eBus adapters v3 with esp8266) Now I have to run virtual machine with HAOS and ebusd add-on special for second adapter. Thanks

[LukasGrebe]

I don't think this is possible.

This addon is "just" a Home Assistant Supervisor compatible docker container of John30's ebusd docker.

As far as I know ebusd only connects to a single ebus adapter. And supervisor only runs a single instance of an addon. Thus the system appears to be fixed to 1 supervisor runs 1 ebusd addon runs 1 ebusd instance connected to 1 ebus adapter.

You could fork this project then set it up as its own repository in home assistants addon listing. This may result in supervisor seeing it as two different addons and run them in parallel to run 2 instances of ebusd connecting to 1 ebus adapter each.

[astrakhan-dimon]

Thank you, it works!

eBUSd2
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
> ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=hee4Ukae0kach6iexaigohph3veJeek5apee6thoof1aiYohzae2gughai3gahch --mqttjson --configpath=/config/ebusd2-configuration/latest/en --latency=20 --accesslevel=* --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd2 --lograwdatafile=/config/ebusd2-configuration/ebusd2.log --lograwdatasize=900 --device=enh:192.168.1.74:9999 --log=all:notice --log=main:notice --log=bus:notice --log=update:notice --log=network:notice --log=other:notice --lograwdatafile=/config/ebusd2-configuration/ebusd2.log
2024-02-06 21:02:05.642 [main notice] ebusd 23.2.p20230716 started on device: 192.168.1.74:9999, enhanced
2024-02-06 21:02:05.683 [bus notice] device status: resetting
2024-02-06 21:02:05.686 [bus notice] bus started with own address 31/36
2024-02-06 21:02:05.688 [bus notice] signal acquired
2024-02-06 21:02:05.726 [bus notice] device status: reset
2024-02-06 21:02:06.107 [mqtt notice] connection established
2024-02-06 21:02:15.886 [bus notice] new master 03, master count 2
2024-02-06 21:02:15.887 [update notice] sent scan-read scan.08 id QQ=31: 
2024-02-06 21:02:16.047 [update notice] sent scan-read scan.08 id QQ=31: 
2024-02-06 21:02:16.203 [update notice] sent scan-read scan.08 id QQ=31: 
2024-02-06 21:02:16.362 [update notice] sent scan-read scan.08 id QQ=31: 21;21;22;0010005726;3100;006016;N0
2024-02-06 21:02:16.534 [bus notice] scan 08: ;Vaillant;BAI00;0405;0803
2024-02-06 21:02:16.534 [update notice] store 08 ident: done
2024-02-06 21:02:16.535 [update notice] sent scan-read scan.08  QQ=31: Vaillant;BAI00;0405;0803
2024-02-06 21:02:16.571 [main notice] found messages: 144 (3 conditional on 28 conditions, 0 poll, 10 update)
2024-02-06 21:02:21.770 [update notice] sent poll-read bai FlowTemp QQ=31: 45.94;ok
2024-02-06 21:02:25.123 [mqtt error] communication error: connection lost
2024-02-06 21:02:27.174 [update notice] sent poll-read bai FlowTempDesired QQ=31: 68.00