You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configuring the z-wave adapter with the network key generated using the command fails: cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g'
Log output: ERROR : zwave: Found NetworkKey, but invalid format. Ignoring
However lowercasing the key to 0x2f,0xd6,0x8e,0x86,0x45,0x4a,0x4c,0x23,0x05,0x44,0x25,0x78,0x86,0x07,0x14,0x4e INFO : zwave: Found NetworkKey, initializing with support for Security Devices
Adding whitespace after each of the commas also causes the network key to be rejected.
I think the networkKey should not be case sensitive and should also tolerate whitespace. I also think that the UI should indicate that a networkKey is in an invalid format.
The text was updated successfully, but these errors were encountered:
Configuring the z-wave adapter with the network key generated using the command fails:
cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g'
0x2F,0xD6,0x8E,0x86,0x45,0x4A,0x4C,0x23,0x05,0x44,0x25,0x78,0x86,0x07,0x14,0x4E
Log output:
ERROR : zwave: Found NetworkKey, but invalid format. Ignoring
However lowercasing the key to
0x2f,0xd6,0x8e,0x86,0x45,0x4a,0x4c,0x23,0x05,0x44,0x25,0x78,0x86,0x07,0x14,0x4e
INFO : zwave: Found NetworkKey, initializing with support for Security Devices
Adding whitespace after each of the commas also causes the network key to be rejected.
I think the networkKey should not be case sensitive and should also tolerate whitespace. I also think that the UI should indicate that a networkKey is in an invalid format.
The text was updated successfully, but these errors were encountered: