Just as a datapoint, I updated my Zwave instance to .105.2 without issue so not sure what problems people are running into.
1 Like
@fuzzymistborn I’m very happy that you successfully updated.
Here’s the problem so many people encountered:
starting version 3.2.8
[16:37:40] INFO: Don't worry, this temporary installation is not overwriting your current one.
[16:37:40] INFO: Installing Home Assistant: latest...
[16:37:40] INFO: Please be patient, this might take a few minutes...
Fatal Python error: initsite: Failed to import the site module
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site.py", line 73, in <module>
import os
File "/usr/local/lib/python3.7/os.py", line 27, in <module>
import stat as st
ModuleNotFoundError: No module named 'stat'
[16:37:40] ERROR: An error occurred while installing Home Assistant:
or you can read this: Can't update hassio to 0.105.x
If you have a solution, you’re welcome!!!
just adding to the state_color discussion here, @i00 issued this: https://github.com/home-assistant/home-assistant-polymer/issues/4821
1 Like
I do not know what is this missing python folder is. And hassio just updated it to the latest 3.10, but still the same. Will be more patient and wait a couple of days…
It’s interesting to see how this whole situation with state_color will pan out in the end… but so far that issue (and similar ones asking for more or less opposite) have been closed with a very lapidary ‘it’s by design’ comments.
hope it will be ‘re-evaluated’ . that’s why I added some valid arguments for that, while acknowledging we need to go forward.
device_class wasn’t invented in vain though, firmly believe the design team will see that.
will keep my customize_domain’s for the moment though:
automation:
custom_ui_state_card: state-card-custom-ui
templates:
icon_color: >
if (state === 'on') return 'rgb(251, 210, 41)';
return 'rgb(54, 95, 140)';
binary_sensor:
custom_ui_state_card: state-card-custom-ui
templates:
icon_color: >
if (state === 'on') return 'rgb(251, 210, 41)';
return 'rgb(54, 95, 140)';
input_boolean:
custom_ui_state_card: state-card-custom-ui
templates:
icon_color: >
if (state === 'on') return 'rgb(251, 210, 41)';
return 'rgb(54, 95, 140)';
switch:
custom_ui_state_card: state-card-custom-ui
templates:
icon_color: >
if (state === 'on') return 'rgb(251, 210, 41)';
return 'rgb(54, 95, 140)';
4 Likes
To do with polishing of gemstones?
I have the same problem with 105.2, have to downgrade too. 0.104.3
no, snooker balls 
If by ‘very lapidary’ you mean the comment was ‘typed with two middle fingers’ then, yeah.
1 Like
A lapidary is an artist or artisan who forms stone, minerals, or gemstones into decorative items such as cabochons, engraved gems, and faceted designs. A lapidarist uses the lapidary techniques of cutting, grinding, and polishing. Hardstone carving requires specialized carving techniques. Wikipedia
1 Like
Just use anchors on entities cards if you don’t want to type state_color over and over again
anchors:
entities_color: &entitites_color
type: entities
state_color: true
…
- <<: *entities_color
entitites:
- ...
1 Like
I don’t know how to do that.
Just place that at the very to of the Lovelace.yaml
Then you just reference it in your views.
This will probably be a confusing explanation, but here goes… If you are familiar with a conditional card, the entity-filter card works very much the same way. It’s really more of a ‘helper’ card that displays another card inside of it.
Here’s an example code block with comments.
# This is the required portion where the filtering takes place
type: entity-filter
entities:
- person.arsaboo
- person.melody
state_filter:
- not_home
# Now this is the card that it displays the filtered results in
# Everything below is optional, without, it'd default to next two lines
card:
type: entities # could also be "glance" or "map"
title: Family Members Outside Of Home
show_header_toggle: false
state_color: true
So basically the top lines do the filtering, and then it gets displayed in another card. Everything under card: is the actual Entities card being displayed, so that is actually the top-level setting even though it doesn’t appear to be at first glance.
The confusing part here (and I believe the part you got tripped up on), is that card: and everything underneath it is completely optional for entity-filter card. Most examples you see don’t include all the lines I did. If you don’t specify things, it will use this as the default:
card:
type: entities
So it’ll work just fine, but without that in place, it then becomes unclear where to add the extra card options like title, show_header_toggle, and state_color. The above code should clear it up I think…
Hopefully my explanation made made sense, I had a very long/busy day and am super tired 
2 Likes
It’s done. #31720
1 Like
I believe the last line should be state_color: true (for the sake of those who just copy/paste and get an error)
1 Like