Odd behavior on reload groups?

I’m having an odd issue when I reload groups as I am working on a new lighting automation scheme reload seems to turn on another group?

When I hit the button for “Reload groups, group entities, and notify services”, for some reason it throws a warning “WARNING (MainThread) [homeassistant.components.automation.all_radios_turn_off] all_radios_turn_off: Already running” and my radios group turns ON (which should only be on if the group of “people” are all “not home”…purpose is keep dogs company when nobody is home)

Any idea what this means? When I see it the radios are not turning off, so i seems like it’s not running when it complains it’s already running?
Anyone got a guess why I’m getting that warning I never used to?

As far as I can tell, everything works perfectly EXCEPT during reload.

People is a special group.

When you reload the groups, all groups will go to ‘unknown’. Then when the groups reload, they should go back to their other state.

The warning there means the automation is set to single mode and is currently running when trying to run again. My guess is it’s running for the ‘unknown’ state change, then trying to run again for the reloaded state change nearly immediately.

What is the triggers for automation.all_radios_turn_off? Or better yet, what is the whole automation?

Ah. Yeah, one of the triggers is people group “not home”…and “unknown” != “home”.

However it doesn’t go back, I guess because they trigger so fast? Is there a way I can make it queue them so it goes on then off instead of on then conflict on off?

EDIT: Found the documentation for automation modes…now I guess I just need to modify them all to “queued” mode (since I generally assume they would do that)

Correct, it doesn’t go back because it happens so fast that the automation was still running.

It would be better to not trigger on that condition, but queued or restart is fine too.