Double Events in stock Generic Z-Wave Contact Sensor driver

storageanarchy · July 24, 2019, 3:05pm

(I also emailed this to support)

I recently moved 4ea Ecolink DWZWAVE2.5-ECO contact sensors from my SmartThings hub to my Hubitat hub, where it was assigned the “Generic Z-Wave Contact Sensor” driver.

Although this never happened on SmartThings, this device/driver combo on Hubitat is pretty consistently reporting double events for Open and Closed, as shown in the Live Logging snippet below:

[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:48:09.000 am [ **debug** ](http://192.168.1.194/device/edit/833)parsed 'zw device: 63, command: 7105, payload: 00 00 00 FF 06 16 00 00 00 , isMulticast: false' to [[name:contact, value:open, descriptionText:Driveway Sensor Lower was opened]]
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:48:08.998 am [ **debug** ](http://192.168.1.194/device/edit/833)parsed 'zw device: 63, command: 3003, payload: FF FF , isMulticast: false' to [name:contact, value:open, descriptionText:Driveway Sensor Lower was opened]
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:48:08.996 am [ **info** ](http://192.168.1.194/device/edit/833)Driveway Sensor Lower was **opened**
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:48:08.994 am [ **info** ](http://192.168.1.194/device/edit/833)Driveway Sensor Lower was **opened**
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:48:08.990 am [ **debug** ](http://192.168.1.194/device/edit/833)NotificationReport cmd:NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:6, event:22, sequence:false, eventParametersLength:0, eventParameter:[])
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:48:08.987 am [ **debug** ](http://192.168.1.194/device/edit/833)SensorBinaryReport cmd:SensorBinaryReport(sensorValue:255)
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:47:43.194 am [ **debug** ](http://192.168.1.194/device/edit/833)parsed 'zw device: 63, command: 3003, payload: 00 FF , isMulticast: false' to [name:contact, value:closed, descriptionText:Driveway Sensor Lower was closed]
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:47:43.180 am [ **info** ](http://192.168.1.194/device/edit/833)Driveway Sensor Lower was **closed**
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:47:43.150 am [ **debug** ](http://192.168.1.194/device/edit/833)parsed 'zw device: 63, command: 7105, payload: 00 00 00 FF 06 17 00 00 00 , isMulticast: false' to [[name:contact, value:closed, descriptionText:Driveway Sensor Lower was closed]]
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:47:43.148 am [ **info** ](http://192.168.1.194/device/edit/833)Driveway Sensor Lower was **closed**
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:47:43.146 am [ **debug** ](http://192.168.1.194/device/edit/833)SensorBinaryReport cmd:SensorBinaryReport(sensorValue:0)
[dev:833](http://192.168.1.194/logs#dev833)2019-07-24 10:47:43.132 am [ **debug** ](http://192.168.1.194/device/edit/833)NotificationReport cmd:NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:6, event:23, sequence:false, eventParametersLength:0, eventParameter:[])

These events are being recorded, as shown in the event log for the device below:

Name	Value	Description Text	Source	Date
contact	open	Driveway Sensor Lower was opened	DEVICE	2019-07-24 10:48:08.999 AM EDT
contact	open	Driveway Sensor Lower was opened	DEVICE	2019-07-24 10:48:08.998 AM EDT
contact	closed	Driveway Sensor Lower was closed	DEVICE	2019-07-24 10:47:43.205 AM EDT
contact	closed	Driveway Sensor Lower was closed	DEVICE	2019-07-24 10:47:43.147 AM EDT

Looking closely at the Live Log, you can see that the events is being reported for both the 7105 and the 3003 commands (each with different payloads). This is causing untold issues with apps and routines having to deal with duplicated events.

I'm pretty sure this shouldn't be happening...can it be fixed/prevented?

Thanks!

Barry

snell · July 24, 2019, 3:26pm

So it appears the device is reporting the contact as part of the basic set of Z-Wave response AND the more specific alarm/alert set (cannot remember the exact name). There are drivers folks have written than can ignore duplicates like this. You may be able to find one with a quick search.

aaiyar · July 24, 2019, 3:36pm

Tagging @JasonJoel - I believe he has written a custom driver for several Ecolink sensors that fixes this issue.

snell · July 24, 2019, 3:59pm

Not to just pass the buck before... But the WADWAZ driver I am working on would prevent this because it checks the current state before sending an event. I hope to put a project post up about it in the next few days when I get a couple more hours into it the next couple nights.

While that would be for that sensor, the basics are pretty generic so it should be possible to remake it for the Ecolink.

chuck.schwer · July 24, 2019, 4:28pm

The system does this as well. it is not needed in a driver. The problem here is a race condition, the 2 messages come in 1 ms apart, that is not enough time for the driver to update the state to open in the database, so the first and second message are processed at the same time. You would see the same problem with your driver. One of the 2 messages needs to be ignored.. I don't know if that is a setting on the device to not send it (the preferable option, since less messages on the network is always better) or if it is a setting in the driver to ignore the incoming message.

snell · July 24, 2019, 4:36pm

Hmm... I saw this case early on with mine but not since I started performing my checks against the states I am setting. I will try to remember to look again.

storageanarchy · July 24, 2019, 6:23pm

Chuck -

Any chance of getting a fix out to us soon?

In my searches, it appears this specific problem with Ecolink devices was reported over a year ago - I would hope a fix is almost ready to release, no?

chuck.schwer · July 24, 2019, 8:15pm

Considering I just found out about it, it will go on the list, I don't have a date for you.

storageanarchy · July 24, 2019, 9:11pm

Understood.

The problem has been discussed in the community before, and is not limited to just the Ecolink Contact Sensors, apparently. In my searches, I found reports of issues with many different Ecolink devices, and with other vendors.

Here's another community report on the Ecolink contact sensors: Ecolink Contact Sensor

Probably there's a parameter setting that will stop the devices sending 2 notifications.

TIA

mike.maxwell · July 24, 2019, 9:25pm

This is fixed in platform 2.1.3

mik3 · July 24, 2019, 9:55pm

Awesome! You guys rock!

Will it be a specific driver or will we continue to use the generic driver ?

jtmpush18 · July 25, 2019, 2:20pm

Gosh!
I didn't even get a chance to put in my two cents worth, and say "My Ecolink sensors are doing the same thing!"
You guys fix things fast!

snell · July 25, 2019, 2:31pm

I tried more with my WADWAZ driver last night and was hitting the duplicate bug also no matter what code I put in to validate and prevent it... So they come in so fast it cannot evaluate and change the variable before the next one is in and validating against that same variable.

aaiyar · July 25, 2019, 3:20pm

Interesting - I haven't run into this issue with the generic driver and the WADWAZ-1 contact sensor.

snell · July 25, 2019, 4:34pm

I did not originally either. But when I was playing around more last night I could hit it. It only happens with the internal sensor. The result is it provides an Alarm report (the normal item) and a Basic report at the same time. The Basic does not get sent when the external sensor is triggered.

snell · July 26, 2019, 1:13am

I upgraded my test Hubitat with 2.1.3 and can no longer produce the duplicate with my WADWAZ driver either so it looks like a more general fix not just for the devices listed for that version.

mike.maxwell · July 26, 2019, 1:49am

Well that's good news, we just noted the ones that we tested with...

snell · July 26, 2019, 1:51am

That is what I expected, thus why I thought it might not hurt to let you know here. Plus a heads-up for anybody watching this thread that might have missed the update itself.

storageanarchy · August 7, 2019, 6:22pm

So, while my Ecolink contact sensors now behave more appropriately, I find today that ALL of my (older) Ecolink motion sensors (Model: PIR-ZWAVE2) are exhibiting even worse behavior - reporting multiples of duplicate active/inactive events in a row...

Oddly, these "appear" to stop if you turn ON debug logging, but that may be an artifact of what the code reports depending upon the debug/info logging setting.

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 01:57:56.765 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:37:01.533 pm [warn](http://192.168.1.173/device/edit/1314)debug logging disabled...

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:56.700 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:56.690 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:56.589 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:56.571 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:56.567 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:56.417 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:56.131 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:55.732 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:55.556 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:55.215 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:55.138 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:55.102 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:54.942 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:54.899 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:54.817 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:53.219 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:53.122 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:25:53.090 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:22.390 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:22.373 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:22.341 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:20.891 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:20.823 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:20.795 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:20.659 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:20.615 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:20.584 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:20.050 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:20.003 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:19.967 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:19.933 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:18.705 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:21:18.662 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:20:25.079 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:19:24.555 pm [warn](http://192.168.1.173/device/edit/1314)description logging is: true

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:19:24.553 pm [warn](http://192.168.1.173/device/edit/1314)debug logging is: false

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:19:24.549 pm [info](http://192.168.1.173/device/edit/1314)updated...

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:13:22.934 pm [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:13:22.926 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:13:22.923 pm [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:0)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:07:11.933 pm [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: FF , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:07:11.927 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:07:11.924 pm [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:255)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:07:01.452 pm [warn](http://192.168.1.173/device/edit/1314)description logging is: true

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:07:01.449 pm [warn](http://192.168.1.173/device/edit/1314)debug logging is: true

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:07:01.446 pm [info](http://192.168.1.173/device/edit/1314)updated...

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:05:36.584 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:02:14.597 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:01:44.494 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:01:39.729 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:01:39.657 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 12:01:39.641 pm [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:34:06.226 am [warn](http://192.168.1.173/device/edit/1314)debug logging disabled...

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:27:03.175 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:27:03.167 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:27:03.160 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:0)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:23:11.480 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: FF , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:23:11.452 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:23:11.447 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:255)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:24.215 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:24.173 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:24.168 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:0)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:24.129 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:24.103 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:24.097 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:0)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:23.149 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:23.145 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:23.143 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:0)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:23.079 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:23.074 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:23.071 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:0)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:23.005 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:23.002 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:22.999 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:0)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:21.379 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:21.365 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:21.351 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:0)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:20.181 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:20.177 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:08:20.174 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:0)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:05:09.362 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 8003, payload: 64 , isMulticast: false' to [[name:battery, unit:%, value:100, descriptionText:Office Motion Sensor (old) battery is 100%], 8408]

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:05:09.357 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) battery is 100%

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:05:09.210 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 8407, payload: , isMulticast: false' to hubitat.device.HubMultiAction@95d207

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:05:09.196 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) tamper is clear

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:05:09.178 am [debug](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) woke up

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:05:01.917 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 7105, payload: 00 FF 00 FF 07 03 01 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:05:01.899 am [debug](http://192.168.1.173/device/edit/1314)NotificationReport(v1AlarmType:0, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:3, sequence:false, eventParametersLength:1, eventParameter:[0])

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:52.047 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 7105, payload: 00 FF 00 FF 07 03 01 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:52.044 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) tamper is detected

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:52.031 am [debug](http://192.168.1.173/device/edit/1314)NotificationReport(v1AlarmType:0, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:3, sequence:false, eventParametersLength:1, eventParameter:[0])

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:50.813 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 3003, payload: FF , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:50.809 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:50.806 am [debug](http://192.168.1.173/device/edit/1314)SensorBinaryReport(sensorValue:255)

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:49.627 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 8407, payload: , isMulticast: false' to hubitat.device.HubMultiAction@9f4fcc

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:49.600 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) tamper is clear

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:49.593 am [debug](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) woke up

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:36.210 am [debug](http://192.168.1.173/device/edit/1314)parsed 'zw device: 0D, command: 7105, payload: 00 FF 00 FF 07 03 01 00 , isMulticast: false' to []

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:36.206 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) tamper is detected

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:36.189 am [debug](http://192.168.1.173/device/edit/1314)NotificationReport(v1AlarmType:0, v1AlarmLevel:255, reserved:0, notificationStatus:255, notificationType:7, event:3, sequence:false, eventParametersLength:1, eventParameter:[0])

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:06.175 am [warn](http://192.168.1.173/device/edit/1314)configure...

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:02.299 am [warn](http://192.168.1.173/device/edit/1314)description logging is: true

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:02.296 am [warn](http://192.168.1.173/device/edit/1314)debug logging is: true

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 10:04:02.293 am [info](http://192.168.1.173/device/edit/1314)updated...

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 09:54:38.934 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 09:51:29.839 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 09:39:32.256 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) battery is null%

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 09:39:31.659 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) battery is null%

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 09:39:31.448 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) battery is null%

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 09:39:31.093 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) battery is null%

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 09:07:00.183 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 09:06:27.204 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:58:19.781 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:58:19.619 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:58:19.616 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:58:19.052 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:58:18.876 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:58:18.814 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:58:17.599 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:58:17.564 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:58:17.525 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:57:20.853 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:57:20.786 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:57:20.490 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:57:20.459 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:57:20.376 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:57:20.138 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:57:13.753 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:57:12.435 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:57:11.109 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:56:38.035 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:56:37.395 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:56:37.074 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:56:36.949 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:56:36.490 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:56:36.429 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:56:36.365 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is active

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:55:49.186 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:55:48.008 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

[dev:1314](http://192.168.1.173/logs#dev1314)2019-08-07 08:55:46.862 am [info](http://192.168.1.173/device/edit/1314)Office Motion Sensor (old) is inactive

@mike.maxwell - is there any chance these extraneous, repeated events can be eliminated also?

lightingdan · September 7, 2019, 12:44am

Was having this problem still on the latest version of HE software. Decided to just try something crazy and switched my driver from the Generic Z Wave Contact Sensor to the Fibaro Door/Window 2 Sensor driver.

Problem solved. No more multiple open or close events. Just one open and one close for each open and close of my door.