recovair 260/4 no communication

[alpxp]

Hi everyone,
Just received "eBUS Adapter v5". Was following the First Steps guide and got stuck in the end where no data from the bus is coming from my Valiant Recovair 260/4. How to diagnose the problem?

The green LED on adapter is permanently on.
My wiring looks like that:

The log looks like that:

2023-05-18 13:12:20.966 [main info] loading configuration files from https://cfg.ebusd.eu/
2023-05-18 13:12:21.245 [main info] reading templates /
2023-05-18 13:12:21.562 [main info] read templates in /
2023-05-18 13:12:21.562 [main info] reading file memory.csv
2023-05-18 13:12:21.859 [main info] successfully read file memory.csv
2023-05-18 13:12:21.859 [main info] reading file broadcast.csv
2023-05-18 13:12:22.176 [main info] successfully read file broadcast.csv
2023-05-18 13:12:22.176 [main info] read config files, got 11 messages
2023-05-18 13:12:22.177 [bus notice] device status: resetting
2023-05-18 13:12:22.177 [bus notice] bus started with own address 31/36
2023-05-18 13:12:22.178 [main info] registering data handlers
2023-05-18 13:12:22.178 [main info] registered data handlers
2023-05-18 13:12:22.195 [bus debug] ERR: SYN received during no signal, switching to ready
2023-05-18 13:12:22.195 [bus notice] signal acquired
2023-05-18 13:12:22.858 [bus notice] device status: reset, supports info
2023-05-18 13:12:22.966 [bus notice] device status: extra info: firmware 1.1[3501].1[3501], jumpers 0x03
2023-05-18 13:12:32.178 [main debug] performing regular tasks
2023-05-18 13:12:42.179 [main debug] performing regular tasks
2023-05-18 13:12:52.179 [main debug] performing regular tasks

alpxp@raspberrypi4:~ $ ebusctl i
version: ebusd 23.1.23.1
update check: OK, device firmware 1[8419] available
device: /dev/ttyACM0, enhanced, firmware 1.1[3501].1[3501]
signal: acquired
symbol rate: 23
max symbol rate: 24
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 31: master #8, ebusd
address 36: slave #8, ebusd

Status:

Chip ID: dc5475930574, [ESP32-C3, rev 4](http://192.168.2.73/#/status?verbose)
Hostname: ebus-930574
Up time: 3210
Free heap: 119556
ebusd connected: yes (inactive)
eBUS signal: acquired

alpxp@raspberrypi4:~ $ 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

alpxp@raspberrypi4:~ $ ebusctl scan result
done

What am I missing? Why no messages on ebus? Does ebus communication need to be turned on on recovair somehow? Or am I not wiring it right?

Thank you

[QubaB]

What is your ebusd configuration in file /etc/default/ebusd ?
EBUSD_OPTS=...

Did you used option --scanconfig=full ?

[alpxp]

Hi.
The trick was to use the option --loglevel=debug. I don't understand why it only works in debug mode. But it quite certainly only detects my Racovair when I use --loglevel=debug.

Here is what happens without the debug:

alpxp@raspberrypi4:~ $ sudo ebusd -f -d ens:/dev/ttyACM0 --scanconfig=08 -c /home/alpxp/confs
2023-05-24 20:48:43.703 [main notice] ebusd 23.1.23.1 started with single scan on enhanced device /dev/ttyACM0
2023-05-24 20:48:43.710 [bus notice] device status: resetting
2023-05-24 20:48:43.711 [bus notice] bus started with own address 31/36
2023-05-24 20:48:43.746 [bus notice] signal acquired
2023-05-24 20:48:44.667 [bus notice] device status: reset, supports info
2023-05-24 20:48:44.775 [bus notice] device status: extra info: firmware 1.1[3501].1[3501], jumpers 0x03
2023-05-24 20:48:53.711 [main notice] starting initial scan for 08
2023-05-24 20:48:53.809 [main error] initial scan failed: ERR: read timeout
2023-05-24 20:48:59.277 [main notice] starting initial scan for 08
2023-05-24 20:48:59.391 [main error] initial scan failed: ERR: read timeout
2023-05-24 20:49:09.391 [main notice] starting initial scan for 08
2023-05-24 20:49:09.499 [main error] initial scan failed: ERR: read timeout

and

alpxp@raspberrypi4:~ $ ebusctl info
version: ebusd 23.1.23.1
device: /dev/ttyACM0, enhanced, firmware 1.1[3501].1[3501]
signal: acquired
symbol rate: 25
max symbol rate: 25
min arbitration micros: 6
max arbitration micros: 6
reconnects: 0
masters: 1
messages: 1
conditional: 0
poll: 0
update: 0
address 31: master #8, ebusd
address 36: slave #8, ebusd

And with the debug:

alpxp@raspberrypi4:~ $ sudo ebusd -f -d ens:/dev/ttyACM0 --loglevel=debug --scanconfig=08 -c /home/alpxp/confs
2023-05-24 20:49:37.775 [main notice] ebusd 23.1.23.1 started with single scan on enhanced device /dev/ttyACM0
2023-05-24 20:49:37.775 [main info] loading configuration files from /home/alpxp/confs/
2023-05-24 20:49:37.775 [main debug] reading directory /home/alpxp/confs/
2023-05-24 20:49:37.775 [main debug] file type of /home/alpxp/confs/vaillant is dir
2023-05-24 20:49:37.775 [main info] read config files, got 0 messages
2023-05-24 20:49:37.781 [bus notice] device status: resetting
2023-05-24 20:49:37.781 [bus notice] bus started with own address 31/36
2023-05-24 20:49:37.782 [main info] registering data handlers
2023-05-24 20:49:37.782 [main info] registered data handlers
2023-05-24 20:49:37.803 [bus debug] ERR: SYN received during no signal, switching to ready
2023-05-24 20:49:37.803 [bus notice] signal acquired
2023-05-24 20:49:38.667 [bus notice] device status: reset, supports info
2023-05-24 20:49:38.790 [bus notice] device status: extra info: firmware 1.1[3501].1[3501], jumpers 0x03
2023-05-24 20:49:47.782 [main debug] performing regular tasks
2023-05-24 20:49:47.782 [main notice] starting initial scan for 08
2023-05-24 20:49:47.782 [bus info] scan 08 cmd: 3108070400
2023-05-24 20:49:47.791 [bus debug] start request 31
2023-05-24 20:49:47.791 [bus debug] arbitration start with 31
2023-05-24 20:49:47.839 [bus debug] arbitration won
2023-05-24 20:49:47.839 [bus debug] arbitration delay 5 micros
2023-05-24 20:49:47.839 [bus info] arbitration delay 5 - 5 micros
2023-05-24 20:49:47.839 [bus debug] switching from ready to send command
2023-05-24 20:49:47.843 [bus debug] send/receive symbol latency 4 ms
2023-05-24 20:49:47.843 [bus info] send/receive symbol latency 4 - 4 ms
2023-05-24 20:49:47.847 [bus debug] send/receive symbol latency 4 ms
2023-05-24 20:49:47.851 [bus debug] send/receive symbol latency 4 ms
2023-05-24 20:49:47.856 [bus debug] send/receive symbol latency 4 ms
2023-05-24 20:49:47.856 [bus debug] switching from send command to send command CRC
2023-05-24 20:49:47.860 [bus debug] send/receive symbol latency 4 ms
2023-05-24 20:49:47.860 [bus debug] switching from send command CRC to receive command ACK
2023-05-24 20:49:47.865 [bus debug] switching from receive command ACK to receive response
2023-05-24 20:49:47.918 [bus debug] switching from receive response to receive response CRC
2023-05-24 20:49:47.922 [bus debug] switching from receive response CRC to send response ACK
2023-05-24 20:49:47.926 [bus debug] send/receive symbol latency 4 ms
2023-05-24 20:49:47.926 [bus notice] new master 03, master count 2
2023-05-24 20:49:47.926 [update info] sent MS cmd: 3108070400 / 0ab57265636f5602290203
2023-05-24 20:49:47.926 [bus notice] scan 08: ;Vaillant;recoV;0229;0203
2023-05-24 20:49:47.926 [update notice] store 08 ident: done
2023-05-24 20:49:47.926 [update notice] sent scan-read scan.08  QQ=31: Vaillant;recoV;0229;0203
2023-05-24 20:49:47.926 [bus debug] notify request: done
2023-05-24 20:49:47.926 [bus notice] scan 08: ;Vaillant;recoV;0229;0203
2023-05-24 20:49:47.926 [bus debug] switching from send response ACK to send SYN
2023-05-24 20:49:47.927 [main debug] reading directory /home/alpxp/confs/vaillant/
2023-05-24 20:49:47.927 [main debug] file type of /home/alpxp/confs/vaillant/08.recov.csv is file
2023-05-24 20:49:47.927 [main debug] found 1 matching scan config files from vaillant with prefix 08: done
2023-05-24 20:49:47.927 [main debug] reading directory /home/alpxp/confs/vaillant/
2023-05-24 20:49:47.927 [main debug] file type of /home/alpxp/confs/vaillant/08.recov.csv is file
2023-05-24 20:49:47.931 [bus debug] send/receive symbol latency 4 ms
2023-05-24 20:49:47.931 [bus debug] switching from send SYN to ready
2023-05-24 20:49:47.932 [main error] error reading scan config file vaillant/08.recov.csv for ID "recov", SW0229, HW0203: ERR: element not found, vaillant/08.recov.csv:25: ERR: element not found, field type TEMP in field 0
2023-05-24 20:49:47.932 [main error] initial scan failed: ERR: element not found
2023-05-24 20:49:52.635 [network info] [00001] client connection opened 127.0.0.1
2023-05-24 20:49:52.635 [main debug] >>> info
2023-05-24 20:49:52.635 [main debug] <<< version: ebusd 23.1.23.1
device: /dev/ttyACM0, enhanced, firmware 1.1[3501].1[3501]
signal: acquired ...
2023-05-24 20:49:52.635 [network debug] [00001] wait for result
2023-05-24 20:49:52.637 [network info] [00001] connection closed
2023-05-24 20:49:53.636 [network debug] dead connection removed - 0
^C2023-05-24 20:49:57.082 [main notice] SIGINT received
2023-05-24 20:49:57.754 [main notice] ebusd stopped

and the Recovair is visible in

alpxp@raspberrypi4:~ $ ebusctl info
version: ebusd 23.1.23.1
device: /dev/ttyACM0, enhanced, firmware 1.1[3501].1[3501]
signal: acquired
symbol rate: 24
max symbol rate: 42
min arbitration micros: 5
max arbitration micros: 5
min symbol latency: 4
max symbol latency: 4
reconnects: 0
masters: 2
messages: 32
conditional: 0
poll: 0
update: 0
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=recoV;SW=0229;HW=0203"
address 31: master #8, ebusd
address 36: slave #8, ebusd

I wonder if this is a bug and should be moved to issues?

Anyhow... Now I'm stuck with the 08.recov.csv, which is not in the database. I downloaded the one from this pull request. But it gives an error:

ERR: element not found, field type TEMP in field 0

I also don't see other messages with the data in the log. Should I see them at this point as the "First steps" say?

[QubaB]

I was downloading configuration files and manually adujsted them. I also obtained errors like "ERR: element not found, field type TEMP in field 0" as you.

You should try to download also _templates.csv (in /etc/ebusd directory) and probably other csv files. When I downloaded all configuration files it started to work (probably different definitions in _templates.csv in different versions).

[alpxp]

Thank you for the advice. I downloaded https://github.com/john30/ebusd-configuration/tree/master/ebusd-2.1.x/en to /etc/ebusd.
And added `08.recov.csv' there as well. The log now says:

2023-05-24 21:43:09.830 [main debug] found 3 matching scan config files from vaillant with prefix 08: done
2023-05-24 21:43:09.830 [main error] unable to load scan config 08: no file from vaillant with prefix 08 matches ID "recov", SW0229, HW0203

So it does not seem to see the added file:

alpxp@raspberrypi4:~ $ ls /etc/ebusd/en/vaillant/08.recov.csv 
/etc/ebusd/en/vaillant/08.recov.csv

Presumably because this file is broken anyway?
How did you figure out how to adjust the config files manually?

[QubaB]

I think that the name of directory cannot contain /en/ it should be /etc/ebusd/vaillant

[alpxp]

Sorry. They are. I tried both.

alpxp@raspberrypi4:/etc/ebusd/vaillant $ ls /etc/ebusd/vaillant/08.*
/etc/ebusd/vaillant/08.bai.csv  /etc/ebusd/vaillant/08.ehp.csv  /etc/ebusd/vaillant/08.hmu.csv  /etc/ebusd/vaillant/08.recov.csv

Still, 3 found.

2023-05-25 10:06:51.094 [main debug] found 3 matching scan config files from vaillant with prefix 08: done
2023-05-25 10:06:51.095 [main error] unable to load scan config 08: no file from vaillant with prefix 08 matches ID "recov", SW0229, HW0203

I think this might have to do with the fact that /etc/ebusd/vaillant/08.recov.csv has errors. Although log does not say this directly.
If I isolate this file in separate folder and run

alpxp@raspberrypi4:~/confs $ ebusd -f --checkconfig -c /home/alpxp/confs
2023-05-25 10:13:18.197 [main notice] ebusd 23.1.23.1 performing configuration check...
vaillant/08.recov.csv:31: ERR: element not found, field type TEMPSENSOR in field 1
2023-05-25 10:13:18.201 [main error] error reading config files from /home/alpxp/confs/: ERR: element not found, last error: vaillant/08.recov.csv:31: ERR: element not found, field type TEMPSENSOR in field 1

This is why I asked about how do you know how to debug the csv files.
Thanks for your help!

[QubaB]

You should edit _templates.csv and add "tempsensor" to the first column and add additinonal columns specification (I do not know the meaning of columns).

I did not edited _templates.csv at the end, so I cannot give you more help.

[alpxp]

That was it! Thank you very much!
I can read some of the data now. I'll have to figure out how to generate 08.recov.csv for my device.
And I will probably submit a bug reporting that only --loglevel=debug works. Strange.