Well got new devices for fam and now none of notifications work. I tried renaming them in the companion app and in HA renamed them and nothing so far has worked. What is the best way going forward to make sure my notifications still work if i replace the devices and login. I renamed them with what they were called before and removed the old devices from HA. Still wasn't enough.
#New Devices Notification Automation Issues
mint hollow
true sage
How are you sending the notifications? If the service is named the exact same as it was before (and that's what you're using), there's no reason that shouldn't work, what's the error?
One way forward to help prevent reoccurrence is to create notify groups. That way you can add and remove members (could just be a single member, too) and keep the group name consistent.
mint hollow
Sending different ways some from blueprints, some from hand built automations that were done with notification feature and mobile app. So its a mix I want to see if there is a better way to future proof this so I can simply replace a device and keep everything working.
Where are notification groups created?
true sage
mint hollow
Can you also tell me what would be best practice when getting new device. Should I logout of HA on that phone and remove the device in HA. Then come up with a generic device name to use? So if person is Tim just name it TimsPhone. I noticed Android lets you specify the name at login and iphone did not ask.
Would be a nice feature if a person already logged and owns device prompt at login if this is a replacement for the currently logged in device. Then let HA handle all the replacements. Luckly I am not far in my build out but it could be painful for someone who learns of this issue down the road.
true sage
I'm not familiar with the specifics there: #1284965926336335993 likely could give you some more thoughts on the apps themselves. However, it'd be a perfectly valid use case for someone to maintain multiple devices (but don't disagree that having a replacement workflow might be nice).
When I swapped out my phone recently, I believe I just logged out/removed the server from the Companion app on my phone, and then logged into the app on my new phone. I also did run into the situation you described, where the service names were updated (since they contain the model of the phone). That's where I went the path of using the notify group going forward. It has a benefit of adding more notification channels in the future if you'd like, as well.
mint hollow
Looka like I had a notification group for my frigate blueprint its named all_devices
however those are some of the blueprints that are not working i went in and changed the names of devices for all_devices. how do i verify if maybe also updates to HA removed the service name im using for notify group. it has been service: mobile_app_devicename for the longest time
mint hollow
Looks like services no longer exist how do i translate this to new method of notification group
rustic crystal
Services has just been renamed actions
mint hollow
so where i have services in the yaml do i need to now change to actions
example: #phone app notification group for notifying both phones
notify:
- name: MOBILE_PHONES
platform: group
services:- service: Michelle's Phone
- service: Robert's Phone
mint hollow
i now have: example: #phone app notification group for notifying both phones notify: - platform: group name: MOBILE_PHONES services: - action: mobile_app_phonename1 - action: mobile_app_phonename2
dev tools gives no errors
but whwn i try and use MOBILE_PHONES as a device group in blue print it gives unknown devices error. So something new that doesn't like
true sage
It's not a device, it's an entity. You're referring to the Frigate blueprint above? Make sure you're using the "Notification Group" input for your group
mint hollow
im using that field have been for nearly 2 yrs.
i just put MOBILE_PHONES in it but when i do i get unknown device error
true sage
Are there any more details on the error you can share
The "Mobile Device" field is still required... perhaps that is no longer valid
mint hollow
when i try and save the blueprint it says Message malformed: Unknown device: false
if i try it with single devices added in mobile device field it works fine
true sage
Right, you need a device selected
mint hollow
it just clicked
i think it was a combo of me not editing this blueprint in a while and actions hacing to be used in config yaml
then i forgot yiou always have to have a device selected but it wil be ignored
ahh wait that is why they all went into error and always will the device even though name is same must have a different id associated blueprint
im having to go to every camera notification and reselect the device
Is there anyway to avoid device id breaking it by using a name on device.
This needs to ve thought out to help HA go mainstream. I can't see a HomeKit user as an example making a transition to HA. HomeKit wouldn't have these problems of getting new mobile device. Person would sign in as their account and continue to get notifications from app no matter what new device was named.