ChirpyTurnip

HI have the same problem now also for a few days - but I only just noticed. Previously my Lenovo smart plugs that I run under LocalTuya were 100% solid....

Mine have always been on static IPs so I know that's not my cause.... :-( On Tue, 8 Feb 2022 at 13:21, Saramidek ***@***.***> wrote: > Not in My case...

So I'm the same - no trace of the other Weatherflow HACS integration and the Weatherflow integration in the list is the 'official' one:  Same error as @jkaberg, and...

My HA and tempest are definitely in separate subnets and firewalled off from each other. I would expect that the config flow will allow me specify the target IP address...

I have the same problem (only Gen1 devices) but want to note that *immediately* after the HA restart (when it says "Home Assistant has Started!") all the Shelly devices are...

For me the reproduction of the issue is fast and reliable --> Restart, count to 100, instant chaos! :-) Here are my logs from running to restart to config reloads........

That doesn't sound super ideal - it would be better if it was an easy fix. :-) The problem does not appear to occur in safe mode....but then in safe...

> Your callgrind files are impressive assuming they are 60s long. You have on of the busiest systems I have ever seen. I can't claim a record...they are 600s long.....I...

OK....so this is all a little bit weird. It actually behaves better with the debugpy: entry in the configuration.yaml....like basically no issue. At one point one device dropped off (and...

OK....I ran it again with HA.core + Shelly in debug mode, and _debugpy:_ in the configuration.yaml. This time I saw the _asyncio_ messages in the log.....so it might have done...