I checked your report, and I see that login has failed because either the credentials are incorrect, or your Omada controller uses another login method. What is your Omada controller version?
I tried creating a new custom local user account on my Omada controller and using that. But unfortunately still get the same error.
Diagnostic report for new local user credentials:
07cca3a8-cd5c-4e32-912d-82c4f3cd759d
(I have previously suggested that an advanced user function on Homey Pro that would be extremely useful when trying new apps or generally just having issues would be view only access to logs. I’m sure that would help a lot of people solve problems/errors with a lot less banging heads against walls ha ha)
I do try to keep all my devices (networking, NAS, Raspberry Pi servers, desktop & mobile devices) running on all the latest updates/firmware.
The credentials are definitely correct, tried autocomplete from my password manager, copy & paste, and manually inputting.
You need to provide an email address. For me this is a hint you need to connect your Omada controller with the cloud if i understand correctly. I try to avoid cloud stuff as much as possible so I didn’t continue on there.
It’s usually the email address of the TP-Link ID you used when setting up the controller. The app communicates locally via the IP address.
Hm, I don’t have a TP-Link Id, when i made the setup (Docker) i just needed to setup a local account.
A local account should also work. Just enter the username of the account in the email address field.
It might be beneficial in a future release to re-label that entry field “e-mail address / local username” to save keep getting asked similar questions, or people being put off thinking it’s cloud account authentication only.I have noticed Homey apps in general do have a tendency to leave you guessing what exactly to enter in which fields.
I’ll close my cake hole and go mind my own business now ha ha
I did a login now, no error message but no devices were found. Do i need to enable something in Omada?
No everything should work without changing settings. Do you have the latest Omada controller version (6.2)?
Oh its 5.15 in my Docker, i will check this why it isn’t on 6.x, i have auto upgrade enabled on Docker on Unraid. I will report back
Yes you need the latest version. They recently changed the method of retrieving the clients list from the controller.
Ok, thanks for the hint, I did upgrade now, I can see now all my clients. Will you add later the possibility to add the access points/router/switches in Omaha itself too?
Best regards and great work!
Yes, I will add EAP/switch/router support later as well. I first want to get the clients working correctly.
