Closed mivola closed 8 months ago
Hi @mivola,
Would you please share the configuration CSV file that you're using? I would like to check the ebus data type and divider configured for the message OtShutdownLimit. If DPT-9 (2 byte float) works the message should probably be encoded as SIR with divisor 10.
Best Christian
desiredtemp is defined as UCH without divisor. as such, it is mapped to DPT 5.010 according to the docs
desiredtemp is defined as UCH without divisor. as such, it is mapped to DPT 5.010 according to the docs
Thanks a lot for the clarification and the link to the doc. Just for my (and others) reference in the future: here is the missing link between desiredtemp and the UCH type: https://github.com/john30/ebusd-configuration/blob/4675cd03b2763867cf74bd12426b1990bebb6204/ebusd-2.1.x/de/_templates.csv#L13
Description
in my knx.cfg I want to include OtShutdownLimit. I tried different associations (
mc/OtShutdownLimit/0
,mc/OtShutdownLimit/desiredtemp
) and datatypes (9, 12) but it doesnt properly work.ebusctl write -c mc OtShutdownLimit 22
, no update is sent to the knx busso I wonder how I can properly use this field or if there is a bug in ebusd or the config?
the ebusd is started in docker with these env vars:
Actual behavior
Expected behavior
ebusd version
23.2
ebusd arguments
see description
Operating system
other
CPU architecture
x64
Dockerized
latest
Hardware interface
other
Related integration
TCP (cmdline client like ebusctl or netcat), MQTT generic, KNX
Logs
n/a