I’m using the 'home" state for those devices in multiple other automations, so I suspect that’s not the issue. Regardless of the state of that input boolean, if its state is included as a condition in the automation, it never fires.
I gotta believe I’m missing something simple. Help?
Nothing to apologize for - most new posters aren’t aware of how that works and that’s why I made the image.
One thing to check - go to your dev states panel and make sure that the state of the input boolean is actually ‘off’ and not ‘Off’. Case makes a difference.
HA errors aren’t always the most descriptive. I once had HA not start up because I copied and pasted a script with a degree symbol in it. No error log at all. Turned out it couldn’t start because the degree symbol was not in UTF-8 format but no error message to that effect except from systemctl. After I figured it out which file it was and corrected it, I posted a error and it was addressed.
But this is a heads up to people that copy and paste example scripts - make sure the editor you use can specifically save files in UTF-8 format.