Closed CrossEyeORG closed 3 years ago
This is a bug in zwave-js-server. I'll report it there.
For reference: https://github.com/zwave-js/zwave-js-server/issues/355
Thanks for the report.
Meanwhile, if you're looking for some workarounds, you can either try the kpine/zwave-js-server:s2
image, which is based on that PR, or you can mount a modified options.js
file to make the zwave-js-server happy.
module.exports = {
logConfig: {
filename: process.env.LOGFILENAME,
forceConsole: true,
},
storage: {
cacheDir: "/cache",
deviceConfigPriorityDir: "/cache/config",
},
networkKey: process.env.NETWORK_KEY,
securityKeys: {}
};
You can also manually specify all of the s2 security keys in that file as well, w/o requiring the s2 build. That PR just adds the environment variables.
module.exports = {
logConfig: {
filename: process.env.LOGFILENAME,
forceConsole: true,
},
storage: {
cacheDir: "/cache",
deviceConfigPriorityDir: "/cache/config",
},
securityKeys: {
S0_Legacy: "1111111111111111",
...
},
};
Fixed with tag 1.10.2-8.2.1
and current latest
.
I am on the latest branch
kpine/zwave-js-server:latest
and am now receiving the following error,Validated that rolling back to version
1.10.0-8.2.0
I was able to get around the above issue.Looking at the latest pull requests, I am seeing Add S2 key support #7 which is where I think the above bug was introduced in version
1.10.1-8.2.1
.