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.
Cool, now if I could only figure out, how the âgroupâ thingy would work here. I want to notify my wifeâs and my device. New to this stuff and just can not figure it out.
Just a tip for those that have GPS troubles. My wifeâs GPS was all over the place and nothing I tried, fixed that. So last night I remembered a similar problem on my phone. The fix? Clear the phone cache!! Worked great for my phone and my wifeâs. This is not app cache, etc. it is the actual ANDROID cache on the phone. Search for it on google, it is relatively simple. IMPORTANT: The phone has to be attached to a PC!! Charger does not count!!!
Donât think so. Home Assistant log shows no deprecated warning and I checked the documentation. Everything is fine. Seems vscode produce a false positive warning.
Iâve setup an automation using this blueprintâthanks so much for your work! This is my first time using a blueprint, so maybe Iâm doing something wrong! I believe I setup everything right, putting in people, zones, a notification group, etc ⌠but the automation isnât triggering. It shows âneverâ as last run.
Strange. For some reason, my automations would not load anymore. So I deleted all entries in the yaml file. Set this up again and it is not working (anymore). Worked before I cleaned out the automations.yaml.
Still looking for the âwhyââŚ
âExecuted: 12. August 2023 um 20:39:38
Error: UndefinedError: âdict objectâ has no attribute âentity_idââ
Is the error I get when I trigger it manually, not sure if that is normal. Has not been activated bei HA since I configured it.
Looks like the tracker under âPERSONSâ was automatically changed by something. Reset that to the actual tracking device and all was good.
I have noticed, that under âPERSONSâ, tracker are sometimes added automatically. I keep finding trackers there, that I did not include. So check there, that might also be your problemâŚ
@RobertoCravallo what was your solution for the âgroupâ thing? I think that has been my problem. When I change my automation to notify a single device, it works great â when I put a group in, no luck at all (it fails).
Here is what I have for the automation:
- alias: Zone Notification Extended
id: "1691234"
description: Notifies when people arrive and leave zones
use_blueprint:
path: panhans/zone_notification_extended.yaml
input:
persons:
- person.me
- person.wife
- person.etc
zones:
- zone.my_first_zone
- zone.my_second_zone
notify_group: family_notification_group
And that family_notification_group is defined in my configuration.yaml file as:
This is what is working for me⌠I put this in my configuration.yaml and it was working. Just rechecked, I was not using the group feature, reapplied it now. Not sure if it is actually working, as I only had âdevice to notifyâ set. Would be nice, if I could just put multiple devices into that input field.
####################################################
# #
# Group for automation messages #
# #
####################################################
notify:
- name: "My notification group"
platform: group
services:
- service: mobile_app_sylvia_note
- service: mobile_app_roberts_s23
Now if I could only figure out, how to put an /local/images/mage.png in the arriving and leaving titles. I would like a very small red or green dot there.
After I reload âGroups, etcâ I can find âMy notification groupâ. Did you restart HA, I think that might be needed for this to work.
I can now send notifications to a group in the HA back-end. See attached picture. I have not been able to test the blueprint, will walk the dog later and see what happens. Manual execution of the blueprint does not work!