If anyone tries this let me know how you get on. I’ve tried finding the noise reduction configuration, but no luck yet…
Worth reaching out on the git conversation?
I’ve also been struggling to get the contents of the basv file (Amongst other things!)
In my case I had the error:
main error] error reading scan config file vaillant/15.basv.csv for ID “basv3”, SW0760, HW7304: ERR: end of input reached, vaillant/15.basv.csv:1: ERR: end of input reached, missing message type/name/pbsb
I’ve just copied the contents of 15.700.csv into 15.basv.csv and am now receiving the basv data.
Previously the 15.basv.csv file just had an entry of ‘15.700.csv’.
The same applies to the 76.vwzio.csv file (Copy 76.vwz.csv)
1 Like
exactly the same my side , I had to copy the all content to the related CSV, the “routing” not working
BTW, for my boiler behind the VR32 (sorry to keep that) , I finally manage to catch it, I saw an error on scan 15 and V32 not being decoded, so I just renamed the 08.bai.csv ( I know it’s for the boiler ) to 15.V32.csv and it works perfect now !
1 Like
Hello everyone,
I am experiencing issues with some outputs that are now missing.
- Return
- Flow Rate
The hardware as follows
- eBUS Adapter Shield Interface v6 Wifi connected
- Vaillant ASHP 7Kw
- Home Assistant
- Core2025.1.4
- Supervisor2024.12.3
- Operating System14.2
- Frontend20250109.2
- eBUSd version: 24.1.1
And ive downloaded the lastest from :-
https://github.com/john30/ebusd-configuration.git
The mqtt-hassio.cfg.txt was from your feed back in Nov and rename mqtt-hassio.cfg
Could anyone who has a working configuration with all the parameters I require to get Emons back working properly?
Thank you to [Andre_K] for the solution
1 Like
I think most of us are using this fork, which has all values working, at least for me: GitHub - jonesPD/ebusd-configuration: ebusd configuration files
2 Likes
thanks, It’s working correctly now
1 Like
My adapter appears to have fallen off my network for some reason. Is there a way to reconnect it? I’m connecting over WiFi.
Does it come back after a power cycle? I think if it permanently doesn’t get a connection it should present a hotspot again like on first setup.
1 Like
It randomly reconnected at 4am so I think it was a blip with my router as it kept throwing http errors
Hi Folks,
I am interested in getting independant metrics from my Vaillant AeroTherm 5+ system, so been reading up about this on various threads.
I am from a microsoft stack software engineering background so used to acronyms… 
At the moment however I am just trying to understand the basics.
Does the following 10,000ft view of things sound about right, or have I got it wrong already 
- This is connected directly into an existing connector inside the Vaillant ASHP?
- If so then, if any existing ducts are not available then would need to drill hole in wall to feed cable in?
- EBUS – The message protocol?
- EBUS Adapter – Like the Shield v5? Takes the eBus data and presumably converts it into a different format?
- Raspberry Pi
- Connect straight onto adapter using pins or else via Wifi
- This runs the ebusd software which is some kind of marshalling software that can post messages using MQTT
- This is an event based queuing protocol? So the next stage software like Home assist subscribes to the queue and pulls message packets when available to create the fancy graphs I see a lot of this site?
- Home assistant
- Provides all the fancy graphs showing things like COP, in and out flow temps etc?
However the data from above is coming straight from the Heat Pump right?, so same data as existing Vailant sensors? If so:
- Cannot be used to double check Vaillant’s values?
- Is this system just used for folk who do not have the SensoComfort App, and so no other way of seeing COP values?
EmonPi
This looks like a more meaty, fully independent monitor as it is not using the EBUS direct from the Vaillant ASHP? But expensive and looks more intimidating for a newbie. Would need solid DIY skills and competence for fuse boxes etc, or get many folk get a contractor in to fit it?
It connects onto the eBus (anywhere along the eBus), and takes all messages being sent anywhere along the eBus. So it takes data from the indoor units as well as from the outdoor unit (so can take the Room Temperature from the Senso Comfirt and the Outside Temperature)
I personally upload my data from HA to OpenenergyMonitor. So you don’t need the EmonPi for this. I do like the visuals of the OpenenergyMonitor portal.
I do feel that the data is far more accurate when using the eBusD rather than the App, and of course, you are not relying on the Vaillant Cloud. And I do wonder how long it will take before it changes to a subscription model
Hello all - sharing my journey.
My goal was to have the Outdoor temp sensor from ebus replace the metoffice data on emoncms.org. I have my ebus receiver running in the EmonPI2 and publishing to mqtt by following the instructions in this thread. Looking at the config and docs I assumed it would be easy to get the messages into local emoncms and then propagate to emoncms.org - but it doesn’t look like it’s going to happen.
I had the data coming into local emoncms by changing the ebusd base topic to emon/. There doesn’t seem to be any way to forward it on - looks more to be an emonhub action based on the config of the other sensors. The existing MQTT config is set up specifically to push data into opencms by the looks of it - publishing to ToEmonCMS isn’t possible because that’s what it’s subscribing to.
I then tried setting up a new MQTT interfacer with a base topic of ebusd/ - this didn’t do anything. Nothing in the logs, no connection attempts. Could be due to the broker settings being the same.
[[MQTT]]
...
[[EBUSD]]
Type = EmonHubMqttInterfacer
[[[init_settings]]]
mqtt_host = 127.0.0.1
mqtt_port = 1883
mqtt_user = emonpi
mqtt_passwd = emonpimqtt2016
[[[runtimesettings]]]
pubchannels = ToEmonCMS,
nodevar_format_enable = 1
nodevar_format_basetopic = ebusd/
nodename = EBUSD
So, I’m currently rethinking my architecture, which is a shame because all the pieces seem to be there - hopefully I’m just missing something.
Options for me are:
- quick and dirty script to push the relevant stuff to emoncms.org using curl and cron, running on emonpi2
- Have ebusd push data via mqtt to a broker on my automation server, have homeassitant or something else push the data to emoncms.org (begs the question why have the ebus receiver on the emonpi2 at all - I could just plug it directly into the server).
You can just use the sync function to move data to emoncms.org
Hi Championc,
Thanks for getting back to me.
Can you expand on the eBus part please?
Is this via a wired connection hooking straight into the heat pump itself, or is this available wirelessly as presumably the outside temp gauge and Vaillant controller operates?
(If so) then in essence I just need a modernish raspberry pi hooked up to the ebus adapter somewhere near the existing Vaillant controller, then the software on the pi (ebusd and home assistant), produces all the nice graphs I see on these forums, giving independent COP values, COP whilst active versus cycling etc?
This is a little device connected via 2 wires to the heatpump. It can then provide the ebus data either locally to an RPi it’s plugged into or also wirelessly to a computer running Ebusd or Home Assistant.
Yes. Home assistant is not needed even - you can install emonCMS on the Pi and have everything you need on there. That’s how it looks for me:
The little external device on the right is the eBus adapter, which is connected to the heat pump and via USB to the Pi. The Pi runs on an emonSD image and I simply installed ebusd on there as well. It is completely self contained.
Hey all.
I have a PI 4 B and Sheild C6 adapter fitted to the GPIO pins of the PI.
Had a go last night, (I have zero programming skill so used chat GPT as a guide) Managed to get RPI OS installed, and ebusd downloaded but could not configure it to a point where it could start the eBUSd software without errors.
Is it easier to setup on RPi OS or Homeassistant OS? As I’ve changed that many settings I think I’ll go for a clean install and try again!
Or, does anyone have an image/clone/backup of their SD card after configuring one that they could share?
This might be very helpful for others.
1 Like
I wouldn’t go with a cloned image, a simple setup script is sufficient. We could collaboatively write a guide. It’s been a year, but the general steps are
- Install emonSD image onto SD card. This way all the nice emonCMS apps are also available. Can be found here
- Insert into RPi, boot up & login via ssh.
- Add the ebusd repository according to this guide. I’m unsure which Debian the current images are built upon, my Nov 23 is on bullseye. Install ebusd.
- Clone the jonesPD github repo locally.
- Modify the ebusd config to point at the jonesPD folder and use the appropriate serial device for ebus communication.
- Optionally install Node-RED and configure a flow to pipe relevant values into emonCMS. This way, a standalone ebus-driven heatpump app could be configured.
Did I miss anything?