beacon 00000004

fleet › 00000004
IST
refreshes every 30 seconds

00000004

present
Last reported bygw-1544D93A6A2F37E830d ago, when it last changed
First seen
Signal-44dBmas the gateway heard it, at that moment
Beacon battery100%reported by the beacon itself
Status bits0passed through, never interpreted
Events4arrivals, departures and snapshots

Where and when

These are changes, not sightings. §07 has the gateway report arrivals and departures; a beacon that stays put produces no message at all, so an empty stretch here means nothing moved. The periodic snapshot is what refreshes a stationary beacon, every snapshot_h hours.

A beacon also reports no position. The positions below are the gateway's, at the nearest fix it had — the last column says how far from the event that fix was taken.
TimeEventGatewayIn messageGateway positionFix age
snapshotgw-1544D93A6A2F37E8782-33.81647, 151.184010s
snapshotgw-1544D93A6A2F37E8776-33.81650, 151.183990s
arrivedgw-1544D93A6A2F37E8770-33.81648, 151.184030s
arrivedgw-65CDC543D6A5D88814083-33.81653, 151.184070s

Beacon battery

Level reported by the beacon99 to 101 % across 16h 39m, 4 samples
101 99
§13 tells a flat beacon cell from a departed asset using this. A level that fell to nothing before the beacon vanished is the first reading, not the second.