FAQ
Find answers to common questions about the plugin's operational modes, sensor setup, force arming, privacy redaction, and platform support.
Operational Modes
What operational modes does the plugin support?
The plugin runs in one of three modes, set through the mode field. Each mode changes how the plugin behaves at startup.
| Mode | Description |
|---|---|
normal | Regular operation with all configured devices responsive. |
paused | Pauses the plugin so all devices become non-responsive. |
reset | Removes the accessories associated with the plugin. |
See Operational Mode for the full field reference.
What happens when I set the mode to reset?
Reset mode begins a countdown with warnings before it removes every accessory the plugin created. You have approximately 40 seconds to reverse the setting and restart Homebridge before the removal happens.
danger
Leaving the plugin in reset mode removes all associated accessories after the countdown, which can undo automations and customizations tied to them.
Sensors and Zones
Which sensors can the plugin expose?
The plugin exposes a fixed set of read-only sensor types, selected through the adtType field on each sensor. The supported types are co, doorWindow, fire, flood, glass, heat, motion, shock, and temperature.
See Supported Devices for what each type maps to.
Why do I have to list every sensor manually?
Earlier versions detected sensors automatically and managed their addition and removal, but portal irregularities could remove all sensors and cause an unintended reset. To avoid this, you now explicitly specify each sensor you want to integrate into Homebridge.
Each sensor is an object with four fields:
| Field | Description |
|---|---|
name | Display name used for clarity, shown in the event of an unforeseen reset. |
adtName | Must match the name shown under the "Name" column in the portal "System" tab. |
adtZone | Must match the "Zone" column in the portal. Only zones 1 through 99 are supported. |
adtType | Must match the "Device Type" column, mapped to a supported type such as doorWindow. |
See Sensors and Zones for the full setup.
What if my sensor type is not listed?
If you do not find your type listed, the plugin notifies the author automatically so support can be added once enough information is gathered. It is recommended that you do not create a separate GitHub issue for an unsupported type.
Arming
Why does the plugin force arm my system?
The Home app relies on the HAP protocol to establish arm states, and that protocol expects the arm request to succeed. To satisfy it, the plugin force arms whenever it detects active motion or open sensors.
Force arming is always on and cannot be disabled, because turning it off would cause arming failures without alert notifications.
warning
If you automate arming, you accept the risk that the system may not fully arm when a sensor is active or open at the time of the request.
See Force Arming for how to check your sensors before arming.
Can I use Arm Night?
Arm Night on ADT Pulse systems is only available through the panel itself and is not visible on the Web Portal or the mobile app. You can still place your system into Arm Night mode with this plugin.
See Arm Night Support for details.
Why does my temperature sensor show 0 degrees or 100 degrees?
The Temperature Sensor works with temperature values in the HAP protocol rather than open or closed states, so the accessory converts its binary status into degrees. Normal temperatures are represented as 0 degrees Celsius, and abnormal temperatures are represented as 100 degrees Celsius.
See Temperature Sensors for more on this conversion.
Privacy
Does the plugin track me?
The plugin adheres to the verified Homebridge plugin requirements, so it does not track you in any way. Its detection feature only notifies the author when it encounters an undocumented sensor or panel status.
What information is sent, and is it redacted?
Personally identifiable details are redacted before any report leaves your system, replaced with the literal string *** REDACTED FOR PRIVACY ***. Redacted fields include IP addresses, MAC addresses, serial numbers, update timestamps, the security panel's master code, and session tokens.
A privacy warning is shown when you run the included scripts, when the plugin starts, and when it is about to notify the author.
See Detection and Privacy for the full redaction reference and an example report.
Can I opt out of detection reports?
You can prevent detection reports by blocking the URL that the plugin uses to notify the author. If you block that URL, the author will not be able to offer assistance or support, since the plugin can no longer report the undocumented statuses it needs to diagnose issues.
Platform Support
Does the plugin work on HOOBS?
HOOBS may use an outdated configuration UI that has not been resolved by the HOOBS team. HOOBS users should manually configure the plugin using the sample configuration rather than relying on the config UI.
info
Support for HOOBS is offered on a best-effort basis. See HOOBS Support for the current status and manual configuration guidance.
Is my country supported?
ADT Pulse is available to consumers in either the United States or Canada, selected through the subdomain field. Set subdomain to portal for the United States or portal-ca for Canada.
See Portal Region for details.
Does the plugin support Z-Wave accessories?
Z-Wave accessories connected to the ADT Pulse gateway are not supported and are not planned, due to implementation complexity and platform instability. See the Supported Devices page for alternative suggestions.