TP-link omada integration not working anymore after update to core-2024.1.6

[jodewee]

The problem

Tp-Link Omada integration does not work anymore (controller ER7212PC) after updating from 2024.1.5 to 2024.1.6
Failed to connect:

What version of Home Assistant Core has the issue?

core-2024.1.6

What was the last working version of Home Assistant Core?

core-2044.1.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

TP-link omada

Link to integration documentation on our website

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

Diagnostics information

home-assistant_tplink_omada_2024-01-31T12-11-31.401Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[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)}}

[jodewee]

[jodewee]

when i try to remove and add it again, with ssl disabled, it won't work anymore

[joostlek]

Can you maybe downgrade to 2024.1.5 and check if it does work on that version?

[jodewee]

Can you maybe downgrade to 2024.1.5 and check if it does work on that version?

Yes, it works again after downgrading to 2024.1.5
Already also tried to re-upgrade to 2024.1.6 after downgrading again, and then, the integration breaks again.

[joostlek]

We might have found a solution, could you maybe give this a shot:

cd /config
curl -o- -L https://gist.githubusercontent.com/bdraco/43f8043cb04b9838383fd71353e99b18/raw/core_integration_pr | bash /dev/stdin -d tplink_omada -p 109212

And reboot afterwards?

[jodewee]

unfortunately that didn't help. Also reboot the whole vm after first try a "restart homeassistant"
Install was scuccessfull though

[jodewee]

[joostlek]

Can you maybe share full logs? I don't see this error in the logs, but I would expect to see it. Can you also verify that this is the tplink_omada integration and not the omada custom integration?

[jodewee]

is says custum integration after i ran that command above.

[jodewee]

home-assistant_tplink_omada_2024-01-31T14-08-15.795Z.log
home-assistant_2024-01-31T14-08-35.458Z.log

[joostlek]

For some reason tplink_omada isn't shown on the list at the top of your log

[jodewee]

anything else i can do?

[jodewee]

i re-ran the command, and enable the debug logs again on the integration;
home-assistant_tplink_omada_2024-01-31T14-12-51.100Z.log

[jodewee]

i can try to remove and re-add the integration/omada controller?

[jodewee]

ok, that seems to be working, but only with the custom inegration you just provided,
because i also tried it before i made the issue her on the forum

[joostlek]

Can we verify this works correctly? Then we can merge this and release it as a fix

[jodewee]

Thanks for the quick response, i suppose you'll have to integrate that fix into the next core release, and after that i rmove it from the custom integrations?

[joostlek]

Yep!

[m2r57700]

Hi
I have same issue.
Do you know when the next core release will be deployed ?

[MartinHjelmare]

Same procedure as every yearmonth. 😄

We release on the first Wednesday of the month.

[m2r57700]

So only a few days to wait.

[CaptMauser]

Hello,
Todays version 2024.2.0 didn’t solve the issue… 😳
Still no tplink Omada integration working.

The workaround above also didnt work for me...

[m2r57700]

For me it works again but
For the host I use only the Ip@ of the controller with the port X.X.X.X:8043 (no http, no https)
I didn't select the Verify SSL Certificate.

[CaptMauser]

I am using SSL, maybe this is the difference 😳

[kistelek2]

Broken again here after update to 2024.2.0 with apparently the same error.

[CaptMauser]

I am using SSL, maybe this is the difference 😳

Just did a reinstall of the ingetration and now it works again, still shows that it is a "custom integration"...
AND: i am not using SSL, this was a wrong information

[joostlek]

If you tried the fix I posted above, please don't forget to remove /config/custom_components/tplink_omada. 2024.2 has the same version.

[CaptMauser]

Can you please write exactly what I should write in the Terminal, since I am a real rookie in Linux... ;)

[joostlek]

Please checkout support on the discord for that, I'm not sure what your system looks like and I don't want to break anything

[CaptMauser]

I did install my backup from yesterday where I did not apply the fix, then istalled back the 2024.2 and reinstalled the integration, now everything working again (without "custom integration")

[Steve2017]

We might have found a solution, could you maybe give this a shot:

cd /config
curl -o- -L https://gist.githubusercontent.com/bdraco/43f8043cb04b9838383fd71353e99b18/raw/core_integration_pr | bash /dev/stdin -d tplink_omada -p 109212

And reboot afterwards?

I had updated to 2024.2 and could not get Omada to run - tried this and it worked.

[joostlek]

In that case it's just coincidental, 2024.2 has that same fix, this should not be used anymore since you might be missing future updates

[kistelek2]

In that case it's just coincidental, 2024.2 has that same fix, this should not be used anymore since you might be missing future updates

I didn't use the fix for the original fault, I rolled back the upgrade instead. Now with 2024.2 I don't have my Omada working as I posted above. I don't really want to roll back again as I lose data from other places and I can live without the Omada for a while. Is there some other fix or issue?

[Steve2017]

In that case it's just coincidental, 2024.2 has that same fix, this should not be used anymore since you might be missing future updates

Turns out I needed to restart HA a couple of times. Once I removed the custom component set up by that command and restarted twice, it allowed me to install the integration. I just had to make sure I had unchecked “Validate SSL”.

[P3TACCO]

I cannot get back in either.
I deleted the integration and now when I try to start up again I can't log in
I have the OC200 hardware controller - all was working great before the update that broke it.

If I use just the IP address and uncheck the "Verify SSL" box
and enter my login and password I get "Invalid authentication" error, but I can log in through a web browser with that info no problem.

If I keep the Verify SSL" checked I get "Failed to Connect".

When I try the IP with the HTTP and HTTPS ports included
I Get "Unexpected Error".

I've tried the IP with http:// and https://
And tried copying the web browser URL which has a alphanumeric string after the IP number.

Still nothing.

The Docs need to be VERY specific about what the format for the "Host URL" is expected to be - that seems to be very sensitive/prone to errors.

Rebooted and reloaded HA several times - no change

Very frustrating

[Steve2017]

If I use just the IP address and uncheck the "Verify SSL" box and enter my login and password I get "Invalid authentication" error, but I can log in through a web browser with that info no problem.

If I keep the Verify SSL" checked I get "Failed to Connect".

When I try the IP with the HTTP and HTTPS ports included I Get "Unexpected Error".

I use the software controller in a VM on my Synology NAS, so it might be different for me.

I think I just used the IP address with the port (8043 with no HTTP or HTTPS) and I deselected the "Verify SSL" box.

I did need to restart HA a couple of times and make sure the HACS version I had installed was completely gone - including by deleting a folder in \config\custom_components

[P3TACCO]

Ok...

Finally got in.

I had to make a secondary administrator account on my Omada controller.

I kept getting the "Invalid authentication" error. And my Omada controller was recording the failed log in attempt. So HA and Omada were talking.

The password for my primary admin account has special characters in addition to letters and numbers.
I think HA is not parsing/passing these correctly and that's what is throwing the authentication error.

I made a second admin account and used only numbers and letters for the password.

I used just the IP address of the controller, no port addendum, and unchecked the SSL box.
Logged right in with the new account.

[MarkGodwin]

Without giving too much away, can you describe the special character that was causing the problem?

When I try to set a password in the Omada interface with basic international characters, the controller refuses with the error: "This field should be visible ASCII or space."

[P3TACCO]

It was the "#" sign. I haven't tried others.
The Omada app accepts it as a valid character in the password - but I don't think it was being parsed correctly by the HA integration.
Upper case, lower case and numbers in combination all appear to work correctly.

The thing is, it worked OK before the update that broke the integration.