What? Inadequate because you don’t understand what it means?
I do not Z-Wave or Zigbee. All of my devices are strictly wired or WiFi.
I wanted to mention what the state of HA was following the update. Trying to figure out if it’s the update that caused the issues, or something else and the update simply brought it to the surface.
did you run the Check Configuration Tool? For me it gives errors and rolled back in 104.3
Doing full restore to pre-upgrade. I cannot get Node-Red working. ESPHome is one thing, and I can live with that short term. Node-Red, however, is critical. Will do full restore, then test upgrade with my config on dev HA (been thinking about setting that back up anyway).
The addon check config? No, because that stopped working properly after version 0.96 for me. Took long time and didn’t provide a final status
yes. But there is a problem with 105.x, you can have a look there: Can't update hassio to 0.105.x - #43 by hfeenstra
Once again, you can flag again my answer, but this is a fact, you’re really aggressive with people who simply ask or report things, sorry for you if my english is so bad, maybe it’s due to the fact that i do not speak ONLY english…
5 Likes
Critiquing someone else’s style isn’t very helpful to anyone is it. If you don’t like a reply, ignore it and move on.
Thank you for the link. I am trying to restore from the snapshot I took before the upgrade.
Hopefully this issue will be fixed in the next release.
I didn’t flag your answer.
Yes probably I shouldn’t have said WTF and if I offended anyone I apologise.
3 Likes
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…
1 Like
no problem, a nice day, or night.
1 Like
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.
2 Likes
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.
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.