Since latest update get all the time disconnected waiting for discovery warnings

[smarthomefamilyverrips]

The problem

since the latest update I get many warnings in my logs for my devices being disconnected waiting for discovery while they are available

This error originated from a custom integration.

Logger: custom_components.localtuya.common Source: custom_components/localtuya/pytuya/init.py:677 Integration: LocalTuya (documentation, issues) First occurred: 08:21:15 (8 occurrences) Last logged: 08:21:15

[132...4ed] Disconnected - waiting for discovery broadcast [132...04b] Disconnected - waiting for discovery broadcast [132...94f] Disconnected - waiting for discovery broadcast [482...820] Disconnected - waiting for discovery broadcast [482...4a3] Disconnected - waiting for discovery broadcast -->

Environment

HA OS - Localtuya version: 5.1.0 - Home Assistant Core version: 2023.3.1 - [] Does the device work using the Home Assistant Tuya Cloud component ?

• [] Does the device work using the Tinytuya (https://github.com/jasonacox/tinytuya) command line tool ?
• [x] Was the device working with earlier versions of localtuya ? Which one? 5.0.0
• [] Are you using the Tuya/SmartLife App in parallel ?

Steps to reproduce

1.

DP dump

Provide Home Assistant traceback/logs

put your log output between these markers

Additional information

[Mangomc]

Same here and Also Command 9 timed out waiting for sequence number -100

[woempiej]

I've got the same errors as smarthomefamilyverrips

[Spiffo]

Same here:

2023-03-09 16:20:57.819 WARNING (MainThread) [custom_components.localtuya.common] [bf4...sph] Disconnected - waiting for discovery broadcast 2023-03-09 16:21:02.767 WARNING (MainThread) [custom_components.localtuya.pytuya] [bf4...sph] Command 9 timed out waiting for sequence number -100 2023-03-09 16:21:07.659 WARNING (MainThread) [custom_components.localtuya.pytuya] [bf4...sph] Command 3 timed out waiting for sequence number -102 2023-03-09 16:21:12.674 WARNING (MainThread) [custom_components.localtuya.pytuya] [bf4...sph] Command 3 timed out waiting for sequence number -102 2023-03-09 16:21:17.705 WARNING (MainThread) [custom_components.localtuya.pytuya] [bf4...sph] Command 3 timed out waiting for sequence number -102 2023-03-09 16:21:22.712 WARNING (MainThread) [custom_components.localtuya.pytuya] [bf4...sph] Command 3 timed out waiting for sequence number -102 2023-03-09 16:21:22.756 ERROR (MainThread) [homeassistant] Error doing job: Fatal error: protocol.data_received() call failed. Traceback (most recent call last): File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 876, in _read_ready__data_received self._protocol.data_received(data) File "/config/custom_components/localtuya/pytuya/__init__.py", line 668, in data_received self.dispatcher.add_data(data) File "/config/custom_components/localtuya/pytuya/__init__.py", line 472, in add_data msg = unpack_message( File "/config/custom_components/localtuya/pytuya/__init__.py", line 304, in unpack_message raise DecodeError("Not enough data to unpack header") custom_components.localtuya.pytuya.DecodeError: Not enough data to unpack header

[jmmateos]

Same error as smarthomefamilyverrips, but only with two version 3.4 devices. The other devices versions (3.3 and 3.4) work correctly.

[walberjunior]

Same here

2023-03-14 07:53:40.299 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 9 timed out waiting for sequence number -100
2023-03-14 07:53:40.306 WARNING (MainThread) [custom_components.localtuya.common] [eb0...3xu] Disconnected - waiting for discovery broadcast
2023-03-14 08:44:04.596 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 9 timed out waiting for sequence number -100
2023-03-14 08:44:04.604 WARNING (MainThread) [custom_components.localtuya.common] [eb0...3xu] Disconnected - waiting for discovery broadcast
2023-03-14 08:45:20.179 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 9 timed out waiting for sequence number -100
2023-03-14 08:45:20.187 WARNING (MainThread) [custom_components.localtuya.common] [eb0...3xu] Disconnected - waiting for discovery broadcast
2023-03-14 08:52:38.236 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 9 timed out waiting for sequence number -100
2023-03-14 08:52:38.242 WARNING (MainThread) [custom_components.localtuya.common] [eb0...3xu] Disconnected - waiting for discovery broadcast
2023-03-14 09:03:19.899 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 9 timed out waiting for sequence number -100
2023-03-14 09:03:19.906 WARNING (MainThread) [custom_components.localtuya.common] [eb0...3xu] Disconnected - waiting for discovery broadcast
2023-03-14 09:05:11.292 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 9 timed out waiting for sequence number -100
2023-03-14 09:05:11.299 WARNING (MainThread) [custom_components.localtuya.common] [eb0...3xu] Disconnected - waiting for discovery broadcast
2023-03-14 09:10:01.299 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 9 timed out waiting for sequence number -100
2023-03-14 09:10:01.307 WARNING (MainThread) [custom_components.localtuya.common] [eb0...3xu] Disconnected - waiting for discovery broadcast
2023-03-14 09:10:19.491 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 9 timed out waiting for sequence number -100
2023-03-14 09:10:19.497 WARNING (MainThread) [custom_components.localtuya.common] [eb0...3xu] Disconnected - waiting for discovery broadcast
2023-03-14 09:10:24.363 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 7 timed out waiting for sequence number 3
2023-03-14 09:10:24.372 ERROR (MainThread) [custom_components.localtuya.common] [eb0...3xu] Failed to set DPs {1: True}
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/asyncio/locks.py", line 390, in acquire
    await fut
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
    return fut.result()
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/localtuya/common.py", line 333, in set_dps
    await self._interface.set_dps(states)
  File "/config/custom_components/localtuya/pytuya/__init__.py", line 846, in set_dps
    return await self.exchange(CONTROL, dps)
  File "/config/custom_components/localtuya/pytuya/__init__.py", line 769, in exchange
    msg = await self.dispatcher.wait_for(seqno, payload.cmd)
  File "/config/custom_components/localtuya/pytuya/__init__.py", line 450, in wait_for
    await asyncio.wait_for(self.listeners[seqno].acquire(), timeout=timeout)
  File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
    raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError
2023-03-14 09:11:31.255 WARNING (MainThread) [custom_components.localtuya.pytuya] [eb0...3xu] Command 9 timed out waiting for sequence number -100
2023-03-14 09:11:31.262 WARNING (MainThread) [custom_components.localtuya.common] [eb0...3xu] Disconnected - waiting for discovery broadcast

[Andes1984]

Same here:

`Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: custom_components.localtuya.common Source: custom_components/localtuya/pytuya/init.py:677 Integration: LocalTuya integration (documentation, issues) First occurred: 17:21:17 (495 occurrences) Last logged: 23:19:48

[604...a9f] Disconnected - waiting for discovery broadcast [881...491] Disconnected - waiting for discovery broadcast [881...27b] Disconnected - waiting for discovery broadcast [881...4c2] Disconnected - waiting for discovery broadcast [881...7e3] Disconnected - waiting for discovery broadcast `

[Anj-0110]

Same here! I am knew to the forums, how long before there are suggestions on how to fix?

[eba...dwv] Disconnected - waiting for discovery broadcast 08:18:57 – (WARNING) LocalTuya (custom integration) - message first occurred at March 14, 2023 at 07:54:25 and shows up 18949 times

[Verardim]

Hi, I had a similar problem. I updated HA to 2023.3.4 and concurrently LocalTuya to 5.1.1. From then on (despite all the listed attempts, it never got back to normal functions). Immediately after reboot all the covers up controls got greyed out. I tried several workarounds: rebooting HA, reconfiguring cover devices from Localtuya, reinstalling Localtuya, downgrading Localtuya first to 5.0.0 then to 4.1.1, downgrading either HA to 2023.3.3 and LocalTuya to 5.0.0. The up controls kept being greyed out and after some minutes all the cover entities became unavailable. Here is the latest logs with HA at 2023.3.3 and LocalTuya to 5.0.0: 2023-03-17 14:56:29.552 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2023-03-17 15:00:32.467 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry localtuya for cover 2023-03-17 15:00:33.020 WARNING (MainThread) [custom_components.localtuya.common] [721...261] Disconnected - waiting for discovery broadcast 2023-03-17 15:00:34.732 WARNING (MainThread) [custom_components.localtuya.common] [721...261] Disconnected - waiting for discovery broadcast 2023-03-17 15:00:39.737 WARNING (MainThread) [custom_components.localtuya.pytuya] [721...261] Command 10 timed out waiting for sequence number 1 2023-03-17 15:00:39.739 ERROR (MainThread) [custom_components.localtuya.common] [721...261] Initial state update failed, giving up: TimeoutError() 2023-03-17 15:01:19.116 WARNING (MainThread) [custom_components.localtuya.common] [721...261] Disconnected - waiting for discovery broadcast 2023-03-17 15:02:19.118 WARNING (MainThread) [custom_components.localtuya.common] [721...261] Disconnected - waiting for discovery broadcast 2023-03-17 15:03:23.928 WARNING (MainThread) [custom_components.localtuya.pytuya] [721...b19] Command 10 timed out waiting for sequence number 1 2023-03-17 15:03:23.937 ERROR (MainThread) [custom_components.localtuya.pytuya] [721...b19] Failed to get status: File "/config/custom_components/localtuya/pytuya/init.py", line 863, in detect_available_dps File "/config/custom_components/localtuya/pytuya/init.py", line 795, in status File "/config/custom_components/localtuya/pytuya/init.py", line 769, in exchange File "/config/custom_components/localtuya/pytuya/init.py", line 450, in wait_for 2023-03-17 15:04:26.482 WARNING (MainThread) [custom_components.localtuya.pytuya] [721...261] Command 10 timed out waiting for sequence number 1 2023-03-17 15:04:26.485 ERROR (MainThread) [custom_components.localtuya.pytuya] [721...261] Failed to get status: File "/config/custom_components/localtuya/pytuya/init.py", line 863, in detect_available_dps File "/config/custom_components/localtuya/pytuya/init.py", line 795, in status File "/config/custom_components/localtuya/pytuya/init.py", line 769, in exchange File "/config/custom_components/localtuya/pytuya/init.py", line 450, in wait_for [/share/Domotica/Homeassistant] # grep tuya home-assistant.log.1 > tuya_log.1 [/share/Domotica/Homeassistant] # more tuya_log.1 2023-03-17 14:56:29.552 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2023-03-17 15:00:32.467 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry localtuya for cover 2023-03-17 15:00:33.020 WARNING (MainThread) [custom_components.localtuya.common] [721...261] Disconnected - waiting for discovery broadcast 2023-03-17 15:00:34.732 WARNING (MainThread) [custom_components.localtuya.common] [721...261] Disconnected - waiting for discovery broadcast 2023-03-17 15:00:39.737 WARNING (MainThread) [custom_components.localtuya.pytuya] [721...261] Command 10 timed out waiting for sequence number 1 2023-03-17 15:00:39.739 ERROR (MainThread) [custom_components.localtuya.common] [721...261] Initial state update failed, giving up: TimeoutError() 2023-03-17 15:01:19.116 WARNING (MainThread) [custom_components.localtuya.common] [721...261] Disconnected - waiting for discovery broadcast 2023-03-17 15:02:19.118 WARNING (MainThread) [custom_components.localtuya.common] [721...261] Disconnected - waiting for discovery broadcast 2023-03-17 15:03:23.928 WARNING (MainThread) [custom_components.localtuya.pytuya] [721...b19] Command 10 timed out waiting for sequence number 1 2023-03-17 15:03:23.937 ERROR (MainThread) [custom_components.localtuya.pytuya] [721...b19] Failed to get status: File "/config/custom_components/localtuya/pytuya/init.py", line 863, in detect_available_dps File "/config/custom_components/localtuya/pytuya/init.py", line 795, in status File "/config/custom_components/localtuya/pytuya/init.py", line 769, in exchange File "/config/custom_components/localtuya/pytuya/init.py", line 450, in wait_for 2023-03-17 15:04:26.482 WARNING (MainThread) [custom_components.localtuya.pytuya] [721...261] Command 10 timed out waiting for sequence number 1 2023-03-17 15:04:26.485 ERROR (MainThread) [custom_components.localtuya.pytuya] [721...261] Failed to get status: File "/config/custom_components/localtuya/pytuya/init.py", line 863, in detect_available_dps File "/config/custom_components/localtuya/pytuya/init.py", line 795, in status File "/config/custom_components/localtuya/pytuya/init.py", line 769, in exchange File "/config/custom_components/localtuya/pytuya/init.py", line 450, in wait_for

[Anj-0110]

Along with the above, my localtuya lights randomly turn themselves on. How do I figure out what triggered the "service light.turn on"? When I command a device my user name is listed. Shown below, something in HA commanded these to turn on, how do I dig further into this? Or, is this a result of the above problems??

Mudd Room turned on triggered by service light.turn_on 08:03:03 - 7 minutes ago Galley 11 turned on triggered by service light.turn_on 08:03:03 - 7 minutes ago Galley 9 turned on triggered by service light.turn_on 08:03:03 - 7 minutes ago Galley 12 turned on triggered by service light.turn_on 08:03:03 - 7 minutes ago Galley 13 turned on triggered by service light.turn_on 08:03:03 - 7 minutes ago Galley 14 turned on triggered by service light.turn_on 08:03:03 - 7 minutes ago

[woempiej]

@Anj-0110

I don't think it is related to this problem. I don't have this scenario. Did you check your automations? All the light turned on at the same time.

[Anj-0110]

I have disabled nearly all the automations. And, when an automation is triggered it tells me in the log what automation it was triggered by. From what I can tell, being new to all this, is that LOCALTUYA is losing connection therefore turning the lights on when it reconnects. When the lights turn on within the system they are all the same color and brightness. Below is just one of the entries from the log. Also, when I reload localtuya from the integrations page I can duplicate the lights.on scenerio. How do I toubleshoot this further?? I do have a zigbee stick that is plugged into a usb extension cable on my Pi-4 as I had read this can mess with the wifi signal. What else can I try???

This error originated from a custom integration.

Logger: custom_components.localtuya.common Source: custom_components/localtuya/pytuya/init.py:677 Integration: LocalTuya (documentation, issues) First occurred: 07:44:31 (1084 occurrences) Last logged: 08:13:01

[eb2...qe2] Disconnected - waiting for discovery broadcast [ebb...3xl] Disconnected - waiting for discovery broadcast [eba...dwv] Disconnected - waiting for discovery broadcast [eb9...gtc] Disconnected - waiting for discovery broadcast

[woempiej]

Look here https://community.home-assistant.io/t/lights-turning-on-for-unknown-reason/375494/17

[dragonjon]

Same error as smarthomefamilyverrips in version 5.1.0 with some devices (but not all) with 3.1 and 3.3 firmware

[TimMayle]

Having also this error when I shut down my light (which will be often). Firmware 3.3. integration 5.1.0

[Anj-0110]

I am still getting mulitple issues recorded in the log...

Some of the log entries make sense and some do not. Nonetheless, it seems there is an issue with LocalTuya with no solutions.

Is my wifi signal dropping the connection to the tuya lights? It appears when the lights connect, there is something in the code that tells the light to come on. However, when the light turns on, it is random lights?? In the smartlife app, I have checked the memory state upon power failure but the settings do not match the light output, they turn on at 56% to a light red color. Something has to be commanding this but do not know where to go and don't understand yaml even if I did read it. When I restart HA, all the lights turn on to 56% to a light red color. I have checked multiple other issues but cannot seem to find a fix to this??

This is super frustrating! Any suggestions??

Below are some entries from the log.

This error originated from a custom integration.

Logger: custom_components.localtuya.common Source: custom_components/localtuya/pytuya/init.py:677 Integration: LocalTuya (documentation, issues) First occurred: 11:31:58 (751 occurrences) Last logged: 12:34:20

[240...b3b] Disconnected - waiting for discovery broadcast [ebf...b3p] Disconnected - waiting for discovery broadcast [eb4...28n] Disconnected - waiting for discovery broadcast [eb1...jfh] Disconnected - waiting for discovery broadcast [ebd...gfl] Disconnected - waiting for discovery broadcast

--

This error originated from a custom integration.

Logger: custom_components.localtuya.pytuya Source: custom_components/localtuya/pytuya/init.py:795 Integration: LocalTuya (documentation, issues) First occurred: 11:32:03 (29 occurrences) Last logged: 12:39:51

[eb2...n96] Command 3 timed out waiting for sequence number -102 [eb1...jfh] Command 10 timed out waiting for sequence number 1 [eb3...yxb] Command 3 timed out waiting for sequence number -102 [ebd...gfl] Command 3 timed out waiting for sequence number -102 [ebd...gfl] Command 16 timed out waiting for sequence number 2

--

This error originated from a custom integration.

Logger: custom_components.localtuya.common Source: custom_components/localtuya/pytuya/init.py:259 Integration: LocalTuya (documentation, issues) First occurred: 11:32:14 (11 occurrences) Last logged: 12:19:50

[240...13e] Initial state update failed, giving up: TimeoutError() [ebf...b3p] Initial state update failed, giving up: TimeoutError() [eb4...28n] Initial state update failed, giving up: TimeoutError() [eb1...jfh] Initial state update failed, giving up: TimeoutError() [ebd...gfl] Initial state update failed, giving up: TimeoutError()

[Thrasher2020]

Same here, thankfully I have migrated away from Tuya and only have 1 bulb left (soon to be replaced when the shipment arrives!)

[Anj-0110]

Same here, thankfully I have migrated away from Tuya and only have 1 bulb left (soon to be replaced when the shipment arrives!)

Meaning you have changed your devices or is there another way to communicate with TUYA devices other than Localtuya??

[cjsmns]

I'm also having the same issue.

This error originated from a custom integration.

Logger: custom_components.localtuya.common
Source: custom_components/localtuya/pytuya/__init__.py:677
Integration: LocalTuya (documentation, issues)
First occurred: 1:54:51 PM (86 occurrences)
Last logged: 6:05:16 PM

[eb7...oat] Disconnected - waiting for discovery broadcast
[654...8d8] Disconnected - waiting for discovery broadcast
[763...61e] Disconnected - waiting for discovery broadcast
[eb9...8g8] Disconnected - waiting for discovery broadcast
[ebb...zgo] Disconnected - waiting for discovery broadcast

Actually, before this one, there are a bunch of other errors and warnings.

This error originated from a custom integration.

Logger: custom_components.localtuya.common
Source: custom_components/localtuya/pytuya/__init__.py:259
Integration: LocalTuya (documentation, issues)
First occurred: 3:10:12 PM (4 occurrences)
Last logged: 6:05:16 PM

[eb7...oat] Initial state update failed, giving up: TimeoutError()

This error originated from a custom integration.

Logger: custom_components.localtuya.pytuya
Source: custom_components/localtuya/pytuya/__init__.py:795
Integration: LocalTuya (documentation, issues)
First occurred: 3:10:12 PM (4 occurrences)
Last logged: 6:05:16 PM

[eb7...oat] Command 10 timed out waiting for sequence number 1

This error originated from a custom integration.

Logger: custom_components.localtuya.pytuya
Source: custom_components/localtuya/pytuya/__init__.py:647
Integration: LocalTuya (documentation, issues)
First occurred: 1:54:51 PM (78 occurrences)
Last logged: 6:04:56 PM

[eb7...oat] Command 9 timed out waiting for sequence number -100

[ejpenney]

I'm seeing this issue as well. Started for me about a week ago. Reloading the integration, or restarting Home Assistant doesn't resolve this. It seems I need to unplug (or otherwise remove power, then re-apply) each device that disconnects. I'm not sure what environmental factors causes LocalTuya/the device to get into this state.

This error originated from a custom integration.

Logger: custom_components.localtuya.common
Source: custom_components/localtuya/pytuya/__init__.py:677
Integration: LocalTuya (documentation, issues)
First occurred: April 9, 2023 at 3:01:11 AM (268 occurrences)
Last logged: 10:11:26 AM

[273...b46] Disconnected - waiting for discovery broadcast
[280...95c] Disconnected - waiting for discovery broadcast
[040...550] Disconnected - waiting for discovery broadcast
[470...68d] Disconnected - waiting for discovery broadcast
[273...da7] Disconnected - waiting for discovery broadcast

[Thrasher2020]

Last Tuya bulb back in the box - since the last update nothing has been reliable sadly. Maybe if it manages to become as stable as it used to I will dig them out again, but for now I am switching to Zigbee instead of WiFi.

[woempiej]

My WiFi Yeelight bulbs are very reliable and local only. It is a Tuya issue...

I *had 3 devices (2x LSC LED Strip and a LSC E14 RGBW bulb) Since the update I saw errors in my logs (This one: "Disconnected - waiting for discovery broadcast" and more). I removed the E14 bulb out of my install and the errors are gone.

PS: I didn't re-add the E14 bulb ;)

[lion6000]

Same problem. And spamming me

Logger: custom_components.localtuya.common Source: custom_components/localtuya/pytuya/init.py:677 Integration: LocalTuya integration (documentation, issues) First occurred: 03:51:04 (233 occurrences) Last logged: 13:51:37 [bf8...hdz] Disconnected - waiting for discovery broadcast [bf0...vkl] Disconnected - waiting for discovery broadcast [bff...nnq] Disconnected - waiting for discovery broadcast [bf3...sb7] Disconnected - waiting for discovery broadcast

[ALERTua]

I noticed that this happens after the devices lose and reestablish wifi connection. After this, Tuya works, but localtuya stops working.

[mickandkez]

I have been able to consistently replicate the issue. When the device becomes unavailable, I use my phone/computer to for example a light, adjust the brightness in cloud based Tuya (HA or Tuya/Smartlife APP) and instantly (like sub 1 second delay) it comes back online in local Tuya for about 10 seconds then becomes unavailable. If I continue do keep adjusting brightness or turning on/off through Tuya App (cloud) or HA Tuya it stays available. But as soon as no commands are sent from Tuya (cloud) 10 seconds later goes offline. Also when I get it to become available this way I can switch to controlling brightness for example through Tuya local and as long as I don't stop triggering it, it stays online.

[edsil]

Same here. All LocalTuya devices become unavailable and the integration stops working, I can't even restart it. If I restart Homeassistant altogether, LocalTuya works for a random amount of time, but eventually the integration (and all associated devices) become unavailable again Log:

This error originated from a custom integration.

Logger: custom_components.localtuya.pytuya
Source: custom_components/localtuya/pytuya/__init__.py:647
Integration: LocalTuya integration (documentation, issues)
First occurred: 22:11:15 (1 occurrences)
Last logged: 22:11:15

[bf1...tap] Command 9 timed out waiting for sequence number -100

[RosensRauk]

Me too is getting spammed: Felet härrör från en anpassad integration.

Logger: custom_components.localtuya.pytuya Source: custom_components/localtuya/pytuya/init.py:647 Integration: LocalTuya integration (documentation, issues) First occurred: 3 maj 2023 kl. 23:38:39 (15 occurrences) Last logged: 00:31:15

[314...357] Command 9 timed out waiting for sequence number -100 [178...199] Command 9 timed out waiting for sequence number -100 [178...2e2] Command 9 timed out waiting for sequence number -100 [178...4ce] Command 9 timed out waiting for sequence number -100

All the lights work as expected. But I am getting frustrated because this has been happening for several months.

[TheAznShumai]

I am having the same issue also. My issue stems on the device being unavailable and then reconnecting automatically. Somewhere during that time, I get a block of these warnings.

[RosensRauk]

Same here

Felet härrör från en anpassad integration.

Logger: custom_components.localtuya.common Source: custom_components/localtuya/pytuya/init.py:259 Integration: LocalTuya integration (documentation, issues) First occurred: 12:26:16 (1 occurrences) Last logged: 12:26:16

[314...357] Initial state update failed, giving up: TimeoutError()

[314...357] Command 10 timed out waiting for sequence number 1

[314...357] Command 9 timed out waiting for sequence number -100

[314...357] Disconnected - waiting for discovery broadcast

[petercogen]

Same here...

[nima-1102]

Same here...

Updated to Version 5.2.1 ?

[petercogen]

Yes, 5.2.1

[Idan37S]

Same here. Any update on this issue? Was anyone able to resolve it?

[Mangomc]

Issue was fixed with 5.2.1 Never got the message again after updating

[Idan37S]

It still happens to me at v5.2.1

[ComputaBloke]

My Smart Kettle device was affected.

I've also got it working after these steps: 1) Trying to check and debug device via iot tuya site. 2) Removing problem device/entities from HA and re-adding. 3) Update to localtuya v5.2.1. 4) Adding debug logging to configuration.yaml 5) Adding explicit scan interval (e.g. 4 secs) on device.

For issue above with device doing unexpected things and aren't in an automation... The 'DPIDs to send in reset command' and 'Remember last state' are a couple of settings which might cause devices/entities to switch unexpectedly. Ive also recently had a bulb go bad, suspect simply the IC chip or relay perhaps aged after constant use for 4 years. I hoped for longer, but not a bad run.

[ComputaBloke]

Oh and also, on my router, added the devices MAC to DHCP static IP assignments.

Hope these ideas might help!

[alvingalangcitaka]

I have the same issue. It happen when it's having token request in which used by localtuya to retrieve local keys. There might be a case where the request rejected due to maximum retries limit. So, since I've inserted all my devices, I disable to api configuration.

In other case, I can confirmed that the issue also occurred after I restart my router, which in my case done every 3.15 am. So, I believe this issue happen while re-connecting the device after network failure. The workaround that I have is creating automation to reload the config entry everytime device unavailable detected.

Something like this : ` alias: LocalTuya Auto Recover description: "" trigger:

• platform: state entity_id:
  • switch.booster_pump to: unavailable for: hours: 0 minutes: 0 seconds: 30 condition: [] action:
• service: homeassistant.reload_config_entry data: {} target: entity_id: switch.booster_pump mode: single `

[SpartanTech]

latest home assistant, as well as 5.2.1 having this issue as well

[msbjr88]

Same issue as everyone else is describing.

[woempiej]

Yes ;)

[2IIZ]

Same issue. My logs say it stopped working on 18th of July. Last day working was 17th. Only 1 device stopped working, my other two localtuya device is working correctly.

[babelhoo]

All my localtuya devices work correctly, still, for the last few days, I'm getting hammered with ton of: (MainThread) [custom_components.localtuya.common] [110...577] Initial state update failed, giving up: TimeoutError() messages logged

[2IIZ]

Same issue. My logs say it stopped working on 18th of July. Last day working was 17th. Only 1 device stopped working, my other two localtuya device is working correctly.

I got 2 devices that apparently stopped working, of a total of 3. I switched from localtuya (HACS) to the Tuya integration. I got the 2 device that didn't worked with localtuya, working now with Official Tuya integration from HA. In the Tuya integration, the only one that doesn't work (written unsupported) is the only one that work on localtuya (HACS).

[geidorei]

Same issue - devices greying out, then returning..

Tuya devices and Tapo plugs.

[kriger1965]

Hi, having, the same issue - alls local touya devices going offline in an unexpected timeframe. Restarting (not the quick Reload) homeassistant do solve "some" issues, but after a unrecognized time also all tuya items are unavailable again.

here a extract of my logfile: see attacement connection.log

[kriger1965]

Same issue. My logs say it stopped working on 18th of July. Last day working was 17th. Only 1 device stopped working, my other two localtuya device is working correctly.

I got 2 devices that apparently stopped working, of a total of 3. I switched from localtuya (HACS) to the Tuya integration. I got the 2 device that didn't worked with localtuya, working now with Official Tuya integration from HA. In the Tuya integration, the only one that doesn't work (written unsupported) is the only one that work on localtuya (HACS).

this is not possible for me beacause: 1) I wont get "locked" with the china cloud and 2) some devices not possible to admin with standard tuya ...

[ethan-dow]

Commenting here because I have the same problem.

2023-09-20 19:50:39.175 WARNING (MainThread) [custom_components.localtuya.common] [201...ed1] Disconnected - waiting for discovery broadcast

It tries several times per second.

[VladimirV01]

I also have this problem. Tuya version is 5.2.1 and the logs show the problem described in this issue and my tuya devices become unavailable at random intervals.

This error originated from a custom integration.

Logger: custom_components.localtuya.common Source: custom_components/localtuya/pytuya/init.py:677 Integration: LocalTuya integration (documentation, issues) First occurred: 16 September 2023 at 10:31:22 (4098 occurrences) Last logged: 23:00:14

[bf8...gfu] Disconnected - waiting for discovery broadcast [bf4...tjo] Disconnected - waiting for discovery broadcast [bfc...kcf] Disconnected - waiting for discovery broadcast [bff...ps3] Disconnected - waiting for discovery broadcast [bfa...01z] Disconnected - waiting for discovery broadcast

[nawwman]

Getting the same here, lots of occurences.

`This error originated from a custom integration.

Logger: custom_components.localtuya.common Source: custom_components/localtuya/pytuya/init.py:255 Integration: LocalTuya (documentation, issues) First occurred: October 9, 2023 at 16:19:11 (29 occurrences) Last logged: 15:57:48

[423...cde] Disconnected - waiting for discovery broadcast [423...f76] Disconnected - waiting for discovery broadcast [423...801] Disconnected - waiting for discovery broadcast [423...616] Disconnected - waiting for discovery broadcast [423...456] Disconnected - waiting for discovery broadcast`

[frontendbuddy]

Hey, I believe I am getting the same issue here but only for two devices - OXT light switches.

2023-11-27 21:40:53.315 INFO (MainThread) [custom_components.localtuya.common] [bf3...u6a] Trying to connect to 192.168.1.27... 2023-11-27 21:40:53.581 WARNING (MainThread) [custom_components.localtuya.common] [bf3...u6a] Disconnected - waiting for discovery broadcast 2023-11-27 21:40:54.800 INFO (MainThread) [custom_components.localtuya.common] [bf8...6ei] Trying to connect to 192.168.1.145... 2023-11-27 21:40:54.998 WARNING (MainThread) [custom_components.localtuya.common] [bf8...6ei] Disconnected - waiting for discovery broadcast

What is even more weird is that these two devices I can control via Tuya mobile app and in the iot.tuya.com I can see that their status is online...

So it's only HA problem, it feels like something is preventing a connection between the device and the LocalTuya integration. I've restarted router multiple times, made upgrades of everything, tried also to downgrade the integration to lower version 5.0 and nothing helps. I have this weird feeling that it's HA that forbids these two devices to connect due to too many failed connection requests.