[Maintained Fork] Switch Manager – Wireless Button/Switch Action Manager (HACS) – v5.0.0 with Matter support

Share your Projects! Custom Integrations
, , , ,
1

Hey everyone,

a few months ago I posted about my maintained fork of the Switch Manager integration (originally by @Sian-Lee-SA, abandoned since). A lot has happened since v3.0.9, so here is a fresh summary – and the big one: Switch Manager now supports Matter remotes.

What is Switch Manager?

Switch Manager lets you manage the button presses of your wireless switches and remotes (Zigbee via ZHA / Zigbee2MQTT / deCONZ, Z-Wave, MQTT, BTHome, Hue, ESPHome, Tasmota, Shelly, Homematic, Lutron … and now Matter) through one UI – no hand-written automations. Pick a blueprint for your device, click a button on the device image and assign actions to press / press 2x / hold / hold (released) and so on.

:new_button: v5.0.0 – Matter support

Remotes added to Home Assistant over Matter don’t fire a bus event – each button is an event.* entity. Switch Manager now has a generic event-entity connection type for exactly that:

  • Pick the blueprint, press a button on the remote and auto discovery shows the device by name – done.

  • Ready-made blueprints (with device images) for the IKEA BILRESA dual button and the IKEA BILRESA scroll wheel.

  • Scroll wheels: Matter batches a fast flick into one event with a notch count. The new scale_field / repeat blueprint options turn that into a single, correctly scaled brightness step (or N runs of a discrete action) – your sequence stays a plain light.turn_on with brightness_step_pct: 5, no templates.

  • The same connection type works for any other integration that exposes remotes as event entities (Hue, Zigbee2MQTT with HA discovery, …), so new blueprints for those are easy to add.

Matter blueprints
Matter blueprints624×1084 61.2 KB

v4 – the frontend rewrite (the reason it keeps working with new HA releases)

The old panel was a 5 MB bundle with frozen copies of Home Assistant’s editor components, which broke with every other HA release (the “Option” dropdown and the target pickers in the action editor were the usual victims). v4 replaced that with a small TypeScript panel that uses Home Assistant’s own runtime components – the action editor is literally HA’s native Add action dialog, so it always matches your installed HA version.

Switch editor
Switch editor1311×1400 96.7 KB

Add action
Add action1400×1262 124 KB

Other things since v3.0.9:

  • Blueprint picker with a protocol filter (mqtt / zha / zwave / deconz / matter / …)

  • Switches heal automatically when a blueprint update only adds buttons or actions; the “Fix” button for real mismatches now actually repairs the switch

  • MQTT auto discovery for devices whose name contains a slash, stored variables shown in the variables dialog, hold actions on classic Homematic switches, Lutron Aurora after the Z2M transition change, setup no longer fails when the panel is already registered, and a pile of HA 2026.x compatibility fixes

  • Blueprint library: 190+ devices – new since the last post e.g. Aqara H2 EU (hold / double press), Aqara TH-S04D and more Aqara mini switches, Sunricher SR-ZG9002KR12-Pro 12-button knob and SR-ZGP2801K4-DIM, Innr RC-250, Zemismart ZMR4, Smarthjemmet QUAD-ZIG-SW, Shelly 1 Mini Gen3, Hue Wall Switch Module with hold (released)

  • README rewritten with docs for blueprints, event entities, troubleshooting – and a video from Smart-Live (German) that takes a look at the fork: https://www.youtube.com/watch?v=M_hLZacsjP4

Installation via HACS

  1. HACS → Custom repositories → add https://github.com/macpit/Home-Assistant-Switch-Manager → Category: Integration

  2. Install, restart HA, open the Switch Manager panel

Coming from the original repo? Your switch configs in .storage/switch_manager are preserved – swap the integration and restart.

Release notes: Release v5.0.0 — Matter support · macpit/Home-Assistant-Switch-Manager · GitHub

GitHub: GitHub - macpit/Home-Assistant-Switch-Manager: Switch manager is a centralised component to handle button pushes for your wireless switches. This includes anything passed through the event bus. The component relies on switch blueprints which is easily made to allow GUI configuration of your switches and their button pushes. This helps remove clutter from the automations. · GitHub

Contributions are very welcome – especially blueprints for Matter remotes you own (the event types are easy to read off the event.* entity in developer tools) and for anything else not yet covered. Open an issue or send a PR. And if Switch Manager is useful to you, a :star: on GitHub helps others find it.

Greets, Marc

5 Likes
2

Thank you for maintaining and continuing to improve Switch Manager! It’s great to see Matter support added, especially the support for event entities and more flexible button actions.

We’re from Zemismart, and we noticed that Zemismart ZMR4 is already included in your Blueprint library. We really appreciate the work you’ve put into supporting our devices.

We’d also be happy to provide you with some of our Matter devices for testing if you’re interested. If there are any Zemismart Matter remotes, switches, or other devices that you’d like to add support for, please let us know. We’d be glad to help with device information or arrange samples for testing.

Thanks again for your contribution to the Home Assistant community!

3 Likes
3

@macpit Are Tapo smart buttons included? That would be very helpful!
@zemismart Oh, finally some company that cares about Home Assistant

4

Thanks for the great feedback, both!

@zemismart That’s a fantastic offer — thank you! I’ll send you a DM so we can sort out the details. Short version: I’d love to. So far every device in the blueprint library came from users contributing via PR — having a manufacturer on board lifts this to a whole new level.

@jan-tdy Not bundled yet — but good news: since v5.0.0 the integration supports any device that exposes event entities in Home Assistant, and the Tapo buttons (e.g. S200B via the H100 hub / tplink integration) do exactly that. So chances are it already works via the new event-entity connection type. If you share the events your button fires (Developer Tools → States → the event entity), I’m happy to add an official blueprint so it works out of the box for everyone.

Small update: v5.0.1 is out — new blueprint for the LinknLink eMotion Air Plus (thanks @jakob42!).

What’s next: after letting the Matter release settle, the next big thing will be a GUI release: custom icons/thumbnails, UX improvements, and a visual blueprint editor with built-in sharing — create a blueprint in the UI and submit it back to the project with one click. Switch Manager lives from shared blueprints; most of you shouldn’t ever need to write YAML for your remote. No ETA yet — tracked in issue #5.

Greets, Marc

5

@macpit
I am asking because, as I know, Tapo buttons do not expose their events.
See the TP-Link integration docs.

6

@jan-tdy You’re right — I checked, and I have to correct myself: the official tplink integration docs state the hub-attached S200B/S200D buttons don’t report presses yet. The H100 hub doesn’t push button events; it only writes them to internal trigger logs, and the upstream library (python-kasa) doesn’t surface them yet — there’s an open issue/PR for it. There’s a custom integration (tapo-button) that polls those logs and fires events with a few seconds of delay, which Switch Manager’s new event connection could consume — but honestly, a laggy button is a frustrating button. The good news: once the upstream fix lands and tplink exposes the presses as event entities, it will work with Switch Manager automatically via the generic event-entity support from v5.0.0 — and I’ll add an official blueprint then. I’ll keep an eye on it.

7
  1. Will try using home-assistant-tapo-p100
  2. I am starting to suspect your responses are AI-generated
  3. I am not sure if the upstream fix ever lands; the same for robot vacuums (I am now using mine fork(jan-tdy/TapoVac-ADV) of a community integration)
  4. Currently using Tapo automations, it is very laggy, so 5seconds would be BETTER for me :rofl:
8

@jan-tdy Yes, I use AI — also for Switch Manager, that’s public on GitHub, nothing hidden. This is a hobby project, and without AI Switch Manager wouldn’t be where it is today. I’m an engineer and use these tools like anyone else does.

On point 4: if a few seconds of delay beats your current setup, the tapo-button integration + Switch Manager’s event connection should already work for you today — let me know how it goes.

Marc

9

No problem with AI; I use it too, but the unfiltered good news: once the upstream fix lands and tplink exposes the presses as event entities, it will work with Switch Manager automatically via the generic event-entity support from v5.0.0 — and I’ll add an official blueprint then. I’ll keep an eye on it. In every message (including the AI’s You’re right —) is too much…

And with the Tapo button integration:
I do not like it… And it is polling every second.
So I will keep using the Tapo app for the buttons. Goodbye, strange solutions…

1 Like