kpine
kpine
> This is a device with VerifiedChanges right? Yes.
Not sure if you're done yet, so apologies if you're still fixing things, but here's what I see with the [latest](https://github.com/OpenZWave/open-zwave/commit/ac3d0d60837190ea119848a110ec08ba4d39818a). I wiped my cache first before doing this as...
Here's a log showing some weird behavior for the verify changes (as discussed in Discord). Using latest ozwdaemon. [ozwd.log](https://github.com/OpenZWave/open-zwave/files/4967745/ozwd.log) First I set the Dim Duration to 10 seconds. The switch...
Perhaps it's `ReleaseDLL` instead of `Release`? Looks like that's how it's built for Windows ozw-admin. https://github.com/OpenZWave/ozw-admin/blob/da04ebfbadc57484c487ebc846431eb283e83176/scripts/win32build.bat#L3
Has anyone tried increasing the MQTT client timeout in ozwd to see if that works around the problem? Maybe increasing the timeout would allow ozwd to finish whatever it's doing...
> In a nutshell it seems that the capabilities report where the min- and maximum temperature are reported, this information is passed with a field size for the minimum and...
> The Norwegian thread and goes all over the place but since OpenHab and HA both use OZW under the hood, both are affected. OpenHAB is an independent implementation of...
> About that screenshot: I was linked the Z-wave specification before which is the same document Heat-It seemed to use but it differs from your My screenshot is from document...
For the interview, in v1 and v2, the controller must enumerate all of the "ambiguous" setpoint values. In V3 it only needs to enumerate the setpoints that it says are...
FYI, my older tstat with V2 Setpoint and multi-channel association has no problem accepting an encapsulated command that comes from source endpoint 1. Not sure if there's a requirement one...