Hmm ok… so we must only wait for a fix… I was back to 0.82.1
Change “/lovelace” to “/states”
However it’s totally dead for me - starts up then just hangs -still running but nothing in the log - and that’s the chatty journalctl -fu [email protected] log file which stops after a short while.
The database upgrade went quickly and successfully
Downgrading to 0.82 hasn’t helped 
(Removed a comment RE: Google Calendar - it’s called Google and doesn’t mention calendar)
Thanks, that did it 
Downgrading to 0.81.6 gives me trouble also now. Seems to have something to do with auth token, i have no idea what to do now. This error comes over and over again:
2018-11-29 15:33:07 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1706082512] Unexpected error inside websocket API
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api/http.py", line 140, in async_handle
connection = await auth.async_handle(msg)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api/auth.py", line 76, in async_handle
msg['access_token'])
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/auth/__init__.py", line 362, in async_validate_access_token
cast(str, unverif_claims.get('iss')))
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/auth/__init__.py", line 325, in async_get_refresh_token
return await self._store.async_get_refresh_token(token_id)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/auth/auth_store.py", line 190, in async_get_refresh_token
await self._async_load()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/auth/auth_store.py", line 247, in _async_load
name=group_dict['name'],
KeyError: 'name'Do you use owntracks? You have to change your owntracks config. It has moved from device_tracker: to its own component owntracks:. After this change, the web interface became up and running again (for me) after a restart of HA.
If you are using owntrack, its configuration has to be moved from device_tracker: to the root of configuration.yaml
for example:
device_tracker:
- platform: owntrack
max_gps_accuracy: 200
becomes
owntracks:
max_gps_accuracy: 200
Hope this help. My UI was stuck too before I changed that
2 Likes
Commented Owntracks out and that made no difference.
Disabling all Device Trackers and it’s working. Now to narrow down the culprit…
Nope, but i use asuswrt, which has become it’s own component as well. It hasn’t been working since 0.81.6. I did move the settings back. Now i’ve upgraded to 0.83.0 again, but i have a failing “device tracker”, despite having the settings as they should (configuration.yaml):
asuswrt:
host: 192.168.1.1
username: !secret asuswrt_username
password: !secret asuswrt_password
protocol: telnet
From the logs:
2018-11-29 15:50:41 ERROR (MainThread) [homeassistant.setup] Error during setup of component asuswrt
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py", line 145, in _async_setup_component
hass, processed_config)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/asuswrt.py", line 57, in async_setup
await api.connection.async_connect()
File "/srv/homeassistant/lib/python3.6/site-packages/aioasuswrt/connection.py", line 100, in async_connect
self._host, self._port)
File "/usr/local/lib/python3.6/asyncio/streams.py", line 75, in open_connection
lambda: protocol, host, port, **kwds)
File "/usr/local/lib/python3.6/asyncio/base_events.py", line 777, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.6/asyncio/base_events.py", line 764, in create_connection
yield from self.sock_connect(sock, address)
File "/usr/local/lib/python3.6/asyncio/selector_events.py", line 451, in sock_connect
return (yield from fut)
File "/usr/local/lib/python3.6/asyncio/selector_events.py", line 481, in _sock_connect_cb
raise OSError(err, 'Connect call failed %s' % (address,))
ConnectionRefusedError: [Errno 111] Connect call failed ('192.168.1.1', 22)
EDIT: Thought the OwnTracks post was for me. Still relevant though.
1 Like
Have updated to 0.83 but HA does not load ?
Got it - had to remove the Bluetooth Tracker Too…
- platform: bluetooth_tracker
request_rssi: true
consider_home: 180
Now to work out what is flooding the logs with:-
Nov 29 15:02:19 haas hass[4241]: Traceback (most recent call last):
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/aiohttp/web_protocol.py", line 390, in start
Nov 29 15:02:19 haas hass[4241]: resp = await self._request_handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/aiohttp/web_app.py", line 366, in _handle
Nov 29 15:02:19 haas hass[4241]: resp = await handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/aiohttp/web_middlewares.py", line 106, in impl
Nov 29 15:02:19 haas hass[4241]: return await handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/http/static.py", line 66, in staticresource_middleware
Nov 29 15:02:19 haas hass[4241]: return await handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/http/real_ip.py", line 34, in real_ip_middleware
Nov 29 15:02:19 haas hass[4241]: return await handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/http/ban.py", line 66, in ban_middleware
Nov 29 15:02:19 haas hass[4241]: return await handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/http/auth.py", line 97, in auth_middleware
Nov 29 15:02:19 haas hass[4241]: return await handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/http/real_ip.py", line 34, in real_ip_middleware
Nov 29 15:02:19 haas hass[4241]: return await handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/http/ban.py", line 66, in ban_middleware
Nov 29 15:02:19 haas hass[4241]: return await handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/http/auth.py", line 97, in auth_middleware
Nov 29 15:02:19 haas hass[4241]: return await handler(request)
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/http/view.py", line 115, in handle
Nov 29 15:02:19 haas hass[4241]: result = await result
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/api.py", line 220, in post
Nov 29 15:02:19 haas hass[4241]: if not request['hass_user'].is_admin:
Nov 29 15:02:19 haas hass[4241]: File "/home/pi/homeassistant/lib/python3.5/site-packages/aiohttp/web_request.py", line 201, in __getitem__
Nov 29 15:02:19 haas hass[4241]: return self._state[key]
Nov 29 15:02:19 haas hass[4241]: KeyError: 'hass_user'@bachoo786 See above, probably OwnTracks or Asuswrt component that you have to change in your config.
Also anyone have problem with broadlink switch? I cannot control all my broadlink switch.
Ah, looks like it’s all my HTTP Sensors…
HASS is returning
<html><head><title>500 Internal Server Error</title></head>
<body><h1>500 Internal Server Error</h1>Server got itself in trouble</body></html>Does anyone definitively know if the asuswrt component using SSH works in this release? I don’t want to upgrade if the asuswrt device tracker component is still broken.
And to clarify since the docs are pretty vague -
Do we just need to setup the asuswrt component and that will automatically start tracking devices or do we still need to add the asuswrt device tracker config to the "device_tracker: " section?
Assuming it’s the former then if I have a asuswrt device tracker set up then do I need to remove that config entry?
1 Like
Nope I don’t have any of those components in my config.
It’s been over an hour now it’s not working.
Telnet port is 23. Add port: 23 into the configuration.
1 Like
I’ve stuck on loading 0.83 but after i read to remove OwnTracks in config i finally got it HA working again.
I am having the following errors:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: group.all_switches
2018-11-29 15:55:41 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: group.all_switches
2018-11-29 15:55:41 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: group.all_switches
2018-11-29 15:55:41 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: group.all_switchesSame here. I actually forgot I had it enabled since I don’t use it anymore. Everything seemed to come up just fine, but the UI wasn’t loading. There wasn’t anything apparent in the logs at the warn level either. I saw this thread, removed the config, restarted the container, and everything came up as expected.
1 Like