Allow S2 keys in OZW format for migration from networkKey #399
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows for migrations from
"networkKey"
, which are allowed to be in OZW format, to"S0_Legacy"
without requiring a change in key format. Client applications can choose to migrate key formats on their own.First reported at https://community.home-assistant.io/t/zwave-js-fails-to-load/342679. Based on the error, I am assuming the user had a previously working addon, so the key must have originally been entered in the OZW format, and after upgrading the addon it migrated it to the
S0_Legacy
option name, which doesn't allow OZW format keys.