Totally agree with you, but when people ask something, he could also choose not to answer instead of answering with aggressivity. WTF is not very nice…
no problem, a nice day, or night.
of course, if you personally don’t like another person’s style.
but just imagine if in this public forum anyone starts WTFing or bullying others in any way? I bet there will be no option to
very soon. that’s why moderators (and flagging) do exist.
not teaching anyone, but it’s not so ideal here.
Thanks for resolving the problem.
What is the reason for
entity-filter card handing the option differently?
I and others have made the same mistake and entered
state_color as a first-level option of the
entity-filter card. Why does it use a different convention compared to the other cards?
(Not complaining, just trying to learn more)
Just as a datapoint, I updated my Zwave instance to .105.2 without issue so not sure what problems people are running into.
@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
Maybe its hass.io related. I run in Docker.
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)';
To do with polishing of gemstones?
I have the same problem with 105.2, have to downgrade too. 0.104.3
no, snooker balls
Have you or @erikkt placed an issue on github?
If by ‘very lapidary’ you mean the comment was ‘typed with two middle fingers’ then, yeah.
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
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: - ...
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.