What needs to happen for OIDC to be put on the roadmap?
Anyone else having a second ZBT-2 discovered after updating to 2026.5?
the docker images are corrupt
ERROR: for homeassistant failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header
ERROR: failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header
I had the Lovelace UI completely broken on 1st boot, after a reboot most of the links in the left panel don't work and a few in the rest of the UI.
Error while loading page logbook.
Error while loading page history.
Error while loading page integrations.
Error while loading page logs.
Error while loading page calendar.
Error while loading page zwave_js.
Error while loading page core_zwave_js.
Error while loading page zha.
But a least the integrations, addons, automations & sensors are working, it's only the UI which is berzerked.
Since it all counts, it would have been nice to put OIDC on the roadmap to show that users (following feature request guidelines) are being heard/noticed since this is by far the feature request with most votes.
A serial proxy is nice but a usb proxy would be fab. Possible?
Seems like its more a platform which the devs use to promote their own ideas, as rarely any of the ideas get picked on, but that is just my view..
Edit: realized the question is rhetorical
Edit2: I do want the feature, I just don't like the way the devs handle feature requests. I rephrased.
Battery page should be able to display low battery devices only as an option. why would you want to sift through tens to potentially hundreds of items when you are only trying to find dead or low devices.
I tried to update my Yellow from HA OS 17.2 to 17.3 and it crashed and never came back up.
This is so frustrating.
In the maintenance page, I've spare batteries:
Issue in core or in frontend ?
Edit: my bad, i'm using the integration Battery Notes
Had the same issue (interestingly only on one out of 4 servers) -- a hard power cycle brought it back to life for me.
Something changed for conditions for entity-filter. The following code used the state of input_boolean.badges_einblenden for testing the state, after the update it seems to be ignored and state is tested against the entities in the list:
type: entity-filter
entities:
- entity: switch.steckdosenleiste_sekretar_usb
- entity: switch.radiowecker
conditions:
- condition: state
entity: input_boolean.badges_einblenden
state: "on"
Nice work with the (groupable) notify entities. Wondering how to supply parameters such as notification_icon (available for the original notify.mobile_app_*) to actions targeting these entities or groups thereof?
The action for these entities that is suggested by the automation editor (notify.send_message) does not allow to set any data except title and message.
Believe it is not possible, you'll need to continue using the old services for advanced usage beyond simple text notifications.
Buy a Usb to RS-232 Adapter, You do know USB IS a Serial Port ?
Bose Soundtouch has been broken by this release
Setup failed for 'soundtouch': Unable to import component: No module named 'websocket._dispatcher
The change to Alexa Devices for invoking routines as part of send text command does not appear to work. This change was included via Add routine management to Alexa Devices by chemelli74 · Pull Request #166291 · home-assistant/core · GitHub however it is not working.
Love the acitivity log on the security Dashboard. ![]()
![]()
But it would really benefit from an activity filter like the HA Node-RED event nodes provide:
- Ignore unknown states
- Ignore new state if last state was unknown
When you restart HA, the log is spammed with screens full of messages about everything that got unknown and back to it's current state after the reboot because of the 2026.5 update.
I gave up scrolling midway and didn't reach the first real interesting entry before getting bored. ![]()
Most likely this happened to a lot other users with large setups.
I bet many wanted to take a look at this feature after reading it in the release notes, just right after updating (and restarting).
The RS232 stuff seems very useful, I am not that familiar with ESPHome, does anyone have a suggested device for controlling RS232 with ESPhome?

