Tried everything. Nothing works. 
Its fine. Life goes on.
1 Like
Weeks later of to and fro emails to support, the end result, if its over 12 months old, please ask some one on the forum to help 
So this sensor goes in the bin, and I need to buy a new one! 
I would wait a bit with that…
@Brad_ST, knowing that the some Centralite leak sensors has received some firmware incorrectly. What is the chance that the motion sensors has hit something similar?
Could you please have a look on the topic and advise if you can, what could be going on with these motion sensors?
Having worked with motion sensors so much, I do suspect that something went wrong down the line of DTH changes or firmware updates. The odds of finding this should be pretty low because of the amount of testing that the hardware guys would have to do to repro the issue. I don’t want to lose another one of these sensors so I refuse to remove any others from my system. I’ve seen many instances where a small change would result in similar issues. If I’m not wrong, the current DTH is a catch-all for a few sensors from different manufacturers. My suspicion is something with the initial fingerprinting of the device when pairing. Either that or all of these devices have the exact same failure mode after some long term use. Either way it doesn’t seem financially prudent for SmartThings to investigate this further. These are old sensors with a 12 month warranty. They’ve since moved on to bigger things. Looks like a partnership with Aeotec? Maybe someday the sensors will be cheaper to buy and at the very least available.
@impee
You said you removed and added it back. Did you actually do the reset?
When I had a similar issue, removing it and adding it back did not get the motion back.
I had to do the reset procedure on the sensor.
Then add it back and then motion started again.
yep, I reset it about 10 times. Any how I have now thrown it in the bin, as I spent far too many hours trying to get it to work…but it looks like I still didn’t learn my lesson, as I went and bought a new Samsung Motion Sensor, which I would imagine in a few years they will again break it with a buggy \ intentional firmware update.
I have 4 - 5 motion sensors doing this. No way I’m I tossing out $140+ in sensors. Samsung better get this fixed.
1 Like
There’s no way they’re gonna fix this. They’ve pretty much abandoned the whole ST product line. Guess its time to start looking around for another sensor.
Ugh. Me too. I have the exact same sensor and it’s reporting temp but not motion (which is what I need it for). It failed about a week ago and at the time I assumed that it just needed a new battery. I have done the hard reset procedure with a fresh battery. At least now I know that it’s not just me. If anyone makes any headway on this please keep us posted.
Samsung told me to go buy new sensors. They are all broken… I tried to get a discount on new ones also. They basically didn’t care. I am so disappointed. I loved SmartThings… now its just… Time to switch I guess!
Random thought. Will these motion sensors work with any other system? So we could test the sensor. Samsung said it was a faulty sensor but if it works with a different system then we’d know for sure its with smartthings?
Likely would work with Home Assistant, but it would cost you more in time and hardware (Zigbee coordinator) than a new sensor. If you ever think you’ll switch, they’re worth keeping to try.
Old thread, but I have moved across to home assistant since my hub v2 died 3 weeks ago. Can confirm they do not work on home assistant. I have 2 3325-S that stopped working on my smartthings v2 hub awhile ago. I think it must be a firmware corruption.
I have exactly the same problem. After I remove my old motion sensors from a routine, it stopped reporting motion, though temperature are still reported.
My SmartSense Motion Designed by SmartThings (FCC:T3L-SS014 and IC 12192A-SS014). The model shown in Smartthings advance user mode is Model: 3325-S