Matter WindowCovering (Cluster 258) from Brel M-Box detected as General Percentage and not controllable

Please use template to report bugs and problems. Post here your questions when not sure where else to post
Only for bugs in the Domoticz application! other problems go in different subforums!

Moderators: leecollings, remb0

Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.

Use the following template when posting here:

Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....

If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly

If you are replying, please do not quote images/code from the first post

Please mark your topic as Solved when the problem is solved.
Post Reply
Joky
Posts: 3
Joined: Monday 16 November 2026 18:17
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Matter WindowCovering (Cluster 258) from Brel M-Box detected as General Percentage and not controllable

Post by Joky »

# Matter WindowCovering (Cluster 258) from Brel M-Box is not mapped correctly in Domoticz

## Environment

- Domoticz version: 2026.1 (Build 17929)
- Matter hardware: `Matter (python-matterjs-server)`
- Matter Server: `matterjs-server 1.6.0`
- Docker installation
- Brel Hub-04 (M-Box)
- Brel DM45LE/S screen motor

## Description

The Matter node is discovered correctly by Domoticz, but the Matter WindowCovering device is not properly mapped.

The device appears in Domoticz as:

```text
Type: General
SubType: Percentage
```

instead of a controllable Blinds/WindowCovering device.

## What works

The Matter setup itself is working correctly:

- MatterJS server discovers the Brel M-Box.
- The DM45LE/S motor is exposed as a Matter WindowCovering device.
- Open (`UpOrOpen`) works.
- Close (`DownOrClose`) works.
- Stop (`StopMotion`) works.
- `GoToLiftPercentage` works.
- Position values are updated correctly inside MatterJS.

MatterJS reports values such as:

```text
CurrentPositionLiftPercent100ths = 5000
TargetPositionLiftPercent100ths = 5000
```

and the physical screen moves accordingly.

## What Domoticz does

Domoticz discovers the node:

```text
Node 2
Vendor: Brel
Product: M-Box
Status: OK
```

and creates a device:

```text
IDX: 82
Name: Brel
Type: General
SubType: Percentage
```

## Problem

The Domoticz device always remains at:

```text
100%
```

even when the screen position changes.

Example:

1. In MatterJS execute:

```json
{
"liftPercent100thsValue": 5000
}
```

2. MatterJS updates:

```text
CurrentPositionLiftPercent100ths = 5000
```

3. Physical screen moves to approximately 50%.

4. Domoticz device remains:

```text
100%
```

and is not updated.

## Expected behaviour

Domoticz should:

- Detect Matter WindowCovering Cluster `0x0102` (258).
- Create a controllable Blinds/WindowCovering device.
- Update the position according to:
- `CurrentPositionLiftPercent100ths`
- `TargetPositionLiftPercent100ths`
- Support:
- Up/Open
- Down/Close
- Stop
- Set Percentage

## Additional information

MatterJS correctly identifies the device as:

```text
Device Type: Window Covering
Cluster: 258 (0x0102)
Product: DM45LE/S
```

So the issue appears to be in the Domoticz Matter device mapping for WindowCovering devices.
User avatar
gizmocuz
Posts: 3077
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Top of the world
Contact:

Re: Matter WindowCovering (Cluster 258) from Brel M-Box detected as General Percentage and not controllable

Post by gizmocuz »

Thanks for the detailed report and the MatterJS values, that pins it down nicely.

Your diagnosis is correct. The Matter driver does recognise the WindowCovering cluster (0x0102) and reads the lift position, but it currently creates only a read-only device from it (the General/Percentage device you see). There is no command path yet to send Up/Open, Down/Close, Stop or GoToLiftPercentage back to the blind. So Matter blind control is simply not implemented yet, there is nothing wrong with your setup or the M-Box.

We will add a proper controllable Blinds device for WindowCovering (open, close, stop and set position). I have opened an issue to track it: https://github.com/domoticz/domoticz/issues/7203

If you are willing to help, the Domoticz log lines from when the Brel node is discovered (Setup > Log) and the cluster/attribute list MatterJS shows for that node would help us map it correctly, and once there is a test build it would be great if you could try it against your M-Box.
Quality outlives Quantity!
Joky
Posts: 3
Joined: Monday 16 November 2026 18:17
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Matter WindowCovering (Cluster 258) from Brel M-Box detected as General Percentage and not controllable

Post by Joky »

Thanks for handling this issue.
I have installed now Domoticz 2026.4 . With this version the position in % is now reported from Domoticz. However there is no control.
Domoticz 2026.4 (build 18630):

Brel M-Box / DM45LE/S
Matter WindowCovering (cluster 258)

Current behavior:
- Device is created as General/Percentage
- Position updates work correctly

Expected behavior:
- Create a controllable Blinds/WindowCovering device
- Support Open/Close/Stop/Set Percentage

I hope this will help you for further improvement.
Regards Jo
Joky
Posts: 3
Joined: Monday 16 November 2026 18:17
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Matter WindowCovering (Cluster 258) from Brel M-Box detected as General Percentage and not controllable

Post by Joky »

I am sorry,
I forgot to add the Attributes/cluster on endpoint 2:

Attributes of Identify Cluster on Endpoint 2
ClusterId 3 (0x0003)
IdentifyTime
AttributeId: 0 (0x0000) - Value type: uint16
0
IdentifyType
AttributeId: 1 (0x0001) - Value type: IdentifyTypeEnum
0
GeneratedCommandList
AttributeId: 65528 (0xFFF8) - Value type: List[command-id]
[]
AcceptedCommandList
AttributeId: 65529 (0xFFF9) - Value type: List[command-id]
[0]
Custom/Unknown Attribute
AttributeId: 65530 (0xFFFA) - Value type: unknown
[]
AttributeList
AttributeId: 65531 (0xFFFB) - Value type: List[attrib-id]
FeatureMap
AttributeId: 65532 (0xFFFC) - Value type: map32
0
ClusterRevision
AttributeId: 65533 (0xFFFD) - Value type: ClusterRevision
4
Post Reply