Connectivity & power window — 03:15–03:35 PM (EEST)

Device Amur Power Monitor (c59e4e5b) · 2026-08-29 · window shown in local time (UTC+3) · DB range 12:15:00–12:35:00 UTC
Readings plotted
–
Offline/online gaps
–
Longest gap
–
Power-blip events
–

Current & voltage, with offline gaps marked

Current (mA, left axis) Voltage (V, right axis) MQTT reconnect flap (≤ 38 s, load kept running) Power blip / reboot (near-zero current, voltage spike)

Gap log

#Offline atOnline atDurationCurrent just before → afterType

All gaps > 10s since 00:00 (local)

Full device history for today, not just the 20-minute window above — – gaps, longest –, total downtime –.
#Offline atOnline atDurationCurrent just before → afterType

Reading

This 20-minute stretch is noisier than the device's baseline: 11 brief offline→online flaps occur, each a few seconds to ~38 seconds long. In 10 of the 11, current resumes right where it left off (1300–1700 mA) — those are ordinary MQTT/Wi-Fi reconnects, not evidence the load changed, and none came close to the 5-minute streakBreakGapMs or 30-minute confirmMs the freeze detector uses.

One gap is different. At 12:27:24 UTC (03:27:24 PM), after a 37 s gap, current reads 0.24 mA then 0.49 mA while voltage jumps to 5.15 V (vs. the nominal ~5.09–5.10 V) — the load actually disappeared, not just the telemetry. It's followed by a ragged restart ramp (456.8 → 862.5 → 1346.7 mA across ~5 s), a brief undershoot around 12:27:44–53 (1032–1187 mA), and then a settle into a visibly higher steady regime (~1650–1850 mA) than the ~1350–1650 mA cycling seen beforehand — shaded in the lighter red band on the chart.

This is the same brownout/reboot signature seen at the onset of the earlier, much longer freeze event (idle period 3), just far shorter and occurring mid-activity rather than after a long idle. No freeze_suspected event was logged for this window, correctly — the detector is scoped to sustained freezes, not brief reboot blips like this one.