search

FutureTense / keymaster

Home Assistant integration for managing Z-Wave enabled locks
MIT License
231 stars 43 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

and this is to compare against a BE649ZP

Subscribed to Z-Wave JS Log Messages…
2022-05-27T17:18:15.916Z SERIAL « 0x011d0004002b179f03a8003d929d9d2bfa7c39cd4e8afd5f6a19d18cf26dcf    (31 bytes)
2022-05-27T17:18:15.924Z CNTRLR   [Node 043] [~] [Door Lock] currentMode: 0 => 255                  [Endpoint 0]
2022-05-27T17:18:15.925Z CNTRLR   [Node 043] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2022-05-27T17:18:15.926Z CNTRLR   [Node 043] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2022-05-27T17:18:15.927Z CNTRLR   [Node 043] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
2022-05-27T17:18:15.928Z CNTRLR   [Node 043] [~] [Door Lock] boltStatus: "unlocked" => "locked"     [Endpoint 0]
2022-05-27T17:18:15.929Z CNTRLR   [Node 043] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
2022-05-27T17:18:15.930Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:15.932Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 168
                                    └─[SupervisionCCGet]
                                      │ session id:      10
                                      │ request updates: 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:18:15.945Z SERIAL » 0x011800132b119f03d40092c31fd6c0994948664635bf0525c905              (26 bytes)
2022-05-27T17:18:15.947Z DRIVER » [Node 043] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      201
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 212
                                    └─[SupervisionCCReport]
                                        session id:          10
                                        more updates follow: false
                                        status:              Success
                                        duration:            0s
2022-05-27T17:18:15.949Z SERIAL « [ACK]                                                                   (0x06)
2022-05-27T17:18:15.953Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-27T17:18:15.954Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:15.955Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-27T17:18:15.975Z SERIAL « 0x01050013c90020                                                     (7 bytes)
2022-05-27T17:18:15.976Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:15.977Z DRIVER « [REQ] [SendData]
                                    callback id:     201
                                    transmit status: OK
2022-05-27T17:18:16.085Z SERIAL « 0x01200004002b1a9f03a9002520d8817e1f2acc009fda769f1a3fae791b61c5914 (34 bytes)
                                  83c
2022-05-27T17:18:16.089Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:16.091Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 169
                                    └─[SupervisionCCGet]
                                      │ session id:      11
                                      │ request updates: false
                                      └─[NotificationCCReport]
                                          notification type:   Access Control
                                          notification status: 255
                                          notification event:  Keypad lock operation
                                          event parameters:
                                            userId: 0x01
2022-05-27T17:18:16.094Z CNTRLR   [Node 043] [~] [Door Lock] currentMode: 255 => 255                [Endpoint 0]
2022-05-27T17:18:16.106Z SERIAL » 0x011800132b119f03d500b30073c91c8a3cf7a0d4d0c19a25cac3              (26 bytes)
2022-05-27T17:18:16.108Z DRIVER » [Node 043] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      202
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 213
                                    └─[SupervisionCCReport]
                                        session id:          11
                                        more updates follow: false
                                        status:              Success
                                        duration:            0s
2022-05-27T17:18:16.110Z SERIAL « [ACK]                                                                   (0x06)
2022-05-27T17:18:16.114Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-27T17:18:16.115Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:16.116Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-27T17:18:16.201Z SERIAL « 0x01050013ca0023                                                     (7 bytes)
2022-05-27T17:18:16.202Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:16.203Z DRIVER « [REQ] [SendData]
                                    callback id:     202
                                    transmit status: OK
2022-05-27T17:18:21.781Z SERIAL « 0x011d0004002b179f03aa00c4eb196fee56f4d0bdc9fb1c33a6ee6cf7852ef1    (31 bytes)
2022-05-27T17:18:21.784Z CNTRLR   [Node 043] [~] [Door Lock] currentMode: 255 => 0                  [Endpoint 0]
2022-05-27T17:18:21.785Z CNTRLR   [Node 043] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2022-05-27T17:18:21.786Z CNTRLR   [Node 043] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2022-05-27T17:18:21.787Z CNTRLR   [Node 043] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
2022-05-27T17:18:21.788Z CNTRLR   [Node 043] [~] [Door Lock] boltStatus: "locked" => "unlocked"     [Endpoint 0]
2022-05-27T17:18:21.789Z CNTRLR   [Node 043] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
2022-05-27T17:18:21.790Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:21.792Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 170
                                    └─[SupervisionCCGet]
                                      │ session id:      12
                                      │ request updates: false
                                      └─[DoorLockCCOperationReport]
                                          current mode:           Unsecured
                                          active outside handles: false, false, false, false
                                          active inside handles:  false, false, false, false
                                          latch status:           open
                                          bolt status:            unlocked
                                          door status:            open
2022-05-27T17:18:21.809Z SERIAL » 0x011800132b119f03d600e36708ec342eaebb7342a2fa3b25cb57              (26 bytes)
2022-05-27T17:18:21.811Z DRIVER » [Node 043] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      203
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 214
                                    └─[SupervisionCCReport]
                                        session id:          12
                                        more updates follow: false
                                        status:              Success
                                        duration:            0s
2022-05-27T17:18:21.813Z SERIAL « [ACK]                                                                   (0x06)
2022-05-27T17:18:21.818Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-27T17:18:21.819Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:21.820Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-27T17:18:21.840Z SERIAL « 0x01050013cb0022                                                     (7 bytes)
2022-05-27T17:18:21.840Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:21.841Z DRIVER « [REQ] [SendData]
                                    callback id:     203
                                    transmit status: OK
2022-05-27T17:18:21.947Z SERIAL « 0x01200004002b1a9f03ab00cb7262ce0b961aea7cc57f220ca98e4afacd4f4da2a (34 bytes)
                                  b1c
2022-05-27T17:18:21.950Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:21.951Z DRIVER « [Node 043] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 171
                                    └─[SupervisionCCGet]
                                      │ session id:      13
                                      │ request updates: false
                                      └─[NotificationCCReport]
                                          notification type:   Access Control
                                          notification status: 255
                                          notification event:  Keypad unlock operation
                                          event parameters:
                                            userId: 0x01
2022-05-27T17:18:21.954Z CNTRLR   [Node 043] [~] [Door Lock] currentMode: 0 => 0                    [Endpoint 0]
2022-05-27T17:18:21.965Z SERIAL » 0x011800132b119f03d7003c5b6bdec9de3dd5546c532f2a25cc2f              (26 bytes)
2022-05-27T17:18:21.966Z DRIVER » [Node 043] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      204
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 215
                                    └─[SupervisionCCReport]
                                        session id:          13
                                        more updates follow: false
                                        status:              Success
                                        duration:            0s
2022-05-27T17:18:21.969Z SERIAL « [ACK]                                                                   (0x06)
2022-05-27T17:18:21.973Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-05-27T17:18:21.974Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:21.975Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-05-27T17:18:22.077Z SERIAL « 0x01050013cc0025                                                     (7 bytes)
2022-05-27T17:18:22.078Z SERIAL » [ACK]                                                                   (0x06)
2022-05-27T17:18:22.080Z DRIVER « [REQ] [SendData]
                                    callback id:     204
                                    transmit status: OK
firstof9 commented 2 years ago

2022-05-27T17:15:38.476Z DRIVER « [Node 037] [REQ] [ApplicationCommand] └─[SecurityCCCommandEncapsulation] │ sequenced: false └─[NotificationCCReport] V1 alarm type: 16 V1 alarm level: 1

The notifications seem to be coming thru, but are not translated, so only the sensors update. Is this from physically manipulating the lock or via the lock/unlock in HA?

firstof9 commented 2 years ago

Did some digging, found this table of alarm codes for your lock:

image

I'll double check with zwavejs to see if the mappings are there and if not get them added so your notifications work as expected.

Based on this alarmType 16 = User Access, and the alarmLevel would be which userCode was used.

fireheadman commented 2 years ago

if that comes back with something positive, sounds like we would just need to 'enable' those 2 entities when using keymaster. crossing my fingers for you and thanks!

firstof9 commented 2 years ago

Nah if the mapping's missing, this will have zwavejs send the notifications like the other locks, and it will just start working in keymaster.

firstof9 commented 2 years ago

Oh boy, this looks like it's gonna be a pickle, these alarm codes your lock produces matches nothing with normal notifications. I'll see about a work around in keymaster at this point.

fireheadman commented 2 years ago

how many beers you need for this?

btw, I just got my S2 Z-Wave Repeater installed... so one less S0 device to worry about.

firstof9 commented 2 years ago

None of your devices outside of your locks should be using S0, and even then I usually recommend S2 locks :stuck_out_tongue_closed_eyes:

kbarnes3 commented 2 years ago

I updated to Keymaster v0.0.80 today which has the fix for this issue. Going through the issue, I enabled the sensors for alarm level and alarm type for my FE599 lock as well. I can see these sensors change appropriately based on the lock code that is entered. I also updated the Keymaster configuration to point to these sensors:

image

However, my notification script is still not firing when codes are used that have notifications enabled.

I do have all of this working with another lock in Keymaster, so hopefully I haven't made any dumb mistakes here, but I can't rule it out.

Is there any extra steps I need to take upon update to get a FE599 lock to work?

firstof9 commented 2 years ago

For some reason the event doesn't fire for these locks, I don't know why at this time.