Hi, Chris,
As I said over here, on this other post, I’m curious to know what this switch does, too, so if you can do something for us, we can all learn a little, perhaps.
The best way to figure out what the dimmer switch is doing when you change the value manually is to put the openHAB Zwave binding into debug mode and watch everything that happens. I think all that is required to do Zwave debug logging is to make sure that the following code is in your logback.xml file:
<appender name="ZWAVEFILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>logs/zwave.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!-- weekly rollover and archiving -->
<fileNamePattern>logs/zwave-%d{yyyy-ww}.log.zip</fileNamePattern>
<!-- keep 30 days' worth of history -->
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}:%-4line]- %msg%n</pattern>
</encoder>
</appender>
<!-- Change DEBUG->TRACE for even more detailed logging -->
<logger name="org.openhab.binding.zwave" level="DEBUG" additivity="false">
<appender-ref ref="ZWAVEFILE" />
</logger>
(I’m almost certain that most, if not all, of this code may already be in the default logback.xml file, but I don’t know for sure. The only thing you may have to do is change the logging level for the Zwave binding to DEBUG. And 30 days of Zwave debug history is a lot of history to keep. Careful that you don’t fill up your storage.)
Once you verify that you have a log file being produced, you can ssh into your box and use a command like this:
tail -f /opt/openhab/logs/zwave.log | grep --line-buffered "NODE 6"
substituting in the node number for the dimmer and the log file location, both of which can/should/may be different in your installation.
Then you’ll see stuff like this show up:
2016-12-08 07:19:33.512 [DEBUG] [ApplicationCommandMessageClass:41 ]- NODE 6: Application Command Request (ALIVE:DONE)
2016-12-08 07:19:33.514 [DEBUG] [ApplicationCommandMessageClass:146 ]- NODE 6: Incoming command class SWITCH_MULTILEVEL (0x26)
2016-12-08 07:19:33.515 [DEBUG] [veMultiLevelSwitchCommandClass:95 ]- NODE 6: Received Switch Multi Level Request
2016-12-08 07:19:33.516 [DEBUG] [veMultiLevelSwitchCommandClass:115 ]- NODE 6: Switch Multi Level report, value = 99
2016-12-08 07:19:33.518 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 6: Notifying event listeners: ZWaveCommandClassValueEvent
2016-12-08 07:19:33.520 [DEBUG] [.z.internal.ZWaveActiveBinding:472 ]- NODE 6: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_MULTILEVEL, value = 99
2016-12-08 07:19:33.530 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 6: Notifying event listeners: ZWaveTransactionCompletedEvent
(This is the technique I used to figure out what the scene commands report back for my HS-WS100+.)
Then go run the dimmer up and down and report back to us what, if anything, shows up in the logs.
/Bill