beacon a128ff86

fleet › a128ff86

13 Nov 04:16:12 IST
refreshes every 30 seconds

a128ff86

gone

Last reported by	gw-1544D93A6A2F37E8		34d ago, when it last changed
First seen	09 Oct 06:59:13
Signal	-54	dBm	as the gateway heard it, at that moment
Beacon battery	94	%	reported by the beacon itself
Status bits	0		passed through, never interpreted
Events	4		arrivals, 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.

Time	Event	Gateway	In message	Gateway position	Fix age
09 Oct 08:00:15	departed	gw-1544D93A6A2F37E8	515	-33.81646, 151.18401	0s
09 Oct 07:59:05	departed	gw-65CDC543D6A5D888	12292	-33.81651, 151.18399	0s
09 Oct 07:00:19	arrived	gw-1544D93A6A2F37E8	514	-33.81648, 151.18397	0s
09 Oct 06:59:13	arrived	gw-65CDC543D6A5D888	12291	-33.81649, 151.18397	0s

Beacon battery

Level reported by the beacon93 to 95 % across 66s, 2 samples

§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.