This is fixed now!
My assumptions (NOGET must be at the command class level) appears to be correct. This was fixed by the last update of the Zwave jar file (Build 146), generated by @chris. Thanks a lot!!
Now this device is ready to be used!
Now how to “finalize” this device in the database ?
How to make sure this is OK and the definition is final ?
One minor point is left:
This device has an unusual reset procedure, by a config item that is both writable as set by the device:
When you write 255 (0xFF) to this parameter, all configurable values are set back to their defaults. After some time, at the next wake up, the device will “answer” that by making the value -86 again (input is 0 to 255, but output is -128 to +127, in 2’s complement notation)
I can see this line in my logfile, after changing the sensor:
21:50:24.456 NODE 28: Application Command Request (ALIVE:DONE)
21:50:24.457 NODE 28: resetResendCount initComplete=true isDead=false
21:50:24.458 NODE 28: Incoming command class COMMAND_CLASS_CONFIGURATION, endpoint 0
21:50:24.459 NODE 28: SECURITY not supported
21:50:24.460 NODE 28: Received COMMAND_CLASS_CONFIGURATION V1 CONFIGURATIONCMD_REPORT
21:50:24.460 NODE 28: Node configuration report, parameter = 1, value = -86, size = 1
21:50:24.461 NODE 28: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent
21:50:24.462 NODE 28: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_CONFIGURATION, value=
21:50:24.463 NODE 28: Update CONFIGURATION 1/1 to -86
21:50:24.464 NODE 28: Configuration pending removed for config_1_1
21:50:24.464 NODE 28: Commands processed 1.
21:50:24.465 NODE 28: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@c8c39e.
21:50:24.466 NODE 28: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@c8c39e.
21:50:24.467 NODE 28: notifyTransactionResponse TID:861 DONE
21:50:24.468 NODE 28: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
21:50:24.469 Transaction completed - outstandingTransactions 1
21:50:24.470 Transaction completed - outstandingTransactions 0
21:50:24.471 ZWaveReceiveThread queue empty
21:50:24.472 Transaction SendNextMessage 0 out at start. Holdoff false.
21:50:24.835 NODE 28: WakeupTimerTask 0 Messages waiting, state DONE
21:50:25.335 NODE 28: WakeupTimerTask 0 Messages waiting, state DONE
21:50:25.336 NODE 28: No more messages, go back to sleep
21:50:25.337 NODE 28: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
21:50:25.338 NODE 28: SECURITY not supported
21:50:25.339 NODE 28: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
21:50:25.340 NODE 28: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactio
It seems like the sensor is anwering with ‘-86’, however, the OpenHab CLI (neither GUI) does not reflect this:
openhab> openhab:things show zwave:device:07a8817ea9:node28
config_1_1 : 2
This is not a big deal, but it puzzles me…
What to do about that?
Perhaps ignore it?