Introducing the (unofficial) Matter Bridge.
Extending the functionality of the matter plugin from acting as a controller for Matter devices we can now publish all your indigo devices out over Matter. (Subject to Matter’s device definitions).
Why? If you are happy with Apple and HA and Alexa bridges you don’t need this. But as it becomes more of a future standard it’s something I think the platform will benefit from. I’m also trying to simplify my setup by removing HA and Home Bridge and this lets me just have a single setup for publishing devices to both Apple and Alexa in one go.
Why not? Matter doesn’t support every device that Indigo does (or even Apple Home) so they won’t work. matter.js as an implementation of Matter doesn’t have support for every role. Some gaps exist there on the bridge side.
Some gaps are just down to me not having built them, or had devices to test with.
The gaps are tracked in indigo issues with details and help is appreciated on these gaps.
There are comprehensive docs on GitHub with some different from normal formatting
https://simons-plugins.github.io/indigo-matter/
But in short.
1. Plugin menu > Install matter bridge npm package
2. Plugin menu > Add devices
3. Plugin menu > generate pairing code
4. Apple Home/ Alexa/ HA etc. add matter hub with code from (3).
Repeat 3 and 4 for how many other systems you want to add devices to.
This is beta, so don’t jump in with everything in one go. It’s rested and I believe the function is good. There is backup of the fabric you can use but a small possibility setup could be wiped in a further release. Worst case is just needs the devices adding again and re-pairing to the other systems. I’m not expecting this anymore.
Let me know what you think and any feedback or issues.
*unofficial as this is not certified by the Matter standards organisation. It does use the standard matter.js library that matter-bridge and other home automation systems use. Home Assistant is certified as it went through the test process.
But this is thoroughly tested and uses test devices per matter docs for running all tests, see the docs for test details.
Matter bridge
Re: Matter bridge
I have spent a long time in the last week on this bridge (alongside time hardening the coordinator) and I think I am close to a release that should take this out of beta.
If anyone is keen to help test across either Apple Home or Alexa (anyone who had issues with it recently? ) or even another system and can try out a range of device types and is happy reporting issues back into GitHub please let me know.
Thanks
Simon.
If anyone is keen to help test across either Apple Home or Alexa (anyone who had issues with it recently? ) or even another system and can try out a range of device types and is happy reporting issues back into GitHub please let me know.
Thanks
Simon.
Re: Matter bridge
2026.26.0 is now out in the plugin store.
This takes it out of beta and , along with a lot of hardening of behaviour around deleting devices and ensuring devices dont end up in decoupled states in Apple Home or Alexa etc, introduces some new functionality to allow you to migrate a Matter device, ie a switch in Apple Home to a new Indigo device, if you are replacing hardware or changing a zigbee socket to a wave etc. without having to lose the setup in Apple.
Other than some tidy of menus and small bug fixes and supporting some more niche products the most major pending feature is to enable multiple bridges.
This takes it out of beta and , along with a lot of hardening of behaviour around deleting devices and ensuring devices dont end up in decoupled states in Apple Home or Alexa etc, introduces some new functionality to allow you to migrate a Matter device, ie a switch in Apple Home to a new Indigo device, if you are replacing hardware or changing a zigbee socket to a wave etc. without having to lose the setup in Apple.
Other than some tidy of menus and small bug fixes and supporting some more niche products the most major pending feature is to enable multiple bridges.
Re: Matter bridge
I've now migrated 50 devices to the Matter bridge to have them both in Apple and Alexa. A few polarity quirks worked out on sensors and all working well.
I have lights, motion sensors, contact sensors, leak sensors, smoke alarms, thermostats and more working.
I have lights, motion sensors, contact sensors, leak sensors, smoke alarms, thermostats and more working.
Re: Matter bridge
An update on compatibility with other systems.
Alexa is proving very flakey.
It connects and subscribes to the matter bridge very differently to both Apple Home and Home Assistant and even on small number of devices it’s unreliable.
On 56 it can control devices but doesn’t maintain a subscription to know current state. Likely would work on voice and might be better more modern Echos but not on mine.
Home Assistant however is just like Apple Home. Joins and subscribes instantly and has very fast updates.
Alexa is proving very flakey.
It connects and subscribes to the matter bridge very differently to both Apple Home and Home Assistant and even on small number of devices it’s unreliable.
On 56 it can control devices but doesn’t maintain a subscription to know current state. Likely would work on voice and might be better more modern Echos but not on mine.
Home Assistant however is just like Apple Home. Joins and subscribes instantly and has very fast updates.
Re: Matter bridge
Correction I’ve narrowed this down to devices that Alexa doesn’t support. So having a leak sensor in your bridge works fine in Apple but doesn’t in Alexa and worse it makes Alexa stop reading the entire bridge rather than just skip that one device.
So if you need Alexa don’t include leak, and possibly smoke /CO sensors and you are good.
I have 60 devices running well now.
So if you need Alexa don’t include leak, and possibly smoke /CO sensors and you are good.
I have 60 devices running well now.
Re: Matter bridge
After more hours than I care to admit (please dont tell my wife) testing this I have fixed the Alexa bridge issues.
Motion sensors now work - Fable tells me this is the first Matter bridge to make this work with Alexa.. took a lot of digging into the spec and testing across real devices and Apple / test bridges but Alexa now shows motion.
Leak sensors - The UI will warn you on pairing a leak sensor to pair as contact if you use your bridge on Alexa and the fix is to set as contact sensors. I believe others including HA have this fix in place too.
Smoke and CO sensors - They work, or at least dont break anything. I havent triggered either to test.
Motion sensors now work - Fable tells me this is the first Matter bridge to make this work with Alexa.. took a lot of digging into the spec and testing across real devices and Apple / test bridges but Alexa now shows motion.
Leak sensors - The UI will warn you on pairing a leak sensor to pair as contact if you use your bridge on Alexa and the fix is to set as contact sensors. I believe others including HA have this fix in place too.
Smoke and CO sensors - They work, or at least dont break anything. I havent triggered either to test.
Re: Matter bridge
Matter plugin
what’s new, v2026.25.0 → v2026.28.0
(bridge node updates install automatically)
A lot of changes to harden the
Bridge health monitoring
• New “Matter Bridge Health” device — the bridge’s own status as an Indigo device you can trigger on (healthy / churning / recovery).
• Alexa subscription-churn detection: the bridge spots the Echo pattern where subscriptions collapse and rebuild in a loop, and reports it in the Event Log instead of leaving stale tiles as the only symptom.
• Per-fabric health (fabric1Name/Health … fabric5Health): with several ecosystems paired, see which one is having trouble — named by vendor (“Apple Home”, “Amazon Alexa”, …), so triggers can target the right one.
• Automatic session hygiene (new): when a controller opens a fresh secure session, its stale older ones are closed on the spot, and long-quiet unused sessions are tidied. This removes the pile-up condition behind “Alexa silently stops updating” — where updates were delivered and acknowledged on an old session the Echo was no longer listening to. Per-controller session counts and cleanup totals appear in the bridge’s diagnostics, and if the monitoring itself ever breaks, the Event Log says so — silence never means “all clear”.
Colour-temperature lights: honest ranges
• Exported CT and extended-colour lights can now publish their real warm/cool limits to Apple Home/Alexa instead of the generic 2000–6500 K — so controllers stop asking bulbs for colours they can’t reach (the cause of Apple Adaptive Lighting re-sending the same command every few seconds, forever, to warm-limited bulbs).
• The range is learned from the hardware: the plugin watches what a bulb actually answers and adopts only proven limits; a wrong range self-corrects in both directions. No configuration needed.
• New “Calibrate Colour-Temperature Bounds” action — sweeps your CT lights to both extremes and publishes each bulb’s measured limits immediately. Off lamps stay off; lit lamps are skipped by default. Scriptable/schedulable.
• Optional Warmest/Coolest white (K) fields in Manage Matter Exports to seed a range by hand; the learner still refines it from evidence.
• Existing accessories pick up their measured ranges live — no re-pairing needed.
Bug fixes
• A colour-temperature change on a lit lamp no longer dims or switches it off (writes now carry the lamp’s live brightness).
• Fixed the Adaptive Lighting loop against warm-limited bulbs (clamped echo vs controller request, re-asserted every ~3 s).
• A plain Indigo relay (e.g. Virtual On/Off Device) exported as a door lock now actually locks/unlocks from Home/Alexa — taps used to revert.
• Re-adopting an orphaned accessory onto a device previously exported under a different role no longer fails; options that don’t apply to the new role are dropped and named in the log.
• General hardening: export settings validated at save time, diagnostics counters only count what actually happened.
Heads-up
• Exporting water-leak / freeze / rain sensors while an Echo is paired can break Alexa’s Matter updates entirely (Alexa can’t model that device family) — the export dialog now warns before you do it.
what’s new, v2026.25.0 → v2026.28.0
(bridge node updates install automatically)
A lot of changes to harden the
Bridge health monitoring
• New “Matter Bridge Health” device — the bridge’s own status as an Indigo device you can trigger on (healthy / churning / recovery).
• Alexa subscription-churn detection: the bridge spots the Echo pattern where subscriptions collapse and rebuild in a loop, and reports it in the Event Log instead of leaving stale tiles as the only symptom.
• Per-fabric health (fabric1Name/Health … fabric5Health): with several ecosystems paired, see which one is having trouble — named by vendor (“Apple Home”, “Amazon Alexa”, …), so triggers can target the right one.
• Automatic session hygiene (new): when a controller opens a fresh secure session, its stale older ones are closed on the spot, and long-quiet unused sessions are tidied. This removes the pile-up condition behind “Alexa silently stops updating” — where updates were delivered and acknowledged on an old session the Echo was no longer listening to. Per-controller session counts and cleanup totals appear in the bridge’s diagnostics, and if the monitoring itself ever breaks, the Event Log says so — silence never means “all clear”.
Colour-temperature lights: honest ranges
• Exported CT and extended-colour lights can now publish their real warm/cool limits to Apple Home/Alexa instead of the generic 2000–6500 K — so controllers stop asking bulbs for colours they can’t reach (the cause of Apple Adaptive Lighting re-sending the same command every few seconds, forever, to warm-limited bulbs).
• The range is learned from the hardware: the plugin watches what a bulb actually answers and adopts only proven limits; a wrong range self-corrects in both directions. No configuration needed.
• New “Calibrate Colour-Temperature Bounds” action — sweeps your CT lights to both extremes and publishes each bulb’s measured limits immediately. Off lamps stay off; lit lamps are skipped by default. Scriptable/schedulable.
• Optional Warmest/Coolest white (K) fields in Manage Matter Exports to seed a range by hand; the learner still refines it from evidence.
• Existing accessories pick up their measured ranges live — no re-pairing needed.
Bug fixes
• A colour-temperature change on a lit lamp no longer dims or switches it off (writes now carry the lamp’s live brightness).
• Fixed the Adaptive Lighting loop against warm-limited bulbs (clamped echo vs controller request, re-asserted every ~3 s).
• A plain Indigo relay (e.g. Virtual On/Off Device) exported as a door lock now actually locks/unlocks from Home/Alexa — taps used to revert.
• Re-adopting an orphaned accessory onto a device previously exported under a different role no longer fails; options that don’t apply to the new role are dropped and named in the log.
• General hardening: export settings validated at save time, diagnostics counters only count what actually happened.
Heads-up
• Exporting water-leak / freeze / rain sensors while an Echo is paired can break Alexa’s Matter updates entirely (Alexa can’t model that device family) — the export dialog now warns before you do it.
Re: Matter bridge
2026.29.2
A lot of hardening and back end refactors in teh latest release but now deleting an indigo device will drop the published matter device too. If you want to repoint the matter device to a new indigo device, you can do this via the migrate matter device menu item before deleting the original.
A lot of hardening and back end refactors in teh latest release but now deleting an indigo device will drop the published matter device too. If you want to repoint the matter device to a new indigo device, you can do this via the migrate matter device menu item before deleting the original.