[BUG] Hue Wall switch module RDM001 quirk not loaded

[tundratier]

Bug description

I’m having trouble with the wall swithces, as well. I have the old RDM001, and it does not load the quirk when pairing the device. So I don’t have the options available to change the button modes. It even says so within the log file:

2025-04-27 13:06:27.169 DEBUG (MainThread) [zha] (ZHAGatewayProxy) handling event protocol for event: RawDeviceInitializedEvent(device_info=RawDeviceInitializedDeviceInfo(ieee=00:17:88:01:0c:c2:6f:d6, nwk=0xD9BE, pairing_status=<DevicePairingStatus.INTERVIEW_COMPLETE: 2>, model=‘RDM001’, manufacturer=‘Signify Netherlands B.V.’, signature={‘manufacturer’: ‘Signify Netherlands B.V.’, ‘model’: ‘RDM001’, ‘node_desc’: {‘logical_type’: <LogicalType.EndDevice: 2>, ‘complex_descriptor_available’: 0, ‘user_descriptor_available’: 0, ‘reserved’: 0, ‘aps_flags’: 0, ‘frequency_band’: <FrequencyBand.Freq2400MHz: 8>, ‘mac_capability_flags’: <MACCapabilityFlags.AllocateAddress: 128>, ‘manufacturer_code’: 4107, ‘maximum_buffer_size’: 82, ‘maximum_incoming_transfer_size’: 128, ‘server_mask’: 11264, ‘maximum_outgoing_transfer_size’: 128, ‘descriptor_capability_field’: <DescriptorCapability.NONE: 0>}, ‘endpoints’: {1: {‘profile_id’: 260, ‘device_type’: <DeviceType.NON_COLOR_SCENE_CONTROLLER: 2096>, ‘input_clusters’: [0, 1, 3, 64512], ‘output_clusters’: [25, 0, 3, 4, 6, 8]}}}), event_type=‘zha_gateway_message’, event=‘raw_device_initialized’)
2025-04-27 13:06:27.169 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for Signify Netherlands B.V. RDM001 (00:17:88:01:0c:c2:6f:d6)
2025-04-27 13:06:27.170 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class ‘zhaquirks.philips.wall_switch.PhilipsWallSwitch’>
2025-04-27 13:06:27.170 DEBUG (MainThread) [zigpy.quirks] Fail because device_type mismatch on at least one endpoint

My HA Versions are:

Core: 2025.4.4
Supervisor: 2025.04.0
Operating System: 15.2
Frontend: 20250411.0

I tried to replace the quirk file with the latest from the Github Link posted above but the contents are identical. It seems to use the latest version.

Steps to reproduce

1. Add new device through ZHA
2. Set wall switch module into pairing mode
3. Complete pairing
4. Wall Switch will be detected as generic zigbee device without any manufacturer-specific options available

Expected behavior

The quirk for the wall switch module is loaded to enable setting manufacturer-specific options.

Screenshots/Video

No response

Device signature

Device signature

{
  "node_descriptor": {
    "logical_type": 2,
    "complex_descriptor_available": 0,
    "user_descriptor_available": 0,
    "reserved": 0,
    "aps_flags": 0,
    "frequency_band": 8,
    "mac_capability_flags": 128,
    "manufacturer_code": 4107,
    "maximum_buffer_size": 82,
    "maximum_incoming_transfer_size": 128,
    "server_mask": 11264,
    "maximum_outgoing_transfer_size": 128,
    "descriptor_capability_field": 0
  },
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0830",
      "input_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0xfc00"
      ],
      "output_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0006",
        "0x0008",
        "0x0019"
      ]
    }
  },
  "manufacturer": "Signify Netherlands B.V.",
  "model": "RDM001",
  "class": "zigpy.device.Device"
}

Diagnostic information

Diagnostic information

[Paste the diagnostic information here]

Logs

Logs

[Paste the logs here]

Additional information

No response

[tundratier]

Looking into https://github.com/zigpy/zha-device-handlers/blob/c2f64fd0a34fbac677bdac7b1a5fe069c69dd0a5/zhaquirks/philips/wall_switch.py and the signature of my wall switch module, it seems that it is identifying itself as an RDM001, while using the clusters of the RDM004. Can anyone more involved with the zigpy quirk code validate this theory?
The WSM was connected to a Hue bridge until recently. Maybe an OTA update updated the clusters of the RDM001 switch to be consistent with the newer RDM004?

[youpko]

I ran in to the same problem with two of these wall switches (production date of early 2023), Migrating them from the Hue Bridge to Home Assistant result a not usable device.
After going through the logs I found the same as what is described as above.

My logs

2025-05-05 11:50:49.365 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(timestamp=datetime.datetime(2025, 5, 5, 9, 50, 49, 365650, tzinfo=datetime.timezone.utc), priority=0, src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0xA6F9), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=1, source_route=None, extended_timeout=False, tsn=128, profile_id=260, cluster_id=0, data=Serialized[b'\x18\x07\x01\x04\x00\x00B\x18Signify Netherlands B.V.\x05\x00\x00B\x06RDM001'], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=116, rssi=-82)
2025-05-05 11:50:49.366 DEBUG (MainThread) [zigpy.zcl] [0xA6F9:1:0x0000] Received ZCL frame: b'\x18\x07\x01\x04\x00\x00B\x18Signify Netherlands B.V.\x05\x00\x00B\x06RDM001'
2025-05-05 11:50:49.366 DEBUG (MainThread) [zigpy.zcl] [0xA6F9:1:0x0000] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl<0x18>(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=0, direction=<Direction.Server_to_Client: 1>, disable_default_response=1, reserved=0, *is_cluster=False, *is_general=True), tsn=7, command_id=1, *direction=<Direction.Server_to_Client: 1>)
2025-05-05 11:50:49.367 DEBUG (MainThread) [zigpy.zcl] [0xA6F9:1:0x0000] Decoded ZCL frame: Basic:Read_Attributes_rsp(status_records=[ReadAttributeRecord(attrid=4, status=<Status.SUCCESS: 0>, value=TypeValue(type=CharacterString, value='Signify Netherlands B.V.')), ReadAttributeRecord(attrid=5, status=<Status.SUCCESS: 0>, value=TypeValue(type=CharacterString, value='RDM001'))])
2025-05-05 11:50:49.368 INFO (MainThread) [zigpy.device] [0xa6f9] Read model 'RDM001' and manufacturer 'Signify Netherlands B.V.' from <Endpoint id=1 in=[basic:0x0000, power:0x0001, identify:0x0003, manufacturer_specific:0xFC00] out=[ota:0x0019, basic:0x0000, identify:0x0003, groups:0x0004, on_off:0x0006, level:0x0008] status=<Status.ZDO_INIT: 1>>
2025-05-05 11:50:49.368 INFO (MainThread) [zigpy.device] [0xa6f9] Discovered basic device information for <Device model='RDM001' manuf='Signify Netherlands B.V.' nwk=0xA6F9 ieee=xx:xx:Xx:xx:xx:xx:xx:xx is_initialized=True>
2025-05-05 11:50:49.368 DEBUG (MainThread) [zigpy.application] Device is initialized <Device model='RDM001' manuf='Signify Netherlands B.V.' nwk=0xA6F9 ieee=xx:xx:Xx:xx:xx:xx:xx:xx is_initialized=True>
2025-05-05 11:50:49.369 DEBUG (MainThread) [zha] Emitting event raw_device_initialized with data RawDeviceInitializedEvent(device_info=RawDeviceInitializedDeviceInfo(ieee=xx:xx:Xx:xx:xx:xx:xx:xx, nwk=0xA6F9, pairing_status=<DevicePairingStatus.INTERVIEW_COMPLETE: 2>, model='RDM001', manufacturer='Signify Netherlands B.V.', signature={'manufacturer': 'Signify Netherlands B.V.', 'model': 'RDM001', 'node_desc': {'logical_type': <LogicalType.EndDevice: 2>, 'complex_descriptor_available': 0, 'user_descriptor_available': 0, 'reserved': 0, 'aps_flags': 0, 'frequency_band': <FrequencyBand.Freq2400MHz: 8>, 'mac_capability_flags': <MACCapabilityFlags.AllocateAddress: 128>, 'manufacturer_code': 4107, 'maximum_buffer_size': 82, 'maximum_incoming_transfer_size': 128, 'server_mask': 11264, 'maximum_outgoing_transfer_size': 128, 'descriptor_capability_field': <DescriptorCapability.NONE: 0>}, 'endpoints': {1: {'profile_id': 260, 'device_type': <DeviceType.NON_COLOR_SCENE_CONTROLLER: 2096>, 'input_clusters': [0, 1, 3, 64512], 'output_clusters': [25, 0, 3, 4, 6, 8]}}}), event_type='zha_gateway_message', event='raw_device_initialized') (1 listeners)
2025-05-05 11:50:49.369 DEBUG (MainThread) [zha] (ZHAGatewayProxy) handling event protocol for event: RawDeviceInitializedEvent(device_info=RawDeviceInitializedDeviceInfo(ieee=xx:xx:Xx:xx:xx:xx:xx:xx, nwk=0xA6F9, pairing_status=<DevicePairingStatus.INTERVIEW_COMPLETE: 2>, model='RDM001', manufacturer='Signify Netherlands B.V.', signature={'manufacturer': 'Signify Netherlands B.V.', 'model': 'RDM001', 'node_desc': {'logical_type': <LogicalType.EndDevice: 2>, 'complex_descriptor_available': 0, 'user_descriptor_available': 0, 'reserved': 0, 'aps_flags': 0, 'frequency_band': <FrequencyBand.Freq2400MHz: 8>, 'mac_capability_flags': <MACCapabilityFlags.AllocateAddress: 128>, 'manufacturer_code': 4107, 'maximum_buffer_size': 82, 'maximum_incoming_transfer_size': 128, 'server_mask': 11264, 'maximum_outgoing_transfer_size': 128, 'descriptor_capability_field': <DescriptorCapability.NONE: 0>}, 'endpoints': {1: {'profile_id': 260, 'device_type': <DeviceType.NON_COLOR_SCENE_CONTROLLER: 2096>, 'input_clusters': [0, 1, 3, 64512], 'output_clusters': [25, 0, 3, 4, 6, 8]}}}), event_type='zha_gateway_message', event='raw_device_initialized')
2025-05-05 11:50:49.369 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for Signify Netherlands B.V. RDM001 (00:17:88:01:0c:c5:24:48)
2025-05-05 11:50:49.370 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.philips.wall_switch.PhilipsWallSwitch'>
2025-05-05 11:50:49.370 DEBUG (MainThread) [zigpy.quirks] Fail because device_type mismatch on at least one endpoint

After reading through the wall_swith.py at line 94 the comments specify the cluster input/output IDs. But comparing it to the log my device has an extra output basic:0x0000 cluster. I presume this is the reason the quirk gets rejected.

 #  <SimpleDescriptor endpoint=1 profile=260 device_type=2080
 #  device_version=1
 #  input_clusters=[0, 1, 3, 64512]
 #  output_clusters=[3, 4, 6, 8, 25]>

compared to my log

<Endpoint id=1 
in=[basic:0x0000, power:0x0001, identify:0x0003, manufacturer_specific:0xFC00] 
out=[ota:0x0019, basic:0x0000, identify:0x0003, groups:0x0004, on_off:0x0006, level:0x0008] 
status=<Status.ZDO_INIT: 1>>

I hope this helps finding the cause of this issue. I have no experience python programming so I don't know what I can do further with this information.