kpine

I forgot I was already mapping the `crashes` directory to a bind mount. This is a workaround to keep the crash dumps out of the config directory. I realized I...

For COMMAND_CLASS_SWITCH_MULTILEVEL Set command, a value of 100 is not valid. 0 is off and 99 is 100%. Anything in-between 100 and 255 is reserved. 

I don't have the device so I can't say why the COMMAND_CLASS_MANUFACTURER_PROPRIETARY value is moving the blinds. As the label says, it appears to be for changing Venetian blind slat...

Are you sure you're running the latest? What is the SHA digest for your image? Here's what I have. ``` $ docker images --digests | grep allinone-latest openzwave/ozwdaemon allinone-latest sha256:815a5c8141a693d8d8a1c1f5fd36165024fbb42a4e0136760f69c8481ea5076f...

Do you know which docker image you were using? build-169 has a change related to logging, wondering if makes a difference. I thought I was on the latest but wasn't,...

On build-169 I was able to watch the log file get to about 9.6MB and then it was rotated, ozwd survived the rotation without a hiccup, so perhaps the latest...

I would not assume this behavior is intentional. The target check and refresh logic was recently added as part of #1321, which is still in progress. If you downgrade to...

From your initial report I was assuming you were activating the device locally (from a physical switch). Can you clarify if you were doing that, or using z-wave commands? There...

Value id keys are unsigned 64, so that value is not too large. Can you post both the topic and json for that value? There have been cases of the...

These don't match: `OpenZWave/1/node/10/instance/1/commandclass/50/value/72339069195812888/` `"ValueIDKey": 72339069195812900,` Unless there's some cases I'm unaware of, I could expect both of those to be equal. You might try using `72339069195812888` in the command...