Log flooding with "Unexpected Payload from Device" messages

[lpwevers]

Hi,

I installed tuya-local and added two light bulbs. They're the LSC ones from the local Action. Though they work fine using local-tuya, my HA log is flooding with "Unexpected Payload from Device" messages. For each light bulb I get one almost every minute:

2023-03-10 08:10:06.427 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_buiten_local error reading: Unexpected Payload from Device
2023-03-10 08:11:07.677 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_buiten_local error reading: Unexpected Payload from Device
2023-03-10 08:11:07.765 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_local error reading: Unexpected Payload from Device
2023-03-10 08:12:08.930 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_buiten_local error reading: Unexpected Payload from Device
2023-03-10 08:12:09.056 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_local error reading: Unexpected Payload from Device
2023-03-10 08:13:10.181 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_buiten_local error reading: Unexpected Payload from Device
2023-03-10 08:13:10.331 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_local error reading: Unexpected Payload from Device
2023-03-10 08:14:11.432 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_buiten_local error reading: Unexpected Payload from Device
2023-03-10 08:14:11.612 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_local error reading: Unexpected Payload from Device
2023-03-10 08:16:18.975 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_buiten_local error reading: Unexpected Payload from Device
2023-03-10 08:16:19.172 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_local error reading: Unexpected Payload from Device
2023-03-10 08:17:20.250 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_buiten_local error reading: Unexpected Payload from Device
2023-03-10 08:17:20.430 WARNING (MainThread) [custom_components.tuya_local.device] LI_Schuur_local error reading: Unexpected Payload from Device

Is this normal behaviour? Or is there anything I can do to get rid of these messages?

[make-all]

This is a protocol level error, I expect one of the device configuration values is incorrect - either the local key, or the protocol version. There are cases where "auto" will not pick up the right protocol version, mostly these devices are 3.2 protocol devices, but may be 3.4 or 3.5 also, so try setting the protocol version manually.

[lpwevers]

Thanks, I tried setting the protocol version manually. I can choose either 3.2 or 3.3; the other versions will not let me connect to the device at all. But either version of the protocol does not make a difference in the log messages generated.

The devices do work, so I assume the local key to be correct or they wouldn't work at all. Maybe these devices are not fully supported yet?

[make-all]

It seems a similar issue was reported to the upstream library for LSC bulbs: jasonacox/tinytuya#99
There are frequent reports in there of "null response" in the payload, which I think is what is behind the "Unexpected payload" exception in the API function this integration uses.

[make-all]

I guess if everything else is working and you just want to suppress these from the logs, you can add the following to config/configuration.yaml (or modify the logger section if there is already one there):

logger:
  default: warning
  logs:
    custom_components.tuya_local.device: error

[lpwevers]

Thanks for that. I'll see if fixing the issue in the upstream library for LSC will eventually solve my issue as well. I do have the exact same bulbs.

For now I'm keeping my logs clean with your suggestion for the change in configuration.yaml

Kind regards,
Louis

[make-all]

It seems from the upstream bug report, that someone has identified this problem as starting after the devices have been blocked from the internet for a few days. Are you blocking the devices from reaching the cloud?

[lpwevers]

No, I'm not. To be more precise I use them both local and using the cloud services. Sometimes local doesn't work immediately so in case that happens I try using the cloud.