Testing z-wave binding on openhab-2 runtime environment
Normally for Fibaro you should use Group 3 for the controller. Did set Group 3 for the controller. Maybe there is something wrong with the configuration parameter 24 - tamper operating modes.
From OH1 i know it has a lot of operating modes. Maybe just the text is displayed the wrong way … but maybe it is testing z-wave binding on openhab-2 runtime environment value itself. Bildschirmfoto um Alarm ON was send. After updating the config i have to change parameter 24 to value 1. Reports stop being sent when the vibrations cease. The reports are sent in Sensor Alarm command class. Reports to the association groups are sent using Sensor Alarm command class Available settings: Everything working fine right now!
Looks like Zwave needed some time so set it up right. I have updated the Database of Fibaro Motion Sensor. Now there differences in Parameter are visible. Just updated to the latest OH2 and Zwave binding but no luck so far…. This is not defined in the database as far as I can see for this device and is for sure not a supported class for this device.
In theory, this comes from the device during the discovery. Also Value 4 would not work, because both are including Fibar Command Class. Also shortened the Value-Descriptions so that the differences are visible. Have this so be set for OH2 binding as well? No converter set for state zwave: After a view tries the node is working as aspected. Sometimes startup is logging ZWave timeout is set to ms. Soft reset is false. PIR, temperature, lux are working.
Triggering a tamper alarm again by shaking the device results in:. So what to to? So that this get correct by the healing process itself? Is this the way this is working? This error is not related to the soft reset option. It is related to startup initialisation sequencing and should be fixed in the next version I hope! Maybe there is a communication testing z-wave binding on openhab-2 runtime environment - maybe the device is too far so not all messages are received?
The security report is not related to the alarm report you see later in the log. Can you describe your problem testing z-wave binding on openhab-2 runtime environment please? Maybe i wakeup the device to often so that i interrupt the testing z-wave binding on openhab-2 runtime environment of discovering device and functions?
Then… one device is working, but the next one broke… And so on. The same setup worked perfectly with OH1. Nothing on the environment have changed. Between not working and working i restarted the Raspberry. I parallel reinitialized the nodes not working correct. Each after the other. Maybe there is crashing something in the background? After restarting OH2 i could proceed…. Just updated to the latest OH2 and Zwave binding but no luck so far… No messages returned from converter.
Hey, whats about that from OH1 Binding? ZWaveSerialHandler] - Serial port is initialized ZWaveController] - ZWave timeout is set to ms. ModelRepositoryImpl] - Loading model 'default. ModelRepositoryImpl] - Loading model 'rrd4j. Node found SerialApiGetInitDataMessageClass] - Sometimes startup is logging ZWave timeout is set to ms. Sorry … again … there still some problems with PIR and Tamper. Triggering a tamper alarm again by shaking the device results in: No - this is currently not enabled at all in the OH2 binding.
Got it - thanks. Take a look at the end of the look. I splitter two blocks and wrote down some clues. Thats not from the log.
That happens right now: Received Sensor Binary Request v1 ZWaveController] - Notifying event listeners: Got an event from Z-Wave network: ZWaveCommandProcessor] - Checking transaction complete: This is probably related to the startup issue that I mentioned earlier.
Even with restarts all is good. That startup issue is because serial port initialization happens after node initialization? Controller failed to register event handler. Sometimes a get this error message in die logfiles.
Already processed another send data request for this callback Id, ignoring. Timeout while sending message. Requeueing - 0 attempts left! ThingUpdatedEvent ] - Thing 'zwave: