Opened an issue on GitHub. My name is A-J70 there.
Could someone please upload it again, the link expired? 
I’ve prepared a version of Ysard’s CSV file that doesn’t have any field name starting with a number, in my setup ebusd starts without complaining, I have a different system so I cannot test it very much.
Try it and see if the errors are gone.
This file has been prepared and tested in a boiler only configuration (no remote thermostat/control AFAIK) with a Chaffoteaux Mira .
I’m not the maintainer of this file so I cannot help very much in using it.
Not suited for hybrid configurations.
1 Like
I’m getting more errors I believe. I’ve used the _templates.csv from Ysard’s repo. And not getting any messages decoded properly:
[update error] unable to parse read boiler heat_request_status_2 from 37fe2010080591000006910000 / : ERR: invalid position
2025-01-24 21:54:10.048 [update notice] received read boiler boiler_status: heating
2025-01-24 21:54:10.204 [update notice] received read boiler heat_request_status_1: on;off;off;off
2025-01-24 21:54:10.330 [update error] unable to parse read boiler heat_request_status_2 from 37fe2010080591000006910000 / : ERR: invalid position
2025-01-24 21:54:10.423 [update notice] received read broadcast accept_telegrams_heating_status:
2025-01-24 21:54:10.498 [update notice] received unknown BC cmd: 37fe200f0401200100
2025-01-24 21:54:10.885 [main notice] starting initial broadcast scan
2025-01-24 21:54:10.977 [update notice] sent unknown BC cmd: 31fe07fe00
2025-01-24 21:54:12.566 [update notice] sent poll-read boiler error_slot_9 QQ=31: 5P3;0;-;-;-;-:-
2025-01-24 21:54:12.610 [update notice] received read broadcast accept_telegrams_z1_heat_request_mode:
2025-01-24 21:54:12.686 [update notice] received unknown BC cmd: 37fe200f04c6790300
2025-01-24 21:54:13.417 [update notice] received read broadcast accept_telegrams_z2_heat_request_mode:
2025-01-24 21:54:13.492 [update notice] received unknown BC cmd: 37fe200f04c67a0300
2025-01-24 21:54:15.064 [update notice] received read boiler boiler_status: heating
2025-01-24 21:54:15.220 [update notice] received read boiler heat_request_status_1: on;off;off;off
2025-01-24 21:54:15.342 [update error] unable to parse read boiler heat_request_status_2 from 37fe2010080591000006910000 / : ERR: invalid position
2025-01-24 21:54:15.717 [update notice] received read broadcast accept_telegrams_z3_heat_request_mode:
2025-01-24 21:54:15.787 [update notice] received unknown BC cmd: 37fe200f04c67b0300
2025-01-24 21:54:16.404 [update notice] received unknown BC cmd: 37fe201004d7420000
2025-01-24 21:54:16.550 [update notice] received unknown BC cmd: 37fe20100dc19402006996be0000c2940200
2025-01-24 21:54:16.698 [update notice] received unknown BC cmd: 37fe20100e6a96be0000c39402006b96be0000
2025-01-24 21:54:16.841 [update notice] received unknown BC cmd: 37fe20100dc49402006c96be0000c5940200
2025-01-24 21:54:16.989 [update notice] received unknown BC cmd: 37fe20100e6d96be0000c69402006e96be0000
2025-01-24 21:54:16.992 [mqtt error] decode boiler heat_request_status_2: ERR: invalid position
2025-01-24 21:54:17.022 [bus notice] max. symbols per second: 109
2025-01-24 21:54:17.145 [update notice] received unknown BC cmd: 37fe201010d3460000cf9c0000d9950000da950000
2025-01-24 21:54:17.301 [update notice] received unknown BC cmd: 37fe201010db950000dc950000dd950000de950000
2025-01-24 21:54:17.398 [update notice] received read broadcast accept_telegrams_sra_status:
2025-01-24 21:54:17.473 [update notice] received unknown BC cmd: 37fe200f0405200100
2025-01-24 21:54:17.630 [update notice] received unknown BC cmd: 37fe201010d9940000da940000db940000dc940000
2025-01-24 21:54:17.754 [update notice] received unknown BC cmd: 37fe201008dd940000de940000
2025-01-24 21:54:17.905 [update notice] received unknown BC cmd: 37fe20100f604731010061973101006297440200
2025-01-24 21:54:18.005 [bus notice] max. symbols per second: 141
2025-01-24 21:54:18.059 [update notice] received unknown BC cmd: 37fe20100f639744020064974402006597440200
2025-01-24 21:54:18.231 [update notice] sent poll-read boiler error_slot_9 QQ=31: 5P3;0;-;-;-;-:-
2025-01-24 21:54:18.286 [update notice] received unknown BC cmd: 37fe2010056697440200
2025-01-24 21:54:18.414 [update notice] received read dhw dhw_real_temp: 8.0
2025-01-24 21:54:18.543 [update notice] received unknown BC cmd: 37fe200002c67c
2025-01-24 21:54:18.620 [update notice] received unknown BC cmd: 37fe200f04c67c0300
2025-01-24 21:54:19.138 [update notice] received read broadcast accept_telegrams_dhw_status:
2025-01-24 21:54:19.212 [update notice] received unknown BC cmd: 37fe200f0402200100
2025-01-24 21:54:20.007 [update notice] received read broadcast accept_telegrams_z1_thermoreg_offset:
2025-01-24 21:54:20.082 [update notice] received unknown BC cmd: 37fe200f0564710a0000
2025-01-24 21:54:20.239 [update notice] received read boiler boiler_status: heating
2025-01-24 21:54:20.394 [update notice] received read boiler heat_request_status_1: on;off;off;off
2025-01-24 21:54:20.519 [update error] unable to parse read boiler heat_request_status_2 from 37fe2010080591000006910000 / : ERR: invalid position
2025-01-24 21:54:20.649 [update notice] received unknown BC cmd: 37fe200002c67d
2025-01-24 21:54:20.723 [update notice] received unknown BC cmd: 37fe200f04c67d0300
2025-01-24 21:54:21.108 [update notice] store 3c ident: ERR: invalid position
2025-01-24 21:54:21.108 [update error] unable to parse scan-read scan.3c from 313c070400 / 00: ERR: invalid position
2025-01-24 21:54:21.109 [main error] scan config 3c: ERR: invalid position
2025-01-24 21:54:21.110 [mqtt error] decode boiler heat_request_status_2: ERR: invalid position
2025-01-24 21:54:22.155 [mqtt error] decode scan.3c : ERR: invalid position
2025-01-24 21:54:22.601 [update notice] received read broadcast accept_telegrams_z1_fixed_temp:
2025-01-24 21:54:22.668 [update notice] received unknown BC cmd: 37fe200f056571360100
2025-01-24 21:54:22.792 [update notice] received unknown BC cmd: 37fe201008de464b00d1f20700
2025-01-24 21:54:22.917 [update notice] received unknown BC cmd: 37fe201008dc464b00d2f20400
2025-01-24 21:54:23.037 [update notice] received unknown BC cmd: 37fe201008da469600d3f20100
2025-01-24 21:54:23.345 [update notice] received read broadcast accept_dhw_target_temp:
2025-01-24 21:54:23.439 [update notice] received unknown BC cmd: 37fe200e086126c20168015802
2025-01-24 21:54:23.927 [update notice] received unknown BC cmd: 37fe200002c67e
2025-01-24 21:54:24.002 [update notice] received unknown BC cmd: 37fe200f04c67e0300
2025-01-24 21:54:24.178 [update notice] sent poll-read boiler error_slot_9 QQ=31: 5P3;0;-;-;-;-:-
2025-01-24 21:54:25.658 [update notice] received unknown BC cmd: 37fe2001026571
2025-01-24 21:54:25.751 [update notice] received unknown BC cmd: 37fe200e0865713601c800c201
2025-01-24 21:54:25.906 [update notice] received read boiler boiler_status: heating
2025-01-24 21:54:26.065 [update notice] received read boiler heat_request_status_1: on;off;off;off
2025-01-24 21:54:26.186 [update error] unable to parse read boiler heat_request_status_2 from 37fe2010080591000006910000 / : ERR: invalid position
You need to use this file with ysard’s
_templates.csv
Yes, I’ve used his csv file, the log in my above post is with that one.
Unknown messages are the norm as we’ve been able to decode only part of the protocol.
Are the most common metrics updated in HA? I’m referring as an example to Z1 room temp, LWT, EWT and so on?
BTW I’va added a note on this regard in the OP, because many messages still remains of unknown meaning ebusd will continuously generate decoding errors, the only sensible way I’ve found to declutter logs is to raise the log threshold for ebusd from info to error for the “update” function (ebusctl log update error)
Some message seems to be decoded:
2025-01-24 21:54:10.048 [update notice] received read boiler boiler_status: heating
2025-01-24 21:54:10.204 [update notice] received read boiler heat_request_status_1: on;off;off;off
2025-01-24 21:54:10.423 [update notice] received read broadcast accept_telegrams_heating_status:
2025-01-24 21:54:12.566 [update notice] sent poll-read boiler error_slot_9 QQ=31: 5P3;0;-;-;-;-:-
2025-01-24 21:54:12.610 [update notice] received read broadcast accept_telegrams_z1_heat_request_mode:
2025-01-24 21:54:13.417 [update notice] received read broadcast accept_telegrams_z2_heat_request_mode:
2025-01-24 21:54:15.064 [update notice] received read boiler boiler_status: heating
2025-01-24 21:54:15.220 [update notice] received read boiler heat_request_status_1: on;off;off;off
2025-01-24 21:54:17.398 [update notice] received read broadcast accept_telegrams_sra_status:
2025-01-24 21:54:18.231 [update notice] sent poll-read boiler error_slot_9 QQ=31: 5P3;0;-;-;-;-:-
2025-01-24 21:54:18.414 [update notice] received read dhw dhw_real_temp: 8.0
2025-01-24 21:54:19.138 [update notice] received read broadcast accept_telegrams_dhw_status:
2025-01-24 21:54:20.007 [update notice] received read broadcast accept_telegrams_z1_thermoreg_offset:
2025-01-24 21:54:20.239 [update notice] received read boiler boiler_status: heating
2025-01-24 21:54:20.394 [update notice] received read boiler heat_request_status_1: on;off;off;off
2025-01-24 21:54:22.601 [update notice] received read broadcast accept_telegrams_z1_fixed_temp:
2025-01-24 21:54:23.345 [update notice] received read broadcast accept_dhw_target_temp:
2025-01-24 21:54:24.178 [update notice] sent poll-read boiler error_slot_9 QQ=31: 5P3;0;-;-;-;-:-
2025-01-24 21:54:25.906 [update notice] received read boiler boiler_status: heating
2025-01-24 21:54:26.065 [update notice] received read boiler heat_request_status_1: on;off;off;off
In your configuration many parameters are missing from the normal bus traffic as there is no one transmitting these, as the “native” bus network is composed only of the boiler.
We haven’t ben able to reverse engineer the handshaking protocol to emulate an ariston device like the remote control with ebusd and, to be honest, I don’t think it’s wise to do so with a critical system like a HVAC
You can:
-
set ebusd to read explicitly the most useful parameters from the boiler just adding a number (1,2…9) after the “r” character in the
r,boiler,xxxlines, this force ebusd to read the parameter every N cycles, don’t’ exagerate as this polling increase the bus usage, in your case should’n be a problem given that the bus is almost silent, this is an example:
r3,boiler,EWT_temp,heating return temperature,,3c,2000,6910,ign,s,IGN:1,,,,,,SIN,10,°C -
an alternative that I use for the parameters that almost never change (like boiler counters and thermoregulation settings) I run a scheduled script that polls these every hour, a file that contains many lines like these:
#!/bin/bash
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
touch /tmp/last_ebus_readall.txt
docker exec ebusd ebusctl read -m 0 -c boiler boiler_circulation_cycles && sleep 2
docker exec ebusd ebusctl read -m 0 -c boiler boiler_fan_cycles && sleep 2
docker exec ebusd ebusctl read -m 0 -c boiler boiler_life_time && sleep 2
docker exec ebusd ebusctl read -m 0 -c boiler boiler_pressure && sleep 2
docker exec ebusd ebusctl read -m 0 -c boiler boiler_type && sleep 2
every read parameter is ten sent via mqtt (if configured properly) to HA via mosquitto
1 Like
Thanks. I’ve tried for example reading the ext_temp, but this is what I get in the logs:
025-01-26 18:00:30.439 [update error] unable to parse read boiler ext_temp from 313c2000027647 / 0100: ERR: invalid position
2025-01-26 18:00:30.441 [main error] read boiler ext_temp: decode ERR: invalid position
And this in the command:
docker exec ebusd ebusctl read -VV -m 0 -c boiler ext_temp
ERR: Invalid position in decode [2000027647/00]
Do you have the external probe installed? In any way it seeems your boiler doesn’t answer to that query. Have you tried the other parameters?
Can you please help me too?
I have Ariston Clas EVO System and it seams that I can not decode any of the parameters.
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
ebusd --foreground --httpport=8889 --mqtthost=192.168.100.20 --mqttport=1883 --mqttuser=homeasssistant --mqttpass=my pass --scanconfig --mqttjson --configpath=/config/ebusd/ariston.csv --latency=10 --accesslevel=* --pollinterval=5 --mqttint=/config/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.100.161:9999 --log=all:info --log=main:info --log=bus:info --log=update:info --log=network:info --log=other:debug
2025-01-27 11:11:47.405 [device notice] transport opened
2025-01-27 11:11:47.406 [main info] registering data handlers
2025-01-27 11:11:47.407 [mqtt info] mosquitto version 2.0.20 (compiled with 2.0.20)
2025-01-27 11:11:47.407 [mqtt debug] connection requested
2025-01-27 11:11:47.407 [main info] registered data handlers
2025-01-27 11:11:47.407 [main notice] ebusd 24.1.p20241114 started with broadcast scan on device: 192.168.100.161:9999, TCP, enhanced
2025-01-27 11:11:47.407 [main info] loading configuration files from /config/ebusd/ariston.csv/
2025-01-27 11:11:47.407 [main error] error reading config files from /config/ebusd/ariston.csv/: ERR: element not found, last error:
2025-01-27 11:11:47.407 [bus notice] bus started with own address 31/36
2025-01-27 11:11:47.410 [mqtt notice] connection established
2025-01-27 11:11:47.410 [mqtt debug] publish ebusd/global/version “ebusd 24.1.p20241114”
2025-01-27 11:11:47.410 [mqtt debug] publish ebusd/global/running true
2025-01-27 11:11:47.410 [mqtt debug] publish ebusd/global/running true
2025-01-27 11:11:47.415 [bus notice] signal acquired
2025-01-27 11:11:47.415 [device notice] reset, supports info
2025-01-27 11:11:47.418 [device notice] extra info: firmware 1.1[5114].1[5114], jumpers 0x0b
2025-01-27 11:11:47.562 [bus notice] new master 37, master count 2
2025-01-27 11:11:47.562 [update info] received BC cmd: 37fe20100c059100000691000007910000
2025-01-27 11:11:47.562 [update notice] received unknown BC cmd: 37fe20100c059100000691000007910000
2025-01-27 11:11:47.671 [update info] received BC cmd: 37fe2000026047
2025-01-27 11:11:47.671 [update notice] received unknown BC cmd: 37fe2000026047
2025-01-27 11:11:48.358 [update info] received BC cmd: 37fe200002c679
2025-01-27 11:11:48.358 [update notice] received unknown BC cmd: 37fe200002c679
To see what is already grabbed in your system and what is missing can you please run the following commands:
- run on the host machine that runs ebusd the script readall.sh found on the ebusd Github repo:
https://raw.githubusercontent.com/john30/ebusd/refs/heads/master/contrib/scripts/readall.sh
this script reads every “r,xxx” line of the CSV one after the other, it will throw many errors but ignore them, please post here the results, it will give me a hint on what parameters my file is already capable of reading. You may need to fix/adapt the script
- affter the script execution run the command
ebusctl find -vthis should dump all the good readings
I am not at cmd commands level…I really don’t know how to run this, sorry.
Let’s start with the most best kept secrets here, as I really did not find any post about:
I have Studio Code Server installed on my HA, so I add a /ebusd/ folder under the /config folder.
In this /ebusd folder I added the ariston.csv, _template.csv and the mqtt-hassio.cfg files.
In your adddon the configuration is like this:
loglevel_all: info
mqtttopic: ebusd
mqttint: /config/ebusd/mqtt-hassio.cfg
mqttjson: true
network_device: 192.168.100.161:9999
latency: 10
configpath: /config/ebusd
loglevel_bus: info
loglevel_update: info
loglevel_main: info
loglevel_other: info
loglevel_network: info
mode: ens
pollinterval: 5
mqttport: 1883
mqtthost: 192.168.100.20
mqttuser: xxxxxxxx
mqttpass: xxxxxx
mqttlog: false
mqttretain: false
http: false
accesslevel: "*"
So, the secret remain, the mqtt-hassio.cfg is where it should? Should I run any command to clone this file in etc/ebusd…or is OK like that?
There is no any “adddon” folder, visible.
My Clas EVO System has John V6 board and the Ariston Cube S Net thermostat
Sorry @MBRetrofit, if I understand the question correctly and you’re asking me where to put my files to be used by the ebusd addon then I cannot help, as stated multiple times I don’t use the ebusd addon as I have not HAOS.
This kind of questions should be posed to the addon maintainer and/or on the addon thread here on the forum.
Hope you solve…
No worry, I solved. All files in /config/ebusd and path for mqtt is mqttint: /config/ebusd/mqtt-hassio.cfg
In the meantime I found the Terminal but any commands related with “ebusctl” gave me this kind of reply: ➜ ~ ebusctl find -v
zsh: command not found: ebusctl
If you run ebusd as an addon you should run ebusctl command inside the addon/container, use something similar to:
docker exec -it $(docker ps | grep ebusd | awk '{print $1}') /bin/bash
and then type:
ebusctl info
ebusctl find -v
and so on
You are very smart,
I just noticed that my son installed EMQX instead of Mosquitto.
On Addon log I have like this with your .csv’s:
-log=other:info
2025-01-30 10:05:20.507 [device notice] transport opened
2025-01-30 10:05:20.507 [main info] registering data handlers
2025-01-30 10:05:20.509 [mqtt info] mosquitto version 2.0.20 (compiled with 2.0.20)
2025-01-30 10:05:20.509 [main info] registered data handlers
2025-01-30 10:05:20.509 [main notice] ebusd 24.1.p20241114 started with broadcast scan on device: 192.168.100.161:9999, TCP, enhanced
2025-01-30 10:05:20.509 [main info] loading configuration files from /config/ebusd/
2025-01-30 10:05:20.510 [main info] reading templates /
2025-01-30 10:05:20.513 [main info] read templates in /
2025-01-30 10:05:20.513 [main info] reading file ariston.csv
2025-01-30 10:05:20.537 [main info] successfully read file ariston.csv
2025-01-30 10:05:20.537 [main info] read config files, got 337 messages
2025-01-30 10:05:20.537 [bus notice] bus started with own address 31/36
2025-01-30 10:05:20.537 [device notice] reset, supports info
2025-01-30 10:05:20.540 [mqtt notice] connection established
2025-01-30 10:05:20.541 [bus notice] signal acquired
2025-01-30 10:05:20.543 [device notice] extra info: firmware 1.1[5114].1[5114], jumpers 0x0b
2025-01-30 10:05:20.595 [bus notice] new master 7f, master count 2
2025-01-30 10:05:20.595 [update info] received BC cmd: 7ffe207007050a1e01041901
2025-01-30 10:05:20.596 [update notice] received update-read broadcast cast_date QQ=7f: 10:05;30.01.2025
On # ebusctl info, I have:
version: ebusd 24.1.p20241114
update check: revision 24.1 available, device firmware v5-c6 1[4c15] available
device: 192.168.100.161:9999, TCP, enhanced, firmware 1.1[5114].1[5114]
access: *
signal: acquired
symbol rate: 67
max symbol rate: 151
min arbitration micros: 9
max arbitration micros: 15
min symbol latency: 5
max symbol latency: 14
scan: finished
reconnects: 0
masters: 5
messages: 341
conditional: 0
poll: 0
update: 55
address 00: master #1
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 37: master #18
address 3c: slave #18, scanning
address 70: master #4
address 75: slave #4, scanning
address 7f: master #24
address 84: slave #24, scanning
On ebusctl find -v
heatpump heatpump_fan1_speed = no data stored
heatpump heatpump_fan1_state = no data stored
heatpump heatpump_fan2_speed = no data stored
heatpump heatpump_fan2_state = no data stored
heatpump heatpump_flow_switch = no data stored
heatpump heatpump_flowmeter = no data stored
heatpump heatpump_info = no data stored
heatpump heatpump_inverter_nominal_power = no data stored
heatpump heatpump_last_error = no data stored
heatpump heatpump_LWT_temp = no data stored
heatpump heatpump_main_pump = no data stored
heatpump heatpump_mode = no data stored
heatpump heatpump_other_info1 = no data stored
heatpump heatpump_power_consumption = no data stored
heatpump heatpump_preheater_state = no data stored
heatpump heatpump_safety_thermostat = no data stored
heatpump heatpump_shutoff_protection = no data stored
heatpump heatpump_suction_temp = no data stored
heatpump heatpump_teo_temp = no data stored
heatpump pump_max_pwm = no data stored
heatpump pump_min_pwm = no data stored
heatpump pump_operation = no data stored
heatpump silent_mode = no data stored
heatpump water_pump_info = no data stored
ignored ign4 = no data stored
ignored ign5 =
ignored ign6 =
scan.05 = no data stored
scan.3c = no data stored
scan.75 = (ERR: invalid position for 3175070400 / 00)
scan.84 = (ERR: invalid position for 3184070400 / 00)
sensys Address_23_sw_version = no data stored
sensys boiler_sw_version = no data stored
sensys energymgr_sw_version = no data stored
sensys heatpump_sw_version = no data stored
sensys remote_command_sw_version = no data stored
With .csv files from Y on ebusctl find -v, I have
broadcast accept_telegrams_external_temp = (empty for 37fe2000027647 / )
broadcast accept_telegrams_heating_status = (empty for 37fe2000020120 / )
broadcast accept_telegrams_sra_status = (empty for 37fe2000020520 / )
broadcast accept_telegrams_z1_fixed_temp = (empty for 37fe2000026571 / )
broadcast accept_telegrams_z1_fixed_temp_2010 = no data stored
broadcast accept_telegrams_z1_heat_request_mode = (empty for 37fe200002c679 / )
broadcast accept_telegrams_z1_heat_temp_range = (empty for 37fe2000020081 / )
broadcast accept_telegrams_z1_thermoreg_offset = (empty for 37fe2000026471 / )
broadcast accept_telegrams_z1_thermoreg_offset_2010 = no data stored
broadcast accept_telegrams_z2_fixed_temp = (empty for 37fe2000026572 / )
broadcast accept_telegrams_z2_fixed_temp_2010 = no data stored
broadcast accept_telegrams_z2_heat_request_mode = (empty for 37fe200002c67a / )
broadcast accept_telegrams_z2_heat_temp_range = (empty for 37fe2000020082 / )
broadcast accept_telegrams_z2_thermoreg_offset = (empty for 37fe2000026472 / )
broadcast accept_telegrams_z2_thermoreg_offset_2010 = no data stored
broadcast accept_telegrams_z3_fixed_temp = (empty for 37fe2000026573 / )
broadcast accept_telegrams_z3_fixed_temp_2010 = no data stored
broadcast accept_telegrams_z3_heat_request_mode = (empty for 37fe200002c67b / )
broadcast accept_telegrams_z3_heat_temp_range = (empty for 37fe2000020083 / )
broadcast accept_telegrams_z3_thermoreg_offset = (empty for 37fe2000026473 / )
broadcast accept_telegrams_z3_thermoreg_offset_2010 = no data stored
broadcast accept_thermoreg_type = (empty for 37fe200002c079 / )
broadcast accept_z1_thermoreg_slope = no data stored
broadcast accept_z1_water_max_temp = no data stored
broadcast accept_z1_water_min_temp = no data stored
broadcast cast_slave_addr = no data stored
dhw celectic_status = no data stored
dhw dhw_comfort_mode_status = dhw_comfort_mode_status=on;da46=UKN;dc46=UKN;de46=UKN
dhw dhw_comfort_mode_status_w = no data stored
dhw dhw_real_temp = =48.0
dhw dhw_status = no data stored
dhw dhw_target_temp = no data stored
scan.05 = no data stored
scan.3c = no data stored
scan.75 = (ERR: invalid position for 3175070400 / 00)
scan.84 = (ERR: invalid position for 3184070400 / 00)
In fact, I only change the _template with a smaller one from somewhere from here and values almost become populated,
ebusctl find -d -v
boiler boiler_pressure = boiler_pressure=3.0
boiler boiler_status = boilerstatus=standby
boiler boiler_type = =ext_tank_ntc
boiler config_version_counter = =237
boiler dhw_flowmeter = =0.0
boiler EWT_temp = =54.1
boiler fan_speed = =0
boiler flame_active = onoff=off
boiler hours_burner_on = =1190
boiler ignition_cycles = =6541
broadcast bus_control =
broadcast cast_date = time=15:50;date=30.01.2025
energymgr dhw_comfort_mode = =always_on
energymgr dhw_info_3 = dhw_comfort_temp=48.0;dhw_reduced_temp=10.0
energymgr dhw_status = onoff=on
energymgr dhw_thermal_cleansing_mode = onoff=on
energymgr error = error_code=—
energymgr ext_temp = =3276.7
energymgr z1_setpoint_temp = =10.0
ignored ign4 =
ignored ign5 =
ignored ign6 =
scan.75 = (ERR: invalid position for 3175070400 / 00)
scan.84 = (ERR: invalid position for 3184070400 / 00)
37fe200f0f69966400006a96be00006b96be0000 = 688: energymgr z1_setpoint_temp
37fe200f057647ff7f00 = 183: energymgr ext_temp
37fe20100c059100000691000007910000 = 2988: ignored ign6
37fe201004c04b0100 = 3119: boiler boiler_status
37fe2020106126e001622664006426320074260000 = 9: energymgr dhw_info_3
7f3c2000026810 / 03012b02 = 50
7f3c2000027747 / 0301ef01 = 51
7f3c200002c300 / 020100 = 10
7f3c200002c314 / 0201ff = 15
7f3c200102c428 / 03010003 = 51
703c2000040e11d140 / 030300ed = 3160: boiler flame_active
7f3c2000024013 / 03010000 = 19: boiler fan_speed
7f3c20000442d843d8 / 05038d190000 = 2: boiler ignition_cycles
7f3c2000024bd1 / 0301a604 = 2: boiler hours_burner_on
7f3c2000026847 / 03010000 = 4: boiler dhw_flowmeter
7f3c2000026910 / 03010f02 = 88: boiler EWT_temp
7f3c2000027547 / 03011e00 = 14: boiler boiler_pressure
7f3c200002c04b / 020101 = 255: boiler boiler_status
7f3c200002c428 / 020101 = 9: boiler boiler_type
7f3c200004d1400e11 / 0303ed00 = 612: boiler config_version_counter
37fe20200c008101008201008301008401 = 9: energymgr z1_heat_temp_range
37fe20200c0120010220010520010b2001 = 9: energymgr heating_status
37fe20201060713403607234036073340360743403 = 9: energymgr z1_heat_water_max_temp
37fe20201061725e0161735e0161745e0161755e01 = 9: energymgr z2_heat_water_min_temp
7ffe20200462716400 = 2: energymgr z1_day_temp
37fe2020106273be006274be006275be006276be00 = 9: energymgr z3_day_temp
37fe202010647174ff647200006473000064740000 = 9: energymgr z1_heat_offset
37fe20201065729001657390016574900165759001 = 9: energymgr z2_heat_setpoint_temp_set
37fe2020106a7296006a7396006a7496006a759600 = 9: energymgr z2_heat_slope
37fe20200cc07901c07a01c07b01c07c01 = 9: energymgr z1_heat_therm_type_selection
37fe20200cc27a0ac27b0ac27c0ac27d0a = 9: energymgr z2_heat_room_temp_infl
7f3c2000046810c04b / 04032b0201 = 37
7f3c200004c2046547 / 0403020000 = 7
7f3c20000446d14cd1 / 05030000b800 = 2
7f3c20000442d943d9 / 0503596b3100 = 1
7f3c20000444d945d9 / 0503e93e0300 = 2