[archer-mr600] Unable to authenticate (returns null)

[henrik242]

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 from authenticate(). Any ideas why?

[henrik242]

I see that both data and sign are set to seemingly sane values in fetchSessionId.js, but the fetch response is null.

[hertzg]

There are two cases when it can return null

when fetchBusy() returns isLoggedIn as false

node-tplink-api/src/authenticate.js

Lines 21 to 24 in 4ff2c6d

	const { isLoggedIn } = await fetchBusy(baseUrl);
	if (isLoggedIn && !forceLogin) {
	return null;
	}

or if it was not abe to obtain sessionId (probably wrong password or smth?)

node-tplink-api/src/authenticate.js

Lines 26 to 34 in 4ff2c6d

	const sessionId = await fetchSessionId(baseUrl, {
	encryption,
	sequence,
	username,
	password,
	});
	if (!sessionId) {
	return null;
	}

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.

[hertzg]

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.

[hertzg]

Did you manage to either do a packet capture or know why it's not working? @henrik242

[hertzg]

Closing this due to inactivity