ADT Door/Window Sensor routine, schedule or automation is not running

The checks in more detail

Check whether your ADT plan and panel support rules, often called automations or scenes, that react to a sensor event, such as turning on a connected light when a door opens. If the app offers such rules, create one with a trigger, the door opening, and an action, the light or the notification, and test it with the system in test mode. A rule that does not run may be limited by the mode, a schedule or the device's status, so check the conditions. If the action is in another platform, such as a smart plug or an assistant, check that the integration supports the sensor event;

some integrations expose only the system's armed state, not each sensor, so read what the integration can do before building. Make sure the sensor reports reliably: replace weak batteries and check the magnet alignment, because an automation can only be as good as the reports it gets. Keep the panel within range. The time zone matters for schedules. Do not rely on an automation as your only safety measure, and keep the alarm itself as the foundation. If a documented automation fails, note the rule and the time, then contact ADT support. Re-adding the sensor can clear a confused pairing, and renaming it to a simple name helps assistants find it.

A practical way to start is a single, simple rule that you can test and trust, such as an alert to your phone when the front door opens while the system is armed in Away mode. Once that works, add a second rule, for example a light that comes on when the back door opens after dark. Building one rule at a time makes problems easy to trace: if the second fails, the first still works and the fault is in the new rule. Keep a note of each rule with its trigger, condition and action, because a year later nobody remembers why a light comes on when the garage door opens.