Replies: 2 comments
-
Yes. Including a node into the network is handled by the stick. Bootstrapping the node (exchanging security keys etc.) happens afterwards and is handled by Z-Wave JS. At this point the node is already part of the network. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for the quick answer!
… On Jul 6, 2022, at 9:56 AM, AlCalzone ***@***.***> wrote:
Yes. Including a node into the network is handled by the stick.
Bootstrapping the node (exchanging security keys etc.) happens afterwards and is handled by Z-Wave JS. At this point the node is already part of the network.
—
Reply to this email directly, view it on GitHub <#4782 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABG55EQDVQVDPNNFL6D7FULVSWGBDANCNFSM52ZVJ5QA>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Running version 9.6.0
Is it expected that if inclusion is aborted (receive that event from the controller), that the node is still added? That is what I'm seeing.
I start inclusion, initiate inclusion on the device. The device requests s2 unauthenticated. I respond with NO security grants on purpose. Get an aborted event, but the node is added anyway.
Is this expected behavior
zwavejs.log
?
Beta Was this translation helpful? Give feedback.
All reactions