john30 / ebusd

daemon for communication with eBUS heating systems
GNU General Public License v3.0
563 stars 130 forks source link

Several different kinds of arbitration errors w/ ebus shield v5 #1331

Closed mikopp closed 2 weeks ago

mikopp commented 2 weeks ago

Description

Hi John,

I face several different arbitration errors.

1) I have a recovair 275. This is working just fine. However I built an automation that turns off the power for it when the outside air is to moist or too hot so as to not get that inside. When I do that and the device is off for some hours and then turns on again, the log file shows arbitration lost error messages...I don't have the log file handy anymore, once I see it again I'll submit it.

ebusd is running while the power is off, and tries to read which of course it can't. The only solve is to physically remove the power from the ebus shield v5 and plug it in again, then it recovers.

Do you know why this happens? can I recover in some other means that does not require me to physically reboot the shield?

2) sometimes when the loxberry boots and changes the time too late with ntp I also get arbitration errors. Again the only solve is to physically reboot by power cycling the shield. I have in the mean time worked to ensure ntp is fully synced before ebus starts, but I still wonder how to avoid the physical power cycle

3) I now get arbitration lost error on my geotherm vs 83 for some read operations

2024-09-02 14:34:15.907 [update notice] received unknown MS cmd: 7050b5040132 / 0a001e00030102f0150101
2024-09-02 14:34:16.046 [update notice] received unknown MS cmd: 1050b5040132 / 0a001e00030102f0150101
2024-09-02 14:34:16.199 [bus error] poll ehp HeatpumpType failed: ERR: arbitration lost
2024-09-02 14:34:16.306 [update notice] received write mc RoomTempOffset QQ=70: 0.00
2024-09-02 14:34:16.500 [update notice] received unknown MS cmd: 7050b50503436e01 / 00
2024-09-02 14:34:16.605 [update notice] received unknown MS cmd: 1050b5040131 / 020002
2024-09-02 14:34:17.011 [update notice] received read mc Status16 QQ=70: 28.69
2024-09-02 14:35:15.766 [update notice] received unknown MS cmd: 1050b5040132 / 0a001e00030102f0150101
2024-09-02 14:35:15.915 [update notice] received unknown MS cmd: 1050b5040131 / 020002
2024-09-02 14:35:16.009 [update notice] received read mc Mode QQ=70: 21;off;0;0;disabled;pool;day
2024-09-02 14:35:16.083 [update notice] sent poll-read uih YieldThisYear QQ=31: 1360;772;623;420;176;156;137;82;0;0;0;0
2024-09-02 14:35:16.279 [bus error] poll uih YieldThisYear failed: ERR: arbitration lost
2024-09-02 14:35:16.395 [update notice] received read mc Status QQ=70: 0;off;28.62;5
2024-09-02 14:35:16.579 [update notice] received unknown MS cmd: 7050b5040132 / 0a001e00030102f0150101
2024-09-02 14:35:16.733 [update notice] received write mc RoomTempOffset QQ=70: 0.00
2024-09-02 14:35:17.015 [update notice] received unknown MS cmd: 7050b50503436e01 / 00
2024-09-02 14:35:19.176 [update notice] received update-read broadcast hwcStatus QQ=10: off;26;off
2024-09-02 14:35:19.350 [update notice] received unknown BC cmd: 10feb505034a0200
2

99% of requests are successful though, so I am not sure what is up

One piece of extra info, I run two shields (recovair + geotherm) and thus two ebusd on a loxberry (rasberry pi 4) connected both with usb and enhanced arbitration

root 83068 1 0 Sep01 ? 00:10:01 /usr/bin/ebusd --pidfile=/var/run/ebusd2.pid --mqttport=1883 --mqttpass= --mqttuser=loxberry -c /etc/ebusd/config/ebusd-configuration/latest/de --scanconfig -d ens:/dev/ttyACM1 -p 8889 -l /var/log/ebusd2.log root 83121 1 0 Sep01 ? 00:11:08 /usr/bin/ebusd --mqttport=1883 --mqttpass= --mqttuser=loxberry -c /etc/ebusd/config/ebusd-configuration/latest/de --scanconfig -d ens:/dev/ttyACM0

Thanks Mike

PS: I'm from Austria, so if you want to switch to German, go ahead.

Actual behavior

getting arbitration errors when air flow looses power and gets it again and in other situations

Expected behavior

I want to avoid the error message in the first place, but if that is not possible, would like a software solve instead of physically having to go to my basement and reboot the shields ;)

ebusd version

23.3

ebusd arguments

--mqttport=1883 --mqttpass= --mqttuser=loxberry -c /etc/ebusd/config/ebusd-configuration/latest/de --scanconfig -d ens:/dev/ttyACM0

Operating system

Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite)

CPU architecture

arm64

Dockerized

None

Hardware interface

Adapter Shield v5 via USB

Related integration

MQTT generic

Logs

2024-09-02 14:34:15.907 [update notice] received unknown MS cmd: 7050b5040132 / 0a001e00030102f0150101 2024-09-02 14:34:16.046 [update notice] received unknown MS cmd: 1050b5040132 / 0a001e00030102f0150101 2024-09-02 14:34:16.199 [bus error] poll ehp HeatpumpType failed: ERR: arbitration lost 2024-09-02 14:34:16.306 [update notice] received write mc RoomTempOffset QQ=70: 0.00 2024-09-02 14:34:16.500 [update notice] received unknown MS cmd: 7050b50503436e01 / 00 2024-09-02 14:34:16.605 [update notice] received unknown MS cmd: 1050b5040131 / 020002 2024-09-02 14:34:17.011 [update notice] received read mc Status16 QQ=70: 28.69 2024-09-02 14:35:15.766 [update notice] received unknown MS cmd: 1050b5040132 / 0a001e00030102f0150101 2024-09-02 14:35:15.915 [update notice] received unknown MS cmd: 1050b5040131 / 020002 2024-09-02 14:35:16.009 [update notice] received read mc Mode QQ=70: 21;off;0;0;disabled;pool;day 2024-09-02 14:35:16.083 [update notice] sent poll-read uih YieldThisYear QQ=31: 1360;772;623;420;176;156;137;82;0;0;0;0 2024-09-02 14:35:16.279 [bus error] poll uih YieldThisYear failed: ERR: arbitration lost 2024-09-02 14:35:16.395 [update notice] received read mc Status QQ=70: 0;off;28.62;5 2024-09-02 14:35:16.579 [update notice] received unknown MS cmd: 7050b5040132 / 0a001e00030102f0150101 2024-09-02 14:35:16.733 [update notice] received write mc RoomTempOffset QQ=70: 0.00 2024-09-02 14:35:17.015 [update notice] received unknown MS cmd: 7050b50503436e01 / 00 2024-09-02 14:35:19.176 [update notice] received update-read broadcast hwcStatus QQ=10: off;26;off 2024-09-02 14:35:19.350 [update notice] received unknown BC cmd: 10feb505034a0200

john30 commented 2 weeks ago

the arbitration wrt poll is answered here: https://github.com/john30/ebusd-esp32/issues/14#issuecomment-2330578593 for the potential issue with the adapter not connecting to wifi during power off-on (if I understood it correctly), please open an issue in the right repo if desired (and also state the version currently in use): https://github.com/john30/ebusd-esp32/issues other than that I don't see an ebusd issue here, so closing

mikopp commented 2 weeks ago

@john30 there is no wifi issue. the adapters are connected via usb and connected to ebus via cable of course. I am confused what this has to do with esp32.

The issue is that if the KWL device is powered off, the ebusd of course keeps running. once the KWL device is powered back on the ebusd is producing errors and can't read or write anymore until I do a power cycle on the ebus shield v5 adapter.

Can you let me know what you need to analyse this? again no wifi nor network issue here.