From e0cb63400769cf3932e21a2b8733cdb2b1d84861 Mon Sep 17 00:00:00 2001 From: Robert Svensson Date: Fri, 18 Aug 2023 13:16:07 +0200 Subject: [PATCH] Update UniFi Poe port documentation (#28607) Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/unifi.markdown | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/source/_integrations/unifi.markdown b/source/_integrations/unifi.markdown index 59aefee45f1..d2a43d83c71 100644 --- a/source/_integrations/unifi.markdown +++ b/source/_integrations/unifi.markdown @@ -96,11 +96,9 @@ Clean up clients on the UniFi Network application that has only been associated Allow control of network access to clients configured in the integration options by adding MAC addresses. Items in this list will have a Home Assistant switch created, using the UniFi Device name, allowing for blocking and unblocking. -### Control clients powered by POE +### PoE port control -Entities appear automatically for each connected POE client. If no POE client device is in operation, no entity will be visible. Note: UniFi infrastructure devices such as access points and other switches are not (yet) supported, even if they are powered over ethernet themselves. - -Note that POE control actually configures the network port of the switch which the client is connected to. +Provides per-port PoE control. Entities are disabled by default. This feature requires admin privileges. ### Control DPI Traffic Restrictions