Error connection every reboot RPI about hass-nabucasa HOT 19 CLOSED

Do you have a stack trace ?

from hass-nabucasa.

Where i found the stack trace? In home-assistant.log file there is no error about it. I try to restart for find error.

from hass-nabucasa.

You need enable it once per config panel, not with the remote portal. The remote portal is just once during a session.

from hass-nabucasa.

I use the url generated in android app, and it works until the rpi is restarted. After to make the url work on anrdoid app I have to connect to the site nabu home and click on connect

from hass-nabucasa.

This is the error when reboot

from hass-nabucasa.

I also noticed that in the account when I click connect, it reads the url in https. When I update the page, the url disappears in the "remote ui" section

from hass-nabucasa.

To permanently enable it, go to the Home Assistant frontend of your installation. Go to the Configuration panel -> Click on Home Assistant Cloud -> Enable the Remote Control toggle to enabled.

After that, it should be on by default.

from hass-nabucasa.

To permanently enable it, go to the Home Assistant frontend of your installation. Go to the Configuration panel -> Click on Home Assistant Cloud -> Enable the Remote Control toggle to enabled.

After that, it should be on by default.

Hi frenk, I had already enabled it in the first configuration. It always remains enabled even when I restart, but on the nabucasa site the link disappears after clicking it.

from hass-nabucasa.

Yes, that is expected. We fetch your URL when you click connect and open a window to your instance, as fallback we display the link.

If you refresh you will have to click it again to fetch the url again.

from hass-nabucasa.

Yes, that is expected. We fetch your URL when you click connect and open a window to your instance, as fallback we display the link.

If you refresh you will have to click it again to fetch the url again.

ok, but when I restart the rpi that error appears and the I have to connect to the nabucasa site and click connect to make it work. It's a bug?

from hass-nabucasa.

I find the problem after few test. The problem is in the new section internal url and external url. I had set my lan as internal and the nabucasa url as external, but after each reboot I had to reconnect it from the nabucasa site. After removing internal and external and restarting it continued to work without reconnecting it. The error occurred after setting internal url and external url.

from hass-nabucasa.

I have entries for both as shown here and don't have this issue:

Were yours the same?

from hass-nabucasa.

yes mine were the same, I'll try to put them back and see if it works after restarting the rpi

from hass-nabucasa.

You should not have to put the Nabu Casa url as external url. It will be used automatically if no external url is specified.

from hass-nabucasa.

I have the same problem. I restart Home Assistant (Ubuntu, Docker, 0.110.5) and xyz.ui.nabu.casa is not available and wants to reconnect. Accessing HA via localhost:8123 works and "Cloud connection status" says it's connected and 'Remote control' is toggled on.

The log shows:

homeassistant       | 2020-06-06T14:28:37.344979518Z Traceback (most recent call last):
homeassistant       | 2020-06-06T14:28:37.344983426Z   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 153, in _async_step
homeassistant       | 2020-06-06T14:28:37.344986558Z     self, f"_async_{cv.determine_script_action(self._action)}_step"
homeassistant       | 2020-06-06T14:28:37.344996761Z   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 623, in _async_call_service_step
homeassistant       | 2020-06-06T14:28:37.344999529Z     *self._prep_call_service_step(), blocking=True, context=self._context
homeassistant       | 2020-06-06T14:28:37.345001836Z   File "/usr/src/homeassistant/homeassistant/core.py", line 1253, in async_call
homeassistant       | 2020-06-06T14:28:37.345004231Z     task.result()
homeassistant       | 2020-06-06T14:28:37.345006639Z   File "/usr/src/homeassistant/homeassistant/core.py", line 1288, in _execute_service
homeassistant       | 2020-06-06T14:28:37.345009258Z     await handler.func(service_call)
homeassistant       | 2020-06-06T14:28:37.345031688Z   File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 518, in admin_handler
homeassistant       | 2020-06-06T14:28:37.345035006Z     await result
homeassistant       | 2020-06-06T14:28:37.345038145Z   File "/usr/src/homeassistant/homeassistant/components/cloud/__init__.py", line 202, in _service_handler
homeassistant       | 2020-06-06T14:28:37.345042317Z     await cloud.remote.connect()
homeassistant       | 2020-06-06T14:28:37.345046245Z   File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/remote.py", line 259, in connect
homeassistant       | 2020-06-06T14:28:37.345050101Z     raise RemoteNotConnected()
homeassistant       | 2020-06-06T14:28:37.345067496Z hass_nabucasa.remote.RemoteNotConnected

from hass-nabucasa.

@arjenfvellinga do you have a script to call remote.cloud_connect ?

from hass-nabucasa.

Yes I have, an automation:

- id: connect_remote_on_start
  alias: Connect Remote on Start
  initial_state: 'on'
  trigger:
    platform: homeassistant
    event: start
  action:
#  - delay: '00:02:00'
  - service: cloud.remote_connect

I added it because of the reconnect issue. I think you're suggestion now the error in the log is from the automation?

from hass-nabucasa.

Yes. Since Home Assistant has been starting faster, it might not be ready to connect yet.

from hass-nabucasa.

With a delay it seems to be working, thanks

from hass-nabucasa.