Hi,
I would like to have a TP-Link Omada app like “Ubiquiti UniFi Network” app. I am not a developer.
Is there more interest for this?
Thank you!
The quickest way to check whether a device is supported is to search the app store. If you can’t find the specific device, have a look for the brand of device you are looking for.
If no app is found, you can make a request to Athom or the Homey Community to add support. See [Requests] Official Homey App and Device Request for ways of doing that.
I’m already working on such an app. What features would you like to have included? The signal strength, IP and connection status will be supported when it’s released, but let me know if you want any other features
Switch/AP up/down traffic would be nice if possible. Also switch/AP up-time, and if a firmware update is available (the Omada controller can be configured to perform regular checks) so you could create a flow to notify you when an update is needed for example. And maybe display on the Omada Controller tile in Homey the new Site Health Score out of 100, if that’s available through their API. Just off the top of my head thoughts.
Great, would love this too.
For me I would like to see the same functions and Flow cards as the Unifi app: Ubiquiti UniFi Network | Homey
Installing it! I will provide you the feedback later.
Hi Sven,
great, thank you a lot 
Im installing it right now too, will give you feedback after some playing too.
Installing it also. And I too will have a mooch with it on my network and give some feedback.
Excellent work, thank you!
I’m not sure what I am doing wrong, but I can’t seem to connect any of my network devices, and the only error I get is “Something went wrong, please try again.”
Multiple users have this issue. Can you share a diagnostics report?
I will generate and share one shortly.
What are the expected targets for the devices being added in Homey? (OC2/300, switch, AP) And as Omada SDN uses both cloud and local user credentials, which is applicable, and how does it handle the 2FA? (as Omada doesn’t appear to have an application password for circumventing 2FA, and I obviously don’t want to disable the security of my network hardware.)
Diagnostic report ID: 530a2826-9373-4e89-9fd3-70a108907c05
I see “ECONNREFUSED” errors, which means that Homey was unable to reach your Omada Controller. This can occur when you have a firewall rule blocking access between Homey and the Omada controller. I see multiple IPs, are you sure you entered your Omada controller IP correctly? 2FA is not supported yet, since the app needs to log in periodically when the session expires (the Homey app uses the same interface as the Omada web UI). I think local users are supported, but I’m not sure since I only use the TP-Link ID login.
For now you can only add Client devices. Clients (phones, tablets, other devices connected to your WiFi network) can be blocked, request reconnect and you can view the IP address, connection status and signal strength in Homey.
I couldn’t see any settings in the app to add the OC300, so I am presuming that when you add a Homey device of TP-Link Omada and the only device to add is labelled “Client” it means for you to enter the IP address, email address, and password of your Omada controller?
I’m just guessing here (Homey app documentation is ominously scarce for all apps… and I have only had my Homey a couple months, so I am still mostly just guessing and see ha ha) I’m not quite sure how your app is intended to work, so please excuse my ignorance or asking any dumb questions.
My hope is to eventually be able to monitor all my Omada network devices through Homey, and be able to enable/disable switch ports, power cycle PoE devices, and enable/disable SSIDs (I have 4 at present for different purposes) as well as control WiFi clients. Lofty hopes I know, but worthy goals I am sure.
I’m probably unable to connect due to 2FA, but I am not comfortable disabling that for my cloud account, as it’s used by all my TP-Link hardware.
I forgot to add, there is no firewall between my Homey Pro and OC300 yet. I wanted to get everything working before making things more complicated with firewall rules… at least if you know it works without the firewall, then it’s only the firewall rules to troubleshoot.
I tried both cloud and local users using the OC300 controller IP, and the IP of the web interface of AP… all before sending the report. The same result for all combinations.
