0.108: Logos, Area Pages, Lovelace Entity Card, Lovelace Map History

Mutt · April 11, 2020, 11:42pm

Wow that’s pretty bad.
On 0.108.3 pi3b I’m on 0.13 (5m)
And on the pi4-4 on 0.03 (again 5m)

firstof9 · April 11, 2020, 11:47pm

16:46:36 up 39 days,  3:13,  2 users,  load average: 0.64, 0.58, 0.63

on my Pi3B, I have a lot of integrations going.

Isaac18 · April 12, 2020, 2:59am

I have problems with Broadlink as well. RF Lights work fine but the rollers (defined as switches) won’t work. Something interesting happened though, as one roller gets only the open instruction but doesn’t close. The code for opening the roller is at least a third in length. Is there a new limit to the code length?

nickrout · April 12, 2020, 3:54am

Read the whole thread, and the linked issues.

TL;DR it is broken, it is being worked on, and there is a workaround.

mirekmal · April 12, 2020, 7:15am

Interesting… I made experiment copying unchanged mini-graph-card configuration that works and does not work between cards and found strange behavior. Card that work perfectly as stand alone card, copied to card where graphs are embedded into stack-in-card continues to work as intended. Card that does not work within the same stack, when copied to outside as stand alone card started to work as intended. You can see this on screenshot below:

Upper left graph is exactly the same one as stand alone one at the bottom (so working fine as such, but not when embedded)
right-most upper graph is copy of stand alone chart that work perfectly elsewhere, and continues to do so ahen embedded into stack

This leads me to conclusion, that perhaps there are specific mini-graph-chart settings, that leds to such behavior. I’ll try to play with these to see if some conclusion can be drawn.

tom_l · April 12, 2020, 7:21am

You should raise an issue with the custom card developer or discuss it in the mini graph card topic.

SmirkDeGecko · April 12, 2020, 8:09am

Hi I’m also having the same issue. anyluck on your troubleshooting?

nickrout · April 12, 2020, 8:21am

Have to tried clearing your browser cache?

carloscae · April 12, 2020, 9:33am

god damn… i’m running on VM server… normally takes seconds to restart, now it’s more like minutes.
i stupidly updated both supervisor and home assistant at the same time, now I don’t know what’s the issue.

rock · April 12, 2020, 9:34am

Since the update to 108, currently on 108.3, I have noticed that I get continously logs with:

[homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12

Anyone have an idea on what has happened? Never had this before
Running Hassio on Rasp 3b+

splunkenizer · April 12, 2020, 9:50am

Since 107.7 the update notification in the GUI does not work correctly. The updater services reports the correct new version, but I did not get the update button showing up. I did the update via cli and everything works fine. But now it’s reporting the wrong latest version in the gui and the cli as well.

How can I fix this?

config $ ha core info
arch: amd64
audio_input: null
audio_output: null
boot: true
custom: false
image: homeassistant/qemux86-64-homeassistant
ip_address: 172.30.32.1
last_version: 0.107.7
machine: qemux86-64
port: 8123
ssl: true
version: 0.108.3
wait_boot: 600
watchdog: true

tom_l · April 12, 2020, 9:58am

Have you tried clearing your browser cache?

BertrumUK · April 12, 2020, 10:23am

Yep - see here

mac_intos · April 12, 2020, 12:15pm

Update : managed go back with the wipe and restore function

splunkenizer · April 12, 2020, 1:54pm

Hi

Was that answer to my version issue? If yes, I have tried with a cleared browser, but no change. That would also not explain, why the cli is reporting the wrong version as last_version.

tom_l · April 12, 2020, 1:57pm

If it’s reporting that you are still on 0.107 then your update failed.

filmgarage · April 12, 2020, 2:07pm

My Homekit setup was broken. I thought I messed up but it turns out that 0.108.3 fixes my issue. I wasn’t able to switch on/off groups or rooms with Siri commands anymore. Now everything is working fine again. Thanks!!!

Meeseeks · April 12, 2020, 2:42pm

I had to reinstall my venv environment. After that everything works.

rodpayne · April 12, 2020, 3:36pm

Regarding hide_entity option being deprecated:

I have many, many warnings in the log like:

2020-04-11 20:47:05 WARNING (MainThread) [homeassistant.components.automation] The 'hide_entity' option (with value 'True') is deprecated, please remove it from your configuration. This option will become invalid in version 0.110

Before the end comes, could the name of the item or the configuration file location be added to the warning message to make it easier to track down?

Is this the same as hidden: true in the entity attributes, and Hide from UI in Customizations? I can find those and, if so, you can disregard the ask in #1. It just could use a better description in the warning for what to look for.
Just because hidden: true no longer has a direct effect in the UI, why is it necessary to purge it from the attributes of all entities? It is possible to configure Lovelace with an entity state filter that references the attribute, somewhat preserving the functionality.
Why doesn’t Lovelace honor it as an implicit filter in the first place?

123 · April 12, 2020, 4:02pm

Should your request not be implemented before 0.110 arrives, this works from the command line in the config directory:

grep --include=\*.{yaml,py} -rnw "hide_entity"

It will search, recursively, through all files ending with .yaml or .py, in all sub-directories and report the file and line-number containing the matching word hide_entity (or any other word you may wish to find).