knedd
commented
11 months ago I had this bug this morning. Was able to correct it by reestablishing the full MFA process, including entering an updated fingerprint.
From: ibogost @.> Date: Tuesday, July 25, 2023 at 8:47 AM To: mrjackyliang/homebridge-adt-pulse @.> Cc: Subscribed @.***> Subject: [mrjackyliang/homebridge-adt-pulse] ADT Pulse Julu 25 changes appear to have broken the plugin (Issue #104) Describe the bug:
Overnight between July 24 and 25, the ADT Pulse plug-in cannot login to accounts or operate ADT system. Logging into ADT Pulse app today produces the following pop up message:
“Starting on 7/25, ADT is enhancing our security protocols for the Pulse app. Users will be asked to log in and authenticate their devices (press yes if you recognize the device). If you have any questions, please visit our Support Center.“
I have attempted to reset 2FA but cannot determine if this will help. The fingerprint value did not change, and I have not yet tried creating a new ADT account.
(The plug-in was flooding ADT’s service with failed logins and their portal has blocked my network (hopefully temporarily). Whatever else is going on, the plug-in should probably not infinitely attempt to login like this.)
Steps to reproduce the bug:
- Use the plugin after 7/24/2023
Expected behavior:
Successful login to ADT Pulse service by the plugin.
Homebridge information:
Find these 4 lines in the beginning of the logs, then replace the text inside the grave accents:
[7/25/2023, 7:12:24 AM] [ADT Pulse] running on linux (x64)
[7/25/2023, 7:12:24 AM] [ADT Pulse] homebridge-adt-pulse v2.1.7
[7/25/2023, 7:12:24 AM] [ADT Pulse] node v16.15.1
[7/25/2023, 7:12:24 AM] [ADT Pulse] homebridge v1.4.1
Logs related to this bug:
ADT Pulse: Login failed.
ADT Pulse: Logging in...
ADT Pulse: Response path -> undefined
ADT Pulse: Response path matches -> fa lse
ADT Pulse: Login failed.
ADT Pulse: Logging in..
ADT Pulse: Response path -> undefined
ADT Pulse: Response path matches -> fa lse
ADT Pulse: Login failed.
ADT Pulse: Logging in..
ADT Pulse: Response path -> undefined
ADT Pulse: Response path matches -> fa lse
ADT Pulse: Login failed.
— Reply to this email directly, view it on GitHubhttps://github.com/mrjackyliang/homebridge-adt-pulse/issues/104, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI2BNPXO5FQHPZWTGYDA23DXR656ZANCNFSM6AAAAAA2XASZG4. You are receiving this because you are subscribed to this thread.Message ID: @.***>
ibogost
github-actions[bot]
Describe the bug:
Overnight between July 24 and 25, the ADT Pulse plug-in cannot login to accounts or operate ADT system. Logging into ADT Pulse app today produces the following pop up message:
“Starting on 7/25, ADT is enhancing our security protocols for the Pulse app. Users will be asked to log in and authenticate their devices (press yes if you recognize the device). If you have any questions, please visit our Support Center.“
I have attempted to reset 2FA but cannot determine if this will help. The fingerprint value did not change, and I have not yet tried creating a new ADT account.
(The plug-in was flooding ADT’s service with failed logins and their portal has blocked my network (hopefully temporarily). Whatever else is going on, the plug-in should probably not infinitely attempt to login like this.)
Steps to reproduce the bug:
Expected behavior:
Successful login to ADT Pulse service by the plugin.
Homebridge information:
Find these 4 lines in the beginning of the logs, then replace the text inside the grave accents:
Logs related to this bug: