3 devices lost their configs - can't add them back in.

[FS1961]

The Problem:

3 Devices lost their attributes with the new Local Tuya update. Had to load an earlier version to correct. 5.2.2 restores the devices correctly. Pretty sure it's a bug in 5.2.3

Environment

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

Steps to reproduce

1. Load 5.2.3

DP dump

Provide Home Assistant traceback/logs

put your log output between these markers

Additional information

Working for years and this update breaks just these units.

Before and after.

The integration used to be able to query the device or the site and pre-populate the device with its values. Was this removed?

Everything works falling back!

[FS1961]

@rospogrigio - is this not enough?

[CloCkWeRX]

May be worth trialling https://github.com/xZetsubou/hass-localtuya/
Not possible to tell root cause without logs.

[FS1961]

I can appreciate that. I have this in my config.yaml I will attach the logs logger: default: critical logs: custom_components.alexa_media: debug # for API debugging (verbose and intended for service debugging) alexapy: debug # for proxy debugging authcaptureproxy: debug custom_components.localtuya: debug custom_components.localtuya.pytuya: debug [localtuya log.txt](https://github.com/user-attachments/files/18704356/localtuya.log.txt) That's everything from the logs.

…

On Feb 7, 2025, at 8:38 AM, CloCkWeRX ***@***.***> wrote: May be worth trialling https://github.com/xZetsubou/hass-localtuya/ Not possible to tell root cause without logs. — Reply to this email directly, view it on GitHub <#1911 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXPFZNWCZVWOVSIAREMLXCL2ORPITAVCNFSM6AAAAABVTFLKPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGE2DIOBXGM>. You are receiving this because you authored the thread.

[CloCkWeRX]

Thanks. Unfortunately not much easily discerned there , apart from the multiple devices waiting for a broadcast then timing out.

[FS1961]

Thanks. On Feb 7, 2025, at 12:37 PM, CloCkWeRX ***@***.***> wrote: Thanks. Unfortunately not much easily discerned there , apart from the multiple devices waiting for a broadcast then timing out. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>