0.83: Fibaro Home Center Hubs, locks via voice, Traccar

[ATXcoder (Tom)]

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'

[masterkenobi (Ben)]

yes you are right. i was using telnet too. I have changed it to SSH and port 22. It seems to be working now.

[thaihung9221]

TTS Error - This error seems to affect quite a lot of people, looking forward to early patches, thanks to the programmer

[BadHass]

If I track 2 phones with Owntracks, do I use the same url for both phones?

[bachoo786]

Same error I got downgrading to 0.82.1

[ATXcoder (Tom)]

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)

[gregg098]

I have the same issue with various groups. No changes to config other than upgrading.

[maurizio53 (Maurizio Fabiani)]

same here… back to 0.82.1

[gregg098]

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.

[masterkenobi (Ben)]

OK. Confirm Google Home Mini is supported!

[bachoo786]

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

[WedHumpDay (Jason)]

This resolved my stuck UI.

@jncanches

device_tracker:
  - platform: owntrack
    max_gps_accuracy: 200

becomes

owntracks:
  max_gps_accuracy: 200

[woody4165 (Woody)]

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

[woody4165 (Woody)]

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

[kevjs1982]

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.

[woody4165 (Woody)]

Thanks.

I am going to downgrade to 0.82.x, but I don’t remember what was the latest NON-beta version, any help please?

Thanks

[jusdwy]

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!)

Custom Dark Sky Animated Weather Card

@balance82 I asked this in Discord today, and Arsaboo stated it is updated on his repro: https://github.com/arsaboo/homeassistant-config The way I ended up fixing this was: Rename the dark-sky-weather-card.js to dark-sky-weather.card.js.old Create a new dark-sky-weather-card.js in www/custom_ui. Contents for the file here In the ui-lovelace.yaml file, replaced the contents for the old weather card with the following: - id: dark_sky_animated_card type: custom:dark-sky-weather-card …

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)

[silvrr]

82.1

adsfasdfasdfa

[Schneider (Antonio Schneider)]

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!