Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to reach the Home Assistant cloud. #15221

Closed
gurbina93 opened this issue Jun 29, 2018 · 24 comments · Fixed by #17984
Closed

Unable to reach the Home Assistant cloud. #15221

gurbina93 opened this issue Jun 29, 2018 · 24 comments · Fixed by #17984
Assignees

Comments

@gurbina93
Copy link

gurbina93 commented Jun 29, 2018

Home Assistant release with the issue: Home Assistant 0.72.1

Last working Home Assistant release (if known):
Home Assistant 0.72.1

Operating environment (Hass.io/Docker/Windows/etc.):
hassio 1.3.1

Component/platform: https://www.home-assistant.io/components/cloud/

Description of problem:
My HA Cloud component had been working great with all my devices, suddenly Google started saying my devices are not available and when I check my HA I see I am logged out of the Cloud and whenever I try to connect again I get the follow message:
"Unable to reach the Home Assistant cloud."
Whatever I try, create a new account or sign in, I get the same error. I do have internet connectivity.

I am not getting any other errors and I can connect to my HA via Putty or Web

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

# Example configuration.yaml entry configuring Google Assistant
cloud:
  google_actions:
    filter:
      include_entities:
        - light.kitchen
        - light.kitchen_left
      include_domains:
        - switch
      exclude_entities:
        - switch.outside
    entity_config:
      switch.kitchenlight:
        name: Custom Name for Google Assistant
        aliases:
         - kitchen lights
         - pantry
        room: kitchen

Traceback (if applicable):


Additional information:

2018-06-30 06:05:06 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
2018-06-30 06:05:19 WARNING (SyncWorker_7) [homeassistant.components.media_player.sonos] No Sonos speakers found
2018-06-30 06:05:51 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:05:56 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temperatura is taking over 10 seconds
2018-06-30 06:06:02 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:06:13 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:06:17 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2018-06-30 06:06:23 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:06:34 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:06:45 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:06:56 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:07:07 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:07:18 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:07:29 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:07:40 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:07:51 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:08:02 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:08:13 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:08:24 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:08:35 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:08:46 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:08:57 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:09:08 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:09:19 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:09:30 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:09:41 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:09:52 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:10:03 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:10:14 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:10:25 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:10:35 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:10:46 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:10:57 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:11:08 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:11:19 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:11:30 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:11:36 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_temperatura is taking over 10 seconds
2018-06-30 06:11:41 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:11:52 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:11:57 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2018-06-30 06:12:03 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:12:14 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:12:25 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:12:36 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:12:47 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:12:58 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:13:09 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
2018-06-30 06:13:20 ERROR (MainThread) [homeassistant.components.cloud] Error fetching Cognito keyset: Cannot connect to host cognito-idp.us-east-1.amazonaws.com:443 ssl:None [Try again]
@gurbina93
Copy link
Author

stopping pi-hole solved the issue. whenever pi-hole starts on boot it won't connect to HA Cloud
I am running the pi-hole add-on with the following settings:
{ "log_level": "info", "password": "changeme", "update_lists_on_start": false, "http_port": 80, "https_port": 443, "dns_port": 53, "ssl": false, "certfile": "fullchain.pem", "keyfile": "privkey.pem", "interface": "", "ipv6": true, "ipv4_address": "", "ipv6_address": "", "virtual_host": "", "hosts": [ { "name": "hassio.local", "ip": "here the IP address of my RaspberryPi/Hassio" } ] }

Could this host setting be messing up the connection to HA cloud?

@frenck
Copy link
Member

frenck commented Jun 30, 2018

I have the exact same issue on a Generic Linux installation (Ubuntu 18.04/Bionic).
All other add-ons have a working DNS resolving, except for the containers Home Assistant & Supervisor.

This seems to be the root cause for this issue.

[edit]: Seems to go wrong for all containers running on the host network.

@gurbina93
Copy link
Author

gurbina93 commented Jun 30, 2018

@frenck I have been reading a few posts around, it seems to be a well known issue with the Pi-Hole addon on Hass.io where you have to set a static IP, and set the DNS servers to your router (or better yet, a public DNS server to avoid any loops) in resinOS.

I tried using DHCP reservation and also binding my IP/MAC address with no success, so I gave up and set the static IP and DNS directly on resinOS as recommended on several threads.

I had the Speedtest component running and it slowed down the connection from 100Mbps to 2-3 Mbps while I had issues with Pi-Hole until I set the static IP and DNS.

@frenck
Copy link
Member

frenck commented Jun 30, 2018

@gurbina93 I wrote the Pi-hole add-on 😉

Still there is something not completely as it should be...

@Naesstrom
Copy link

I noticed the same problem in my log tonight, is there anyway to set IP and DNS without moving the SD to a computer?

@willsy555
Copy link

Same issue here, can't connect to HA Cloud suddenly and the most recent change is adding Pi-Hole! @gurbina93 ...can I ask what the details are for the workaround? i.e. set the static IP and DNS directly on resinOS as recommended on several threads.... Do you have a link to what that means?
Thanks very much.
Will.

@gurbina93
Copy link
Author

@willsy555 I am running Hass.io on a Raspberry Pi. You need to set a static IP the OS itself since Hass.io seems to be Docker container running on top of this OS called resinOS (correct me if I am mistaken). For some people simply binding IP and MAC in the router did the trick, apparently.

As I mentioned I am running Hass.io on a Raspberry Pi, if your case is different I might not be able to help since I a typical Windows guy.

What I did was grab the MicroSD card from my Raspberry Pi, plug it into my Windows PC and edit this file with notepad:
system-connections/resin-eth0 (or resin-sample)

Since I only use an ethernet connection this is how my file looks like:

[connection]
id=Ethernet
type=ethernet
interface-name=eth0

[ipv4]
method=manual
address1=192.168.0.100/24,192.168.0.1;
dns=192.168.0.1,8.8.8.8;

192.168.0.100/24 is the static IP I want and 192.168.0.1 is the IP of my router. On the DNS I've seen people using their router IP, ISP DNS or a public DNS like Google (8.8.8.8), CloudFlare (1.1.1.1) and others. In my case I set the secondary DNS to Google DNS.

Here you can find some information on how to edit the connection file, I'd keep it short and remove anything that is not necessary such as the wifi connection.
https://docs.resin.io/reference/resinOS/network/2.x/#setting-a-static-ip

Once you're done insert your MicroSD card back to your Pi, boot it up and you should be good to go.

@willsy555
Copy link

willsy555 commented Jul 2, 2018

@gurbina93 Thank you so much for the detailed explanation. That's perfect... I'm using Hass.io on a Raspberry Pi too, so all should be the same for me... Much appreciated :-). I will give it a try in the next day or two.
Cheers
Will.

@OddmarDam
Copy link

Hi.

I'm running Ubuntu 16.04 server. IPV6 is disabled on all interfaces. Still unable to connect to Home Assistant cloud, cant even create an account.

@IxsharpxI
Copy link

IxsharpxI commented Aug 19, 2018

im having the same issues.. ubuntu 16.04 vm and hass.io

@Qu3uk
Copy link

Qu3uk commented Aug 20, 2018

Can create account, reset password but can't connect. Can't see anything in the logs with the following as well.

# Logger logger: default: warn logs: homeassistant.components.cloud: debug

@Nixellion
Copy link

Ubuntu 16.04, hass.io docker installation, same issue. Server's behind a router with static external IP and static lan IP

@Sephyr0s
Copy link

Same here, any idea on how to fix this?

@IxsharpxI
Copy link

i got an email today to confirm email. but still unable to login

@scfigg
Copy link

scfigg commented Aug 29, 2018

Same here. Ubuntu 16.04 Hassio install. Can't connect to HA cloud or authenticate with Wink. No pi hole installed either. Static IP.

@IxsharpxI
Copy link

ive gotten it to work. but not with hassio. its got to be a hassio issue. im now running docker on a vm and have home assistant in a container.

@Nixellion
Copy link

@lxsharpxl as far as I know that's basically what hass.io does. It installs docker and adds home assistant container and basically just works as a management application. I'm not sure but I think it uses the same homeassistant docker container.

For what it's worth I did install hassio on Ubuntu in docker, so it should be pretty much the same.

I did notice, however, that it requires a domain with SSL certificate, could that be an issue on my end? I was trying it with local address IP 192.168.x.x:8123

@Qu3uk
Copy link

Qu3uk commented Sep 3, 2018

@Nixellion I don't think Cloud required a local ssl as it appears not to require you to expose your instance to the internet.

There is no need for any further configuration or to expose your instance to the internet

Cloud Docs

@Nixellion
Copy link

@Qu3uk Thanks. While working on another issue I found out that my hass docker container can't resolve any domain names, there's some problem with DNS. As described here https://community.home-assistant.io/t/restful-returns-unavailable/66691/10

And here home-assistant/supervisor#448

I don't know how to solve this DNS issue yet.

@xKronyx
Copy link

xKronyx commented Sep 13, 2018

I had the same problem, I did this:
docker exec -it homeassistant /bin/bash
echo "nameserver 8.8.8.8" > /etc/resolv.conf

and it solved my problem !

I did a restart of my linux host and the problem is back, i had to do the modification again.

@Nixellion
Copy link

@xKronyx Thanks for response, but that's exactly what I ended up doing! :) And I think I also wrote that in one of these related threads. Anyway, more = better :)

I do hope docker image will be fixed at some point, and I hope this workaround wont break with updates. I suppose it will though.

borpin added a commit to borpin/hassos that referenced this issue Sep 19, 2018
I found that there is a need to add in the dns and gateway IP addresses otherwise there was no route out.  I note there are a number of issues alive re this routing problem e.g. home-assistant/core#15221
pvizeli pushed a commit to home-assistant/operating-system that referenced this issue Sep 20, 2018
* Update documentation for a static IPV4 address via nmcli

This update documents a method to change to a Static IPV4 address using the NetworkManager CLI (nmcli).

Happy for the formatting to be modified to suit local convention.

I cannot be more specific about how to get into the base OS as I don't know!

* Additional nmcli commands for dns and gateway

I found that there is a need to add in the dns and gateway IP addresses otherwise there was no route out.  I note there are a number of issues alive re this routing problem e.g. home-assistant/core#15221

* Update network.md
@allmoney
Copy link

Same problem right now.

@Qu3uk
Copy link

Qu3uk commented Sep 26, 2018

Looked in to this again a little and still at a loss. I still get nothing logged in the home assistant log file, although I need to try setting the log to trace. I don't use Docker or PiHole, just python virtualenv on centos and cloudflare/google dns.

Looking at the code it appears to be asyncio timing out however the error code mentioned is 502 suggesting a bad gateway but without detailed logs I can't work it out or reconstruct the url its using.

Line 69

I do have a static IP and for me this has never worked.

@nefilim
Copy link

nefilim commented Oct 13, 2018

Having the same problem trying to integrate with Nest API - using hass.io image running on Raspberry Pi.
I'm assigning the host a static IP and for DNS my own caching DNS server + google's publish DNS as secondaries.

@ghost ghost added the in progress label Oct 29, 2018
@ghost ghost removed the in progress label Oct 29, 2018
@home-assistant home-assistant locked and limited conversation to collaborators Feb 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.