bug: Kwikset 910 device file lacks associations/lifeline by default

Describe the bug

when i physically lock or unlock the 910 it appears to send zero notifications watching zwavejs_1.log with tail -f show no traffic occurring at all

Device information

Kwikset 910 NODE 003

Last Known Working Configuration

• unknown (think it worked years ago but can’t be sure my memory is accurate)

• New device

• Previously working device (node-zwave-js)

  • Which library version/docker image/adapter version?
  • Have you made any recent configuration changes to the device? Describe.

• Previously working device (other platform)

  • Which platform?
  • Have you made any recent configuration changes to the device? Describe.

Installation information How did you install node-zwave-js?

• zwavejs2mqtt (latest) docker image
• zwavejs2mqtt (dev) docker image
• ioBroker.zwave2 adapter
• Pkg
• Manual Docker build
  • node-zwave-js branch: master
  • zwavejs2mqtt branch: master
• Manually built (as described in the docs)
• Other:

To Reproduce Steps to reproduce the behavior:

1. restart container
2. wait for all interviews to complete
3. tail -f zwavejs_1.log at silly
4. re-interview node 003
5. check lock works by changing secured/unsecured
6. verify messages flow in log as expected
7. walk over to door and hand turn bolt OR use external keypad to change secure state
8. observe not a single thing is appended to the zwave log (this is where the log ends at step 5 as nothing came into log)

Additional context could this be related to https://github.com/zwave-js/node-zwave-js/issues/1764? is it possible for the device to send info that never comes up via the serial driver? is there easy way for me to see if same 0 traffic happens in simplicity studio - if that is useful / can be done then i am game for that.

I have tried multiple re-interviews and see no error in the interviews that i can spot.

App Version 1.1.1+94ff7ed.94ff7ed

Zwavejs Version 6.3.0-8f22052

Logfile: 910issue.log

[scyto]

The model I have is definitely not zwave plus if that helps.

[blhoward2]

Reopening this because we actually need to fix the issue. The device file doesn’t have association definitions and it appears these locks don’t auto-associate group 1 as a lifeline. I’m unclear that all models are zwave plus too.

I’ll update the device file to fix this.