OH2 Z-Wave refactoring and testing... and SECURITY

mstormi · August 19, 2018, 6:57pm

Hmm. Node 10 is real, it is a ZME_05461 double switch and it’s one of the first zwave devices I’ve ever setup. Ancient it is, and nothing about it changed recently.

chris · August 19, 2018, 7:01pm

Then I doubt that it’s really sending these requests - I’d try resetting it in the first instance and see if that fixes the problem. I don’t think it’s related in any way to the change in the binding.

mstormi · August 19, 2018, 7:15pm

Hmm, the exception did not happen again (only during binding startup) and the device is working flawlessly.
I’ll leave it like that (it’s so old I even don’t know any more how to reset it) and keep watching.

mstormi · August 19, 2018, 7:31pm

Got some more exceptions, a different node this time.
Btw, it did not happen with the binding as of Aug, 14th (xml and nodes haven’t changed since).
Do you still think it’s unrelated ? Here’s that node’s .xml: network_c602b032__node_113.xml (19.1 KB)

2018-08-19 21:21:43.148 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Exception processing frame: Message: class=ApplicationCommandHandler[4], type=Request[0], dest=81, callback=16, payload=10 51 08 91 01 0F 26 03 03 00 01 :
java.lang.NullPointerException: null
2018-08-19 21:21:44.002 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Exception processing frame: Message: class=ApplicationCommandHandler[4], type=Request[0], dest=81, callback=16, payload=10 51 08 91 01 0F 26 03 03 00 01 :
java.lang.NullPointerException: null
^C
[21:21:51] openhabian@openhabianpi:/etc/openhab2/items$ vi + /var/log/openhab2/openhab.log

2018-08-19 21:21:58.282 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01
2018-08-19 21:21:58.284 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01
2018-08-19 21:21:58.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01
2018-08-19 21:21:58.288 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-08-19 21:21:58.289 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 113: Application Command Request (ALIVE:DONE)
2018-08-19 21:21:58.291 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: resetResendCount initComplete=true isDead=false
2018-08-19 21:21:58.291 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 10 71 08 91 01 0F 26 03 03 00 01 24
2018-08-19 21:21:58.292 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: Incoming command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY, endpoint 0
2018-08-19 21:21:58.293 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: Command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY not found, trying to add it.
2018-08-19 21:21:58.294 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 113: Unknown command class 0x91
2018-08-19 21:21:58.295 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: Unsupported Z-Wave command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY
2018-08-19 21:21:58.296 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: SECURITY not supported
2018-08-19 21:21:58.298 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Exception processing frame: Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01 :
java.lang.NullPointerException: null
        at org.openhab.binding.zwave.internal.protocol.ZWaveNode.processCommand(ZWaveNode.java:1357) [243:org.openhab.binding.zwave:2.4.0.201808191228]
        at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager$ZWaveReceiveThread.run(ZWaveTransactionManager.java:484) [243:org.openhab.binding.zwave:2.4.0.201808191228]
2018-08-19 21:21:58.299 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-08-19 21:21:58.300 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-08-19 21:21:58.322 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01
2018-08-19 21:21:58.324 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01
2018-08-19 21:21:58.327 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01
2018-08-19 21:21:58.328 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-08-19 21:21:58.329 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 113: Application Command Request (ALIVE:DONE)
2018-08-19 21:21:58.330 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 10 71 08 91 01 0F 26 03 03 00 01 24
2018-08-19 21:21:58.332 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: resetResendCount initComplete=true isDead=false
2018-08-19 21:21:58.334 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: Incoming command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY, endpoint 0
2018-08-19 21:21:58.335 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: Command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY not found, trying to add it.
2018-08-19 21:21:58.336 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01
2018-08-19 21:21:58.338 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 113: Unknown command class 0x91
2018-08-19 21:21:58.339 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01
2018-08-19 21:21:58.340 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: Unsupported Z-Wave command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY
2018-08-19 21:21:58.343 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 113: SECURITY not supported
2018-08-19 21:21:58.345 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 10 71 08 91 01 0F 26 03 03 00 01 24
2018-08-19 21:21:58.345 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Exception processing frame: Message: class=ApplicationCommandHandler[4], type=Request[0], dest=113, callback=16, payload=10 71 08 91 01 0F 26 03 03 00 01 :
java.lang.NullPointerException: null
        at org.openhab.binding.zwave.internal.protocol.ZWaveNode.processCommand(ZWaveNode.java:1357) [243:org.openhab.binding.zwave:2.4.0.201808191228]

chris · August 19, 2018, 7:40pm

Well, for starters this is a totally different issue than the one you raised a few minutes ago, and is not related so I don’t link them together.

There was only a small change between the 14th and 18th binding, and it was to do with adding command classes - this one here could be linked - the earlier one was more like a corrupt frame.

mstormi · August 20, 2018, 8:24am

Got that exception on some more devices, as far as I can see all of them are Fibaro FGRM-222 and binding complains about unknown class 0x91 COMMAND_CLASS_MANUFACTURER_PROPRIETARY.

chris · August 20, 2018, 8:31am

Strange - this hasn’t changed at all between bindings from the 14th to the 18th. Unfortunately the exception doesn’t provide enough information. Normally there’s a stack trace that shows where the error is, but it’s not in your log - is there more available?

mstormi · August 20, 2018, 8:41am

No, the exception is all I see (see bottom).

2018-08-20 10:26:19.264 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 00 5F 08 91 01 0F 26 03 03 01 00 1A
2018-08-20 10:26:19.292 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 08 91 01 0F 26 03 03 01 00
2018-08-20 10:26:19.293 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 08 91 01 0F 26 03 03 01 00
2018-08-20 10:26:19.295 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 08 91 01 0F 26 03 03 01 00
2018-08-20 10:26:19.296 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-08-20 10:26:19.297 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 95: Application Command Request (ALIVE:DONE)
2018-08-20 10:26:19.298 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: resetResendCount initComplete=true isDead=false
2018-08-20 10:26:19.298 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: Incoming command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY, endpoint 0
2018-08-20 10:26:19.299 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: Command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY not found, trying to add it.
2018-08-20 10:26:19.300 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 95: Unknown command class 0x91
2018-08-20 10:26:19.301 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: Unsupported Z-Wave command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY
2018-08-20 10:26:19.301 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: SECURITY not supported
2018-08-20 10:26:19.303 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Exception processing frame: Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 08 91 01 0F 26 03 03 01 00 :
java.lang.NullPointerException: null
        at org.openhab.binding.zwave.internal.protocol.ZWaveNode.processCommand(ZWaveNode.java:1357) [243:org.openhab.binding.zwave:2.4.0.201808191228]
        at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager$ZWaveReceiveThread.run(ZWaveTransactionManager.java:484) [243:org.openhab.binding.zwave:2.4.0.201808191228]
2018-08-20 10:26:19.305 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-08-20 10:26:19.306 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-08-20 10:26:19.503 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 5F 06 31 05 04 22 00 00 BC
2018-08-20 10:26:19.532 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 06 31 05 04 22 00 00
2018-08-20 10:26:19.533 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 06 31 05 04 22 00 00
2018-08-20 10:26:19.542 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 06 31 05 04 22 00 00
2018-08-20 10:26:19.543 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-08-20 10:26:19.544 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 95: Application Command Request (ALIVE:DONE)
2018-08-20 10:26:19.545 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: resetResendCount initComplete=true isDead=false
2018-08-20 10:26:19.546 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2018-08-20 10:26:19.547 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: SECURITY not supported
2018-08-20 10:26:19.547 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 95: Received COMMAND_CLASS_SENSOR_MULTILEVEL V2 SENSOR_MULTILEVEL_REPORT
2018-08-20 10:26:19.548 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 95: Sensor Type = Power(4), Scale = 0
2018-08-20 10:26:19.549 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 95: Sensor Value = 0E+1
2018-08-20 10:26:19.550 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 95: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2018-08-20 10:26:19.551 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 95: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 0E+1
2018-08-20 10:26:19.553 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 95: Sensor conversion not performed for POWER.
2018-08-20 10:26:19.554 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 95: Updating channel state zwave:device:ddd23e6c:node95:sensor_power to 0 [DecimalType]
2018-08-20 10:26:19.556 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 95: Commands processed 1.
2018-08-20 10:26:19.557 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 95: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1075190.
2018-08-20 10:26:19.557 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-08-20 10:26:19.558 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-08-20 10:26:19.559 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-08-20 10:26:19.559 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-08-20 10:26:21.298 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 00 5F 08 91 01 0F 26 03 03 03 37 2F
2018-08-20 10:26:21.322 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 08 91 01 0F 26 03 03 03 37
2018-08-20 10:26:21.323 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 08 91 01 0F 26 03 03 03 37
2018-08-20 10:26:21.324 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 08 91 01 0F 26 03 03 03 37
2018-08-20 10:26:21.325 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-08-20 10:26:21.326 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 95: Application Command Request (ALIVE:DONE)
2018-08-20 10:26:21.327 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: resetResendCount initComplete=true isDead=false
2018-08-20 10:26:21.328 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: Incoming command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY, endpoint 0
2018-08-20 10:26:21.329 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: Command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY not found, trying to add it.
2018-08-20 10:26:21.330 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 95: Unknown command class 0x91
2018-08-20 10:26:21.331 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: Unsupported Z-Wave command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY
2018-08-20 10:26:21.332 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 95: SECURITY not supported
2018-08-20 10:26:21.333 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Exception processing frame: Message: class=ApplicationCommandHandler[4], type=Request[0], dest=95, callback=0, payload=00 5F 08 91 01 0F 26 03 03 03 37 :
java.lang.NullPointerException: null
        at org.openhab.binding.zwave.internal.protocol.ZWaveNode.processCommand(ZWaveNode.java:1357) [243:org.openhab.binding.zwave:2.4.0.201808191228]
        at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager$ZWaveReceiveThread.run(ZWaveTransactionManager.java:484) [243:org.openhab.binding.zwave:2.4.0.201808191228]
2018-08-20 10:26:21.334 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-08-20 10:26:21.335 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

Found another similar one. Node 12 is a Fibaro FGMS.

2018-08-20 08:16:04.216 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 0C 0A 57 01 31 05 03 0A 01 5C AF D8 AC
2018-08-20 08:16:04.253 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=12, callback=0, payload=00 0C 0A 57 01 31 05 03 0A 01 5C AF D8
2018-08-20 08:16:04.257 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=12, callback=0, payload=00 0C 0A 57 01 31 05 03 0A 01 5C AF D8
2018-08-20 08:16:04.260 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=12, callback=0, payload=00 0C 0A 57 01 31 05 03 0A 01 5C AF D8
2018-08-20 08:16:04.263 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-08-20 08:16:04.265 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 12: Application Command Request (ALIVE:REQUEST_NIF)
2018-08-20 08:16:04.267 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Incoming command class COMMAND_CLASS_APPLICATION_CAPABILITY, endpoint 0
2018-08-20 08:16:04.269 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Command class COMMAND_CLASS_APPLICATION_CAPABILITY not found, trying to add it.
2018-08-20 08:16:04.270 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 12: Unsupported command class COMMAND_CLASS_APPLICATION_CAPABILITY
2018-08-20 08:16:04.272 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Unsupported Z-Wave command class COMMAND_CLASS_APPLICATION_CAPABILITY
2018-08-20 08:16:04.274 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: SECURITY not supported
2018-08-20 08:16:04.276 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Exception processing frame: Message: class=ApplicationCommandHandler[4], type=Request[0], dest=12, callback=0, payload=00 0C 0A 57 01 31 05 03 0A 01 5C AF D8 :
java.lang.NullPointerException: null
        at org.openhab.binding.zwave.internal.protocol.ZWaveNode.processCommand(ZWaveNode.java:1357) [243:org.openhab.binding.zwave:2.4.0.201808191228]
        at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager$ZWaveReceiveThread.run(ZWaveTransactionManager.java:484) [243:org.openhab.binding.zwave:2.4.0.201808191228]
2018-08-20 08:16:04.279 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

chris · August 20, 2018, 8:43am

Ok, thanks. I see the issue - just ignore it for now and I’ll add a fix at some point. The frames aren’t processed in any case, so I just need to add something to ignore them.

chris · August 20, 2018, 8:55am

I’ve updated the binding - hopefully it should remove these exceptions.

Lolodomo · August 20, 2018, 11:42am

Just for information, I solved my problem with my Aeon Labs Smart Energy Switch (DSC06). To get a feedback in openHAB from an action to the local switch button, it is necessary to change the value of the parameter 80 (automatic notifications). It is set by default to “Nothing”. I switched it to “Basic CC Report” and now it works well as I expected.

Lolodomo · August 20, 2018, 12:13pm

Ok I come back to my problem to setup the ST814 using Paper UI.
As a reminder, I am trying to set the parameter 6 “Auto report time” to 60. After monitoring the REST call in Firefox, I can confirm that that the call is done with config_6_2 set to 0 rather than 60 entered into the field !

So it looks like a bug either in Paper UI or the way the parameter is defined by the binding:

      <parameter name="config_6_2" type="integer" groupName="configuration"
                 min="0" max="1439">
        <label>6: Auto report time</label>
        <description><![CDATA[
Sets the time interval when a sensor report is sent<br /><h1>Overview</h1><p>0 = Disable</p> <p>1 min - 1439 min = Auto report periodically</p>
        ]]></description>
        <default>0</default>
        <options>
          <option value="0">Disable</option>
        </options>
        <limitToOptions>false</limitToOptions>
</parameter>

Could it be a problem relative to options + limitToOptions set to false ?

@mhilbush : did you already set this parameter using Paper UI ?

PS: I will now try using HABmin.

mstormi · August 20, 2018, 12:15pm

Running for 3 hrs now, I haven’t seen any.
Thanks.

Kim_Andersen · August 20, 2018, 12:20pm

Sorry to step in here…
I have a ST814 as well. My problem with it is, that after a coupple of months running, it reports battery level 0. But the device itself does not indicate there is lack of battery. Have you had the same experience?

chris · August 20, 2018, 12:44pm

Well, it might be a bug related to this, but if so, it’s in PaperUI. The definition looks fine - we are saying that there is an option 0, but you are not limited to this, and you can set any value from 0 to 1439.

I think the definition is ok and my guess is there’s a PaperUI bug. What happens if you set the value to 1500 - PaperUI shouldn’t allow you to click the save button which would tell me that it’s correctly defining the parameter in the UI, but then possibly some checks at the end are somehow selecting the options again. (but that’s a guess).

Ben_Douglas · August 20, 2018, 2:07pm

I want to offer a tip to help others if they are trying to include a lock and it is failing to include securely. I know that every guide says to bring the lock close to the zwave controller when doing the secure inclusion. I tried uncusscessfully to include a Kwikset 914TRL lock about 20 times that was placed 12" away from the z-stick in my raspberry pi. I tried everything: fresh batteries, locked, unlocked, high power, network wide, low power, standing on one foot while turning in a circle.
The solution was to hold the lock as close as physically possible to the zstick while doing the secure inclusion. Holding the lock right up against the zstick worked for me the first time.
I hope this can save some frustration for someone.

mhilbush · August 20, 2018, 4:12pm

I use HABmin to make config changes to my zwave devices. If you use HABmin it should properly set the autoreport time to 60.

Lolodomo · August 20, 2018, 7:48pm

Yes, with HABmin it works. But not with Paper UI. Apparently the bug is known and issue already declared.

Lolodomo · August 20, 2018, 7:54pm

I have now added a Fibaro FGMS 001 and I encounter 2 difficulties:

Battery level is not updated
Sensor luminance is either 0 or 1

Here is how are defined my channels:

Number BatterieDetecteur2Salon "Batterie détecteur salon Fibaro [%d %%]" <battery> (GBatterie) { channel="zwave:fibaro_fgms001_00_000:controller:node8:battery-level" }

Number LuminositeSalon "Luminosité salon [%d lux]" <none> (SalleSejour) { channel="zwave:fibaro_fgms001_00_000:controller:node8:sensor_luminance" }

What is the unit of the luminance ? With my Vera, it was a value in lux.

mhilbush · August 20, 2018, 8:02pm

Here’s how I have my channels defined.

Number Living_Luminance        "Living Luminance [%.0f]"     <light>       (gFF_Living,gSensor,gLuminance)     { channel="zwave:device:zstick:node37:sensor_luminance" }
Number Living_BatteryLevel     "Living Battery [%.0f %%]"    <battery>     (gBattery)                          { channel="zwave:device:zstick:node37:battery-level" }

Should be lux. These are typical values I see.

2018-08-19 14:44:36.557 [vent.ItemStateChangedEvent] - Living_Luminance changed from 39 to 70
2018-08-19 15:14:26.112 [vent.ItemStateChangedEvent] - Living_Luminance changed from 70 to 76
2018-08-19 15:44:07.234 [vent.ItemStateChangedEvent] - Living_Luminance changed from 76 to 85
2018-08-19 15:44:15.137 [vent.ItemStateChangedEvent] - Living_Luminance changed from 85 to 88
2018-08-19 16:14:05.194 [vent.ItemStateChangedEvent] - Living_Luminance changed from 88 to 52
2018-08-19 16:43:56.004 [vent.ItemStateChangedEvent] - Living_Luminance changed from 52 to 59
2018-08-19 17:13:46.609 [vent.ItemStateChangedEvent] - Living_Luminance changed from 59 to 28
2018-08-19 17:43:37.379 [vent.ItemStateChangedEvent] - Living_Luminance changed from 28 to 26
2018-08-19 18:13:28.645 [vent.ItemStateChangedEvent] - Living_Luminance changed from 26 to 16
2018-08-19 18:43:19.857 [vent.ItemStateChangedEvent] - Living_Luminance changed from 16 to 5
2018-08-19 19:13:12.776 [vent.ItemStateChangedEvent] - Living_Luminance changed from 5 to 1
2018-08-19 19:42:53.774 [vent.ItemStateChangedEvent] - Living_Luminance changed from 1 to 0
2018-08-20 06:39:24.730 [vent.ItemStateChangedEvent] - Living_Luminance changed from 0 to 1
2018-08-20 07:09:16.434 [vent.ItemStateChangedEvent] - Living_Luminance changed from 1 to 3
2018-08-20 07:38:58.467 [vent.ItemStateChangedEvent] - Living_Luminance changed from 3 to 8
2018-08-20 08:08:58.790 [vent.ItemStateChangedEvent] - Living_Luminance changed from 8 to 5
2018-08-20 08:38:49.581 [vent.ItemStateChangedEvent] - Living_Luminance changed from 5 to 10
2018-08-20 09:08:38.366 [vent.ItemStateChangedEvent] - Living_Luminance changed from 10 to 15
2018-08-20 09:38:27.537 [vent.ItemStateChangedEvent] - Living_Luminance changed from 15 to 45
2018-08-20 10:08:19.623 [vent.ItemStateChangedEvent] - Living_Luminance changed from 45 to 30
2018-08-20 10:38:11.839 [vent.ItemStateChangedEvent] - Living_Luminance changed from 30 to 17
2018-08-20 11:08:04.040 [vent.ItemStateChangedEvent] - Living_Luminance changed from 17 to 88
2018-08-20 11:37:44.882 [vent.ItemStateChangedEvent] - Living_Luminance changed from 88 to 67
2018-08-20 12:07:45.422 [vent.ItemStateChangedEvent] - Living_Luminance changed from 67 to 46
2018-08-20 12:37:36.916 [vent.ItemStateChangedEvent] - Living_Luminance changed from 46 to 94
2018-08-20 13:07:28.585 [vent.ItemStateChangedEvent] - Living_Luminance changed from 94 to 113
2018-08-20 13:37:09.782 [vent.ItemStateChangedEvent] - Living_Luminance changed from 113 to 33
2018-08-20 13:37:19.564 [vent.ItemStateChangedEvent] - Living_Luminance changed from 33 to 32
2018-08-20 14:07:11.617 [vent.ItemStateChangedEvent] - Living_Luminance changed from 32 to 27
2018-08-20 14:37:01.934 [vent.ItemStateChangedEvent] - Living_Luminance changed from 27 to 22
2018-08-20 15:06:51.845 [vent.ItemStateChangedEvent] - Living_Luminance changed from 22 to 52
2018-08-20 15:36:42.087 [vent.ItemStateChangedEvent] - Living_Luminance changed from 52 to 22