Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPM02_WiFi_V2 stopped working #1849

Open
4 tasks done
AlfonsVac opened this issue Nov 20, 2024 · 0 comments
Open
4 tasks done

SPM02_WiFi_V2 stopped working #1849

AlfonsVac opened this issue Nov 20, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@AlfonsVac
Copy link

AlfonsVac commented Nov 20, 2024

The problem

Meter SPM02_WiFi_V2 was working normally, then IoT core licence run out and after extending it again it did not recover.
Device normally work in the app and also in tuya cloud connector for HA.
Device is not possible to add nor when it was added before load any data.
image

Environment

  • Localtuya version: 5.2.1
  • Home Assistant Core version: 2024.10.3
  • 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 ? but no response
  • Was the device working with earlier versions of localtuya ? Which one? a month ago
  • Are you using the Tuya/SmartLife App in parallel ?

Steps to reproduce

  1. It was running normally but when somewhen IoT. Core licence ended it stopped and after activating it again it newer recover similar to all the other devices

DP dump

  INFO:localtuya:Detecting list of available DPS of device bf6deaa502c0f4367blfkr [192.168.9.248], protocol 3.4.
DEBUG:localtuya.pytuya:[bf6...fkr] 3.4 device: negotiating a new session key
DEBUG:localtuya.pytuya:[bf6...fkr] final payload for cmd 3: b'0123456789abcdef'
DEBUG:localtuya.pytuya:[bf6...fkr] Command 3 waiting for sequence number -102
DEBUG:localtuya.pytuya:[bf6...fkr] Connection lost: None
DEBUG:localtuya.pytuya:[bf6...fkr] received null payload (None), fetch new one - 1 retries remaining
DEBUG:localtuya.pytuya:[bf6...fkr] Command 3 waiting for sequence number -102
DEBUG:localtuya.pytuya:[bf6...fkr] received null payload (None) but out of recv retries, giving up
DEBUG:localtuya.pytuya:[bf6...fkr] session key negotiation failed on step 1
DEBUG:localtuya.pytuya:[bf6...fkr] Sending command 10 (device type: v3.4)
DEBUG:localtuya.pytuya:[bf6...fkr] Sending payload: b'{"gwId":"bf6deaa502c0f4367blfkr","devId":"bf6deaa502c0f4367blfkr","uid":"bf6deaa502c0f4367blfkr","t":"1732135364"}'
DEBUG:localtuya.pytuya:[bf6...fkr] final payload for cmd 16: b'{"gwId":"bf6deaa502c0f4367blfkr","devId":"bf6deaa502c0f4367blfkr","uid":"bf6deaa502c0f4367blfkr","t":"1732135364"}'
DEBUG:localtuya.pytuya:[bf6...fkr] Command 16 waiting for sequence number 2
ERROR:localtuya.pytuya:[bf6...fkr] Failed to get status: 
Traceback (most recent call last):
  File "/usr/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/locks.py", line 386, in acquire
    await fut
asyncio.exceptions.CancelledError

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

Traceback (most recent call last):
  File "/root/tuyadebug/localtuya/pytuya/__init__.py", line 849, in detect_available_dps
    data = await self.status()
           ^^^^^^^^^^^^^^^^^^^
  File "/root/tuyadebug/localtuya/pytuya/__init__.py", line 781, in status
    status = await self.exchange(DP_QUERY)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/tuyadebug/localtuya/pytuya/__init__.py", line 755, in exchange
    msg = await self.dispatcher.wait_for(seqno, payload.cmd)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/tuyadebug/localtuya/pytuya/__init__.py", line 446, in wait_for
    await asyncio.wait_for(self.listeners[seqno].acquire(), timeout=timeout)
  File "/usr/lib/python3.12/asyncio/tasks.py", line 519, in wait_for
    async with timeouts.timeout(timeout):
  File "/usr/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
INFO:localtuya:TIMEOUT: No response from device bf6deaa502c0f4367blfkr [192.168.9.248] after 2 attempts.

Provide Home Assistant traceback/logs

Tato chyba pochází z vlastní integrace.

Logger: custom_components.localtuya.common
Zdroj: custom_components/localtuya/common.py:130
integrace: LocalTuya integration (dokumentace, problémy)
První výskyt: 21:22:21 (419 výskyty)
Naposledy logováno: 21:57:18

Missing device configuration for device_id bf6deaa502c0f4367blfkr

Additional information

@AlfonsVac AlfonsVac added the bug Something isn't working label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant