Many devices report a binary sensor value. It makes no sense to sendCommand to a sensor and one could argue attempting to do so should generate an error. The Contact Item type works in this way and is intended to be used to represent binary sensor values (e.g. motion sensors, door/window sensors, etc).
Current Behavior
Many (all?) binary sensor values for Zwave devices use the Switch Item type. This has caused some confusion for some new users and it causes extra work for users to present these sensor readings on their sitemap. The following devices I personally use that I know have binary sensors that require Switch instead of Contact.
First Alert Z-Wave Detector: alarm_general and alarm_smoke channels (this alarm does not support triggering the alarm through zwave)
DMMS1 Dome Z-Wave Plus Motion Detector: sensor_binary, and sensor_burglar channels
Possible Solution
To avoid too much disruption, add another Channel that supports linking to Contacts, or modify the Channel so it supports both (possible?). Ideally only Contact should be supported but it has been a long time like this and the breaking changes could cause a lot of disruption.
Steps to Reproduce (for bugs)
Not Applicable
Context
ersonally, it requires extra work to display and use these sensors values as read only on sitemap and HABPanel.
I've also had to spend time on the forums to deal with people who do not understand why noting happens when they sendCommand to an online Channel linked Item. Sending a command to this Channel should be an error (which would be the case if we used Contact).
It also makes it difficult to combine sensors from multiple bindings into a single Group as some binding authors use Switch and others use Contact. Thus if I have other bindings that report online status that require Contacts I can't use Group:Contact:OR(OFF, ON) to see if one is offline and instead have to write a Rule.
Your Environment
Version used: (e.g., openhab and addon versions) OH 2.4 SNAPSHOT 1380
Environment name and version (e.g. Chrome 39, node.js 5.4, Java 8, ...): official OH Docker image
Operating System and version (desktop or mobile, Windows 10, Raspbian Jessie, ...): Ubuntu 18.04
Expected Behavior
Many devices report a binary sensor value. It makes no sense to sendCommand to a sensor and one could argue attempting to do so should generate an error. The Contact Item type works in this way and is intended to be used to represent binary sensor values (e.g. motion sensors, door/window sensors, etc).
Current Behavior
Many (all?) binary sensor values for Zwave devices use the Switch Item type. This has caused some confusion for some new users and it causes extra work for users to present these sensor readings on their sitemap. The following devices I personally use that I know have binary sensors that require Switch instead of Contact.
Possible Solution
To avoid too much disruption, add another Channel that supports linking to Contacts, or modify the Channel so it supports both (possible?). Ideally only Contact should be supported but it has been a long time like this and the breaking changes could cause a lot of disruption.
Steps to Reproduce (for bugs)
Not Applicable
Context
ersonally, it requires extra work to display and use these sensors values as read only on sitemap and HABPanel.
I've also had to spend time on the forums to deal with people who do not understand why noting happens when they sendCommand to an online Channel linked Item. Sending a command to this Channel should be an error (which would be the case if we used Contact).
It also makes it difficult to combine sensors from multiple bindings into a single Group as some binding authors use Switch and others use Contact. Thus if I have other bindings that report online status that require Contacts I can't use Group:Contact:OR(OFF, ON) to see if one is offline and instead have to write a Rule.
Your Environment