bcutter
bcutter
Roughly 1.5 days after updating HA OS to 14.2 (and Supervisor from 2025.2.0 to 2025.2.1), this old ~~friend~~ enemy is back:      https://www.home-assistant.io/more-info/unsupported/network_manager   I'm...
I can confirm this behavior. Must be the way Watchman is integrated or updates itself. All the actions listed (reloading automations, scripts and scenes) seem to trigger reloading Watchman too....
@dummylabs Is it (meanwhile/as interims solution) possible to stop Watchman from updating when reloading automations, scripts and scenes? HA core team put quite some effort in speeding up reloading automations...
Indeed. An integration causing Core to get fully blocked (for 30 seconds in my case, your mileage may vary due to system performance) is an absolute no-go. The biggest no-go...
Even more annoying is it intercepts editing automations and scripts ⚠️⚠️⚠️ On every save (using the UI, which probably causes `scripts.yaml` and `automations.yaml` to be parsed again bei WM) my...
> Do not run Watchman constantly. Do you really mean this like you wrote it? Is this a "You are holding it wrong!" blaming? Are we now discussing if this...
> v0.6.3 should be fully compliant with HA async requirements for custom integrations ...unfortunately saving automations or scripts in the UI still makes whole HA freeze for 20 to 30...
That switch would be nice. It would allow things like using the automation_reload event to trigger an automation which waits for 30 (or with Watchman disabled only 1 to 3)...
Not experiencing this. But around 04:00 in the night is generally a bad time for intensive tasks as per default the recorder purge takes place here (if not disabled/set to...
Did you have a look at https://developers.home-assistant.io ? What I described is the pure user experience after dozens of HA core updates over the years (which basically is: migration happens...