I didn’t try DNS name as I don’t have one normally. So I tried http://ip https://ip, https://ip/api/logon etc. Nothing works. Will try to set a DNS name
I also tried everything but not working. Switching on/off redirecting to HTTPS - but nothing change
Don’t think setting a DNS Name should be the solution. I would like to work with ip address also
There’s supposed to be an update coming out that will allow the ip to work as well, but until then, if you want to use the integration using a name instead of ip works. I agree it’s a bit silly to have to use the name, but bugs are bugs.
FWIW, currently only switches are pulled in from this integration (not APs or anything else) and only the poe for the ports. Nothing else. IMO, this is kind of a waste of an integration at the moment.
It is hard to be patient, but still this has more than the other integration that only had device trackers. Plus other support is planned so hopefully it can get to feature parity with the unifi integration and people can enjoy the same or similar functionality for a lot less money.
The router and AP device trackers of the HACS integration provide a lot of usefull information in the attributes.
My hope is that the new official integration will follow, but I don’t expect it for the near future.
source_type: router
ip: 10.0.0.2
mac: 1c:61:b4:XX:XX:XX
host_name: AP Büro
type: ap
model: EAP225-Outdoor(EU) v3.0
firmware: 5.0.8 Build 20220613 Rel. 51936
status: 14
status_category: 1
clients: 17
users: 17
memory: 56
download: 77504140
upload: 7469739
tx_rate: 4207
rx_rate: 2033
icon: mdi:access-point-network
friendly_name: AP Büro
cpu: 1
source_type: router
ip: 10.0.0.1
mac: 1c:61:b4:XX:XX:XX
host_name: ER605
type: gateway
model: ER605 v2.0
firmware: 2.1.2 Build 20230210 Rel.62992
status: 14
status_category: 1
icon: mdi:router-network
friendly_name: ER605
cpu: 15
memory: 33
download: 528633580799
upload: 8066007689
clients: 4
1 Like
Allright, I wanted to try, but can’t get it to work. What is the exact URL to use?
I have set the controller to use omada.local as hostname, I can ping it, so I would think https://omada.local:443
You shouldn’t need the :443, but I don’t think it will hurt.
Honestly, I’m glad there are so many people that want to use an Omada integration. It took a long time to get this off the ground since I originally submitted it, but I did have plans to grow it a lot after getting the inital PR approved. The PR rules say you can only start with a single domain, so I chose switches for the PoE control, mainly because it’s what I actually needed first.
Sorry about the initial bugs - I have a DNS name for my controller, and I didn’t think to try with an IP address. 
Fixes for these two things should be relatively easy. I’m not exactly sure how quick the HA release cycle is during the month, but hopefully you won’t have to wait too long. It looks like there are some other weird problems, but hopefully that will become clearer once all the noise dies down.
So. I do have lots planned, also willing to accept help 
And, look at it this way, last week there was no integration, which isn’t a lot better than having a broken one…
5 Likes
Yeah I know, it was just to prevent questions about the configured port 
if you need help on any topic (except developtment), i’m ready to do so. I tried the custom component before and was really eager to jump to this one instead.
Do i understand it wont work on config with just IP address?
I might have some documentation suggestions 
Thanks. It depends on your port setting I guess, for me it would be 443, but it’s not working.
Hopefully in the next update
very weird… in browser url, this work. Setting up the intragtion, it doesnt. There is no log at all, so i cant figure out which part is wrong.
@bagpuss did you have a peek at the custom component that already existed? ha-omada/config_flow.py at ed823c731af246bc6dd0286f6fb548d275321166 · zachcheatham/ha-omada · GitHub
that config flow worked for me, maybe cherry pick some setup there?
How can I find out my dns name?
Noob question: Will this integration allow us to control clients?
eg. I currently use Omada android app to allow or block internet access to my son’s tablet. Is there a roadmap to allow such functionality in this integration? If there is a way to do it, I can leverage home assistant automation on a whole lot of things.
For starters you should set it on your DNS server. After that in the interface, Settings, Controller > Access config
Anyway, it doesn’t work for me
1 Like
Works fine for me to control POE on/off state
Verify SSL off
Or
Verify on, if you have a let’s encrypt cert.
With the new Home Assistant 2023.3.2 I noticed an update to the TP-Link integration.
I was hopefull about it, but unfortunately still not working.
The good thing is: there’s a different error message now: Invalid flow specified, coming from styles.ts:353
Works for me as well, https://ip-address, verify SSL off. It does not yet recognize any devices other than the OC300 hardware controller I have and defaults to the only one site I have.
Am very excited to start testing as addiitonal functionality comes online. Below is the information about my current setup if needed. Which devices are going to next be supported? They should be all the below since I am more important than everyone else (ROFL)…
The Omada hardware I have is:
OC300 Hardware Controller
TL-ER7206 Router
TL-SG2218 Switch
EAP225 Ceiling WAP (two of these)
EAP225 Outdoor WAP
The router and switch are connected directly by CAT6
All three WAPs are connected with CAT6 directly to the switch
System Information
| version | core-2023.3.2 |
|---|---|
| installation_type | Home Assistant Supervised |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.10.10 |
| os_name | Linux |
| os_version | 5.10.0-21-arm64 |
| arch | aarch64 |
| timezone | America/New_York |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.31.0 |
| Stage | running |
| Available Repositories | 1309 |
| Downloaded Repositories | 24 |
AccuWeather
| can_reach_server | ok |
|---|---|
| remaining_requests | 17 |
Home Assistant Cloud
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Debian GNU/Linux 11 (bullseye) |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.03.1 |
| agent_version | 1.4.1 |
| docker_version | 23.0.1 |
| disk_total | 915.4 GB |
| disk_used | 16.9 GB |
| healthy | true |
| supported | true |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | AppDaemon (0.11.0), Core DNS Override (0.1.1), Duck DNS (1.15.0), File editor (5.5.0), Home Assistant Google Drive Backup (0.110.1), Log Viewer (0.14.0), Mosquitto broker (6.1.3), Samba share (10.0.0), Terminal & SSH (9.6.1), AdGuard Home (4.8.2) |
Dashboards
| dashboards | 5 |
|---|---|
| resources | 15 |
| views | 29 |
| mode | storage |
Recorder
| oldest_recorder_run | February 7, 2023 at 1:58 AM |
|---|---|
| current_recorder_run | March 8, 2023 at 4:39 PM |
| estimated_db_size | 2256.60 MiB |
| database_engine | sqlite |
| database_version | 3.38.5 |