M-Box matter hub not doing anything useful

🛎️ Get Help Devices
1

This is a Matter wifi bridge for motorized shades - it seems to be used for a few brands of generic China roller shades - dooya matter hub m-box dd7006m

I'm able to add it to the Hubitat as a Matter device (11 digit code) but it shows up as a "Nature Remo Nano" which is apparently a fan/thermostat controller.

I think I foolishly expected it to expose the raw matter devices and let me work on top of them, but it doesn't seem to. There are multiple shades attached to the hub.

Is there some way I can get the Hubitat to let me control these devices?

Thanks.

2

I'd try the "Generic Matter Bridge" driver. Be sure to run "Configure" after you switch, and check Logs for any errors if you run into problems.

3

Thanks Bert!

Some progress - that now creates two child "Generic Window Component Shade" devices.

However nothing seems to happen when issuing commands, and the "state" it reads is wrong (20%)

Not sure where I go from here!

Under "Current States" for the hub:
supportedThermostatFanModes
State Variables
endpoints {}
shutterType {"02":"00","03":"00"}

"Close" command issued to Generic Component Window Shade:
dev:722026-04-03 06:40:08.631 AMdebug
descMap:[endpoint:02, cluster:0102, attrId:000A, value:00, clusterInt:258, attrInt:10]
dev:722026-04-03 06:40:08.627 AMtrace
description:read attr - endpoint: 02, cluster: 0102, attrId: 000A, value: 0400
dev:722026-04-03 06:40:06.913 AMdebug
descMap:[endpoint:02, cluster:0102, attrId:000A, value:05, clusterInt:258, attrInt:10]
dev:722026-04-03 06:40:06.908 AMtrace
description:read attr - endpoint: 02, cluster: 0102, attrId: 000A, value: 0405

"Set 50%" command issued:
dev:722026-04-03 06:42:22.733 AMdebug
descMap:[endpoint:02, cluster:0102, attrId:000A, value:00, clusterInt:258, attrInt:10]
dev:722026-04-03 06:42:22.729 AMtrace
description:read attr - endpoint: 02, cluster: 0102, attrId: 000A, value: 0400
dev:722026-04-03 06:42:20.823 AMdebug
descMap:[endpoint:02, cluster:0102, attrId:000A, value:0A, clusterInt:258, attrInt:10]
dev:722026-04-03 06:42:20.815 AMtrace
description:read attr - endpoint: 02, cluster: 0102, attrId: 000A, value: 040A

"Configure" command issued to hub:
dev:722026-04-03 06:37:48.671 AMdebug
descMap:[:]
dev:722026-04-03 06:37:48.666 AMtrace
description:subscriptionResult - subscriptionId: 1932928389
dev:722026-04-03 06:37:48.576 AMdebug
descMap:[endpoint:03, cluster:0102, attrId:000A, value:00, clusterInt:258, attrInt:10]
dev:722026-04-03 06:37:48.571 AMtrace
description:read attr - endpoint: 03, cluster: 0102, attrId: 000A, value: 0400
dev:742026-04-03 06:37:48.555 AMinfo
Generic Component Window Shade position is 20%
dev:722026-04-03 06:37:48.544 AMdebug
descMap:[endpoint:03, cluster:0102, attrId:0008, value:14, clusterInt:258, attrInt:8]
dev:722026-04-03 06:37:48.540 AMtrace
description:read attr - endpoint: 03, cluster: 0102, attrId: 0008, value: 14
dev:722026-04-03 06:37:48.529 AMdebug
descMap:[endpoint:03, cluster:0102, attrId:0000, value:00, clusterInt:258, attrInt:0]
dev:722026-04-03 06:37:48.525 AMtrace
description:read attr - endpoint: 03, cluster: 0102, attrId: 0000, value: 0400
dev:722026-04-03 06:37:48.503 AMdebug
descMap:[endpoint:02, cluster:0102, attrId:000A, value:00, clusterInt:258, attrInt:10]
dev:722026-04-03 06:37:48.498 AMtrace
description:read attr - endpoint: 02, cluster: 0102, attrId: 000A, value: 0400
dev:732026-04-03 06:37:48.478 AMinfo
Generic Component Window Shade position is 20%
dev:722026-04-03 06:37:48.468 AMdebug
descMap:[endpoint:02, cluster:0102, attrId:0008, value:14, clusterInt:258, attrInt:8]
dev:722026-04-03 06:37:48.463 AMtrace
description:read attr - endpoint: 02, cluster: 0102, attrId: 0008, value: 14
dev:722026-04-03 06:37:48.453 AMdebug
descMap:[endpoint:02, cluster:0102, attrId:0000, value:00, clusterInt:258, attrInt:0]
dev:722026-04-03 06:37:48.449 AMtrace
description:read attr - endpoint: 02, cluster: 0102, attrId: 0000, value: 0400
dev:722026-04-03 06:37:48.115 AMdebug
getComponentSubscriptions:[[ep:0x03, cluster:0x0102, attr:0x0008], [ep:0x03, cluster:0x0102, attr:0x000A], [ep:0x03, cluster:0x0102, attr:0x0000]]
dev:722026-04-03 06:37:48.104 AMdebug
getComponentSubscriptions:[[ep:0x02, cluster:0x0102, attr:0x0008], [ep:0x02, cluster:0x0102, attr:0x000A], [ep:0x02, cluster:0x0102, attr:0x0000]]
dev:722026-04-03 06:37:48.096 AMdebug
Endpoints found: [[endpointId:02, inClusters:001D,0039,0003,0004,0005,0102], [endpointId:03, inClusters:001D,0039,0003,0004,0005,0102]]
dev:722026-04-03 06:37:47.246 AMwarn
configure()

4

After doing some more research, it appears Hubitat does not actually support Matter devices generically and if you aren't lucky with whatever the default drivers are doing, they won't work. The promise of Matter is that you DON'T need a custom driver, so that's a bit counter intuitive.

It also appears Hubitat is not Matter certified, although it advertises it "works with" Matter.

These shades are work fine with Alexa and Home Assistant so that's rather disappointing with no custom driver. I prefer Hubitat's ease of maintenance and rule engine, but I guess it's time to migrate to Home Assistant.

5

If you have Home Assistant and the shades are already connected to Home Assistant bring them into Hubitat via the Home Assistant Device Bridge from Hubitat Package Manager.

I bring several devices into Hubitat this way allowing me to use Rule Machine for all my automations.

There is no such thing as the perfect platform.

Also, you could download the Matter Advanced Bridge from Hubitat Package Manager and try it to see if it will make your shades work. If you do this apply the Matter Advanced Bridge driver to your matter bridge device then hit discover all. It will create child devices for the shades and this driver may work.

2 Likes