Trigger on event from sensor

Development
1

I’m trying to trigger an action (open the door) when my keypad sensor reports an event. (number 6).

OZW log says the following when the code is wright and you press “home” on the keypad:
Info, Node010, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:6, status=255

And when the code is wright and you press “away”:
Info, Node010, Received Alarm report: type=0, level=255, sensorSrcID=0, type:Access Control event:5, status=255

I don’t want to use alarm level for other reasons so I’d like to use access control.

In automations.yaml I did the following:

  • alias: Open Door
    trigger:
    platform: event
    entity_id: sensor.keypad_access_control_10_9
    event: 6
    action:
    - service: does its thing

I guess my automations.yaml is wrong / event and sensor can not be combined like that.

What’d you do here?

Thanks!

2

You need an “even_type” after the platform as a trigger.

Post the whole even from the log, from the date and time to the end for both, and we can probably work it out.

3

Hi!

Here is the part from the log when typing the correct code:

2017-12-13 19:26:48.555 Detail, Node010,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x0a, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x06, 0x01, 0x01, 0x60
2017-12-13 19:26:48.555 Detail,
2017-12-13 19:26:48.555 Info, Node010, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:6, status=255
2017-12-13 19:26:48.555 Detail, Node010, Refreshed Value: old value=0, new value=0, type=byte
2017-12-13 19:26:48.556 Detail, Node010, Changes to this value are not verified
2017-12-13 19:26:48.556 Detail, Node010, Refreshed Value: old value=0, new value=0, type=byte
2017-12-13 19:26:48.556 Detail, Node010, Changes to this value are not verified
2017-12-13 19:26:48.556 Detail, Node010, Refreshed Value: old value=0, new value=0, type=byte
2017-12-13 19:26:48.556 Detail, Node010, Changes to this value are not verified
2017-12-13 19:26:48.556 Detail, Node010, Refreshed Value: old value=6, new value=6, type=byte
2017-12-13 19:26:48.556 Detail, Node010, Changes to this value are not verified
2017-12-13 19:26:48.556 Detail, Node010, Notification: ValueChanged
2017-12-13 19:26:48.596 Detail, Node010, Notification: ValueChanged
2017-12-13 19:26:48.635 Detail, Node010, Notification: ValueChanged
2017-12-13 19:26:48.663 Detail, Node010, Notification: ValueChanged
2017-12-13 19:26:48.698 Detail, Node010,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x0a, 0x02, 0x84, 0x07, 0x78
2017-12-13 19:26:48.699 Detail,
2017-12-13 19:26:48.699 Info, Node010, Received Wakeup Notification from node 10
2017-12-13 19:26:48.699 Info, Node010,   Node 10 has been marked as awake
2017-12-13 19:26:48.699 Detail, Node010, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x84, 0x08, 0x25, 0x50, 0x14
2017-12-13 19:26:48.699 Detail, Node010, Notification: Notification - Node Awake
2017-12-13 19:26:48.734 Detail,
2017-12-13 19:26:48.734 Info, Node010, Sending (WakeUp) message (Callback ID=0x50, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x84, 0x08, 0x25, 0x50, 0x14
2017-12-13 19:26:48.747 Detail, Node010,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-13 19:26:48.747 Detail, Node010,   ZW_SEND_DATA delivered to Z-Wave stack
2017-12-13 19:26:48.762 Detail, Node010,   Received: 0x01, 0x07, 0x00, 0x13, 0x50, 0x00, 0x00, 0x03, 0xb8
2017-12-13 19:26:48.769 Detail, Node010,   ZW_SEND_DATA Request with callback ID 0x50 received (expected 0x50)
2017-12-13 19:26:48.769 Info, Node010, Request RTT 34 Average Request RTT 30
2017-12-13 19:26:48.769 Info, Node010,   Node 10 has been marked as asleep
2017-12-13 19:26:48.770 Detail,   Expected callbackId was received
2017-12-13 19:26:48.770 Detail,   Expected reply was received
2017-12-13 19:26:48.770 Detail,   Message transaction complete
2017-12-13 19:26:48.770 Detail,
2017-12-13 19:26:48.770 Detail, Node010, Removing current message
2017-12-13 19:26:48.770 Detail, Node010, Notification: Notification - Node Asleep

Thanks!

4

I misread your previous post using an event from the “OZW log”, I’m not sure if that’s even possible.

What is the event log for that device from the “home-assistant.log”?

You may have to set logger to info, if already set at a higher level, just to to see the log at the time you press the keypad.

5

So after everything loaded correctly from the keypad also in the dashboard, it seems that access control is a sensor.:
11

So this should make it relatively easy, correct?

6

Yes, you can use the attributes of the sensor to trigger your automation.