I have the following KNX configuration
knx:
light:
- name: Schlafen Bett
address:
- 5/2/22 # Beleuchtung/Obergeschoss/Schlafen Bett
state_address:
- 5/5/222 # Beleuchtung/Status/Schlafen Bett DPT1
brightness_address:
- 5/3/222 # Beleuchtung/Helligkeitswerte/Schlafen Bett
brightness_state_address:
- 5/5/223 # Beleuchtung/Status/Schlafen Bett DPT5
rgbw_address:
- 5/3/223 # Beleuchtung/Helligkeitswerte/Schlafen Bett
rgbw_state_address:
- 5/5/224 # Beleuchtung/Status/Schlafen Bett DPTColorRGBW
which causes this warning in the protocol:
Logger: xknx.ga_dpt
Quelle: runner.py:154
Erstmals aufgetreten: 18:28:17 (6 Vorkommnisse)
Zuletzt protokolliert: 20:28:17DPT decoding error. Telegram from 1.2.29 to 5/5/222 with payload can’t be decoded by DPTColorRGBW: <CouldNotParseTelegram description=“Invalid payload type for DPTColorRGBW” expected_type=“DPTArray” payload=“”/>
DPT decoding error. Telegram from 1.2.29 to 5/5/223 with payload can’t be decoded by DPTColorRGB: <CouldNotParseTelegram description=“Invalid payload length for DPTColorRGB” expected_length=“3” payload=“”/>
I don’t understand why it would expect a 6 byte value on the state_address (5/5/222), in my opinion this would be the binary state off | on of the light as is with all other (non-RGBW) light entities. this is the only RGBW one i have installed.
there is after all a separate gbw_state_address for this.
also, brightness_state_address is being set to the 1 byte brightness value by the RGBW LED actor. why HASS expects a RGB (DPT 232.600?) value here instead of a brightness is beyond my comprehension.
however, I did not study the code yet.
i would be very grateful for some education.
!