Open jbeardon opened 6 months ago
Wierd an automation is causing this error. I have seen some similar errors logged on HA Core repo but they seem to be caused by integrations performing non thread safe operations.
I will have a look at this myself but what HACs integrations do you have loaded?
Hi Mark - I thought it odd as well but I have always had concerns about this setup (particularly the external sensor event automation). It literally gets triggered with every sensor state change and then has to evaluate whether the sensor is using a defined integration that it starts and ends with certain text - if, like myself, you have a lot of sensors, it's triggering almost continuously. I've been meaning to re-write the even trigger part of it so that it's only triggering from specific sensors and not having to do the whole valuation thing.
In answer to your question, although I do have a number of HACS integrations, the only one that was mentioned in any of the posts I came across was Watchman, which I removed prior to doing further troubleshooting. The only thing in the logs creating errors referenced this automation so didn't really look further.
For reference, I have these HACS integrations installed: Tapo: Cameras Control myenergi Moonraker Frigate (proxy) keymaster Haier hOn Event Sensor Holidays Alarmo WebRTC Camera Octopus Energy HASS.Agent Alexa Media Player Bambu Lab Drayton Wiser
Just a heads up for anyone using recipes/manage_temps_v2.md
I attempted to update to HA 2024.4.1 this morning and although everything seemed to go well, HA became unavailable within a matter of minutes. Tried the upgrade a few times after rolling back but experienced the same issue - removed a few HACS integrations that were documented as causing issues - no joy.
Looking at the logs, the trigger automation for manage_temps_v2 was referenced in multiple, repeated errors until losing connection to HA - example at the bottom of this issue.
I'm no expert but after eventually managing to get HA running long enough, I disabled the automations relating to Manage Temps V2 and HA has been stable since.
I've been using Manage Temps for at least 6 months - this problem was not present with HA 2024.3 but there is a definite corrolation.