The one rule

Your computer’s Ethernet adapter and the sensor must always be on the same subnet.

This is the single most common cause of “the sensor is dead” reports. The sensor is fine; the computer simply cannot reach it.

The rule applies twice:

WhenWhat goes wrong if you skip it
Before you first discover the sensorThe software shows an empty device list
After you change the sensor’s IPThe sensor is now on the new subnet, your adapter is still on the old one, and the device disappears

Factory default

Sensors ship with a static address on a fixed subnet. Confirm the exact value for your model on its series page, then set your adapter to a free address in the same range.

Windows

  1. Open Settings → Network & Internet → Ethernet → Edit IP assignment
  2. Switch from Automatic (DHCP) to Manual
  3. Enable IPv4, then enter:
    • IP address: any free address in the sensor’s subnet
    • Subnet mask: same as the sensor
    • Gateway: leave empty
  4. Save, then verify with ping
  ipconfig
ping <sensor-ip>
  

macOS

  1. Open System Settings → Network → Ethernet → Details
  2. Set Configure IPv4 to Manually
  3. Enter an address in the sensor’s subnet, same mask, leave the router empty
  4. Apply, then verify
  ifconfig en0
ping -c 3 <sensor-ip>
  

Multi-sensor installations

Give every sensor a fixed address outside the DHCP pool, and document the assignment. Two sensors on the same address produce intermittent behaviour that is very hard to diagnose later — one of them answers, the other does not.

PracticeReason
Fixed addresses outside the DHCP rangeThe router will never hand the address to a laptop
Label each sensor with its addressService visits years later still work
Keep a table of sensor ↔ address ↔ locationDebugging a multi-sensor scene needs it

Next

Once the host and sensor agree on a subnet, go to Find sensor.