[Device Support Request] not standard TS004F?

Is your feature request related to a problem? Please describe. I got a Moes Smart Button. I can register it with ZHA, but I can create event for press, double press or long press.

I don’t really understant the device reference.
It reports it-self like a TS004F _TZ3000_kjfzuycl. TS004F is the reference, and TZ3000_kjfzuycl a kind of manufacturer ID?

There is already a quirk for TS004F, but it seems to be a 4 gang switch? with different manufacturer?

Is it really the same product, or do I have to try to make a news TS004F quirk?

Describe the solution you’d like A would like to catch event on press, double press and long press, in order to make automations.

Device signature

{
  "node_descriptor": "NodeDescriptor(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=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0104",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0004",
        "0x0006",
        "0x1000",
        "0xe001"
      ],
      "out_clusters": [
        "0x0003",
        "0x0004",
        "0x0006",
        "0x0008",
        "0x000a",
        "0x0019",
        "0x1000"
      ]
    }
  },
  "manufacturer": "_TZ3000_kjfzuycl",
  "model": "TS004F",
  "class": "zigpy.device.Device"
}

Diagnostic information

I don't have any diagnostic button.

Additional logs

with a 10s long press

_TZ3000_kjfzuycl TS004F Stop event was fired with parameters: {'options_mask': None, 'options_override': None}
17:05:42 - Maintenant
_TZ3000_kjfzuycl TS004F Step event was fired with parameters: {'step_mode': <StepMode.Up: 0>, 'step_size': 85, 'transition_time': 10, 'options_mask': None, 'options_override': None}
17:05:41 - Maintenant

with a single press

_TZ3000_kjfzuycl TS004F Move To Level event was fired with parameters: {'level': 255, 'transition_time': 1, 'options_mask': None, 'options_override': None}
17:06:22 - Il y a 2 minutes

with a double press

_TZ3000_kjfzuycl TS004F 92aa42fe on_of  
éteint
Add any other context or screenshots about the feature request here.
17:06:16 - Il y a 2 minutes

[drudgebg]

This work for button pressed alternate mode:

       (ALT_SHORT_PRESS, BUTTON): {
            ENDPOINT_ID: 1,
            CLUSTER_ID: 8,
            PARAMS: {'transition_time': 1, 'options_mask': None, 'options_override': None},
        },

[vbelloir]

No, alternate mode is for single press when lights are on.

When lights are off, it generates an ON command, but when there are already ON, it generate move_to_color_temp, move_to_level or move_to_hue_and_saturation commands.

For the PR, I can try.