SetModeOverride not working?

[gr0mit1]

Description

I'm controlling the boiler flow temp using SetModeOverride.

I'm publishing the following values via MQTT from Home Assistant:
{
"hcmode": {"value": 0},
"flowtempdesired": {"value": 55.0},
"hwctempdesired": {"value": 0.0},
"hwcflowtempdesired": {"value": null},
"setmode1": {"value": null},
"disablehc": {"value": 0},
"disablehwctapping": {"value": 0},
"disablehwcload": {"value": 0},
"setmode2": {"value": null},
"remoteControlHcPump": {"value": 0},
"releaseBackup": {"value": 0},
"releaseCooling": {"value": 0}}

Actual behavior

Since migrating to the built-in ebusd it refuses to set the boiler flow temp. I get the following error:

12:46:00	Warning	ebusd: encode not found write bai/SetModeOverride

Expected behavior

my HA ebusd daemon responds correctly. iirc I had to add an additional message definition to the ebusd file? Is there another way to achieve the same result using the built-in ebusd?

ebusd version

current source from git

ebusd arguments

micro-ebusd

Operating system

Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite)

CPU architecture

x64

Dockerized

None

Hardware interface

Adapter Shield v5/C6/Stick via USB

Related integration

other

Logs

12:46:00	Warning	ebusd: encode not found write bai/SetModeOverride

[john30]

seems this is a micro-ebusd issue, so please use https://github.com/john30/ebusd-esp32/issues/ instead.
anyway, what message definitions did you use previously and did you also set the user level in micro-ebusd to match the ebusd accesslevel?

[gr0mit1]

Hi John – Happy New Year! This was what I had to do in ebusd to be able to control the flow temp of my Vaillant Ecotec Plus, buried deep in this thread: #1572: I discovered that the SetModeOverride command needs to be manually added to your configuration files. Specifically, in the file bai.308523.inc, I added the following line: r;wi,,SetModeOverride,Betriebsart,,08,B510,00,hcmode,,UCH,,,,flowtempdesired,,D1C,,,,hwctempdesired,,D1C,,,,hwcflowtempdesired,,UCH,,,,setmode1,,UCH,,,,disablehc,,BI0,,,,disablehwctapping,,BI1,,,,disablehwcload,,BI2,,,,setmode2,,UCH,,,,remoteControlHcPump,,BI0,,,,releaseBackup,,BI1,,,,releaseCooling,,BI2 With this in place, I was able to successfully call: ebusctl write SetModeOverride '0;55;0;-;-;0;0;0;-;0;0;0' This enabled me to write the flow temp setpoint from Home Assistant: actions: - data: payload: >- 0;{{ states('input_number.boiler_flow_temp') | int }};0;-;-;0;0;0;-;0;0;0 topic: vaillant/bai/SetModeOverride/set action: mqtt.publish From: John ***@***.***> Reply to: john30/ebusd ***@***.***> Date: Saturday, 3 January 2026 at 13:39 To: john30/ebusd ***@***.***> Cc: Tim Robinson ***@***.***>, Author ***@***.***> Subject: Re: [john30/ebusd] SetModeOverride not working? (Issue #1647) [Image removed by sender.]john30 left a comment (john30/ebusd#1647)<#1647 (comment)> seems this is a micro-ebusd issue, so please use https://github.com/john30/ebusd-esp32/issues/ instead. anyway, what message definitions did you use previously and did you also set the user level in micro-ebusd to match the ebusd accesslevel? I set UserLevel to ‘admin’ – see screenshot. Any ideas? Thanks Tim — Reply to this email directly, view it on GitHub<#1647 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC2Y4I4ORWGRGT5YF2XEG7T4E7BBLAVCNFSM6AAAAACQHOT6QCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBXGA3DEMJWGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>