TP-Link Deco integration in HA - problem connecting

Third party integrations
1

Dear all,

Unfortunately, I couldn’t find anything using the search function, and even Google and the integration documentation didn’t help me:

I have installed Home Assistant on a Raspberry Pi as a newbie and would like to control the devices on my TP-Link Deco routers via the HACS integration - among other things to be able to assign them to persons.

Unfortunately, I am already failing to connect to my router (Deco X50) after installing the integration.

I get the error message “unable to connect to host” in the mask where I have to enter host, username and password, etc., although it is 100% the correct host IP (192.168.68.1), even a https:// in front of it does not help. With the browser I can call up the admin panel with this IP without any problems.

Is there anyone here who could help me?

2

I have same problem. Do you resolve this?

3

Sams issue. Any suggestioni. Decò m5

4

I have same problem with Deco x55.

5

Same problem here with another Deco M5

6

Same here, xe75pro

I had the M5 for a while, and it worked fine with HA. But now I upgraded my mesh, removed the integration and added the new one… well, last step failed in HA…

I see many versions with this issue, including the for me previously working m5. So my guts feeling says there’s a general issue in the current setup. This could be because either side has changed or I am forgetting something to grant access to it which I didn’t forget before.

Used http and https without the checkmark, no successful result

7

Same problem here with the x50 decos

8

Hi, i bouth a Deco X50 and have the same problem, did anyone solve it?

9

Update: works for me with my new XE75Pro

I noticed an update on the deco integration and I decided to try again.
Just to be sure I removed and reinstalled the integration, and followed the readme exactly. So username admin, and then password. IOS helps with the password, but it also changes the username. This in this case should not change, so I set it back to admin, and it all works fine, like it did with my M5.

Since the auto change of the username could have been unnoticed, hereby a heads-up. But it could also have been fixed with the update, I don’t know for sure.