Aisha’s right, and I’d add a few things from running Pi gateways on a production floor.
Buy a splitter that says 802.3af/at on it and lets the switch negotiate, never a passive injector. Check the cable run, long thin patch leads drop enough voltage that the Pi throttles. You can see that from the Pi itself:
$ vcgencmd get_throttled
throttled=0x50005 # bit 0 = under-voltage now, bit 16 = has happened since boot
I’d send that value to Hermetry with the probe readings. The gateway can report its own telemetry on v1/telemetry as a normal device, while the probes go on v1/gw/telemetry as children. Then an alarm rule on the gateway’s profile for pi.undervolt == 1 tells you the supply is marginal before the SD card gets corrupted.
Remember that when the gateway goes offline, every child goes offline with it. So the gateway’s offline alarm is the one that matters, and the children’s offline alarms will all fire too unless their delay is longer. We put the gateway on 300 s and the children on 900 s. The child behaviour is described here: Gateways and devices behind a gateway.
And keep the SQLite buffer you’d use anyway, a PoE switch reboot during a firmware update is a 2-minute outage.