In your automation you can simply call this service, making you live easier to maintain it. So in the end the service does the same thing, but you don’t have to go through the whole documentation.
My current counter is now on 56 automations that uses this service. If I would update the service, then I don’t have to redo all other 56 automations, since they all point to this single service.
Have a look at the examples that you can use in your automation: Useful examples
I recently discovered this blueprint and would love to put this to use.
After an assortment of tests, I think I’m seeing a bug that prevents messages from being sent. It is coming up with the wrong notify.[device name]. The notify.[device name] may have been a valid entry in the past - but it is not now.
I have removed the blueprint, redownloaded, performed restart… it’s just not working. If I send a notification without the blueprint - those work.
I have tried the blueprint function with “both” and “home” and the messages don’t go through. They do, however, say it’s looking for a service that doesn’t exist; this applies both to my phone and my wife’s phone.
Flip side: it does work for my WearOS watch. But that’s one of three devices I’d need to hit.
I nosed around some and found a way to view the effects of the script. I’ll add what I’ve learned here, since I didn’t see it in what I reviewed.
I have this working on all three device.
The script looks at the device_trackers and extrapolates the notify.mobile_app_[device name] and if it doesn’t match, the script doesn’t work. For my wife’s phone, the router had reserved the non-“_2”, so her device_Tracker was [device]_2 and for mine, I had renamed the device to be more human-friendly. In both cases, this threw things off.
I made sure that the device in mobile app and the device_tracker had the exact same name. Once that was done, success.
Awesome to see that you were able to find to issue and resolve it, and thanks for the feedback!
Currently there is no way to get the device services, so that is why I had to used the “find and replace” -part. But as you mentioned it did not work initially, so I’ll need to see if I can come up with some solution, since also others have noticed the same.
Is it possible to use this service with Node-RED?
I’m not using Node-RED, but it is just a “Script”, so I guess so?! Have you ran into issues? What is your experiences so far?
Just released a new version, check it out: Release 2024.04 · Grumblezz/Home-Assistant-Notify-Mobile-Companion-App-Devices (github.com) and updating should be super easy to update to the latest version with just two clicks:
