Add docs for Omada device sensors (#35101)

* Add docs for omada device sensors

* tiny tweaks

---------

Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
This commit is contained in:
MarkGodwin 2024-10-21 08:56:54 +01:00 committed by GitHub
parent fa2184b5c0
commit fa1797ebf9
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -13,6 +13,7 @@ ha_domain: tplink_omada
ha_platforms:
- binary_sensor
- device_tracker
- sensor
- switch
- update
ha_integration_type: hub
@ -28,6 +29,10 @@ The integration provides basic configuration and status of Omada devices control
- Verify SSL Certificates: Enable to check the validity of the certificate presented by the Omada controller.
- Username/Password: A user account with permissions to view & configure the site is required.
{% note %}
A local account must be used for login. Do not turn on two-factor authentication for local accounts, or the integration will not be able to log in.
{% endnote %}
### Multiple Sites
If you have multiple sites managed by your controller, you will be prompted to choose which site to manage.
@ -44,24 +49,24 @@ Controller versions 5.1.0 and later are supported.
## Supported Omada devices
### Network Switches
All adopted Omada devices expose:
- Device status sensors
- CPU and Memory percentage sensors
- Firmware updates
### Network switches
- Support for enabling/disabling Power over Ethernet on a per-port basis
- Firmware Update
### Access Points
- Firmware Update
### Internet Gateways
### Internet gateways
- WAN/LAN Port connectivity sensors
- WAN Port Online detection sensors
- WAN Port Connect/Disconnect switches
- LAN Port PoE activity sensor
- Firmware Update
### Device trackers
## Device trackers
The integration can track Wi-Fi devices connected to access points managed by the TP-Link Omada controller. All known Wi-Fi clients will be initially created in a disabled state. You then need to enable the entities that you want to track.