ebusd stopped working - log analysis needed

[sebska]

Hi there,

i had a running ebusd-Addon in Homeassistant. Since it is summer I did not notice when it stopped working (01. Jun2025 22:00:00).
But now I can not understand what happened.

I have a eBUS Adapter Shield v5:

Build: [20250615](https://adapter.ebusd.eu/v5/ChangeLog#20250615)
[ebusd device string](https://github.com/john30/ebusd/wiki/2.-Run#device-options): "ens:192.168.7.130:9999" or "mdns:64e833095f24" since ebusd 24.1
WiFi station/client: xxxxxxxx, 192.168.7.130, 36% (-82dBm)
WiFi access point: inactive
Chip ID: 64e833095f24, ESP32-C3, rev 4
Hostname: ebus
Up time: 00:02:57 / 177 s
Free heap: 78972 / 253844
ebusd connected: yes (inactive)
eBUS signal: no signal

Within HomeAssistant i am using [https://github.com/LukasGrebe/ha-addons] and currently the Version is 25.1.0

The Logs show (notice):

s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
2025-06-18 14:52:58.578 [main notice] SIGTERM received
2025-06-18 14:52:59.319 [device error] transport closed
2025-06-18 14:52:59.324 [main notice] ebusd stopped
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 --httpport=8889 --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=che8Guas3ooza2eeGipei2MavajiWei7isoh0waung1eechohduk2bahz4efeipu --scanconfig --mqttjson --configpath=/config/ebusd --accesslevel=* --mqttint=/config/ebusd/mqtt-hassio.cfg --mqttvar=filter-name= --mqtttopic=EBusD --device=ens:192.168.7.130:9999 --log=all:notice --configlang=de
2025-06-18 14:53:09.509 [device notice] transport opened
2025-06-18 14:53:09.515 [main notice] ebusd 25.1.p20250414 started with broadcast scan on device: 192.168.7.130:9999, TCP, enhanced
2025-06-18 14:53:09.519 [bus notice] bus started with own address 31/36
2025-06-18 14:53:09.519 [device notice] reset, supports info
2025-06-18 14:53:09.522 [device notice] extra info: firmware 1.1[560f].1[560f], jumpers 0x0b
2025-06-18 14:53:09.830 [mqtt notice] connection established
2025-06-18 14:55:04.688 [bus notice] signal acquired
2025-06-18 14:55:06.062 [bus error] signal lost
2025-06-18 14:55:16.971 [device error] transport closed
2025-06-18 14:55:16.971 [bus notice] device invalid
2025-06-18 14:55:19.732 [main notice] update check: revision 25.1 available
2025-06-18 14:55:22.016 [device error] transport closed
2025-06-18 14:55:22.016 [bus error] unable to open 192.168.7.130:9999: ERR: generic I/O error
2025-06-18 14:55:22.016 [bus notice] device invalid
2025-06-18 14:55:28.048 [device notice] transport opened
2025-06-18 14:55:28.048 [bus notice] re-opened 192.168.7.130:9999
2025-06-18 14:55:28.052 [device notice] reset, supports info

Info:

s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
2025-06-18 15:00:10.687 [main notice] SIGTERM received
2025-06-18 15:00:11.206 [device error] transport closed
2025-06-18 15:00:11.206 [main notice] ebusd stopped
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 --httpport=8889 --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=che8Guas3ooza2eeGipei2MavajiWei7isoh0waung1eechohduk2bahz4efeipu --scanconfig --mqttjson --configpath=/config/ebusd --accesslevel=* --mqttint=/config/ebusd/mqtt-hassio.cfg --mqttvar=filter-name= --mqtttopic=EBusD --device=ens:192.168.7.130:9999 --log=all:info --configlang=de
2025-06-18 15:00:17.193 [device notice] transport opened
2025-06-18 15:00:17.194 [main info] registering data handlers
2025-06-18 15:00:17.196 [mqtt info] mosquitto version 2.0.20 (compiled with 2.0.20)
2025-06-18 15:00:17.197 [main info] registered data handlers
2025-06-18 15:00:17.197 [main notice] ebusd 25.1.p20250414 started with broadcast scan on device: 192.168.7.130:9999, TCP, enhanced
2025-06-18 15:00:17.197 [main info] loading configuration files from /config/ebusd/
2025-06-18 15:00:17.197 [main info] reading templates /
2025-06-18 15:00:17.198 [main info] read templates in /
2025-06-18 15:00:17.198 [main info] reading file memory.csv
2025-06-18 15:00:17.200 [main info] successfully read file memory.csv
2025-06-18 15:00:17.200 [main info] reading file broadcast.csv
2025-06-18 15:00:17.200 [main info] successfully read file broadcast.csv
2025-06-18 15:00:17.200 [main info] read config files, got 11 messages
2025-06-18 15:00:17.201 [bus notice] bus started with own address 31/36
2025-06-18 15:00:17.201 [device notice] reset, supports info
2025-06-18 15:00:17.203 [device notice] extra info: firmware 1.1[560f].1[560f], jumpers 0x0b
2025-06-18 15:00:17.512 [mqtt notice] connection established
2025-06-18 15:00:20.498 [network info] [00001] client connection opened 127.0.0.1
2025-06-18 15:00:20.498 [network info] [00001] connection closed
2025-06-18 15:02:27.344 [device notice] extra info: ID 64e833095f24210000
2025-06-18 15:02:27.424 [main notice] update check: revision 25.1 available, device firmware v5 1[560f] up to date
2025-06-18 14:55:28.057 [device notice] extra info: firmware 1.1[560f].1[560f], jumpers 0x0b

Can anybody help me to sort out, what went wrong?

Regards
Sebastian

[sebska]

Hi there,

is is working again. There was the ebus-cable broken: eBUS signal: no signal in the Adapter Shield said it all....

I was so blind.

Sebastian