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
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.
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?
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.
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.
I don’t know, I believe it does but I haven’t tested with one.
I think it does. I went to http://[My Google Home Mini IP]:8008/setup/eureka_info and I see a bunch of info.
That did the trick 
EDIT: only 10 mins of joy, back to troubleshooting.
Anyone here care to explain why we need this “config entry” stuff?
For me it looks like it just makes everything more complicated and less comfortable. I just do not find a way to store my config in a version controll system anymore with this.
So newbies can run through a setup wizard and configure everything - no need for SSH/Samba etc. Supposadly easy to do sensible migrations so OwnTracks changing doesn’t break load of installs
Is a pain to backup/disable if stuff goes wrong.