ADT Pulse integration


Yes. In the configuration.yaml.



I got the sensors and everything to work. the time i reported it not working was when the plugin was installed on a ubuntu vm. But moved my config to pi and connected. Now i just gotta figure out how to change the report to Open/Closed instead of devStatOk or open


thanks. I’ll need the page before this one. I don’t know how the camera picture link is formed.


Here is the main dashboard


Hi All - I have this system! Excited to hear there is a way to work with it in

I’m trying to get things up and running and I can’t figure this out.

What exactly goes in this section, in both username and password sections? I’ve tried entering my local Mosquitto server creds,but it fails - I think?

> [email protected] start /usr/src/app
> node server.js

2018-7-24 16:48:16 Pulse.pulse Spanning
2018-7-24 16:48:16 Pulse: New Client undefined
2018-7-24 16:48:16 Pulse: Login called Authenticating
MQTT Sub to: home/alarm/cmd
2018-7-24 16:48:16 Pulse: Authentication Failed
2018-7-24 16:48:16 Pulse: httpResponse:[object Object]
2018-7-24 16:48:21 Pulse: Login called Authenticating
2018-7-24 16:48:21 Pulse: Authentication Failed
2018-7-24 16:48:21 Pulse: httpResponse:[object Object]
2018-7-24 16:48:26 Pulse: Login called Authenticating

Here is the config

  "ssl": false,
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem",
  "pulse_login": {
    "username": "",
    "password": ""
  "mqtt_host": "",
  "mqtt_connect_options": {
    "username": "",
    "password": ""
  "alarm_state_topic": "home/alarm/state",
  "alarm_command_topic": "home/alarm/cmd",
  "zone_state_topic": "adt/zone",
  "smartthings_topic": "smartthings",
  "smartthings": false

Thank you!


this needs to contain your ADT Pulse login for the


thank you! I see how the image url is placed here.
To pull the image you need to be logged in to the pulse portal. I think it’s best to download the image and store it in HomeAssistant to display it inside the UI.
I’ve added it to my todo list.


Ah! Got it!

How about the other section? Should that be where you enter the MQTT username and password?

Edit: disregard - all working now… I think :slight_smile:


Tested when I got home. The alarm_away still doesnt set


No problem I will play also. Another thing to note. Arlo does the same thing. Pulls the image and stores it. I also think ring door bell does the same thing


I got it all working using MQTT - which is great. I can integrate this into Node-Red and do all kinds of cool automation - AWESOME! Thank you @haruny! I’m going to share this great addon on reddit, with other folks who were hoping to find a way to integrate this ADT system type with their HA systems.

The only thing I can’t figrue out is how to make sensors from my sensors (doors/windows/etc) and then how to have them show up on the default dashboard?

I tried adding some bits of the text above and in the howto and I keep receving errors.

I have this in my configuration.yaml

  - platform: mqtt
    name: "ADT Pulse"
    state_topic: "home/alarm/state"
    command_topic: "home/alarm/cmd"
    payload_arm_home: "arm_home"
    payload_arm_away: "arm_away"
    payload_disarm: "disarm"

But where in can I use this?

I tried adding the sensors, but they give me configuration errors, whether I put the in configuration.yaml or binary_sensor.yaml

  - platform: mqtt
    name: “Garage Door”
    state_topic: “adt/zone/Garage Door/state”
    payload_on: “Open”
    payload_off: “OK”
    retain: true
    value_template: ‘{{ value_json.status }}’

Thanks for all the help!


Configure them as binary sensors following the example below. Replace YOUR_SENSOR_NAME with the exact name that ADT Pulse has associated with that zone/sensor. Change the device_class as appropriate for each zone/sensor.

Per @haruny’s instructions in an earlier post, you can get a dump of the zone/sensor data including names:

After running the add-on, to list all the zones found, you can call:

# mosquitto_sub -h YOUR_MQTT_IP -v -t "adt/zone/#"

Follow this example

- platform: mqtt
      name: "Z1 Entry Doors"
      device_class: door
      state_topic: "adt/zone/YOUR_SENSOR_NAME/state"
      payload_on: "devStatOpen"
      payload_off: "devStatOK"
      value_template: '{{ value_json.status }}'

Then just add the calls the binary_sensor in your dashboard.


Interesting - everything starts up fine and I’m sub’ed to the topic, but nothing prints out.

I can issue MQTT commands to arm/disarm/etc - but I don’t get a listing on that topic when starting the addon.

Any ideas?


Where do I place this? Everywhere I try I get an error.


In configuration.yaml under the heading for binary_sensor.

  - platform: mqtt
        name: "Z1 Entry Doors"
        device_class: door
        state_topic: "adt/zone/YOUR_SENSOR_NAME/state"
        payload_on: "devStatOpen"
        payload_off: "devStatOK"
        value_template: '{{ value_json.status }}'

Or if you break out your binary_sensor section to its own yaml file (like below), then you’d just place it in the binary_sensor.yaml.

binary_sensor: !include binary_sensor.yaml


Are you calling the command quoted above? It’s a command line command. So you need to SSH to your instance and execute the command. The addon doesn’t print out the listing. That’s totally separate.


Yep! I know how to use MQTT and I’m typing the command within the console.

Similar to subscribing to home/alarm/cmd and I can see all my commands when I issue them.


I try to add this to binary_sensor.yaml, but then I receive an error on config check

Configuration invalid
Error loading /config/configuration.yaml: mapping values are not allowed here
  in "/config/binary_sensor.yaml", line 93, column 13

Here is the config.

  - platform: mqtt
        name: "Z1 Entry Doors"
        device_class: door
        state_topic: "adt/zone/Garage Door/state"
        payload_on: "devStatOpen"
        payload_off: "devStatOK"
        value_template: '{{ value_json.status }}'


Sorry, that wasn’t clear from your question. I don’t know what to tell you. This is what I run and my results.

[email protected]:~$ mosquitto_sub -h [MY_IP_ADDR] -v -u hass -P [PASSWORD] -t "adt/zone/#"

adt/zone/Z1 Entry Doors/state {"id":"sensor-9","devIndex":"E1VER1","name":"Z1 Entry Doors","tags":"sensor,doorWindow","status":"devStatOK","statusTxt":"Z1 Entry Doors - Closed\nLast Activity: Today 8:55 PM","activityTs":1531702508134}
adt/zone/Z2 Master Bedroom/state {"id":"sensor-10","devIndex":"E2VER1","name":"Z2 Master Bedroom","tags":"sensor,doorWindow","status":"devStatOK","statusTxt":"Z2 Master Bedroom - Closed\nLast Activity: 6/17 12:49 PM","activityTs":1529254141541}
adt/zone/Z3 Front Windows/state {"id":"sensor-11","devIndex":"E3VER1","name":"Z3 Front Windows","tags":"sensor,doorWindow","status":"devStatOK","statusTxt":"Z3 Front Windows - Closed\nLast Activity: 1/22 5:45 PM","activityTs":1516661127558}
adt/zone/Z4 Bedroom Windows/state {"id":"sensor-12","devIndex":"E4VER1","name":"Z4 Bedroom Windows","tags":"sensor,doorWindow","status":"devStatOK","statusTxt":"Z4 Bedroom Windows - Closed\nLast Activity: 7/12 10:49 AM","activityTs":1531406991636}
adt/zone/Z5 Back Doors/state {"id":"sensor-13","devIndex":"E5VER1","name":"Z5 Back Doors","tags":"sensor,doorWindow","status":"devStatOK","statusTxt":"Z5 Back Doors - Closed\nLast Activity: Today 4:50 PM","activityTs":1531687815325}
adt/zone/Z6 Family RoomMotion/state {"id":"sensor-14","devIndex":"E6VER1","name":"Z6 Family RoomMotion","tags":"sensor,motion","status":"devStatOK","statusTxt":"Z6 Family RoomMotion - Okay\nLast Activity: 1/22 5:41 PM","activityTs":1516660888847}
adt/zone/Z7 Laundry Room Smoke/state {"id":"sensor-8","devIndex":"E7VER1","name":"Z7 Laundry Room Smoke","tags":"sensor,fire","status":"devStatOK","statusTxt":"Z7 Laundry Room Smoke - Okay\nLast Activity: 5/27 9:47 AM","activityTs":1527428852554}

What happens when you run the following. Do you get the output for all your MQTT devices?

mosquitto_sub -h YOUR_MQTT_IP -v -t "#"