search

FutureTense / keymaster

Home Assistant integration for managing Z-Wave enabled locks
MIT License
218 stars 44 forks source link

ISSUE: FE599 locks not notifying on events #281

Closed fireheadman closed 2 years ago

fireheadman commented 2 years ago

Describe the bug FE599 locks --> When locking/unlocking via code and/or manual, no notify events are being triggered and sent to mobile device. Works fine for BE649ZP locks

Environment (please complete the following information): image image

Logs Paste your error logs here.

Screenshots none available to show

fireheadman commented 2 years ago

have factory reset both FE599 locks, then erased all codes. excluded and re-included to HA.... even removed and reinstalled to keymaster. then programmed via HA using the lovelace card all new codes. These work to lock/unlock the door lock.

If I use the goto the scripts and manually trigger a lock reset, it will produce a notification to my device, so I know the scripts work.

The locks for whatever reason(s) are not triggering the scripts.

firstof9 commented 2 years ago

Make sure the lock's producing notifications first:

https://www.home-assistant.io/integrations/zwave_js/#node-events-notification

fireheadman commented 2 years ago

noticed I have a lot of these stacking up... image

image

image

firstof9 commented 2 years ago

No idea what that is.

fireheadman commented 2 years ago

its coming from keymaster attempting to send notifications out, but something is holding them up.... not sure how to make them release either, they are read only.

I just rebooted my host (not just a HA restart) and they are still there

firstof9 commented 2 years ago

My notifications show up where they should. image

fireheadman commented 2 years ago

agreed... but these are in the entities tab (search your entities for 'persistent'). I get them in that location also.

firstof9 commented 2 years ago

Nothing shows up.

fireheadman commented 2 years ago

might be a bit before I pick this up.... just applied the latest update for Z Wave that HA was broadcasting v0.1.59 and now my controller is no longer responding. https://community.home-assistant.io/t/z-wave-latest-version-0-1-59-controller-no-longer-works/424785

what a freaking day this is!... I need some beer fast

fireheadman commented 2 years ago

UPDATE: Looks like a few others were bit by this update, luckily I had an full backup from 12am, so performed a partial restore of this addon, so I'm 1 step forward --> 5 steps backwards at the moment.

fireheadman commented 2 years ago

Back on track from that detour... had to factory reset everything, flush keymaster, few system reboots. have all 3 locks working with codes.

BE649ZP (frontdoor) notifies perfect FE599 (garage and pantry locks) do not notify at all.

I'm able to test notifications by going to scripts and manually triggering the 'reset_lock' script... image

2022-05-24 18:18:01 INFO (MainThread) [homeassistant.components.script.keymaster_pantrydoor_reset_lock] keymaster_pantrydoor_reset_lock: Running script sequence
2022-05-24 18:18:01 INFO (MainThread) [homeassistant.components.script.keymaster_pantrydoor_reset_lock] keymaster_pantrydoor_reset_lock: Executing step call service
2022-05-24 18:18:01 INFO (MainThread) [homeassistant.components.script.keymaster_pantrydoor_manual_notify] keymaster: Pantry Door Manual Notify: Running script sequence
2022-05-24 18:18:01 INFO (MainThread) [homeassistant.components.script.keymaster_pantrydoor_manual_notify] keymaster: Pantry Door Manual Notify: Executing step call service

This will pop up on my phone (top alert) and others are from the front door testing. image

firstof9 commented 2 years ago

Make sure the lock is emitting notifications first:

https://www.home-assistant.io/integrations/zwave_js/#node-events-notification

fireheadman commented 2 years ago

@firstof9 was there a specific part of this document you are wanting to implement?

fireheadman commented 2 years ago

if possible, a quick bullet rundown of how to use this section of the UI, this would be my first time using events

fireheadman commented 2 years ago

This is all I get from that document, I'm willing to provide more content/output, but I need a little more guidance from you in order to understand this better....
image

fireheadman commented 2 years ago

as a side note, I brought in my alarm sensors for the door (front) and (garageinterior) and plugged them into keymaster. These triggered notifications to when the door was open/closed, but still nothing for when someone inputs a code and/or manually unlocks the FE599 locks.

**Had to disable the door open/close notification as it was randomly alerting the door was closed multiple times from the automation included in keymaster.

firstof9 commented 2 years ago

Do the "listen to events" then go lock/unlock your FE599, if you see no events, keymaster has nothing to pickup to relay on.

fireheadman commented 2 years ago

checking in to see if you had a few min to explain more on the "lock is emitting notifications first" and how to test this for you.

fireheadman commented 2 years ago

well that was easier than I expected... nice to know another part of HA. (THANKS!)

Only my BE649ZP fired zwave messages. Neither of my FE599 locks produced output (yet they work when entering codes programmed via keymaster)

What would be the next steps in troubleshooting this? image

fireheadman commented 2 years ago

Something to add on this... I have a GE wall wart/switch, this operates in S0 (same as the FE599 locks).... It also does not report on the events.

The BE649ZP is S2 and it reports.

I will have a upgrade wall switch to try this test on again, but my hunch is Z-WaveJS event listening is not setup to listen to S0 events (maybe because they spew in large amounts?)

firstof9 commented 2 years ago

I will have a upgrade wall switch to try this test on again, but my hunch is Z-WaveJS event listening is not setup to listen to S0 events (maybe because they spew in large amounts?)

No it doesn't work like that.

Next step is to monitor the ZwaveJS Log while you cycle a log and see what it's reporting.

fireheadman commented 2 years ago

Here is the output from me sending an LOCK function to the garageintdoor (FE599) from the UI


Subscribed to Z-Wave JS Log Messages…
2022-05-26T04:10:08.161Z SERIAL » 0x010900132502984025211e                                            (11 bytes)
2022-05-26T04:10:08.163Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      33
                                  └─[SecurityCCNonceGet]
2022-05-26T04:10:08.167Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:10:08.170Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:10:08.172Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:08.173Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:10:09.455Z SERIAL « 0x010500132100c8                                                     (7 bytes)
2022-05-26T04:10:09.456Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:09.457Z DRIVER « [REQ] [SendData]
                                    callback id:     33
                                    transmit status: OK
2022-05-26T04:10:09.466Z SERIAL « 0x0110000400250a9880d874da8cd97dcdc58a                              (18 bytes)
2022-05-26T04:10:09.469Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:09.470Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xd874da8cd97dcdc5
2022-05-26T04:10:09.476Z SERIAL » 0x011e001325179881c25953747d420cf09e095de8d8d1de0c7e6b9b43592522cc  (32 bytes)
2022-05-26T04:10:09.478Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      34
                                  └─[SecurityCCCommandEncapsulation]
                                    │ nonce id: 216
                                    └─[DoorLockCCOperationSet]
                                        target mode: Secured
2022-05-26T04:10:09.481Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:10:09.485Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:10:09.486Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:09.487Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:10:09.505Z SERIAL « 0x010500132200cb                                                     (7 bytes)
2022-05-26T04:10:09.506Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:09.507Z DRIVER « [REQ] [SendData]
                                    callback id:     34
                                    transmit status: OK
2022-05-26T04:10:09.565Z SERIAL « 0x0108000400250298400c                                              (10 bytes)
2022-05-26T04:10:09.566Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:09.569Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceGet]
2022-05-26T04:10:09.587Z SERIAL » 0x01110013250a9880ec0ede3981824da1052306                            (19 bytes)
2022-05-26T04:10:09.588Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x05
                                  │ callback id:      35
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xec0ede3981824da1
2022-05-26T04:10:09.593Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:10:09.595Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:10:09.596Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:09.597Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:10:09.612Z SERIAL « 0x010500132300ca                                                     (7 bytes)
2022-05-26T04:10:09.613Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:09.614Z DRIVER « [REQ] [SendData]
                                    callback id:     35
                                    transmit status: OK
2022-05-26T04:10:09.634Z SERIAL « 0x0121000400251b98810f4cb357a25a8ed0cad1ff5d62992a0aecac77d61473c9e (35 bytes)
                                  9edd5
2022-05-26T04:10:09.636Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:09.638Z CNTRLR   [Node 037] [~] [Door Lock] currentMode: 0 => 255                  [Endpoint 0]
2022-05-26T04:10:09.640Z CNTRLR   [Node 037] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2022-05-26T04:10:09.642Z CNTRLR   [Node 037] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2022-05-26T04:10:09.644Z CNTRLR   [Node 037] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
2022-05-26T04:10:09.645Z CNTRLR   [Node 037] [~] [Door Lock] boltStatus: "locked" => "locked"       [Endpoint 0]
2022-05-26T04:10:09.647Z CNTRLR   [Node 037] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
2022-05-26T04:10:09.649Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[DoorLockCCOperationReport]
                                        current mode:           Secured
                                        active outside handles: false, false, false, false
                                        active inside handles:  false, false, false, false
                                        latch status:           open
                                        bolt status:            locked
                                        door status:            open
2022-05-26T04:10:14.520Z SERIAL » 0x010900132502984025241b                                            (11 bytes)
2022-05-26T04:10:14.521Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      36
                                  └─[SecurityCCNonceGet]
2022-05-26T04:10:14.524Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:10:14.527Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:10:14.528Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:14.529Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:10:15.768Z SERIAL « 0x010500132400cd                                                     (7 bytes)
2022-05-26T04:10:15.769Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:15.770Z DRIVER « [REQ] [SendData]
                                    callback id:     36
                                    transmit status: OK
2022-05-26T04:10:15.779Z SERIAL « 0x0110000400250a9880d874da8cd97dcdc58a                              (18 bytes)
2022-05-26T04:10:15.780Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:15.782Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xd874da8cd97dcdc5
2022-05-26T04:10:15.793Z SERIAL » 0x011d00132516988135ec7db2ce088f3e5f4a57d835bc73a057531a30252554    (31 bytes)
2022-05-26T04:10:15.794Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      37
                                  └─[SecurityCCCommandEncapsulation]
                                    │ nonce id: 216
                                    └─[DoorLockCCOperationGet]
2022-05-26T04:10:15.797Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:10:15.801Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:10:15.802Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:15.804Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:10:15.821Z SERIAL « 0x010500132500cc                                                     (7 bytes)
2022-05-26T04:10:15.822Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:15.824Z DRIVER « [REQ] [SendData]
                                    callback id:     37
                                    transmit status: OK
2022-05-26T04:10:15.845Z SERIAL « 0x0108000400250298400c                                              (10 bytes)
2022-05-26T04:10:15.846Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:15.848Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceGet]
2022-05-26T04:10:15.859Z SERIAL » 0x01110013250a9880b13fe2fe1f8b034a0526a6                            (19 bytes)
2022-05-26T04:10:15.860Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x05
                                  │ callback id:      38
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xb13fe2fe1f8b034a
2022-05-26T04:10:15.863Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:10:15.866Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:10:15.867Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:15.868Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:10:15.883Z SERIAL « 0x010500132600cf                                                     (7 bytes)
2022-05-26T04:10:15.884Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:15.886Z DRIVER « [REQ] [SendData]
                                    callback id:     38
                                    transmit status: OK
2022-05-26T04:10:15.907Z SERIAL « 0x0121000400251b98810f4cb357a25a8ed0bd9dea13298993bbb1145f16eeeeb24 (35 bytes)
                                  c912e
2022-05-26T04:10:15.908Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:10:15.910Z CNTRLR   [Node 037] [~] [Door Lock] currentMode: 255 => 255                [Endpoint 0]
2022-05-26T04:10:15.911Z CNTRLR   [Node 037] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2022-05-26T04:10:15.912Z CNTRLR   [Node 037] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2022-05-26T04:10:15.914Z CNTRLR   [Node 037] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
2022-05-26T04:10:15.915Z CNTRLR   [Node 037] [~] [Door Lock] boltStatus: "locked" => "locked"       [Endpoint 0]
2022-05-26T04:10:15.916Z CNTRLR   [Node 037] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
2022-05-26T04:10:15.917Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[DoorLockCCOperationReport]
                                        current mode:           Secured
                                        active outside handles: false, false, false, false
                                        active inside handles:  false, false, false, false
                                        latch status:           open
                                        bolt status:            locked
                                        door status:            open
fireheadman commented 2 years ago

and this is an UNLOCK function (to complete the cycle request)


Subscribed to Z-Wave JS Log Messages…
2022-05-26T04:14:22.152Z SERIAL » 0x0109001325029840252718                                            (11 bytes)
2022-05-26T04:14:22.153Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      39
                                  └─[SecurityCCNonceGet]
2022-05-26T04:14:22.155Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:14:22.159Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:14:22.160Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:22.161Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:14:23.400Z SERIAL « 0x010500132700ce                                                     (7 bytes)
2022-05-26T04:14:23.402Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:23.404Z DRIVER « [REQ] [SendData]
                                    callback id:     39
                                    transmit status: OK
2022-05-26T04:14:23.412Z SERIAL « 0x0110000400250a9880d874da8cd97dcdc58a                              (18 bytes)
2022-05-26T04:14:23.414Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:23.415Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xd874da8cd97dcdc5
2022-05-26T04:14:23.422Z SERIAL » 0x011e001325179881e8aaaf6cccb205faa3110db4d86712b5cfb96147ca25285d  (32 bytes)
2022-05-26T04:14:23.423Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      40
                                  └─[SecurityCCCommandEncapsulation]
                                    │ nonce id: 216
                                    └─[DoorLockCCOperationSet]
                                        target mode: Unsecured
2022-05-26T04:14:23.426Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:14:23.431Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:14:23.431Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:23.433Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:14:23.451Z SERIAL « 0x010500132800c1                                                     (7 bytes)
2022-05-26T04:14:23.452Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:23.453Z DRIVER « [REQ] [SendData]
                                    callback id:     40
                                    transmit status: OK
2022-05-26T04:14:23.510Z SERIAL « 0x0108000400250298400c                                              (10 bytes)
2022-05-26T04:14:23.512Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:23.513Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceGet]
2022-05-26T04:14:23.523Z SERIAL » 0x01110013250a9880ac5ddb5112e5a648052984                            (19 bytes)
2022-05-26T04:14:23.524Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x05
                                  │ callback id:      41
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xac5ddb5112e5a648
2022-05-26T04:14:23.527Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:14:23.530Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:14:23.531Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:23.532Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:14:23.547Z SERIAL « 0x010500132900c0                                                     (7 bytes)
2022-05-26T04:14:23.548Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:23.550Z DRIVER « [REQ] [SendData]
                                    callback id:     41
                                    transmit status: OK
2022-05-26T04:14:23.569Z SERIAL « 0x0121000400251b98810f4cb357a25a8ed007f15ef3282d7f37ac9a7617d5d3adb (35 bytes)
                                  745e4
2022-05-26T04:14:23.571Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:23.573Z CNTRLR   [Node 037] [~] [Door Lock] currentMode: 255 => 0                  [Endpoint 0]
2022-05-26T04:14:23.574Z CNTRLR   [Node 037] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2022-05-26T04:14:23.576Z CNTRLR   [Node 037] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2022-05-26T04:14:23.577Z CNTRLR   [Node 037] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
2022-05-26T04:14:23.579Z CNTRLR   [Node 037] [~] [Door Lock] boltStatus: "locked" => "locked"       [Endpoint 0]
2022-05-26T04:14:23.580Z CNTRLR   [Node 037] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
2022-05-26T04:14:23.582Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[DoorLockCCOperationReport]
                                        current mode:           Unsecured
                                        active outside handles: false, false, false, false
                                        active inside handles:  false, false, false, false
                                        latch status:           open
                                        bolt status:            locked
                                        door status:            open
2022-05-26T04:14:28.465Z SERIAL » 0x0109001325029840252a15                                            (11 bytes)
2022-05-26T04:14:28.466Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      42
                                  └─[SecurityCCNonceGet]
2022-05-26T04:14:28.468Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:14:28.472Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:14:28.473Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:28.474Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:14:29.758Z SERIAL « 0x010500132a00c3                                                     (7 bytes)
2022-05-26T04:14:29.759Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:29.761Z DRIVER « [REQ] [SendData]
                                    callback id:     42
                                    transmit status: OK
2022-05-26T04:14:29.770Z SERIAL « 0x0110000400250a9880d874da8cd97dcdc58a                              (18 bytes)
2022-05-26T04:14:29.771Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:29.772Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xd874da8cd97dcdc5
2022-05-26T04:14:29.779Z SERIAL » 0x011d0013251698816c71602dc8f003aabd4b08d8a29de077aa386944252b25    (31 bytes)
2022-05-26T04:14:29.780Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      43
                                  └─[SecurityCCCommandEncapsulation]
                                    │ nonce id: 216
                                    └─[DoorLockCCOperationGet]
2022-05-26T04:14:29.793Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:14:29.795Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:14:29.796Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:29.797Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:14:29.807Z SERIAL « 0x010500132b00c2                                                     (7 bytes)
2022-05-26T04:14:29.809Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:29.810Z DRIVER « [REQ] [SendData]
                                    callback id:     43
                                    transmit status: OK
2022-05-26T04:14:29.831Z SERIAL « 0x0108000400250298400c                                              (10 bytes)
2022-05-26T04:14:29.832Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:29.834Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceGet]
2022-05-26T04:14:29.848Z SERIAL » 0x01110013250a9880d51fc2a89476ed91052cdd                            (19 bytes)
2022-05-26T04:14:29.849Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x05
                                  │ callback id:      44
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xd51fc2a89476ed91
2022-05-26T04:14:29.851Z SERIAL « [ACK]                                                                   (0x06)
2022-05-26T04:14:29.855Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-26T04:14:29.856Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:29.857Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-26T04:14:29.872Z SERIAL « 0x010500132c00c5                                                     (7 bytes)
2022-05-26T04:14:29.873Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:29.875Z DRIVER « [REQ] [SendData]
                                    callback id:     44
                                    transmit status: OK
2022-05-26T04:14:29.895Z SERIAL « 0x0121000400251b98810f4cb357a25a8ed0016555d2634c2babd55bfa68b3ca0a9 (35 bytes)
                                  7145c
2022-05-26T04:14:29.896Z SERIAL » [ACK]                                                                   (0x06)
2022-05-26T04:14:29.897Z CNTRLR   [Node 037] [~] [Door Lock] currentMode: 0 => 0                    [Endpoint 0]
2022-05-26T04:14:29.898Z CNTRLR   [Node 037] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2022-05-26T04:14:29.900Z CNTRLR   [Node 037] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2022-05-26T04:14:29.901Z CNTRLR   [Node 037] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
2022-05-26T04:14:29.902Z CNTRLR   [Node 037] [~] [Door Lock] boltStatus: "locked" => "locked"       [Endpoint 0]
2022-05-26T04:14:29.903Z CNTRLR   [Node 037] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
2022-05-26T04:14:29.904Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[DoorLockCCOperationReport]
                                        current mode:           Unsecured
                                        active outside handles: false, false, false, false
                                        active inside handles:  false, false, false, false
                                        latch status:           open
                                        bolt status:            locked
                                        door status:            open
fireheadman commented 2 years ago

lock producing this info image

firstof9 commented 2 years ago

Almost seems like the notification command class may be missing. Press the download diagnostics button on the device screen and drag and drop the file into a reply.

fireheadman commented 2 years ago

zwave_js-ddaa05708f2bd81ebc568bae422128e9-Connected Keypad with Lever-19d90ac1c622d3b9691a77ca3ef8454c.json.txt

firstof9 commented 2 years ago

Do you have the alarmType and alarmLevel sensors showing up under that +2 entities not shown under Sensors?

fireheadman commented 2 years ago

image

Yes, but by default they are disabled.

fireheadman commented 2 years ago

image

image

firstof9 commented 2 years ago

Go ahead and enable them and select them in the keymaster config. ZwaveJS must not have an alarm mapping setup for this lock.

fireheadman commented 2 years ago

ok those are enabled... image

....and selected in the config image

doing a quick restart as Slot 4 has now started acting up (showing Adding...) for the garageintdoor .

fireheadman commented 2 years ago

all slots are now connected.... went to garageintdoor and manually unlocked/locked it, also entered a code. nothing is sent for a notification after enabling the 2 sensors.

anything else that could be tried? do you know of anyone using the FE599 and getting alerts/notifications?

firstof9 commented 2 years ago

Can you confirm those sensor values are changing?

fireheadman commented 2 years ago

yes they appear to be changing.... or one of them did. From 1 to 3. image

fireheadman commented 2 years ago

image image

firstof9 commented 2 years ago

Does the alarmType change when you manually lock/unlock and lock/unlock from inside HA?

fireheadman commented 2 years ago

it does not. I have rebooted a few times... alarmLevel is now 2 alarmType is 16

unsure what caused it to change from 3 to 2

firstof9 commented 2 years ago

Normally that would be the userCode slot that unlocked the door via the keypad.

firstof9 commented 2 years ago

At this point I'm leaning towards an issue with the lock itself, in regards to the notifications. The issue is beyond the scope of the keymaster integration.

fireheadman commented 2 years ago

So you think that I have two defective locks that are brand-new? Pantry Lock Garage lock Both are Fe599

firstof9 commented 2 years ago

Firmware wise, it's possible, but again, not really in the scope of keymaster.

fireheadman commented 2 years ago

I suppose we stick a pin in this until others experience the same thing. Thanks for showing me a few new things.

fireheadman commented 2 years ago

I have a 3rd FE599 coming to me tomorrow, curious to see if it behaves the same. Would be highly coincidental for three in a row to act the same.

firstof9 commented 2 years ago

You could always watch the zwavejs logs as well, set to silly or debug level and toggle one of the locks and see what the driver's seeing.

fireheadman commented 2 years ago

So added the 3rd NEW Schlage FE599 lock this morning. I'm willing to put all my $$$$ on this that I do not have 3 defective locks.

I'm not saying keymaster is at fault, perhaps something in the Z-WaveJS server is not acknowledging the signals being sent from the lock to the server? I'm not sure where to continue on this venture to get help. I'm also willing to bet other users out there with FE599 locks will experience the same thing..... so much so, I would have no issues going to HD/Lowes and buying x10 more of these locks and pair all of them to prove all x10 locks will not send out notifications.

As a side note, getting a notification is a "minor" detail for me (it would be nice to have).... so in the meantime, we will make due with the functinons that keymaster is proving today and leave it at that.

Welcome to close this as "unresolved". Maybe someone else will come across this and pick up the torch.

firstof9 commented 2 years ago

Like I said you'd have to check the driver log from zwavejs to know for sure.

fireheadman commented 2 years ago

that is something I will need to learn more about, guessing that is on the host system instead of the docker container running Hassio

firstof9 commented 2 years ago

In HA go to Settings (the cog icon) -> Devices & Services -> Configure on ZwaveJS Click the Logs tab at the top. Keep that screen up and go cycle a lock, this will be the driver logs from zwavejs.

image image image

fireheadman commented 2 years ago

FE599 Logs

Subscribed to Z-Wave JS Log Messages…
2022-05-27T17:15:27.069Z SERIAL « 0x0108000400250298400c                                              (10 bytes)
2022-05-27T17:15:27.071Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:27.072Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceGet]
2022-05-27T17:15:27.080Z SERIAL » 0x01110013250a98800e04fe478a88d10605c66f                            (19 bytes)
2022-05-27T17:15:27.081Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x05
                                  │ callback id:      198
                                  └─[SecurityCCNonceReport]
                                      nonce: 0x0e04fe478a88d106
2022-05-27T17:15:27.084Z SERIAL « [ACK]                                                                   (0x06)
2022-05-27T17:15:27.087Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-27T17:15:27.088Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:27.089Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-27T17:15:27.113Z SERIAL « 0x01050013c6002f                                                     (7 bytes)
2022-05-27T17:15:27.114Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:27.115Z DRIVER « [REQ] [SendData]
                                    callback id:     198
                                    transmit status: OK
2022-05-27T17:15:27.133Z SERIAL « 0x011e000400251898810f4cb357a25a8ed071dd54bc410ee7da2509c24c9e15df  (32 bytes)
2022-05-27T17:15:27.135Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:27.136Z CNTRLR   [Node 037] [~] [Notification] alarmType: 16 => 16                 [Endpoint 0]
2022-05-27T17:15:27.137Z CNTRLR   [Node 037] [~] [Notification] alarmLevel: 3 => 1                  [Endpoint 0]
2022-05-27T17:15:27.138Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[NotificationCCReport]
                                        V1 alarm type:  16
                                        V1 alarm level: 1
2022-05-27T17:15:34.211Z SERIAL « 0x0108000400250298400c                                              (10 bytes)
2022-05-27T17:15:34.212Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:34.213Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceGet]
2022-05-27T17:15:34.222Z SERIAL » 0x01110013250a9880d415c2539dee365005c74d                            (19 bytes)
2022-05-27T17:15:34.224Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x05
                                  │ callback id:      199
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xd415c2539dee3650
2022-05-27T17:15:34.226Z SERIAL « [ACK]                                                                   (0x06)
2022-05-27T17:15:34.230Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-27T17:15:34.231Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:34.232Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-27T17:15:34.254Z SERIAL « 0x01050013c7002e                                                     (7 bytes)
2022-05-27T17:15:34.255Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:34.257Z DRIVER « [REQ] [SendData]
                                    callback id:     199
                                    transmit status: OK
2022-05-27T17:15:34.276Z SERIAL « 0x0121000400251b98810f4cb357a25a8ed06ae871cae14693eed47f4320b009d63 (35 bytes)
                                  dfa7f
2022-05-27T17:15:34.278Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:34.280Z CNTRLR   [Node 037] [~] [Door Lock] currentMode: 0 => 255                  [Endpoint 0]
2022-05-27T17:15:34.281Z CNTRLR   [Node 037] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2022-05-27T17:15:34.283Z CNTRLR   [Node 037] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2022-05-27T17:15:34.284Z CNTRLR   [Node 037] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
2022-05-27T17:15:34.285Z CNTRLR   [Node 037] [~] [Door Lock] boltStatus: "locked" => "locked"       [Endpoint 0]
2022-05-27T17:15:34.286Z CNTRLR   [Node 037] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
2022-05-27T17:15:34.287Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[DoorLockCCOperationReport]
                                        current mode:           Secured
                                        active outside handles: false, false, false, false
                                        active inside handles:  false, false, false, false
                                        latch status:           open
                                        bolt status:            locked
                                        door status:            open
2022-05-27T17:15:38.404Z SERIAL « 0x0108000400250298400c                                              (10 bytes)
2022-05-27T17:15:38.405Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:38.407Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceGet]
2022-05-27T17:15:38.414Z SERIAL » 0x01110013250a9880b5fb6b64606940c005c8cf                            (19 bytes)
2022-05-27T17:15:38.415Z DRIVER » [Node 037] [REQ] [SendData]
                                  │ transmit options: 0x05
                                  │ callback id:      200
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xb5fb6b64606940c0
2022-05-27T17:15:38.418Z SERIAL « [ACK]                                                                   (0x06)
2022-05-27T17:15:38.421Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-27T17:15:38.422Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:38.424Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-27T17:15:38.448Z SERIAL « 0x01050013c80021                                                     (7 bytes)
2022-05-27T17:15:38.449Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:38.450Z DRIVER « [REQ] [SendData]
                                    callback id:     200
                                    transmit status: OK
2022-05-27T17:15:38.470Z SERIAL « 0x011e000400251898810f4cb357a25a8ed0e814ecd432b509a2c5609370426448  (32 bytes)
2022-05-27T17:15:38.471Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:15:38.473Z CNTRLR   [Node 037] [~] [Notification] alarmType: 16 => 16                 [Endpoint 0]
2022-05-27T17:15:38.474Z CNTRLR   [Node 037] [~] [Notification] alarmLevel: 1 => 1                  [Endpoint 0]
2022-05-27T17:15:38.476Z DRIVER « [Node 037] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[NotificationCCReport]
                                        V1 alarm type:  16
                                        V1 alarm level: 1
fireheadman commented 2 years ago

that was on Silly since Debug doesn't provided everything.