Running openHab 2.0 on openhabian, I have the aeotek zwave gen 5.
I have a GoControl Door/Windows Sensor It is showing up in my things as a WADWAZ-1 I followed a few of the examples out there and it is not showing any door open or close events or the tamper. when I try and attach it to a my only choice in the paper UI is “switch” and it will not let me select a contact or other device type.
How do I get a contact sensor to show up as a contact and then show me the status of “open/closed”? None of the configuration is making any sense, why is it refusing to let me choose a contact but wants to treat it as a switch?
So far it is… http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/9
It’s not “linear brand” but it looks exactly like that and is identifying as a WADWAZ. as well as the internal board looking 100% identical down to the additional sensor screw terminals. from what I can tell Linear lets hundreds of companies sell their zwave devices as random brand names. The Monoprice unit is the same WADWAZ as far as I can tell from reading the forum here. Everyone I find that has had success is running 1.7 or 1.8 and not 2.0
Maybe I should abandon 2.0 and find a openhabian image with 1.8 on it? it seems that there is far more resources and success out there using the non 2.0 versions.
I would suggest to check if your device is in the database - check the manufacturer, type and id as suggested in the docs. If it’s not there, then it will need to be added.
It says “Linear corp” and Type/ID 2001:0102 firmware 4.84 and is showing up in openhab detected as a WADWAZ-1
that matches what is in the database.
I thought that if a device was not in the database it will not show up as a specific device, IS that wrong? will a device just pick a random device from the database?
Sorry - I misread the last message - I thought it wasn’t showing up.
No - definitely not.
OH2 (actually ESH) is much more prescriptive than OH1, so item types are limited by the system.[quote=“timgray, post:1, topic:29944”]
why is it refusing to let me choose a contact but wants to treat it as a switch?
[/quote]
the sensor_door channel is defined as a contact.
You’ve not said what version you’re running, but if it’s an old one, then maybe it’s been changed?
My versionis whatever comes installed in openHabian it refuses to let anything be a contact. the only choice is switch.
I am starting to suspect that the current openhabian is extremely buggy and incomplete , I just tried to delete channels and they say they delete but they do not go away, I try to delete it again and it says it is not found. refreshing the webpage and it still shows them there.
I get completely different views between paper UI and habmin UI. I think I might actually need to abandon open Habian and openhab 2.0 and go back to the last 1.x release. it seems there is a LOT more control and documentation for the previous versions. Also I am finding more people having success with Zwave on non 2.0 versions here in the forums.
I am not familiar with openHabian, but there is probably 2 versions - the (now old) master, and the snapshot version which will be much more up to date. This should be up to you to decide.[quote=“timgray, post:7, topic:29944”]
Also I am finding more people having success with Zwave on non 2.0 versions here in the forums.
[/quote]
Strange - I don’t find this, but of course you are free to use the older version if you like.
Interesting, I will try the snapshot first then. I am absolutely finding wierd issues with what I have installed. I will start over and only use the snapshot, I see it’s at 2.1 so there has to be a lot fixed in it that may solve my issues.
Completely reinstalled on a clean setup with the “snapshot” release and now I can select “contact” for the binary_sensor.
Running 2017-6-12
Ok it shows up as the WADWAZ-1 on node 2, it’s the only Zwave device right now, but it is now throwing the following errors in the log. every time I open or close the door.
2017-06-14 10:53:47.918 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.IllegalStateException: Could not update state, because callback is missing
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateState(BaseThingHandler.java:267)[106:org.eclipse.smarthome.core.thing:0.9.0.201706091022]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1104)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:567)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveBasicCommandClass.processBasicReport(ZWaveBasicCommandClass.java:111)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveBasicCommandClass.handleApplicationCommandRequest(ZWaveBasicCommandClass.java:85)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:248)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:214)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:208)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1324)[183:org.openhab.binding.zwave:2.1.0.201706122104]
2017-06-14 10:53:47.942 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.IllegalStateException: Could not update state, because callback is missing
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateState(BaseThingHandler.java:267)[106:org.eclipse.smarthome.core.thing:0.9.0.201706091022]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1104)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:567)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass.processNotificationReport(ZWaveAlarmCommandClass.java:194)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveAlarmCommandClass.handleApplicationCommandRequest(ZWaveAlarmCommandClass.java:124)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:248)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:214)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:208)[183:org.openhab.binding.zwave:2.1.0.201706122104]
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1324)[183:org.openhab.binding.zwave:2.1.0.201706122104]
