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

Device's host field is being deleted every time HA reboots #1903

Open
gilshahar7 opened this issue Jan 18, 2025 · 0 comments
Open

Device's host field is being deleted every time HA reboots #1903

gilshahar7 opened this issue Jan 18, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@gilshahar7
Copy link

gilshahar7 commented Jan 18, 2025

The problem

One of my localtuya devices is losing it's "Host" field every time i reboot homeassistant:

Image

Once i enter the IP address again it works normally.
The IP address is static in the router and so far stayed the same this whole time.

The "Host" field is being deleted consistently when i reboot HA.

I have 2 other devices that work fine and they keep their host field.

Environment

  • Localtuya version: 5.2.3
  • Home Assistant Core version: 2025.1.2
  • [] 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 ?
  • [] Was the device working with earlier versions of localtuya ? Which one?
  • [] Are you using the Tuya/SmartLife App in parallel ?

Steps to reproduce

  1. manually edit the device and add the static IP in the "Host" field.
  2. reboot HomeAssistant
  3. The "Host" field is empty again and the device is not responsive

DP dump

INFO:localtuya:localtuya version 1.0.0
INFO:localtuya:Python 3.11.9 (tags/v3.11.9:de54cf5, Apr  2 2024, 10:12:12) [MSC v.1938 64 bit (AMD64)] on win32
INFO:localtuya:Using pytuya version '10.0.0'
INFO:localtuya:Detecting list of available DPS of device XXXXXXXXXXXXXXXX [192.168.1.12], protocol 3.3.
DEBUG:localtuya.pytuya:[bf9...orp] Sending command 10 (device type: type_0a)
DEBUG:localtuya.pytuya:[bf9...orp] Sending payload: b'{"gwId":"XXXXXXXXXXXXXXXX","devId":"XXXXXXXXXXXXXXXX","uid":"XXXXXXXXXXXXXXXX","t":"1737211870"}'
DEBUG:localtuya.pytuya:[bf9...orp] Command 10 waiting for sequence number 1
DEBUG:localtuya.pytuya:[bf9...orp] Dispatching message CMD 10 TuyaMessage(seqno=1, cmd=10, retcode=1, payload=b'\xf7"J\xb9\xc5\xaeE\x98a\xc6n\xeb\xbd\xdc\x88\x9e=\x96\r\xc9\xe1(\xd9>\xd4\x00\x0fL9\xf5\x15\x14', crc=946057560, crc_good=True)
DEBUG:localtuya.pytuya:[bf9...orp] Deciphered data = ''
DEBUG:localtuya.pytuya:[bf9...orp] ERROR Invalid JSON Response from Device - 900 - payload: ""
AVAILABLE DPS ARE [{}]
INFO:localtuya:COMPLETE response from device XXXXXXXXXXXXXXXX [192.168.1.12].

**** deviceInfo returned OK ****

TuyaDebug (Tuya DPs dump) [1.0.0]

Device XXXXXXXXXXXXXXXX at 192.168.1.12 key XXXXXXXXXXXXXXXX protocol 3.3 dev_type type_0a:
@gilshahar7 gilshahar7 added the bug Something isn't working label Jan 18, 2025
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