I was able to set the device to
- on-time (parameter 2) - 3 min
polling-time - 10 min
With these settings I was hoping to see on/off every 3 min (or every ~10 min since it was mentioned here that triggering an off/on event be a combination of both the polling-time and the on-time) but I did not see such events.
The log file shows a Queue full error on the zwave thread (note1) so maybe the missing events problem is not related to specifically to the device this time (I’ll add another device and check if the missing events were specific to the device or due to a more general zwave problem).
@chris, do you know what could cause the Queue full error on the zwave thread?
– note1 - Queue full error on the zwave thread
cat /var/log/openhab2/openhab.log ... 2017-04-17 05:43:28.805 [ERROR] [WaveSerialHandler$ZWaveReceiveThread] - Exception during ZWave thread. java.lang.IllegalStateException: Queue full at java.util.AbstractQueue.add(AbstractQueue.java:98)[:1.8.0_121] at java.util.concurrent.ArrayBlockingQueue.add(ArrayBlockingQueue.java:312)[:1.8.0_121] at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager.processReceiveMessage(ZWaveTransactionManager.java:345)[200:org.openhab.binding.zwave:126.96.36.199704162057] at org.openhab.binding.zwave.internal.protocol.ZWaveController.incomingPacket(ZWaveController.java:1215)[200:org.openhab.binding.zwave:188.8.131.52704162057] at org.openhab.binding.zwave.handler.ZWaveControllerHandler.incomingMessage(ZWaveControllerHandler.java:636)[200:org.openhab.binding.zwave:184.108.40.206704162057] at org.openhab.binding.zwave.handler.ZWaveSerialHandler$ZWaveReceiveThread.run(ZWaveSerialHandler.java:320)[200:org.openhab.binding.zwave:220.127.116.11704162057]