Did you execute the action manually? Every person has an entity_id. The only trigger entities which are allowed are persons. If you want to test your automation you can change the state in the developer options of the observed persons.
I have an issue with this as well. If I manually change the state of the person entity from zone to zone, it works as intended, but it breaks if there is a “not_home” state in-between. For example, I get this error when traveling from “not_home” to “home”:
UndefinedError: ‘None’ has no attribute ‘attributes’
Thank you very much for your testing ambitions. I wish I could provide more stable code based on unit tests.
The zone handling in person entities especially the home zone is a little bit inconsistent. I’ve updated the blueprint again. Hopefully it works now as expected. Feel free to give feedback again.
very cool blueprint!! May I make a suggestion? The GPS on my wife’s mobile gets very erratic and enters and leaves “the Zone” very often, even though the phone has not moved. At night this is really a pain, as the sleep tracker on her wrist keeps vibrating. So I previously used a time window from 06-22 hours for notification. Is it possible to implement that with your blueprint?
Thanks again for your work,
Robert from Mannheim, Germany
There seems to be a bug in the blueprint. Sylvia is no where close to IdAW 104, so she could not actually be entering it. Sorry for the terrible picture, can’t take a screen shot of the message screen on my S23.
The blueprint is just based on the state of person entities. If the state changes a notification will be fired. I just use that blueprint for geo locations.
Your history shows Sylvia entered ldAW 104. So a notification will be fired if you configured your automation for that location. But if she never entered that location your integration that sets the state for her is fooling you.