2026.5: We're on the same frequency now 📡

[RedKing]

@TheWanderingTurkey

Respectfully, this does not address the core question around how the decisions are made to add things to the roadmap. I would encourage the core team to consider opening up a real discussion about the roadmap itself through a dedicated blog post.

Open source just means that source code is openly available. It doesn't mean that anyone gets to vote on anything.

[xiport]

the old toggles didnt exactly match the off state icon blue, but they were complementary colors. the issue with the new toggle background color is that it leans toward a greenish hue which doesn't match with anything. this should get you back to the previous toggle colors, though it no longer looks good due to the new element styling:
--ha-color-on-primary-normal:rgb(3,169,244)!important;
--ha-color-fill-primary-normal-resting:rgb(15, 104, 145)!important;

i can live with the new default toggle colors with the exception of their new borders which I find very harsh and would highly urge the project to tone down. maybe its a nice contrast for a dedicated screen mounted to a wall, but for any other viewing it's obtrusive and lacks esthetic. this is basically mandatory:
span.switch:style(border-color:rgba(76,76,76,0.5)!important)

[parautenbach (Pieter Rautenbach)]

How would that work practically? To me this comes across as entitled.

[godofredo-dc]

Is it possible to have all three proxies in the same esp32? I have a bunch of Bluetooth proxies around the house and I wonder is they can be upgraded with ir and rf. Tks

[tonny1 (Tonny T)]

Yes same for me ?

[JohannCR (Johann)]

I agree with what has been said about theme breaking changes...
Those should either be optional/opt-ins, or the doc should at the very least provide detailed instructions on how to get the old look back.
And I don't mean a link to the list of css properties, but rather the values used in the default themes, otherwise it's a guessing game for most people...

I've tried the suggestions in this thread, but the only one that worked was for the dark theme.
Can anyone share the old switch color configs for the light theme ? Thanks !

[danielg88]

Fixed my problems with this release by manually installing aioesphomeapi

This is what I found in the error logs:
ERROR (MainThread) [homeassistant.setup] Setup failed for 'usb': Unable to import component: No module named 'aioesphomeapi'

[IOT7712]

@danielg88

Fixed my problems

I'd classify that as a workaround. Glad you got it going. Did you update the GitHub bug report with your results?

[dunxd]

I found that I can hide battery entities I don't want to appear in the automatic dashboards by opening their settings and switching off Visible. Happily the documentation about what this setting does is right there next to the toggle.

[Michel]

I think that should work, I have XIAO Smart IR Mate for IR and added a Bluetooth proxy to play around an that works fine. I don't expect the IR/RF components to be very demanding on CPU/memory. You just need to have enough pins to connect the additional IR/RF hardware.

[audiocommander (auco)]

Sorry, a bit out of the same frequency here: Can we maybe focus on updates that are less likely to break everything? I have run into massive problems with five (!) integrations with 2026/5: Tapo, MusicAssistant, SwitchBot, InfluxDB, Wyoming. It broke my doorbell, cam, Grafana and a lot of other things, even though I took care BEFORE and followed all migration guides. Still totally broken since the update. I know how to help myself, but I find myself constantly fixing things that are broken due to updates. This is not really necessary imho, if (e.g.) a protocol would be defined to be around for a while. And/or maybe have a better deprecation system. I need a stable system and updates that break things every two to three months so badly that HA is partially not running anymore, ...well... I tend to not update anymore then, that's not helpful either. Just my 2c, love HA, all best!

[monupurohit]

Tuya device not working post HA upgrade : Core 2026.5.1

The following integrations and platforms could not be set up:
openai_conversation
wled
tuya
homeassistant_hardware
zha
wyoming

• Unable to install package universal-silabs-flasher==1.1.0: × Failed to read universal-silabs-flasher==1.1.0 ├─▶ Failed to read metadata from installed package │ universal-silabs-flasher==1.1.0 ├─▶ Failed to parse METADATA file: │ /usr/local/lib/python3.14/site-packages/universal_silabs_flasher-1.1.0.dist-info/METADATA ╰─▶ Metadata field Name not found
• Unable to install package tuya-device-handlers==0.0.18: × Failed to read tuya-device-handlers==0.0.18 ├─▶ Failed to read metadata from installed package │ tuya-device-handlers==0.0.18 ├─▶ Failed to parse METADATA file: │ /usr/local/lib/python3.14/site-packages/tuya_device_handlers-0.0.18.dist-info/METADATA ╰─▶ Metadata field Name not found
• Unable to install package tuya-device-sharing-sdk==0.2.8: × Failed to read tuya-device-sharing-sdk==0.2.8 ├─▶ Failed to read metadata from installed package │ tuya-device-sharing-sdk==0.2.8 ├─▶ Failed to parse METADATA file: │ /usr/local/lib/python3.14/site-packages/tuya_device_sharing_sdk-0.2.8.dist-info/METADATA ╰─▶ Metadata field Name not found
• Unable to install package wyoming==1.7.2: × Failed to read wyoming==1.7.2 ├─▶ Failed to read metadata from installed package wyoming==1.7.2 ├─▶ Failed to parse METADATA file: │ /usr/local/lib/python3.14/site-packages/wyoming-1.7.2.dist-info/METADATA ╰─▶ Metadata field Name not found
• Unable to install package zha==1.3.1: × Failed to read zha==1.3.1 ├─▶ Failed to read metadata from installed package zha==1.3.1 ├─▶ Failed to parse METADATA file: │ /usr/local/lib/python3.14/site-packages/zha-1.3.1.dist-info/METADATA ╰─▶ Metadata field Name not found

details info:

Tuya device not working post HA upgrade : Core 2026.5.1

Issues post Home Assistant Upgrade

Installation methodHome Assistant OS Core2026.5.1 Supervisor2026.04.2 Operating System17.3 Frontend20260429.3 Post upgrade Tuya and ZHA devices are not loading Logger: homeassistant.util.package Source: util/package.py:187 First occurred: 15:26:14 (30 occurrences) Last logged: 15:34:10 Unable to install package universal-silabs-flasher==1.1.0: × Failed to read universal-silabs-flasher==1.1.0 ├─▶ Failed to read metadata from installed package │ universal-silabs-flasher==1.1.0 ├─▶ Failed …

[chrisdelt (delt)]

Hi,
Please can you consider and fix Rfxcom ?

RFXtrx integration fails to connect after upgrade to 2026.5

Hi, It's here, but does not work after reboot...

and there:

RFXtrx integration broken with Python 3.14 - pyserial Timeout.time_left() returns None causing TypeError in serial.read()

All my rollerblinds doesn't work anymore

Thanks for all

[trianglesis (Ole D)]

Strange CPU peak is now happening right at 00:)) for two days straight, as soon as I updated HA to 2026.5, and the next day to 2026.5.1

OS update was also installed with the 2026.05 version.

2 days

7 days

Two long peaks, about 1 hour long each, were only detected because PRi was too loud for too long, so I checked what was wrong.

Everything worked just fine, no critical errors, all responsive.

Peak usage goes back to normal as soon as I hit OS Reboot.

Installed on: RPi5

# ha core check
Processing... Done.

Command completed successfully.
# ha core stats
blk_read: 0
blk_write: 0
cpu_percent: 0.73
memory_limit: 8327102464
memory_percent: 9.88
memory_usage: 822767616
network_rx: 0
network_tx: 0

board: rpi5-64
boot: A
boot_slots:
  A:
    state: booted
    status: good
    version: "17.3"
  B:
    state: inactive
    status: good
    version: "17.2"
data_disk: MSI-M371-500GB-511250904141001345
update_available: false
version: "17.3"
version_latest: "17.3"

UPD: Yes, this is Music Assistant beta #10.

The issue:

• Very high CPU usage after midnight followed by MA restart since 2.9.0b10 · Issue #5454 · music-assistant/support · GitHub

[TheWanderingTurkey]

Who said anything about voting? I am asking for transparency in the process used to make roadmap decisions. Otherwise, what was the point in making the roadmap itself public, if not to encourage users to engage with the future?

Being open source doesn't mean users owe anyone their loyalty. This is a symbiotic relationship, not a dictatorship.

[NathanCu (Nathan Curtis)]

Eh. Not exactly. And this is a hard dish to swallow but it sets the correct expectations.

Open source means you get to see how the sausage is made... Full stop. Nothing else. People ascribe a lot to OSS that's not true and this is one of them. Open does not give you any inherent rights for design or execution.

Its like going to a restaurant with an open kitchen. It does not mean ANYTHING about you even getting one iota of influence about what's coming out of the kitchen (barring food allergies etc.)

What I mean is the minute you start trying to tell Wolfgang Puck what to do in his kitchen he has the right to point at the door.

Now you get to watch him make the pumpkin puree and the homemade chicken stock that goes in his world famous pumpkin soup but I guarantee it won't go well if you try to walk onto the line and demand he puts raisins in it. You want raisins go make your own soup... here's the recipe.

Yes I'm being melodramatic about it but it's basically the same thing. We have a community and we help each other but at the end of the day they have ZERO obligation to listen to a darned word any of us say.

Would it be a bad time for them yes. But they could. And none of us would have a leg to stand on.

So yes suggestions to what goes in the soup. But unless you're willing to put on your chefs whites and go to work... Tell the waiter about your allergies and enjoy the soup.

[PecosKidd]

Nice analogy, Nathan. Now, about those flies in the soup….

[RedKing]

@TheWanderingTurkey

Being open source doesn't mean users owe anyone their loyalty. This is a symbiotic relationship, not a dictatorship.

It's a software project. Don't get carried away by your metaphors.

[WeaselBreath]

How do we 'undo' the toggle switch changes? Sry, just like the last time change of moving the developer tool from the sidebar, it was the first thing I wanted to change after upgrading to this version. Any one else figured out how to revert back yet?

[reste_narquois (Chris Warne)]

I guess on the terms of Nathan's analogy, you either pick the flies out yourself (or volunteer to install a fly catcher in the kitchen to stretch it a bit), or just go up the road to another restaurant.