Thank you very much. I used the repo you mentioned.
I copied 15.ctlv2.csv to 15.ctlv3.csv because 15.ctlv3.csv was missing.
I copied 76.vwz.csv to 76.vwzio.csv because the link in 76.vwzio.csv to 76.vwz.csv did not work.
I downloaded f6.netx2.csv from ebusd-configuration/ebusd-2.1.x/de/vaillant/f6.netx2.csv at bcc234454da556d3636b35b041193e4777acaa18 · rmalbrecht/ebusd-configuration · GitHub
Now all necessary files are found. There are still some error messages regarding some fields. As long as I don’t miss a specific field, I won’t look for it.
It doesn’t seem to want to allow a service: mqtt.publish. Does it have to be done differently now ? I think all mqtt config is now within the integration ???
After not touching my ebusd config in about a year, I have now switched from the Sensocomfort 720/2 to the 720/3 and a few things weren’t working. Now I am looking for a way to update the csv files, but it’s all still very confusing.
I initially downloaded the JonesPD files and made a few edits, now it seems there are various repos thst each have different files. John (the Online repo that is automatically polled I think?) has the latest Updates 2 Months ago, others are only 2 Weeks old for some files, but 9 years for others…
I think the repo of JonesPD is the most up-to-date and complete for the ctlv2.csv (VRC 720/2) and hmu.csv. Renaming 15.ctlv2.csv to 15.ctlv3.csv should enable the 720/3 for ebusd as it is very similar to 720/2 (BTW: all csv files should be local and then can be edited).
If you get to decoding ebus messages from the 720/3 I would be very interested in the register for the ‘HWC alternative point’. This setting is only available in the 720/3 controller UI (not in 720/2) and I would like to check if this setting is hidden but also available in the 720/2 via ebus. This setting can be used to exclusively activate the backup heater in DHW (hot water) mode. Thanks! 
1 Like
Unfortunately…I don’t know what I am doing in terms of eBus, so I won’t be much help in terms of decoding anything new, unless you give me some instructions…
Same problem here.
The container stucks in “starting”.
Any useful ebusd logfile (error) messages?
No, I’m sorry. I would like to provide more information. Just the normal ebusd-output.
I have the ‘EBUS to WiFi Adapter Module V6.3’ connected to the VR71 of my Vaillant system. It succesfully reads out data and I can make all kinds of graphs which is a nice starting point. However, I have some questions regarding an error message on my thermostat and how to get more frequent data.
Error on thermostat
Ever since connecting the adapter (and even before linking it to HA) there has been an error on my thermostat (VRC720). In Dutch it says "Signaal sensor S9 FM5 ongeldig’, or in English ‘Signal sensor S9 FM5 invalid’. There’s is nothing connected to the S9 input on the VR71 itself (only S1, S2 and S3 are connected). Has anyone else experienced this, anything I could try? It’s mainly very annoying to not see the temperatures on the thermostat immediately… I’ve also asked the question to the developer of the adapter, but no response yet.
More frequent data
For some specific entitities I would like to receive much more frequent data but I can’t figure out how to achieve that. For example, one of the most interesting for me is the CurrentConsumedPower (sensor.ebusd_hmu_ebusd_hmu_currentconsumedpower). However, it seems to take 5-10 minutes before a first data point is captured when the heatpump starts working (and there is a change in the CurrentConsumedPower). For example here you can see one of the circuits was turned on at ~21:25 (maybe even earlier?), but the CurrentConsumedPower only gives a first datapoint at 21:30 (whereas I would expect a steady rise with more steps every 10 seconds for example).
The ‘poll for data every second’ is set to 5 seconds already. I tried editing the CSV file to give higher priority to certain entities, but that doesn’t seem to change anything. Did I set this up wrong?
Anything I could try?
For compleness some screenshots on the settings: [well guess not as I’m only allowed to put two links…]
Concerning the S9 error:
What is your VR71 configuration (can be set up in the VRC720, values can be 1,2,3 or 6)? Only in configuration 3 the system would expect the storage cylinder temperature sensor (SP1) on S9. I don’t see how connecting the ebus adapter could trigger the error message unless some other configuration change took place, too. Did you try restarting the VRC720? Is the error gone when the ebus adapter is disconnected?
Concerning more frequent data:
I had inconsistent results when trying to adjust poll intervals using the poll priorities in the CSVs.
-
Instead you could setup a time-based trigger (e.g. every minute) in HA activating a MQTT publish action like:
ebusd/hmu/currentconsumedpower/get
This should update the reading in HA. -
Alternatively you could setup a CRON-based schedule and issue the ‘
ebusctl read -f -c hmu CurrentConsumedPower’ command e.g. every minute on the HA system level. -
Or you could use the recently identified hmu register
CurrentConsumedPowerWattwhich delivers the current consumed power in Watt (not kW) and this value is polled automatically every minute by the VR921 (internet gateway, if you have one).
See this PR for more information:
1 Like
Restarting the VRC720 seems to have done the trick for now (I hadn’t realized there was a button…). The VR71 is set to value 3 and as far as I remember has always been like that. Nothing else has changed. The error is indeed gone when the adapter is removed. Let’s see if it stays gone…
Edit: well, that didn’t take long, error is back already 
The time-based seems to be the easiest way forward. I’m still very new to all this, so could you point me in the right direction where I would need to add this command?
I don’t have a VR921 otherwise would have been a nice way out!
Assuming you have the ‘ebusd addon’ and ‘Mosquitto MQTT’ up and running in HA, you just need to create an automation that is e.g. triggered every minute and performs an ‘MQTT publish action’ with the topic
ebusd/hmu/currentconsumedpower/get
with any payload (e.g. 0) and QoS set to 1 (as you wish). This can all be done in the HA GUI for automations.
You can test the action in the ‘Development/Action’ section of HA before creating the automation. Successful polling can be monitored with the respective entity in HA or e.g. in the ebusd logfile.
1 Like
Only when the ebus adapter is hooked up or also in absence of the adapter?
Hi everyone,
Great topic, I connected the EBUS adapter shield C6 to my old Vaillant boiller (TurboTEC 242/3-5 -2009 version) just to gain experience for the new EcoTec version which is on the way.
Almost all the parameters contained in the 08.bai.7401.csv file are present via MQTT integration, some of them I will remove manually by editing the file because I don’t have any other Vaillant proprietary thermostats or whaterver connected to it.
Even though the parameters refresh rate is terrible (tried with pool data interval 1 seccond = no success), I hope I will speed up some of them by automations, did’t tried yet.
Now, after 2 days of research with no success I kindly ask for your help with controlling the IO pins from the adapter shield, I intend to plug into it a relay board to control heating on or off and to remove the Tuya wireless thermostat currently in use.
No matter what I try it seems these pins cannot be controlled via MQTT (or I don’t know the right topic yet), only via web interface or REPL command window…
If I execute: io -o -h 0 or io -o -l 0 in in REPL, I can control the state of the DO5 high or low:
…the logs confirm that .
…but with MQTT no success, I tried every combinations like :
Topic: eas/io/0/set
Payload: {“value”:1}
…this is just an example like many other combinations I made between eas and ebusd topics…nothing works…from outside the web interface.
…tried even with shell scripts:
echo “io -o -h 0” | nc -w 2 192.168.1.136 9999
echo “io -o -l 0” | nc -w 2 192.168.1.136 9999
chmod +x /config/scripts/set_io0_high.sh
chmod +x /config/scripts/set_io0_low.sh
…nothing works.
It seems there is no much information about controlling these IO’s via MQTT or other method other than it’s own web interface.
I’m stuck …any help will be highly appreciated…thank you.
Sorry for the late reply, haven’t been able to play around with it It seems since I rebooted both my thermostats a few times the error is now gone… As far as I can remember the error was there only when the adapter was hooked up, but currently I can’t reproduce the issue (hopefully it stays like that).
Thanks also for the suggestions on creating an automation, that’s something I will look into.
To check if it’s working, should I be seeing values in the log or only that it was triggered? For example in the ebusd log I see:
2024-10-24 08:39:01.670 [mqtt notice] read hmu currentconsumedpower: 0
Edit: I think I got it working. I’ve created a few such automations, where for one case I wasn’t sure what the ‘topic’ should be and can now clearly see which ones are working and which not.
Hi. At the moment I use HA Addon for install ebusd. But there is very old version of ebusd (23.2).
How can I install the newest version (24.1)?
2 Likes
Well, my Home Assistant with ebusd addon was working fine for a long time, but today it suddenly stopped. I didn’t change anything, but although both sides seem to think everything is fine, no data is being transmitted between the adapter andthe addon (Wifi Connection) anymore…
1 Like
My ebusd seems to be throwing errors and issues with more frequency. It is also complaining that it’s outdated and wants version 24.1 which I can’t find
1 Like
Hi,
No news about how to catch device behind on the VR32 ?
I have an Hybrid setup with Arotherm+ & VWZAI, VRC700, and a VR32 to address my ECOTEC PRO on #2
Regards,
Ulric