Cannot connect using HA Companion app for Android v1.2.0

Mobile Apps Home Assistant Companion for Android
1

Configuration:

  • Home Assistant 0.103.0
  • Running Hass.io in Docker on a NUC with Ubuntu 18.04
  • default_config: appears in my configuration.yaml
  • Nabu Casa Cloud remote access is enabled, and works fine in Chrome for Android on the same device (https://verylongstring.ui.nabu.casa)
  • Installed Home Assistant app from Play Store, version 1.2.0

Steps to reproduce:

  • On my home network, I launch the app for the first time. It does not detect my local HA instance.
  • I choose to enter address manually, and paste in my nabu.casa remote URL
  • I see the following screen:
    Screenshot_20191213-095553_2
    Screenshot_20191213-095553_21080Ă—543 53.7 KB
  • After a few seconds, I see the following updated screen:
    Screenshot_20191213-095602_2
    Screenshot_20191213-095602_21080Ă—543 56.7 KB

    ( Error: invalid client id or redirect uri )
  • I check the HA log and see a new error: Timeout while looking up redirect_uri https://home-assistant.io/android

Any advice greatly appreciated. Thanks!

1 Like
2

I’m getting a similar error on my daughters phone.
I have added mine(OnePlus 6), my fiance(OnePlus 5) and my sons(OnePlus 3), my daughters(OnePlus 3) gets the following error after adding the url:

IMG_20191214_091121_01
IMG_20191214_091121_01360Ă—640 17.4 KB

Any ideas?
Tried to wipe cache, and reinstalling the app. without any luck.

Tried both on the Wifi and on the cellular net.

3

Hey @wrkn! had the same issue, and while investigating came across this: https://companion.home-assistant.io/en/getting_started/migration.html#4---common-problems

specifically the first point there, my Home Assistant runs in a Docker and resolves home-assistant.io to an IPv6 address, however IPv6 connectivity was broken.

Once I fixed IPv6 connectivity in the containers (I used https://github.com/robbertkl/docker-ipv6nat) login with the app using the Nabu Casa URL worked as expected.

Hope that helps.

1 Like
4

Thank you for the suggestion!

Unfortunately, quickly adding & running that ipv6nat container didn’t seem to make a difference and I really don’t know enough about ipv6 to even troubleshoot or diagnose the issue. Rather than banging my head against the wall wondering what “broken” actually means, I just disabled ipv6 on my server using the following:

Works now!