Matter Hub simple setup to link Google Home, Alexa and Siri to Home Assistant

I just want to create a new post to highlight the brilliant work of @t0bst4r for creating the Home-Assistant-Matter-Hub addon. I’ve searched the forum and there is very little discussion on what I think is an amazing concept .

Home-Assistant-Matter-Hub allows almost any home assistant entity to be made available to any Matter-compatible controller like Alexa, Apple Home or Google Home. No messing about with complex cloud configuration, All interaction is local and lightning fast. No lag changes update immediately, no matter where the changes took place.

I was going to outline the setup and configuration , but there is an excellent setup guide here.

Google Home for me is now completely stable, no dropouts , no delay. So much better than interacting with the cloud. It is a night and day improvement.

Setup of Home-Assistant-Matter-Hub was a simple install of an addin and exposing which entities to add to the hub. There are still rough edges and not all domains are available. As a concept it’s genius.

Why is a Matter hub not a core component of home assistant. This exemplifies everything which Home assistant stands for: local control, no cloud, no outside control.

4 Likes

Because matter is still experimental. There are also quirks with onboarding devices and some say that you don’t have full control of the devices you adopt doe to needing internet access to adopt and the manufacturer having the ability to brick devices if they want.

Idk how true that last bit is, but regardless, matter is marked as experimental within Hass.

Your not adopting devices but making your home assistant existing devices availiable to any local matter controller on your network say a Google Home hub, Alexa Echo , apple TV, LG TV

It saves having to link home assistant to the cloud and keep everything local

Thanks to @t0bst4r for the work done. I managed to add the lights and switches in the Home app and Google Home.
Maybe in a future update we will be able to select only certain devices from a domain. Now when I select lights as domain, it integrates everything it finds lights. The same with switches.

edit: It also works very well with Alexa on port 5540 only.

After trial and error I now have a single option.

{
  "filter": {
    "include": [
      {
        "type": "label",
        "value": "matter"
      }
    ],
    "exclude": []
  }
}

I have created the label “matter” in Home Assistant and added it to all the entities I want added. Once updated restart the addon. This ensures only entities maked matter are used.

Hope this helps :slight_smile:

4 Likes

Wow!!! thank you very much for the advice :slight_smile:

Hi! How to use scenes with this addon? With Emulated Hue in Alexa, the command was given saying - activate “scene name”. I was using the tuya scenes with IR controls for the tv. Now a scene is actually a button switched to On by default. Thanks in advance for the answers.

Scenes are supported as on and off switches

Hi,

first of all: great job t0bst4r. This is amazing.

I have a problem getting scenes to work: The scenes show up but seem not to get triggered by HA.

  • the respective scenes can be triggered from HA directly (scene.turn_on) without issues
  • Scenes got correctly recognized (included via a dedicated new label - which worked great, thank you lonebaggie for the idea) and added as OnOffPluginUnits
  • Added them and also other entities to Alexa via App successfully
  • Can trigger them via Alexa (me: “Turn on Scene ABC” - Alexa: “Ok”)
  • Log for add-on shows activity e.g.:
    [ 2024-11-21T12:42:00.727Z ] [ INFO ] [ matter.js / Behavior ]: Invoke xxxxxxxxxxxxxxxxxxxxxxxxx.aggregator.scene_breakfast.onOff.on online#xxxxxxxxxxxxxxxxxxxxxxxxx (no payload)
  • scene does not get turned on though
  • my lights trigger directly.

Remark: I recognized in the add-on frontend that all my scenes show as “on” all the time. On the UI I cannot see them swithing status.

Anybody got scenes working with this add-on?

Have to admit read that it’s deprecated but still went with the matter bridge and not the Home-Assistant-Matter-Hub as the first one started without an issue and the latter one crashed on me.
So with the bridge went into the google home and added the qr code. After that google popped up to grant permissions and after that “you need a hub for matter to set up and control with google home”. Am i missing something?

hi, thank’s to t0bs4r !
I used matterbridge so… i need to test and use this nice upgrade !

but…
“The command ‘/bin/ash -o pipefail -c npm install -g home-assistant-matter-hub@$package_version’ returned a non-zero code: 1”

install failed on HA (proxmox VM).
and… for a docker install… to me ( as a beginner) it’s rough as forbidden ^^

if you need other data, just tell me ( i know it’s an alpha version !)

Hi!
I couldn’t get scenes to work either but scripts do work perfectly. So I set up scripts that just activate the scenes, and only share the scripts, thanks to @lonebaggie’s ‘matter’ label.

1 Like

Works great on homeassistant sofar. Wonder if there will be a proxmox lxc version too?

thanks voslin great idea, will follow that recommendation

Just saw the release notes on 3.0.0-alpha.43 (2024-11-28)

:adhesive_bandage: Fixes

  • scene: default to off state to be able to turn it on (1af9513)

:grinning:

1 Like

It works really good, and fast too. Only thing I really can’t get to work is the climate. Google Home constantly says, this device needs to be configured in the assistant.

Indeed it works now! (3.0.0-alpha.47)

Cannot get a virtual switch (programmed in config.yaml) to work with Alexa….specifically it won’t turn off the virtual switches. Does anybody else have virtual switches working?

next time, follow a good guide,

This bug needs to update proxmox, :wink:

Why am I getting error like this?