VRC 720/2 with MEH 97/6 not compatible with ebusd?

[witmic01]

Hello all,

I would like to ask for some help.

Ebusd here does not work with

• VRC 720/2 (sensoCOMFORT)
• MEH 97/6 (Hydraulikstation)
• aroTHERM plus VWL 75/6 A 230V S2

The heat pump system itself has been working flawlessly now for 6 weeks (0 errors listed; I conclude from this that the wiring is ok) but ebusd does not recognise any of the components.

ESERA RS232 adapter used (via USB adapter into Raspberry Pi 3), signals are received, but not a single device is recognised (ebusctl only reports "scanning"). Adapter has been checked and "refurbished" by ESERA meanwhile - no improvement on this. (eBus Adapter v3 ordered in Dec/2022 and eagerly awaited.)

Maybe the manufacturer has modified the firmware. Firmware here:

• Regler (sensoCOMFORT): -> 05.14
• Waermepumpe 1 (aroTHERM): -> 06.07
• WP-Regelungsmodul (Hydraulikstation?): -> 06.07

Has anybody this same setup running successfully with ebusd?

Thanks a lot for any feedback!

Best regards

Michael.

ebusd.log
raw.log

[cyberthom42]

Ich have a similar setup

• SensoComfort VRC 720f (8.05)
• aroTHERM plus 55/6 (6.07)
• Hydraulikstation MEH 97/6 (6.07)

For me it works perfect (ebus adapter 2.1)

address 03: master #11 address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0607;HW=5103", loaded "vaillant/08.hmu.csv" address 0a: slave, scanned "MF=Vaillant;ID=PMW01;SW=0206;HW=8302", loaded "vaillant/0a.pmw.hwc.csv" address 10: master #2 address 12: slave, scanned "MF=Vaillant;ID=PMW01;SW=0206;HW=8302" address 15: slave #2, scanned "MF=Vaillant;ID=BASV2;SW=0507;HW=1704", loaded "vaillant/15.basv.csv" address 31: master #8, ebusd address 36: slave #8, ebusd address 71: master #9 address 76: slave #9, scanned "MF=Vaillant;ID=VWZIO;SW=0607;HW=5103" address f1: master #10 address f6: slave #10, scanned "MF=Vaillant;ID=NETX2;SW=4027;HW=5703" address f7: master #20 address fc: slave #20, scanned "MF=Vaillant;ID=PMW01;SW=0206;HW=8302"

[flushbug]

Looks like I have a vr720 and not a vr720/2 but the article no is the same. Maybe the official successor? Can not find anything about the difference. Also strange because my system was installed last year in September.

vr720f is the wireless version with an additional base station so it sounds reasonable that the firmware version is different.

Even if the vr720 firmware is different, the heatpump should be found on the bus as our firmware versions are the same.

maybe there is some issue with your bus access at all ? I have read that esera Interfaces are sometimes struggeling with write access.
i had to turn on write access in the ebusd config for the scan to be successful. Just guessing.

[witmic01]

Ok, that sounds reasonable: The firmware of the VR720 is one thing, but since I can see a lot of "b5" messages (=Vaillant) on the Bus when raw logging, the controller firmware doesn't seem to be my problem. I will concentrate on the hardware now.

Thanks a lot!

Michael.

[SzosszeNET]

@witmic01 did you manage to get yours works working? I do seem to have the same version (firmware?) ebus components but if I start ebusd with the VR720 attached I quite some errors arbritartion lost, etc
After I disconnect the VR720 and start ebusd it looks like it gets some actual data too

[witmic01]

Yes, my configuration is working now. Firmware versions are ok, my problem obviously was the adapter hardware (Esera RS232). Currently using Daniel Kucera's adapter, which works flawlessly so far.

[SzosszeNET]

@witmic01, that puzzles me than. I got his adapter today, set up the latest ebusd container not sure if it's working all right - assume not?

2023-02-23 22:58:07.676 [main notice] ebusd 23.1.23.1 started with auto scan on device esp-ebus.majoros.me:3333
2023-02-23 22:58:08.483 [bus notice] bus started with own address 31/36
2023-02-23 22:58:08.486 [bus notice] signal acquired
2023-02-23 22:58:10.711 [bus notice] new master 10, master count 2
2023-02-23 22:58:10.766 [bus notice] new master 03, master count 3
2023-02-23 22:58:10.766 [update notice] received unknown MS cmd: 1008b5110101 / 0938390080ffff0000ff
2023-02-23 22:58:11.035 [bus notice] new master 71, master count 4
2023-02-23 22:58:11.035 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff5008ff6c0000ff
2023-02-23 22:58:11.302 [update notice] received unknown MS cmd: 1076b512030f0101 / 076003000080ff00
2023-02-23 22:58:11.516 [update notice] received unknown BC cmd: 10feb505025c00
2023-02-23 22:58:11.780 [update notice] received unknown MS cmd: 1008b51009000037ffffff060000 / 0101
2023-02-23 22:58:12.045 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101
2023-02-23 22:58:12.318 [update notice] received unknown MS cmd: 1076b5040100 / 0a00ffffffffffffff5008
2023-02-23 22:58:12.556 [update notice] received unknown MS cmd: 1008b507020937 / 023202
2023-02-23 22:58:12.794 [update notice] received unknown BC cmd: 10feb516080039592223020423
2023-02-23 22:58:15.466 [update notice] received unknown BC cmd: 10feb51603014007
2023-02-23 22:58:15.987 [update notice] received unknown MS cmd: 0376b51206130010b40400 / 0200ff
2023-02-23 22:58:18.639 [bus notice] scan 08: ;Vaillant;HMU00;0607;5103
2023-02-23 22:58:18.639 [update notice] store 08 ident: done
2023-02-23 22:58:18.639 [update notice] sent scan-read scan.08 QQ=31: Vaillant;HMU00;0607;5103
2023-02-23 22:58:18.639 [bus notice] scan 08: ;Vaillant;HMU00;0607;5103
2023-02-23 22:58:19.300 [main notice] read common config file vaillant/broadcast.csv
2023-02-23 22:58:19.465 [main notice] read common config file vaillant/scan.csv
2023-02-23 22:58:19.630 [main notice] read common config file vaillant/general.csv
2023-02-23 22:58:19.896 [main notice] read scan config file vaillant/08.hmu.csv for ID "hmu00", SW0607, HW5103
2023-02-23 22:58:20.223 [main notice] found messages: 65 (0 conditional on 0 conditions, 0 poll, 10 update)
2023-02-23 22:58:20.374 [update notice] sent unknown MS cmd: 3108b5090124 / 09003231323233383030
2023-02-23 22:58:20.582 [update notice] sent scan-read scan.08 id QQ=31:
2023-02-23 22:58:20.735 [update notice] sent scan-read scan.08 id QQ=31:
2023-02-23 22:58:21.430 [update notice] sent scan-read scan.08 id QQ=31: 21;22;38;0010047382;1300;105253;N9
2023-02-23 22:58:21.430 [bus notice] scan 08: ;21;22;38;0010047382;1300;105253;N9
2023-02-23 22:58:21.697 [update notice] received read hmu Status01 QQ=10: 28.0;28.5;-;-;-;off
2023-02-23 22:58:21.965 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff5008ff6c0000ff
2023-02-23 22:58:22.233 [update notice] received unknown MS cmd: 1076b512030f0101 / 076003000080ff00
2023-02-23 22:58:22.567 [update notice] received update-write hmu SetMode QQ=10: auto;27.5;-;-;0;1;1;0;0;0
2023-02-23 22:58:22.654 [bus error] own master address 31 is used by another participant
2023-02-23 22:58:23.374 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101
2023-02-23 22:58:23.613 [bus notice] scan 15: ;Vaillant;CTLV2;0514;1104
2023-02-23 22:58:23.613 [update notice] store 15 ident: done
2023-02-23 22:58:23.613 [update notice] sent scan-read scan.15 QQ=31: Vaillant;CTLV2;0514;1104
2023-02-23 22:58:23.613 [bus notice] scan 15: ;Vaillant;CTLV2;0514;1104
2023-02-23 22:58:23.766 [update notice] sent unknown MS cmd: 3115b5090124 / 09003231323233313030
2023-02-23 22:58:23.923 [update notice] sent scan-read scan.15 id QQ=31:
2023-02-23 22:58:24.002 [bus notice] max. symbols per second: 109
2023-02-23 22:58:24.158 [update notice] sent scan-read scan.15 id QQ=31:
2023-02-23 22:58:24.318 [update notice] sent scan-read scan.15 id QQ=31: 21;22;31;0020260921;0953;013860;N1
2023-02-23 22:58:24.318 [bus notice] scan 15: ;21;22;31;0020260921;0953;013860;N1
2023-02-23 22:58:24.483 [main error] unable to load scan config 15: no file from vaillant with prefix 15 matches ID "ctlv2", SW0514, HW1104
2023-02-23 22:58:24.483 [main error] scan config 15: ERR: element not found
2023-02-23 22:58:26.688 [main error] scan config 36: ERR: read timeout
2023-02-23 22:58:28.882 [bus notice] scan 76: ;Vaillant;VWZIO;0202;0103
2023-02-23 22:58:28.882 [update notice] store 76 ident: done
2023-02-23 22:58:28.882 [update notice] sent scan-read scan.76 QQ=31: Vaillant;VWZIO;0202;0103
2023-02-23 22:58:28.882 [bus notice] scan 76: ;Vaillant;VWZIO;0202;0103
2023-02-23 22:58:29.063 [update notice] sent unknown MS cmd: 3176b5090124 / 09003231323234323030
2023-02-23 22:58:29.245 [update notice] sent scan-read scan.76 id QQ=31:
2023-02-23 22:58:29.425 [update notice] sent scan-read scan.76 id QQ=31:
2023-02-23 22:58:29.605 [update notice] sent scan-read scan.76 id QQ=31: 21;22;42;0010031644;0082;010561;N4
2023-02-23 22:58:29.605 [bus notice] scan 76: ;21;22;42;0010031644;0082;010561;N4
2023-02-23 22:58:29.769 [main error] unable to load scan config 76: no file from vaillant with prefix 76 found
2023-02-23 22:58:29.769 [main error] scan config 76: ERR: element not found
2023-02-23 22:58:30.751 [update notice] received read hmu Status01 QQ=10: 28.0;28.5;-;-;-;off
2023-02-23 22:58:31.019 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff5008ff6c0000ff
2023-02-23 22:58:31.287 [update notice] received unknown MS cmd: 1076b512030f0101 / 076003000080ff00
2023-02-23 22:58:31.551 [update notice] received update-write hmu SetMode QQ=10: auto;27.5;-;-;0;1;1;0;0;0
2023-02-23 22:58:31.816 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101
2023-02-23 22:58:39.929 [update notice] received unknown MS cmd: 0376b51206130010b30400 / 0200ff
2023-02-23 22:58:40.719 [update notice] received read hmu Status01 QQ=10: 28.0;28.5;-;-;-;off
2023-02-23 22:58:40.987 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff5008ff6c0000ff
2023-02-23 22:58:41.255 [update notice] received unknown MS cmd: 1076b512030f0101 / 076003000080ff00
2023-02-23 22:58:41.519 [update notice] received update-write hmu SetMode QQ=10: auto;27.5;-;-;0;1;1;0;0;0

[codingstube]

Good morning everyone,

I get a similar setup. Can someone explain, where the ebus adapter is connected. Should I use the ebus interface in the MEH97/6 or VRC720.

In my opinion I should connect it to the ebus interface in the MEH97/6, although there are already devices connected like the VRC720. Am I right?

Thanks

[JonesGW-MGD]

Makes no difference - attach in parallel to any ebus-designated set of terminals - ideally keep the cable as short as reasonably possible too, if that is a determining factor in your choice of location - but it's not hyper-sensitive to this in my experience.

[codingstube]

Thanks Jones.

Finally I got my Shield v5 Adapter. But I only get temperatures (outside/inside) and Firmware Versions.

ebusctl info
version: ebusd 23.3.23.3
device: 192.168.0.67:9999, TCP, enhanced, firmware 1.1[431e].1[431e]
signal: acquired
symbol rate: 115
max symbol rate: 144
min arbitration micros: 11
max arbitration micros: 25
min symbol latency: 5
max symbol latency: 16
scan: running
reconnects: 0
masters: 4
messages: 501
conditional: 0
poll: 0
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0902;HW=5103", loaded "vaillant/08.hmu.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=CTLV2;SW=0514;HW=1104", loaded "vaillant/15.ctlv2.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9

Any other data is missing. So do I have a wrong/old csv file?

EBUSD_CONFIGPATH is https://cfg.ebusd.eu

Log output example:

2024-07-12 09:27:17.472 [update notice] received unknown MS cmd: 1076b5040100 / 0a0318271112070524670f
2024-07-12 09:27:17.709 [update notice] received unknown MS cmd: 1008b507020900 / 02bf04
2024-07-12 09:27:17.949 [update notice] received update-read broadcast vdatetime QQ=10: 11:27:16;12.07.2024
2024-07-12 09:27:18.212 [update notice] received unknown MS cmd: 1008b5110100 / 091d0112000000000000
2024-07-12 09:27:18.431 [update notice] received update-read broadcast outsidetemp QQ=10: 15.402
2024-07-12 09:27:18.662 [update notice] received update-write hmu StatusCirPump QQ=10: on
2024-07-12 09:27:18.892 [update notice] received unknown MS cmd: 1008b5120204ff / 00
2024-07-12 09:27:19.126 [update notice] received unknown MS cmd: 1008b513020528 / 0101
2024-07-12 09:27:19.222 [update notice] received read hmu State QQ=71: 0;0;192;0
2024-07-12 09:27:19.389 [update notice] received unknown BC cmd: 10feb510020601
2024-07-12 09:27:20.435 [update notice] received unknown MS cmd: 0376b51206130012000006 / 0200ff
2024-07-12 09:27:22.636 [update notice] received read hmu State QQ=71: 0;0;192;0
2024-07-12 09:27:25.976 [update notice] received read hmu Status01 QQ=10: 17.5;17.0;-;-;-;off
2024-07-12 09:27:26.068 [update notice] received read hmu State QQ=71: 0;0;192;0

[JonesGW-MGD]

Hi there,

firstly, you're posting on a closed thread - this may not be the best way to get assistance from others - suggest perhaps you create a new discussion topic instead?

But a few things from what you have shared. You are accessing the latest 'official' repository files because your config path is the online source.

You are getting more than simply outside/inside temperatures though - in the small snippet of the logs you have provided you can see the status of the circulation pump and several other status settings (read hmu stat....)

It might help others if you outline in a bit more detail how you are running the daemon - standalone, in a container, using the Home Assistance add-on etc. That can help people give specific advice. Also outline how you intend to consume the data that ebusd provides - HA, your own MQTT etc. etc.

To troubleshoot and explore what you are receiving further, you should be able to go to a terminal session on the instance running your ebusd daemon and use the ebusctl command, such as:

ebusctl read Hours

or

ebusctl read EnergyIntegral

in fact you should be able to read any of the read message types from either of the two files that are loaded.

The only device that isn't loading a configuration file is address 76 - which most likely is a hydraulic unit like a VWZ MEH 97/6? There is no official file for address 76 but if you google/search these forums you may see reference to vaillant/76.vwzio.csv - the bottom line here is that to use this file you need to find it first from someone and then run all your config locally.

I would start by trying to get the most data from the files that have loaded first.

[codingstube]

Hi Jones,
wow thanks for your fast and detailed response.
I have now all config files I need and it is working. What I didn‘t understand is, that ebusd scan not all data, that I have to read it manually to test/receive the actually data.

Now that I‘m getting data I‘ll implement it to my mqtt server.