brutella / hkknx-public

hkknx is a HomeKit KNX bridge for KNX.
https://hochgatterer.me/hkknx
99 stars 6 forks source link

Thermostat - issue reading value #232

Closed thorsten-gehrig closed 1 year ago

thorsten-gehrig commented 1 year ago

Hi I see a bug with receiving the "set to temperature" on hkknx. I´m havving the latest version 2.4.2-b2 For my thermostat i have 4/1/123 as targert-temperature. I have this configured for Write/read/inialiize.

My issue: the "set to temperature" is received on the bus as "response" but not "write". Any value send to the bus as "write" is processed - but on my scenario the most updates are received as "response". hkknx does only take values from "write" - while "response" on 4/1/123 should also be update the value, isnt?

The log file clearly identfies KNX Type as WRITE and RESPONSE - but only the WRITE does update the value - not the response...

Best Thorsten

brutella commented 1 year ago

That's an interesting behaviour. I thought that response telegrams are only triggered by read telegrams.

Am I wrong to expect that when the set temperature is updated, the new value is sent to a group address via a write telegram?

thorsten-gehrig commented 1 year ago

Usually they should be triggered by read telegrams - but this should also update the value, isnt? You are right that they SHOULD be updated via a write telegram... but in some use cases those telegram can not be submitted or get lost. Anyhow - I have fixed my use case so I´m fine (EDOMI now send WRITE instead of RESPONSE) Best Thorsten