If a node has been security bootstrapped with the S0 Command Class in an S2 capable network, the SIS / Primary controller MUST issue a warning message to the user informing that the node has not been included securely. Requires 2. on the HA side
TODO Home Assistant (frontend):
Show big fat warning that the node is being included insecurely at the start of the process.
Show specific error message when inclusion failed, so show as much info as possible. The Driver has been adjusted to deliver this info.
Show warning that the node was NOT added securely (despite the fact that the user choose secure inclusion).
Issues/improvements
Show right after the node was added, not at the end of the interview --> https://github.com/home-assistant/core/issues/117636
Distinguish between the different reasons for insecure inclusion instead of "an error". See https://github.com/zwave-js/node-zwave-js/pull/5570 for details
If a node has been security bootstrapped with the S0 Command Class in an S2 capable network, the SIS / Primary controller MUST issue a warning message to the user informing that the node has not been included securely. Requires 2. on the HA side
TODO Home Assistant (frontend):
Show big fat warning that the node is being included insecurely at the start of the process.
Show specific error message when inclusion failed, so show as much info as possible. The Driver has been adjusted to deliver this info.
Show warning that the node was NOT added securely (despite the fact that the user choose secure inclusion).