All,
I have taken ownership of this DTH (with @jwillaz permission, of course) and have updated it. The discussion continues here:
I have the same problem with the sensor reporting continuous motion. I can see it go to no motion and then back to motion immediately every 4 minutes. This also occurred after a battery change. Its also eating batteries as this is the second change in 6 months.
Anyone have Ideas
Are you using the latest DTH:
1 Like
Yes
Iāve tried that and the basic Z-wave motion sensor one. Seems to be something with the device. I will try pulling the batteries again tonight and see what happens.
I recommend pairing it right next to the hub then make sure it sits there for a bitā¦they have to exchange security keys. However, if it still exhibits the behavior next to the hub you may have a defective device.
Last Night I removed batteries and removed and readded the device to my network. Seemed to work. I then moved it to its normal location and ran a zwave repair. Device worked fine all night and was responsive but slow in the morning. I then attempted to change settings for time and sensitivity in ST. Hitting the button on the device after. I set the time to 1 minute. The device is now back to reporting motion every 1 minute. It reports no motion and then about 300ms later it reports motion.
Using the latest DH
Sounds like a device issue. Do you have a good āmeshā built that allows for clean transmission?
No problems with other devices. This device is about 25 feet from the hub so I doubt it is an interference issue. Iām guessing it is defective or something is getting buggered in the setup.
Seems like itā¦I donāt have the same issues as you.
How is your battery life?
The one I have had for 3 months is down to 58% but it is in a high-traffic area. So, not as good as I have seen 
Did you get yours to keep the settings? I changed my DH which exposed the parameters for the 255/5s, it works for a period of time but then reverts back to the original settings. I also changed the DH, pressed the button, changed the parameter 18 to 255, pressed the button on sensor, changed back to the original generic zwave motion sensor, pressed button on back of sensor,. In IDE, under My Devices it shows the correct settings. It works for about 10 minutes then reverts back to original settings. Any help would be greatly appreciated or if I left out any details.
@cmmvweb I took mine back to the default settings and live with it performing as designed. I believe it was wearing on the batteries a bit more than it should have. I donāt think battery wear is as bad now (using default settings).
Iāve found that the Loweās Iris Motion Sensors fit my applications as well or better.
I donāt believe Iād buy another GE Smart Motion Sensor. It works, but the cons seem to be worse than other motion sensors. Price-wise the Iris sensors can be purchased for less than $15 and seem to work just about as well.
Luke
Iāll take a look at the Iris sensors. Thanks for getting back. Been fighting this for so long and the settings will never stick for some reason.
I know this is an old thread, however, I ran into the same issues as a lot of these posters so I wanted to post what worked for me. This may help others.
First, I noticed that if I add the motion sensor with the new SmartThings app, it gets added as a Window/Door Sensor. If I add it using the older SmarthThings Classic app - it gets added correctly as a Motion Sensor.
Second, I was running into the same issue with a lot of posters where after the initial batteries died, I replaced them. The issue I had was that it was constantly reporting motion - every 1-5 minutes, constantly. I was using li-ion rechargeable batteries and I believe thatās what was causing the constant reporting. It would work just fine using a USB power cord. I bought a set of non-rechargeable batteries and now itās working just fine. It must be something with the rechargeable batteries that I was using. I ended up using Surefire CR123a from Lowes.
Hope that helps someone -