What happened

You set the sensor to a new address. The sensor rebooted onto the new subnet. Your adapter is still on the old subnet, so the two can no longer see each other.

  before:  adapter 192.168.0.50  ←→  sensor 192.168.0.10
after:   adapter 192.168.0.50  ✗   sensor 10.0.0.10
  

This is not a fault. It is the expected consequence of step ②.

Fix

Move the adapter to the new subnet and confirm:

  ping -c 3 <sensor-new-ip>
  

If you did not record the new address, see “Recovering an unknown address” below.

Recovering an unknown address

ApproachNotes
Sweep the target subnet with the software’s scanFastest when you know roughly where it went
Check the DHCP server’s lease tableWorks if you assigned it via DHCP
Reset to factory defaultsLast resort — you lose the calibration profile

Preventing it

This failure disappears if the set-IP procedure is followed as three steps rather than one. See Set IP — the third step exists precisely for this.