I am using SSL. It won’t connect on 443 - I must specify 8123. It is in my router but I get no connection to anything on 443.
I’m using https://mydomain.duckdns.org:8123 - works fine on 4G, WLAN etc. all working.
Since deleting .ios.conf, I now only get the away for both devices. Other levels are no longer there. Also get the password type prompt on all devices…
I wonder if I should kill the ’ and -?
Weird… you aren’t specifiying 443 correct? Just your address? The s in https automatically uses 443 without specifying it?
Also the base_url under http: section of config also has no port number correct?
It does have a port number :8123
It will not connect without this!
I have to use the port number everywhere or it won’t connect.
My router used to connect to it’s internal interface if I just used https:// so I switched that off in the router (set it to not allow connections from the internet) Now I get a connection refused error. Specifying 8123 works everywhere.
I do have 80, 443 and 8123 forwarded in my router to the Pi IP address (static)
Your router should be forwarding port 443 to 8123 on the Pi. You should not need 8123 exposed externally on your router.
Yeah should. It does not work! Not sure how much more clearly I can state it.
Sorry, I missed part of your earlier post. A bit surprising, but I use a non-standard port in my configuration, so I also include the port (along with https:) in my ios app configuration. Works like a charm. You can just remove the 443 re-direction and possibly 80 as well. At least with hass.io and the duckdns add-in, it works fine.
Back to your original challenge. If a standard web browser works using your external https://url:port, then I would delete the app off of your phone, and re-install it. That seemed to clear up some challenges for me.
Good idea. I actually did that yesterday…
No difference.
I am wondering if I should change David’s-iPad to davids_ipad - dunno if that is possibly screwing it up. YAML can be a bit of a bitch I find although it’s validating ok.
You may be on to something. I ran into someing like this when I renamed a zwave device. It was converted with an extra underscore, and took me forever to spot it.
Well I just edited my iPad and it’s unchanged. It’s somewhat weird. I am wondering if there is somewhere else it’s storing stuff.
I just edited the .ios.conf and it only had the iPad in it. So the AWAY is coming from the known_devices.yaml…
I use bluetooth tracking (not BLE) with our iphones to do home/away tracking. It also uses the known_devices.yaml file. I didn’t implement the iOS app until recently.
Well weird.
I deleted the known devices file
I changed the name in HA to exclude - and ’
Then restarted HA and it found my iPhone (I also deleted the app again there)
Now it’s recreated the known devices and I’m getting both devices as home.
No tracking of battery status or level though. Maybe that will pop back in?
My needs are simple for tracking - just home or away. So I use the bluetooth tracker, since we always have bluetooth on our phones.
I had the same error “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” untill I enabled notifications in the home assistant app, after that it worked fine.
