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.
This needs a good solution… I run home assistant as docker container for a reason and i really like a “fallback” when i mess up my config… And i ocassionally do
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 rangeHas 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'
2 Likes
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?
Same error I got downgrading to 0.82.1
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)
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: 63This resolved my stuck UI.
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