Consider S0 inclusion in S2 capable network insecure

[AlCalzone]

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.

[AlCalzone]

Note that this is already done for the case when S0 is chosen automatically, e.g. for a (seemingly) legacy lock. If S0 is chosen by the user, this requirement does not really make sense. So we'll have to figure out how to align with the specification here.