Anyone else finding the notifications really unreliable on the iOS app? I’ve got automations set to notify my phone and my wife’s phone, and sometimes the notifications come through and sometimes they don’t 
I have not experienced this.
Any logs generated?
Notifications generated by automations are pretty reliable for me. Location based notifications are totally unreliable though.
So here’s two messages generated by an automation earlier:
May 11 16:43:18 server hass[23753]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: domain=notify, service_data=message=The alarm has been disarmed, data=push=badge=0, category=ALARM, service_call_id=140256685140904-486, service=justin_fiona>`
May 11 16:43:18 server hass[23753]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: domain=notify, service_data=message=The alarm has been disarmed, data=push=badge=0, category=ALARM, service_call_id=140256685140904-487, service=ios_fionas_iphone>
May 11 16:43:18 server hass[23753]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: domain=notify, service_data=message=The alarm has been disarmed, data=push=badge=0, category=ALARM, service_call_id=140256685140904-488, service=ios_justins_iphone>
then
May 11 16:43:18 server hass[23753]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=140256685140904-486>
May 11 16:43:19 server hass[23753]: INFO:homeassistant.components.notify.ios:iOS push notification rate limits for None: 28 sent, 150 allowed, 0 errors, resets in 8:16:40
May 11 16:43:19 server hass[23753]: INFO:homeassistant.components.notify.ios:iOS push notification rate limits for None: 26 sent, 150 allowed, 0 errors, resets in 8:16:40
May 11 16:43:19 server hass[23753]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=140256685140904-488>
May 11 16:43:19 server hass[23753]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=140256685140904-487>
But it never reached my phone. Not sure whether it reached my wife or not.
Here’s another one that did work
May 12 00:16:20 server hass[20914]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: domain=notify, service_call_id=139947339213736-20, service_data=data=push=badge=0, category=ALARM, message=The alarm has been disarmed, service=justin_fiona>
May 12 00:16:20 server hass[20914]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: domain=notify, service_call_id=139947339213736-21, service_data=data=push=badge=0, category=ALARM, message=The alarm has been disarmed, service=ios_justins_iphone>
May 12 00:16:20 server hass[20914]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: domain=notify, service_call_id=139947339213736-22, service_data=data=push=badge=0, category=ALARM, message=The alarm has been disarmed, service=ios_fionas_iphone>
then
May 12 00:16:20 server hass[20914]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=139947339213736-20>
May 12 00:16:20 server hass[20914]: INFO:homeassistant.components.notify.ios:iOS push notification rate limits for justins_iphone: 46 sent, 150 allowed, 0 errors, resets in 0:43:39
May 12 00:16:20 server hass[20914]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=139947339213736-21>
May 12 00:16:20 server hass[20914]: INFO:homeassistant.components.notify.ios:iOS push notification rate limits for fionas_iphone: 41 sent, 150 allowed, 0 errors, resets in 0:43:39
May 12 00:16:20 server hass[20914]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=139947339213736-22>The alarm was disarmed in different ways (one manually and one from a presence detection) but the messages are all triggered from the same automation, which triggers when the HA Alarm state changes to ‘disarmed’, so the method of disarming shouldn’t matter. Interestingly the one that worked has
“push notification rate limits for justins_iphone”
and the one that didn’t has
“push notification rate limits for None”
Why is it failing to get the correct device name? The groupname is the same in both examples, as they’re from the same automation.
I wonder if it’s because I’m using notification groups, and if I split out the notifications to the 2 phones separately it would be more reliable?
I have the same issue. Started looking into it and found that the IOS app on my phone had all "X"s for the status.of (iOS component loaded, Devicetracker component loaded and iOS notify platorm loaded.
If I hit save then they will all come up check marked and loaded again but if I close the app and open it again they are all "X"s again
Mine’s not doing that (that I’m aware of)
I am not using groups. Maybe that is the factor here.
I have the IOS client loaded on 3 devices. One is my phone, one is my wifes phone, and one is my iPad.
At this moment, both the iPad and my wifes phone are showing locations where they were yesterday (which is a couple of hundred miles from where they are today). Neither device is with me at the moment, but I pet dollars to donuts that when I open the Home Assistant app, they will both show the black X near location even though they once were tracking location successfully.
I’ve un-installed and re-installed a few times, and am usually able to get tracking to work for a while, but it always quits again.
What I don’t understand frankly is why the tracker on my iphone works more reliably than the other two.
I’ll keep using the app, in hopes that it gets better, but I’m going to have to eliminate all my automations that are location-based until a more reliable solution exists.
I’m also going to add that if your notifications use the dir_of_travel property of a proximity object, then that’s SUPER-unreliable when using the IOS app.
Same here. I don’t have our devices in groups (just use notifications for individual devices), and they just seem to stop working now and then. Very hit and miss.
I still have some older automations that use Pushover instead of HA’s native iOS notifications, and they always seem to trigger. I might go back to using that.
Maybe I should try removing the group bit. Just means I have to duplicate every notification, but if it makes it reliable then I can cope with doing that!
I know it’s been months, but I’ve been using Home Assistant for a few weeks now and I have the same problem. I was wondering if you still have this problem with the latest version of the iOS app.
It’s really annoying since I have automations based on zone enter/exit events and I have to save the settings almost daily in the app.
I’m not sure, but perhaps this is related to restarting Home Assistant. I’ve been adding features to my Home Assistant configuration almost daily and restart afterwards. Maybe you need to save each time after a restart / new configuration update.
I don’t have a problem with notifications, but I still have the problem where the components in Settings aren’t loaded now and then. So have to keep opening Settings, and tapping Save under Connections to keep reloading them again.