Thanks Sean… one of your earlier examples threw me off… I thought I tried that before but apparently not as yours is working for me now. Cheers.
I upgraded to 0.105.2 and HassOS 3.9 today. The upgrade itself seemed to work great, but lots of things broke afterward.
ESPHome can no longer do OTA updates, Node-Red stop functioning altogether (redoing that installation).
I did 0.105.2 first then the OS, did I do the wrong order. Should I have expected so many issues with this update? All my components were up to their latest and greatest version before upgrading (jus to make sure).
1 Like
Why is there still no warning like “Do not install 105.2 it still not reliable with Z-wave…” or other things…
One solution would be to FORCE new version program to check if Check Home Assistant Configuration was run before. It would avoid bad surprises…
WTF? esphome is a completely separate application. How can updating home assistant or hassos affect it?
? This is not very adequate…
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)