An ebusd add-on

Porsti · March 26, 2026, 1:30pm

a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }

Unfortunately, I can currently only post one image, so here is a screenshot of the Home Assistant page.

wrongisthenwright · March 26, 2026, 2:08pm

You are making some confusion.

uEbusd is a replacement for the HA addon so, if it works for your HVAC system, you can disable the ebusd add-on in HA.

either you use uEbusd or you use the addon.

uEbusd should send MQTT messages to your broker

Porsti · March 28, 2026, 10:20am

Hi,

Thanks for the tip. I hadn’t thought of that, and I couldn’t find any information about it in other forums.

Now I’m one step closer since the connection is established.

Unfortunately, I’m still not receiving any data from the heating system.

Porsti · March 28, 2026, 10:49am

Unfortunately, this information from the log is not being received by HA via MQTT.


{
  "desiredtemp": 42.80078125,
  "outsidetemp": 7,
  "forced": null,
  "hwc": 0,
  "hc": 0,
  "hwcdesiredtemp": 10
}

  
{
  "status": "heat",
  "action": "pumpoff",
  "desiredtemp": 42.8125,
  "desiredpress": null,
  "settingdegree": null,
  "hwcdesiredtemp": 10,
  "fuel": null
}

However, I can see this information in the MQTT Explorer.

oliof · March 28, 2026, 12:57pm

I had to add REST sensors for some things that wouldn’t come through HA automatically.

I gave uebusd a short test. But it didn’t take my config files and all my entities broke or got duplicated or both. So I am staying with the old setup for now.

Porsti · March 28, 2026, 2:34pm

Hi,

I couldn’t get it to work with the old configuration. I’ve made some progress with the new one.

How do I add REST sensors?

This is my first experience with ebusd and MQTT.

Is this correct, or should it say something else?

oliof · March 28, 2026, 7:15pm

No that’s not correct.

You need to tell uebus the address and username/password of the MQTT server you are running, which needs to be accessible by the MQTT integration.

Porsti · March 28, 2026, 7:55pm

This is what the Home Assistant configuration looks like. The MQTT connection works without any problems.

empifree · April 2, 2026, 7:30am

I noticed that sometimes some data is not updating for a longer period. I noticed it because I set up my energy diagram to see also the heat pump consumption. When my total current consumption was high I checked the heat pump sensors and there was no data.

My ebusd configuration:

In the logs I see very often “unkwon MS cmd”:


2026-04-02 09:26:21.366 [update notice] received poll-read ctlv2 Hc2PumpStatus QQ=f1: 1

2026-04-02 09:26:21.557 [update notice] received poll-read ctlv2 Hc2ActualFlowTempDesired QQ=f1: 37.9029

2026-04-02 09:26:21.747 [update notice] received poll-read ctlv2 Z2DayTemp QQ=f1: 22

2026-04-02 09:26:21.939 [update notice] received poll-read ctlv2 Z2ActualRoomTempDesired QQ=f1: 22

2026-04-02 09:26:22.122 [update notice] received poll-read ctlv2 Z2OpMode QQ=f1: auto

2026-04-02 09:26:24.177 [update notice] sent poll-read hmu YieldHcDay QQ=31: 34.1

2026-04-02 09:26:28.003 [update notice] received read hmu Status01 QQ=10: 42.0;37.5;3.000;-;44.0;on

2026-04-02 09:26:28.186 [update notice] received unknown MS cmd: f115b52406020003011b00 / 0601031b000000

2026-04-02 09:26:28.326 [update notice] received unknown MS cmd: 1076b5110101 / 09ff4b0003ff580000ff

2026-04-02 09:26:28.422 [update notice] received unknown MS cmd: f115b52406020001000f00 / 0601010f000000

2026-04-02 09:26:28.644 [update notice] received unknown MS cmd: 1076b512030f0001 / 07c1020000801302

2026-04-02 09:26:28.929 [update notice] received read vr_70 SensorData QQ=10: 35.69;-;-;-;40.31;35.62;c8 7c 00

2026-04-02 09:26:29.197 [update notice] received update-write hmu SetMode QQ=10: auto;37.5;-;-;0;1;1;0;0;0

2026-04-02 09:26:29.463 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101

2026-04-02 09:26:29.719 [update notice] received write vr_70 SetActorState QQ=10: off;-;off;off;-;-;off

2026-04-02 09:26:29.962 [update notice] received write vr_70 Mc2Operation QQ=10: on;37.5;on;15

2026-04-02 09:26:30.171 [update notice] sent poll-read hmu YieldHcMonth QQ=31: 111.3

2026-04-02 09:26:35.613 [update notice] received update-write omu OMUControl QQ=03: prerun;prerun;fan_overrun;-0.215;0.055;710;88

2026-04-02 09:26:36.169 [update notice] sent poll-read hmu YieldHwc QQ=31: 6929

2026-04-02 09:26:37.979 [update notice] received read hmu Status01 QQ=10: 42.0;37.5;3.000;-;44.0;on

2026-04-02 09:26:38.244 [update notice] received unknown MS cmd: 1076b5110101 / 09ff4b0003ff580000ff

2026-04-02 09:26:38.511 [update notice] received unknown MS cmd: 1076b512030f0001 / 07c1020000801302

2026-04-02 09:26:38.720 [update notice] received unknown BC cmd: 10feb505025c00

2026-04-02 09:26:39.006 [update notice] received read vr_70 SensorData QQ=10: 35.69;-;-;-;40.38;35.69;c8 7c 00

2026-04-02 09:26:39.271 [update notice] received update-write hmu SetMode QQ=10: auto;37.5;-;-;0;1;1;0;0;0

2026-04-02 09:26:39.537 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101

2026-04-02 09:26:39.780 [update notice] received unknown MS cmd: 1008b50702094b / 026601

2026-04-02 09:26:40.049 [update notice] received read hmu DateTime QQ=10: valid;09:26:41;02.04.2026;3.000

2026-04-02 09:26:40.284 [update notice] received update-read Broadcast Vdatetime QQ=10: 09:26:39;02.04.2026

2026-04-02 09:26:40.540 [update notice] received write vr_70 SetActorState QQ=10: off;-;off;off;-;-;off

2026-04-02 09:26:40.805 [update notice] received unknown MS cmd: 1008b5110100 / 09a302146400090001c8

2026-04-02 09:26:41.049 [update notice] received write vr_70 Mc2Operation QQ=10: on;37.5;on;15

2026-04-02 09:26:41.262 [update notice] received update-read Broadcast Outsidetemp QQ=10: 3.000

2026-04-02 09:26:42.205 [update notice] sent poll-read hmu YieldHwcDay QQ=31: 0.0

2026-04-02 09:26:44.189 [update notice] received unknown MS cmd: f115b52406020003011b00 / 0601031b000000

2026-04-02 09:26:44.372 [update notice] received unknown MS cmd: f115b52406020001000f00 / 0601010f000000

2026-04-02 09:26:47.933 [update notice] received read hmu Status01 QQ=10: 42.0;37.5;3.000;-;44.0;on

2026-04-02 09:26:48.185 [update notice] sent poll-read hmu YieldHwcMonth QQ=31: 1.1

2026-04-02 09:26:48.279 [update notice] received unknown MS cmd: 1076b5110101 / 09ff4b0003ff580000ff

2026-04-02 09:26:48.545 [update notice] received unknown MS cmd: 1076b512030f0001 / 07c1020000801302

2026-04-02 09:26:48.831 [update notice] received read vr_70 SensorData QQ=10: 35.69;-;-;-;40.38;35.69;c8 7c 00

2026-04-02 09:26:49.098 [update notice] received update-write hmu SetMode QQ=10: auto;37.5;-;-;0;1;1;0;0;0

2026-04-02 09:26:49.365 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101

2026-04-02 09:26:49.621 [update notice] received write vr_70 SetActorState QQ=10: off;-;off;off;-;-;off

2026-04-02 09:26:49.865 [update notice] received write vr_70 Mc2Operation QQ=10: on;37.5;on;15

2026-04-02 09:26:53.216 [update notice] received unknown MS cmd: f108b50905540200180b / 060201180b460c

2026-04-02 09:26:53.397 [update notice] received read hmu Status01 QQ=f1: 42.0;37.5;3.000;-;44.0;on

And for data like TargetFlowTemp it only updates rarely:

2026-04-02 07:51:18.192 [update notice] sent poll-read hmu TargetFlowTemp QQ=31: 0.00
2026-04-02 08:22:48.135 [update notice] sent poll-read hmu TargetFlowTemp QQ=31: 40.00
2026-04-02 08:54:18.176 [update notice] sent poll-read hmu TargetFlowTemp QQ=31: 38.50
2026-04-02 09:25:48.192 [update notice] sent poll-read hmu TargetFlowTemp QQ=31: 38.00

Or EnergyIntegral:

2026-04-02 08:18:24.190 [update notice] sent poll-read hmu EnergyIntegral QQ=31: -304
2026-04-02 08:49:54.184 [update notice] sent poll-read hmu EnergyIntegral QQ=31: -171
2026-04-02 09:21:24.188 [update notice] sent poll-read hmu EnergyIntegral QQ=31: -290

Is there something I can do, so the data is fetched more often?

oliof · April 2, 2026, 8:42pm

You can set priority by polling an entity with ebusd/$circuit/$entity/get and content ?1 via MQTT. I have an automation that does this for all known ebusd entities at home assistant startup and once per hour. (

empifree · April 2, 2026, 9:53pm

Can you specify a bit more? I am new to that topic. And also can you share your automation?

oliof · April 4, 2026, 6:45am

OK, so if you check your MQTT server, i.e. with the MQTTExplorer App, or any other way, you will see an ebusd topic, with a number of entries and values.

A freshly started ebus instance may not update (some) values frequently. But ebus knows priorities for certain values, and you can set them in various ways. For thes examples, assume I want to get the CopHcMonth value updated more regular (chosen because it usually is not reported very often)

on the commandline:

ebusctl read -p 1 -f -c hmux0 CopHcMonth

This means that I read the value, while setting Priority to 1 (-p 1), getting fresh values (-f), from the circuit hmux0. After that, this value will be sent more frequently due to the priority setting.

But I can do this via an MQTT message I send to the MQTT server as well. On the MQTT side, the topic is ebusd///get (equivalent to read), with the message ?1 (equivalent to -p 1).

I should immediately get a value back:

Side note: Some values seem to get filtered by the default hass-mqtt.config of ebusd, and instead of tweaking that, I pull the values as MQTT sensors. An example from my configuration.yaml:

mqtt:
  sensor:
    - name: "HMU Compressor Speed"
      unique_id: "hmu_compressor_speed"
      state_topic: "ebusd/hmux0/RunDataCompressorSpeed"
      unit_of_measurement: "rps"
      value_template: "{{ value_json['0'].value }}"
      icon: mdi:speedometer

the good news is that I can query those as well with the get and ?1 method to get them to update speedily. And you can build your own climate and water heater entities this way that make use of multiple entities.

Back to automations. It’s tedious to do that for more than one time for more than one value after ebusd restarts. So, let’s automate this.

The simple version: For every value you are interested, add an MQTT publish action. Run this whenever HomeAssistant starts, and every hour.

But this is kinda annoying if you have many entries you want updated, so there is another way: Find all ebus controlled sensors, build the MQTT query for that and run them in a loop. So that’s automatable as well. Unfortunately, in preparing this post I found my full automation to be somewhat broken so I need to revisit and fix it up. But that’ll take some time.

empifree · April 4, 2026, 7:07pm

Wow, very helpful and with the MQTT Explorer App I now have also a better insight! Thank you very much!

miho8 · April 12, 2026, 9:32am

I recently did the uodate to ebusd 26.x and the changes seem to have broken my system. I am running HA on a RP4 with an ebus adaptor v5 and ebusd as an app.

The website of the ebus adaptor v5 shows the signal as acquired.

However, I don’t get any messages through to ebusd. Ebusctl info shows the signal as not present. How can I debug that further?

No changes were done around the serial interface but I am not certain that there wasn’t an inadvertant change due to some other update.

afiwube · July 27, 2026, 9:27pm

@miho8 Can you share your App config yaml?
A common mistake is not entering the ens prefix for the device.

Your screenshot of the adapter lists ens:/dev/tty… as the device string but your ebusctl info reads /dev/tty… (missing the ens protocol)

afiwube · August 6, 2026, 9:57am

I helped someone upgrade to version 26 and they recorded it. Perhaps it’s helpful to someone else.

In German: https://www.youtube.com/watch?v=BK9Vht0MnBQ

oliof · August 7, 2026, 2:46pm

~~Anyone else experience issues with the MQTT transport not connecting after updatingto 2026.8?~~

PEBKAC, fixed.