Closed itProfi closed 4 months ago
as the PB byte seems to be b5 (=Vaillant), you could just try one of the 08.*.csvs. what is the scan result? depending on the adapter used, you might have to add "--latency=50" or so to the ebusd start params
I decide back to my boiler ) Same problem:
2023-08-26 18:13:02.042 [main notice] ebusd 23.2.23.2 started with single scan on device: /dev/ttyUSB1
2023-08-26 18:13:02.043 [main info] loading configuration files from /etc/ebusd/
2023-08-26 18:13:02.043 [main debug] reading directory /etc/ebusd/
2023-08-26 18:13:02.043 [main debug] file type of /etc/ebusd/mqtt-integration.cfg is file
2023-08-26 18:13:02.043 [main debug] file type of /etc/ebusd/memory.csv is file
2023-08-26 18:13:02.044 [main debug] file type of /etc/ebusd/_templates.csv is file
2023-08-26 18:13:02.044 [main debug] file type of /etc/ebusd/vaillant is dir
2023-08-26 18:13:02.044 [main debug] file type of /etc/ebusd/broadcast.csv is file
2023-08-26 18:13:02.044 [main info] reading templates /
2023-08-26 18:13:02.049 [main info] read templates in /
2023-08-26 18:13:02.049 [main info] reading file memory.csv
2023-08-26 18:13:02.052 [main info] successfully read file memory.csv
2023-08-26 18:13:02.052 [main info] reading file broadcast.csv
2023-08-26 18:13:02.056 [main info] successfully read file broadcast.csv
2023-08-26 18:13:02.056 [main info] read config files, got 11 messages
2023-08-26 18:13:02.077 [bus notice] bus started with own address 31/36
2023-08-26 18:13:02.077 [main info] registering data handlers
2023-08-26 18:13:02.077 [main info] registered data handlers
2023-08-26 18:13:02.109 [bus debug] ERR: SYN received during no signal, switching to ready
2023-08-26 18:13:02.109 [bus notice] signal acquired
2023-08-26 18:13:05.673 [bus notice] new master 10, master count 2
2023-08-26 18:13:05.735 [bus notice] new master 03, master count 3
2023-08-26 18:13:05.735 [update info] received MS cmd: 1008b5110101 / 093c3c0080ffff0000ff
2023-08-26 18:13:05.735 [update notice] received unknown MS cmd: 1008b5110101 / 093c3c0080ffff0000ff
2023-08-26 18:13:07.700 [update info] received BC cmd: 10feb5160800ffffffffffffff
2023-08-26 18:13:07.700 [update notice] received unknown BC cmd: 10feb5160800ffffffffffffff
2023-08-26 18:13:10.817 [update info] received MS cmd: 1008b510090000144cffff05ff00 / 0101
2023-08-26 18:13:10.817 [update notice] received unknown MS cmd: 1008b510090000144cffff05ff00 / 0101
2023-08-26 18:13:12.078 [main debug] performing regular tasks
2023-08-26 18:13:12.078 [main notice] starting initial scan for 08
2023-08-26 18:13:12.079 [bus info] scan 08 cmd: 3108070400
2023-08-26 18:13:12.114 [bus debug] start request 31
2023-08-26 18:13:12.114 [bus debug] arbitration start with 31
2023-08-26 18:13:12.200 [bus debug] arbitration lost
2023-08-26 18:13:12.200 [bus debug] ERR: arbitration lost during ready, retry
2023-08-26 18:13:12.200 [bus debug] start request 31
2023-08-26 18:13:12.200 [bus debug] arbitration start with 31
2023-08-26 18:13:12.286 [bus debug] arbitration lost
2023-08-26 18:13:12.286 [bus debug] ERR: arbitration lost during ready, retry
2023-08-26 18:13:12.286 [bus debug] start request 31
2023-08-26 18:13:12.286 [bus debug] arbitration start with 31
2023-08-26 18:13:12.372 [bus debug] arbitration lost
2023-08-26 18:13:12.372 [bus debug] ERR: arbitration lost during ready, retry
2023-08-26 18:13:12.372 [bus debug] start request 31
2023-08-26 18:13:12.372 [bus debug] arbitration start with 31
2023-08-26 18:13:12.458 [bus debug] arbitration lost
2023-08-26 18:13:12.458 [bus debug] notify request: ERR: arbitration lost
2023-08-26 18:13:12.458 [main error] initial scan failed: ERR: arbitration lost
2023-08-26 18:13:15.818 [update info] received MS cmd: 1008b5110101 / 093c3c0080ffff0000ff
2023-08-26 18:13:15.818 [update notice] received unknown MS cmd: 1008b5110101 / 093c3c0080ffff0000ff
2023-08-26 18:13:17.817 [update info] received MS cmd: 1008b5040100 / 0a00ffffffffffffff0080
2023-08-26 18:13:17.817 [update notice] received unknown MS cmd: 1008b5040100 / 0a00ffffffffffffff0080
2023-08-26 18:13:18.070 [update info] received MS cmd: 1008b5110102 / 05004c964c78
2023-08-26 18:13:18.070 [update notice] received unknown MS cmd: 1008b5110102 / 05004c964c78
2023-08-26 18:13:20.801 [update info] received MS cmd: 1008b510090000144cffff05ff00 / 0101
2023-08-26 18:13:20.801 [update notice] received unknown MS cmd: 1008b510090000144cffff05ff00 / 0101
2023-08-26 18:13:22.459 [main debug] performing regular tasks
2023-08-26 18:13:22.459 [main notice] starting initial scan for 08
2023-08-26 18:13:22.459 [bus info] scan 08 cmd: 3108070400
2023-08-26 18:13:22.486 [bus debug] start request 31
2023-08-26 18:13:22.486 [bus debug] arbitration start with 31
2023-08-26 18:13:22.574 [bus debug] arbitration lost
2023-08-26 18:13:22.574 [bus debug] ERR: arbitration lost during ready, retry
2023-08-26 18:13:22.574 [bus debug] start request 31
2023-08-26 18:13:22.574 [bus debug] arbitration start with 31
2023-08-26 18:13:22.660 [bus debug] arbitration lost
2023-08-26 18:13:22.660 [bus debug] ERR: arbitration lost during ready, retry
2023-08-26 18:13:22.660 [bus debug] start request 31
2023-08-26 18:13:22.660 [bus debug] arbitration start with 31
2023-08-26 18:13:22.745 [bus debug] arbitration lost
2023-08-26 18:13:22.745 [bus debug] ERR: arbitration lost during ready, retry
2023-08-26 18:13:22.745 [bus debug] start request 31
2023-08-26 18:13:22.745 [bus debug] arbitration start with 31
2023-08-26 18:13:22.831 [bus debug] arbitration lost
2023-08-26 18:13:22.831 [bus debug] notify request: ERR: arbitration lost
2023-08-26 18:13:22.831 [main error] initial scan failed: ERR: arbitration lost
2023-08-26 18:13:25.007 [network info] [00001] client connection opened 127.0.0.1
2023-08-26 18:13:25.008 [network debug] [00001] wait for result
2023-08-26 18:13:25.008 [main debug] >>> i
2023-08-26 18:13:25.008 [main debug] <<< version: ebusd 23.2.23.2
device: /dev/ttyUSB1
signal: acquired
symbol rate: 24
max symbol rate: 44
r ...
I have Protherm 23MOV https://fixbroken.ru/oshibka-f20-na-kotle-proterm-gepard/
https://teplopoint.ru/kotly/kotel-protherm-gepard-23-mov with EBUS support
Also, I have Thermolink P thermostat - https://tdkomfort.ru/shop/komnatnyi-regulyator-protherm-thermolink-p-4529.html I connect to EBUS via Orange PI Zero board extender - https://www.ebay.com/itm/274313895394?hash=item3fde61dde2:g:zF4AAOSwlBtedkgT ebusd version 21.2 When I connect ,I see:
How I can support my Protherm?