eqtrack fleet

IST
refreshes every 30 seconds
0/2
gateways reporting
4
beacons present
6
beacons ever seen
970
messages accepted
0
contract breaches

Gateways 2

gw-1544D93A6A2F37E8

silent 4 beacons
Last message29d ago
Firmwaree1f2415
Config version7current
Message sequence784per gateway, not per beacon
Restarts2
Supplybaton battery
Cell voltage4,057mV90% charged
Peak draw16mAheaviest sample
Modem in PSM96.6%of the last window
Position-33.81650, 151.1839929d ago

gw-65CDC543D6A5D888

silent 2 beacons
Last message30d ago
Firmwaree1f2415
Config version7current
Message sequence14,084per gateway, not per beacon
Restarts45
Supplybaton battery
Cell voltage4,194mV100% charged
Peak draw8mAheaviest sample
Modem in PSM89.5%of the last window
Position-33.81650, 151.1839830d ago

Beacons 6

BeaconStateLast gatewayLast heardWhereRSSI dBmBattery %
00000001presentgw-1544D93A6A2F37E830d ago-33.81647, 151.18401-3893
00000002presentgw-1544D93A6A2F37E830d ago-33.81647, 151.18401-3795
00000003presentgw-1544D93A6A2F37E830d ago-33.81647, 151.18401-41100
00000004presentgw-1544D93A6A2F37E830d ago-33.81647, 151.18401-44100
a128ff86gonegw-1544D93A6A2F37E834d ago-33.81648, 151.18397-5494
00000042gonegw-1544D93A6A2F37E834d ago-33.81645, 151.18401-6085
§07 is a delta protocol: a gateway reports arrivals and departures, not sightings. So last heard is the last time a gateway said it could hear this beacon — an arrival, or a snapshot naming it. A beacon sitting still generates nothing in between, and a gap up to the snapshot interval is the protocol working rather than a beacon going quiet.

It is deliberately not the moment the beacon was reported gone. A departure is noticed at the next scan, up to a whole interval later, and on a gateway that has moved since, somewhere else — so where resolves the position of the gateway when it last heard the beacon, not when it noticed the silence. The other reading puts an asset where it demonstrably is not.

Contract 0 recorded, 0 breaches

None. Every message has kept the contract.

Location lookup

Location lookup is on. 0 request(s) to Google, 0 answered from cache, 0 error(s). Fixes are keyed by the access points heard, so a gateway that has not moved is not asked about twice.