HI,
Having been using the notify.notify service for since forever, I find myself lost looking for a reason it won’t work after I updated to the new iOS app today.
Would have thought that to be of no impact for this service at all, since the app is using service.mobile_app_etcetc, and indeed working correctly.
All my other services notify.xxx work fine too, except for the generic notify.notify, which of course is the iOS notification system.
Am I wrong to believe this was a built-in notify platform, for all home-assistant devices running the iOS app?
It has worked like that since the beginning and all of a sudden has stopped. (at least for the iPhone with the new app)
please give me a pointer how to solve this? Hope there will be a generic replacement.
update
see below post:
1 Like
Ill mark this as solved by replying to myself:
silly of me of course, I had followed the migration guide, and deleted the entry for my iPhone from iOS.conf.
Have now restated that and voila, the notify.notify service is backup for the instance.
Must admit I find the design decision to give the new device-tracker the identical name as the device name not very thought through. Many users will already have that device_tracker for their networked device. Would have been easier if a default prefix of mobile_app would have been chosen imho.
Especially since the new mobile app creates many sensors with that identical device name. Took a lot of changing to get it to be unique in my setup, and that was for 1 device alone. Still have a few to go…
For now, I will change all ‘old’ device_trackers to device_tracker.device-name_retro, and see what happens in the future.
That way I am future proof (because embracing the new way of notifying and all other underlying techniques ) and still am able to use the ‘retro’ way if notify.notify…