Connection to device lost from time to time

[dooblem]

Hello,

First thanks for providing this great integration ! I'm using it with the last HA version.

I'm using it to manage a Feyree EV Charger (goodcell_ev_charger.yaml).

Every few days, it seems that the device stops responding to queries (device unavailable in HA). And when polling the device using tinytuya lib directly, I get an error saying to check the local key. Then I just hard reboot the device to make it work again.

I've seen in the readme that polling the device too often can cause problem to some devices. And when enabling the debug log in HA, I see there is a lots of communication between the device and HA (maybe 1 packet every second)

A tcpdump is also showing lot of traffic.

Here is some extract of the log, filtering on what I guess is decoded packets sent/received (I can provide the raw verbose log if needed).

$ tail -f home-assistant.log | grep -e 'decoded results' -e 'building command' -e heartbeat

2025-03-19 09:05:21.345 DEBUG (SyncWorker_8) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371521,"data":{"dps":{"105":0}}}'
2025-03-19 09:05:21.452 DEBUG (SyncWorker_6) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:21.463 DEBUG (SyncWorker_6) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:21.961 DEBUG (SyncWorker_10) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371521,"data":{"dps":{"106":0}}}'
2025-03-19 09:05:22.068 DEBUG (SyncWorker_7) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:22.080 DEBUG (SyncWorker_7) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:22.320 DEBUG (SyncWorker_9) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371522,"data":{"dps":{"107":0}}}'
2025-03-19 09:05:22.427 DEBUG (SyncWorker_0) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:22.438 DEBUG (SyncWorker_0) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:25.402 DEBUG (SyncWorker_3) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371525,"data":{"dps":{"105":0}}}'
2025-03-19 09:05:25.509 DEBUG (SyncWorker_12) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:25.521 DEBUG (SyncWorker_12) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:26.021 DEBUG (SyncWorker_2) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371525,"data":{"dps":{"106":0}}}'
2025-03-19 09:05:26.127 DEBUG (SyncWorker_5) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:26.138 DEBUG (SyncWorker_5) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:26.508 DEBUG (SyncWorker_11) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371526,"data":{"dps":{"107":0}}}'
2025-03-19 09:05:26.614 DEBUG (SyncWorker_13) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:26.626 DEBUG (SyncWorker_13) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:29.582 DEBUG (SyncWorker_8) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371529,"data":{"dps":{"102":2331}}}'
2025-03-19 09:05:29.686 DEBUG (SyncWorker_6) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:29.697 DEBUG (SyncWorker_6) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:29.700 DEBUG (SyncWorker_10) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371529,"data":{"dps":{"105":0}}}'
2025-03-19 09:05:29.805 DEBUG (SyncWorker_7) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:29.817 DEBUG (SyncWorker_7) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:29.921 DEBUG (SyncWorker_0) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:29.932 DEBUG (SyncWorker_0) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:29.962 DEBUG (SyncWorker_4) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371529,"data":{"dps":{"106":0}}}'
2025-03-19 09:05:30.069 DEBUG (SyncWorker_1) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:30.080 DEBUG (SyncWorker_1) [tinytuya.core.Device] heartbeat received data=None
2025-03-19 09:05:30.563 DEBUG (SyncWorker_3) [tinytuya.core.XenonDevice] decoded results='{"protocol":4,"t":1742371530,"data":{"dps":{"107":0}}}'
2025-03-19 09:05:30.670 DEBUG (SyncWorker_12) [tinytuya.core.XenonDevice] building command 9 payload=b'{"gwId":"bfd4a0e3d70544b62asfgj","devId":"bfd4a0e3d70544b62asfgj"}'
2025-03-19 09:05:30.682 DEBUG (SyncWorker_12) [tinytuya.core.Device] heartbeat received data=None

How is it working ?

I red on the forum that tuya-local connects only when discovery broadcast messages are sent by the device ?

I see that dps are not received all at once but there are separate packets for different metrics/dps. Is it the device sending them separately by itself, or us requesting them ?

Is it possible/advised to lower the polling, or the rate at which we respond to the device ?

Thanks in advance,
Marc

[make-all]

The issue described is likely fixed by the latest tinytuya, integrated into tuya-local 2025.5.0, see #3050