I recently setup an Ecolink Z-Wave PIR sensor (PIRZWAVE2-ECO), and it works well. I have two gripes with it:
1.) The “reset” time is way too long (4 minutes), and so far as I know that cannot be changed
2.) Even at max sensitivity, it still takes five seconds or so for it to actually turn the light on. And that is with the motion sensors mounted in the best place I could find. Even if I wave in front of it, it still takes five seconds or so to react.
Does anyone know if it’s possible to improve the reaction time?
Coming late to the party (as usual) but in the interest of leaving breadcrumbs for future readers:
The reset time can be reduced to 4-5 seconds by putting the jumper on internally in the “TEST” position. I’ve done this on several of these in my own home, and aside from the desired shorter reset time, I have not seen any side-effects.
I also have this issue, but only occasionally. I think it has more to do with the Vera’s response time and processing through PLEG than the sensor itself, in my case. I haven’t tested a direct association to see if it behaves differently/better, since it’s only occasionally that it’s slow for me.
Surprise! You can in fact change reset times programmatically instead of the jumper.
First, make sure you aren’t in “Test” mode on the jumper.
The default time from the factory is 4 minutes. This can be changed programmatically in 1 minute resolutions.
I’m using UI5 as an example, on the Device Options tab (for that device) you want to add:
Variable = 1
Data Size = 1 byte hex
Desired value = X (where X is how many minutes you want for a motion reset).
This should work for all the Ecolink/Schlage/MonoPrice motion sensor clones. They all use the same internal integrated circuit.
[quote=“TC1, post:3, topic:183460”]Surprise! You can in fact change reset times programmatically instead of the jumper.
First, make sure you aren’t in “Test” mode on the jumper.
The default time from the factory is 4 minutes. This can be changed programmatically in 1 minute resolutions.
I’m using UI5 as an example, on the Device Options tab (for that device) you want to add:
Variable = 1
Data Size = 1 byte hex
Desired value = X (where X is how many minutes you want for a motion reset).
This should work for all the Ecolink/Schlage/MonoPrice motion sensor clones. They all use the same internal integrated circuit.
Hope this helps,
-TC[/quote]
Are you kidding me? This works on the Schlage ones? I knew (and have used) it on my Monoprice ones, but I didn’t know I could do it on my Schlage ones!! This is most excellent news as I need/want the pet detection!
@SirMeili, it should work, I know for a fact it works on the MPs and one other clone brand. From a hardware POV, they are all almost identical. Please try it and let us know how it works out.
[quote=“TC1, post:3, topic:183460”]Surprise! You can in fact change reset times programmatically instead of the jumper.
First, make sure you aren’t in “Test” mode on the jumper.
The default time from the factory is 4 minutes. This can be changed programmatically in 1 minute resolutions.
I’m using UI5 as an example, on the Device Options tab (for that device) you want to add:
Variable = 1
Data Size = 1 byte hex
Desired value = X (where X is how many minutes you want for a motion reset).
This should work for all the Ecolink/Schlage/MonoPrice motion sensor clones. They all use the same internal integrated circuit.
This was a no go on my Schlages as well. I get the same message as @wezley69 until I remove the device option and reconfigure. It was worth a try though. My guess is that they have perhaps different “firmware” on them.
It works on my MonoPrice ones under UI7 so it’s not an UI issue. It may indeed be a firmware issue although I can’t see why they would take that out for the Schlage and Ecolink ones as they are default to the Vision one. Which is the one all these are modeled after. The MonoPrice ones alsoi have the pet sensors but those are no match for my 70 to 80lbs GSD’s.
To set the variable in UI7
Go to Device Options for the sensor
Select ‘Add Configuration Setting’
For the ‘Variable’ field enter the number 1
For the ‘Data Size’ field select ‘1 byte hex’
For the ‘Desired value’ field enter the number of minutes you want for the time out. I entered the number 1
[quote=“BOFH, post:11, topic:183460”]It works on my MonoPrice ones under UI7 so it’s not an UI issue. It may indeed be a firmware issue although I can’t see why they would take that out for the Schlage and Ecolink ones as they are default to the Vision one. Which is the one all these are modeled after. The MonoPrice ones alsoi have the pet sensors but those are no match for my 70 to 80lbs GSD’s.
To set the variable in UI7
Go to Device Options for the sensor
Select ‘Add Configuration Setting’
For the ‘Variable’ field enter the number 1
For the ‘Data Size’ field select ‘1 byte hex’
For the ‘Desired value’ field enter the number of minutes you want for the time out. I entered the number 1[/quote]
The firmware can be the only difference I can think of. I also have my Monoprice ones using this, so I know it’s works on those. I wish it would work, but alas it is a no go
It is indeed strange (and unfortunate) that it works on at least two other clone versions of this sensor and not on a couple of others. My apologies if I got folks’ hopes up unnecessarily
It didn’t work for me either. Failed at Setting user configuration. I’m on UI5. Ahh well… 5 second ain’t bad. This is good to know though if I ever get the Mono Price ones…
I was just thinking. Another major difference between the Monoprice and Schlages is the “temp” sensor they include. Perhaps the newer Monoprice are based on the Schlage, but they do have other differences which might explain why the Schlages don’t work.
Could be, it seems the MP and the Vision ZP 3102 are cousins, hence why it works in both of them. I could have sworn the setting worked in other PIR sensors, but maybe you are right, only the ones with the added temp function.
