Push notifications in the iOS app (1.5) have become incredibly unreliable for me. Some days it works some days it doesn’t. I can update the push settings in the app in the morning and have messages fail by evening. Then return to working again without updating the push settings.
If this wasn’t bad enough, when a notification to my phone fails it prevents further execution of automation actions. I’ve put all the notifications I can at the end of my actions but some have conditions in the actions that require the notification to go first. I even wrote a script to handle the notification instead. However it seems if the script fails to send the push message the actions in the automation that called the script still halt!
I’ve tried a few things to troubleshoot this, like only using wifi, or only using cellular. Can’t really spot any pattern.
So, I’m looking for better notification options if you have a suggestion.
I have no issues with iOS notifications, so I’ve stopped using pushbullet that I was using prior.
The main reason for me is that with iOS notifications I can actually take action and act upon that feedback, as opposed to a one way notification that would then require me to unlock the phone, open the HA app and locate the tab/resource that I want to act upon.
I’m happy with telegram as I was already used to use it for everything else (including work related notifications). A few months ago I also discovered mqttwarn and found to be very useful since I can change the notification type/channel/app without have to touch/restart HA.
My work and home are very close together. A block apart. The app can’t cope with this. It’s a known bug. If you imagine a lot of users are Americans who drive great distances between home and work. Other users, like me, walk to work, and it takes me about 80 seconds.
Ah yes I get what you mean (I too face these problems with areas too close to each other). I am considering using ibeacons for short distances. Might be something for you.
Same, never used them, but they sound very promising for what I want. I want lovelace views to change depending on the room you are in (using a state switch). If I am correct then this would be possible with ibeacons.
So I got telegram working, nice little bot who could message a system or general chat group. Then out of the blue the groups were migrated to super groups and the chat ids changed.
@tom_l You are the only person who has ever reported notification failure behavior like this. Have you tried reinstalling the app? Have you switched over to the 2.0 beta? Do you have some weird device configuration that would cause your device token (generated by Apple) to change? If you can hop on Discord at some point I can totally help you debug this one on one including looking at server logs to see exactly what’s happening.
I’m pretty sure I don’t. It’s just a bog standard Hassio NUC image talking to the v1.5 app using DuckDNS.
Thanks Robbie, but I spent a considerable amount of time commenting out all my iOS notifications and I’m not likely to put them back. Not just because of the problems I’ve been having but also because Telegram (which has not missed a beat) is cross-platform which works well for my guests with Android phones.
I’m still using the iOS app on my iPad and iPhone for tracking and to view the front end. One thing I noticed is that if I have not used the app for a few hours the first time I bring up the app (from background or starting it) authentication fails. Then the app works as expected. This happens for both my devices. Like this evening on cellular data:
2019-05-28 17:27:03 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 1.152.110.110
2019-05-28 17:27:04 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 1.152.110.110
2019-05-28 17:27:04 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 1.152.110.110
Right after that failed login it was working fine.
If it happens on my home network my router’s (EdgerouterX) local address is reported as the failed IP address, not the iDevice’s IP address.