I am changing from Vera to Hubitat. I have a dozen of the Jasco 26933 wall dimmers with sensors and they worked well with the Vera. In Vera I adjusted the parameters to "manual" and sensitivity on "high".
After pairing the 26933 to Hubitat I changed the parameters to "manual" and sensitivity to "high" but it is clear that the sensitivity is not on high. I repaired a 26933 to Vera and set it to high and tested it to see when it activated. It activated at about 10 feet with very little movement. Then I paired the same sensor to Hubitat and set it to high. I had to be about 4 feet away with lots of movement.
I tried this on another unit and got the same results.
Is there a way to look at the parameters in the unit to see if the change has actually taken place? At this point it appears that Hubitat is not setting sensitivity to high.
Interesting, I think you're right, will update shortly...
Yeah, they are backwards.
low == high and high == low.
I'll get this fixed in the next hotfix, in the mean time set the preference to low.
I will leave it at high in anticipation of you fixing it. I can live with jumping up and down for 5 minutes to get it to respond. I need the exercise.....8-}
On another note does this unit update the time stamp if there is continuous motion or does it keep the original activate time stamp? I have been trying to see how the time stamp works.
Um, not so sure. I use Jason Bottjen’s (@JasonJoel’s) excellent component drivers for the 26931 and 26933, and this exact same discussion occurred in this forum a few years back when those drivers were released. I believe that the consensus was that the parameter’s name, as given by Jasco, is backwards from the defined operation. The parameter is named “motion sensitivity”, but the defined operation is “amount of motion required to turn on light”. Here is a photo of the relevant portion of the manual:
I believe the current operation of the driver matches the documentation. Low amount of motion to turn on light = high sensitivity. It’s Jasco that is confused, and Vera doesn’t match the Jasco documentation. Hubitat’s driver and @JasonJoel’s driver match the Jasco documentation.
Well I have one of these in production and I can confirm the settings in the driver is currently reversed.
I was getting ready to bin the thing due to its lack of sensitivity...
I pulled the parameter values from the z-wave alliance page.
If you set parameter 13 to 1, it requires a High amount of motion to turn the light on, and if you set parameter 13 to 3, it requires a low amount of motion to turn on the light. To me, that seems the opposite of sensitivity. I believe that Jasco screwed up the submitted Z-Wave Alliance parameters table, and tried to fix it by redefining what “High” meant (high amount of motion, not high sensitivity) to avoid recertification after the firmware was frozen.
this is not true.
I just got done testing mine, param 13 was set to 3 and there was quite a bit of motion involved in triggering active, setting the value to 1 required significantly less motion to activate motion active.
Our GE/Jasco driver is being updated to reflect the sensitivity settings being used in our other motion sensor drivers and other devices on the market.
High == highly sensitive to motion
Low == less sensitivity to motion.
Me too. Sorry, Mike, I must have been confused. I have tested it many times myself. My memory is not what it used to be. You will understand when you get old.
I just ran a bunch of tests, and the Hubitat is currently correct with the latest update. If you set sensitivity to high the slightest movement will set it off. If you set it low, it takes a lot of movement to set it off.
It is now responding like it did when I was using them with my Vera unit.
I did go back and double check... On my custom driver high=1 on all of them, so I think the in-box driver is now the same as mine were. Not that that is a requirement or anything, but consistency is nice.
