I’ve tried that a dozen times. It makes no difference. I’ve commented it out along with everything in the ios.yaml file. It just contains my ios actionaable push notifications.
I have no references to ios anywhere.
I’ve tried removing discovery: and it still looks for the ios component and creates the error.
There’s no iso.conf file and no hidden file either.
If you read further than what you quoted you will see that it says for subsequent starts you need ios: in config yaml file.
I suggest:
Comment out the ios: line in config and remove that include ios.yaml part altogether.
Remove the ios integration.
Reset the app on your iOS device.
Force close the app
Restart home assistant.
Uncomment ios: from config yaml
Restart home assistant.
Run the app (the BETA version) and authenticate with Home Assistant.
Have a look and see if it has automatically added the integration.
Have a look for .ios.conf a hidden ‘dot’ file on /config/ folder.
In the app, when you logon, don’t use any advanced settings. Just input your Home Assistant URL and click save and it should lead you through logging onto home assistant.
After first logging on I normally force close and load again. Check the settings>notification settings and click on the push I’d one. You should see the same push ID there as is in the .ios.conf file - it MIGHT take a few minutes for it to sync up.
You should also be able to push using the up arrow in the bottom left corner your location from ios to home assistant.
So you do have an .ios.conf file… what is in that? Can you show your config yaml? Have you tried manually adding the integration for ios? (Config->integrations)
The .ios.conf file is empty.
The config.yaml is in the first post.
I have tried manually adding the integration. To no avail.
So, up early this morning and I set about creating a new SD card for a new instance of HassIO.
Running 2 RPis, I then copied over the contents of each file and element of config.yaml one at a time, restarting between each and checking if the iOS component was still loaded and that the app was still showing the component on restart in an effort to identify where it breaks…
I’ve just finished and…
… it seems to be fine.
So, no further forward in my understanding of what caused this.
OK so are you able to access your HA externally at ALL even from a Web Browser? Your 10.0.x.x IP address looks to me like CGNAT - carrier grade NAT and if so, you do not have a real routable IP address and external access will be impossible. Does your ISP provide IPv6 native/dual stack?