iOS devices not getting push ID

[junior466]

Home Assistant release with the issue:

0.87.1
Last working Home Assistant release (if known):

0.87
Operating environment (Hass.io/Docker/Windows/etc.):

Ubuntu 16.04
Virtual environment
Component/platform:
iOS

Description of problem:

iOS component fails to get push ID.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

ios:

Traceback (if applicable):

The notify.ios platform was loaded but no devices exist! Please check the documentation at https://home-assistant.io/ecosystem/ios/notifications/ for more information

Additional information:

I've attempted the steps described here twice as a method of troubleshooting but had no success.

Here's what my app looks like:

Screenshot 1
Screenshot 2

[WilkyF18]

Same issue. My iPhone which I registered when running 0.84 has a push notification ID.

However, my wife's iPhone that I setup today while running 0.87 does not get a push notification ID.

[aram535]

Same situation here, followed the same steps. Running 0.87.1 in docker. 2 iPhones, 3 iPads all same.

[tunip]

Same issue here. Running 0.87.1 in Docker. 2 iPhones.

[marcotini]

Same, Docker with 1 iPhone working and 2 not.

[hotsnow]

same, 0.87.1, iPhone.

[rhadamantys]

dito. iPhone 6s with iOS 12.1.4 and Home Assistant 0.87.1 on Raspberry

[NPYK]

ios 12.1.2 iphone xr ,HA 0.87.1, I also reproduce this issue.

[MichaelRoxin]

Same here, Iphone X HA 0.871

Wife is on Iphone 6 plus and works perfectly.

[robbiet480]

Will look into this shortly. Can y'all provide your app version? (you can find it on Settings -> About under the logo)

[robbiet480]

Nevermind, this has been fixed, apologies y'all. Just force restart the app and it should register for notifications. Let me know if you're still having issues.

[eugenelai]

Wooo confirmed fixed! @robbiet480 out of curiosity can you outline the issue?

[robbiet480]

@eugenelai Had to make some changes to support the 2.0 beta and while they worked fine for beta and dev apps it silently broke the production app. A quick one line fix later and we were back in business.

[eugenelai]

Cheers!!!!!!!11

[aram535]

@robbiet480 I got the phones to generate a push id now -- thanks for that. Now the push ids are not getting into HA (running 0.88 now).

[lancelon]

Anyone know if it's possible to setup the iOS companion app on the DuckDNS platform? I'm at working trying to figure out why notifications adamantly will not work anymore despite me changing/trying almost everything and I realised the one constant so far is that my phone and my HA instance are on separate IP networks...I've been using the DuckDNS addon to 'remote in' to my system and maybe (just for setup) you have to be on the same network??

[TomBrien]

@lancelon, is you’re problem the original issue here? Do you get the push-ID? What service are you sending to? Have you tried sending from dev tools?

[lancelon]

I have to confess my problem isn't the original issue, I do get push IDs, I just never get notifications on the device and the list of services on the HA side never shows in the list 'notify.mobile_app_[mydevice]'
Mobile app otherwise works as advertised. And the odd thing is, it worked when I was on the various beta apps! I wondered if it might all suddenly start working if my phone and the HA instance were on the same network rather than DuckDNSing in. I know that notifications CAN work through DuckDNS but maybe setting up/onboarding can't successfully be done via DuckDNS...?

[TomBrien]

If you don’t see it in the services you probably need to restart home assistant

[lancelon]

Hi Tom

I wish it were that simple! Tried that lots of times. My new best idea, which I’m going to try tonight, is attempting the onboarding from the lan rather than duckdns. Few webhook errors in my logs so something’s definitely amiss.

Thanks

On 28 Jan 2020, at 17:51, Tom Brien [e-mail] wrote:

If you don’t see it in the services you probably need to restart home assistant

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.