Router model TP-Link C5400 not compatible with tp-link presence detection

[cbgta]

Home Assistant release with the issue:
0.69.1

Last working Home Assistant release (if known):
None

Operating environment (Hass.io/Docker/Windows/etc.):
Linux ubuntu 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Running the official docker @ homeassistant/home-assistant:latest

Component/platform:
device_tracker.tplink

Description of problem:
This router does not have a "username" it only accepts a password for logging in. I have tried using admin/root/administrator to no avail. I have also tried the javascript tricks in the documentation, but they just respond with this:

document.getElementById("login-password").value;
VM111:1 Uncaught TypeError: Cannot read property 'value' of null
    at <anonymous>:1:42

document.getElementById("pcPassword").value;
VM119:1 Uncaught TypeError: Cannot read property 'value' of null
    at <anonymous>:1:38

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

device_tracker:
  - platform: tplink
    host: 192.168.0.1
    username: admin
    password: !secret tplink

Traceback (if applicable):

2018-05-27 12:16:23 ERROR (SyncWorker_4) [homeassistant.components.device_tracker.tplink] AP didn't respond with JSON. Check if credentials are correct
2018-05-27 12:16:23 ERROR (SyncWorker_4) [homeassistant.components.device_tracker.tplink] Couldn't fetch auth tokens! Response was: {"errorcode":"login failed","success":false,"data":{"failureCount":4,"errorcode":"-5002","attemptsAllowed":6}}
2018-05-27 12:16:24 ERROR (SyncWorker_4) [homeassistant.components.device_tracker.tplink] Router didn't respond with JSON. Check if credentials are correct.
2018-05-27 12:16:24 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform tplink

Additional information:
The router has Alexa and IFTTT integration, so it should be possible to get something sensible out of it! :-)

Maybe the TP-link cloud is the right way to attack this problem?

Routers with similar firmware that i found that probably have the same problems: C1900, C2300, C3150.
Assumption based on this router emulator: https://www.tp-link.com/us/support/emulators

[Trashmee]

Looks similar to this one - w/o real solution yet:

#9120

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[cbgta]

@balloobbot I tested again on 0.77.3. The issue is still there.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.