Hi,
We are developing a Matter-certified device using the On/Off Plug-In Unit device type (0x010A).
The device commissions and operates correctly across major Matter controllers (Home Assistant, Google Home, Apple Home). However, we are facing a product launch blocker related to UI representation.
Every controller renders this device type as a generic "Switch" with a toggle icon, driven entirely by the Device Type ID — regardless of ProductName, NodeLabel, or userLabel settings.
This creates two concerns:
-
Branding — The "switch" representation does not reflect the device's actual function or intended user interaction.
-
Safety — Users may treat it as a standard switch and operate it at inappropriate times, which is a real safety concern for our specific use case.
Our questions (focused on what the Matter specification allows):
- Does the Matter specification provide any mechanism — beyond Device Type ID — that a manufacturer can use to influence how controllers render a device in their UI?
- Is there a more suitable device type for a device that exposes On/Off functionality but is not intended to be used as a general-purpose switch or plug?
- Are there any plans in the roadmap to introduce finer-grained UI hints or device sub-types within the spec?
We want to stay fully spec-compliant, so we are looking for what is formally supported within the Matter standard rather than controller-specific workarounds.
Any guidance from the spec or SDK maintainers would be greatly appreciated.
Thank you!
Hi,
We are developing a Matter-certified device using the On/Off Plug-In Unit device type (0x010A).
The device commissions and operates correctly across major Matter controllers (Home Assistant, Google Home, Apple Home). However, we are facing a product launch blocker related to UI representation.
Every controller renders this device type as a generic "Switch" with a toggle icon, driven entirely by the Device Type ID — regardless of ProductName, NodeLabel, or userLabel settings.
This creates two concerns:
Branding — The "switch" representation does not reflect the device's actual function or intended user interaction.
Safety — Users may treat it as a standard switch and operate it at inappropriate times, which is a real safety concern for our specific use case.
Our questions (focused on what the Matter specification allows):
We want to stay fully spec-compliant, so we are looking for what is formally supported within the Matter standard rather than controller-specific workarounds.
Any guidance from the spec or SDK maintainers would be greatly appreciated.
Thank you!