Almost always need to re-interview my Z-Wave door lock to get it back online after updating HA

[hapklaar]

Describe the issue you are experiencing

See topic.

Not sure if any bug report has ever been filed for this.

Would be great if the add-on would take care of this automatically.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Z-Wave JS

What is the version of the add-on?

0.1.86

Steps to reproduce the issue

1. Use Danalock V3-BTZE Z-Wave doorlock and integrate into HA
2. Update HA
3. Observe device becoming 'unavailable' and not return back to 'alive'

System Health information

System information spins forever and copy button does nothing. Shows core and supervisor metrics though.

Anything in the Supervisor logs that might be useful for us?

Nothing relevant

Anything in the add-on logs that might be useful for us?

Log only contains the last 100 lines from the re-interview itself:

2023-08-14T15:46:53.032Z CNTRLR   [Node 017]   supports CC Configuration (0x70) in version 4
2023-08-14T15:46:53.032Z CNTRLR » [Node 017]   querying the CC version for Time Parameters...
2023-08-14T15:46:53.169Z CNTRLR   [Node 017]   supports CC Time Parameters (0x8b) in version 1
2023-08-14T15:46:53.169Z CNTRLR » [Node 017]   querying the CC version for Schedule Entry Lock...
2023-08-14T15:46:53.390Z CNTRLR   [Node 017]   supports CC Schedule Entry Lock (0x4e) in version 3
2023-08-14T15:46:53.400Z CNTRLR   [Node 017] Embedded device config loaded
2023-08-14T15:46:53.404Z CNTRLR   [Node 017] Interviewing Z-Wave Plus Info...
2023-08-14T15:46:53.404Z CNTRLR » [Node 017] querying Z-Wave+ information...
2023-08-14T15:46:53.548Z CNTRLR « [Node 017] received response for Z-Wave+ information:
                                  Z-Wave+ version: 1
                                  role type:       SleepingListeningSlave
                                  node type:       Node
                                  installer icon:  0x0300
                                  user icon:       0x0300
2023-08-14T15:46:53.549Z CNTRLR   [Node 017] Interviewing Time...
2023-08-14T15:46:53.549Z CNTRLR   [Node 017] Interviewing Battery...
2023-08-14T15:46:53.550Z CNTRLR » [Node 017] querying battery status...
2023-08-14T15:46:53.686Z CNTRLR « [Node 017] received response for battery information:
                                  level:                           67
2023-08-14T15:46:53.686Z CNTRLR   [Node 017] Interviewing Firmware Update Meta Data...
2023-08-14T15:46:53.686Z CNTRLR » [Node 017] Querying firmware update capabilities...
2023-08-14T15:46:53.839Z CNTRLR « [Node 017] Received firmware update capabilities:
                                    firmware targets:      0, 0
                                    continues to function: undefined
                                    supports activation:   undefined
2023-08-14T15:46:53.840Z CNTRLR   [Node 017] Interviewing Time Parameters...
2023-08-14T15:46:53.840Z CNTRLR » [Node 017] setting current time...
2023-08-14T15:46:53.999Z CNTRLR   [Node 017] Interviewing Association...
2023-08-14T15:46:53.999Z CNTRLR » [Node 017] querying number of association groups...
2023-08-14T15:46:54.175Z CNTRLR « [Node 017] supports 1 association groups
2023-08-14T15:46:54.176Z CNTRLR » [Node 017] querying association group #1...
2023-08-14T15:46:54.315Z CNTRLR « [Node 017] received information for association group #1:
                                  maximum # of nodes: 1
                                  currently assigned nodes: 1
2023-08-14T15:46:54.317Z CNTRLR   [Node 017] Checking/assigning lifeline groups: 1
                                  supports classic associations:       true
                                  supports multi channel associations: false
2023-08-14T15:46:54.317Z CNTRLR   [Node 017] Configuring lifeline group #1:
                                  group supports multi channel:  false
                                  configured strategy:           auto
                                  must use node association:     true
                                  must use endpoint association: false
2023-08-14T15:46:54.318Z CNTRLR   [Node 017] Lifeline group #1 is already assigned with a node association
2023-08-14T15:46:54.318Z CNTRLR   [Node 017] Interviewing Association Group Information...
2023-08-14T15:46:54.319Z CNTRLR » [Node 017] Association group #1: Querying name...
2023-08-14T15:46:54.472Z CNTRLR « [Node 017] Association group #1 has name "Lifeline"
2023-08-14T15:46:54.472Z CNTRLR » [Node 017] Association group #1: Querying command list...
2023-08-14T15:46:54.620Z CNTRLR » [Node 017] Association group #1: Querying info...
2023-08-14T15:46:54.767Z CNTRLR « [Node 017] Received info for association group #1:
                                  info is dynamic: false
                                  profile:         General: Lifeline
2023-08-14T15:46:54.768Z CNTRLR   [Node 017] Interviewing Door Lock...
2023-08-14T15:46:54.770Z CNTRLR » [Node 017] requesting lock configuration...
2023-08-14T15:46:54.910Z CNTRLR « [Node 017] received lock configuration:
                                  operation type:                Constant
                                  outside handles can open door: true, false, false, false
                                  inside handles can open door:  true, false, false, false
2023-08-14T15:46:54.911Z CNTRLR » [Node 017] requesting current lock status...
2023-08-14T15:46:55.189Z CNTRLR « [Node 017] received lock status:
                                  current mode:       Unsecured
                                  door status:        open
                                  bolt status:        unlocked
                                  latch status:       open
2023-08-14T15:46:55.190Z CNTRLR   [Node 017] Interviewing User Code...
2023-08-14T15:46:55.190Z CNTRLR » [Node 017] querying number of user codes...
2023-08-14T15:46:55.340Z CNTRLR   [Node 017] Interviewing Notification...
2023-08-14T15:46:55.341Z CNTRLR » [Node 017] querying supported notification types...
2023-08-14T15:46:55.616Z CNTRLR « [Node 017] received supported notification types:
                                  · Access Control
2023-08-14T15:46:55.616Z CNTRLR » [Node 017] querying supported notification events for Access Control...
2023-08-14T15:46:55.757Z CNTRLR « [Node 017] received supported notification events for Access Control: 1, 2, 3,
                                   4, 5, 6, 9, 11
2023-08-14T15:46:55.758Z CNTRLR » [Node 017] enabling notifications for Access Control...
2023-08-14T15:46:55.903Z CNTRLR   [Node 017] Interviewing Configuration...
2023-08-14T15:46:55.904Z CNTRLR   [Node 017] ConfigurationCC: Loading configuration parameters from device confi
                                  g
2023-08-14T15:46:55.907Z CNTRLR » [Node 017] finding first configuration parameter...
2023-08-14T15:46:56.106Z CNTRLR » [Node 017] querying parameter #1 information...
2023-08-14T15:46:57.189Z CNTRLR   [Node 017] Timed out while waiting for a response from the node (ZW0201)
2023-08-14T15:46:57.190Z CNTRLR   [Node 017] Querying parameter #1 information timed out, skipping scan...
2023-08-14T15:46:57.191Z CNTRLR » [Node 017] querying parameter #1 value...
2023-08-14T15:46:57.199Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-08-14T15:46:57.371Z CNTRLR   [Node 017] failed to decode the message, retrying with SPAN extension...
2023-08-14T15:46:57.543Z CNTRLR » [Node 017] querying parameter #2 value...
2023-08-14T15:46:57.687Z CNTRLR » [Node 017] querying parameter #3 value...
2023-08-14T15:46:57.826Z CNTRLR » [Node 017] querying parameter #4 value...
2023-08-14T15:46:57.969Z CNTRLR » [Node 017] querying parameter #5 value...
2023-08-14T15:46:58.108Z CNTRLR » [Node 017] querying parameter #6 value...
2023-08-14T15:46:58.252Z CNTRLR   [Node 017] Interviewing Schedule Entry Lock...
2023-08-14T15:46:58.253Z CNTRLR » [Node 017] Querying supported number of schedule slots...
2023-08-14T15:46:58.402Z CNTRLR « [Node 017] received supported number of schedule slots:
                                  day of week:     2
                                  day of year:     2
                                  daily repeating: 2
2023-08-14T15:46:58.402Z CNTRLR » [Node 017] setting timezone information...
2023-08-14T15:46:58.598Z CNTRLR   [Node 017] Interview stage completed: CommandClasses
2023-08-14T15:46:58.599Z CNTRLR   [Node 017] Interview stage completed: OverwriteConfig
2023-08-14T15:46:58.600Z CNTRLR   [Node 017] Interview completed
2023-08-14T15:46:58.600Z CNTRLR   [Node 017] The node is ready to be used

Additional information

Others are having same/similar issues, seems to have been goin on for a long time already:
https://community.home-assistant.io/t/automate-z-wave-js-re-interview/315483

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.