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
Currently we just fire the knx_event for incoming telegrams, as stated in the documentation.
We could
fire on outgoing telegrams too, not only on incoming
add a parameter "direction" for incoming/outgoing
add a parameter "source" for IA (eg. to identify which wall switch was used)
add a parameter "type" for write or response (maybe also read)
I'm still not very convinced about using the knx_event at all since we can't really decode the payload and dealing with raw payloads should not be a user-facing task in HA (besides maybe for DPT 1/2/3).
The text was updated successfully, but these errors were encountered:
There are some requests about updating the HA knx_event.
Eg. home-assistant/core#43256
Currently we just fire the
knx_event
for incoming telegrams, as stated in the documentation.We could
I'm still not very convinced about using the
knx_event
at all since we can't really decode the payload and dealing with raw payloads should not be a user-facing task in HA (besides maybe for DPT 1/2/3).The text was updated successfully, but these errors were encountered: