2026.5: We're on the same frequency now 📡

Blog
67

@Brookke

The new maintenance dashboard is a great addition :+1:

One thing I noticed though: it seems to only detect battery entities reporting percentages (device_class: battery), while integrations exposing battery state as enums (low / medium / high) are ignored completely.

For example, the Withings integration now exposes battery state as:

device_class: enumoptions: low, medium, high

which is technically well-modeled, but these devices never appear in the dashboard. It would be great if enum-based battery entities could also be included in some way.

3 Likes
68

Great addition this month again. Thank you the team and community.

With this new release, I got to update the navigation path from /hassio/ingress/dxxxx_music_assistant to app/dxxxx_music_assistant

This is my existing shortcut solution but I will look to the new shortcut card as well in future.

type: custom:mushroom-template-badge
content: Music Assistant
icon: mdi:playlist-music
color: orange
tap_action:
  action: navigate
  navigation_path: /app/dxxxx_music_assistant

I have also shortcut in title which is appear only on mobile like this example.
This is still OK after the update:

type: custom:mushroom-chips-card
chips:
  - type: action
    tap_action:
      action: navigate
      navigation_path: /lovelace/temperatur
    icon: mdi:temperature-celsius
  - type: action
    tap_action:
      action: navigate
      navigation_path: /lovelace/ev
    icon: mdi:car
visibility:
  - condition: screen
    media_query: "(min-width: 0px) and (max-width: 767px)"
69
1 Like
70

I DON'T AGREE
to your post, documentation wasn't "a scream headline".
We all know: writing documentation is boring and often regarded useless or not worth the time (expecially our chefs). The more it is valuable that this HA team does this work not only good but even better. Because: we all NEED the documentation. It's the interface between the HA team's work and the feature a user wants to use. Without we had no idea what is possible and how to achive it. Look at so much quite nice chinese gadgets: no documentation -> garbage. Or do reverse engineering. If you can.
So: THANKS for documentation, THANKS for even impoving it!

4 Likes
72

os
os616×351 14.5 KB

:thinking: For some reason the 15.2 OS version is flagged as skipped but the newer versions are ignored (won't show) and I don't have buttons to unskip it.

I would like to access Advanced SSH & Web Terminal to force updating but some of the UI links aren't working, /config/app/a0d7b954_ssh/info throws "Error while loading page app."

Edit: I managed to trick it into updating to OS 17.3 from the Developer tools part of the UI, still having the UI pages errors.

I will probably manage to update core to 2026.5.1 the same way so the UI will be fixed.

Edit2: So after emptying my browser cache all works perfectly in the UI, I should have started with that yesterday...

73

The new maintenance dashboard is a great start to replace some of the custom views I've got! Is there any way to use the dashboard/ it's contents within a view instead? I have a "Status" dashboard that links off to subviews for various things (e.g. batteries, media players, etc.) and the maintenance dashboard is the perfect replacement for my unloved batteries view.

1 Like
75

I'm not going to say this again, and I've already said it once before:

RBAC and ODIC is not part of the release. Please take this to a feature request, or make a separate topic. Just stop the conversation in this topic. Thanks.

@stevemann @BodhiPolitic

4 Likes
76

The release post specifically calls out making the Roadmap public. The discussion began with a question on how we, the users, can get features added to the Roadmap. Either that announcement should have been it's own separate post, or the requests for clarification on how the Roadmap can be contributed to are 100% on topic.

3 Likes
77

Sorry but no, these 2 topics constantly crowd release topics. It happens every time the road map is discussed. It's not happening again. The team knows about the feature requests, the topics have been discussed to death. We do not need another place. If you wish to discuss either feature, use the following links for each discussion.

RBAC Feature Request

ODIC Feature Request

EDIT: Adjusted the comment to appease a few upset individuals.

5 Likes
78

The documentation for Home Assistant is massive. It always amazes me that the docs keep up with changes and additions to core.

Yes, some of the docs are written by engineers. And only engineers can grok. Some are exceptionally comprehensive that even Grandma might understand.

If you don't understand what a particular doc is saying, just ask here. And when you figure it out, pass it forward:

docs
docs788×192 20.7 KB

1 Like
80

Ok, I noticed that all of my routines show up as entities in HA via Alexa Devices. When I click press on the entity it does nothing (either via UI or as part of script). Some of my routines actually respond back via voice to a device spoken to, etc if the routine is to speak back and some routines just carry out commands like turn on something via skill, etc.. Is the press button the way to invoke these routines in HA? or was the send_text command was supposed to support routines since it allows you to select an echo device? Either way, the routine invocation is not working. Thanks for your support.

Here is the yaml from the button press on a routine that is called "tester"

action: button.press
metadata: {}
target:
entity_id: button.my_amazon_account_tester
data: {}

81

It's the button.press action that should run the routine.

82

Here is the yaml from the button press on a routine that is called "tester". The keyword to invoke the routine is another word, but the routine is named "tester" in Alexa. Nothing is happening when this is invoked.

action: button.press
metadata: {}
target:
entity_id: button.my_amazon_account_tester
data: {}

83

Right, so all you do is call that and the routine should run. Or press the button in the UI.

84

I know, I know, “documentation” doesn’t exactly scream headline feature. But hear me out: making Home Assistant more approachable is one of our biggest missions this year, and darn good documentation is a big part of that. We’ve expanded our documentation team and are investing heavily in this, and the new templating docs are the very first taste of what’s to come. I’m really proud of where this is heading. :books:

I assume I'm in the minority on this, but I think reading every manual and document from software to even appliances is a really nice "life-hack" with the amounts of things you will realize your software and hardware can do. Specially in the Smart (or not so much) Home, where appliances hide option like turning the beeps off under odd key combinations.

It's honestly frustrating useful features and choices are hidden beneath obtuse language or hundreds of redundant pages.

So I'm incredibly happy to hear of investment on documentation!

I've done many templates, and before this release I've already noticed the improved documentation and it is probably going to save me so much more time than a lot of (of course necessary) software improvements in homeassistant might have in its place.

Navigating the Jinja original page... (no offense to the jinja developers, writing and hosting documentation well isn't easy) was a headache. It doesn't support dark mode nicely with any browser extension or css trick, the index does not follow you so you have to constantly hit the Home key... it was incredibly tedious.

Now? It's all in HA's documentation, which is on a fluid, intuitive webpage with incredible examples. And now the autocomplete "intellisense" like feature is the cherry on top.

Incredible stuff, I hope to see more love given to integration documentation, specially for those integrations that have been in HA for a while, and had more and more headings added to it. It really increases HA's value.

It reminds me of Archlinux, some pick said Linux distribution because of its incredible wiki, and many including myself use it even if they use other distributions because of how good it is!

3 Likes
85

Breaking HA update/upgrade for Frank Energie integration due to missing dependencies:

Logger: homeassistant.setup
Source: setup.py:278
First occurred: 00:47:11 (1 occurrence)
Last logged: 00:47:11

Setup failed for custom integration 'frank_energie': Requirements for frank_energie not found: ['python-frank-energie==2026.3.22'].

Logger: homeassistant.util.package
Source: util/package.py:187
First occurred: 00:47:08 (3 occurrences)
Last logged: 00:47:11

Unable to install package python-frank-energie==2026.3.22: × No solution found when resolving dependencies: ╰─▶ Because python-frank-energie==2026.3.22 depends on cryptography>=44.0.1,<47.0.0 and cryptography==47.0.0, we can conclude that python-frank-energie==2026.3.22 cannot be used. And because you require python-frank-energie==2026.3.22, we can conclude that your requirements are unsatisfiable.

Solution: Install Release Update HA > 2026.5.0 · HiDiHo01/home-assistant-frank_energie · GitHub

86

hmm, seems deconz issnt working anymore? having issues connecting to the gateway?

2026-05-07 15:33:44.317 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz
2026-05-07 15:33:54.323 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at core-deconz
87

The script execution (button press) is reported as successful but the routine does not run - there is no error in HA logs. Also, button press is fine for routine actions with no voice response playback. However, for routines that do respond via voice (besides the usual "OK"), an echo device must be selected for context (in the Alexa mobile app for example) to speak back, which can be the device spoken to or another device. By the way, I am using Alexa+. Should I report this all of this as an issue in Github?

88

Yes report an issue

89

is ther something changed how it handles now usb devices? i have never had issues to my deconz usb stick, now after restart, seems it doesnt connect to it anymore? i have to restart the deconz addon