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

Cloud / Nabu Casa Remote not working: "Home Assistant is starting, not everything will be available until it is finished." #41625

Closed
alexsands opened this issue Oct 10, 2020 · 11 comments · Fixed by NabuCasa/hass-nabucasa#197
Assignees

Comments

@alexsands
Copy link

The problem

After restarting Home Assistant, it hangs on "Home Assistant is starting, not everything will be available until it is finished." permanently. The Nabu Casa Remote UI is unavailable, and the "Cloud" menu option in the Configuration menu is not visible (i.e. http://homeassistant.local:8123/config/cloud/ does not load).

With some debugging, I found that I can bypass the issue by removing cloud: from my configuration.yaml. Home Assistant then starts normally and everything works (without remote UI access, obviously), but adding cloud: back causes this issue once again.

This issue started happening suddenly on Oct. 10th, with no known changes between when it was working and when it started failing.

There are others having this same problem on the community forum. Link to that commentary here.

Environment

  • Home Assistant Core release with the issue: 0.116.2
  • Last working Home Assistant Core release (if known): Also happened on 0.115 (I tried to upgrade to see if the problem was fixed). I've only gotten this issue once or twice so not sure what the last clean release was
  • Operating environment (OS/Container/Supervised/Core): HassOS 4.13 in VirtualBox on a Mac Mini
  • Integration causing this issue: Core? Or potentially hass_nabucasa
  • Link to integration documentation on our website:

Problem-relevant configuration.yaml

###############################################################################
# DEFAULT CONFIG ELEMENTS
###############################################################################

homeassistant:
  customize: !include customize.yaml

cloud:

mobile_app:

frontend:
  themes: !include_dir_merge_named themes

lovelace: !include lovelace/lovelace.yaml

config:

discovery:

map:

history:

logbook:

updater:

system_health:

python_script:

sun:

ssdp:

zeroconf:


###############################################################################
# INCLUDES
###############################################################################

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
light: !include lights.yaml
scene: !include scenes.yaml
input_select: !include input_selects.yaml
input_boolean: !include input_booleans.yaml
sensor: !include sensors.yaml
binary_sensor: !include binary_sensors.yaml
zone: !include zones.yaml

Traceback/Error logs

2020-10-10 15:59:15 ERROR (MainThread) [hass_nabucasa.iot] Unexpected error
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/hass_nabucasa/iot_base.py", line 108, in connect
    await self._handle_connection()
  File "/usr/local/lib/python3.8/site-packages/hass_nabucasa/iot_base.py", line 147, in _handle_connection
    await self.cloud.auth.async_check_token()
  File "/usr/local/lib/python3.8/site-packages/hass_nabucasa/auth.py", line 172, in async_check_token
    await self._async_renew_access_token()
  File "/usr/local/lib/python3.8/site-packages/hass_nabucasa/auth.py", line 199, in _async_renew_access_token
    await self.cloud.run_executor(cognito.renew_access_token)
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.8/site-packages/pycognito/__init__.py", line 617, in renew_access_token
    refresh_response = self.client.initiate_auth(
  File "/usr/local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/usr/local/lib/python3.8/site-packages/botocore/client.py", line 633, in _make_api_call
    request_dict = self._convert_to_request_dict(
  File "/usr/local/lib/python3.8/site-packages/botocore/client.py", line 681, in _convert_to_request_dict
    request_dict = self._serializer.serialize_to_request(
  File "/usr/local/lib/python3.8/site-packages/botocore/validate.py", line 297, in serialize_to_request
    raise ParamValidationError(report=report.generate_report())
botocore.exceptions.ParamValidationError: Parameter validation failed:
Invalid type for parameter AuthParameters.REFRESH_TOKEN, value: None, type: <class 'NoneType'>, valid types: <class 'str'>
2020-10-10 16:00:18 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
2020-10-10 16:00:18 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 80 seconds
2020-10-10 16:01:41 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
2020-10-10 16:01:41 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 80 seconds
2020-10-10 16:03:04 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
2020-10-10 16:03:04 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 80 seconds
2020-10-10 16:04:27 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
2020-10-10 16:04:27 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 80 seconds
2020-10-10 16:05:50 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
2020-10-10 16:05:50 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 80 seconds
2020-10-10 16:07:13 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
2020-10-10 16:07:13 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 80 seconds
2020-10-10 16:08:03 ERROR (MainThread) [hass_nabucasa.iot] Unexpected error
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/hass_nabucasa/iot_base.py", line 108, in connect
    await self._handle_connection()
  File "/usr/local/lib/python3.8/site-packages/hass_nabucasa/iot_base.py", line 147, in _handle_connection
    await self.cloud.auth.async_check_token()
  File "/usr/local/lib/python3.8/site-packages/hass_nabucasa/auth.py", line 172, in async_check_token
    await self._async_renew_access_token()
  File "/usr/local/lib/python3.8/site-packages/hass_nabucasa/auth.py", line 199, in _async_renew_access_token
    await self.cloud.run_executor(cognito.renew_access_token)
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.8/site-packages/pycognito/__init__.py", line 617, in renew_access_token
    refresh_response = self.client.initiate_auth(
  File "/usr/local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/usr/local/lib/python3.8/site-packages/botocore/client.py", line 633, in _make_api_call
    request_dict = self._convert_to_request_dict(
  File "/usr/local/lib/python3.8/site-packages/botocore/client.py", line 681, in _convert_to_request_dict
    request_dict = self._serializer.serialize_to_request(
  File "/usr/local/lib/python3.8/site-packages/botocore/validate.py", line 297, in serialize_to_request
    raise ParamValidationError(report=report.generate_report())
botocore.exceptions.ParamValidationError: Parameter validation failed:
Invalid type for parameter AuthParameters.REFRESH_TOKEN, value: None, type: <class 'NoneType'>, valid types: <class 'str'>
2020-10-10 16:08:37 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
2020-10-10 16:08:37 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 80 seconds

Additional information

@fugly1967
Copy link

Same issue - needed to revert to 0.115.6

@probot-home-assistant
Copy link

cloud documentation
cloud source
(message by IssueLinks)

@probot-home-assistant
Copy link

Hey there @home-assistant/cloud, mind taking a look at this issue as its been labeled with an integration (cloud) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

@alexsands
Copy link
Author

Just tried to downgrade HA Core to 0.114.4, which seems to have brought back the "Home Assistant Cloud" option in the Configuration menu again. But when I try to log in to Home Assistant Cloud, I now get:

Unable to reach the Home Assistant cloud.

@cogneato
Copy link

@acsands13 is this a vm? Can you share the output of ha dns info from the ssh add-on terminal?

@redoxf
Copy link

redoxf commented Oct 14, 2020

I too have this issue, I suspect the Home Assistant cloud starts sooner than My AdGuard addon.

Are you guys using AdGuard or Pi-Hole add ons on the same computer ?

@alexsands
Copy link
Author

@acsands13 is this a vm? Can you share the output of ha dns info from the ssh add-on terminal?

@cogneato Yes, this is running in VirtualBox on a Mac Mini. Pasted the "System Health" info at the bottom of this comment for reference.

Here's the output of ha dns info:

host: 172.30.32.3
locals:
- dns://192.168.1.254
- dns://2600:1700:281:6280::1
servers: []
version: "9"
version_latest: "9"

And here are my DNS logs under Supervisor → System:

[INFO] 172.30.32.1:45780 - 11310 "A IN api.github.com. udp 32 false 512" NOERROR qr,rd,ra 62 0.014717107s
[INFO] 172.30.32.1:42996 - 43381 "A IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 58 0.018329437s
[INFO] 172.30.32.1:42996 - 43552 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 123 0.020963659s
[INFO] 172.30.32.1:57469 - 9002 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 131 0.011984467s
[INFO] 172.30.32.1:57469 - 8838 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 219 0.013166977s
[INFO] 172.30.32.1:57657 - 2141 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000075101s
[INFO] 172.30.32.1:57657 - 2335 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000038771s
[INFO] 172.30.32.1:35064 - 7007 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.00007715s
[INFO] 172.30.32.1:35064 - 7184 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000041271s
[INFO] 172.30.32.1:59645 - 28421 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000072129s
[INFO] 172.30.32.1:59645 - 28581 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000041796s
[INFO] 172.30.32.1:57470 - 55623 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074663s
[INFO] 172.30.32.1:57470 - 55802 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000039484s
[INFO] 172.30.32.1:54512 - 20267 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000075608s
[INFO] 172.30.32.1:54512 - 20466 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000042579s
[INFO] 172.30.32.1:37481 - 4528 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 131 0.012012793s
[INFO] 172.30.32.1:37481 - 4331 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 219 0.012997525s
[INFO] 172.30.32.1:46441 - 12929 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 123 0.014772975s
[INFO] 172.30.32.1:46441 - 12740 "A IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 58 0.021156088s
[INFO] 172.30.32.1:45257 - 31681 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000076923s
[INFO] 172.30.32.1:45257 - 31870 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000040232s
[INFO] 172.30.32.1:47029 - 16466 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074447s
[INFO] 172.30.32.1:47029 - 16675 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000040249s
[INFO] 172.30.32.1:38379 - 38876 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000073734s
[INFO] 172.30.32.1:38379 - 39077 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000045048s
[INFO] 172.30.32.1:44307 - 9625 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074891s
[INFO] 172.30.32.1:44307 - 9805 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000040205s
[INFO] 172.30.32.1:51313 - 19320 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000075305s
[INFO] 172.30.32.1:51313 - 19498 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000047447s
[INFO] 172.30.32.1:60467 - 51001 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 219 0.012211473s
[INFO] 172.30.32.1:60467 - 51153 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 131 0.012812221s
[INFO] 172.30.32.1:37744 - 54769 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 219 0.015956376s
[INFO] 172.30.32.1:37744 - 54941 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 131 0.016666s
[INFO] 172.30.32.1:35891 - 63372 "A IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 58 0.015658453s
[INFO] 172.30.32.1:35891 - 63559 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 123 0.01598179s
[INFO] 172.30.32.1:37021 - 52161 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 219 0.015074592s
[INFO] 172.30.32.1:37021 - 52353 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 131 0.016071507s
[INFO] 172.30.32.1:59438 - 29638 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074795s
[INFO] 172.30.32.1:59438 - 29813 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000040852s
[INFO] 172.30.32.1:50456 - 27995 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000073748s
[INFO] 172.30.32.1:50456 - 28165 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000041939s
[INFO] 172.30.32.1:58626 - 18898 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000075063s
[INFO] 172.30.32.1:58626 - 19097 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000041517s
[INFO] 172.30.32.1:39342 - 13172 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074367s
[INFO] 172.30.32.1:39342 - 13342 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.00004667s
[INFO] 172.30.32.1:33330 - 51484 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000075302s
[INFO] 172.30.32.1:33330 - 51680 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000042312s
[INFO] 172.30.32.1:41278 - 59103 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 131 0.011533555s
[INFO] 172.30.32.1:41278 - 58957 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 219 0.012506917s
[INFO] 172.30.32.1:48391 - 60658 "A IN accounts.spotify.com. udp 38 false 512" NOERROR qr,rd,ra 168 0.012955897s
[INFO] 172.30.32.1:48391 - 60850 "AAAA IN accounts.spotify.com. udp 38 false 512" NOERROR qr,rd,ra 180 0.013483946s
[INFO] 172.30.32.1:33010 - 45626 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 123 0.011673944s
[INFO] 172.30.32.1:33010 - 45434 "A IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 58 0.019568072s
[INFO] 172.30.32.1:48603 - 2588 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000073521s
[INFO] 172.30.32.1:48603 - 2756 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000041091s
[INFO] 172.30.32.1:37775 - 20313 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000075101s
[INFO] 172.30.32.1:37775 - 20483 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000043886s
[INFO] 172.30.32.1:43112 - 19338 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000072751s
[INFO] 172.30.32.1:43112 - 19540 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000038329s
[INFO] 172.30.32.1:52003 - 10430 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074252s
[INFO] 172.30.32.1:52003 - 10621 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000039492s
[INFO] 172.30.32.1:46659 - 62569 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000073341s
[INFO] 172.30.32.1:46659 - 62757 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000042193s
[INFO] 172.30.32.1:60709 - 26875 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 131 0.011368128s
[INFO] 172.30.32.1:60709 - 26683 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 219 0.012312902s
[INFO] 172.30.32.1:53887 - 35989 "AAAA IN api.spotify.com. udp 33 false 512" NOERROR qr,rd,ra 150 0.010823878s
[INFO] 172.30.32.1:53887 - 35788 "A IN api.spotify.com. udp 33 false 512" NOERROR qr,rd,ra 138 0.011953052s
[INFO] 172.30.32.1:47045 - 37138 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 123 0.011845699s
[INFO] 172.30.32.1:47045 - 36972 "A IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 58 0.019762869s
[INFO] 172.30.32.1:49181 - 39789 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 131 0.013114739s
[INFO] 172.30.32.1:49181 - 39618 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 219 0.013707299s
[INFO] 172.30.32.1:55031 - 48894 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074416s
[INFO] 172.30.32.1:55031 - 49059 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000040807s
[INFO] 172.30.32.1:47498 - 9501 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000075188s
[INFO] 172.30.32.1:47498 - 9684 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000040217s
[INFO] 172.30.32.1:35494 - 62138 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000073945s
[INFO] 172.30.32.1:35494 - 62321 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000044713s
[INFO] 172.30.32.1:43702 - 21370 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074901s
[INFO] 172.30.32.1:43702 - 21523 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000043255s
[INFO] 172.30.32.1:40807 - 40799 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000080698s
[INFO] 172.30.32.1:40807 - 40989 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000040654s
[INFO] 172.30.32.1:56105 - 65127 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,aa,rd,ra 219 0.000079681s
[INFO] 172.30.32.1:56105 - 65297 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,aa,rd,ra 131 0.000046652s
[INFO] 172.30.32.1:53249 - 54067 "A IN czfe64-front01-iad01.transport.home.nest.com. udp 62 false 512" NOERROR qr,rd,ra 218 0.011326501s
[INFO] 172.30.32.1:53249 - 54337 "AAAA IN czfe64-front01-iad01.transport.home.nest.com. udp 62 false 512" NOERROR qr,rd,ra 265 0.018821429s
[INFO] 172.30.32.1:47368 - 49528 "AAAA IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 131 0.011047238s
[INFO] 172.30.32.1:47368 - 49367 "A IN api.darksky.net. udp 33 false 512" NOERROR qr,rd,ra 219 0.011870099s
[INFO] 172.30.32.1:57261 - 24979 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 123 0.127639783s
[INFO] 127.0.0.1:60911 - 24821 "A IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 58 0.137494814s
[INFO] 172.30.32.1:57261 - 24821 "A IN www.waze.com. udp 30 false 512" NOERROR qr,rd,ra 58 2.138803121s
[INFO] 172.30.32.1:49510 - 32634 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074085s
[INFO] 172.30.32.1:49510 - 32825 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.0000471s
[INFO] 172.30.32.1:59445 - 53735 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000075812s
[INFO] 172.30.32.1:59445 - 53904 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000043717s
[INFO] 172.30.32.1:45613 - 40109 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000075656s
[INFO] 172.30.32.1:45613 - 40288 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000042393s
[INFO] 172.30.32.1:52092 - 42692 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.000074578s
[INFO] 172.30.32.1:52092 - 42861 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000040428s
[INFO] 172.30.32.1:55808 - 26114 "A IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 58 0.00007518s
[INFO] 172.30.32.1:55808 - 26310 "AAAA IN www.waze.com. udp 30 false 512" NOERROR qr,aa,rd,ra 123 0.000072246s

"System Health" info under Configuration → Info:

arch x86_64
chassis vm
dev false
docker true
docker_version 19.03.11
hassio true
host_os HassOS 4.13
installation_type Home Assistant OS
os_name Linux
os_version 5.4.63
python_version 3.8.5
supervisor 247
timezone America/Chicago
version 0.116.2
virtualenv false

@balloob
Copy link
Member

balloob commented Oct 15, 2020

Hm, can you see if in <config>/.cloud/production_auth.json there are values for id_token, access_token and refresh_token ?

@balloob balloob self-assigned this Oct 15, 2020
@alexsands
Copy link
Author

Hm, can you see if in <config>/.cloud/production_auth.json there are values for id_token, access_token and refresh_token ?

@balloob I do not have a file called production_auth.json in that directory. Only seeing:

.cloud $ ls
acme_account.pem
acme_reg.json
remote_fullchain.pem
remote_private.pem

I am not logged into Home Assistant Cloud at the moment. Trying to do so fails with the error message "Unable to reach the Home Assistant cloud."

@balloob
Copy link
Member

balloob commented Oct 15, 2020

Right, that's only if you're logged in.

Are you on Discord? Could you ping me. I'm balloob#6041 or join us in #cloud channel @ https://www.home-assistant.io/join-chat/

@alexsands
Copy link
Author

alexsands commented Oct 15, 2020

Massive thanks to @balloob and @cogneato for the help debugging this. @balloob put in #197 to fix the stack trace for the Invalid type for parameter AuthParameters.REFRESH_TOKEN error.

For others who have this issue, the fix for me was...

It turned out to be an ipv6 DNS server that was present, which should not have been. You can remove it by disabling ipv6 on the VM:

  1. Open your VM and log in as root with root
  2. At the HA command line (i.e. ha > ) type login
  3. You should now see #
  4. Show your connections with nmcli connection show
  5. Show the properties of the connection with nmcli con show "Your Connection Name"
  6. You will probably see auto for the ipv6.method value
  7. Disable ipv6 by running nmcli connection modify "Your Connection Name" ipv6.method "disabled"
  8. Reboot the VM
  9. Try logging into Home Assistant Cloud once everything reboots

@balloob balloob mentioned this issue Oct 16, 2020
21 tasks
@github-actions github-actions bot locked and limited conversation to collaborators Nov 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants