Unable to log into ADT Pulse - possible that ADT is blocking IPs after detection.

[ChrisMD123]

Describe the bug:

Starting two days ago, I became unable to log into ADT Pulse from my home network only - including through HomeBridge. I called ADT and they are not experiencing any systemwide issues, and I confirmed that I can still access portal.adtpulse.com from my phone on cellular and from my computer when using a different Wi-Fi network.

As soon as I blocked HomeBridge from the Internet through my router, I was able to access portal.adtpulse.com again.

I tried it 3-4 times, and each time it was the same: if HomeBridge was allowed to access the Internet, then I could not reach portal.adtpulse.com. If it wasn't, I could.

Steps to reproduce the bug:

1. No steps required - HomeBridge simply stops being able to sign into ADT Pulse. https://portal.adtpulse.com will not resolve in a web browser.
2. Turn off HomeBridge server or block it from the Internet.
3. https://portal.adtpulse.com starts working again - instantly.

Expected behavior:

A clear and concise description of what you expected to happen.

The Apple device you are using:

• Device: Docker container of HomeBridge
• OS: v1.6.1
• Device for browsing: Windows 10 PC

Homebridge information:

Find these 4 lines in the beginning of the logs, then replace the text inside the grave accents:

[7/30/2023, 1:11:05 PM] [ADT Pulse] running on linux (x64)
[7/30/2023, 1:11:05 PM] [ADT Pulse] homebridge-adt-pulse v2.1.7
[7/30/2023, 1:11:05 PM] [ADT Pulse] node v18.17.0
[7/30/2023, 1:11:05 PM] [ADT Pulse] homebridge v1.6.1

Logs related to this bug:

N/A

[ChrisMD123]

Solved the issue by starting from scratch and recreating the 2FA key. If I had to guess, Pulse may have disabled all keys on their end which was causing them to block what they assumed were malicious attempts to sign in.

[github-actions[bot]]

This issue is now locked and considered resolved due to inactivity.