Well, I’m back… Back in mid-September, I got my Archer C5400X V1 working, and it worked well, up until recently…
I noticed the issue when “Presences” became “Unknown”, which led me to this integration, and I saw it had “failed to set up”. (it had been previously set up, successfully)
I had changed nothing, but I notice that the TP-Link Router Integration is now at v2.0.0… I wonder if this has anything to do with it…
When I click on Configure, everything looks like it did before (including the “encrypted” password), but when I hit “Submit”, I get a message saying my router is NOT supported!
As you see, it points me toward this url, which is for a C6U API, but I don’t see how that applies to me…
I’ve also tried the regular password, checking and unchecking SSL, etc., but to no avail.
I looked for the reference to “encrypted password”, to see if I had to redo it, but it seems to have disappeared? Is it no longer applicable? Am I missing something?
in the version 2.0.0 the encrypted password was deleted. Ty to readd your router to HA using your regular password. In the screenshot that you uploaded - you use the encrypted password that is not supported now.
I even tried changing my router’s LOCAL password, to be sure it was different from the “Cloud” one. I logged out of the router’s GUI before returning to attempt login through HA.
FWIW, I’ll try rebooting the actual router… That’ll take some time, so I’ll go do something else (lunchtime here!), and report back IF it changes anything (which, TBH, I doubt)
Hi, Alexandr
I installed version 2.0.1, and re-attempted using the encrypted password (following the instructions on your site). Unfortunately, still no luck…
Here are two screenshots of my tries with SSL checked, and unchecked, respectively.
Tested the integration on my VR600, working nicely. No CPU and RAM stats (not really an issue though).
Is it possible via this integration to get the WAN IP from the router?
Well, this is odd… In that first screenshot, I had obscured the encrypted password, consisting of a 256-character hexadecimal string.
I followed your instructions here, to the letter.
In following them again, to produce a second screenshot (I was going to munge, rather than obscure, the password for posting), I noted that the encrypted password was different. This time, IT WORKED!
It is possible that I followed the first procedure in Edge, then copied the value to Firebox… This time, I did everything within Firefox.
P.S.: FYI, if it can be of use to you, here are the stats returned by the sensors:
(note the six ‘unavailable’ sensors at the bottom; not an issue for me, but I thought you’d want to know)
Device tracking is working - Go to Developer tools and search for your MAC address - you’ll find sensor like device_tracker.YOUR_MAC or device_tracker.YOUR_PHONE_NAME .
Added Router data fetching Switch - you may disable router data fetching before accessing the router, so it wont logging your out. If you forget to enable it back - it would be automatically enable after 20 minutes
Added service for sending SMS message - Available only for MR LTE routers