I have the ADT Command/Control (Commander) system [they use different names in different documents]. When I got this system they claimed it was the future for ADT. Later, they had so much trouble with it they continued with the Pulse system with upgrades. So, I am stuck with the Commander system. I wish I could use the ADT Pulse integration. Does anyone know a path for me to get some of the features the Pulse Community has made possible?
Thanks for any suggestions, Doug
How do you change the scan interval? In my (add on) configuration page, I tried setting scan_interval to 300, in case it was seconds; then I tried 300000, in case it was milliseconds but either case, the calls to ADT API kept going on at a rate of one every 5 seconds.
This didnāt work for me, either. The only way I could get the fingerprint key was by enabling Developer Options in my Android phone, then plugging it to my computer and using Chrome Developer Tools to debug the phone. Once I logged in to ADT, using the ADT Phone App, the fingerprint key was sent across and I was able to capture it.
Hi,
Iāve been using the ADT integration for a month or 2 (not the MQTT one).
The logs occasionally complain about too much polling, and various other warnings. No big deal, but it seems from scanning this thread, ADT isnāt thrilled with short polling times.
I was wondering if anyone has tried these non-polling methods:
- ADT Pulse can send emails based on events. Perhaps using the IMAP integration would be useful (ok, youād be polling your IMAP server)
- Alexa routines, which could call scripts on HA to update sensors (maybe via MQTT?)
These methods would get around all the pulse authentication and polling issues.
ā Rob
Thank you for this. I was having a hard time obtaining the fingerprint using the add-on configuration, some of the chrome options must have changed. I followed these steps and was able to get the fingerprint. Working fine!
Thanks @rlippmann and @sbabcock23 for making changes to pyadtpulse and hass-adtpulse. They have some more great things coming.
Iāve been busy squishing bugs on the async version of the HA ADT Pulse Integration, but itās almost ready.
Besides being async, it will be push instead of poll (ok, technically in the background itās doing a lightweight poll, which is what the Pulse website/app also does), so updates will be pretty much instantaneous.
Also, force arming will be supported.
Iāve also been working to reverse engineer the 2 factor authentication mechanism. I think I might have it, though.
In the meantime, I made an easier way to find out your browser fingerprint.
Simply go to this link and you should be able to see the fingerprint (which beats having to figure out your browser developer tools).
This should work for the MQTT integration and the Homebridge integration as well.
Iāve been looking at integrating cameras, which should be possible as ADT uses a Janus WebRTC server, but trying to do it in Python looks like a huge pain. If anyone has any experience with Janus, I would appreciate any help.
0.2.6 update resolved all issues and integration is now active again for me.
2FA is included on my login. I used the āFingerprint Browser Detectorā as mentioned with success.
Entity state changes are also pretty much instant. Maybe 1 or 2 sec delay.
Current HA setup is below:
ADT Pulse integration (0.2.6) installed via HACS
Proxmox VE 7.4-3 on a i5 Lenovo M710q mini PC. 128SSD 16gig RAM
Home Assistant 2023.5.2
Supervisor 2023.04.1
Operating System 10.1
Frontend 20230503.3 - latest
Going to rebuild my alarm dashboard but for the time being, all entities are showing up.
THANK YOU! @rlippmann @ryans and anyone else who has worked on this.
Youāre welcome. Is anyone else trying this? I could use more feedback on how itās working outside of my site.
I would use this if I knew a safe way to load it. last time I tried it messed me up.
Are there instructions anywhere?
Does this work with an ADT+ system? (Not ADT Pulse). I received the system as a replacement for the Nest Secure system, and was hoping to tie it into my HA setup.
Probably not.
Are there any plans to update this integration? Or the pyadtpulse 1.1?
Iāve seen you comment on a couple of these threads. I was upgraded to Command a year, maybe a year and half ago and Iāve been happy with it. Fully integrated with Google Assistant etcā¦
Did you ever find a solution for Control?
Sorry, took a break for a bit.
Iāve been working on pyadtpulse 1.1 which does automatic relogin after about 2 hours (since ADT seems to start ignoring update requests after a while), and makes the gateway and alarm panel devices in HA.
hass-adtpulse 0.3 will use those things, and also adds a separate sensor for trouble issues (i.e. low battery, tamper, etc). This is so you can actually write an automation with entities to check it, instead of having to go through the attributes.
Currently testing both now. Seems pretty stable, but the relogin stuff takes a while to see if itās actually working.
Hey guys im back. I am using the integration. I may add its much easier than in 2018. Second looks like it didnt build the Alarm panel. There was an issue with the setup. Can anyone help me out with getting the alarm panel working. My integration is all there meaning i have my sensors reporting but my alarm panel is just not an option and not in entities. And when i check my notifications. I tried the alarm_control__panel: !include alarm.yaml in the config
but when i put the code for the alarm in the alarm.yaml. It says it cant get platform.
Are we still using the MQTT platform looks like in my previous alarm panel i had:
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ā
but since the HACS integration i wanted to know what we should have since it doesnt have it documented
I had the same issue, it seems to be due to the recent update to pyadtpulse from 1.0.0 to 1.1 which changed where some of the code is located that alarm_control_panel.py
is looking for during setup. I temporarily resolved it by updating the requirement in the manifest.json file to "pyadtpulse==1.0.0"
which seems to at least resolve the error but I cant get it to arm or disarm the system.
I just put out 0.3.1 for adtpulse. (Donāt use 0.3.0, I made a boo-boo that wonāt let it load).
As for MQTT, thatās a separate integration.
New features:
automatic relogin
gateway and alarm are separate devices, as are each sensor.
add trouble entity for each sensor
options flow to set poll interval, relogin interval, keepalive interval
Let me know how itās working.