Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZEN04 800LR with 2.1 firmware unable to get past NodeInfo in Interview #4033

Closed
3 tasks done
voc0der opened this issue Nov 22, 2024 · 2 comments
Closed
3 tasks done
Labels
bug Something isn't working

Comments

@voc0der
Copy link

voc0der commented Nov 22, 2024

Checklist

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

Deploy method

Docker

Z-Wave JS UI version

9.27.5.b68aa39

ZwaveJS version

14.3.4

Describe the bug

The ZEN04 800LR with 2.1 firmware from factory does not seem to ever get recognized correctly due to the attached error. If you add it, it says it's added and authenticated successfully but it spins with a status interview of NodeInfo.

It doesn't ever show up, but I restarted the container, and then it showed up, but it was stuck on NodeInfo and still spinning. Tried every advanced feature, nothing helped. Got the errors below during re-interviewing.

To Reproduce

Try to pair the ZEN04 800LR with 2.1 firmware from factory

Expected behavior

It pairs successfully.

Additional context

This is after pairing it:

2024-11-22T20:56:30.711Z CNTRLR   [Node 058] Error during node interview: Argument validation failed:
                                  Expected parameter nodeIds to be an Array<number>, got 1 (ZW0322)

From Zniffer
This is at the late stage of the initializing the device via interview after pairing:

2024-11-22T21:04:41.682Z DRIVER « [Node 059] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 197
                                    │ security class:  S2_Authenticated
                                    └─[MultiChannelAssociationCCReport]
                                        group id:           2
                                        maximum # of nodes: 5
                                        node ids:
                                        endpoints:
2024-11-22T21:04:41.683Z CNTRLR « [Node 059] received information for multi channel association group #2:
                                  maximum # of nodes:           5
                                  currently assigned nodes:     
                                  currently assigned endpoints: 
2024-11-22T21:04:41.684Z CNTRLR   [Node 059] Checking/assigning lifeline groups: 1
                                  supports classic associations:       true
                                  supports multi channel associations: true
2024-11-22T21:04:41.684Z CNTRLR   [Node 059] Configuring lifeline group #1:
                                  group supports multi channel:  true
                                  configured strategy:           auto
                                  must use node association:     true
                                  must use endpoint association: false
2024-11-22T21:04:41.686Z CNTRLR » [Node 059] Assigning lifeline group #1 with a node association via Association
                                   CC...
2024-11-22T21:04:41.688Z CNTRLR   [Node 059] Error during node interview: Argument validation failed:
                                  Expected parameter nodeIds to be an Array<number>, got 1 (ZW0322)
2024-11-22T21:04:41.688Z DRIVER   all queues idle
2024-11-22T21:04:42.655Z SERIAL « 0x0122000400131a9f0368004adbf8e6d223a15255205565f67e614f79ce7e8e79e (36 bytes)
                                  bd4004b

I tried and reproduced this exact behavior 4 times before giving up. I have 45+ other nodes with no issues.

@voc0der voc0der added the bug Something isn't working label Nov 22, 2024
@kpine
Copy link
Contributor

kpine commented Nov 22, 2024

Upgrade to v9.27.7.

@voc0der
Copy link
Author

voc0der commented Nov 23, 2024

Fixed, thank you!

@voc0der voc0der closed this as completed Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants