Matter Help C8-Pro (Matter Over Wifi)

albertjmulder · January 8, 2026, 8:39pm

So I have a C8-Pro and trying to connect a Matter device to it, but it never connects. "Looks like you’re having trouble pairing your device."

This is a matter over Wifi device. I seen in the wiki that it has to go through an alexa or google or somethign else first. Why? What is the point of having yet another hub? When HE says it supports matter I would expect it to support matter not got through another device first and then it would send it to the hubitat. to me that is not supporting matter devices, that is supporting matter devices from another hub. Why does hubitat not properly support matter?

Or am I completely wrong.

ogiewon · January 8, 2026, 8:52pm

When Hubitat released its original Matter support, it did require the use of another system like Apple Home, Amazon Alexa, or Google Home to perform the initial Matter Commissioning process for a new device. Then, from that system, one could generate a sharing/pairing code for Hubitat. This was necessary as the Hubitat hub does not contain a Bluetooth radio that is required for Matter Commissioning.

Since then, Hubitat has updated the Hubitat Mobile Phone application to allow Matter Commissioning of Matter over WiFi devices. Thus, using your smart phone (which has a Bluetooth radio), Matter over WiFi devices can be directly added to Hubitat.

Matter over Thread devices still require the use of another system, as the Hubitat Hub does not contain a Thread radio.

albertjmulder · January 8, 2026, 8:59pm

Aw ok I got it with the Hubitat App. Thanks.

Now how can we get habitat to support my new device? It comes through as Generic Matter Outlet, and it has RGB and does not detect it. I have it set to Generic Matter Multi-EndPoint Switch, and it created 3 child devices, however the third child should be for the RGB, but it made it also a switch, the first two each independently control each outlet, which works great, how can I get the third child to correctly see the RGB?

aaiyar · January 8, 2026, 9:01pm

What is the device?

bcopeland · January 8, 2026, 9:08pm

Just ask.. I love writing drivers for unique devices (ones that don't fit neatly under generic drivers)...

ogiewon · January 8, 2026, 11:45pm

Please share the device details. We need the manufacturer and model number of this device in order for anyone to assist further.

albertjmulder · January 9, 2026, 12:05am

So I have the InvisOutlet Aura, that just got sent to the backers. No I have installed the "Matter Advanced Bridge" and that was able to create 6 child drivers and it created:

Working: Matter Generic Component Switch (Top outlet)

Working: Matter Generic Component Switch (Bottom outlet)

Working: Generic Component Omni Sensor (Illuminance)

Partly Working: Generic Component RGBW (The CT version Works, but the RGB does nothing)

Not working: Matter Generic Component Switch (Hidden Touch Button Top that can be used to turn on outlet or configured to run a scene) Setup via app

Not working: Matter Generic Component Switch (Hidden Touch Button Bottom that can be used to turn on outlet or configured to run a scene) Setup via app

Let me know what other info you need. more than happy to provide

kkossev · January 9, 2026, 8:24am

Yesterday I pushed an update of the MAB, adding support for Matter buttons :

After updating the MAB package, please do the following :

delete the child device #0B and #0C
In the Preferences tab, enable the 'Advanced Options' and un-toggle the ' Minimize State Variables' option, we may need more detailed info for troubleshooting.
run a new '_ Discover All' process

Refresh the device web page, the last two child devices must be recreated, using the new ''Matter Generic Component Button' diver. Let me know if any 'button pushed' events are registered.

albertjmulder · January 9, 2026, 6:00pm

So this is what I get when using one of the touch buttons now with new update you did:

dev:19472026-01-09 11:16:09.336 AMdebugBridge#1942 Device#0B shortRelease event processed
dev:19472026-01-09 11:16:09.308 AMdebugBridge#1942 Device#0B handleUnprocessed: {"endpoint":"0B","cluster":"003B","evtId":"0003","clusterInt":59,"evtInt":3,"values":{"0":{"type":"04","isContextSpecific":true,"value":"01"}}}
dev:19472026-01-09 11:16:09.306 AMdebugBridge#1942 Device#0B [[name:unprocessed, value:{"endpoint":"0B","cluster":"003B","evtId":"0003","clusterInt":59,"evtInt":3,"values":{"0":{"type":"04","isContextSpecific":true,"value":"01"}}}, descriptionText:Bridge#1942 Device#0B unprocessed cluster 003B event 0003 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:19472026-01-09 11:16:09.288 AMdebugBridge#1942 Device#0B currentPosition changed to 00
dev:19472026-01-09 11:16:09.286 AMdebugBridge#1942 Device#0B handleUnprocessed: {"endpoint":"0B","cluster":"003B","attrId":"0001","value":"00","clusterInt":59,"attrInt":1}
dev:19472026-01-09 11:16:09.285 AMdebugBridge#1942 Device#0B [[name:unprocessed, value:{"endpoint":"0B","cluster":"003B","attrId":"0001","value":"00","clusterInt":59,"attrInt":1}, descriptionText:Bridge#1942 Device#0B unprocessed cluster 003B attribute 0001 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:19472026-01-09 11:16:08.957 AMdebugBridge#1942 Device#0B initialPress event processed
dev:19472026-01-09 11:16:08.956 AMdebugBridge#1942 Device#0B handleUnprocessed: {"endpoint":"0B","cluster":"003B","evtId":"0001","clusterInt":59,"evtInt":1,"values":{"0":{"type":"04","isContextSpecific":true,"value":"01"}}}
dev:19472026-01-09 11:16:08.954 AMdebugBridge#1942 Device#0B [[name:unprocessed, value:{"endpoint":"0B","cluster":"003B","evtId":"0001","clusterInt":59,"evtInt":1,"values":{"0":{"type":"04","isContextSpecific":true,"value":"01"}}}, descriptionText:Bridge#1942 Device#0B unprocessed cluster 003B event 0001 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:19472026-01-09 11:16:08.835 AMdebugBridge#1942 Device#0B currentPosition changed to 01
dev:19472026-01-09 11:16:08.834 AMdebugBridge#1942 Device#0B handleUnprocessed: {"endpoint":"0B","cluster":"003B","attrId":"0001","value":"01","clusterInt":59,"attrInt":1}
dev:19472026-01-09 11:16:08.832 AMdebugBridge#1942 Device#0B [[name:unprocessed, value:{"endpoint":"0B","cluster":"003B","attrId":"0001","value":"01","clusterInt":59,"attrInt":1}, descriptionText:Bridge#1942 Device#0B unprocessed cluster 003B attribute 0001 (to be re-processed in the child driver!), unit:null, type:physical]]

Also its still only getting the CT driver instead of a RGBW driver (When manually switching only the CT part works)

kkossev · January 9, 2026, 6:19pm

Refresh the device web page - how many child devices do you have?

~~(the logs look good, the buttons are sending events to the child device)~~

albertjmulder · January 9, 2026, 6:23pm

kkossev · January 9, 2026, 6:24pm

Please click on the reSubscribe button and try again

kkossev · January 9, 2026, 6:27pm

Let's try to get the buttons working first...

albertjmulder · January 9, 2026, 6:28pm

did the re subscribe, and this is what comes in the logs for the last device (OC):

dev:19482026-01-09 11:27:12.845 AMdebugBridge#1942 Device#0C shortRelease event processed
dev:19482026-01-09 11:27:12.844 AMdebugBridge#1942 Device#0C handleUnprocessed: {"endpoint":"0C","cluster":"003B","evtId":"0003","clusterInt":59,"evtInt":3,"values":{"0":{"type":"04","isContextSpecific":true,"value":"01"}}}
dev:19482026-01-09 11:27:12.842 AMdebugBridge#1942 Device#0C [[name:unprocessed, value:{"endpoint":"0C","cluster":"003B","evtId":"0003","clusterInt":59,"evtInt":3,"values":{"0":{"type":"04","isContextSpecific":true,"value":"01"}}}, descriptionText:Bridge#1942 Device#0C unprocessed cluster 003B event 0003 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:19482026-01-09 11:27:12.822 AMdebugBridge#1942 Device#0C currentPosition changed to 00
dev:19482026-01-09 11:27:12.821 AMdebugBridge#1942 Device#0C handleUnprocessed: {"endpoint":"0C","cluster":"003B","attrId":"0001","value":"00","clusterInt":59,"attrInt":1}
dev:19482026-01-09 11:27:12.819 AMdebugBridge#1942 Device#0C [[name:unprocessed, value:{"endpoint":"0C","cluster":"003B","attrId":"0001","value":"00","clusterInt":59,"attrInt":1}, descriptionText:Bridge#1942 Device#0C unprocessed cluster 003B attribute 0001 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:19482026-01-09 11:27:12.510 AMdebugBridge#1942 Device#0C initialPress event processed
dev:19482026-01-09 11:27:12.508 AMdebugBridge#1942 Device#0C handleUnprocessed: {"endpoint":"0C","cluster":"003B","evtId":"0001","clusterInt":59,"evtInt":1,"values":{"0":{"type":"04","isContextSpecific":true,"value":"01"}}}
dev:19482026-01-09 11:27:12.506 AMdebugBridge#1942 Device#0C [[name:unprocessed, value:{"endpoint":"0C","cluster":"003B","evtId":"0001","clusterInt":59,"evtInt":1,"values":{"0":{"type":"04","isContextSpecific":true,"value":"01"}}}, descriptionText:Bridge#1942 Device#0C unprocessed cluster 003B event 0001 (to be re-processed in the child driver!), unit:null, type:physical]]
dev:19482026-01-09 11:27:12.488 AMdebugBridge#1942 Device#0C currentPosition changed to 01
dev:19482026-01-09 11:27:12.486 AMdebugBridge#1942 Device#0C handleUnprocessed: {"endpoint":"0C","cluster":"003B","attrId":"0001","value":"01","clusterInt":59,"attrInt":1}
dev:19482026-01-09 11:27:12.484 AMdebugBridge#1942 Device#0C [[name:unprocessed, value:{"endpoint":"0C","cluster":"003B","attrId":"0001","value":"01","clusterInt":59,"attrInt":1}, descriptionText:Bridge#1942 Device#0C unprocessed cluster 003B attribute 0001 (to be re-processed in the child driver!), unit:null, type:physical]]

kkossev · January 9, 2026, 6:34pm

Thank you for sending the logs. I will analyze them and provide an update later, most likely by tomorrow.
Currently, I am working on adding Matter Locks to the AMB package, will be included in the next update...

Nuki Lock