Hi
I have no Matter device but alot of Zigbee and WiFi devices.
I have install Home-Assistant-Matter-Hub becurse I want to connect Home Assistant to Google Home and then use Google Assistent to control some of my devices.
The problem is that I can see the devices in Google Home but I can’t do anything.
/UPDATE
Forgot to tell that I running
Home Assistant Core 2024.10.4 (Going to upgrade to 2024.12.1 tomorrow)
Home Assistant OS 13.2 (Going to upgrade to 14.0 tomorrow)
I dont want to be that guy who says “its not working” - but - its not working - with Alexa.
I have installed and the add on is running. I can see a QR code and pairing code - no errors in the log.
I go to my phone, Alexa app and add device - matter - scan the QR code and nothing.
Im not really sure where to start or what infro to provide for anyone to help?
Have you setup any filters to add entities into the matter hub ?
I have the same problem. I use port 5540 and have added around 93 device in the bridge. In the alexa app I have selected add hub - matter and scanned the qr code. But nothing happens. IPv6 is activated in the network.
pretty sure the matterbridge is the old version of the matter-hub
Hi guys, after installing the addon and scan the QR Code this message appears. Why? Isn’t the addon supposed to simulate a matter hub?
I have the same issue. I have a google home mini speaker at home, but I get also the message after scanning the QR code with the google home app. Maybe only the newer Nest Mini speakers can act as Matter Hub?
Hey,
first of all, a big shout out to t0bst4r for providing this great addon!
I would like to control my HA Stuff with Alexa. But i have the same problem like some of the users here in the thread.
I can see the QR-Code but when i scan it with the Alexa nothing happens. It does not find the bridge. I restarted the echo dot. I restarted and reinstalled the addon. nothing works.
is there any thing i can do to get i working?
Greets!
Flex
I Solved my Problem!
My echo dot had a low connection to the wifi… (idk why)… restarted it twice and also restarted it via amazon cloud…and boom wifi connection is awesome now and it did the pairing process succesfully!
it works super fast and is awesome to use!
Thanks again to the developer! 
I was wondering the same thing.
It seems very active (last release yesterday), so it’s certainly not eol.
Has anyone compared the two? Why are there two at all?
the only thing i’ve seen is a comment on reddit that said:
Last I saw the luligu one only had a plugin for zigbee entities where the t0bst4r one was aiming to expose all entities.
Not much other info out there. I installed both to test them out. It seems that matterbridge is more plugin driven, meaning you can add other devices like zigbee2mqtt, etc, making it more flexible if you want to support multiple things. But, it is also not nearly as flexible as home-assistant-matter-hub in the inclusion and exclusion of devices where i can include or exclude entities in home-assistant-matter-hub using entity_id, domains, labels, etc. making it a breeze, in matterbridge, you need to list each entity individually (a bit of a pain).
While the Mini has matter now, I don’t believe it can actually act as a matter hub. It also lacks the Thread border router built-in like the 2nd Gen Home has. Seems like an afterthought on the Mini.
Why would this affect pairing?
EDIT: curios about this - I also powered off my Alexa and back on and - I am not sure if this was the catalyst but my hub was also discovered and is now working
I’ve tried to get matter-hub working with google home. I did a very basic test matter config with just a single light entity.
I can see the light change state in the matter-hub browser and I can scan the qr code and see everything get setup in the logs, but then in google home on my phone it only ever says “offline” when I click through the “test” and into the entity.
Really no idea where to start with this? I see other people have it working so I think it must be something w/ my ipv6 in docker though I can’t see anything obviously wrong. I can from the command line access the container w/ the ipv6 address and I see the ipv6 udp debug messages during setup.
It ultimately gets commissioned successfully, i see the entity update state in the browswer but google home always shows it offline after a LONG pause before it gets to that conclusion.
two things I see suspect this in the log:
[ 2024-12-15T05:26:24.367Z ] [ DEBUG ] [ Matter / MdnsScanner ]: Adding operational device 8655D494A4D273FD-000000005C300D18._matter._tcp.local in cache (interface ens32, ttl=120) with TXT data: SII: 500 SAI: 300 SAT: 4000 T: 0 DT: undefined PH: undefined ICD: 0 VP: undefined DN: undefined RI: undefined PI: undefined
And this shows up sometimes on the browser but not sure what it means – but when it does the entity is gone:
Unexpected token 'N', "Not Found" is not valid JSON
Any tips on where to start debugging?
I’m up and running with Alexa after the power cycle suggested (still not sure if this was the root solution but I’ll take it)
I now have another odd issue - adding the light domain shows all lights in the web ui. I then created a label and applied to a couple of switches but not seeing anything even with a restart.
If I add a pattern include this works straight away. This is using the haos add in - perhaps a bug?
Can report this is working stable with Alexa, HAOS and installing it as an addon for me.
I use this so far to control lights, trigger scenes and a script triggering a robot vacuum. Lights work also fine replicating state… “Alexa, tell me - is light XYZ on?” → “Yes / no”…
With the initial installation I needed to regenerate the Bridge and QR Code one time (do not remember exactly but I think I used the factory reset button) as the pairing intially failed.
Overall this add-on saves me some hazzles as I used nodered before to expose HA devices to my echos and that setup was regularily requiring maintenance.
It is not working here as well. Alexa cannot connect, it does not find the hub. After writing the first sentence, the 10th or so try worked. What I did: In Alexa app, on the bottom go to “more” (Mehr), swype right and select “Search” (Suche) on the right pane. I was asked to allow rights for “devices near me” (Geräte in der Nähe) (Edit: or maybe it was “Location allowance” (Standortberechtigung)). I did so by disabling the toggle button which was active for “remove allowance for unused app” (Berechtigung für ungenutzte App entfernen). Afterwards I could see the search request in the Matter Hub logging. I needed two or three more runs to also successfully get all items listed, but I assume I was just too impatient.
(Added german wording because I guessed the englisch settings)
Why are my thermostats not working in Alexa anymore? Before v55 they were working. In Matter Hub Alexa, I see the temperature and humidity, but in Alexa I see that the device is unresponsive.
edit: I renamed the thermostats and then refreshed the addon. Now it works very well in Alexa.