R1DEN

@softhack007 hey, since you added the discussion label, maybe you have any ideas? Given your knowledge or wled internal workings and this [comment](https://github.com/Aircoookie/WLED/issues/3467#issuecomment-1774721722)

Isn't it possible to just not invalidate the preset when turning it off/on? And invalidate it on all other changes? I don't see the need for additional variables (apart from...

Sure thing: The first three files are from working sensors: from great signal to extremely poor - all work stable. [zha-68f170441170f4e2f60d00d9e3caabf0-LUMI lumi.json](https://github.com/home-assistant/core/files/13758837/zha-68f170441170f4e2f60d00d9e3caabf0-LUMI.lumi.json) [zha-68f170441170f4e2f60d00d9e3caabf0-LUMI lumi-1.json](https://github.com/home-assistant/core/files/13758838/zha-68f170441170f4e2f60d00d9e3caabf0-LUMI.lumi-1.json) [zha-68f170441170f4e2f60d00d9e3caabf0-LUMI lumi-2.json](https://github.com/home-assistant/core/files/13758839/zha-68f170441170f4e2f60d00d9e3caabf0-LUMI.lumi-2.json) And the one which...

The only thing I see different is that the faulty device doesn't have a `manufacturer` attribute (the LQI entity hasn't been enabled yet).

It seems like I may have found a workaround. When the device is paired - you can change its name right at the pairing screen - that causes its ID...

Well after that I've re-paired it several times, then just re-paired it without deletion and it seems to be working okay for more than 24 hrs (once again). So it's...

@sparkplug23 @tmargot you can check https://github.com/SlashDevin/NeoGPS/issues/110#issuecomment-1622238073

I'm gonna provide some more input to this one. I had a project since 2019 which is working perfectly fine on my old laptop with the old version of `toolchain-xtensa`...

I have the same exact issue... furthermore the TRV is only precise to 1 degree, while I need my thermostat to be set with 0.1 precision and 0.1 tolerance

@tomg1970 hey, firstly you would want to use a custom quirk for this TRV