KNX - Dim light - Payload invalid / CouldNotParseTelegram

Hi,
I’m seeing a lot of log errors in my setup around processing dimmer status telegrams. it seems that my knx setup is sending 1 Byte status DPT 5 (1byte_unsigned 0-255) while the HA knx light integration is expecting DPT5.001 which is percent (0-100).

Is there a way to specify that in the yaml configuration?

Logger: xknx.log
Source: /usr/local/lib/python3.9/site-packages/xknx/remote_value/remote_value.py:179
First occurred: 5:56:59 PM (52 occurrences)
Last logged: 5:57:44 PM

Can not process <Telegram direction=“Incoming” source_address=“1.0.145” destination_address=“3/2/128” payload="<GroupValueResponse value="" />" /> for Parents room hall spot light - State: <CouldNotParseTelegram description=“Payload invalid” payload=""/>
Can not process <Telegram direction=“Incoming” source_address=“1.0.121” destination_address=“3/2/128” payload="<GroupValueResponse value="" />" /> for Parents room hall spot light - State: <CouldNotParseTelegram description=“Payload invalid” payload=""/>
Can not process <Telegram direction=“Incoming” source_address=“1.0.145” destination_address=“3/2/151” payload="<GroupValueResponse value="" />" /> for Parents room tv spot light - State: <CouldNotParseTelegram description=“Payload invalid” payload=""/>
Can not process <Telegram direction=“Incoming” source_address=“1.0.145” destination_address=“3/2/151” payload="<GroupValueWrite value="" />" /> for Parents room tv spot light - State: <CouldNotParseTelegram description=“Payload invalid” payload=""/>
Can not process <Telegram direction=“Incoming” source_address=“1.0.145” destination_address=“3/2/151” payload="<GroupValueWrite value="" />" /> for Parents room tv spot light - State: <CouldNotParseTelegram description=“Payload invalid” payload=""/>

Is there any way to enale HA to parse it correctly?

Thanks,
Efi

This is essentially the same.

The error message looks a bit awkward - there is no payload listed :thinking:
What actuator is this coming from?
Can you do a ETS or Wireshark log of such traffic please?
And maybe enable debug logging for xknx.knx see KNX - Home Assistant (last paragraph)

Are you sure you didn’t use a DPT 3 GA?