john30
Connection to ebus adapter lost until adapter or ebusd is restarted
Hi, I have finally managed to configure WiFi ebus adapter with my Vaillant ecoTEC and home assistant using MQTT. In home assistant I register like 10 Vaillant variables to be polled automatically. Some are registered as ?1 polls, some as ?9 polls. It runs fine for few hours only and then it hangs. To be precise, ebusd stops retrieving polled variables from ebus adapter/ebus. Ebus adapter is still alive, connected to the network, sending 0xaa(SYN) and 0xc6(CRC) bytes, TCP stack of the "ebusd machine" sends ACK to these packets but there is no more communication from ebusd side.
Diggind deeper into the issue it turns out that there is some intermittent network issue or ebus adapter issue which causes TCP retransmits. After these retransmits ebus adapter is only sending 0xaa and 0xc6, ebusd ACKs these messages and that is all, what happens further.
If I reload ebusd or adapter it runs fine again.
EBUSD_OPTS="--dumpfile=/var/log/dump.log --lograwdatafile=/var/log/raw.log --pollinterval=10 --acquireretries=6 --acquiretimeout=30 --receivetimeout=75 --sendretries=6 --scanconfig=08 --configpath=/root/ecotec -d enh:192.168.2.5:9999 --mqtthost=192.168.2.7 --mqttport=1883 --mqttlog --mqttversion=3.1.1 --loglevel=debug"
Snapshot of the ebusd log: 2021-04-19 12:06:36.030 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1333, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:06:36.030 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:06:38.032 [mqtt debug] publish ebusd/bai/WP off 2021-04-19 12:06:38.032 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1334, 'ebusd/bai/WP', ... (3 bytes)) 2021-04-19 12:06:38.033 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WP', ... (3 bytes)) 2021-04-19 12:06:42.710 [main debug] performing regular tasks 2021-04-19 12:06:43.070 [bus info] poll cmd: 3108b509030d5500 2021-04-19 12:06:43.070 [bus debug] start request 31 2021-04-19 12:06:43.070 [bus debug] arbitration start with 31 2021-04-19 12:06:44.044 [bus error] poll bai HwcWaterflow failed: ERR: no signal 2021-04-19 12:06:44.044 [bus debug] ERR: read timeout during skip, switching to no signal 2021-04-19 12:06:44.044 [bus error] signal lost 2021-04-19 12:06:44.447 [bus debug] ERR: SYN received during no signal, switching to ready 2021-04-19 12:06:44.447 [bus notice] signal acquired 2021-04-19 12:06:44.487 [bus error] device status: unexpected available enhanced byte 2 2021-04-19 12:06:52.046 [mqtt debug] publish ebusd/global/uptime 8945 2021-04-19 12:06:52.046 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1335, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:06:52.047 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:06:52.711 [main debug] performing regular tasks 2021-04-19 12:07:02.712 [main debug] performing regular tasks 2021-04-19 12:07:08.063 [mqtt debug] publish ebusd/global/uptime 8961 2021-04-19 12:07:08.063 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1336, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:07:08.064 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes)) ... ... ... ... 2021-04-19 12:07:24.079 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1337, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:07:24.079 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:07:32.714 [main debug] performing regular tasks 2021-04-19 12:07:35.034 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-04-19 12:07:40.093 [mqtt debug] publish ebusd/global/uptime 8993 2021-04-19 12:07:40.093 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1338, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:07:40.094 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:07:40.418 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-04-19 12:07:42.715 [main debug] performing regular tasks 2021-04-19 12:07:45.848 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-04-19 12:07:51.236 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-04-19 12:07:52.716 [main debug] performing regular tasks 2021-04-19 12:07:56.107 [mqtt debug] publish ebusd/global/uptime 9009 2021-04-19 12:07:56.107 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1339, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:07:56.107 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:08:02.716 [main debug] performing regular tasks 2021-04-19 12:08:12.123 [mqtt debug] publish ebusd/global/uptime 9025 2021-04-19 12:08:12.123 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1340, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:08:12.124 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:08:12.717 [main debug] performing regular tasks 2021-04-19 12:08:14.550 [bus error] device status: unexpected available enhanced byte 2 2021-04-19 12:08:22.718 [main debug] performing regular tasks 2021-04-19 12:08:28.133 [mqtt debug] publish ebusd/global/uptime 9041 2021-04-19 12:08:28.133 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1341, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:08:28.134 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:08:32.719 [main debug] performing regular tasks 2021-04-19 12:08:42.719 [main debug] performing regular tasks 2021-04-19 12:08:44.148 [mqtt debug] publish ebusd/global/uptime 9057 2021-04-19 12:08:44.148 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1342, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:08:44.149 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:08:52.720 [main debug] performing regular tasks 2021-04-19 12:09:00.162 [mqtt debug] publish ebusd/global/uptime 9073 2021-04-19 12:09:00.162 [mqtt debug] log Client ebusd_21.2_903 sending PUBLISH (d0, q0, r0, m1343, 'ebusd/global/uptime', ... (4 bytes)) 2021-04-19 12:09:00.163 [mqtt debug] log Client ebusd_21.2_903 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (4 bytes))
does this issue still persist? what does the Wemos status page look like in this situation?
Yes it still persists. I have removed lxc container reload from my crontab and the issue appeared immediately. Wemos status page increments uptime counter and shows: ebusd connected: yes (inactive); eBUS signal: acquired; Build: 20201122; ebusd device string: enh:192.168.x.y:9999; WiFi signal: 60% (-70dBm)
And log contains this sequence: 2021-10-11 10:35:35.347 [mqtt debug] log Client ebusd_21.2_72 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-10-11 10:35:38.336 [main debug] performing regular tasks 2021-10-11 10:35:48.337 [main debug] performing regular tasks 2021-10-11 10:35:51.362 [mqtt debug] publish ebusd/global/uptime 223008 2021-10-11 10:35:51.362 [mqtt debug] log Client ebusd_21.2_72 sending PUBLISH (d0, q0, r0, m14261, 'ebusd/global/uptime', ... (6 bytes)) 2021-10-11 10:35:51.363 [mqtt debug] log Client ebusd_21.2_72 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-10-11 10:35:52.009 [bus debug] ERR: read timeout during skip, switching to no signal 2021-10-11 10:35:52.010 [bus error] signal lost 2021-10-11 10:35:52.041 [bus debug] ERR: SYN received during no signal, switching to ready 2021-10-11 10:35:52.041 [bus notice] signal acquired 2021-10-11 10:35:52.044 [bus error] device status: unexpected available enhanced byte 2 2021-10-11 10:35:58.338 [main debug] performing regular tasks 2021-10-11 10:36:07.378 [mqtt debug] publish ebusd/global/uptime 223024 2021-10-11 10:36:07.378 [mqtt debug] log Client ebusd_21.2_72 sending PUBLISH (d0, q0, r0, m14262, 'ebusd/global/uptime', ... (6 bytes)) 2021-10-11 10:36:07.378 [mqtt debug] log Client ebusd_21.2_72 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-10-11 10:36:08.338 [main debug] performing regular tasks
I don't think so. The Wemos has external antenna and AP is 3 meters away from Wemos...
Maybe, but in my case heap size is reported above 30K and does not drop rapidly in minutes. For example: Up time: 1956 Free heap: 31664
Maybe, but in my case heap size is reported above 30K and does not drop rapidly in minutes. For example: Up time: 1956 Free heap: 31664
+1 heap size stays above 30k, even when uptime is more than a couple of hours
so is this an adapter 3 or something else? if adapter 3, did you set the jumpers correctly? your mentioned CRC in the first post isn't a CRC but part of the enhanced protocol
so is this an adapter 3 or something else? if adapter 3, did you set the jumpers correctly? your mentioned CRC in the first post isn't a CRC but part of the enhanced protocol
in my case it's an adapter 3, yes. jumpers are set appropriately according to the guide (https://adapter.ebusd.eu/img/smd-wifi.jpg). can't speak for @mbisak
which versions do you use? ebusd and abusd-esp please provide some ebusd logging
ebusd = latest docker release (= ebusd 21.2.v21.2-48-g24a6525) ebusd-esp = build 20201122
the error happens after some time, there is no indication/event like WiFi disconnect before the occurence. somehow the connection between ebusd and the Adapter seems to get stuck and remains in an unresponsive state - reading or writing to the bus is not possible then and the custom defined priority polls are stopped being polled from that point on. note that if the problem occurs, issuing "ebusctl info" within the docker container becomes unresponsive aswell while the log still continues. not every restart of the ebusd container fixes the problem. sometimes 2-3 attempts are needed to make it work again. I've attached the log from 2 hours of today, since the error itself may not be sufficient. at 15:38 the container has been restarted, since then sending and reading from the bus has been working again without an issue (by the time of writing).
which versions do you use? ebusd and abusd-esp please provide some ebusd logging
I use adapter version 3, ebusd-esp HW, firmware for Wemos D1 mini Pro. configured as Adapter 3 Rx+Tx, ebusd 21.2.v21.2, jumpers set as on the pictures.
BR, Martin
localhost: i
version: ebusd 21.2.v21.2
update check: OK, broadcast.csv: different version available, memory.csv: different version available, vaillant/08.bai.csv: different version available, vaillant/broadcast.csv: different version available, vaillant/errors.inc: different version available, vaillant/general.csv: different version available
signal: acquired
symbol rate: 23
max symbol rate: 101
min arbitration micros: 1
max arbitration micros: 92
min symbol latency: 9
max symbol latency: 39
reconnects: 0
masters: 2
messages: 213
conditional: 3
poll: 23
update: 8
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0105;HW=7803", loaded "vaillant/bai.0010021877.inc" ([PROD='0010021877']), "vaillant/08.bai.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
Hi, seems fixed with new version. I have also upgraded ebusd virtual machine to Debian 11. It works fine since yesterday evening. I will update the case in few days.
Martin
please try with a build from the latest sources
are you referring to ebusd or ebusd-esp?
unfortunately failed again. I will monitor it closely to get the exact logs when it fails...
Failed again: 2021-11-23 08:51:18.200 [update notice] sent poll-read bai ModulationTempDesired QQ=31: 28.0 2021-11-23 08:51:18.201 [bus debug] notify request: done 2021-11-23 08:51:18.201 [bus debug] switching from send response ACK to send SYN 2021-11-23 08:51:18.213 [bus debug] send/receive symbol latency 12 ms 2021-11-23 08:51:19.704 [main debug] performing regular tasks 2021-11-23 08:51:19.933 [mqtt debug] publish ebusd/bai/ModulationTempDesired 28.0 2021-11-23 08:51:19.933 [mqtt debug] log Client ebusd_21.3_2779 sending PUBLISH (d0, q0, r0, m5140, 'ebusd/bai/M odulationTempDesired', ... (4 bytes)) 2021-11-23 08:51:19.934 [mqtt debug] log Client ebusd_21.3_2779 received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/Mod ulationTempDesired', ... (4 bytes)) 2021-11-23 08:51:25.938 [mqtt debug] publish ebusd/global/uptime 34324 2021-11-23 08:51:25.938 [mqtt debug] log Client ebusd_21.3_2779 sending PUBLISH (d0, q0, r0, m5141, 'ebusd/globa l/uptime', ... (5 bytes)) 2021-11-23 08:51:25.939 [mqtt debug] log Client ebusd_21.3_2779 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/ uptime', ... (5 bytes)) 2021-11-23 08:51:29.054 [bus info] poll cmd: 3108b509030d9800 2021-11-23 08:51:29.054 [bus debug] start request 31 2021-11-23 08:51:29.054 [bus debug] arbitration start with 31 2021-11-23 08:51:29.704 [main debug] performing regular tasks 2021-11-23 08:51:30.026 [bus error] device status: unexpected available enhanced byte 2 2021-11-23 08:51:30.042 [bus debug] arbitration won 2021-11-23 08:51:30.042 [bus debug] arbitration delay 2 micros 2021-11-23 08:51:30.042 [bus debug] switching from ready to send command 2021-11-23 08:51:30.053 [bus debug] send/receive symbol latency 10 ms 2021-11-23 08:51:30.063 [bus debug] send/receive symbol latency 10 ms 2021-11-23 08:51:30.074 [bus debug] send/receive symbol latency 10 ms 2021-11-23 08:51:30.084 [bus debug] send/receive symbol latency 9 ms 2021-11-23 08:51:30.134 [bus debug] notify request: ERR: read timeout 2021-11-23 08:51:30.134 [bus error] poll bai ReturnTemp failed: ERR: read timeout 2021-11-23 08:51:30.134 [bus debug] ERR: read timeout during send command, switching to skip 2021-11-23 08:51:32.048 [bus debug] ERR: read timeout during skip, switching to no signal 2021-11-23 08:51:32.048 [bus error] signal lost 2021-11-23 08:51:38.090 [bus notice] signal acquired 2021-11-23 08:51:39.022 [bus notice] max. symbols per second: 153 2021-11-23 08:51:39.704 [main debug] performing regular tasks 2021-11-23 08:51:40.039 [bus info] poll cmd: 3108b509030d0500 2021-11-23 08:51:40.039 [bus debug] start request 31 2021-11-23 08:51:40.039 [bus debug] arbitration start with 31 2021-11-23 08:51:40.132 [bus debug] arbitration won 2021-11-23 08:51:40.132 [bus debug] arbitration delay 3 micros 2021-11-23 08:51:40.132 [bus debug] switching from ready to send command 2021-11-23 08:51:40.132 [bus debug] notify request: ERR: SYN received 2021-11-23 08:51:40.132 [bus error] poll bai Flame failed: ERR: SYN received 2021-11-23 08:51:40.132 [bus debug] ERR: SYN received during send command, switching to ready 2021-11-23 08:51:40.186 [bus debug] ERR: SYN received during receive command, switching to ready 2021-11-23 08:51:41.954 [mqtt debug] publish ebusd/global/uptime 34340 2021-11-23 08:51:41.954 [mqtt debug] log Client ebusd_21.3_2779 sending PUBLISH (d0, q0, r0, m5142, 'ebusd/global/uptime', ... (5 bytes)) 2021-11-23 08:51:41.954 [mqtt debug] log Client ebusd_21.3_2779 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (5 bytes)) 2021-11-23 08:51:42.841 [bus error] device status: unexpected available enhanced byte 2 2021-11-23 08:51:49.705 [main debug] performing regular tasks 2021-11-23 08:51:51.052 [bus info] poll cmd: 3108b509030d0200 2021-11-23 08:51:51.053 [bus debug] start request 31 2021-11-23 08:51:51.053 [bus debug] arbitration start with 31 2021-11-23 08:51:51.105 [bus debug] arbitration won 2021-11-23 08:51:51.105 [bus debug] arbitration delay 3 micros 2021-11-23 08:51:51.105 [bus debug] switching from ready to send command 2021-11-23 08:51:51.122 [bus debug] send/receive symbol latency 16 ms 2021-11-23 08:51:51.132 [bus debug] send/receive symbol latency 10 ms 2021-11-23 08:51:51.142 [bus debug] send/receive symbol latency 9 ms 2021-11-23 08:51:51.151 [bus debug] send/receive symbol latency 9 ms 2021-11-23 08:51:51.162 [bus debug] send/receive symbol latency 10 ms 2021-11-23 08:51:51.176 [bus debug] send/receive symbol latency 13 ms 2021-11-23 08:51:51.185 [bus debug] send/receive symbol latency 9 ms 2021-11-23 08:51:51.186 [bus debug] switching from send command to send command CRC 2021-11-23 08:51:51.196 [bus debug] send/receive symbol latency 10 ms 2021-11-23 08:51:51.196 [bus debug] switching from send command CRC to receive command ACK 2021-11-23 08:51:51.200 [bus debug] switching from receive command ACK to receive response 2021-11-23 08:51:51.224 [bus debug] switching from receive response to receive response CRC 2021-11-23 08:51:51.227 [bus debug] switching from receive response CRC to send response ACK 2021-11-23 08:51:51.236 [bus debug] send/receive symbol latency 9 ms 2021-11-23 08:51:51.236 [update info] sent MS cmd: 3108b509030d0200 / 03fe0700 2021-11-23 08:51:51.237 [update notice] sent poll-read bai WaterPressure QQ=31: 2.046;ok 2021-11-23 08:51:51.237 [bus debug] notify request: done 2021-11-23 08:51:51.237 [bus debug] switching from send response ACK to send SYN 2021-11-23 08:51:51.247 [bus debug] send/receive symbol latency 10 ms 2021-11-23 08:51:54.967 [mqtt debug] publish ebusd/bai/WaterPressure 2.046;ok 2021-11-23 08:51:54.967 [mqtt debug] log Client ebusd_21.3_2779 sending PUBLISH (d0, q0, r0, m5143, 'ebusd/bai/WaterPressure', ... (8 bytes)) 2021-11-23 08:51:54.967 [mqtt debug] log Client ebusd_21.3_2779 received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/WaterPressure', ... (8 bytes)) 2021-11-23 08:51:57.970 [mqtt debug] publish ebusd/global/uptime 34356 2021-11-23 08:51:57.970 [mqtt debug] log Client ebusd_21.3_2779 sending PUBLISH (d0, q0, r0, m5144, 'ebusd/global/uptime', ... (5 bytes)) 2021-11-23 08:51:57.971 [mqtt debug] log Client ebusd_21.3_2779 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (5 bytes)) 2021-11-23 08:51:59.705 [main debug] performing regular tasks 2021-11-23 08:52:02.058 [bus info] poll cmd: 3108b509030d0d00 2021-11-23 08:52:02.058 [bus debug] start request 31 2021-11-23 08:52:02.058 [bus debug] arbitration start with 31 2021-11-23 08:52:02.614 [bus debug] arbitration won 2021-11-23 08:52:02.614 [bus debug] arbitration delay 7 micros 2021-11-23 08:52:02.614 [bus debug] switching from ready to send command 2021-11-23 08:52:02.614 [bus debug] notify request: ERR: SYN received 2021-11-23 08:52:02.614 [bus error] poll bai GasvalveUC failed: ERR: SYN received 2021-11-23 08:52:02.614 [bus debug] ERR: SYN received during send command, switching to ready 2021-11-23 08:52:02.671 [bus debug] ERR: SYN received during receive command, switching to ready 2021-11-23 08:52:09.706 [main debug] performing regular tasks 2021-11-23 08:52:13.070 [bus debug] ERR: read timeout during skip, switching to no signal 2021-11-23 08:52:13.070 [bus error] signal lost 2021-11-23 08:52:13.229 [bus debug] ERR: SYN received during no signal, switching to ready 2021-11-23 08:52:13.229 [bus notice] signal acquired 2021-11-23 08:52:13.229 [bus info] poll cmd: 3108b509030d4400 2021-11-23 08:52:13.229 [bus debug] start request 31 2021-11-23 08:52:13.229 [bus debug] arbitration start with 31 2021-11-23 08:52:13.233 [bus error] device status: unexpected available enhanced following byte 1 2021-11-23 08:52:13.409 [bus debug] arbitration won 2021-11-23 08:52:13.409 [bus debug] arbitration delay 2 micros 2021-11-23 08:52:13.409 [bus debug] switching from ready to send command 2021-11-23 08:52:13.416 [bus debug] notify request: ERR: SYN received 2021-11-23 08:52:13.416 [bus error] poll bai WP failed: ERR: SYN received 2021-11-23 08:52:13.416 [bus debug] ERR: SYN received during send command, switching to ready 2021-11-23 08:52:13.474 [bus debug] ERR: SYN received during receive command, switching to ready 2021-11-23 08:52:13.986 [mqtt debug] publish ebusd/global/uptime 34372 2021-11-23 08:52:13.986 [mqtt debug] log Client ebusd_21.3_2779 sending PUBLISH (d0, q0, r0, m5145, 'ebusd/global/uptime', ... (5 bytes)) 2021-11-23 08:52:13.986 [mqtt debug] log Client ebusd_21.3_2779 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (5 bytes)) 2021-11-23 08:52:18.349 [bus error] device status: unexpected available enhanced byte 2 2021-11-23 08:52:19.706 [main debug] performing regular tasks 2021-11-23 08:52:19.827 [bus error] device status: unexpected available enhanced following byte 1 2021-11-23 08:52:22.031 [bus debug] ERR: read timeout during skip, switching to no signal 2021-11-23 08:52:22.031 [bus error] signal lost 2021-11-23 08:52:25.314 [bus debug] ERR: SYN received during no signal, switching to ready 2021-11-23 08:52:25.314 [bus notice] signal acquired 2021-11-23 08:52:25.314 [bus info] poll cmd: 3108b509030d5500 2021-11-23 08:52:25.314 [bus debug] start request 31 2021-11-23 08:52:25.314 [bus debug] arbitration start with 31 2021-11-23 08:52:25.532 [bus error] device status: unexpected available enhanced following byte 1 2021-11-23 08:52:26.917 [bus error] device status: unexpected available enhanced following byte 1 2021-11-23 08:52:27.094 [bus debug] arbitration won 2021-11-23 08:52:27.094 [bus debug] arbitration delay 1 micros 2021-11-23 08:52:27.094 [bus debug] switching from ready to send command 2021-11-23 08:52:27.095 [bus debug] notify request: ERR: SYN received 2021-11-23 08:52:27.095 [bus error] poll bai HwcWaterflow failed: ERR: SYN received 2021-11-23 08:52:27.095 [bus debug] ERR: SYN received during send command, switching to ready 2021-11-23 08:52:27.160 [bus debug] ERR: SYN received during receive command, switching to ready 2021-11-23 08:52:29.707 [main debug] performing regular tasks 2021-11-23 08:52:30.002 [mqtt debug] publish ebusd/global/uptime 34388 2021-11-23 08:52:30.002 [mqtt debug] log Client ebusd_21.3_2779 sending PUBLISH (d0, q0, r0, m5146, 'ebusd/global/uptime', ... (5 bytes)) 2021-11-23 08:52:30.002 [mqtt debug] log Client ebusd_21.3_2779 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (5 bytes)) 2021-11-23 08:52:36.063 [bus info] poll cmd: 3108b509030d1600 2021-11-23 08:52:36.063 [bus debug] start request 31 2021-11-23 08:52:36.063 [bus debug] arbitration start with 31 2021-11-23 08:52:36.106 [bus debug] arbitration won 2021-11-23 08:52:36.106 [bus debug] arbitration delay 5 micros 2021-11-23 08:52:36.106 [bus debug] switching from ready to send command 2021-11-23 08:52:36.116 [bus debug] send/receive symbol latency 9 ms 2021-11-23 08:52:36.126 [bus debug] send/receive symbol latency 10 ms
...
Seems that it can solve the issue: 2021-11-26 16:18:15.140 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/up time', ... (6 bytes)) 2021-11-26 16:18:20.769 [main debug] performing regular tasks 2021-11-26 16:18:30.770 [main debug] performing regular tasks 2021-11-26 16:18:31.156 [mqtt debug] publish ebusd/global/uptime 152586 2021-11-26 16:18:31.156 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9850, 'ebusd/global/ uptime', ... (6 bytes)) 2021-11-26 16:18:31.156 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/up time', ... (6 bytes)) 2021-11-26 16:18:40.770 [main debug] performing regular tasks 2021-11-26 16:18:43.101 [bus debug] ERR: read timeout during skip, switching to no signal 2021-11-26 16:18:43.101 [bus error] signal lost 2021-11-26 16:18:43.251 [bus debug] ERR: SYN received during no signal, switching to ready 2021-11-26 16:18:43.251 [bus notice] signal acquired 2021-11-26 16:18:43.256 [bus error] device status: unexpected available enhanced byte 2 2021-11-26 16:18:47.171 [mqtt debug] publish ebusd/global/uptime 152602 2021-11-26 16:18:47.171 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9851, 'ebusd/global/ uptime', ... (6 bytes)) 2021-11-26 16:18:47.171 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/up time', ... (6 bytes)) 2021-11-26 16:18:50.771 [main debug] performing regular tasks 2021-11-26 16:19:00.771 [main debug] performing regular tasks 2021-11-26 16:19:03.186 [mqtt debug] publish ebusd/global/uptime 152618 2021-11-26 16:19:03.186 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9852, 'ebusd/global/ uptime', ... (6 bytes)) 2021-11-26 16:19:03.187 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/up time', ... (6 bytes)) 2021-11-26 16:19:10.772 [main debug] performing regular tasks 2021-11-26 16:19:13.078 [bus debug] ERR: read timeout during skip, switching to no signal 2021-11-26 16:19:13.078 [bus error] signal lost 2021-11-26 16:19:13.221 [bus debug] ERR: SYN received during no signal, switching to ready 2021-11-26 16:19:13.221 [bus notice] signal acquired 2021-11-26 16:19:13.227 [bus error] device status: unexpected available enhanced byte 2 2021-11-26 16:19:19.203 [mqtt debug] publish ebusd/global/uptime 152634 2021-11-26 16:19:19.203 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9853, 'ebusd/global/ uptime', ... (6 bytes)) 2021-11-26 16:19:19.203 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:19:20.772 [main debug] performing regular tasks 2021-11-26 16:19:30.772 [main debug] performing regular tasks 2021-11-26 16:19:35.215 [mqtt debug] publish ebusd/global/uptime 152650 2021-11-26 16:19:35.215 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9854, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:19:35.215 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:19:36.068 [bus debug] ERR: read timeout during skip, switching to no signal 2021-11-26 16:19:36.068 [bus error] signal lost 2021-11-26 16:19:40.773 [main debug] performing regular tasks
2021-11-26 16:19:41.288 [bus error] arbitration start error
2021-11-26 16:19:41.288 [bus notice] device invalid 2021-11-26 16:19:46.322 [bus notice] device status: resetting 2021-11-26 16:19:46.322 [bus notice] re-opened 192.168.x.y:9999 2021-11-26 16:19:46.325 [bus debug] ERR: SYN received during no signal, switching to ready 2021-11-26 16:19:46.325 [bus notice] signal acquired 2021-11-26 16:19:46.325 [bus info] poll cmd: 3108b509030d2800 2021-11-26 16:19:46.325 [bus debug] start request 31 2021-11-26 16:19:46.325 [bus debug] arbitration start with 31 2021-11-26 16:19:46.373 [bus debug] arbitration won 2021-11-26 16:19:46.373 [bus debug] arbitration delay 3 micros 2021-11-26 16:19:46.373 [bus info] arbitration delay 3 - 3 micros 2021-11-26 16:19:46.373 [bus debug] switching from ready to send command 2021-11-26 16:19:46.384 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:19:46.384 [bus info] send/receive symbol latency 10 - 10 ms 2021-11-26 16:19:46.395 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:19:46.405 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:19:46.415 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:19:46.415 [bus info] send/receive symbol latency 9 - 10 ms 2021-11-26 16:19:46.425 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:19:46.442 [bus debug] send/receive symbol latency 17 ms 2021-11-26 16:19:46.442 [bus info] send/receive symbol latency 9 - 17 ms 2021-11-26 16:19:46.453 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:19:46.453 [bus debug] switching from send command to send command CRC 2021-11-26 16:19:46.463 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:19:46.463 [bus debug] switching from send command CRC to receive command ACK 2021-11-26 16:19:46.472 [bus debug] switching from receive command ACK to receive response 2021-11-26 16:19:46.489 [bus debug] switching from receive response to receive response CRC 2021-11-26 16:19:46.494 [bus debug] switching from receive response CRC to send response ACK 2021-11-26 16:19:46.504 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:19:46.504 [update info] sent MS cmd: 3108b509030d2800 / 024b03 2021-11-26 16:19:46.505 [update notice] sent poll-read bai HcHours QQ=31: 843 2021-11-26 16:19:46.505 [bus debug] notify request: done 2021-11-26 16:19:46.505 [bus debug] switching from send response ACK to send SYN 2021-11-26 16:19:46.515 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:19:46.558 [bus notice] device status: reset 2021-11-26 16:19:49.288 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-11-26 16:19:50.773 [main debug] performing regular tasks 2021-11-26 16:19:51.231 [mqtt debug] publish ebusd/global/uptime 152666 2021-11-26 16:19:51.231 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9855, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:19:51.231 [mqtt debug] publish ebusd/bai/HcHours 843 2021-11-26 16:19:51.231 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9856, 'ebusd/bai/HcHours', ... (3 bytes)) 2021-11-26 16:19:51.231 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:19:51.231 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HcHours', ... (3 bytes)) 2021-11-26 16:19:54.718 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-11-26 16:19:57.032 [bus info] poll cmd: 3108b509030d2200 2021-11-26 16:19:57.033 [bus debug] start request 31 2021-11-26 16:19:57.035 [bus debug] arbitration start with 31 2021-11-26 16:19:57.088 [bus debug] arbitration won 2021-11-26 16:19:57.088 [bus debug] arbitration delay 3 micros 2021-11-26 16:19:57.088 [bus debug] switching from ready to send command 2021-11-26 16:19:57.099 [bus debug] send/receive symbol latency 11 ms 2021-11-26 16:19:57.110 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:19:57.120 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:19:57.130 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:19:57.140 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:19:57.150 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:19:57.159 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:19:57.159 [bus debug] switching from send command to send command CRC 2021-11-26 16:19:57.170 [bus debug] send/receive symbol latency 11 ms 2021-11-26 16:19:57.171 [bus debug] switching from send command CRC to receive command ACK 2021-11-26 16:19:57.186 [bus debug] switching from receive command ACK to receive response 2021-11-26 16:19:57.196 [bus debug] switching from receive response to receive response CRC 2021-11-26 16:19:57.200 [bus debug] switching from receive response CRC to send response ACK 2021-11-26 16:19:57.210 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:19:57.210 [update info] sent MS cmd: 3108b509030d2200 / 029301 2021-11-26 16:19:57.211 [update notice] sent poll-read bai HwcHours QQ=31: 403 2021-11-26 16:19:57.211 [bus debug] notify request: done 2021-11-26 16:19:57.211 [bus debug] switching from send response ACK to send SYN 2021-11-26 16:19:57.222 [bus debug] send/receive symbol latency 11 ms 2021-11-26 16:20:00.774 [main debug] performing regular tasks 2021-11-26 16:20:01.242 [mqtt debug] publish ebusd/bai/HwcHours 403 2021-11-26 16:20:01.242 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9857, 'ebusd/bai/HwcHours', ... (3 bytes)) 2021-11-26 16:20:01.242 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HwcHours', ... (3 bytes)) 2021-11-26 16:20:07.248 [mqtt debug] publish ebusd/global/uptime 152682 2021-11-26 16:20:07.248 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9858, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:20:07.248 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:20:08.044 [bus info] poll cmd: 3108b509030df203 2021-11-26 16:20:08.044 [bus debug] start request 31 2021-11-26 16:20:08.044 [bus debug] arbitration start with 31 2021-11-26 16:20:08.092 [bus debug] arbitration won 2021-11-26 16:20:08.092 [bus debug] arbitration delay 3 micros 2021-11-26 16:20:08.092 [bus debug] switching from ready to send command 2021-11-26 16:20:08.102 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:08.112 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:08.121 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:08.135 [bus debug] send/receive symbol latency 13 ms 2021-11-26 16:20:08.145 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:08.155 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:20:08.165 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:08.165 [bus debug] switching from send command to send command CRC 2021-11-26 16:20:08.174 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:08.174 [bus debug] switching from send command CRC to receive command ACK 2021-11-26 16:20:08.180 [bus debug] switching from receive command ACK to receive response 2021-11-26 16:20:08.198 [bus debug] switching from receive response to receive response CRC 2021-11-26 16:20:08.203 [bus debug] switching from receive response CRC to send response ACK 2021-11-26 16:20:08.212 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:08.213 [update info] sent MS cmd: 3108b509030df203 / 0101 2021-11-26 16:20:08.213 [update notice] sent poll-read bai HeatingSwitch QQ=31: on 2021-11-26 16:20:08.213 [bus debug] notify request: done 2021-11-26 16:20:08.213 [bus debug] switching from send response ACK to send SYN 2021-11-26 16:20:08.223 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:20:10.775 [main debug] performing regular tasks 2021-11-26 16:20:11.252 [mqtt debug] publish ebusd/bai/HeatingSwitch on 2021-11-26 16:20:11.252 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9859, 'ebusd/bai/HeatingSwitch', ... (2 bytes)) 2021-11-26 16:20:11.253 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/HeatingSwitch', ... (2 bytes)) 2021-11-26 16:20:13.412 [bus error] device status: unexpected available enhanced byte 2 2021-11-26 16:20:19.050 [bus info] poll cmd: 3108b509030dc500 2021-11-26 16:20:19.050 [bus debug] start request 31 2021-11-26 16:20:19.050 [bus debug] arbitration start with 31 2021-11-26 16:20:19.097 [bus debug] arbitration won 2021-11-26 16:20:19.097 [bus debug] arbitration delay 4 micros 2021-11-26 16:20:19.097 [bus info] arbitration delay 3 - 4 micros 2021-11-26 16:20:19.097 [bus debug] switching from ready to send command 2021-11-26 16:20:19.107 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:19.117 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:20:19.127 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:19.136 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:19.146 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:19.156 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:20:19.166 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:19.166 [bus debug] switching from send command to send command CRC 2021-11-26 16:20:19.182 [bus debug] send/receive symbol latency 16 ms 2021-11-26 16:20:19.183 [bus debug] switching from send command CRC to receive command ACK 2021-11-26 16:20:19.183 [bus debug] switching from receive command ACK to receive response 2021-11-26 16:20:19.210 [bus debug] switching from receive response to receive response CRC 2021-11-26 16:20:19.215 [bus debug] switching from receive response CRC to send response ACK 2021-11-26 16:20:19.225 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:19.225 [update info] sent MS cmd: 3108b509030dc500 / 04c35ed313 2021-11-26 16:20:19.225 [update notice] sent poll-read bai PrEnergySumHwc1 QQ=31: 332619459 2021-11-26 16:20:19.225 [bus debug] notify request: done 2021-11-26 16:20:19.225 [bus debug] switching from send response ACK to send SYN 2021-11-26 16:20:19.238 [bus debug] send/receive symbol latency 12 ms 2021-11-26 16:20:20.775 [main debug] performing regular tasks 2021-11-26 16:20:21.263 [mqtt debug] publish ebusd/bai/PrEnergySumHwc1 332619459 2021-11-26 16:20:21.263 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9860, 'ebusd/bai/PrEnergySumHwc1', ... (9 bytes)) 2021-11-26 16:20:21.263 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergySumHwc1', ... (9 bytes)) 2021-11-26 16:20:23.265 [mqtt debug] publish ebusd/global/uptime 152698 2021-11-26 16:20:23.265 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9861, 'ebusd/global/ uptime', ... (6 bytes)) 2021-11-26 16:20:23.266 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:20:30.016 [bus info] poll cmd: 3108b509030dc600 2021-11-26 16:20:30.016 [bus debug] start request 31 2021-11-26 16:20:30.016 [bus debug] arbitration start with 31 2021-11-26 16:20:30.064 [bus debug] arbitration won 2021-11-26 16:20:30.064 [bus debug] arbitration delay 3 micros 2021-11-26 16:20:30.064 [bus debug] switching from ready to send command 2021-11-26 16:20:30.074 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:30.084 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:20:30.094 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:30.103 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:30.113 [bus debug] send/receive symbol latency 9 ms 2021-11-26 16:20:30.123 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:20:30.140 [bus debug] send/receive symbol latency 17 ms 2021-11-26 16:20:30.140 [bus debug] switching from send command to send command CRC 2021-11-26 16:20:30.151 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:20:30.151 [bus debug] switching from send command CRC to receive command ACK 2021-11-26 16:20:30.155 [bus debug] switching from receive command ACK to receive response 2021-11-26 16:20:30.186 [bus debug] switching from receive response to receive response CRC 2021-11-26 16:20:30.192 [bus debug] switching from receive response CRC to send response ACK 2021-11-26 16:20:30.204 [bus debug] send/receive symbol latency 12 ms 2021-11-26 16:20:30.204 [update info] sent MS cmd: 3108b509030dc600 / 0480b01600 2021-11-26 16:20:30.205 [update notice] sent poll-read bai PrEnergyCountHwc1 QQ=31: 1486976 2021-11-26 16:20:30.205 [bus debug] notify request: done 2021-11-26 16:20:30.205 [bus debug] switching from send response ACK to send SYN 2021-11-26 16:20:30.215 [bus debug] send/receive symbol latency 10 ms 2021-11-26 16:20:30.775 [main debug] performing regular tasks 2021-11-26 16:20:36.279 [mqtt debug] publish ebusd/bai/PrEnergyCountHwc1 1486976 2021-11-26 16:20:36.279 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9862, 'ebusd/bai/PrEnergyCountHwc1', ... (7 bytes)) 2021-11-26 16:20:36.279 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/PrEnergyCountHwc1', ... (7 bytes)) 2021-11-26 16:20:39.281 [mqtt debug] publish ebusd/global/uptime 152714 2021-11-26 16:20:39.281 [mqtt debug] log Client ebusd_21.3_58 sending PUBLISH (d0, q0, r0, m9863, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:20:39.281 [mqtt debug] log Client ebusd_21.3_58 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-11-26 16:20:40.776 [main debug] performing regular tasks 2021-11-26 16:20:41.037 [bus info] poll cmd: 3108b509030df600
24hrs with new ESP and PIC SW. I'm still receiving EBUS statistics, but ebusd.log contains a lot of error messages. Fortunately seems that EBUS controller or ebusd are able to recover after upgrade. Can I somehow prevent these errors?
cat /var/log/ebusd.log | grep -i err 2021-12-01 19:51:10.188 [bus error] poll bai StorageTemp failed: ERR: read timeout 2021-12-01 19:51:10.188 [bus debug] ERR: read timeout during send command, switching to skip 2021-12-01 19:51:10.290 [bus debug] ERR: SYN received during receive command, switching to ready 2021-12-01 19:51:25.652 [bus error] device status: unexpected available enhanced byte 2 2021-12-01 19:52:25.675 [bus error] device status: unexpected available enhanced byte 2 2021-12-01 19:52:55.981 [bus error] device status: unexpected available enhanced byte 2 2021-12-01 19:53:11.212 [bus debug] notify request: ERR: read timeout 2021-12-01 19:53:11.212 [bus error] poll bai FanSpeed failed: ERR: read timeout 2021-12-01 19:53:11.212 [bus debug] ERR: read timeout during send command, switching to skip 2021-12-01 19:53:11.235 [bus debug] ERR: SYN received during receive command, switching to ready 2021-12-01 19:53:55.905 [bus error] device status: unexpected available enhanced byte 2 2021-12-01 19:54:12.496 [bus error] device status: unexpected available enhanced byte 2 2021-12-01 19:54:26.087 [bus debug] ERR: read timeout during skip, switching to no signal 2021-12-01 19:54:26.087 [bus error] signal lost 2021-12-01 19:54:26.138 [bus debug] ERR: SYN received during no signal, switching to ready 2021-12-01 19:54:26.142 [bus error] device status: unexpected available enhanced byte 2 2021-12-01 19:55:14.737 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-12-01 19:55:20.125 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-12-01 19:55:26.028 [bus debug] ERR: SYN received during receive command ACK, switching to ready 2021-12-01 19:55:30.959 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-12-01 19:55:56.083 [bus debug] ERR: read timeout during skip, switching to no signal 2021-12-01 19:55:56.083 [bus error] signal lost 2021-12-01 19:55:56.282 [bus debug] ERR: SYN received during no signal, switching to ready 2021-12-01 19:55:56.285 [bus error] device status: unexpected available enhanced byte 2 2021-12-01 19:56:26.071 [bus debug] ERR: read timeout during skip, switching to no signal 2021-12-01 19:56:26.071 [bus error] signal lost 2021-12-01 19:56:26.134 [bus debug] ERR: SYN received during no signal, switching to ready 2021-12-01 19:56:29.175 [bus debug] notify request: ERR: read timeout 2021-12-01 19:56:29.175 [bus error] poll bai Flame failed: ERR: read timeout 2021-12-01 19:56:29.175 [bus debug] ERR: read timeout during send command, switching to skip 2021-12-01 19:56:56.385 [bus error] device status: unexpected available enhanced following byte 1 2021-12-01 19:57:26.589 [bus error] device status: unexpected available enhanced byte 2 2021-12-01 19:57:46.126 [bus error] device status: eBUS comm error: framing 2021-12-01 19:57:46.126 [bus debug] notify request: ERR: read timeout 2021-12-01 19:57:46.127 [bus error] poll bai FlowTemp failed: ERR: read timeout 2021-12-01 19:57:46.127 [bus debug] ERR: read timeout during send command, switching to skip 2021-12-01 19:57:57.242 [bus debug] notify request: ERR: read timeout 2021-12-01 19:57:57.242 [bus error] poll bai FanSpeed failed: ERR: read timeout 2021-12-01 19:57:57.242 [bus debug] ERR: read timeout during send command, switching to skip
Unfortunately, it failed today:
2021-12-08 07:05:59.144 [bus debug] send/receive symbol latency 9 ms 2021-12-08 07:05:59.144 [bus debug] switching from send command CRC to receive command ACK 2021-12-08 07:05:59.150 [bus debug] switching from receive command ACK to receive response 2021-12-08 07:05:59.176 [bus debug] switching from receive response to receive response CRC 2021-12-08 07:05:59.181 [bus debug] switching from receive response CRC to send response ACK 2021-12-08 07:05:59.194 [bus debug] send/receive symbol latency 12 ms 2021-12-08 07:05:59.194 [update info] sent MS cmd: 3108b509030d1800 / 03660300 2021-12-08 07:05:59.194 [update notice] sent poll-read bai FlowTemp QQ=31: 54.38;ok 2021-12-08 07:05:59.194 [bus debug] notify request: done 2021-12-08 07:05:59.194 [bus debug] switching from send response ACK to send SYN 2021-12-08 07:05:59.208 [bus debug] send/receive symbol latency 13 ms 2021-12-08 07:06:00.056 [main debug] performing regular tasks 2021-12-08 07:06:00.767 [mqtt debug] publish ebusd/bai/FlowTemp 54.38;ok 2021-12-08 07:06:00.767 [mqtt debug] log Client ebusd_21.3_1154 sending PUBLISH (d0, q0, r0, m37296, 'ebusd/bai/FlowTemp', ... (8 bytes)) 2021-12-08 07:06:00.767 [mqtt debug] log Client ebusd_21.3_1154 received PUBLISH (d0, q0, r0, m0, 'ebusd/bai/FlowTemp', ... (8 bytes)) 2021-12-08 07:06:01.768 [mqtt debug] publish ebusd/global/uptime 252546 2021-12-08 07:06:01.768 [mqtt debug] log Client ebusd_21.3_1154 sending PUBLISH (d0, q0, r0, m37297, 'ebusd/global/uptime', ... (6 bytes)) 2021-12-08 07:06:01.769 [mqtt debug] log Client ebusd_21.3_1154 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-12-08 07:06:10.038 [bus info] poll cmd: 3108b509030d8300 2021-12-08 07:06:10.038 [bus debug] start request 31 2021-12-08 07:06:10.038 [bus debug] arbitration start with 31 2021-12-08 07:06:10.056 [main debug] performing regular tasks 2021-12-08 07:06:11.041 [bus error] poll bai FanSpeed failed: ERR: no signal 2021-12-08 07:06:11.041 [bus debug] ERR: read timeout during skip, switching to no signal 2021-12-08 07:06:11.041 [bus error] signal lost 2021-12-08 07:06:11.279 [bus debug] ERR: SYN received during no signal, switching to ready 2021-12-08 07:06:11.279 [bus notice] signal acquired 2021-12-08 07:06:11.283 [bus error] device status: unexpected available enhanced byte 2 2021-12-08 07:06:17.785 [mqtt debug] publish ebusd/global/uptime 252562 2021-12-08 07:06:17.785 [mqtt debug] log Client ebusd_21.3_1154 sending PUBLISH (d0, q0, r0, m37298, 'ebusd/global/uptime', ... (6 bytes)) 2021-12-08 07:06:17.785 [mqtt debug] log Client ebusd_21.3_1154 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes)) 2021-12-08 07:06:20.057 [main debug] performing regular tasks 2021-12-08 07:06:21.180 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-12-08 07:06:26.567 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-12-08 07:06:30.057 [main debug] performing regular tasks 2021-12-08 07:06:31.954 [bus debug] ERR: read timeout during receive command ACK, switching to skip 2021-12-08 07:06:33.800 [mqtt debug] publish ebusd/global/uptime 252578 2021-12-08 07:06:33.800 [mqtt debug] log Client ebusd_21.3_1154 sending PUBLISH (d0, q0, r0, m37299, 'ebusd/global/uptime', ... (6 bytes)) 2021-12-08 07:06:33.800 [mqtt debug] log Client ebusd_21.3_1154 received PUBLISH (d0, q0, r0, m0, 'ebusd/global/uptime', ... (6 bytes))
Build: 20211205 ebusd device string: enh:192.168.2.5:9999 WiFi signal: 76% (-62dBm) OTA enabled: waiting
ebus firmware : Chip ID: 00e45c62 Hostname: ebus Up time: 230094 Free heap: 29024 ebusd connected: yes (inactive) eBUS signal: acquired eBUS initial signal: yes
M.
Restart of ebusd does not help.
Ebus status shows after restart: Chip ID: 00e45c62 Hostname: ebus Up time: 234042 Free heap: 28728 ebusd connected: no eBUS signal: no signal eBUS initial signal: yes
soft reset of the esp module nor ebusd reset does not help. ESP hw reset didn't help as well. Ebus module needed reset (power cycle). Seems like ebus module looses ebus connectivity.
how does your last post correlate with the one before? in the one before the esp status says signal: acquired and in the second it doesn't