You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sadly I found out that the native KNX IP broadcasting implementation KNXJS requires to know the DPT of each group address upfront.
The current implementation of homebridge-knx doesn't do that, there is a lot of "runtime guessing" involved, which also currently prohibits the use of several DPTs that are available for a long time.
E.G. all received two-byte telegrams are interpreted as DPT9 floats, but could also be 16bit signed DPT8 or unsigned DPT7 integers, which of course reqire different parsing.
It however works sufficiently well if you only have DPT1 (1-bit) devices, such as light switches.
In all other cases it won't work right now.
Sorry for that, I will get back to that later again.
The text was updated successfully, but these errors were encountered:
Sadly I found out that the native KNX IP broadcasting implementation KNXJS requires to know the DPT of each group address upfront.
The current implementation of homebridge-knx doesn't do that, there is a lot of "runtime guessing" involved, which also currently prohibits the use of several DPTs that are available for a long time.
E.G. all received two-byte telegrams are interpreted as DPT9 floats, but could also be 16bit signed DPT8 or unsigned DPT7 integers, which of course reqire different parsing.
It however works sufficiently well if you only have DPT1 (1-bit) devices, such as light switches.
In all other cases it won't work right now.
Sorry for that, I will get back to that later again.
The text was updated successfully, but these errors were encountered: