Everything has been running without a flaw for many years (and thanks again a lot for that ), but with the latest openhab stable (4.2.1-1 via the debian package) update I now have my two Aeotec wallmote quad devices failing with this message :
> *10:42:50.812 [ERROR] [ommandclass.ZWaveSecurityCommandClass] - NODE 3: Error decapsulating security message*
> *java.security.InvalidKeyException: No installed provider supports this key: (null)*
> * at javax.crypto.Cipher.chooseProvider(Cipher.java:958) ~[?:?]*
> * at javax.crypto.Cipher.init(Cipher.java:1299) ~[?:?]*
> * at javax.crypto.Cipher.init(Cipher.java:1236) ~[?:?]*
> * at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveSecurityCommandClass.generateMAC(ZWaveSecurityCommandClass.java:528) ~[bundleFile:?]*
> * at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveSecurityCommandClass.getSecurityMessageDecapsulation(ZWaveSecurityCommandClass.java:319) [bundleFile:?]*
> * at org.openhab.binding.zwave.internal.protocol.ZWaveNode.processCommand(ZWaveNode.java:1237) [bundleFile:?]*
> * at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager$ZWaveReceiveThread.run(ZWaveTransactionManager.java:548) [bundleFile:?]*
The rest of my Zwave network (a dozen of nodes, everything included with security) still works.
Did you checkout the below links - maybe you find some valuable info there - mainly it has something to do with battery devices and secure inclusion IMHO.
How are you managing the security keys between the windows software and OH; and when you included the devices, did you do that in OH? Lastly what does the current node XML looking like? Specifically is the Security Class in the NIF section?
I’ve the same key for both windows and OH, defined ten years ago and never rotated (sorry for the cybersecurity specialists reading that )
All devices excepted the two aeotec wallmote still work, and the two devices were working before an openhab update.
You probably got it : the node.xml of the two devices are… empty (the other ones are normal). But what should I do ?
With a battery device in security, that is probably the worst scenario. Normally you could wake it up to get it configured, but since the security is messed up somehow, the wakeup is probably encoded, so OH can’t “hear” it. Probably the best option is to exclude with the Silabs app, then readd using Openhab. Make sure the key (click advanced) on UI controller is the one you have been using. Also could do the factory reset option, but since the Silabs tool is working it might cause less problems just to exclude it from that app.
), but with the latest openhab stable (4.2.1-1 via the debian package) update I now have my two Aeotec wallmote quad devices failing with this message :
)