Closed henrik242 closed 10 months ago
I see that both data
and sign
are set to seemingly sane values in fetchSessionId.js
, but the fetch response is null
.
There are two cases when it can return null
when fetchBusy()
returns isLoggedIn
as false
or if it was not abe to obtain sessionId
(probably wrong password or smth?)
since forceLogin
is true
by default, and assuming you didn't pass it as false
most likely it's not able to obtain sessionId.
Without seeing request / response for each fetch or a packet capture it's hard to say whats happening in your case.
I see you state "TL-MR6000" in the readme, but I hope you mean the TPlink Archer MR600?
The naming from tplink is weird, the one I have tested it on is TL-ML6400 the one you mention, the Archer MR6000 seems to be different.
I don't have the Archer device, I have a feeling there might be a new firmware and the request or response forcgi/login
is different. Happy to review the PR to merge it if you manage to get it working.
If you set a dummy username & password and provide a packet capture for the fully authentication flow, might be useful as well.
I've fixed the wrong model number and also mentioned that there's an issue with Archer MR600 in the readme now linking to this issue.
Did you manage to either do a packet capture or know why it's not working? @henrik242
Closing this due to inactivity
I see you state "TL-MR6000" in the readme, but I hope you mean the TPlink Archer MR600?
I have one of those, but I'm getting
null
fromauthenticate()
. Any ideas why?