ebusd-configuration
ebusd-configuration copied to clipboard
Communication with ecoTEC plus stopped working
I was very happy with the eBUS adapter Shield v5 up until this night. My HAOS automation tried to set the desired temperature, but no success, got pretty warm in my flat ^^'
I tried re-flashing the shield, restarting ebusd, re-attaching bus, restarting the ecoTEC plus, no success
FW: 2024-01-06
Logs:
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=********* --scanconfig --mqttjson --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.0.154:9999 --log=all:notice
2024-02-24 07:21:09.753 [main notice] ebusd 23.2.p20230716 started with auto scan on device: 192.168.0.154:9999, enhanced
2024-02-24 07:21:10.442 [bus notice] device status: resetting
2024-02-24 07:21:10.443 [bus notice] bus started with own address 31/36
2024-02-24 07:21:10.504 [bus notice] signal acquired
2024-02-24 07:21:10.659 [bus notice] device status: reset, supports info
2024-02-24 07:21:10.801 [bus notice] device status: extra info: firmware 1.1[4106].1[4106], jumpers 0x0f
2024-02-24 07:21:10.952 [mqtt notice] connection established
2024-02-24 07:21:14.075 [bus notice] new master 10, master count 2
2024-02-24 07:21:14.084 [bus notice] new master 03, master count 3
2024-02-24 07:21:14.085 [update notice] received unknown MS cmd: 1008b5110101 / 095b5d008055610000ff
2024-02-24 07:21:18.284 [update notice] received unknown MS cmd: 1008b510090000005affff45ff00 / 0101
2024-02-24 07:21:20.612 [main error] scan config 08: ERR: SYN received
2024-02-24 07:21:22.823 [main error] scan config 15: ERR: SYN received
2024-02-24 07:21:22.875 [bus notice] arbitration won in invalid state ready
2024-02-24 07:21:24.566 [update notice] received unknown MS cmd: 1008b5110101 / 095b5c008055610000ff
2024-02-24 07:21:26.684 [update notice] received unknown MS cmd: 1008b5110102 / 06013c9646825a
2024-02-24 07:21:28.762 [update notice] received unknown MS cmd: 1008b510090000005affff45ff00 / 0101
2024-02-24 07:21:34.971 [main error] scan config 08: ERR: SYN received
2024-02-24 07:21:35.279 [update notice] received unknown MS cmd: 1008b5110101 / 095b5c008055610000ff
2024-02-24 07:21:37.193 [update notice] received unknown MS cmd: 1008b5040100 / 0a00ffffffffffffff0080
2024-02-24 07:21:37.307 [main error] scan config 15: ERR: SYN received
2024-02-24 07:21:37.400 [bus notice] arbitration won in invalid state ready
2024-02-24 07:21:49.647 [main error] scan config 08: ERR: SYN received
2024-02-24 07:21:49.648 [bus notice] arbitration won in invalid state ready
2024-02-24 07:21:50.171 [bus notice] arbitration won in invalid state ready
2024-02-24 07:21:51.786 [main error] scan config 15: ERR: SYN received
2024-02-24 07:21:56.090 [update notice] received unknown BC cmd: 10feb516080033070901010510
2024-02-24 07:21:56.281 [update notice] received unknown MS cmd: 1008b512020064 / 00
2024-02-24 07:22:00.294 [update notice] received unknown MS cmd: 1008b510090000005affff45ff00 / 0101
2024-02-24 07:22:03.999 [main error] scan config 08: ERR: read timeout
2024-02-24 07:22:04.674 [update notice] received unknown MS cmd: 1008b5110101 / 095b5c008055600000ff
2024-02-24 07:22:06.151 [main error] scan config 15: ERR: SYN received
2024-02-24 07:22:06.602 [update notice] received unknown MS cmd: 1008b5040100 / 0a00ffffffffffffff0080
2024-02-24 07:22:06.834 [update notice] received unknown MS cmd: 1008b5110102 / 06013c9646825a
2024-02-24 07:22:08.717 [update notice] received unknown MS cmd: 1008b510090000005affff45ff00 / 0101
2024-02-24 07:22:18.367 [main error] scan config 15: ERR: SYN received
2024-02-24 07:22:18.422 [bus notice] arbitration won in invalid state ready
2024-02-24 07:22:19.182 [update notice] received unknown MS cmd: 1008b510090000005affff45ff00 / 0101
2024-02-24 07:22:23.414 [update notice] received unknown MS cmd: 1008b5110101 / 095b5c008055600000ff
2024-02-24 07:22:25.534 [update notice] received unknown MS cmd: 1008b5110102 / 06013c9646825a
2024-02-24 07:22:29.680 [update notice] received unknown MS cmd: 1008b510090000005affff45ff00 / 0101
2024-02-24 07:22:30.551 [main error] scan config 15: ERR: SYN received
2024-02-24 07:22:30.552 [bus notice] arbitration won in invalid state ready
2024-02-24 07:22:33.912 [update notice] received unknown MS cmd: 1008b5110101 / 095b5c008055600000ff
2024-02-24 07:22:40.194 [update notice] received unknown MS cmd: 1008b510090000005affff45ff00 / 0101
2024-02-24 07:22:42.768 [main error] scan config 08: ERR: SYN received
2024-02-24 07:22:42.769 [bus notice] arbitration won in invalid state ready
2024-02-24 07:22:44.394 [update notice] received unknown MS cmd: 1008b5110101 / 095b5c008055600000ff
2024-02-24 07:22:44.906 [main error] scan config 15: ERR: SYN received
2024-02-24 07:22:48.607 [update notice] received unknown MS cmd: 1008b510090000005affff45ff00 / 0101
I enabled debug logs to get more information:
2024-02-24 07:34:30.554 [mqtt debug] publish ebusd/global/uptime 224
2024-02-24 07:34:32.544 [main debug] performing regular tasks
2024-02-24 07:34:32.544 [bus info] scan 08 cmd: 3108070400
2024-02-24 07:34:32.562 [bus debug] start request 31
2024-02-24 07:34:32.562 [bus debug] arbitration start with 31
2024-02-24 07:34:32.687 [bus debug] arbitration won
2024-02-24 07:34:32.687 [bus debug] arbitration delay 12 micros
2024-02-24 07:34:32.687 [bus debug] switching from ready to send command
2024-02-24 07:34:32.709 [bus debug] notify request: ERR: SYN received
2024-02-24 07:34:32.709 [bus debug] ERR: SYN received during send command, switching to ready
2024-02-24 07:34:32.709 [main error] scan config 08: ERR: SYN received
2024-02-24 07:34:32.709 [mqtt debug] publish ebusd/global/scan "running"
2024-02-24 07:34:32.902 [bus debug] ERR: read timeout during receive command, switching to skip
2024-02-24 07:34:34.709 [main debug] performing regular tasks
2024-02-24 07:34:34.710 [bus info] scan 15 cmd: 3115070400
2024-02-24 07:34:34.751 [bus debug] start request 31
2024-02-24 07:34:34.751 [bus debug] arbitration start with 31
2024-02-24 07:34:34.838 [bus debug] arbitration won
2024-02-24 07:34:34.838 [bus debug] arbitration delay 10 micros
2024-02-24 07:34:34.838 [bus debug] switching from ready to send command
2024-02-24 07:34:34.876 [bus debug] notify request: ERR: SYN received
2024-02-24 07:34:34.876 [bus debug] ERR: SYN received during send command, switching to ready
2024-02-24 07:34:34.876 [main error] scan config 15: ERR: SYN received
2024-02-24 07:34:34.983 [bus debug] ERR: SYN received during receive command, switching to ready
Just downgraded the shield to 20231223 which seems to fixed the issue :thinking: