2026.7.2, just noticed that when asking “What’s weather?” Assist finally replies temperature value too 
Version 2026.7.2 is changed the language from Spanish to English in some UI elements.
In addition, the state of position-aware device trackers is now the smallest zone the device is in, instead of the zone whose center it is closest to.
This feels like a well meaning change that has a side effect. I think (by looking at the Pull Requests) that the reasoning was to better support concentric zones (home, surrounded by a bigger near_home).
However, it exposed a problem for me; I have two zones that are very close (home and and office 100 meters away). My wife’s phone occasionally reported her location with a radius of 200 meters (I since reduced the minimum acceptable radius in the companion app, fixing the issue, but still, this feels wrong) and that made her constantly flip-flop between home and the smaller, but further, office zone.
Location report with a high uncertainty are still usually precise enough that the distance from the center should take priority. The smaller radius should be taken in consideration only when the distance is tied (so for concentric zones). For zones that are near each other and happen to fall into a wide uncertain location, the zone radius has no meaning (if I had to chose, the BIGGER one should win in that case. But I understand the opposite reasoning for concentric zones)
edit: went to open an issue, and found this 2026.7.2 Android device_tracker Zone State is Less Predictable With Some Use Cases · Issue #176316 · home-assistant/core · GitHub
Here’s a core issue for the spanish language issue: https://github.com/home-assistant/core/issues/176288
Don’t really know what happened, other than to say it’s not a code bug, and may have been some kind of vandalism (or a very misguided user) in the lokalise project.
2 Likes
Has anybody done, or had any issues with, the RPi 4 firmware update? I received an update notification with this release to update from 2019-09-10 to 2026-01-09. That’s a LOT of updates according to the change log. I don’t have issues with my Pi4 currently, and wondering if it is worth the risk. Still running completely on the SanDisk Express SD card I created back in Mar 2020.
At a previous Core update from 2026.5.4 => 2026.6.1 my RPi4 CPU Usage doubled from 10 to 20%. Interesting enough, at the recent update from 2026.7.1 => 2026.7.2 this was fixed and I returned from 20 to 10% CPU Usage again 
No idea which specific repair fixed did this 
but big thanks anyway! 
2019 version of what? HA’s date based versions started in 2020. If you’re truely on a 2019 version of HA, that pretty much predates all UI things. You’d be best creating a post asking what to update. Off the top of my head, you’ll likely need to look at updating templates and manually configured mqtt entities assuming you use them. Other than that, most things are the same. Oh, and GPIO is now a custom integration.
am thinking it’s a Pi Firmware from 2019 query rather than HA …the new HAOS 18 plus Core 2026.7 surfaces updates for Pi Firmware in HA so it’s a whole new world…
(upgrading firmware via HA worked great on my Pi5 as a side note)
2 Likes
I have four Powerwall 3s and tried to connect them to HA after this update. Using the last five characters of the WiFi password on each Powerwall I was able to get past the initial authentication dialog, however, three of the four of the Powerwall did not complete the setup and gave me the same error message:
Failed setup, will retry: Updated failed due to Powerwall api error: API returned status code ‘502: Bad Gateway’ , will retry
The fourth device was successfully added and its data shows up via local polling. I assume that only one will act as the “gateway” so this might be expected. So if others have more than one Powerwall, try adding the others / primary one.
If I should expect all four Powerwall 3 devices to be connected, someone please help.
No, the language is fine, what changes are some things in HA, the others remain in Spanish.
RPi 4 firmware. Not talking about HA, other than the new notice it provides about the update.
1 Like
(Replying to myself)…
Found out that some of the intents were refactored, which introduced breaking changes for customized sentences: rule expansions<name>, <area>, and <floor> were removed, but each can be replaced with a list structure: {name}, {area}, and {floor} (which is what I did to fix the problem).
2 Likes
No, Spanish language are not working, after update 2026.7.02 maybe is not a core problem, but it seems that translations in Lokalise service are not working , who will solve this issue?. Who is responsable for this translation service?. Right now seems that all is ok in lokalise, but in HA still problems with 2026.7.2 and reverting 2026.7.1 solve the problem
Note that the <name>, <area> and <floor> expansion rules had the article(s) optionally included, so basically <name> was [the] {name} and for example in Dutch it was [de|het] {name}.
So make sure to add the articles where needed.
1 Like
Valid translations are downloaded and shipped as part of a release. If the translations in lokalize are good again it should be fixed automatically in 2026.7.3
Right now seems that all is ok in lokalise
No, things are not ok in lokalise.
Nearly every spanish translation is still marked as “unverified”. Until it becomes “verified”, it will not ship in 2026.7.03 or any future version.
The only two paths forward is either:
-
community translatiors need to re-verify 45,000 translations (and then maybe whatever happened will just happen again and we’ll be right back to where we are now)
-
or someone at a high up adminstrator level (maybe 2-3 people have this role?) needs to figure out what happened to these keys, since there’s no publicly visible information on why they became unverified years after their last translation update.
1 Like
Anybody else having problems with voice Assist aliases since 2026.7? My aliases for my air conditioners stopped working when I upgraded.
Exposed to Assist, was working fine in 2026.6 and earlier:
But now:
I’m experiencing the same issue. I’ve built my own alarm that automatically reactivates after a set timer time.
Movement restarts the timer and I can see the timer time counting down from the new restarted time. Even though the timer has time left, it still finishes based on the first time set.
I’ve tried to cancel the timer and start it again, but it seems to be storing the first timer time in the background somewhere, as it doesn’t matter if I cancel it, timer.finished still triggers based on the first time the timer was set.
I’m having the exact same issue. I initially thought it might’ve been just MelCloud but just tried aliasing my Tuya AC and it gives the same error, might be a climate entity issue.
Editing to say it looks like it’s being worked on:
3 Likes
I had the same issue. But when Home Assistant restarts, it loses it’s functionality. And I have to delete the device and repair.
Have you experienced the same?