Issues with Vaillant sensoCOMFORT VRC 720F (ESERA ECO 305 GATEWAY)

[simonsays42]

Description

Hi there,

I'm desperately trying to get my Vaillant sensoCOMFORT VRC 720F recognized but I guess it's just unsupported?! Thank to everyone involved and keep up the good work!

Boiler: Vaillant turboTEC plus VCW DE 195/4-5 R1 (WORKING) (address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0518;HW=7401", loaded "vaillant/bai.308523.inc" ([HW=7401]), "vaillant/08.bai.csv")
Control board: Vaillant VBC 02.2.2
Heating Control: Vaillant sensoCOMFORT VRC 720F (Basestation P) (NOT WORKING) (address 15: slave #2)
Should be something like: address 15: slave #2, scanned "MF=Vaillant;ID=72000;SW=0118;HW=7703" loading 15.700.csv (*)
EBUS-Gateway: ESERA ECO 305 (supports ebusd enhanced protocol)

(*): I created a symlink from 15.700.csv to 15.ctlv2.csv and 15.basv0..csv.

ebusd version: 23.2.p20231204
ebusd cmd: ebusd -f --loglevel=debug --scanconfig=full -d enh:10.0.1.4:5001 (i've basically worked out any command line switches with absolutely no success so far)

Output:
[...]
2023-12-17 19:30:31.226 [update info] received MS cmd: 1008b5110101 / 0954540080ff560000ff
2023-12-17 19:30:31.226 [update notice] received unknown MS cmd: 1008b5110101 / 0954540080ff560000ff
2023-12-17 19:30:31.509 [update info] received MS cmd: 1008b5100900005a78ffff000000 / 0101
2023-12-17 19:30:31.509 [update notice] received unknown MS cmd: 1008b5100900005a78ffff000000 / 0101
2023-12-17 19:30:31.754 [update info] received BC cmd: 10feb516080032301917120723
2023-12-17 19:30:31.755 [update notice] received unknown BC cmd: 10feb516080032301917120723
2023-12-17 19:30:32.018 [update info] received MS cmd: 1008b5110102 / 05033c964682
2023-12-17 19:30:32.019 [update notice] received unknown MS cmd: 1008b5110102 / 05033c964682
2023-12-17 19:30:32.302 [update info] received MS cmd: 1008b5110100 / 08a80210001438009b
2023-12-17 19:30:32.302 [update notice] received unknown MS cmd: 1008b5110100 / 08a80210001438009b
2023-12-17 19:30:32.521 [update info] received BC cmd: 10feb5160301ab08
2023-12-17 19:30:32.521 [update notice] received unknown BC cmd: 10feb5160301ab08
2023-12-17 19:30:37.291 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-17 19:30:38.845 [main debug] performing regular tasks
2023-12-17 19:30:38.846 [bus info] scan 08 cmd: 3108070400
2023-12-17 19:30:38.886 [bus debug] start request 31
2023-12-17 19:30:38.886 [bus debug] arbitration start with 31
2023-12-17 19:30:38.937 [bus debug] arbitration won
2023-12-17 19:30:38.937 [bus debug] arbitration delay 5 micros
2023-12-17 19:30:38.937 [bus debug] switching from ready to send command
2023-12-17 19:30:38.964 [bus debug] send/receive symbol latency 26 ms
2023-12-17 19:30:38.979 [bus debug] notify request: ERR: SYN received
2023-12-17 19:30:38.979 [bus debug] ERR: SYN received during send command, switching to ready
2023-12-17 19:30:38.979 [main error] scan config 08: ERR: SYN received
2023-12-17 19:30:39.026 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-17 19:30:39.590 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-17 19:30:40.982 [main debug] performing regular tasks
2023-12-17 19:30:40.982 [bus info] scan 15 cmd: 3115070400
2023-12-17 19:30:41.010 [bus debug] start request 31
2023-12-17 19:30:41.010 [bus debug] arbitration start with 31
2023-12-17 19:30:41.063 [bus debug] arbitration won
2023-12-17 19:30:41.063 [bus debug] arbitration delay 4 micros
2023-12-17 19:30:41.063 [bus debug] switching from ready to send command
2023-12-17 19:30:41.091 [bus debug] send/receive symbol latency 27 ms
2023-12-17 19:30:41.103 [bus debug] notify request: ERR: SYN received
2023-12-17 19:30:41.103 [bus debug] ERR: SYN received during send command, switching to ready
2023-12-17 19:30:41.103 [main error] scan config 15: ERR: SYN received
2023-12-17 19:30:41.147 [bus debug] ERR: SYN received during receive command, switching to ready
2023-12-17 19:30:41.332 [update info] received MS cmd: 1008b5110101 / 0956540080ff562000ff
2023-12-17 19:30:41.332 [update notice] received unknown MS cmd: 1008b5110101 / 0956540080ff562000ff
2023-12-17 19:30:41.691 [bus debug] ERR: read timeout during receive response, switching to skip
2023-12-17 19:30:42.211 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2023-12-17 19:30:42.914 [update info] received MS cmd: 1008b5100900005a78ffff000000 / 0101
2023-12-17 19:30:42.914 [update notice] received unknown MS cmd: 1008b5100900005a78ffff000000 / 0101
[...]

ebusctl: find -V
broadcast datetime = no data stored [ZZ=fe, passive read]
broadcast error = no data stored [ZZ=fe, passive read]
broadcast id = no data stored [ZZ=fe, passive read]
broadcast id = no data stored [ZZ=any, active read]
broadcast signoflife = no data stored [ZZ=fe, passive read]
memory eeprom = no data stored [ZZ=any, active read]
memory ram = no data stored [ZZ=any, active read]
scan.08 = no data stored [ZZ=08, active read]
scan.15 = no data stored [ZZ=15, active read]

ebusctl: info verbose
version: ebusd 23.2.p20231204
device: 10.0.1.4:5001, enhanced
signal: acquired
symbol rate: 18
max symbol rate: 76
min arbitration micros: 1
max arbitration micros: 649
min symbol latency: 22
max symbol latency: 41
scan: finished, some messages pending
reconnects: 0
masters: 3
messages: 13
conditional: 0
poll: 0
update: 4
address 03: master #11
address 08: slave #11, scanning
address 10: master #2
address 15: slave #2, scanning
address 31: master #8, ebusd
address 36: slave #8, ebusd, scanning

Thank you very much.

[john30]

wrong repo, check ebusd-configuration instead