search

mrjackyliang / homebridge-adt-pulse

Homebridge security system platform for ADT Pulse
MIT License
36 stars 7 forks source link

[Bug]: Cannot login to ADT Pulse (Invalid Fingerprint, Fingerprint Tool Bug, ADT Pulse Latest Changes) #147

Closed mrfatboy closed 2 months ago

mrfatboy commented 2 months ago

Pre-check confirmation

Tell me exactly what happened

Still get same login errors. Capture

Please see closed issue here: https://github.com/mrjackyliang/homebridge-adt-pulse/issues/144

Logs relevant to this issue

see above

Legal Agreements

mrjackyliang commented 2 months ago

I believe your IP is banned from the ADT Pulse portal it seems. Are you able to access the web portal directly on your browser? I'm working on the plugin right now, and I'm not having such issues.

I remember when I had T-Mobile Home Internet, I couldn't access the web portal unless I went on a VPN. So it is ISP-dependent.

mrfatboy commented 2 months ago

I am able to login to ADT pulse just fine from same computer.

mrjackyliang commented 2 months ago

Please run the test-api script and post your results here.

mrfatboy commented 2 months ago

Capture2

mrfatboy commented 2 months ago

More info. Homebridge is running in Hyper V in Windows 11. I logged into ADT Pulse and selected trust this computer on the Windows 11 side. I then use the ADT Pulse fingerprinter Detector an copied that into the config file.

mrjackyliang commented 2 months ago

The logs are telling you should refresh your fingerprint. I assume you made changes to the trusted devices on your account?

mrfatboy commented 2 months ago

i just did all of that and I get the same error.

mrjackyliang commented 2 months ago

Can you tell me step by step on how you generated the fingerprint and how you logged in?

Small things like this affect the outcome of the fingerprint, because if it was the correct fingerprint that was authorized, it should not have this error.

mrfatboy commented 2 months ago

I used Brave browser. Shields down.

Logged into adt pulse. Sent code to phone to authorize. Selected "trust this computer"

Opened up adt fingerprint getter in Brave. Copied fingerprint. Pasted into adt plugin config UI.

Also doubled check of same finger print in config.json.

Restart Homebridge. Get the error.

mrjackyliang commented 2 months ago

I used Brave browser. Shields down.

Logged into adt pulse. Sent code to phone to authorize. Selected "trust this computer"

Opened up adt fingerprint getter in Brave. Copied fingerprint. Pasted into adt plugin config UI.

Also doubled check of same finger print in config.json.

Restart Homebridge. Get the error.

Can you copy the fingerprint that you have and do a base64 decode? You can send the fingerprint to my email (contact@mrjackyliang.com).

mrfatboy commented 2 months ago

I just sent the fingerprint and base64 decode to your email.

mrjackyliang commented 2 months ago

I used the fingerprint that you sent, and it logs in fine.

mrfatboy commented 2 months ago

I don't know what to say. Could it be something about the VM?

What else could be different?

Other people are having the same issue.

mrjackyliang commented 2 months ago

Other people aren't having the same issue that you are. The other issue was a weird maintenance period issue, which also happened to me as well. That subsided already, and my login works.

However, you can try running this code on your browser (the Brave Browser) while on the ADT Pulse login page, and compare the value to your fingerprint (what you sent me via email).

window.document.getElementById('fingerprint').value

If the values aren't the same, then just use the value that your browser gave you.

mrfatboy commented 2 months ago

I ran the code. The values are the same. Regarding the other issues on https://github.com/mrjackyliang/homebridge-adt-pulse/issues/144

It seems exactly the same errors.

mrfatboy commented 2 months ago

more info; The VM is running: Ubuntu Focal (20.04.5 LTS) Node.js v18.13.0 ADT Pulse plugin v3.3.1

mrjackyliang commented 2 months ago

I ran the code. The values are the same. Regarding the other issues on #144

It seems exactly the same errors.

The others aren't getting HTTP 500 errors, they're getting automatic signout errors. The logs look very much the same, but the story it tells is very different

mrfatboy commented 2 months ago

I'm at a loss. Your plugin used to work for me before I upgraded to v3 and I switch to a windows 11 VM.

mrfatboy commented 2 months ago

However, i was running homebridge in windows 10 natively and not in Hyper V

mrjackyliang commented 2 months ago

I haven't tested this plugin in hyper-V before, but I can spend some time to see what's up there

EDIT: Can't install Hyper-V, sucks. On a Mac M1.

mrfatboy commented 2 months ago

Maybe the fingerprint doesn't work the same in a VM?

mrjackyliang commented 2 months ago

Maybe the fingerprint doesn't work the same in a VM?

It should be the same. There aren't any special requirements based on OS.

mrjackyliang commented 2 months ago

I'm going to try and see if I can get something rolling on Ubuntu 20.

mrfatboy commented 2 months ago

Something is funky. Tomorrow I will setup another Homebridge instance in native Linux box and see if the plugin works there. I will report back.

If you come at it from a the VM side and see if the plugin is acting differently maybe we can solve it. :)

mrjackyliang commented 2 months ago

Will report back. Installing ubuntu 20 now.

mrjackyliang commented 2 months ago

I suspect ADT made some changes to the fingerprint script. The fingerprint used to log in is not the same as the one generated using the fingerprint tool.

mrjackyliang commented 2 months ago

Okay, I think I found out what's going on. ADT made changes to the fingerprint script so the fingerprint would generate different values when run from another website.

For now, don't use the fingerprint tool. I will be phasing it out in the next version.

Instructions on how to get up and running now:

  1. Login to ADT Pulse, and delete all the trusted devices (just to get all the weird problems out of the way)
  2. Go to the ADT Pulse login page, and use the code window.document.getElementById('fingerprint').value to get the fingerprint and save it in your Homebridge config. DO THIS BEFORE YOU LOGIN. DO NOT RESTART HOMEBRIDGE YET.
  3. Login to your ADT Pulse account and do the usual verification and device saving.
  4. Restart Homebridge.
mrfatboy commented 2 months ago

Great. I will do it first thing in the morning and report back 👍

mrfatboy commented 2 months ago

Followed your above instructions and everything looks good so far. I'm glad we tracked down the issue. :)

mrjackyliang commented 2 months ago

Nice, looks like I came in just as I was about to phase out the fingerprint tool🤣 Man, this timing is amazing.

mrjackyliang commented 2 months ago

v3.4.0 now automatically generates a random fingerprint for you. No more fingerprint tool required.

github-actions[bot] commented 1 month ago

Due to inactivity, this issue will be locked and marked as resolved. If you have any further questions or inquiries, please feel free to open a new issue.