RDM004 (Hue Wall Switch Module): genLevelCtrl (dimming) not sent via direct device-to-device binding either — docs may need clarification

What happened?

On a Hue Wall Switch Module (RDM004, model 929003017102) with a direct Zigbee binding, on/off (genOnOff) works correctly, but dimming (genLevelCtrl hold-to-dim) does not (no brightness_move/brightness_step commands are sent by the switch). This matches the behavior already reported in #21829 for group bindings, so the limitation does not appear to be specific to group bindings.

Also the docs state that only group bindings are working which is not the case.

Additionally, on a dual-rocker RDM004, actions are only sent for input 1. Input 2 never produces an action event, so a double rocker is not usable this way, which is documented correctly but still unfortunate. Any workaround for that would also be appreciated.

What did you expect to happen?

Holding a button bound directly to a light should send genLevelCtrl move/step commands so the light dims, similar to how genOnOff is forwarded.

How to reproduce it (minimal and precise)

• Bind a Hue Wall Switch Module (RDM004) directly to a light using bridge/request/device/bind (not a group).
• Press-and-hold the switch.
• Observe: the light turns on/off correctly, but does not dim.

Zigbee2MQTT version

2.14.1

Adapter firmware version

EmberZNet 8.0.2 [GA]

Adapter

SLZB-MR5U

Setup

Home Assistant Core 2026.9.1
Zigbee2MQTT add-on 2.14.1-1
Mosquitto broker add-on 7.1.0
SLZB-MR5U Zigbee Coordinator Dev firmware Revision: 20251122, SDK 8.0.2.0
RDM004 firmware 2.85.1

Device database.db entry

No response

Debug log

No response

Notes

No response

Start at the bridge/request/device/bind flow and compare direct binding behavior with the limitation reported in #21829. Check the documentation statement about group bindings and the RDM004 input-2 behavior. Done means the supported behavior and limitations are verified, then the implementation or documentation clearly matches those findings.