Got myself a Zipato RFID reader (same as Schlage/Benext) to be used by my cleaning lady. All my normal home/away/alarm functionality is driven by automations and mainly based on presence detection of phones & movement.
So the panel only needs to be used by people not part of the normal household but own a RFID tag from me.
Problem:
As such OZW supports this device but my issue is that this device (for some reason) does not seem to support setting it’s state by the controller. This means it can arm/disarm my alarm based on the tags but I cannot set the panel to arm/disarm by the controller.
This means there is a big risk the panel and my alarm modes get out of sync. And then the cleaning lady comes again after a few days, house mode is Away and alarm is also in away mode. She enters but a using her correct RFID tag will have no effect as the Panel is still in disarm mode (so no state change). With alarm still in away, alarm will sound…
Some ideas but no idea how to do:
So I would like to see when a correct RFID tag is used even if the panel is already in disarm mode. As you can see in below log dump, the device reports correctly that it is disarmed (again) by sending again Access Control event:6, status=255 .
Unfortunately I don’t know how to catch this ‘updated change’ (even tough the status is identical vs previous state). Does not even report a lastupdate
The issue is that this does not generate a state change in hass, also no change in the lastupdated (states.sensor.schlage_link_mini_keypad_rfid_access_control_29_9.last_updated).
Question:
Does anyone know how I can catch this in HASS?
2016-10-30 11:39:07.417 Detail, Node029, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1d, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x06, 0x01, 0x04, 0x72
2016-10-30 11:39:07.423 Detail,
2016-10-30 11:39:07.423 Info, Node029, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:6, status=255
2016-10-30 11:39:07.423 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2016-10-30 11:39:07.423 Detail, Node029, Changes to this value are not verified
2016-10-30 11:39:07.423 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2016-10-30 11:39:07.423 Detail, Node029, Changes to this value are not verified
2016-10-30 11:39:07.423 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2016-10-30 11:39:07.423 Detail, Node029, Changes to this value are not verified
2016-10-30 11:39:07.423 Detail, Node029, Refreshed Value: old value=6, new value=6, type=byte
2016-10-30 11:39:07.424 Detail, Node029, Changes to this value are not verified
2016-10-30 11:39:07.424 Detail, Node029, Notification: ValueChanged
2016-10-30 11:39:07.448 Detail, Node029, Notification: ValueChanged
2016-10-30 11:39:07.474 Detail, Node029, Notification: ValueChanged
2016-10-30 11:39:07.499 Detail, Node029, Notification: ValueChanged
2016-10-30 11:39:07.526 Detail, Node029, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x1d, 0x02, 0x84, 0x07, 0x6f
2016-10-30 11:39:07.527 Detail,
2016-10-30 11:39:07.527 Info, Node029, Received Wakeup Notification from node 29
2016-10-30 11:39:07.527 Info, Node029, Node 29 has been marked as awake
2016-10-30 11:39:07.527 Detail, Node029, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=29): 0x01, 0x09, 0x00, 0x13, 0x1d, 0x02, 0x84, 0x08, 0x25, 0x5a, 0x09
2016-10-30 11:39:07.527 Detail, Node029, Notification: Notification - Node Awake
2016-10-30 11:39:07.527 Detail,
2016-10-30 11:39:07.527 Info, Node029, Sending (WakeUp) message (Callback ID=0x5a, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=29): 0x01, 0x09, 0x00, 0x13, 0x1d, 0x02, 0x84, 0x08, 0x25, 0x5a, 0x09
2016-10-30 11:39:07.535 Detail, Node029, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-10-30 11:39:07.535 Detail, Node029, ZW_SEND_DATA delivered to Z-Wave stack
2016-10-30 11:39:07.614 Detail, Node029, Received: 0x01, 0x07, 0x00, 0x13, 0x5a, 0x00, 0x00, 0x08, 0xb9
2016-10-30 11:39:07.614 Detail, Node029, ZW_SEND_DATA Request with callback ID 0x5a received (expected 0x5a)
2016-10-30 11:39:07.614 Info, Node029, Request RTT 86 Average Request RTT 76
2016-10-30 11:39:07.614 Info, Node029, Node 29 has been marked as asleep
2016-10-30 11:39:07.614 Detail, Expected callbackId was received
2016-10-30 11:39:07.614 Detail, Expected reply was received
2016-10-30 11:39:07.614 Detail, Message transaction complete
2016-10-30 11:39:07.614 Detail,
2016-10-30 11:39:07.614 Detail, Node029, Removing current message
2016-10-30 11:39:07.614 Detail, Node029, Notification: Notification - Node Asleep