After update to 5.1.1 HomaticIP Switches do not work anymore in Switch Manager

[thluther]

Describe the bug
After the update to Switch Manager 5.1.1 all Homeatic IP Devices do not work in Switch Manager anymore. They still work in HA though.
Downgrading to 5.1.0 does not change anything.
Other devices like IKEA still work.

To Reproduce
Steps to reproduce the behavior:

1. use switch
2. try to integrate new switch - identifier not found

Expected behavior
Just work as before

Screenshots
n/a

Desktop (please complete the following information):
not a factor

Smartphone (please complete the following information):
not a factor

Additional context
HA Green 2026.9.0
Homematic(IP) Local for OpenCCU 2.10.0

[StefanHesse]

I have the same problem. After updating from 5.1.0 to 5.1.1 Homematic devices stop immediately to work and no new switches can be added because identifier can't be found.

[GodiHSW]

Same Problem here. I did not update this Integration but the problem occurs also with the old V2.0.5 from Sian-Lee.
Probably an issue with 2026.9?

[StefanHesse]

I had 2026.9 and 5.1.0 and it worked perfectly until I updated to 5.1.1. So it seems to be a problem of Switch Manager.

[Freak128]

I have the same problem. Automations using Homematic switches are working.
As far as I can tell, the homematic.keypress event isn't being triggered. The switch statuses are displayed correctly in the Homematic IP integration.

[asmitconsulting]

My situation is a little different: Until recently, I was still using the old V2.0.5 from Sian-Lee. After updating to HA 2026.09, none of the buttons responded anymore—so I completely reset the HA to its latest version—and everything worked again. Then I switched to the new 5.1.1—that worked too. After I reinstalled 2026.9, the same issue occurred—none of the buttons execute their assigned functions.
I use various Homematic switches (2- and 6-button models, as well as 8-button remotes) and Hue switches, and the commands range from simple switching operations (on/off/toggle) to triggering scripts with Hue, Homematic, and other devices.
I suspect that a central component was changed in version 2026.9, which will require an adjustment to the Switch Manager.

[StefanHesse]

I updated to 2026.9 on Wednesday evening right after it was released and used version 5.1.0 until noon today. I could swear that everything was working fine up until then.
It wasn't until after the update to 5.1.1 this afternoon that I noticed the Homematic devices were no longer working.
What contradicts my observations is that downgrading to 5.1.0 doesn’t solve the problem, and unfortunately, I can’t restore a backup from before 2026.9 to test it out, so I’ll retract my claim just to be on the safe side.

[macpit]

Thanks everyone for the detailed reports, they helped a lot to narrow this down.

From what I can see so far, this most likely isn't caused by Switch Manager itself, and the timing with 5.1.1 seems to be a coincidence. The Homematic blueprints and the event listener haven't changed since v3.0.9, and the 5.1.1 diff only touches frontend components. That would also match your observations that downgrading to 5.1.0 or using the old 2.0.5 doesn't help while IKEA and other integrations keep working.

What I believe is going on: Homematic(IP) Local 2.10.0 appears to no longer fire homematic.keypress (and homematic.impulse) on HA 2026.9. HA 2026.9 replaced voluptuous with the probatio shim, and the integration's click event schema then seems to keep requiring a channel_no field that has already been removed, so every button press is dropped silently. The only trace is a DEBUG line like:

The EVENT could not be validated. ['channel_no'], required key not provided

This is exactly what @Freak128 described (event not reaching the bus while the entity states update fine). It is tracked upstream as SukramJ/aiohomematic#3374, and a fix has been merged in SukramJ/homematicip_local#1287, currently available in the pre-releases 2.10.1b11 and 2.11.0b0. A stable 2.10.1 is announced.

Could someone affected please verify this? Two things would help:

1. Enable debug logging for Homematic(IP) Local, press a button and check whether the line above shows up in the log.
2. If you are comfortable with pre-releases: enable them for Homematic(IP) Local in HACS, install 2.10.1b11 or newer, restart HA and check whether the switches react again. Switch Manager should pick the events up without any changes on its side.

Please report back either way. If it turns out to be something else, I'll dig deeper on the Switch Manager side. I'll keep this open until we have confirmation.

[Jibbonator]

Installed 2.11.0b0
Working again. Switch Manager working as expected.

[macpit]

Thanks @Jibbonator for confirming! So the Homematic(IP) Local pre-release (2.10.1b11 or 2.11.0b0) fixes it, no change needed in Switch Manager. For everyone else: if you'd rather not run a beta, the fix is announced for the stable 2.10.1 release of Homematic(IP) Local. I'll keep this open until that ships and close it then.

[macpit]

Small update: upstream renumbered the upcoming stable release, the fix will ship as Homematic(IP) Local 2.11.0 (not 2.10.1), see SukramJ/homematicip_local@d12c643. Not released yet as of today, only 2.11.0b0. Note it also contains several entity/device registry migrations, so take a backup before updating. I'll close this once 2.11.0 is out.

[Freak128]

Special thaks to @macpit and @SukramJ for your great work! With version 5.2.1 of Switch Manager and pre release version 2.11.0.b.0 of Homematic IP local everything works fine!

[macpit]

Thanks @Freak128 and @Jibbonator for confirming, and thanks everyone for the reports. Closing this: it's an upstream bug in Homematic(IP) Local 2.10.0 on HA 2026.9, nothing in Switch Manager needs to change.

Summary for anyone landing here: if your Homematic switches stopped working after updating to HA 2026.9, update Homematic(IP) Local to 2.11.0b0 (HACS → show beta versions) or wait for the stable 2.11.0. Take a backup first, the release contains registry migrations.