Do you have an “.ios.conf” file in your /config folder?
Is so, rename it “.ios.conf.bak” and try discovery again.
No, I don’t have a file “.ios.conf” in my /config folder. Also manually creating does also not help.
I followed all steps you’ve suggested in this thread. I see this behavior on 2 iOS devices, hence I guess it has something to do with my hassio installation. It looks like something prevents the creation of the “.ios.conf”-file.
Further hints:
I’m getting an 405-error if I’m trying to push my current location. (iOS App 1.5.0 32; hassio 0.84.2)
I’m on HassOS 1.13 and running the installation behind an NGINX Home Assistant SSL proxy. (valid SSL)
I’ve updated system and app today, but still facing the same issue. Anything more I can do?
No one who can help me to debug this behavior?
I had exactly the same problem and found another thread with a solution that worked for me (adding api_password in the http section of configuration.yaml) plus ios:. With luck, we same fix might work for you. The link is:
1 Like
The latest version of the app does not use legacy authentication so that fix is no longer valid.
+1 for getting this when pushing location:
This is with latest version (0.86.2).
In the HA log there is nothing.
I tried to configure the ios app to not use legacy authentication, but it always switches it back on.
Also if I remove the legacy api_password in config yaml then it seems the app cannot even detect the ios component and hence disables device tracker etc anyway… 
IMO What HA urgently needs is a user management UI which allows linking multiple devices from multiple trackers to a given user, and then tracking that user for occupancy and zones. The current approach with known_devices yaml is quite cumbersome.
1 Like
The latest version of the app does not use legacy authentication
It seems the latest version uses the new auth for the UI login - i.e. to display the HTML UI, but it needs the legacy API to support the IOS component.
Because I’m curious: Does Hassio create a ios.conf file?
TBH not sure. I upgraded to hassio ~1 yr back, but maybe the ios conf predated that and never got cleaned up…
1 Like
Also I think possibly this thread should be under the IOS category. Seems like it could be a bug in the hass/ios app infrastructure and maybe the app author (@robbiet480) can help us if its in the correct category?
I‘ve moved the thread to the iOS category as suggested by you.
Hi Folks.
Still seeing this 405 error whenever I try and push location from ios app to HA(ssio).
Is anyone else seeing it? Is it a known defect for ios?
I wonder if maybe its because I have some old entries in my core.device_registry file.
What is the official sanctioned method to clean up this file?
Having the same issue. Have HASSIO 0.87.0 running in a VM with latest version of the iOS app and a valid certificate. Can login and everything. But my phone doesn’t show up in Hass.io
I was having this same issue after upgrading to 0.87.0 (large jump from 0.73 or something) and after moving my known_devices.yaml file (effectively deleted it), deleting ios: from my configuration.yaml file, removing the Home Assistant IOS intergration from Configuration -> Integrations, resetting the app settings, logging in on the app, then reenabling the Home Assistant IOS configuration, I’m able to connect correctly and update my location.
From trying so many different things in random orders, I can’t say if it came down to one thing or all those things.
1 Like
Will try this.
Thanks
BTW I don’t think deleting known_devices.yaml contributes to your success. I already did that and still have the issue.
Just deleted ios from config and removed the integration… rebooting now.
I found when I re-enabled the integration it still had the same three devices configured.
Also location pushes still not working
Weirdly the other data such as iOS version, battery level, charging status etc seem to update OK.
Its just location that does not…
Now working 
I think it was not re-enabling ios in config (I though that the ios integration would do that without needing to re-enable ios: in config)