Matter attribute “NodeLabel” is not taken into account for bridges EndPoints

Everything Matter
, , ,
1

Hello,

I am facing an issue when pairing a Matter bridge (like Hue Bridge) with my M3 Hub. The names of the bridged devices displayed are not those indicated in the Matter NodeLabel attribute (attribute 5), but rather those indicated in ProductName.
This makes the identification process very complicated and time-consuming. This should not be the case.

Could you please fix the firmware of the M3 Hub and the Aqara app to resolve this issue?

I am available for beta testing if necessary.

Best regards

Hue bridge sub-devices in Aqara app

image
image1170×2532 131 KB

Hue bridge node

image
image393×601 13.9 KB

EP Bridde node

image
image855×932 28.6 KB

5 Likes
2

In your setup, using NodeLabel instead of ProductName does improve device type differentiation in listings, ProductName seems like its product model. However, ProductName might offer clearer distinction with other brand‘s Matter devices？

We recommend further investigation about this requirement. If you have experience with other Matter device, we’d welcome real-world examples. I’ll also discuss this approach with our R&D team.

3 Likes
3

Thanks for your reply.
Here is the problem with the current implementation. How could you:

  1. distinguish between devices if you have several of the same model?
  2. identify what the model name, which consists of letters and numbers, corresponds to. This means nothing to users.

IMG_3681
IMG_36811170×2532 187 KB

This does not seem sensible to me in this case because in the Hue bridge, a node name is defined for each device.

1 Like
4

How about ProductLabel? It seems that it can be more clearly expressed than NodeLabel.

1 Like
5

The value of the field NodeLabel is defined by the user, so it is a name that will have meaning for them, unlike a product manufacturer reference (composed of numbers and letters).

Look at 23-27349-008_matter-1-4-2-adopted-core-specification.pdf (page 760)

11.1.5.6. NodeLabel Attribute
This attribute SHALL represent a user defined name for the Node. This attribute SHOULD be set
during initial commissioning and MAY be updated by further reconfigurations.

1 Like
6

Will you take this into account?

1 Like
7

Can this be taken into account in the 2026 roadmap?

2 Likes
9

Hi,

I’d like to follow up on this issue regarding the Matter NodeLabel attribute not being taken into account for bridged endpoints.

Is there any update on this?

When Aqara devices are exposed through the Matter Bridge, it would be very useful if the NodeLabel attribute could be correctly applied to the corresponding bridged endpoints. This would allow Matter controllers to use the intended device/endpoint names instead of relying on generic or automatically generated names.

Could you please clarify:

  • whether this behavior is considered a bug or a current limitation;
  • whether a fix is planned for the Aqara Matter Bridge;
  • whether the fix would be delivered through an M3 firmware update;
  • and whether there is an estimated timeframe?

Proper support for NodeLabel would significantly improve the usability of Aqara’s Matter Bridge, especially in installations with many bridged devices.

Thanks for the update!

1 Like