ADT Pulse integration

Ben_Ellis · July 26, 2018, 1:03pm

If you want to have the status change you can do something like this in your sensors page:

platform: mqtt
    name: "Master Bedroom Window"
    state_topic: "adt/zone/Master Bedroom Window/state"
    payload_on: "devStatOpen" # Use devStatTamper for shock devices
    payload_off: "devStatOK" # 
    retain: true
    value_template: >- 
      {% if is_state('sensor.master_bedroom_window', 'devStatOpen') %}
        Open
      {% else %}
        Closed
      {% endif %}

commandcontrolit · July 26, 2018, 1:12pm

What exactly is the value of what you’re describing here?

Sorry - I’m still learning Thanks!

commandcontrolit · July 26, 2018, 1:25pm

Hey Ben, to use this - does the sensor.master_bedroom_window need to be created elsewhere?

Meaning, doesn’t there need to be a configuration that calls for a friendly name and that name would be master_bedroom_window?

Sorry for the obvious question if I’m missing it.

e1miran · July 26, 2018, 1:31pm

You’re replicating the functionality of the binary_sensor. Personally, I’d just use binary_sensor with the example configuration shown further up above.

commandcontrolit · July 26, 2018, 1:35pm

But in Ben’s example, he’s changing the variable so that it shows open/closed vs on/off.

I think.

Ben_Ellis · July 26, 2018, 1:55pm

Correct. I used sensor instead of binary sensor , so my output was devStatOk and i didnt like that. So I grouped it and updated the code so that mine shows open/closed.

This is what mine looks like

Ben_Ellis · July 26, 2018, 2:08pm

i am still learning also and couldnt get it to work in binary sensor. And now i see why my code was wrong. Thanks for that. But if you use sensor you can use my code. I basically just did what binary sensor does just like e1miran said

Ben_Ellis · July 26, 2018, 2:25pm

This is the same as Arm_Stay_instant

commandcontrolit · July 26, 2018, 2:52pm

So what does your code look like to name your sensor?

commandcontrolit · July 26, 2018, 2:55pm

Really? You can issue that and it works? Tha’s great! I’ll try this later.

e1miran · July 26, 2018, 4:09pm

@Ben_Ellis @commandcontrolit
That’s what device_class is for in binary_sensor. Plus there is the added benefit of showing the correct ‘open/close’ icons for each class without having to configure them oneself. Just remember device_class only works with binary_sensor… not with the plain sensor.

I have the following configured in my binary sensors, and they all display state and icons correctly without me having to do any templating.

device_class: door
device_class: window
device_class: motion
device_class: smoke

Here’s what my config looks like:

binary_sensor:
  - platform: mqtt
    name: "Z1 Entry Doors"
    device_class: door
    state_topic: "adt/zone/Z1 Entry Doors/state"
    payload_on: "devStatOpen" # Use devStatTamper for shock devices
    payload_off: "devStatOK"
    value_template: '{{ value_json.status }}'

  - platform: mqtt
    name: "Z2 Master Bedroom"
    device_class: door
    state_topic: "adt/zone/Z2 Master Bedroom/state"
    payload_on: "devStatOpen" # Use devStatTamper for shock devices
    payload_off: "devStatOK"
    value_template: '{{ value_json.status }}'

  - platform: mqtt
    name: "Z3 Front Windows"
    device_class: window
    state_topic: "adt/zone/Z3 Front Windows/state"
    payload_on: "devStatOpen" # Use devStatTamper for shock devices
    payload_off: "devStatOK"
    value_template: '{{ value_json.status }}'

  - platform: mqtt
    name: "Z4 Bedroom Windows"
    device_class: window
    state_topic: "adt/zone/Z4 Bedroom Windows/state"
    payload_on: "devStatOpen" # Use devStatTamper for shock devices
    payload_off: "devStatOK"
    value_template: '{{ value_json.status }}'

  - platform: mqtt
    name: "Z5 Back Doors"
    device_class: door
    state_topic: "adt/zone/Z5 Back Doors/state"
    payload_on: "devStatOpen" # Use devStatTamper for shock devices
    payload_off: "devStatOK"
    value_template: '{{ value_json.status }}'

  - platform: mqtt
    name: "Family Room Motion"
    device_class: motion
    state_topic: "adt/zone/Z6 Family RoomMotion/state"
    payload_on: "devStatOpen" # Use devStatTamper for shock devices
    payload_off: "devStatOK"
    value_template: '{{ value_json.status }}'

  - platform: mqtt
    name: "Laundry Smoke Detect"
    device_class: smoke
    state_topic: "adt/zone/Z7 Laundry Room Smoke/state"
    payload_on: "devStatOpen" # Use devStatTamper for shock devices
    payload_off: "devStatOK"
    value_template: '{{ value_json.status }}'

Ben_Ellis · July 26, 2018, 4:43pm

So please let me know what you need for the alarm panel ? i saw the email but lost it. I can provide that.

Also your motion should be devStateMotion

e1miran · July 26, 2018, 4:49pm

Thanks. Makes sense. Any idea what it should be for the smoke detector?

This is what mine looks like

alarm_control_panel:
  - 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"

commandcontrolit · July 26, 2018, 5:03pm

Thanks for sharing.

haruny · July 26, 2018, 10:45pm

Folks,
I need your help on implementing Device support. I see some of you have smoke detector, lamps, cameras etc. Apparently there is a second page where you can see these devices. I don’t own any devices. So I don’t see anything (just a “No other devices installed.” message),

If you own devices other than contact/motion sensors, do you mind sharing the output of the following page: https://portal.adtpulse.com/myhome/9.7.0-31/ajax/currentStates.jsp ?
Please submit your outputs to https://github.com/haruny/adt-pulse-mqtt/issues/11

Please mask out any of information you like for your privacy such as location names.

Thank you!
haruny.

commandcontrolit · July 27, 2018, 4:35pm

Tried - doesn’t work.

commandcontrolit · July 27, 2018, 4:37pm

I have no other devices. Sorry I can’t help. Happy to help with anything else you need testing with!

MrLinux · August 1, 2018, 10:20pm

Are there instructions on how to install this manually? hassbian doesn’t have the addon feature.

haruny · August 1, 2018, 10:45pm

Sorry I’m not experienced in hassbian so I can’t provide step by step instructions.
It shouldn’t be different from any other addon however, there is nothing special to it. Probably doable if you change the config.json and server.js a little bit I suppose. There remaining parts has nothing special to it.
It would require you to run nodejs install in a docker container and run the server.js.

MrLinux · August 2, 2018, 5:58am

Seems like going the hass.io route would be the easiest in the long run, so I’m planning to just flash the SD card with hass.io and port over my current install from backup.

Thanks!