How to show custom names for Matter bridge endpoints in controller apps?

[Noushadali007]

Hi ESP-Matter team,

I am working on a Matter Bridge implementation using ESP32-S3 and the ESP-Matter bridge_cli example.

My requirement:

• Single ESP32-S3 acts as a Matter Bridge

• Multiple virtual light endpoints are created dynamically

• I want Matter controller apps to show custom endpoint names like:

  • Living Room Light
  • Kitchen Light
  • Bedroom Light

Currently the controller apps show generic names like:

• Light
• Light 2

I already tried:

• BridgedDeviceBasicInformation::NodeLabel
• FixedLabel cluster

but most controllers still show default names.

Questions:

1. What is the correct way to show custom bridged endpoint names in Matter controller apps?
2. Which ESP-Matter bridge example should I use as reference for dynamic bridged devices?

ESP-Matter version:

• ESP-IDF v5.4.1
• ESP32-S3 target

Thanks.

[tomasmcguinness]

Where are you seeing the default names?

I have built two Matter bridges, both running on the S3. I expose the bridged devices using the NodeLabel attribute of the BridgedDeviceBasicInformation cluster. When I commission them with the Aqara app, it shows pointless names for the child devices, like 105EF001.

In my own controllers, I show the names correctly

I suspect this is just a lack of support by the official controllers. The only way to confirm would be to get an official bridge from the likes of Hue and see what it does. Given that iOS Home doesn't even support Electrical Sensors...

[lboue]

The limitation is on the Aqara app side. I've already reported it, but nothing has changed.

[tomasmcguinness]

Figures. I suspect even commercial Zigbee -> Matter bridges don't use the NodeLabel.