Just noticed that the motion sensor of this sensor never gets triggered in OH2 (other sensors work OK). The sensor shows up in Habmin in channels as a binary sensor, and it also shows that it is linked to the appropriate contact item.
If I trigger the sensor I get a few lines in the logs, but nothing else:
18:53:17.098 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@15edd29
18:53:17.098 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘zwave:device:83fcde36:node3’ has been updated.
18:53:17.350 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@159f819
18:53:17.350 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘zwave:device:83fcde36:node3’ has been updated.
Yes, I have it working fairly well I think. Check option 5, which is which type of event to send. I have mine set to send sensor binary. Check parameter 101 as well. You may have this working already from the sounds of it, but to get all values for the multi part of the device, set this value to 241, and set the interval to report to something that works for your setup. My device is on mains power, so I have the auto-send set to 60 seconds which works well with rrd for graphing. If you are running on battery, you may want to set it to 3600 (1 hr) or something to conserve battery.
I am no z-wave expert, but my understanding is the Basic set is just that. It is the basic command class that all devices support, and is limited to get/set. Sensor binary is a more specific class that just reports two states from the sensor. Open/Closed is an example. Depending on the device they can be used almost interchangeably. For no particular reason, I have had better luck with my devices when I use the more specific command classes, in this case sensor binary vs basic. @chris can go into much more depth than I if you want to know more.
Yes, it just selects which command class to use. Using BASIC is more compatible with different devices, since everything supports it. The ALARM provides more information, but is also more complex in that different devices send different data which can make compatability more difficult.
BASIC is generally supported by all devices, so with this setting you can send the alarm to turn on lights etc directly from the device.
I tried both last night, seems the binary_sensor channel in the binding picks up both. I think the reason why it did not work before because it seems to be getting ON/OFF rather than OPEN/CLOSE, so a contact item just not picking up that signal (which worked in OH1), changing to switch item type solved the problem.
Hi @jamborta, I have upgraded my OH2 to the latest version of OH2 & Zwave addon (20160516) and I have the similar issue with my three FIBARO FGMS001 Motion Sensors ! If the type of this items is defined to “Contact” (in .items file), OH2 doesn’t display the value of motion detection. But if the type is defined to “Switch”, all is right (Basic UI, rules).
Basically, you can’t change the item type yourself - you must use the ones defined by the binding. This is a shortcoming of OH2 - the binding has no knowledge of the items, so it defines the types and the items need to respect this. I know this doesn’t always suit, so it might mean we need to add extra channel types.