This 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
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
1 Like
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.
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
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)
82.1
adsfasdfasdfa
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!
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.
I also have this error with google tts since today, but I’m still on 0.81.6 (HassIO). So I think this error is not related to the new release directly.
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
1 Like
Is it still working? Mine was only working for 10 mins, but i’m using telnet on a RT-AC66U.
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?
Fixed in 0.83.1
1 Like
node-red is not connecting to the HA.
Login attempt or request with invalid authentication from 192.168.X.X