Note
Battery usage could be drastically reduced if Google opened their API for hardware hotword detection. Unfortunately, this is hidden behind a system API that only phone manufacturers have access to.
While unfortunate that they donāt open this API, am I right in thinking that because it is not using a Google API that companion hotword detection will be available in the FOSS āminimalā app variant as well? 
I really hope so! Fdroid releases are currently blocked but I will be excited to see when the new release drops!
1 Like
Finally room control for vacuum. Waiting for 2026.4 so I can use Google for it 
1 Like
Thank you OnFreund for the MTA integration. Looking forward to playing with that.
I am one of few left running HA Core in venv.
Despite python version bump update to 2026.3 went smooth and without any problems.
Thanks to team.
1 Like
Congratulations to the ZHA team for the milestone arbitrary semantic version 1.0.0 (and now 1.0.1)!
I donāt understand where the ānowā view is on the energy dashboard, with the little badges.
Logger: homeassistant.setup
Source: setup.py:278
First occurred: 21:32:45 (1 occurrence)
Last logged: 21:32:45
Setup failed for custom integration ānefiteasyā: Requirements for nefiteasy not found: [āaionefit-updated==0.16ā].
Edit: solved. Manually force update via HACS.
Mostly hidden, but one key aspect and widely impacting of this release, is * Custom integrations can now ship their own brand images.
This enables local caching of all brands! This is not perfect and still needs internet connection now and then, but itās a good step forward air-gapped home automation.
7 Likes
Are there some backend security updates coming? something from the roadmap? would be nice if it would be there with all the dashboard revamps. nothing would make me so happy. 
1 Like
https://github.com/home-assistant/core/issues/158007
I had a dream that this issue will be fixed 
No, another one here but first time Iām struggling to update to this releaseā¦ 
[RESOLVED]
Sadly, my Energy Dashboard did not survive the upgradeā¦
Nothing in the logs. Just this error where the dashboard should be.
UPDATE : Error only occurs when accessing instance via Nabu Casa URL. Energy Dashboard OK when accessed direct from local network.
FURTHER UPDATE : Error clears in Nabu Casa instance once session restarted.
Thank you all for new release 
Minimal version hotword detection works. I just tested itā¦ But from the lockscreen it sorta freezes and never draws anything.
Will the new Energy dashboard be able to handle more than one smart meter?
2 Likes
Update takes forever!!
Never happened before.
Itās been running for over 30 minutes now and only gotten to 44%. Itās creeping along at a rate of about 1% per. 3 minutes.
Whatās going on?
Iām upgrading from 2026.2.3 running on a Yellow.
Any plans to allow for custom wake words with the Android app? Iāve already made my own for microWakeWord and would love to be able to use them.
2 Likes
Thanks for the update. Only thing Iāve noticed is that MQTT seems to be more strict about payloads matching the auto-discovery schema; this is affecting switches exposed by Solar Assistant ( the discovery topic promises true or false strings but the actual state payload is 1 or 0). Iāve sent an email off to the SolarAssistant developers, hopefully that can get fixed soon. But wouldnāt mind if Home Assistant were more forgivingā¦
Edit: can work around this with manual configuration; Iāve shared an example for Deye/SunSynk/Sol-Ark inverters as a gist: Home Assistant MQTT configuration for SolarAssistant, Deye/SunSynk/Sol-Ark inverter Ā· GitHub
1 Like
Iāve seen this when i updated my HAOS test system to 2026.3.0b3 from 2026.3.0b2. It took a long time but eventually completed. I recommend to be patient by now until this is examined and fixed.