Matterbridge by luligu

Hi everyone :wave:

I wanted to highlight a really powerful setup using Matterbridge together with its Home Assistant plugin — it’s one of the cleanest ways to expose Home Assistant entities to Matter ecosystems in a controlled and organized way.

For anyone not familiar, Matterbridge is a Matter plugin manager that allows you to bridge non-Matter devices into platforms like Amazon Echo (Alexa), Google Home, SmartThings, and other Matter-compatible systems — all locally and with great flexibility.


:wrench: What makes this setup stand out

With the Home Assistant plugin, you can control exactly what gets exposed:

  • Filter devices/entities by Area (rooms)
  • Filter by Label
  • Select specific entities by name / entity_id
  • Use include / exclude logic

This means no more dumping everything into your Matter ecosystem — you can keep things clean, organized, and intentional across all platforms.


:brain: Why it’s worth trying

  • Clean and clutter-free device sync across ecosystems
  • Full control over what gets exposed
  • Works locally (no heavy cloud reliance)
  • Great for multi-platform setups
  • Scales well even with large numbers of devices

:gear: Simple setup (Home Assistant OS)

For Home Assistant OS users, setup is very straightforward:

  1. Add the Matterbridge Home Assistant Add-on repository:
    https://github.com/Luligu/matterbridge-home-assistant-addon
  2. Install the Matterbridge add-on from the Add-on Store
  3. Start the add-on and open its Web UI
  4. Add and configure the Home Assistant plugin
    (connect via WebSocket — details here):
    matterbridge-home-assistant-addon/DOCS.md at e7a513db31497f68c16a4e878fc09d444e938429 · Luligu/matterbridge-home-assistant-addon · GitHub
  5. Configure your filters:
  • Areas
  • Labels
  • Entity names
  1. Pair Matterbridge with your preferred Matter platforms (Alexa, Google Home, SmartThings, etc.)

:bulb: Example use cases

  • Expose only “Living Room” devices to all Matter platforms
  • Share only lights or switches using labels
  • Keep internal or advanced entities hidden inside Home Assistant
  • Build a minimal, voice-friendly device set across multiple ecosystems
1 Like