My alarm door sensor keeps saying it opme when its closed. When I remove it from the door it triggers is as triggered alarm but when I place it back on the door it doesn’t read as closed, What can the problem be???
If you have a sensor which is not reporting accurately while mounted but works when pulled off the door, the issue is environmental, or a combination of environment and low battery. This is pretty common. Is this a metal door or metal frame?
What model of sensor is it?
If the sensor has been working appropriately for a long while before this, the issue is possibly caused by lower voltage in the battery in addition to the environmental impact. Try replacing the batteries.
Another possibility, what is the distance between the sensor and magnet? There is a maximum gap distance and if installed at the edge of that max distance you can run into problems like this.
The sensor is located on a metal gun safe door. Its brand new, haven’t tried to replace the batteries yet because it is new and it is located approx. 25 feet from the controller. It still reports as open, but if I remove it, it will trigger as tamper.
Ahh, if that is attached to a thick metal safe then the likely issue is the metal is simply devouring the rf signals. pulling it off of the metal will resolve this and allow signals through.
A good way to guard a metal safe like that is to use a wired sensor on the door, then run that wire back to a DW10 attached to the wall away from the safe. If in a closet for example you can typically hide the wire completely.
You could also try elevating the wireless sensor off of the door with a spacer or extra double sided tape, but that can get ugly.
thats what I thought so i used two pieces of double sided tape and it still say’s open when its closed.
Two pieces of double sided tape may or may not be enough, but another thing to double check is the loop number.
It looks like that sensor zone may be programmed as Loop 1. A DW10 using its built in reed switch should be programmed as Loop 2.
This would cause the issue you are seeing if it is indeed programmed as loop 1.
It was programed as loop #1 and I switched it to loop #2 and it fixed the problem…thanks!