Aeotec NanoMote Quad (ZWA003) in secure mode #6491
Unanswered
kpanchen
asked this question in
Request Support / Investigate Issue
Replies: 1 comment 1 reply
-
Not sure if this is related, but it seems like your device doesn't actually have parameter 41. We have it in our configuration DB, but Aeotec's manual does not list it (down at the bottom). I have to agree though, there's nothing in that log that looks like any If not, we can add a warning to the device DB to not include it securely. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Checklist
I have read and followed the above instructions
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there or the fix did not work.
Describe the issue
What is happening? - Device can be included in both secure (S2) and unsecure mode, both inclusion successful but with secure mode after device goes to sleep it will never communicate with controller again. Unsecure works fine.
What did you expect to happen instead?
Both mode works the same way.
Anything else we should know?
All the attempts are next to the controller, this is the second problematic with security legacy Aeotec device, just want to make sure problem is not on my side. Side note - old controller is still running as devices being moved to a new one.
zwavejs_2023-11-03.log
Software versions
zwave-js-ui: 9.3.1
zwave-js: 12.2.3
Stand alone
Device information
Manufacturer: Aeotec
Model name: Nanomote Quad
Node ID: 54
Checklist
I made sure to provide a driver log on level debug.
The log includes a re-interview of the problematic device (if applicable).
The log includes the problematic interaction with the device (if applicable).
I provided the node ID of the problematic device (if applicable).
Upload Logfile
z-ui_2023-11-03.log
Beta Was this translation helpful? Give feedback.
All reactions