Crazy release again with tons of new thing 
Concerning the google home bluetooth tracker, does someone know what it can detect and how well does it work? Will it for example detect a phone with bluetooth enable? Or a connected watch with BLE?
Thank you very much. So happy with the new light switch.
Can anyone explain how the Google Home BLE device tracker works?
https://www.home-assistant.io/components/device_tracker.googlehome/
The input is just IP of the Home, but how do we know what devices it is going to look for or report on? is it based on your google account or do you need to tell it specific bluetooth MAC addresses?
3 replies
Furthermore regarding Owntracks, so on HA part I don’t need to put owntracks under device_tracker anymore?
Just upgraded from 0.81.6 to 0.83.0, and I also changed out device_tracker with asuswrt in configuration.yaml, and commented out the track_new_devices: false, as that is not supported by the asuswrt component. However, I only get errors, using a Asus RT-AC66U with Telnet:
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)
Is there something I’m overlooking?
3 replies
I’m also interest in this.
I currently use my rpi bluetooth to track when we are home, it would be good if my bedroom G mini could detect when we go to bed and then turn everything off downstairs.
Or am I missing the point of this?
I was using the yale smart alarm but they change their api and I’m hoping someone can fix it
1 reply
No this is my understanding of it too. I have a few GH in my house so I’m now thinking I can effectively set up room-level presence detection with nothing more than the GH devices.
I had to roll back to 0.82.1 as just hung when I updated. Nothing obvious in the logs, though I suspect maybe Xiaomi devices may have something to do with it as my friend had to do the same and it was erroring on his Xiaomi sensors.
I’ll give it a go again in a bit and see if I can fully debug.
2 replies
For Owntracks. the setting in configuration.yaml
owntracks:
Restart show intergration in config but no device.
Install the OwnTracks application for iOS.
In the OwnTracks app, tap the (i) in the top left and click on settings. Change the following settings:
<url given to you when setting up the integration> <=== what to put when in the intergration no device found<Your name>
I haven’t gotten the upgrade yet but i’ve had a look at the code. It seems to look for BLE devices similar to the ble_tracker. I assume it will use the known_devices.yaml to specify what to track
1 reply
How does locking via google assistant work if I need to enter a pin-code to lock?
No restart needed when configuring OwnTracks. Devices don’t show up under integrations yet but device tracker entries will show up.
Google Home Bluetooth tracker seems amazing!
Even if it doesn’t work well enough for room-level detection, it would be an ideal way for home presence detection for all of us not using a Raspberry Pi for its Bluetooth.
Can it be manually updated? I’m desperate to see if I can get my AsusWRT working again!
I agree
What I’m curious about is can I still use the rpi bluetooth which detect us when on our drive and also use google home for room detection.
Is someone aware of these errors?
2018-11-29 12:59:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
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/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 12:59:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
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/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: group.calendar
2018-11-29 12:59:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
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/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: group.calendar
2018-11-29 12:59:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
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/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: group.calendar
2018-11-29 12:59:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
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/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: group.calendar
This release is so awesome! 17track is now an offical component and the best is, I can now finally use the fritzbox callmonitor component 
Thank you really much
No, it’s an open issue with 0.83.0 waiting to be fixed…
All group_all set to initial state ‘on’ have this problem…
I also have problems with 0.83
When I restart HA I see some activity in the logs, and the last records are:
Nov 29 14:13:59 raspberrypi3 hass[31567]: 2018-11-29 14:13:59 INFO (Thread-14) [homeassistant.components.device_tracker.fritz] Successfully connected to FRITZ!Box 7560 (UI)
Nov 29 14:13:59 raspberrypi3 hass[31567]: 2018-11-29 14:13:59 INFO (Thread-14) [homeassistant.components.device_tracker.fritz] Scanning
Nov 29 14:14:02 raspberrypi3 hass[31567]: 2018-11-29 14:14:02 INFO (Thread-18) [homeassistant.components.device_tracker.fritz] Scanning
and it stops after this. Before this fritzbox tracker was scanning and leaving the log records periodically, each 5 seconds or so, but not after this update.
I also notice that some part of HA works, because it writes something into InfluxDB - I can see the changing numbers and graphs in Grafana which visualizes InfluxDB data, and it is only possible if HA is alive. But I cannot open HA in my browser.
I was patient enough to comment out sections in configuration.yaml to see what makes HA hang, and I found that OwnTracks is the culprit. This is my configuration:
device_tracker:
- platform: fritz
interval_seconds: 10
consider_home: 180
track_new_devices: yes
- platform: owntracks
max_gps_accuracy: 200
As soon as I comment out owntracks, HA starts fine.
1 reply
I got problem with google tts after update to 0.83
Thu Nov 29 2018 20:47:12 GMT+0700 (Indochina Time)
Error executing service <ServiceCall tts.google_say (c:6ed4b19be7494df8970833f467b0c61f): entity_id=['media_player.home_speaker'], message=how are you>
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/core.py", line 1177, in _event_to_service_call
await service_handler.func(service_call)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/tts/__init__.py", line 137, in async_say_handle
options=options
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/tts/__init__.py", line 306, in async_get_url
engine, key, message, use_cache, language, options)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/tts/__init__.py", line 318, in async_get_tts_audio
message, language, options)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/tts/google.py", line 83, in async_get_tts_audio
token.calculate_token, part)
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.6/site-packages/gtts_token/gtts_token.py", line 28, in calculate_token
seed = self._get_token_key()
File "/srv/homeassistant/lib/python3.6/site-packages/gtts_token/gtts_token.py", line 57, in _get_token_key
tkk_expr = re.search(".*?(TKK=.*?;)W.*?", line).group(1)
AttributeError: 'NoneType' object has no attribute 'group'
Also for lovelace.
## Log Details (ERROR)
Thu Nov 29 2018 20:47:07 GMT+0700 (Indochina Time)
https://192.168.1.60:8123/frontend_latest/app-0fd67575.js:89:305 Uncaught TypeError: Cannot read property 'toUpperCase' of null
## Log Details (ERROR)
Thu Nov 29 2018 20:47:01 GMT+0700 (Indochina Time)
https://192.168.1.60:8123/frontend_latest/app-0fd67575.js:89:305 Uncaught TypeError: Cannot read property 'state' of undefined
Aha, thanks. Had the same issue of HA not showing the web-interface. Commenting out owntracks helped for now. Have to dig into the breaking change for owntracks, but at least HA is up and running again now.
17track is not working for me: [homeassistant.components.sensor.seventeentrack] Invalid username and password provided
Someone told me it’s related to the google calendar component… if you use it try to comment out that and restart…
1 reply
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)
3 replies
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'
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 replies
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 reply
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.
1 reply
Also anyone have problem with broadlink switch? I cannot control all my broadlink switch.
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 reply
Nope I don’t have any of those components in my config.
It’s been over an hour now it’s not working.
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_switches
Same 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 think it does. I went to http://[My Google Home Mini IP]:8008/setup/eureka_info and I see a bunch of info.
Short joy, after approx 10 minutes, all devices were apparently away, and also the upload/download sensor seems to fail, spamming my log:
2018-11-29 18:23:28 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.asuswrt_download fails
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 221, in async_update_ha_state
await self.async_device_update()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 347, in async_device_update
await self.async_update()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/sensor/asuswrt.py", line 106, in async_update
await super().async_update()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/sensor/asuswrt.py", line 54, in async_update
self._speed = await self._api.async_get_current_transfer_rates()
File "/srv/homeassistant/lib/python3.6/site-packages/aioasuswrt/asuswrt.py", line 217, in async_get_current_transfer_rates
self._rx_latest = data[0]
IndexError: list index out of range
2018-11-29 18:23:28 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.asuswrt_upload_speed fails
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 221, in async_update_ha_state
await self.async_device_update()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 347, in async_device_update
await self.async_update()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/sensor/asuswrt.py", line 88, in async_update
await super().async_update()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/sensor/asuswrt.py", line 54, in async_update
self._speed = await self._api.async_get_current_transfer_rates()
File "/srv/homeassistant/lib/python3.6/site-packages/aioasuswrt/asuswrt.py", line 217, in async_get_current_transfer_rates
self._rx_latest = data[0]
IndexError: list index out of range
Has anyone managed to make the downgrade work? When I go back to version 0.82.1 it does not work.
HTTP Sensors are broke at 0.83 apparently. https://github.com/home-assistant/home-assistant/pull/18733
A fix has been added to the queue of stuff in 0.83.1
Anyone know if it’s possible to switch to the Long Lived Tokens on HTTP Sensors and if they work?
asuswrt broken for me too.
Im getting the same error and i have the same router.
upgraded to 0.83 and now HA will not start. Seeing this in the logs. Any ideas?
2018-11-29 11:48:15 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 390, in start
resp = await self._request_handler(request)
File "/usr/local/lib/python3.6/site-packages/aiohttp/web_app.py", line 366, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 106, in impl
return await handler(request)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/static.py", line 66, in staticresource_middleware
return await handler(request)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 34, in real_ip_middleware
return await handler(request)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 66, in ban_middleware
return await handler(request)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 97, in auth_middleware
return await handler(request)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 34, in real_ip_middleware
return await handler(request)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 66, in ban_middleware
return await handler(request)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 97, in auth_middleware
return await handler(request)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/view.py", line 115, in handle
result = await result
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/api.py", line 85, in get
if not request['hass_user'].is_admin:
File "/usr/local/lib/python3.6/site-packages/aiohttp/web_request.py", line 201, in __getitem__
return self._state[key]
KeyError: 'hass_user'yes you are right. i was using telnet too. I have changed it to SSH and port 22. It seems to be working now.
TTS Error - This error seems to affect quite a lot of people, looking forward to early patches, thanks to the programmer
If I track 2 phones with Owntracks, do I use the same url for both phones?
I just saw that someone else had this error too. Looks to be related to users who have systems that are making calls to HA REST using the Legacy Password. My Node-Red connects to HA’s REST API using the Legacy Password. Going to see if I can re-configure Node-Red to use token instead, but also see a fix has been issued in 83.1 (https://github.com/home-assistant/home-assistant/issues/18783)
1 reply
I have the same issue with various groups. No changes to config other than upgrading.
same here… back to 0.82.1
I added my Google Homes (7 of them) as device trackers, and Home Assistant never finishes starting up. I let it sit for 45 minutes earlier and I could barely navigate the UI, Z wave components get stuck in initializing, other components don’t show up on the front end, etc. Tried restarting a few times with the same problem.
There are no log entries that seem to indicate any issues. When I comment out the Google Home entries, Home Assistant starts up really quick with no issues (other than a few random log errors as others noted such as the group already exists error).
Anyone else having this issue? Will try just adding one of them at a time later today to see if it helps.
OK. Confirm Google Home Mini is supported! 
back to 0.82.1 getting the same errors and now frontend wont load together with that getting these issues:
$
2018-11-29 18:21:12 WARNING (MainThread) [homeassistant.components.cover.mqtt] Payload is not True or False: 14
2018-11-29 18:21:12 WARNING (MainThread) [homeassistant.components.cover.mqtt] Payload is not True or False: 63
2018-11-29 18:21:30 WARNING (MainThread) [homeassistant.components.cover.mqtt] Payload is not True or False: 14
2018-11-29 18:21:31 WARNING (MainThread) [homeassistant.components.cover.mqtt] Payload is not True or False: 63
2018-11-29 18:22:03 WARNING (MainThread) [homeassistant.components.cover.mqtt] Payload is not True or False: 14
2018-11-29 18:22:03 WARNING (MainThread) [homeassistant.components.cover.mqtt] Payload is not True or False: 63
2018-11-29 18:22:36 WARNING (MainThread) [homeassistant.components.cover.mqtt] Payload is not True or False: 14
2018-11-29 18:22:36 WARNING (MainThread) [homeassistant.components.cover.mqtt] Payload is not True or False: 63
Hi all
I’m experiencing a white page in lovelace with this card, was working before upgrading and no modification was done.
- id: 2 # Automatically created id
title: Meteo
icon: mdi:weather-partlycloudy
cards:
- id: xxxxxx # Automatically created id
type: vertical-stack
cards:
- type: entities
title: Temperature
show_header_toggle: false
entities:
- sensor.patio_temp
- sensor.patio_umidita
- type: divider
- sensor.temperature_xxxxx
- sensor.humidity_xxxxx
- type: divider
- sensor.temperature_yyyyy
- sensor.humidity_yyyy
- type: divider
- sensor.rmpro_sala_temperature
- sensor.rmpro_letto_temperature
- type: divider
- sensor.tempest
- sensor.tempesthum
- sensor.tempestbat
- type: entities
title: Umidità, pressione e pioggia
show_header_toggle: false
entities:
- sensor.dark_sky_temperature
- sensor.dark_sky_humidity
- sensor.dark_sky_pressure
- sensor.dark_sky_wind_speed
- sensor.dark_sky_wind_bearing
- sensor.dark_sky_summary
- sensor.dark_sky_cloud_coverage
- sensor.dark_sky_precip_intensity
- sensor.dark_sky_precip_probability
- type: entities
title: Daily Forecast
show_header_toggle: true
entities:
- sensor.pws_weather_1d_metric
- sensor.pws_weather_1n_metric
- type: divider
- sensor.pws_weather_2d_metric
- sensor.pws_weather_2n_metric
- type: divider
- sensor.pws_weather_3d_metric
- sensor.pws_weather_3n_metric
- type: divider
- sensor.pws_weather_4d_metric
- sensor.pws_weather_4n_metric
I have also done the modification in the dark_sky platform sensor adding the 0
- platform: darksky
api_key: !secret darksky_api_key
forecast:
- 0
- 1
- 2
- 3
- 4
- 5
update_interval:
minutes: 5
monitored_conditions:
...
...
Strangely, this happens only in lovelace, with standard UI I get all the sensors showed.
What can I check?
Thanks
A new issue for me after upgrading.
I have Node Red installed on a separate server, working until update to 0.83.
Now the connection to Hassio is not working anymore.
I’m using API pass (in the picture removed) and it’s defined in secrets.yaml
Is there anything new that I have missed?
Thanks
2 replies
That’s probably related to https://github.com/home-assistant/home-assistant/pull/18733 - fix due in 0.83.1
Another poster was going to see if they could get it to worth with the moder tokens.
1 reply
0.83 broke my Lovelace
http://hassio.local:8123/frontend_latest/app-0fd67575.js:89:305 Uncaught TypeError: Cannot read property ‘state’ of undefined
2:49 PM components/system_log/init.py (ERROR)
http://hassio.local:8123/local/custom_ui/dark-sky-weather-card.js?v=4:144:85 Uncaught TypeError: Cannot read property ‘state’ of undefined
2:43 PM components/system_log/init.py (ERROR)
still can load /states without issue. No states in /dev-state seem to be acting up, and everything was working previous to upgrading from 0.82.1
update:
not sure what happened, but when I went from /states to /lovelace it partially loaded. the main page view is blank, but I can click thru my others views without issue. main page does include the custom dark sky card.
and when i comment out the dark sky card it works. something changed with how HA interprets custom cards?
update update: (SOLVED!)
issue was with entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature not starting at 1 in ui_lovelace.yaml.
(also minor change in the dark-sky-weather-card.js to update pressure to mbar)
Hello guys! Thanks for this awesome update.
I am amazed how fast lovelace UI loads now, great work!
Asus component working fine now, just a bug (maybe?) on how download/upload sensors shows data:
Both sensors shows the other’s value. In the image above, I was just downloading, at 50mbps, no upload whatsoever… Very strange.
Here is how it shows on the Asus WebUI:
Also: any adive on using track_new_devices parameter now? I ratter set it manually for each new device.
Thanks!
1 reply
Working now.
Followed advice from someone on here (sorry can’t see your post now!)
remove OwnTracks from device_tracker and put in the configuration.yaml on its own
OwnTracks:Anyone else seeing issues with Schlage Z wave locks? Have a BE468 and a BE469. Both respond to local operation of the lock, but if I lock/unlock through Hass, the status never updates. Saw the update in the change log so I’m guessing it has something to do with that PR.
Any update on when an updated version of DenonAVR will be merged into the release? It’s been about 2 month since it got updated (https://github.com/scarface-4711/denonavr ) Would love to use my new receiver 
RT-AX88U - everything works, but i cant disable track mode for new devices for it.
Google changed the token.
https://github.com/home-assistant/home-assistant/issues/16905#issuecomment-442912708
Having the same issue here…
Hass works normaly, but every 2 minutes log is flooded with this message
Is it still working? Mine was only working for 10 mins, but i’m using telnet on a RT-AC66U.
1 reply
I am using SSH and it works great, apart from the Download/Upload sensor data. Not sure how to set track_new_devices now. Thanks.
Same here. Did the downgrade work for you?
node-red is not connecting to the HA.
Login attempt or request with invalid authentication from 192.168.X.X
@balloob
This error is occurring when I run an ifttt webhook:
Error executing service <ServiceCall switch.turn_off (c:4eb3ebc0579844abb7deb328c5253e54): entity_id=[‘switch.lampada’]>
Traceback (most recent call last):
File “/home/jean/apps/Homeassistant/lib/python3.5/site-packages/homeassistant/core.py”, line 1177, in _event_to_service_call
await service_handler.func(service_call)
File “/home/jean/apps/Homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_component.py”, line 177, in handle_service
self._platforms.values(), func, call
File “/home/jean/apps/Homeassistant/lib/python3.5/site-packages/homeassistant/helpers/service.py”, line 250, in entity_service_call
permission=POLICY_CONTROL
homeassistant.exceptions.Unauthorized: Unauthorized
What do you mean? denonavr already uses the latest package available (0.7.6).
We can’t update the component if the PR (I assume you want https://github.com/scarface-4711/denonavr/pull/65) for support isn’t merged and a new version gets released on pypi.
Updated to 0.83.1 now getting failed login attempt even though I am logged in.
Update server is informing the wrong version and crashing hassio installations. I checked the server (https://s3.amazonaws.com/hassio-version/stable.json) and it’s informing 0.82.1 as the latest, even for whom is already on 0.83. So if someone proceed with the suggested upgrade it will corrupt the installation. That just happened to me.
1 reply
same for me 
I forced the upgrade to 0.83.1 using the following cli command, using ssh, and it fixes the problem.
hassio ha update --options version=0.83.1