I have just succesfully rebuilt my hassio install following the death of the memory card on the RPI and tried to reconnect the mobile app at which point I get Error: invalid client id or redirect uri and then Authentication Controller Error 1 as per the following:
I am not using an external URLand I am only connecting across an internal network. I have tried all combinations of URI, URL, IPs and auth settings (removed the app and reinstalled) and results are the same error messages as above.
The problem appears to be with the App. I have tried with an ipad, initially the App connects and I can see the dashboard. After a short time it bails out and the previously mentioned error occurs.
When I connect using safari or firefox on the phone or ipad everything works as expected - but the App does not, there is definitely a problem with App.
Are there debug logs available within the App or elsewhere to enable better diagnostics?
There is no logging function built into the version you are on, 1.5. May I suggest you try out the 2.0 beta which has an entirely new way of interacting with Home Assistant which should fix these issues?
Whereās as if I use all is ok
192.168.x.x:8123/lovelace/default_view
I assume the app is built on the underlying safari code (but Iām not a coder so itās a pure guess) given its working ok in safari I can only assume something isnāt correct in the way itās trying to authenticate in the app
Can you please update to 0.92.2? It finally contains logging improvements that will give you a better idea of why you are receiving the āError: invalid client id or redirect uriā error.
Iām having the same issue with Hass.io and just updated to 0.92.2. The logs say: OS error while looking up redirect_uri https://home-assistant.io/iOS/beta-auth: Try again
I have updated to 92.2, the original error persists on my iPhone and I get the following in the HA log
2019-05-06 17:10:28 ERROR (MainThread) [homeassistant.components.auth.indieauth] OS error while looking up redirect_uri https://home-assistant.io/iOS: Try again
Without doing anything the hass companion 1.5.1 is running (again) on the iPad although it thinks the HA version is 91.3 ?!?!
Ok Iām struggling here, I run hassio and as far as I can tell it does not have IPV6 enabled within the container (not present in the detail of Ifconfig)
Can you give any pointers if Iām looking in the wrong place ?
Iām getting the same errors too. Tried 1.5.1 and beta 2.0 of the iOS app, and I have IPv6 disabled on my router. Iām running Home Assistant on a Mac Mini. Any help would be appreciated.
Oh also, the problem here isnāt with your device communicating to Home Assistant, itās with Home Assistant trying to download the page at https://home-assistant.io/ios/beta-auth.
Yes, I know there are several solutions to this, and some of these I can implement and probably will. But does this mean that if youāre a BT customer (lots of people in the UK are) and you are not a Nabu Casa subscriber (I am) that you wonāt be able to use the iOS Companion app?
Incidentally Iāve just tried my Nabu Casa URL in the latest version of the Beta (58) and get a SSL error in the app. Sorry Robbie!
After some thinking and debugging over the weekend I appear to have found the source of my problems and fixed my issue.
Drum roll, cymbal crashā¦ it was a network problem, not ipv6 but ipv4!!
I use hassio, the new version of hassio uses hassos, to set the network you can reserve a DHCP address, create a network config file or use the nmcli in docker. For expediency I initially used the nmcli and set up my network stack. While this created a functioning install of hass, it wasnāt really functioning?!?!
So what tipped me off? Following a reboot yesterday I have started to see a number of internet integrations failing, I immediately suspected router issues etc but worked out quickly that the smoking gun was back with hass, while it had the correct network info it wasnāt working correctly. So long story short I followed the instructions for option 2 above and ābangā everything is now functioning as it should.
I think there may be a problem with the way the host passes network details to the container with my version of hassio BUT this is an assumption rather than a position of knowledge and likely a glitch, however the hard coded method has resolved the issues.
