Interesting as I thought that the micro-ebusd solution used the same cloud repository as does the post-24.1 full ebusd (https://ebus.github.io/). I just upgraded to the most recent code and the return temperature is in hmu RunDataReturnTemp which seems to be missing in your case.
relevant scan result from ebusctl info for my Arotherm+, vr720, Unitower and 920 gateway:
As an aside, if you have ufw running on the ebusd host, ebusd service will fail to load unless you make an exception for all udp from the ebusd IP address (fix in router dns if possible). This is because the ebusd mDNS broadcast is sent from a random high port, not the standard 5353 (which is RFC compliant for a non fully-compliant Multicast DNS querier. That phased me for a bit!
They switched to a new TypeSpec language to define the message structure, so maybe that has something to do with it. I don’t have influence over which definition files are loaded with the micro-ebusd, for example the vwzio shows barely any info as opposed to my current local setup. This will probably be sorted out with time, and maybe we need some more people to test this out. My trial only runs another month and I won’t pay to extend it
ebusd log shows: write message hmu HwcMode not found
Then going into the addon:
ebusctl find -w HwcMode ERR: element not found
sensor.ebusd_hmu_hwcmode has repeatedly polled as “eco” even though its been balanced mode for the last three weeks.
I don’t appear to have Hwcmode as an option:
ebusctl find -w Hwc
basv HwcBankHolidayEndPeriod = no data stored
basv HwcBankHolidayStartPeriod = no data stored
basv HwcHolidayEndPeriod = no data stored
basv HwcHolidayStartPeriod = no data stored
basv HwcLockTime = no data stored
basv HwcMaxFlowTempDesired = no data stored
basv HwcOpMode = no data stored
basv HwcParallelLoading = no data stored
basv HwcSFMode = no data stored
basv HwcTempDesired = no data stored
basv HwcTimer_Friday = no data stored
basv HwcTimer_Monday = no data stored
basv HwcTimer_Saturday = no data stored
basv HwcTimer_Sunday = no data stored
basv HwcTimer_Thursday = no data stored
basv HwcTimer_Tuesday = no data stored
basv HwcTimer_Wednesday = no data stored
basv PrEnergySumHwc = no data stored
basv PrEnergySumHwcLastMonth = no data stored
basv PrEnergySumHwcThisMonth = no data stored
basv PrFuelSumHwc = no data stored
basv PrFuelSumHwcLastMonth = no data stored
basv PrFuelSumHwcThisMonth = no data stored
ebusctl info
version: ebusd 25.1.p20250414
update check: revision 25.1 available, device firmware v5-c6 1[6104] available, vaillant/08.hmu.csv: different version available
device: 10.10.1.9:9999, TCP, enhanced, firmware 1.1[560f].1[560f]
signal: acquired
symbol rate: 23
max symbol rate: 169
min arbitration micros: 5
max arbitration micros: 16
min symbol latency: 5
max symbol latency: 15
scan: finished
reconnects: 0
masters: 5
messages: 706
conditional: 0
poll: 0
update: 29
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=BASV3;SW=0708;HW=4304", 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=0202;HW=0103", loaded "vaillant/76.vwzio.csv"
address f1: master #10
address f6: slave #10, scanned "MF=Vaillant;ID=NETX3;SW=0128;HW=0404"
Edit, without the writable flag:
ebusctl find HwcMode
hmu HwcMode = no data stored
hmu HwcModeActive = no data stored
Ah yes, it appears your config does not expose this parameter. I’m not sure which of the zhings you’re seeing would work, msybe HwcOpMode? Can you read/write that?
Hi recently installed Arotherm 7kW instal and got round to installing the hardware adapter today I’ve been through this thread and decided to try the micro-ebusd option. I’m new to eBUS so very much a beginner and will need and appreciate help to understand and process the data. I get a similarly long set of data, 321 items in my case. I think I do get the flow & return temps when I view the dataset in MQTT Explorer, they show up in hmu/status01 as temp & temp_1. Flowrate shows in hmu/BuildingCircuitFlow.
I do seem to get quite a few warning messages in the logs for about a dozen unknown messages but I’ll post those separately.
I’ve got a Frankenstein config based off some jonesPD’s repo files where I changed some things. I’m not even on the latest ebusd version since that would require me to rework some of the config files. Try out the configs at GitHub - jonesPD/ebusd-configuration: ebusd configuration files
Hello everyone, can somebody help me? I have ebus adapter shield c6, home assistant running as haos on minipc, installed mqtt in HA, but I am not getting all the data that I can see on my wvzio live data monitor. I have also installed ebusd add on in HA, and in addon configuratiom tab, a config path is set to: https://ebus.github.io/; acces level: *; mqtt integration config file: etc/ebusd/mqtt-hassio.cfg.
ebusctl info:
so I have to change something in config file (maybe change to other repo, john30?) and/or mqtt integration config file to pull more fields? can anybody help me?
I havent changed config file yet, I have installed mqtt explorer and when I publish ebusd/hmu/livemonitorcurrentsupplytemp/get, in the mqtt explorer I can see the value, but that is not presented in mqtt integration in home assistant, so my conclusion would be that I have to download mqtt-hassio.cfg, change (filter-name:? maybe) something in that file but I am not exactly sure what.
So you can see it on the broker but can’t see it in the HA integration?
There is no such thing (directly) as an MQTT Integration in HA (other than below). Do you mean this value doesn’t appear in this eBUS integration? In which case, it isn’t defined for it to decode it.
Try using a template sensor in HA and reference the MQTT topic/key/value pair directly. MQTT Sensor - Home Assistant
Be careful of teminology -
I think you men that using MQTT Explorer, when you Subscribe to the topic ebusd/hmu/livemonitorcurrentsupplytemp/get you can see it has a value of xx and this updates (is Published to the MQTT Broker by the ebusd) every x seconds?
I’ve visited and read through this thread a number of times but the length and complexity has been putting me off until now.
I have some time available to progress and bitten the bullet and ordered a miniPC for running Home Assistant. Intended for various other home automation including Vaillant ASHP.
Before ordering the C6 adapter. Am i correct in thinking that the eBUS Adapter Stick C6 would be the version to order (if HA is running on a miniPC) and doesnt need a dedicated raspberry Pi? Just wire into the 2 pin bus, power via USB C and the data is then transmitted over wifi or LAN (with an optional LAN add on)
If the miniPC running Home Assistant is nearby the 2 pin bus wiring, I am correct in thinking you can plug the C6 adapter stick into the USB C port to both power and access the data within HA?
I am running ChatGPT research to help document step by step instructions how to configure within HA. If anyone who has gone through the process recently and has taken any notes or if any guides, info or tips may help a newbie in easy to understand terms, any info or template config files would be much appreciated.
Yes you could use a USB port on a computer to power the stick, but afaik it won’t transmit data via USB. It may but I don’t know. It’s trivially easy just to connect to it over WiFi.
I don’t get on well with Home Assistant and only wanted emonCMS monitoring, so bypassed HA completely. No regrets! My posts on how I did that are a short way up this thread.
A quick addendum - if you are using docker then you need to run the ebusctl command within the container:
docker ps to get the container ID; say it is “dead12345678”
docker exec -it dead12345678 ebusctl find to run the command.
If you have remapped the port within ebusd (say from 8888 to 8889) then it is
docker exec -it dead12345678 ebusctl -p 8889 find
