2024.1.6 - TP-Link Omada integration won’t connect to controller

[Steve2017]

The problem

On updating to 2024.1.6 I lost functionality on a number of intergrations, namely TP-Link Omada (software controller), Android TV (Sony TV) and a couple of HACS integrations (Local Tuya lost devices but they could be reinstalled)

After the update, the Omada integration was reporting all entities unavailable. I could not get them to change to available, so I deleted the integration and started again. When trying to set up the Omada integration, the request window instantly responded that there was no connection. It did not even try to locate the controller, so there was no timeout to speak of. It was an instant “no connection”.

I can see some changes to the TP-Link integration in 1.3 but that was for LTE and had no obvious effect on me.

The Android integration lost connection to my Sony TV but I could add it as new.

Rolling back to 2024.1.5 restored all functionality. I have no log of the events, because I restored an earlier version.

What version of Home Assistant Core has the issue?

2024.1.6

What was the last working version of Home Assistant Core?

2024.1.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Omada (TP-Link)

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tplink_omada

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No logs - system was restored to 1.5

Additional information

HA is running on Proxmox. An update and reboot for Proxmox made no difference.

[home-assistant]

Hey there @MarkGodwin, mind taking a look at this issue as it has been labeled with an integration (tplink_omada) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tplink_omada can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tplink_omada Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tplink_omada documentation
tplink_omada source
_{^{(message by IssueLinks)}}

[Steve2017]

At least one other person has reported similar in the blog comments
https://community.home-assistant.io/t/2024-1-happy-automating/665947/417?u=steve61

[louisrg0011]

same problem with the integration TP-Link > TP-Link Omada on 2024.1.6, work very well before the update.

[joostlek]

Probably fixed by #109212