Aeon Labs ZW056 doorbell - how to trigger other actions

I’m running OH 2.5 and I’m trying to add in my ZW056 doorbell as a trigger mechanism in a rule. The doorbell has added in fine, I see it online etc, but I’d like the doorbell to trigger another action via rule.

I’m not seeing any events trigger from a doorbell button push, nothing changes state typically (sometimes the battery level) so I’m not sure what condition to match on. I turned on zwave debug logging and captured this, hoping there’s something meaningful in here I can use?

2020-02-19 11:23:20.682 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 4D 05 70 06 2A 01 00 C1 00 22 
2020-02-19 11:23:20.688 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=77, callback=0, payload=00 4D 05 70 06 2A 01 00 C1 00 
2020-02-19 11:23:20.691 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=77, callback=0, payload=00 4D 05 70 06 2A 01 00 C1 00 
2020-02-19 11:23:20.693 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-02-19 11:23:20.694 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 77: Application Command Request (ALIVE:DONE)
2020-02-19 11:23:20.695 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 77: resetResendCount initComplete=true isDead=false
2020-02-19 11:23:20.697 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 77: Incoming command class COMMAND_CLASS_CONFIGURATION, endpoint 0
2020-02-19 11:23:20.697 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 77: SECURITY not supported
2020-02-19 11:23:20.698 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 77: Received COMMAND_CLASS_CONFIGURATION V1 CONFIGURATIONCMD_REPORT
2020-02-19 11:23:20.699 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 77: Node configuration report, parameter = 42, value = 0, size = 1
2020-02-19 11:23:20.700 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 77: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent
2020-02-19 11:23:20.701 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 77: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_CONFIGURATION, value=org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@9cf
2020-02-19 11:23:20.702 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 77: Update CONFIGURATION 42/1 to 0
2020-02-19 11:23:20.704 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 77: Updating channel state zwave:device:41600d1a:node77:config_decimal_param42 to 0 [DecimalType]
2020-02-19 11:23:20.720 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 77: Commands processed 1.
2020-02-19 11:23:20.727 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 77: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@14ed55.
2020-02-19 11:23:20.728 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-02-19 11:23:20.729 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-02-19 11:23:20.730 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-19 11:23:20.732 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

Thanks!

Nope, much too short:

Please provide a debug log showing the button push.
Make sure you have an item linked to the switch_binary channel.

1 Like