Be469 driver not logging some events


#1

I have an FE469 lock with be469 driver. Events are usually reported correctly in the events tab, but it seems some are missing. I’ve seen both digital and physical events but it happened that at least some physical were missing. I have a rule that warns me if I leave the door unlocked. The rule did fire correctly but there were no related events in the events tab.


#2

You think the driver isn't logging the events or the device isn't reporting them? If the driver is reporting that type of event at all, I would suspect the device before the driver. Do you have a strong signal where the device is? A repeater nearby?


#3

I had the same problem with the new be469 driver with both of my locks. Autolock and Manual Close events are not registered by the driver. I've switched back to Generic lock driver where both these events are registered normally.


#4

I would say that both of you would need to make sure the new driver gets configured properly as all 3 of mine work fine. The driver works perfectly.


#5

What do you mean by that?

Also I don't see any autolock and manual unlock events in your log. Did you try these particular events?


#6

That "digital" event is an autolock
That "physical" event is a manual unlock by keycode.

You need to have a separate tab open with the logs running when you hit the configure button on the device page, make sure the configure process completes and all 30 codes get "fetched"


#7

The lock is working and the driver too. most of the events do get logged. Sometimes, a few are missed in the log (but they are still infested by the system as associates rules do work)


#8

The "digital" event in your log is either a lock through driver page or Schlage button press lock event, but not the autolock I mean.
And the "physical" event I've decribed is not opening the lock by lock code, but physically turning the lock handle to open or close the lock.


These 3 events(manual opening/closing the lock handle and autolock(30 sec autolock configured in the lock itself) are not registered in the new custom driver for BE469 lock logs. I've checked the debug log for the new driver and it shows alarmv2.AlarmReport for these 3 events instead of DoorLockOperationReport for all other events(see below)

Can you try to generate these events and see if they are registered properly for you?

dev:11552019-06-13 15:00:19.045 debugparse: zw device: 3D, command: 9881, payload: 00 62 03 FF 00 00 FE FE , isMulticast: false

dev:11552019-06-13 14:56:44.151 warnskipped alarmType:0

dev:11552019-06-13 14:56:44.149 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:1, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-13 14:56:44.145 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 01 00 , isMulticast: false

dev:11552019-06-13 14:56:35.666 warnskipped alarmType:0

dev:11552019-06-13 14:56:35.665 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-13 14:56:35.656 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 02 00 , isMulticast: false

dev:11552019-06-13 14:55:39.548 warnskipped alarmType:0

dev:11552019-06-13 14:55:39.547 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:9, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-13 14:55:39.540 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 09 00 , isMulticast: false

dev:11552019-06-13 14:55:01.609 warnskipped alarmType:0

dev:11552019-06-13 14:55:01.607 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-13 14:55:01.502 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 02 00 , isMulticast: false

dev:11552019-06-13 14:50:53.936 warnskipped alarmType:0

dev:11552019-06-13 14:50:53.934 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:9, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-13 14:50:53.876 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 09 00 , isMulticast: false

dev:11552019-06-13 14:50:22.730 infoFront Door Lock was unlocked [digital]

dev:11552019-06-13 14:50:22.725 debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:0, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:0)

dev:11552019-06-13 14:50:22.719 debugparse: zw device: 3D, command: 9881, payload: 00 62 03 00 00 00 FE FE , isMulticast: false


#9

Bottom two entries are from "me manually turning the lock/unlock"
Middle entry is from using a key code
Top two entries are using the device page (also with RM) to lock/unlock

I do not use the "Lock's" built in auto-lock so that I cannot verify,...I don't want someone accidentally closing the door with the lock extended or the lock extending automatically in tne middle of closing the door.

Everything else is confirmed to report with the new driver.


#10

Ok, thanks. My BE469 locks are pretty old(one is 7 years old), so probably it is the old firmware problem. I'll continue to use generic driver which is working fine for me.


#11

If you can add the action that's associated with each of the skipped alarm types, I can add them to the driver.


#12

Could you please message @bobbyD or @patrick and let them know my hub is still down going on 15 hours now, and the last response I received was 5 hours ago.


#13

Mike,
I'm sorry, but I completely don't understand your comment.
I'd like to use the manual open/close events as a trigger or condition in RM, but the new Custom BE469 driver doesn't register these events for my locks for unknown reason, so I had to switch back to the generic zwave lock driver that does register these events.


#14

In the logs you posted there are several of the above entries.
Skipped here means this data from the lock didn't create an event in the driver.
If you can tell me which lock action triggered these, I can add the missing ones to the driver.


#15

Got you. Missing ones: Manual Unlock, Manual Lock and Autolock

Manual Unlock

Generic driver
dev:11552019-06-14 09:13:39.236 infoFront Door Lock was manually unlocked [physical][6:2]

dev:11552019-06-14 09:13:39.233 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-14 09:13:39.176 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 02 00 , isMulticast: false

Custom driver
dev:11552019-06-14 09:28:42.996 warnskipped alarmType:0

dev:11552019-06-14 09:28:42.991 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-14 09:28:42.703 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 02 00 , isMulticast: false

Manual Lock

Generic Driver
dev:11552019-06-14 09:13:56.238 infoFront Door Lock was manually locked [physical][6:1]

dev:11552019-06-14 09:13:56.236 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:1, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-14 09:13:56.229 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 01 00 , isMulticast: false

Custom Driver
dev:11552019-06-14 09:32:54.592 warnskipped alarmType:0

dev:11552019-06-14 09:32:54.590 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:1, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-14 09:32:54.578 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 01 00 , isMulticast: false

Autolock

Generic Driver
dev:11552019-06-14 09:12:07.177 infoFront Door Lock was autolocked[6:9]

dev:11552019-06-14 09:12:07.175 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:9, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-14 09:12:07.159 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 09 00 , isMulticast: false

Custom Driver
dev:11552019-06-14 09:29:13.818 warnskipped alarmType:0

dev:11552019-06-14 09:29:13.817 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:9, zwaveAlarmStatus:255, zwaveAlarmType:6)

dev:11552019-06-14 09:29:13.810 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 09 00 , isMulticast: false


#16

perfect, thanks!


#17

Having issues with my BE469's and trying to troubleshoot. I notice that both of them report "locked [digital]" for physically turning the deadbolt with the inside thumb wheel. =/


#18

Mike -

Just setup my Hub yesterday and I am having the same issues with the BE469 customer driver as aryvin. Logging shows all actions as skipped using custom driver. My logs for Manual Lock/Unlock are identical to aryvin's. As with his, the generic lock driver works where the custom one does not. Below are the log entries my additional skipped events not reflected in Aryvin's logs above.

Locking with Schlage Button:
dev:652019-06-26 01:36:09.969 pm warnskipped alarmType:0
dev:652019-06-26 01:36:09.965 pm debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:5, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:652019-06-26 01:36:09.935 pm debugparse: zw device: 03, command: 9881, payload: 00 71 05 00 00 00 FF 06 05 00 , isMulticast: false

Unlocked with User Code:
dev:652019-06-26 01:34:32.253 pm warnskipped alarmType:0
dev:652019-06-26 01:34:32.250 pm debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[4], numberOfEventParameters:1, zensorNetSourceNodeId:0, zwaveAlarmEvent:6, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:652019-06-26 01:34:32.233 pm debugparse: zw device: 03, command: 9881, payload: 00 71 05 00 00 00 FF 06 06 01 04 , isMulticast: false


#19

I had re-added my lock using the new driver (going by this process Sweet Jesus - do the new Schlage drivers make a difference or what?!) and I'm having what appears to be the same issue you are having. My initial troubleshooting seemed like it would simply skip some lock events. It will sometimes report my wife opening with her code but not me with my separate code an hour later, or manually opening the door at 8am but not 9am as other people left. Rule Machine automations I have based on changing status of the lock do not function any more, as the lock / unlock status doesn't appear to get reported. This will work when I set it up and test, but after any amount of time it fails to report correctly. That said, I hadn't done proper testing to confirm the patterns you are picking out here.

I will do that testing and report back. I'm hopeful the changes Mike appears to be making to the driver will fix us both up, though.


#20

these missing events should be fixed in release 2.1.2