Yes, I had a similar problem
I restarted HA core with trusted_proxies and use_x_ commented out and still receive the same browser errors. I do have HAOS pointed to a stand-alone Pi-Hole instance if that would effect the connection.
Temporary work around
Did you find any updates on this? Lost all my vacuums and purifier, only could get back the one vacuum that was on the cn server, however 2 vacuums and the purifier are on the DE server and i get unknow error when trying to incorporate them.
I have over a hundred errors in my core log.
2021-07-13 18:31:29 ERROR (MainThread) [homeassistant] Error doing job: Unclosed connection
2021-07-13 18:34:03 ERROR (MainThread) [homeassistant] Error doing job: Unclosed connection
2021-07-13 18:37:41 ERROR (Recorder) [homeassistant] Error doing job: Unclosed connection
2021-07-13 18:44:11 ERROR (MainThread) [homeassistant] Error doing job: Unclosed connection
2021-07-13 18:46:43 ERROR (Recorder) [homeassistant] Error doing job: Unclosed connection
2021-07-13 18:50:13 ERROR (MainThread) [homeassistant] Error doing job: Unclosed connection
Can this be related to the recorder changes? I’m not using @ anywhere at least that I realize. I’ve already deleted my database to no avail.
I also got a warning from the supervisor that I was using a unsupported install. Im on a pi with the sd card image.
core-2021.7.2
supervisor-2021.06.8
Home Assistant OS 6.1
It gives me a network error and points me to this page.
I was able to clear after a couple of restarts. After deleting the DB it returned but after sevral restarts disappeared again but still have the first error.
Anyone? I haven’t had any trouble with this HA release so wanted to try out the new features…
EDIT: the node status entities are disabled by default but can be enabled in the z-wave device settings GUI
Official fix is in 2021.7.3
1 Like
I have a graph with 10 temperature sensors, the legend is actually bigger now than the graph. Plus the °C is shown vertically bottom to top direction written meanwhile the ticks marks and values are written horizontally left to right. And that refresh bug is affecting the Android Companion App as well, when a graph turned off and the display refreshes it just puts back the graph.
Hi! About trigger ID’s, if I use a ID like “Disarm” i got id: ‘“Disarm”’ in the YAML file. Should ID has double quotes?
…without reading the breaking changes before updating.
4 Likes
or just accept local reverse proxy by default…
Nobody is chaining you here to HA. you are free to go elsewhere if you find somewhere better. I just came back here after 2 years of trying to do that.
no feedback allowed? sorry…
You’re not going to get much sympathy if you don’t read the release notes particularly when something breaks. There have also been warnings in the log files since a few releases before the break occurred.
The change you think is obvious would cause some reverse proxies to break… witness the myriad NGNIX threads about this.
1 Like
Not if you do not RTFM. This forum is not a substitute for that. At least you do not need to wait for months for a fix to undocumented breakage. I just endured that elsewhere.
Fortunately, I know how to fix a bug when it occurs: by reading the changelogs. Still, I think home assistant should simplify my life, not lead to more effort. If I have to read the logs every day or the changelogs before every update, I might as well run to the light switch every time or adjust the heating manually. This is not a relief and should be made more user-friendly in my opinion.
I install photovoltaic plants. Many of my customers would like to use something like home assistant to charge their car or manage their electricity. However, since such things happen from time to time and behause I cannot expect a normal user to know what a changelog or log is, I cannot recommend home assistant to such customers. I think this is a pity, because it is a fantastic software.
In my opinion the update policy should be more end-user friendly.
2 Likes
Marius,
Your comments are valid, but HA is not a system like that. Try SmartThings and you will swear every day when they change something in the cloud backend, without mentioning anything or documenting it at all.
But in HA, you are not forced to update to the latest version. If it is not broken don’t fix it, that’s how the old saying. If you need the new features then read first the breaking changes part of the release notes and consider what you need to update to run your system smoothly.
Regarding the reverse proxy issue, many of us uses Nabu Casa’s service to support the development of Home Assistant and we haven’t experienced any downtime.
I did update my system this morning from more than a 1000 km from home and everything went smoothly. But I read along the breaking changes and all the comments in this topic during the last few days before doing that.
2 Likes
If you try openHAB you may either need to wait months for a fix or run daily snapshot code. It is written in Java to make debugging more challenging ;).
Haha, I can see emoticon, but cannot believe anybody could have such imagination about Java. could you elaborate more please?