Issue with Inclusion for Ring Keypad v2

[bugs181]

Thanks

I believe this is the ONLY resource I've found on the internet about using the Ring keypad outside of the Ring app/ecosystem. For that, I'm very much thankful. I've been a Ring user for a few years now and have been patiently waiting for someone to bring this beautiful keypad into Homeassistant without the Ring cloud services.

Setup / Hardware

My setup is a little complex, so I'll try to be brief and if you need any other info to help diagnose the issue, please let me know.

For the hardware, I'm using an Aeotec Z-Stick Gen5 Plus (ZW090-A) from Amazon. I have the z-wave stick connected to Home Assistant remotely using zwave-js-server where the device is located. In Home Assistant I'm using the Z-WaveJS integration (Not the ZWavetoMQTT project). The integration does not use the supervisor addon and asks the websocket address to connect to remotely.

Issue

The issue I'm having is getting the keypad included properly.

I've tried both classic Inclusion and Smart Inclusion via the QR code. With Smart Inclusion, the device eventually gets added but with a notice that the device was added insecurely. There are no keypad events coming through the zwave-js server logs and nothing on Lovelace (probably because this keypad won't work without S2).

The notice is as follows:

The device was added insecurely
There was an error during secure inclusion. You can try again by excluding the device and adding it again.

Inclusion

DURING inclusion, I'm seeing a lot of timeouts during the interview process.

They are as follows (trimmed for brevity):

21:48:44.495 CNTRLR   Smart Start listening mode enabled
21:49:53.934 CNTRLR   Starting inclusion process with strategy Default...
21:49:53.945 CNTRLR   The controller is now ready to add nodes
21:50:09.857 CNTRLR   handling add node request (status = NodeFound)
21:50:10.045 CNTRLR   handling add node request (status = AddingSlave)
21:50:17.365 CNTRLR   handling add node request (status = ProtocolDone)
21:50:17.365 CNTRLR   finishing inclusion process...
21:50:17.438 CNTRLR   The inclusion process was stopped
21:50:17.438 CNTRLR   finished adding node 32:
                        basic device class:    Routing Slave
                        generic device class:  Entry Control
                        specific device class: Secure Keypad
                        supported CCs: 
                        · Entry Control (0x6f)
                        · Manufacturer Specific (0x72)
                        · Version (0x86)
                        · Z-Wave Plus Info (0x5e)
                        · Security (0x98)
                        · Security 2 (0x9f)
                        · Supervision (0x6c)
                        · Transport Service (0x55)
                        controlled CCs: 
21:50:17.439 CNTRLR » [Node 032] Assigning SUC return route...
21:50:17.722 CNTRLR   [Node 032] Cannot configure Z-Wave+ Lifeline association: Node does not suppor
                      t associations...
21:50:17.722 CNTRLR   [Node 032] Beginning interview - last completed stage: None
21:50:17.723 CNTRLR   [Node 032] new node, doing a full interview...
21:50:17.723 CNTRLR » [Node 032] querying protocol info...
21:50:17.726 CNTRLR   Enabling Smart Start listening mode...
21:50:17.737 CNTRLR « [Node 032] received response for protocol info:
                      basic device class:    Routing Slave
                      generic device class:  Entry Control
                      specific device class: Secure Keypad
                      node type:             Routing End Node
                      is always listening:   false
                      is frequent listening: 250ms
                      can route messages:    true
                      supports security:     false
                      supports beaming:      true
                      maximum data rate:     100000 kbps
                      protocol version:      3
21:50:17.744 CNTRLR   Smart Start listening mode enabled
21:50:17.745 CNTRLR   [Node 032] Interview stage completed: ProtocolInfo
21:50:17.745 CNTRLR » [Node 032] querying node info...
21:50:17.797 CNTRLR « [Node 032] node info received
                      supported CCs:
                      · Z-Wave Plus Info
                      · Security
                      · Security 2
                      · Supervision
                      · Transport Service
                      controlled CCs:
21:50:17.797 CNTRLR   [Node 032] Interview stage completed: NodeInfo
21:50:17.797 CNTRLR   [Node 032] Interviewing Manufacturer Specific...
21:50:17.797 CNTRLR » [Node 032] querying manufacturer information...
21:50:27.833 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:50:27.834 CNTRLR   [Node 032] Interviewing Version...
21:50:27.834 CNTRLR » [Node 032]   querying the CC version for Version...
21:50:37.871 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:50:37.871 CNTRLR   [Node 032] CC version query for Version timed out - assuming the node supports
                       version 1...
21:50:37.871 CNTRLR » [Node 032] querying node versions...
21:50:47.906 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:50:47.906 CNTRLR » [Node 032] querying CC versions...
21:50:47.906 CNTRLR   [Node 032]   skipping query for Entry Control (0x6f) because max implemented v
                      ersion is 1
21:50:47.906 CNTRLR » [Node 032]   querying the CC version for Manufacturer Specific...
21:50:57.941 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:50:57.942 CNTRLR   [Node 032] CC version query for Manufacturer Specific timed out - assuming the
                       node supports version 1...
21:50:57.942 CNTRLR » [Node 032]   querying the CC version for Z-Wave Plus Info...
21:51:07.981 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:51:07.981 CNTRLR   [Node 032] CC version query for Z-Wave Plus Info timed out - assuming the node
                       supports version 1...
21:51:07.981 CNTRLR   [Node 032]   skipping query for Security (0x98) because max implemented versio
                      n is 1
21:51:07.982 CNTRLR   [Node 032]   skipping query for Security 2 (0x9f) because max implemented vers
                      ion is 1
21:51:07.982 CNTRLR » [Node 032]   querying the CC version for Supervision...
21:51:18.019 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:51:18.020 CNTRLR   [Node 032] CC version query for Supervision timed out - assuming the node supp
                      orts version 1...
21:51:18.020 CNTRLR » [Node 032]   querying the CC version for Transport Service...
21:51:28.058 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:51:28.058 CNTRLR   [Node 032] CC version query for Transport Service timed out - assuming the nod
                      e supports version 1...
21:51:28.059 CNTRLR   [Node 032] [+] [Version] interviewComplete: true       [Endpoint 0] [internal]
21:51:28.061 CNTRLR   [Node 032] Interviewing Z-Wave Plus Info...
21:51:28.061 CNTRLR » [Node 032] querying Z-Wave+ information...
21:51:28.113 CNTRLR « [Node 032] received response for Z-Wave+ information:
                      Z-Wave+ version: 2
                      role type:       SleepingListeningSlave
                      node type:       Node
                      installer icon:  0x2001
                      user icon:       0x2001
21:51:28.114 CNTRLR   [Node 032] Interviewing Entry Control...
21:51:28.114 CNTRLR » [Node 032] requesting entry control supported keys...
21:51:38.148 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:51:38.148 CNTRLR » [Node 032] requesting entry control supported events...
21:51:48.187 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:51:48.188 CNTRLR » [Node 032] requesting entry control configuration...
21:51:58.223 CNTRLR   [Node 032] Timed out while waiting for a response from the node (ZW0201)
21:51:58.223 CNTRLR   [Node 032] [+] [Entry Control] interviewComplete: true [Endpoint 0] [internal]
21:51:58.224 CNTRLR   [Node 032] Interview stage completed: CommandClasses
21:51:58.224 CNTRLR   [Node 032] Interview stage completed: OverwriteConfig
21:51:58.225 CNTRLR   [Node 032] Interview completed
21:51:58.225 CNTRLR   [Node 032] The node is ready to be used

Ideas?

Do you have any ideas what else I can try?

[bugs181]

For more context, it might be appropriate to post the Ring keypad version numbers. (Perhaps something has changed?)

FCC ID: 2AEUP5AT2S7 IC: 20271-5AT2S7 Model: 5AT2S7 SKU: 4AK1SZ-0EN0

I'm not sure what the DSN number is so I'll withhold that information for privacy reasons, unless I can determine the information can't be abused.

[bugs181]

Closing, it appears that the config.js file was corrupted and zwave-js-server could not read the S2_Authenticated and S2_AccessControl keys. After fixing this issue, I was able to successfully Include it on the first attempt.