17 Likes
Another brilliant release. I like the interface updates.
Small problem on upgrade, an old ZHA quirks file (for Aqara H1) didn’t pass muster anymore and prevented ZHA from starting. Removing the quirk and deleting and re-pairing the devices solved it.
1 Like
Love the new changes to the flow of automations, but I still cannot connect Alexa Devices.
This has been a problem for at least three weeks now. Just tried it following the update, and the problem still exists. There were threads open for it since 2026.6.2, but they're all closed as "duplicate threads" with no answer, or direction to what they are duplicates of.
Hey, there's a release! I didn't get notified yet. I'm still on beta2, I got no updates for betas 3 and 4 that apparently did happen. I did move my instance to new hardware halfway during the beta week so that may have something to do with it.
Anyhow, lots of cool stuff, curious to see if the small nitbits I had in the beta have been resolved as well.
When will we get the Person purpose specific trigger back that was removed a few updates ago? I understand tjat it was not optimal, but I hoped it would be available until a better solution was ready instead of just removing it for months.
1 Like
Thanks for all the hard work everyone! Great release!
I was trying the Tesla Powerwall 3 setup since that was listed in the release notes. I did get past the integration adding, but then see:
"Failed setup, will retry: Updated failed due to Powerwall api error: API returned status code '502: Bad Gateway' , will retry".
I will go check my settings with the power wall but just posting here in case anyone else sees it and might have a solution.
Matt
1 Like
Thanks for yet again a great new - action packed - release. Kudos to all developers!
After the Update to 2026.7 my log says the sql database is corrupt and goes into an reboot Loop.
When i revert to 2026.4.3 it works perfectly..
An automation engine thinks in primitives. People don’t.
Apparently I'm not a person
2 Likes
Well done to the Home Assistant team and all the beta testers. It's looking really good, and I love the direction you're taking.
Also, a huge congratulations to everyone involved with the website and documentation. Wow... that's been a massive effort, and it really shows!
Blacky 
3 Likes
Isn't that just the zone.entered and zone.left triggers?
1 Like
They aren’t coming back, they were replaced with what @Didgeridrew said
Uhoh do NOT upgrade to this if you're using NGINX as an https proxy. You'll get this error:
Missing 'Host' header in request
edit: workaround in thread above - issue happens if you have http3 enabled.
1 Like
When the bedroom drops below 18°C, turn on the heating.
I do wonder how long before just typing (or rather saying) that is the new automations interface...
1 Like
@lancer73 While custom quirks aren't supported officially, with the original intention being that they're used for quick testing, we tried to keep backwards compatibility with the ZHA bump/refactor included in this release. Can you send or link the custom quirk file you used that broke with this HA version? Thanks!
Am I just missing something but I cannot figure out how to create an automation when I click on a Zigbee button in the new interface?
You probably want the "Event received"/event.received trigger... it's all the way at the bottom of the list.
As a Trekkie growing up in the 70's when you had to step on rubber mats to have the grocery store doors open automagically, this is my target.
I mean Ryker could just tell his room his expectations and bam, instant automation, Picard could do that to the Enterprise. Keep exploring HA.
1 Like
There are SSL cert changes in 2026.7 that will break the Rheem EcoNet integration. It ends up being the exact same as https://github.com/home-assistant/core/issues/172228 (see last comment). Rolling back to 2026.6.4 resolved it for me. Might want to list that integration in the backward incompatible changes section
1 Like
Thanks. But event.received does not give an option to use the button as an input.
This seems like a massive oversight on the part of the developers pushing this new interface out when you can't even set an automation to press a button to turn on a light.