search

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

ebusd does not see the device #65

Closed Andrew55529 closed 6 months ago

Andrew55529 commented 6 months ago

Chip ID: 58cf79f0cfa8, ESP32-C3, rev 3 Hostname: ebus-f0cfa8 PCB: 1.22.1 Build: 20240420 Flash: 4194304 IDF: v5.3-dev-3499-g636ff35b52-dirty Reset reason: 5 eBUS r/w: 22202/0 Host r/w: 0/43552 Up time: 982 Free heap: 113120 / 260628 ebusd connected: yes (inactive) eBUS signal: acquired

I have a protherm ray boiler, but the connection is not working.

2ad9b828-ebusd:/# ebusctl find broadcast datetime = no data stored broadcast error = no data stored broadcast id = no data stored broadcast id = no data stored broadcast signoflife = no data stored memory eeprom = no data stored memory ram = no data stored`

In Home Assistant Add-on: eBUSd:

2024-05-05 00:16:12.623 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:12.667 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:12.710 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:12.753 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:12.796 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:12.839 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:12.883 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:12.927 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:12.970 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.029 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.057 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.113 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.145 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.190 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.233 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.274 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.318 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.362 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.462 [bus debug] ERR: read timeout during receive command, switching to skip 2024-05-05 00:16:13.950 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:13.986 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.030 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.075 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.119 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.220 [bus debug] ERR: read timeout during receive command, switching to skip 2024-05-05 00:16:14.701 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.745 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.789 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.832 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.876 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.920 [bus debug] ERR: SYN received during receive command, switching to ready 2024-05-05 00:16:14.964 [bus debug] ERR: SYN received during receive command, switching to ready

john30 commented 6 months ago

these are debug messages and as such not revealing anything relevant. did you use the right device string to ebusd as shown on the adapter web page?

Andrew55529 commented 6 months ago

Yes. In adapter web page: [ebusd device string]: ens:192.168.9.138:9999 And in HA addon ebusd i write: 192.168.9.138:9999

Andrew55529 commented 6 months ago

I set log level to info and restart addon:

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=ooyai5seeth3phahd8o --scanconfig --mqttjson --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=192.168.9.138:9999 --log=all:info --scanconfig 2024-05-05 22:10:28.739 [main info] configPath URL is valid 2024-05-05 22:10:28.739 [main notice] ebusd 23.2.p20230716 started with auto scan on device: 192.168.9.138:9999 2024-05-05 22:10:28.739 [main info] loading configuration files from https://cfg.ebusd.eu/ 2024-05-05 22:10:29.059 [main info] reading templates / 2024-05-05 22:10:29.387 [main info] read templates in / 2024-05-05 22:10:29.387 [main info] reading file broadcast.csv 2024-05-05 22:10:29.750 [main info] successfully read file broadcast.csv 2024-05-05 22:10:29.750 [main info] reading file memory.csv 2024-05-05 22:10:30.068 [main info] successfully read file memory.csv 2024-05-05 22:10:30.068 [main info] read config files, got 11 messages 2024-05-05 22:10:30.100 [bus notice] bus started with own address 31/36 2024-05-05 22:10:30.100 [main info] registering data handlers 2024-05-05 22:10:30.100 [mqtt info] mosquitto version 2.0.18 (compiled with 2.0.15) 2024-05-05 22:10:30.103 [main info] registered data handlers 2024-05-05 22:10:30.105 [mqtt notice] connection established 2024-05-05 22:10:30.130 [bus notice] signal acquired

john30 commented 6 months ago

according to the ebusd log the device string is not correct (you missed the "ens:" prefix)

Andrew55529 commented 6 months ago

Thank you. My boiler was found

address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0108;HW=7503", loaded "vaillant/bai.0010008045.inc" ([PROD='0010023648']), "vaillant/08.bai.csv"

How can I understand which data is updated automatically and which is not?

in .inc file only type r, not r[1-9]

Andrew55529 commented 6 months ago

And i have some error:

[update info] sent MS cmd: 3108b509030dd500 / 00 [update error] unable to parse poll-read bai VortexFlowSensor from 3108b509030dd500 / 00: ERR: invalid position [mqtt error] decode bai VortexFlowSensor: ERR: invalid position

[update info] sent MS cmd: 3108b509030d2500 / 00 [update error] unable to parse poll-read bai externalFlowTempDesired from 3108b509030d2500 / 00: ERR: invalid position [mqtt error] decode bai externalFlowTempDesired: ERR: invalid position

john30 commented 6 months ago

that depends on the ebusd-configuration files used and what is set to polling in there. additionally messages can be requested for polling via mqtt and so does the mqtt integration for hassio if configured accordingly. see here: https://github.com/john30/ebusd/wiki/MQTT-integration#home-assistant