Try a different label name google might be used internally . You dont need to prefix or postscript label with *
1 Like
everything is gone ahh. I tried adding back one of the original inclusions (domain: switch) and even that didn’t make anything else show up. what have I done 
in the matter addon, the labels only work with ENTITIES, not devices or domains.
yes using it on entities!
I worked out the issue though, re-read the thread and saw a comment.
“BTW, like some here I was having trouble getting the bridge to see any device using a label, after trying everything I deleted and recreated the label and it worked beautiful. I think it may be the fact I changed the label name after creating it and that may have cause it to not work.”
which explains what the documentation says about proper bridge configurations.
“Even when renaming a label or area, the slug doesn’t change. Never.”
I had no idea what this meant initially but it makes sense now. I just renamed my label and based my inclusion on the new label name. but it doesn’t change in the background, the fix is to delete the label and create a new one. it’s now working!
1 Like
Glad to see that you got it sorted.
1 Like
My issue is a little more basic, I go to Matter Hub and select My Hub and I see no devices.
I was using Emulated Hue but Alexa has been doing strange things, I have a specific list and she gets a lot of other stuff not in the list and misses a lot in the list. Trying to troubleshoot that I found Home-Assistant-Matter-Hub and it sounded like the right thing to try next.
My Setup:
- Installation method Home Assistant OS
- Core 2025.9.4
- Supervisor 2025.09.0
- Operating System 16.2
- Frontend 20250903.5
My Hub:
- Name: My Hub
- Port: 5540
- Country Code: US
Include:
- Type: domain
- Value: Light
- Exclude: {}
I also tried adding a Label ‘Matter’ to the devices I wanted included then:
Include:
- Type: label
- Value: Matter
- Exclude: {}
Logs:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
Add-on: Home-Assistant-Matter-Hub
Publish your entities from Home Assistant to any Matter-compatible controller like Alexa, Apple Home or Google Home.
Add-on version: 3.0.0-alpha.87
You are running the latest version of this add-on.
System: Home Assistant OS 16.2 (amd64 / generic-x86-64)
Home Assistant Core: 2025.9.4
Home Assistant Supervisor: 2025.09.0
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2025-09-21 13:19:39.915 INFO WebApi HTTP server (API & Web App) listening on port 62344
2025-09-21 13:19:40.025 INFO HomeAssistantClient Waiting for Home Assistant to be up and running
2025-09-21 13:33:52.033 INFO ServerNodeStore Opened 1dde500dd5394d7fac46558879e98cae storage at /config/data/1dde500dd5394d7fac46558879e98cae
2025-09-21 13:33:52.835 INFO BaseEventStore Initialized new volatile event store
2025-09-21 13:33:52.910 INFO Endpoint 1dde500dd5394d7fac46558879e98cae ready endpoint#: 0 type: RootNode (0x16) behaviors: 
parts ✓index ✓basicInformation ✓accessControl ✓groupKeyManagement ✓generalCommissioning ✓administratorCommissioning ✓operationalCredentials ✓generalDiagnostics ✓commissioning ✓network productDescription subscription sessions ✓events controller ✓descriptor
2025-09-21 13:33:52.953 INFO Endpoint 1dde500dd5394d7fac46558879e98cae.aggregator ready endpoint#: 1 type: Aggregator (0xe) behaviors: parts ✓index ✓descriptor
2025-09-21 13:33:53.234 NOTICE Node 1dde500dd5394d7fac46558879e98cae going online
2025-09-21 13:33:53.400 NOTICE Node 1dde500dd5394d7fac46558879e98cae is online
2025-09-21 13:33:53.409 INFO AccessControlServer initializing ACL manager with ACL
Did you add the devices or the entities? Labels go on the entities.
Hello! with alpha version 88 the addon no longer starts. I went back to version 87
Ohhh noooo! t0bst4r has put a call out for help maintaining this super important project… hopefully we’re able to get someone to help fill the big shoes! It’d be a huge shame to see this project disappear… I personally think it’s important enough to make its way into HA natively!
More info here: ⚠️ Maintainer Wanted · t0bst4r/home-assistant-matter-hub · Discussion #825 · GitHub
1 Like
If this project is not continued, there is also the following actively developed alternative, which also has a HA add-on.
Luligu/matterbridge
Interesting… anyone tried it? He also has a plugin that “allows you to expose the Home Assistant devices and individual entities to Matter.”
Thank you, thank you, thank you!
Why is it not written anywhere that the add-on only enters pairing mode for a short time when it starts or restarts??
I have wasted a day or more trying to connect and simply restarting HA Matter Hub made it visible to Alexa and I’ve been able to connect.
So thanks Phil!
1 Like
I’m also VERY grateful for this info! I wondered about “pairing mode” and maybe restarting… but I didn’t try it and didn’t go back there, for whatever reason…
Probably with VM’s coming out my ears and one of them is my networks/wifi controller, so I went to check all my IPv6 stuff instead 
So thank you VERY much, for saving me a lot more wasted time 
If I try to add the depository I get the following error.
https://github.com/t0bst4r/home-assistant-addons is not a valid add-on repository
Is there a different URL I should be using?
I am using 3.0.3. I have one Hub set up to Matter and sharred out to Alexa. In the last week or so my lighting devices have stop responding but all my other devices thermostats, covers , and switches) are working fine. Is anyone else having this issue?
I’m still using version 3.0.0-alpha.76 which is working perfectly. Is there any reason for me to update to the latest 3.0.3 or, conversely, to not update?
I have a selection of Philips Hue Lights, Wiser Light Switches, Aqara Blind Controllers and an LG A/C unit exposed via the addon.
I’m aware of the ‘If it ain’t broke, don’t fix it’ mantra but am keen to understand the current state of play with the addon.
Also using an older version, because every time I upgraded past it, I lost around 10 devices.
At this point I’ve wasted days trying different ways of getting google home working with Home Assistant and am ready to give up.
I was hoping this approach would work, but while I was able to control devices using Google Home buttons, the Google Voice assistant would not work (it would report devices being offline).
EDIT: Found the problem. I never added Google Nest 2 to my google home. Once I did that everything started working.
I posted on the github for this - am I the only one that just gets a load of entities into goohle home called ‘Door’, Window’, ‘Switch’ etc - as in not where they are. I dont have my devices names so for example I have -
And I hence just get a load of switches etc - and no idea which is which in google home.
Am I supposed to go into every one and name them as below (I tested one and it comes in correct) -
Don’t hold your breath, sadly the project is over for now.
I’ll take rhis opportunity to thank t0bst4r for all his work, awesome job !
I’m jumping to GitHub - Luligu/matterbridge: Matterbridge plugin manager for Matter