Thanks. It did eventually work for me but I needed to reset the commissioning in the matterbridge UI first. Before doing that, Alexa just kept saying searching until it timed out.
1 Like
Thanks @t0bst4r
- Iām using the most recent version 1.5.2-72.
- Lights that support both color and temperature work fine through matter to Alexa. Matter Bridge exposes OnOff, Hue, Saturation, Level clusters
- Lights that only support temperature (not RGB) do not show any temperature control on Alexa. Matter Bridge exposes OnOff, levels clusters. If I add the same light through Nabu Casa integration Temperature is shown in Alexa.
- On HA side these lights are using Z2M. Some lights are Tuya Zigbee, others are Aqara
Yes, I know that. I made the mistake to assume that color is a prerequisite for temperature. Which is wrong obviously. 
I added this to the todo list:
1 Like
Thanks @t0bst4r for all the great work.
Do you know if itās possible to change the device type of dimmable lights and switches?
Currently all lights and groups are exposed as MA-onofflight (0x0100) as Device type in Matterbridge (at least for me). Would it be possible to expose lights as Dimmable Light (0x0101), Color Temperature Light (0x010C) or Extended Color Light (0x010D)?
The reason Iām asking is that Iām trying to use this with my flic twist and for the twist functionality (for example changing the brightness) to work its needs to see a dimmable light to bridged as one of the aforementioned device types
WOW ! Excellent work !
I have started to use this as a docker container and I can see my devices (even disabled ones) in Google Home now ! Just need to figure out how to use Matter devices from the new Switchbot Universal remote and it will be great !
Looking at the logs of the container, I could see:
docker-matter-bridge-1 | 2024-07-05 17:24:09.956 INFO UdpMulticastServer wireguard: send Unknown system error -126 224.0.0.251:5353
docker-matter-bridge-1 | 2024-07-05 17:24:09.956 INFO UdpMulticastServer wireguard: send Unknown system error -126 224.0.0.251:5353
docker-matter-bridge-1 | 2024-07-05 17:24:10.137 INFO UdpMulticastServer wireguard: send Unknown system error -126 224.0.0.251:5353
docker-matter-bridge-1 | 2024-07-05 17:24:10.191 INFO UdpMulticastServer wireguard: send Unknown system error -126 224.0.0.251:5353
Any idea why a VPN solution is mentioned ? It is a bit scary
1 Like
Is there any way to run two instances of the HA matterbridge addon in one instance of HA OS?
I have a guest house whose devices are all on the same HA controller as the main house, but I want Google to think of those devices as being in a separate house so that guests canāt control the main house. From what Iāve seen, Google treats devices behind a matter bridge as if theyāre all one device. You canāt individually remove them from a home or between homes in Google Home.
So, the only solution I can see is to run two parallel instances of matterbridge with different configs for each structure. Thoughts?
Maybe Iām blind, but can someone tell me where I can find the QR Code after first setup? There is no QR Code anymore in log even after a restart of the add-on.
@Rudeen this should be fixed since version 2.1 or so 
@Omnipius as of now you cannot install an addon twice. But at least the ports are configurable since 2.3. so if you find a way to deploy twice (e.g. with a custom docker deployment) you should be able to run it twice. Just be aware that some matter controllers (like Alexa) only support the default matter port (5540).
@EagleDev the QR code is only visible in the log if the matter bridge is not provisioned yet. You can still see it using the web ui, but it could happen that it cannot be paired twice like that. Therefore youād need to factory reset using the Web UI.
To pair it with multiple controllers, youād need to pair the second using the first controller.
2 Likes
Thanks for your work!
I have suffered from the instability (probably due to DuckDNS) when using Google Assistant integration for a very long time.
This add-on works perfectly. I could see the response time is reduced a lot and no more āOfflineā state.
The only minor issue is the supported Matter device types are still limited.
I have a binary sensor with device class garage_door but Google Home shows as a normal sensor instead of a garage door.
The add-on seems already pick the most appropriate one: MA-contactsensor (0x0015).
2 Likes
Yes, every device type needs to implemented one by one. There is noone else adding new features. So I am doing this on my own in my spare time, beside work and family.
Iāll proceed adding new device types, but forgive me if it takes longer. 
Regarding the sensor types:
Contact sensors arenāt always garage doors. Iād assume thatās why Google Home shows it as a ānormalā sensor without a specific type - Google doesnāt know if its related to a garage door, a window, or your fridge.
2 Likes
Hi,
Iām just trying this out, looks very promising as a way to get rid of the Google assistant integration. Great work!
Iām running the latest of everything but I have a problem that my dimmable lights only show up as on off lights (but with temp control) and from the bridge ui I see the type is āMA-colortemperaturelightā. Not sure if Iām missing something that is configurable to get it working?
Ok, thank you
Follow up on my own question, seems to be the level = 255% is not working.
Here is when I turn lights to 100% in home assistant:
If I lower to 99% it workings on Google home and says 99%, but 252% in the bridge ui:
Then if I increase to 100% in Google home it shows up as 254% in bridge ui:
okay. First of all, itās not percentage - obviously. 
Itās a value between 0 and 255. Thatās a visualization bug in matterbridge. Anywayā¦ matter does not accept a value of 255. 254 is the maximum allowed value. I thought Iāve considered that everywhere. But maybe I forgot one edge case. Iāll have a look at that tomorrow.
Haha yeah I figured that, just wanted to point out which value I was talking about
Sounds great!
Iām a great fan! Thanks to Matterbridge I can use my flic buttons in home assistant. I read about factory resetting Matterbridge in order to commission it with for instance Google home as well. Is this possible for me without loosing all entities etc I already have working in home assistant? Or theyāre not affected after being commissioned? I canāt see any qr code in the web gui. Should I instead factory reset it and pair it with Google home first, and later pair the Flic hub to Google home? Sorry if itās confusing.
I havenāt tried it but it should be possible, you just need to share each device: Matter (BETA) - Home Assistant
Iād like to see temperature sensors available via the matter bridge. Is this an entity that is not yet supported or is there a domain I can allow for it to work? (My goal is to be able to ask Alexa what the temperature is in the family room, for example)
I am a developer and could potentially add it myself, but Iām not familiar with the matter protocol at all. What would I need to know to add to this project?
The add-on seems unable to start again after reboot:
Error 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: Matterbridge
Populate your Home Assistant instance as Matter Bridge.
-----------------------------------------------------------
Add-on version: 2.7.1-119
You are running the latest version of this add-on.
System: Home Assistant OS 12.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.8.0
Home Assistant Supervisor: 2024.08.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
#############################
CURRENT CONFIGURATION:
{
"homeAssistant": {
"url": "http://supervisor/core",
"accessToken": "...",
"matcher": {
"includeDomains": [],
"excludeDomains": [],
"includePatterns": [
...
],
"excludePatterns": [],
"includeLabels": [],
"excludeLabels": [],
"includePlatforms": [],
"excludePlatforms": []
}
},
"overrides": {
"domains": {},
"entities": {}
}
}
#############################
[21:10:17.956] [PluginManager] Plugin matterbridge-home-assistant has no type
[21:10:18.086] [Matterbridge] Created Matterbridge Plugin Directory: /root/Matterbridge
CLI: Matterbridge.loadInstance() failed with error: Error: [node-persist][readFile] /root/.matterbridge/storage/.matterbridge/<some_long_string> does not look like a valid storage file!
[21:10:25.302] [PluginManager] Plugin matterbridge-home-assistant has no type
CLI: Matterbridge.loadInstance() failed with error: Error: [node-persist][readFile] /root/.matterbridge/storage/.matterbridge/<some_long_string> does not look like a valid storage file!
I deleted the empty file /addon_configs/*_matterbridge/storage/.matterbridge/<some_long_string> and it works again.