AxeSentry

A quieter phone and a tidier Bitaxe swarm. SWARM HEALTH AT A GLANCE • The dashboard graph is now a health timeline: it shows when devices went offline, ran hot or dropped below their hashrate floor, and how many. • A summary underneath says what's wrong right now — tap to see which devices. • Devices that haven't answered yet after you open the app show as "checking" instead of offline. • Each device's History shows a health strip and how much of the time it stayed healthy. A BETTER LIVE ACTIVITY • Shows how many devices are online (for example 7/9) and flags offline ones, on the Lock Screen and in the Dynamic Island. • Turns itself off when you leave your miners' Wi-Fi, and shows "Paused" instead of old numbers when the app isn't updating. • Prefer it on the Lock Screen only? Turn off the Dynamic Island in Settings. NAME YOUR DEVICES • Rename any device from its detail screen. Your name is used in every alert. MORE DEVICES • Miners whose AxeOS-compatible firmware uses the newer nested status API are now read correctly — hashrate, power, temperatures, fan, block hits and both pools — with reboot, pool switching and frequency/voltage changes. OFFLINE ALERTS YOU CAN TRUST • AxeSentry now knows which Wi-Fi your Bitaxes are on. Step out of the house and your phone stays quiet instead of reporting the whole swarm missing. • One missed check no longer means offline. Choose in Settings how many checks in a row must fail before you're alerted. • Your Bitaxes are polled in smaller groups, so a busy home network doesn't cause timeouts that look like outages. • While a device is being re-checked, the dashboard says so instead of marking it offline. ONE FORM FOR EVERY BITAXE • From the Controls tab, change the primary pool, fallback pool and wallet on all your Bitaxes in one go. • Current settings are filled in for you; leave a field blank to keep what each device already has. • Worker names stay per device, so your pool stats keep lining up. • Nothing restarts until you confirm. SELF-HEALING REBOOTS • Per device, reboot after a number of hours of runtime or at a set time of day. Missed one while the app was closed? It runs once at the next check-in, not once per missed day. • Or reboot when hashrate stays under a floor for as long as you choose. • Give up after a few tries or keep going until it recovers, with a notification each time. • Off until you turn it on. ALSO • Hashrate limits accept GH/s, TH/s or PH/s. • A glitching device can no longer inflate your swarm hashrate — impossible readings from the firmware are ignored.