for what it’s worth it works fine in a browser from my mobile
I dont believe so, only from a browser
Hi all
I’m trying to update from Hassio 0.89.2 to 0.90, but it remains on the 0.89.2
I’ve tried via Web Terminal with hassio ha update command and also from the Hass.io panel
but I get same result.
What can I check/do?
Thanks
hi, i’m in the same boat…
19-03-21 11:57:13 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.90.0
19-03-21 11:57:13 INFO (SyncWorker_16) [hassio.docker.interface] Update Docker homeassistant/raspberrypi3-homeassistant:0.89.2 to homeassistant/raspberrypi3-homeassistant:0.90.0
19-03-21 11:57:13 INFO (SyncWorker_16) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.90.0.
19-03-21 11:59:25 INFO (MainThread) [hassio.auth] Auth request from core_mosquitto for xxxx
19-03-21 11:59:29 INFO (MainThread) [hassio.auth] Success login from xxxx
19-03-21 11:59:38 INFO (MainThread) [hassio.auth] Auth request from core_mosquitto for xxxx
19-03-21 11:59:39 INFO (MainThread) [hassio.auth] Success login from xxxx
19-03-21 12:07:40 INFO (SyncWorker_16) [hassio.docker.interface] Tag image homeassistant/raspberrypi3-homeassistant with version 0.90.0 as latest
19-03-21 12:07:40 INFO (SyncWorker_16) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant Docker application
19-03-21 12:08:13 INFO (SyncWorker_16) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant Docker application
19-03-21 12:08:14 INFO (SyncWorker_16) [hassio.docker.interface] Cleanup Docker images: [‘homeassistant/raspberrypi3-homeassistant:0.89.2’]
19-03-21 12:08:36 INFO (SyncWorker_0) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.90.0
19-03-21 12:18:40 WARNING (MainThread) [hassio.homeassistant] Don’t wait anymore of Home Assistant startup!
19-03-21 12:18:40 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!
Well, I have no clue what happened over night, but suddenly my Hass.IO page loads properly now. I didn’t get a chance to check if my hass.io supervisor was at an older release when I was having the problem, but it is currently 150.
Is this the homeassistant.log file?
Should normally work, you only have the approve your local domain at installation, after it, it should be push method…
But this is also on my list to actually test if I close my router ports
1 Like
I can’t access my nabu casa link either, or there maybe a DNS issue now, it worked this morning…
Now trying with my smartphone, gives a page not found error
Error connection closed when i try to access the page
Same question here for areas.
I prefer set all my definitions in yaml mode instead of integration.
Great work by the way 
This site can’t be reached
ui.nabu.casa ’s server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
Any an idea?
That works indeed
Seems I was disconnected, I had to connect again, now the unique url works again
Strange it was disconnected automatically
I’m getting this too after updating to 0.90 on Orange pi Supervisor is at 150. Hassio component will not load.
2019-03-21 16:04:48 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/ping request 2019-03-21 16:04:48 ERROR (MainThread) [homeassistant.components.hassio] Not connected with Hass.io 2019-03-21 16:04:48 ERROR (MainThread) [homeassistant.setup] Setup failed for hassio: Component failed to initialize.
I just tried that with an automation like this:
- id: startup
alias: Startup Routine
initial_state: 'on'
trigger:
platform: homeassistant
event: start
action:
- service: cloud.remote_connect
However, when I restarted the server it gave the following in the log:
2019-03-21 13:54:08 ERROR (MainThread) [homeassistant.components.automation] Error while executing automation automation.startup_routine. Unknown error for call_service at pos 1:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/automation/__init__.py", line 381, in action
await script_obj.async_run(variables, context)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/script.py", line 131, in async_run
await self._handle_action(action, variables, context)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/script.py", line 210, in _handle_action
action, variables, context)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/script.py", line 299, in _async_call_service
context=context
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/service.py", line 88, in async_call_from_config
domain, service_name, service_data, blocking=blocking, context=context)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py", line 1138, in async_call
self._execute_service(handler, service_call))
File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
future.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
raise self._exception
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py", line 1160, in _execute_service
await handler.func(service_call)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/cloud/__init__.py", line 184, in _service_handler
await cloud.remote.connect()
File "/srv/homeassistant/lib/python3.5/site-packages/hass_nabucasa/remote.py", line 246, in connect
raise RemoteNotConnected()
hass_nabucasa.remote.RemoteNotConnected
Edit:
It appears to work if I add this before the service call:
- delay: '00:00:30'
So, it looks like at the time the start event is received it is not quite ready to connect to the remote endpoint.
Is your Netatmo thermostat working now?
My Netatmo camera wasn’t working yesterday after updating to 0.90 but now seems to be working again even though I didn’t change anything!
Could be something going on with Netatmo servers
Nope! Doesn’t work yet!
This is not necessary. Remote will connect automatically once the main cloud connection is established, which happens when Home Assistant is done with the startup phase.
1 Like