john30 / ebusd-esp32

Firmware for ESP32-C3 allowing eBUS communication for ebusd (https://github.com/john30/ebusd)
https://adapter.ebusd.eu/v5
24 stars 1 forks source link

First run #48

Closed sfoglia closed 7 months ago

sfoglia commented 7 months ago

Hi, I've just unpacked the new adapter v5 hardware v.1.24, started a docker container but something goes wrong:

$ docker run --rm -it -p 8888 john30/ebusd --scanconfig -d ens:10.1.1.33:9999 --latency=20 2024-02-16 07:36:22.166 [bus notice] device status: transport opened 2024-02-16 07:36:22.166 [main notice] ebusd 23.3.23.3 started with broadcast scan on device: 10.1.1.33:9999, TCP, enhanced 2024-02-16 07:36:29.019 [network error] HTTP recv: timed out after 1 sec 2024-02-16 07:36:29.019 [main error] HTTP failure: receive error (headers) 2024-02-16 07:36:29.019 [main error] error reading config files from https://cfg.ebusd.eu/: ERR: element not found, last error: 2024-02-16 07:36:29.019 [bus notice] bus started with own address 31/36 2024-02-16 07:36:31.385 [bus error] device status: transport closed 2024-02-16 07:36:31.385 [bus notice] device invalid 2024-02-16 07:36:36.417 [bus notice] device status: transport opened 2024-02-16 07:36:36.417 [bus notice] re-opened 10.1.1.33:9999 2024-02-16 07:36:36.692 [bus notice] device status: reset, supports info 2024-02-16 07:36:36.804 [bus notice] device status: extra info: firmware 1.1[4106].1[4106], jumpers 0x0f 2024-02-16 07:37:01.013 [bus error] device status: transport closed 2024-02-16 07:37:01.013 [bus notice] device invalid 2024-02-16 07:37:06.052 [bus notice] device status: transport opened 2024-02-16 07:37:06.052 [bus notice] re-opened 10.1.1.33:9999 2024-02-16 07:37:06.696 [bus notice] device status: reset, supports info 2024-02-16 07:37:06.801 [bus notice] device status: extra info: firmware 1.1[4106].1[4106], jumpers 0x0f 2024-02-16 07:37:49.941 [bus error] device status: transport closed 2024-02-16 07:37:49.941 [bus notice] device invalid 2024-02-16 07:37:55.861 [bus error] device status: transport closed 2024-02-16 07:37:55.861 [bus notice] re-opened 10.1.1.33:9999 2024-02-16 07:37:55.861 [bus notice] device invalid 2024-02-16 07:38:00.862 [bus error] device status: transport closed 2024-02-16 07:38:00.862 [bus notice] re-opened 10.1.1.33:9999 2024-02-16 07:38:00.862 [bus notice] device invalid

I could reach https://cfg.ebusd.eu/ but seems that the adapter cannot, also firmware update test seems to fail, what can I do now? Thanks, BR

sfoglia commented 7 months ago

So it seems that was an internet issue?

Now it seems that I'm ready:

docker run --rm -it -p 8888 john30/ebusd --scanconfig -d ens:10.1.1.33:9999 --latency=20 --lograwdata=bytes --log=all:debug --log=network:info

But got this on the screen:

2024-02-16 09:44:22.164 [main info] configPath URL is valid 2024-02-16 09:44:22.216 [bus notice] device status: transport opened 2024-02-16 09:44:22.217 [main info] registering data handlers 2024-02-16 09:44:22.217 [main info] registered data handlers 2024-02-16 09:44:22.217 [main notice] ebusd 23.3.23.3 started with broadcast scan on device: 10.1.1.33:9999, TCP, enhanced 2024-02-16 09:44:22.217 [main info] loading configuration files from https://cfg.ebusd.eu/ 2024-02-16 09:44:22.430 [main info] reading templates / 2024-02-16 09:44:22.639 [main info] read templates in / 2024-02-16 09:44:22.639 [main info] reading file broadcast.csv 2024-02-16 09:44:22.827 [main info] successfully read file broadcast.csv 2024-02-16 09:44:22.827 [main info] reading file memory.csv 2024-02-16 09:44:23.016 [main info] successfully read file memory.csv 2024-02-16 09:44:23.016 [main info] read config files, got 11 messages 2024-02-16 09:44:23.016 [bus notice] bus started with own address 31/36 2024-02-16 09:44:23.016 [bus notice] <aa 2024-02-16 09:44:23.016 [bus notice] signal acquired 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] device status: reset, supports info 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.017 [bus notice] <aa 2024-02-16 09:44:23.045 [bus notice] <aa 2024-02-16 09:44:23.107 [bus notice] <aa 2024-02-16 09:44:23.162 [bus notice] device status: extra info: firmware 1.1[4106].1[4106], jumpers 0x0f 2024-02-16 09:44:23.162 [bus notice] <aa 2024-02-16 09:44:23.176 [bus notice] <aa 9:44:31.839 [bus notice] <aa 2024-02-16 09:44:31.859 [bus notice] <aa 2024-02-16 09:44:31.924 [bus notice] <aa 2024-02-16 09:44:31.944 [bus notice] <aa 2024-02-16 09:44:32.246 [bus notice] <aa 2024-02-16 09:44:32.246 [bus notice] <aa 2024-02-16 09:44:32.246 [bus notice] <aa 2024-02-16 09:44:32.246 [bus notice] <aa 2024-02-16 09:44:32.246 [bus notice] <aa 2024-02-16 09:44:32.440 [bus notice] <aa 2024-02-16 09:44:32.458 [bus notice] <aa 2024-02-16 09:44:32.572 [bus notice] <aa 2024-02-16 09:44:32.739 [bus notice] <aa 2024-02-16 09:44:32.770 [bus notice] <aa 2024-02-16 09:44:32.776 [bus notice] <aa 2024-02-16 09:44:32.796 [bus notice] <aa 2024-02-16 09:44:32.856 [bus notice] <aa 2024-02-16 09:44:32.863 [bus notice] <aa 2024-02-16 09:44:32.974 [bus notice] <aa 2024-02-16 09:44:32.978 [bus notice] <aa 2024-02-16 09:44:33.017 [main debug] performing regular tasks 2024-02-16 09:44:33.017 [main notice] starting initial broadcast scan 2024-02-16 09:44:33.017 [bus info] send message: 31fe07fe00 2024-02-16 09:44:33.064 [bus notice] <aa 2024-02-16 09:44:33.064 [bus notice] <aa 2024-02-16 09:44:33.064 [bus debug] start request 31 2024-02-16 09:44:33.064 [bus debug] arbitration start with 31 2024-02-16 09:44:33.147 [bus notice] <aa 2024-02-16 09:44:33.212 [bus notice] <aa 2024-02-16 09:44:33.216 [bus notice] <aa 2024-02-16 09:44:33.216 [bus debug] arbitration lost (timed out) 2024-02-16 09:44:33.216 [bus debug] ERR: arbitration lost during ready, retry 2024-02-16 09:44:33.216 [bus debug] start request 31 2024-02-16 09:44:33.216 [bus debug] arbitration start with 31 2024-02-16 09:44:33.221 [bus notice] <aa 2024-02-16 09:44:33.271 [bus notice] <aa 2024-02-16 09:44:33.349 [bus notice] <aa 2024-02-16 09:44:33.349 [bus debug] arbitration lost (timed out) 2024-02-16 09:44:33.349 [bus debug] ERR: arbitration lost during ready, retry 2024-02-16 09:44:33.349 [bus debug] start request 31 2024-02-16 09:44:33.349 [bus debug] arbitration start with 31 2024-02-16 09:44:33.356 [bus notice] <aa 2024-02-16 09:44:33.365 [bus notice] <aa 2024-02-16 09:44:33.365 [bus notice] <aa 2024-02-16 09:44:33.365 [bus debug] arbitration lost (timed out) 2024-02-16 09:44:33.365 [bus debug] ERR: arbitration lost during ready, retry 2024-02-16 09:44:33.365 [bus debug] start request 31 2024-02-16 09:44:33.365 [bus debug] arbitration start with 31 2024-02-16 09:44:33.373 [bus notice] <aa 2024-02-16 09:44:33.373 [bus notice] >31 2024-02-16 09:44:33.373 [bus debug] arbitration won 2024-02-16 09:44:33.373 [bus debug] switching from ready to send command 2024-02-16 09:44:33.373 [bus notice] <aa 2024-02-16 09:44:33.373 [bus debug] notify request: ERR: SYN received 2024-02-16 09:44:33.373 [bus debug] ERR: SYN received during send command, switching to ready 2024-02-16 09:44:33.373 [bus error] send to fe: ERR: SYN received, retry 2024-02-16 09:44:33.378 [bus notice] <aa 2024-02-16 09:44:33.378 [bus debug] start request 31 2024-02-16 09:44:33.378 [bus debug] arbitration start with 31 2024-02-16 09:44:33.432 [bus notice] >31 2024-02-16 09:44:33.432 [bus debug] arbitration won 2024-02-16 09:44:33.432 [bus debug] arbitration delay 140 micros 2024-02-16 09:44:33.432 [bus info] arbitration delay 140 - 140 micros 2024-02-16 09:44:33.432 [bus debug] switching from ready to send command 2024-02-16 09:44:33.432 [bus notice] >fe 2024-02-16 09:44:33.502 [bus debug] notify request: ERR: read timeout 2024-02-16 09:44:33.502 [bus debug] ERR: read timeout during send command, switching to skip 2024-02-16 09:44:33.503 [bus error] send to fe: ERR: read timeout, retry 2024-02-16 09:44:33.614 [bus debug] start request 31 2024-02-16 09:44:33.614 [bus debug] arbitration start with 31 2024-02-16 09:44:33.787 [bus notice] <aa 2024-02-16 09:44:34.090 [bus notice] <aa 2024-02-16 09:44:34.209 [bus notice] <aa 2024-02-16 09:44:34.209 [bus debug] arbitration lost (timed out) 2024-02-16 09:44:34.209 [bus debug] ERR: arbitration lost during skip, retry 2024-02-16 09:44:34.209 [bus notice] >31 2024-02-16 09:44:34.209 [bus debug] arbitration won 2024-02-16 09:44:34.209 [bus debug] switching from ready to send command 2024-02-16 09:44:34.209 [bus notice] >fe 2024-02-16 09:44:34.279 [bus debug] notify request: ERR: read timeout 2024-02-16 09:44:34.279 [bus debug] ERR: read timeout during send command, switching to skip 2024-02-16 09:44:34.280 [bus error] send to fe: ERR: read timeout 2024-02-16 09:44:34.280 [main error] initial scan failed: ERR: read timeout 2024-02-16 09:44:34.339 [bus notice] <aa 4:42.786 [bus notice] <aa 2024-02-16 09:44:42.824 [bus notice] <aa 2024-02-16 09:44:42.872 [bus notice] <aa 2024-02-16 09:44:42.915 [bus notice] <aa 2024-02-16 09:44:43.157 [bus notice] <aa 2024-02-16 09:44:43.162 [bus notice] <aa 2024-02-16 09:44:43.304 [bus notice] <aa 2024-02-16 09:44:43.304 [bus notice] <aa 2024-02-16 09:44:43.304 [bus notice] <aa 2024-02-16 09:44:43.310 [bus notice] <aa 2024-02-16 09:44:43.317 [bus notice] <aa 2024-02-16 09:44:43.324 [bus notice] <aa 2024-02-16 09:44:43.333 [bus notice] <aa 2024-02-16 09:44:43.349 [bus notice] <aa 2024-02-16 09:44:43.397 [bus notice] <aa 2024-02-16 09:44:43.439 [bus notice] <aa 2024-02-16 09:44:43.496 [bus notice] <aa 2024-02-16 09:44:43.526 [bus notice] <aa 2024-02-16 09:44:43.567 [bus notice] <aa 2024-02-16 09:44:43.606 [bus notice] <aa 2024-02-16 09:44:43.664 [bus notice] <aa 2024-02-16 09:44:43.697 [bus notice] <aa 2024-02-16 09:44:43.745 [bus notice] <aa 2024-02-16 09:44:43.800 [bus notice] <aa 2024-02-16 09:44:43.824 [bus notice] <aa 2024-02-16 09:44:43.877 [bus notice] <aa 2024-02-16 09:44:43.915 [bus notice] <aa 2024-02-16 09:44:43.965 [bus notice] <aa 2024-02-16 09:44:44.007 [bus notice] <aa 2024-02-16 09:44:44.046 [bus notice] <aa 2024-02-16 09:44:44.131 [bus notice] <aa 2024-02-16 09:44:44.149 [bus notice] <aa 2024-02-16 09:44:44.175 [bus notice] <aa 2024-02-16 09:44:44.218 [bus notice] <aa 2024-02-16 09:44:44.271 [bus notice] <aa 2024-02-16 09:44:44.280 [main debug] performing regular tasks 2024-02-16 09:44:44.280 [main notice] starting initial broadcast scan 2024-02-16 09:44:44.280 [bus info] send message: 31fe07fe00 2024-02-16 09:44:44.305 [bus notice] <aa 2024-02-16 09:44:44.305 [bus debug] start request 31 2024-02-16 09:44:44.305 [bus debug] arbitration start with 31 2024-02-16 09:44:44.362 [bus notice] <aa 2024-02-16 09:44:44.362 [bus notice] >31 2024-02-16 09:44:44.362 [bus debug] arbitration won 2024-02-16 09:44:44.362 [bus debug] switching from ready to send command 2024-02-16 09:44:44.362 [bus notice] >fe 2024-02-16 09:44:44.384 [bus notice] <fe 2024-02-16 09:44:44.384 [bus debug] send/receive symbol latency 21 ms 2024-02-16 09:44:44.384 [bus info] send/receive symbol latency 21 - 21 ms 2024-02-16 09:44:44.384 [bus notice] >07 2024-02-16 09:44:44.427 [bus notice] <07 2024-02-16 09:44:44.427 [bus debug] send/receive symbol latency 43 ms 2024-02-16 09:44:44.427 [bus info] send/receive symbol latency 21 - 43 ms 2024-02-16 09:44:44.427 [bus notice] >fe 2024-02-16 09:44:44.445 [bus notice] <fe 2024-02-16 09:44:44.445 [bus debug] send/receive symbol latency 18 ms 2024-02-16 09:44:44.445 [bus info] send/receive symbol latency 18 - 43 ms 2024-02-16 09:44:44.445 [bus notice] >00 2024-02-16 09:44:44.466 [bus notice] <00 2024-02-16 09:44:44.466 [bus debug] send/receive symbol latency 20 ms 2024-02-16 09:44:44.466 [bus debug] switching from send command to send command CRC 2024-02-16 09:44:44.466 [bus notice] >35 2024-02-16 09:44:44.483 [bus notice] <35 2024-02-16 09:44:44.483 [bus debug] send/receive symbol latency 17 ms 2024-02-16 09:44:44.483 [bus info] send/receive symbol latency 17 - 43 ms 2024-02-16 09:44:44.483 [update info] sent BC cmd: 31fe07fe00 2024-02-16 09:44:44.483 [update notice] sent write broadcast queryexistence QQ=31: 2024-02-16 09:44:44.483 [bus debug] notify request: done 2024-02-16 09:44:44.483 [bus debug] read res: 2024-02-16 09:44:44.483 [bus debug] switching from send command CRC to send SYN 2024-02-16 09:44:44.484 [bus notice] >aa 2024-02-16 09:44:44.518 [bus notice] <aa 2024-02-16 09:44:44.518 [bus debug] send/receive symbol latency 34 ms 2024-02-16 09:44:44.518 [bus debug] switching from send SYN to ready 2024-02-16 09:44:44.545 [bus notice] <aa 2024-02-16 09:44:44.605 [bus notice] <aa 2024-02-16 09:44:44.637 [bus notice] <aa

I'm a little confused, my boiler is Vaillant but how can I understand wich file from https://upd.ebusd.eu/ is needed ?

sfoglia commented 7 months ago

https://github.com/john30/ebusd/wiki/4.-Configuration