core: Nabu Casa error - Remote UI unreachable

Home Assistant release with the issue: 0.103.6

Last working Home Assistant release (if known): 0.103.5

Operating environment (Hass.io/Docker/Windows/etc.): Hass.io on Ubuntu host

Integration:

Description of problem: After upgrading to 0.103.6 (from .5) the GUI in unreachable from its Nabu Casa URL. It is still reachable on its DuckDNS url.

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

Traceback (if applicable): Errors in log, persising after Docker restarts:

2020-01-07 19:12:41 ERROR (MainThread) [hass_nabucasa.remote] Can't handle request-connection without backend
2020-01-07 19:12:41 ERROR (MainThread) [hass_nabucasa.iot] Error handling message
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/iot.py", line 90, in _async_handle_handler_message
    result = await handler(self.cloud, message["payload"])
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/iot.py", line 143, in async_handle_remote_sni
    await cloud.remote.handle_connection_requests(caller_ip)
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/remote.py", line 216, in handle_connection_requests
    raise RemoteNotConnected()
hass_nabucasa.remote.RemoteNotConnected

Additional information: Edit: downgrading to 0.103.5 immediately fixed this issue. Definitely seems to be related to 0.103.6 then. Edit2: seems it’s not related to 0.103.6 after all. Now on 0.103.5, after most HA restarts the remote UI is unreachable for me. Logs are below in the comments.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 44 (12 by maintainers)

Most upvoted comments

We need to implement the fix in the code.

balloob on Feb 26, 2020

Traced it down to https://github.com/boto/boto3/issues/1592 . It seems like it’s related to having other threads also use the AWS SDK. Looks like https://github.com/boto/boto3/issues/1592#issuecomment-540825115 might be a solution.

balloob on Feb 25, 2020

Hi,

I’m experiencing the same issue: after reboot the whole system the remote connection is unreachable for quite some time. I’ve also contacted support about this, but thusfar we haven’t been able to solve it. In my configuration Nabu Casa starts working again when I disable Amazon Polly TTS. Are more people here using that integration?

I’m on Hass 0.104.1 BTW.

MichielvanBeers on Feb 4, 2020

As i mentioned earlier i am having the same issues. I am also running Hass.io on Ubuntu, HA 0.104.3 with Hass.io supervisor v195. My custom components are HACS (0.20.9 = latest), Amazon Rekognition 103, Krisinformation 95fe9d2, Unifi Gateway v0.2.3. Have tried uninstalling them all as well as Custom header and card tools. The remote UI problems started for me after 102. Should i provide som logs as well?

fillwe on Feb 2, 2020

hass_nabucasa.remote.RemoteNotConnected means they was not loaded. The error why is not loaded is in that case the question they we search and should be in the log after start.

@jorismocka yes, the issue with async_enable_local_sdk stop to process the connection and the reason why it not is loaded after start.

@pvizeli thank you for reopening this issue. It really prevents me from restarting my hass.io because I’m afraid to loose my remote access. What is async_enable_local_sdk part of? Code of the Remote UI? Or a third party tool? Thanks a lot.

jorismocka on Jan 30, 2020

This really is an issue for me: after most restarts I am unable to use the Remote UI. Can this get some attention? Should I open a new issue for this?

rschuiling on Jan 29, 2020