# Ghost Multipurpose Sensor readings **URL:** \ **Category:** Connected Things\ **Created:** [November 29, 2016, 5:21pm UTC](https://community.smartthings.com/t/ghost-multipurpose-sensor-readings/65403 "2016-11-29T17:21:48Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![JDRoberts](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/jdroberts/32/56577_2.png) [@JDRoberts](https://community.smartthings.com/u/JDRoberts)\ **Post date:** [November 29, 2016, 6:42pm UTC](https://community.smartthings.com/t/ghost-multipurpose-sensor-readings/65403/2 "2016-11-29T18:42:51Z")
1 inch is probably too far apart, I’m actually surprised it’s ever closed. But there are other possibilities. It might take a look at the following in case he give you any ideas (this is a clickable link) > [@FAQ: My Sensor (any brand) is Stuck on Closed (or Open)](https://community.smartthings.com/t/faq-my-sensor-any-brand-is-stuck-on-closed-or-open/25419): > > When any sensor gets “stuck” in one reporting state, open or closed, it’s almost always one of the following: Low battery. once the battery gets down to about 30%, the signal strength drops by a lot. It just may not be able to report. So you may want to try just changing the battery if it’s getting low. sometimes a new device gets delivered with a bad battery, it can happen. orphaned nodes. Zigbee does have a vulnerability to this. The fix is to unplug the hub for at least 15 minutes, including removing the batteries. This will cause all the zigbee devices to realize they’ve lost connection to the network, and then when you plug the hub back in the address tables will get rebuilt. You may not see an improvement until the next day, it can take a while for the changes to propagate… And all of that said… It’s really weird if it’s reporting open and then closed again immediately throughout the day. To be honest, that sounds more like a defective device. It can happen. --- _[View the full topic](https://community.smartthings.com/t/ghost-multipurpose-sensor-readings/65403)._