From 8d8113fd880a11fb0f207541f55e7140bd72bf9a Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Fri, 9 Oct 2015 00:12:14 +0200 Subject: [PATCH] Move details from header to docs --- source/components/device_tracker.snmp.markdown | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/source/components/device_tracker.snmp.markdown b/source/components/device_tracker.snmp.markdown index 789fd7392ac..bdef4acbbf1 100644 --- a/source/components/device_tracker.snmp.markdown +++ b/source/components/device_tracker.snmp.markdown @@ -12,7 +12,13 @@ footer: true Most wifi-accesspoints (WAP) and wifi-routers (WRT) support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of insances and metrics, like network interfaces, disks, and wifi registrations. -This component uses python-pysnmp. +

+This device tracker needs SNMP to be enabled on the router. +

+ +OID examples: +- Microtik: 1.3.6.1.4.1.14988.1.1.1.2.1.1 (confirmed) +- Aruba: 1.3.6.1.4.1.14823.2.3.3.1.2.4.1.2 (untested) To use the snmp platform in your installation, add the following to your `configuration.yaml` file: @@ -26,6 +32,7 @@ device_tracker: ``` Configuration variables: +- **host** (*Required*): The IP address of the router, eg. 192.168.1.1. - **community** (*Required*): The SNMP community which is configured in the WAP/WRT. Most devices have a default community set to to `public` with read-only permission (which is sufficient). - **baseoid** (*Required*): The OID prefix where wireless client registrations can be found, usually vendor specific. It's advised to use the numerical notation. To find this base OID, check vendor documentation or check the MIB file for your device.