I just encountered this problem and was able to figure out that I got the 404 response if I included a trailling slash on my URL.
Didn’t work: https://server.local:8123/
Did work: https://server.local:8123
I was entering the URL manually and not allowing the app to scan the network for the HA instance.
Jason
The app finds a local 8123 url and I let it use that rather than enter anything manually. But I still get the 404 error. I have not tried anything like disabling SSL on the server side. Will probably just use Safari (which works fine) until a fix gets pushed out.
You are experiencing something that will likely never have a fix pushed out as likely it is a wrong config in your HA or network.
We haven’t been able to reproduce all sources of a 404. Those we identified are the trailing / on the url (and base_url) in configuration.yaml as well as missing websocket support in nginx setups.
This was the answer for me! Thanks so much.
Hello. I have the same issue as others.
I have tried commenting out SSL in my yaml file and using a local ip_address. I can access HA via the local address in a safari browser but it still doesn’t work in the companion app. I get the same 404 error everyone else is getting. I then changed base_url to be my local url and that didn’t help. Finally, I completely commented out the http section of my yaml. This allows me to log into HA without any password locally. No problems from a browser. But, same 404 error.
I saw one comment saying there will not be a fix for this. I’m a little lost as to why it worked one day and not the next. Any ideas on what I look at next if there is something wrong with my configuration?
Thanks!
Is it possible you’re running a version of HA older than 0.95?
Yes, I am running 0.74.2. It has been stable for me so I never upgraded.
I assume this means I need to upgrade.
Thanks for quick response!
Is there a recommended place to read about upgrading? I’m assuming things will break during upgrade.
Thanks.
I’ve the same problem.
Any solution?
@zsoltare you manually specifying the address? If so please make sure your not including a trailing \. Check none of the common problems listed here describe your situation
HA older than 0.95?
Arg… So unfortunately I auto updated the IOS app, and I am not yet on 0.95.
Is it possible to downgrade the app to a working one? Or is this the time I have to drag my HA up to date. Not a good time to do that for me.
@ olbjan this problem occurs regardless of the configuration. If one has an external https URL certificate that renames the duckdns one, then the port is 443 and the server port is 8123 (or 8124 in my case). And regardless of whether you put the external URL in with or without port number, or using port number 443, 8123 or 8124 the problem happens. So I am not sure it is as simple as you suggest.
However, I am running a HA version below 0.95, so I will upgrade and see if that fixes it.
Bruce, if you are successful with an upgrade fixing this, can you please post here. Thanks!
I’ve written a rough guide to how to set up networking for external access properly and you can find it here: https://companion.home-assistant.io/en/troubleshooting/networking
Not trying to say what you’re doing is wrong, just trying to get a supportable basic set of settings for non-technical users of HA.
While I definitely see the problem on the IOS app, I noticed that when I install the Android app on my Android phone, that app works perfectly with my configuration. (I have not changed anything on the server side and I am still back at HA 89.1. Do the IOS and Android apps talk to the server differently?
Jan –
Great writeup on networking for external access. One request, some of us (at least as I understand it) need to set up an NGINX connection so that non-powerful internal devices can talk to HA without the encryption, for example see https://help.konnected.io/support/solutions/articles/32000023964-set-up-hass-io-with-secure-remote-access-using-duckdns-and-nginx-proxy?fbclid=IwAR1fEvULSCM40t200PKTxfp_THZ8CJvvYTGCZUqiNONh_Jv3lShxHL-MT98. Could you add something to your writeup on this topic? (Or comment on whether there is a better way to solve this problem).
You’re in luck, I have konnected.io myself and use nginx for that reason.
So a section on reverse proxies will be added.
SredniV Jason tip worked on my iOS (Nabu Casa url)
Didn’t work: https://server.local:8123/
Did work: https://server.local:8123
No more 404, and no other actions taken (like reinstalling the app, etc).
Not sure if its appropriate to post here since I am getting a different error but I am fighting with this:
“Error
Response status code was unacceptable: 500.”
Running home assistant 99.3, installed as hassbian (not sure if it makes a difference or not)
Any help would be appreciated
Thanks
That’s the solution that worked for me, make sure not to use a trailing slash!
Thanks @SredniV
Thanks man that helped 