You should be able to test using.the services tab under development tools. Select fan favorite level. Only few models support this btw.
there’s an issue for some drop-down blocks in the frontend, but never saw it block the language selection (probably because I never did change that…)
Now I had a reason to do so, the huge list wont drop down past my Safari window border (on a Mac), and I am unable to scroll at all…
I realize some people don’t like Safari, but this really is a bug now…
I’m on Windows 10, so not Mac specific. And my slowness came back as bad as ever after a couple days on this machine, so it wasn’t just a one time fluke. I have the warning about lit-element as well as a couple more:
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features!
The resource at “http://homeassistant.local:8123/static/fonts/roboto/Roboto-Medium.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly.
Thanks for the great update. I am amazed by how many new features and small fixes are packed into every month’s update!
Question about grouping media players:
What does it actually mean? Is it now possible to combine different speakers (like Musiccast and Alexa Echo) into one group and listen music?
Thank you
Same behaviour for me. It’s working with curl and my API Key, but I’m getting invalid API Key in Home Assistant 
It might have something to do with the length of the API key. I need to check max input, but now busy with dinner !! If you can, check great 
I’ve lost external access through DuckDNS/NGINX with 2021.7.n. I changed my http: config to:
http:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# server_port: 8123 - for duckdns
# ssl_certificate: /ssl/fullchain.pem
# ssl_key: /ssl/privkey.pem
use_x_forwarded_for: true
trusted_proxies:
- 172.30.33.0/24
ip_ban_enabled: true
login_attempts_threshold: 15
My attempts to open my duckdns domain produce this error on the browser (mozilla and Chrome). FYI, trusted_networks no longer works with Chrome. I need to use my credentials to get in.
The site at https://mysite.duckdns.org/auth/authorize?response_type=code&redirect_uri=https://mysite.duckdns.org/?auth_callback=1&client_id=https://mysite.duckdns.org/&state=eyJoYXNzVXJsIjoiaHR0cHM6Ly9taWxsYWFsdGEuZHVja2Rucy5vcmciLCJjbGllbnRJZCI6Imh0dHBzOi8vbWlsbGFhbHRhLmR1Y2tkbnMub3JnLyJ9 has experienced a network protocol violation that cannot be repaired.
I’ve verified both NGINX and DuckDNS add-ons are running.
Only put the proxy IP address in trusted proxies.
You mean not the /24? I have - 172.30.33.6 as the proxy. Changing to that specific address didn’t change the error. No errors in ha log.
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