NETGEAR

This platform allows you to detect presence by looking at connected devices to a NETGEAR device.

A recent updates of Orbi APs introduced a bug which takes several hours to detects presence on your local network. The current workaround is to force this integration to use the Orbi’s API v2 by adding the accesspoints: node to your configuration.

To use this device tracker in your installation, add the following to your configuration.yaml file:

# Example configuration.yaml entry
device_tracker:
  - platform: netgear
    password: YOUR_ADMIN_PASSWORD

Configuration Variables

urlstring(Optional)

The base URL, e.g., http://routerlogin.com:5000 for example. If not provided host and port are used. If none provided autodetection of the URL will be used.

hoststring(Optional)

The IP address of your router, e.g., 192.168.1.1.

portinteger(Optional, default: 5000)

The port your router communicates with.

usernamestring(Optional, default: admin)

The username of a user with administrative privileges.

passwordstringRequired

The password for your given admin account.

deviceslist(Optional)

If provided only specified devices will be reported. Can be MAC address or the device name as reported in the NETGEAR UI.

excludelist(Optional)

Devices to exclude from the scan.

accesspointslist(Optional)

Also track devices on the specified APs. Only supports MAC address.

When accesspoints is specified an extra device will be reported for each device connected to the APs specified here, as MY-LAPTOP on RBS40. Router will be reported as AP name for the main AP. Only tested with Orbi.

The use of devices or exclude is recommended when using accesspoints to avoid having a lot of entries.

List of models that are known to use port 80:

Nighthawk X4S - AC2600 (R7800)
Orbi
XR500

See the device tracker integration page for instructions how to configure the people to be tracked.