"Press Type event was fired with parameters: {'press_type': 1}"?

Configuration
1

I brought some white label Zigbee scene switchers\batter powered button, ZHA says that it has configured them, and the appear to connect OK.

When I go to the automations setting it gives me multiple options in the GUI to trigger an event using the scene switch.

I get:

Fist Button Press
First Button continuous press
First button double clicked

As options

However, when I press the scene switcher non of these events are registered. Instead I get a log entry that says

“Press Type event was fired with parameters: {‘press_type’: 1}”

I’m not sure how to capture this in an automation so that I can actually use it in HA.

The device was unbranded, the device info in HA says “TS0041 by _TZ3000_mrpevh8p”

The device signature data is

{
“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=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, 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”: “0x0104”,
“device_type”: “0x0000”,
“input_clusters”: [
“0x0000”,
“0x0001”,
“0xe000”
],
“output_clusters”: [
“0x0006”,
“0x000a”,
“0x0019”
]
}
},
“manufacturer”: “_TZ3000_mrpevh8p”,
“model”: “TS0041”,
“class”: “zhaquirks.tuya.ts0041.TuyaSmartRemote0041TOPlusA”
}

2

Go to Developer Tools, then click the Event tab
Now type * in the listen field and start the listening.
Click the button press you want and look through the captured events.

With * there all events will be captured, but once you have found the event for the button, then you can narrow it down with a better filter.

2 Likes
3

Once I’ve determined what the event is, how do i watch for it in an automation?

4

I get this

event_type: zha_event
data:
  device_ieee: a4:c1:38:bf:47:a5:0f:28
  unique_id: a4:c1:38:bf:47:a5:0f:28:1:0x0006
  device_id: 744a26144b957b782a57805f63035d95
  endpoint_id: 1
  cluster_id: 6
  command: press_type
  args:
    - 0
  params:
    press_type: 0
origin: LOCAL
time_fired: "2024-01-11T19:50:16.486055+00:00"
context:
  id: 01HKX16HN6N5W2XR3XVYJB5SJY
  parent_id: null
  user_id: null

and this

event_type: zha_event
data:
  device_ieee: a4:c1:38:bf:47:a5:0f:28
  unique_id: a4:c1:38:bf:47:a5:0f:28:1:0x0006
  device_id: 744a26144b957b782a57805f63035d95
  endpoint_id: 1
  cluster_id: 6
  command: remote_button_short_press
  args: []
  params: {}
origin: LOCAL
time_fired: "2024-01-11T19:50:16.485302+00:00"
context:
  id: 01HKX16HN5FNGBHK6V8R5VG2TX
  parent_id: null
  user_id: null

How do I listen for them to trigger and automation?

5

You should be able to use an event trigger.

6

OK, an event trigger, but how do I find out what the trigger is for this device when the built in ones seemingly do nothing?

7

The two you just posted is actual events from that device.