Hi. New to OH but I’ve managed to get everything working with the exception of two Z wave devices. The devices report back as’ ZD2102 Door Window Sensor’ and ‘ZG8101 Garage Door Tilt Sensor’. These devices show up in habmin and the garage sensor occasionally reports it’s battery level. I think the door sensor may have reported the battery sensor level before as well. Neither report their statuses (open/closed). I am using org.openhab.binding.zwave-1.8.3.jar binding. I see that both devices are listed at https://github.com/openhab/openhab/tree/master/bundles/binding/org.openhab.binding.zwave/database/vision
My devices look like this:
Contact Door_Laundry "Laundry Door [%s]" <door> (Laundry,Doors) { zwave="6:command=SENSOR_BINARY,respond_to_basic=true,sensor_type=10" }
Number Door_Laundry_Battery "Laundry Door battery [%d %%]" <battery> (Laundry,Battery) { zwave="6:command=BATTERY" }
Contact Door_Garage "Garage Door [%s]" <door> (Garage,Doors) { zwave="7:command=SENSOR_BINARY,respond_to_basic=true,sensor_type=10" }
Number Door_Garage_Battery "Garage Door battery [%d %%]" <battery> (Garage,Battery) { zwave="7:command=BATTERY" }
Can anyone help me troubleshoot this? Many thanks!
No, that’s weird:
The green node 7 does work and has no association to the controller?
And the grey node 6 does not work and has an association to the controller???
Or is it the other way around?
In either case: add node 7 to node 1 in the association … like it is for node 6.
Edit: could be you have two problems: first one node 6 is not fully initialized, wake it up several times manually, second, note 7 does not report to the controller because the association is not set.
When you say wake it up, are you saying open/close the door a bunch of times? I’ve added node 7 to node 1. ‘Member’ shows up as yellow which I’m guessing is because the sensor is sleeping.
No, opening/closing doesn’t wake it up, there should be a little button on the device (often the same button you have used to include it to the zwave network), this sends a NIF and sends data to the controller. You may have to do that several times.
@sihui Thanks again for working with me on this. This is what the manual says:
For “Inclusion” in (adding to) a network: Put the Z-Wave™ Interface Controller into
“inclusion” mode, and following its instruction to add the ZD2102 to your controller. To
get in the “inclusion” mode, the distance between sensor and controller is suggested
to be in one meter. Press the program switch of ZD2102 for 1 second at least.
-1-
The LED on the ZD2102 should go solid, if not, please try again.
For “Exclusion” from (removing from) a network: Put the Z-Wave™ Interface
Controller into “exclusion” mode, and following its instruction to delete the ZD2102 to
your controller. Press the program switch of ZD2102 for 1 second at least to be
excluded.
For “Association”: removing the cover of the ZD2102 to get into the “Awake” mode,
then put the Z-Wave™ Interface Controller into “Association”, and following its
instruction to associate the ZD2102 with other device. Close the cover back after
“association” done, afterward the ZD2102 will get into “Sleep” mode for power saving.
Support one association group (5 nodes).
”Awake” mode: it is to leave the “Sleep” mode by removing the cover of ZD2102, to
allow the Z-Wave™ Interface Controller to do “Inclusion”, “Exclusion”, “Association”
and to reply and receive the commands from controller. http://download.telldus.se/Manuals/Z-Wave/Vision/ZD2102.pdf
So I’m guessing I need to pull the cover and bring the device close to the controller (Z Stick 2) and it will automatically update? Again, I’m away from home so I can’t try this until this evening.
Yes. I followed the directions sihui provided and the device worked very near the controller but not on location. I changed the battery and it now works on location and has operated without problem for many weeks now. Good luck.
In my case, it was new out of the box, and the distance is about 6meters. And it’s the same for 2 different garage sensors. So I doubt it would be an issue with the battery itself?
I see in the logs a lot of entries when I tamper the key, but no association so for. I’ve also tried to excluded it, and re-included it.
What do you mean by this? What are the messages you’re seeing - are they NIF, or are they tamper messages?
If an association is set, then you will see entries when the tamper, or door sensor is set. If there’s no association set, then you won’t get any messages.
Maybe wrong choice of name.
This is the output when I push the button on the sensor:
2016-07-23 07:25:04.121 [DEBUG] [.ApplicationUpdateMessageClass:47 ]- NODE 29: Application update request. Node information received.
2016-07-23 07:25:04.122 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 16 NIF event during initialisation stage PING
2016-07-23 07:25:04.122 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 39 NIF event during initialisation stage PING
2016-07-23 07:25:04.122 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 32 NIF event during initialisation stage PING
2016-07-23 07:25:04.122 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 33 NIF event during initialisation stage PING
2016-07-23 07:25:04.122 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 24 NIF event during initialisation stage PING
2016-07-23 07:25:04.123 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 31 NIF event during initialisation stage PING
2016-07-23 07:25:04.123 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 38 NIF event during initialisation stage PING
2016-07-23 07:25:04.123 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 17 NIF event during initialisation stage PING
2016-07-23 07:25:04.123 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 30 NIF event during initialisation stage PING
2016-07-23 07:25:04.123 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 9 NIF event during initialisation stage PING
2016-07-23 07:25:04.123 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 8 NIF event during initialisation stage PING
2016-07-23 07:25:04.123 [DEBUG] [z.i.p.i.ZWaveNodeStageAdvancer:1060]- NODE 29: 26 NIF event during initialisation stage PING
2016-07-23 07:25:04.123 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:411 ]- NODE 29: Is awake with 0 messages in the wake-up queue.
2016-07-23 07:25:04.124 [DEBUG] [z.internal.ZWaveNetworkMonitor:701 ]- NODE 29: Heal WakeUp EVENT SAVE
2016-07-23 07:25:04.124 [DEBUG] [z.internal.ZWaveNetworkMonitor:575 ]- NODE 29: NETWORK HEAL - SAVE
2016-07-23 07:25:04.126 [DEBUG] [.b.z.i.p.i.ZWaveNodeSerializer:107 ]- NODE 29: Serializing to file /var/lib/openhab/zwave/node29.xml
2016-07-23 07:25:05.128 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:506 ]- NODE 29: No more messages, go back to sleep
2016-07-23 07:25:05.128 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:202 ]- NODE 29: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2016-07-23 07:25:05.129 [DEBUG] [o.b.z.i.protocol.SerialMessage:109 ]- NODE 29: Creating empty message of class = SendData (0x13), type = Request (0x00)
2016-07-23 07:25:05.130 [DEBUG] [WaveController$ZWaveSendThread:1268]- NODE 29: Sending REQUEST Message = 01 09 00 13 1D 02 84 08 25 F0 A3
2016-07-23 07:25:05.146 [DEBUG] [b.z.i.p.s.SendDataMessageClass:38 ]- NODE 29: Sent Data successfully placed on stack.
2016-07-23 07:25:05.163 [DEBUG] [b.z.i.p.s.SendDataMessageClass:74 ]- NODE 29: SendData Request. CallBack ID = 240, Status = Transmission complete and ACK received(0)
2016-07-23 07:25:05.164 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:372 ]- NODE 29: Went to sleep
2016-07-23 07:25:05.164 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:435 ]- NODE 29: Is sleeping
2016-07-23 07:25:05.164 [DEBUG] [WaveController$ZWaveSendThread:1327]- NODE 29: Response processed after 34ms/5118ms.
When I check the manual, I should do something with the controller (z-wave gen5 usbstick) to associate it after removing the cover. Not sure what I can do in fe habmin to trigger this.
I’d suggest capturing a full debug log following the binding startup so we can see what is happening. After starting the binding, give it a few minutes then press the button a few times maybe 10 seconds apart and then send me the log.
Thanks already for you effort!
You can find the log file here: 201607230511.txt
The new garage door sensors are NODE 29 & 30.
And I guess I’m having the same issue for the range extender, NODE 40. Not that openhab must do (can?) anything with this device, but I’m thinking that it’s not working if it’s not associated.
Node 29 looks like it’s working perfectly. At least in this log, it completed its initialisation without any problems at all - no timeouts, and all done in a single wakeup (well, one for ping, and one for initialisation).
Node 30 on the other hand looks broken. The controller is reporting that it’s failed, and if this is a battery sensor, this is something I’ve not seen before. I would exclude and re-include node 30.
Node 40 is also initialised fine. I do note that later in the log there is a timeout to a ping, but otherwise it looks ok.
If you want to view the log yourself, you can use the online viewer which will display things in a reasonably nice way.
Ok - so still node 29 is looking ok. There’s no information in the log from node 28. The controller thinks it’s healthy (which is good, but doesn’t mean much as the controller almost never marks a battery device as FAILED).
I note in the log that OH doesn’t try to set the association. The OH1 database is configured to do this automatically, but it might have been added after 1.8.3 so I would recommend upgrading to the latest nightly build from cloudbees.
