Justin Hammond

>@Fishwaldo will the ValueIDKey be the same when migrating from 1.4 to 1.6 ? Or is this something generated by OZW itself and not from the actual hardware/mesh ? Mostly.......

Just a quick heads up - The Build Version is now reflected in the OZWDaemon_Version in the status topic - You can use this to check the version used. I'm...

Also - regarding the comparision between the original and patched inputs here: https://github.com/danielgtaylor/huma/blob/1519e493315fb852cffee4c0d81d29f599f69068/patch.go#L243 if I read json-patch documentation, we should use: ``` jsonpatch.Equal(document1, document2) ```

No. That’s for a very very ancient version of Security in z-wave. The presence of the Security CC and a bool ValueID indicate if it’s securely added (sorry, can’t remember...

It’s just a normal value that’s exposed by the Security CC.

It’s not a attribute. It’s just like any other Value (on/off level etc) that exposed via a ValueAdded Notification

Right now you can’t. Please open a issue on the OpenZWave tracker. In those cases, only option now is remove failed node and then add node with secure true.

any ETA?

Using rpmsg-lite.

if you API is not completed yet, can I make a suggestion. In the old implementation, you divided the 32 interupt Sources equally between the 2 other CPU's (so we...