Nezmo
April 1, 2019, 5:59pm
2
You are not alone. This is caused by changes in the latest hub firmware. To rectify changes to the DTH are required (which hopefully the developer will handle in due course).
Starting with 0.25.X hub firmware release, the handling of encapsulation for Z-Wave messages are now delegated to the hub. This change was mainly driven from the forthcoming of Z-Wave S2 to our platform and instead of having to add additional encapsulation functionality to the DTHs, we decided that it is best to perform auto encapsulation at the hub level and remove any encapsulation added to the message in order to reduce the responsibilities of the DTHs.
There are two main changes starting in 0.25.X hub firmware release that we should discuss and the impact it will have on the DTHs.
Auto Encapsulation (Security 0, CRC-16, None) of Outgoing Z-Wave Messages
Auto encapsulation of messages is based on the properties of the device and command classes, reported by the device itself. In past…