The ADT Premium Door and Window Sensor does the same job as the basic sensor, reporting open and closed, but adds features that make it more useful for automation, depending on the model, such as a larger gap tolerance, a temperature reading or a tamper switch, and when an automation fails the cause is how those features are exposed in the app and what the connected platforms understand. Start by learning what your sensor reports. Open its page in the ADT app and look at the readings: open or closed, battery, signal and, if present, temperature.
The checks in more detail
A premium sensor that shows a temperature opens the way for a rule such as a notification when a window is open and it is cold outside, or when a freezer door's temperature rises. Give it a clear name and place it in a room, since rules and assistants use both. Building a rule depends on your system. If the ADT app offers automations, choose the sensor as the trigger, set a condition, such as the system mode or a time window, and pick the action, such as an alert or a light.
If rules live in another platform, check what its integration with ADT exposes: the open and closed event is commonly available, while the temperature or the tamper state may not be, so read its documentation before designing. Test every rule with the system in test mode, and watch the timing, remembering that sensors report by radio and may take a second or two. Reliability underlies everything. Keep the battery fresh, since the extra features draw more power, and check the magnet gap and alignment. Keep the panel within range, avoiding metal and masonry between them.
If a rule fires too often, add a delay or a condition, such as only when the system is armed away. If it never fires, check that the sensor reports the event in the app history first, because a rule cannot run on an event that the system never saw. Do not use an automation as the only way to learn about a safety event, such as an open door while armed. Contact ADT support if a documented rule fails, with the sensor model and the rule.
Differential
Likely causes of “ADT Premium Door/Window Sensor routine, schedule or automation is not running”, and how to tell them apart
- 1
A feature the integration does not expose
What separates it The temperature or tamper state never triggers a rule
How to confirm Check the integration's documentation
- 2
A rule condition that is never met
What separates it The automation does not run
How to confirm Review the mode and time conditions
- 3
An unnamed sensor
What separates it Rules and assistants cannot find it
How to confirm Name it and set its room
Before you touch a setting
Record this first — changing settings destroys the evidence
- The device's state in the app
- The battery or power
Try in this order
0 of 3 completedRead what the sensor reports
ReversibleIn the app.
Name it and set its room
ReversibleClear names.
Build the rule
ReversibleTrigger, condition, action.
Model-specific
What is true of this model and not of its siblings
- Premium features
- Temperature and tamper readings may be available.
- Event history
- A rule needs the event to be logged.
Stop boundary
When this stops being a self-service repair
- !If the problem persists after these steps, contact ADT with the device and system details
- !Do not disable a safety device
Evidence ledger
Sources behind this answer
Exact questions
Common questions
What makes the premium sensor different?+
Extra readings or tolerances, depending on the model.
Can I use the temperature?+
If the app or integration exposes it.
Should I use it for safety?+
No, keep the alarm as the base.