remlei

Just enable debug logging with local tuya and you will see what really happens here, and static ip will not fix it because localtuya is waiting for the device to...

probably related to #1019 the fix is probably downgrade to v4.0 maybe 4.0.2 fixes your issue but for my test the issue still exist if you try reloading localtuya or...

>Currently, only Tuya protocols 3.1 and 3.3 are supported (3.4 is not). so yeah its not supported, unless you guys are willing to send your 3.4 devices gadget for free...

You can just add the sensor DPs one by one as entity in Home Assistant, it should work on every single device out there, as long as its not battery...

if that motion sensor is battery powered, well, you only have 10 second to add it to localtuya and even if you manged to add it, its not going to...

well its battery operated so... yeah. this is expected. same with other wifi based tuya device that is battery powered (eg, temperature, motion sensor etc...) as always this is not...

Unfortunately as it seems, battery powered wifi sensor is just bad. The only forgivable wifi based tuya sensor is the mmwave presence sensor since theres no way you will be...

Even if you managed to add it, it will be finicky to make it work with localtuya, after all these tuya device can on push notification to cloud, and you...

I hope this PR fix gets pushed soon, majority of my switches are randomly turning off/toggling. I have to rollback to 4.0.1 just to avoid this issue. edit: for some...

> > > > Hello I have such problems in my configuration. Can you please explains how to rollback the LocalTuya integration to 4.0.2 ? Same steps as you download...