Generated 2026-06-05 01:58 UTC · 1 WP4 gateway (H2100002330) · 118 active devices on file · this report scored against a 25-device sample (page 1) — see Data Quality.
10
GREEN — Will receive WP5
0
YELLOW — Recoverable
6
RED — Offline / stays on WP4
1
GATEWAY — WP4 to flash
0
Retired — Upgrade pool
8
Legacy >90d dark — retire
GREEN online & healthy → ready for WP5YELLOW online but battery/signal marginal — shore up firstRED offline ≤90d — bring up, or stays on WP4 unharmedGATEWAY WP4 gateway scheduled for WP5 pushLEGACY dark >90d → retire-trade-in (TEROS One / Climate One) over recovery
Island-logistics note (ACK = Nantucket airport code): Nantucket is a 30-mile ferry / charter from the mainland, so an on-site visit is materially more expensive than a typical mainland push. Default to remote OTAP with grow-team verification in the AROYA app. Reserve a site visit only for the WP4 gateway swap if the swap-out option is chosen, or if a critical mass of online devices needs hands-on revival. Most LEGACY (>90 d dark) devices are better retired than ferried back.
Mesh backbone (from 25-device sample): 1 gateway (H2100002330), 0 sink, 9 repeaters (mixed range-extenders H110 / climate stations H111), 10 substrate nodes, 0 TEROS-12 probes, 5 ATMOS 14 sensors. Population scaled to 118 active devices on file. The gateway updates to WP5 and pushes the new firmware to every device online at the scheduled time. Devices that are offline at push time stay on WP4 — they are not harmed. Bring them online before the push to receive WP5; otherwise recover later via WP4 gateway revert, or retire / trade in.
1
Gateway
0
Sink
9
Repeater / climate radio
10
Substrate node
0
TEROS-12 probe
5
ATMOS 14
WP4 → WP5 OTAP — what happens at the scheduled push
AROYA pushes WP5 over the air from the gateway. No site visit is required by default — the gateway flashes itself and propagates to every device online at the scheduled minute. Remote is the default; a site visit is the exception.
Go / no-go per device: online at push time, battery ≥ 30 %, signal (RSSI) ≥ 5 (per AROYA mesh classification).
Offline devices stay on WP4 — they are not bricked or harmed. They keep running on WP4 firmware. To bring them onto WP5 later: (a) bring the device online before the next scheduled push, or (b) revert the gateway to WP4 temporarily and re-run the push.
Recovery is reversible: a gateway can be reverted to WP4 with no time limit — stragglers can always be picked up later. The constraint is WP4 ↔ WP5 compatibility, not damage.
Battery-class devices (substrate nodes + TEROS-12 probes) are the only ones on battery; everything else (gateway, sink, repeaters, atm14 climate stations) is PoE. PoE devices generally come back online automatically with cable / power restored.
Action plan — remote-first, island-aware
1
Open app.aroya.io · Facility 2817 · verify gateway H2100002330 + sink + repeaters are online. The 25-device sample shows the gateway online with active comms in the last minute — mesh backbone is alive.
2
Walk the remaining ~93 devices in app (this report only sampled page 1). Flag any battery < 30 % or signal < 5 for swap-or-leave. Long-offline (>90 d) devices are better retired than recovered, especially given ferry logistics.
3
Schedule the WP4 → WP5 push for facility 2817 remotely once in-app green count is confirmed. Mark devices for retire / trade-in (TEROS One Single $319, Climate One $479) using the checkboxes below; state syncs across every device that opens this report.
Device inventory — 25 of 118 active devices (page-1 sample)
This report shows the first 25 of 118 active devices at the facility — the remaining 93 could not be pulled because the opencli browser bridge failed mid-run under parallel-agent load (see Data Quality). The retired-pool view (TEROS-12 / Atmos-14 retired but host node retired-flag) also requires a fresh portal_api session. Use the checkboxes to mark a device for upgrade (TEROS-12 → TEROS One, Atmos-14 → Climate One). Dropdown records operator status. All edits sync across every device that opens this report via https://aroya-report-sync.ciansul.workers.dev/2817.
25devices on this page (sample) · 118 total active
Marked for upgrade: 0
Marked revived: 0
Marked scheduled: 0
Marked won't-fix: 0
Loading…
Serial
Model
Class
Room / Zone
Bucket
Online
Batt %
RSSI
Last (h)
FW
Upgrade?
Trade-in quote
Operator status
Trade-in pricing — fixed
TEROS One (substrate) Dual: MSRP $608 · $150 off → $458 · Single: MSRP $419 · $100 off → $319 Replaces a retired TEROS-12 whose host node is also retired.
Climate One (climate) MSRP $629 · $150 off → $479 Replaces an ATMOS 14 sensor; PoE.
Data quality & what's missing from this view
Only 25 of 118 active devices pulled: the opencli portal_api adapter served page 1 (25 devices, sequential pagination), then the Chrome browser bridge that opencli rides on disconnected under concurrent load from the parallel-agent swarm and did not recover within the session budget. The 93 unpulled devices are real — they appear in the /portal_api/devices/?facility_id=2817&retired=false pagination count (5 pages × 25). Re-pull pages 2–5 in a single quiet session and re-render before scheduling the push.
Retired-pool view not pulled: the retired TEROS-12 / ATMOS 14 inventory whose host puck node is also retired (the TEROS One / Climate One upgrade pool) lives at /portal_api/devices/?facility_id=2817&retired=true. Same browser-bridge failure mode; this is the gap that decides whether the retired-trade-in column shows 0 or 20+ candidates. Re-pull with a clean session.
Firmware version field empty for non-repeater devices in the sample: the version attribute on the 25 devices reads as null for atm14 sensors and as 1.2.1.0 for repeaters / nodes (the WP4-era firmware). Repeaters carry the firmware string; battery-class endpoints don't expose it on this endpoint shape.
Bucket thresholds (sample-derived): GREEN = online + (battery ≥ 30 % or PoE) + RSSI ≥ 5. YELLOW = online but battery < 30 % or RSSI < 4. RED = offline ≤ 90 d. LEGACY-RMA = offline > 90 d (i.e. last communication before 2026-03-07). LEGACY-RMA dominates the sample because ACK has many 2024-era atm14 / node devices that have not phoned home in 12–24 months.
Single token tenancy: repeat the pull with the customer-facing AROYA portal token before publishing externally — a different operator login may have authoritative access to additional devices or a different retired-flag view.
Email/relationship context: the email-context agent returned a cold-contact result for ACK Natural — no firmware-related correspondence on file in the Addium inbox. The customer has not been pre-briefed on the WP4 → WP5 push; coordinate with the org's primary contact (likely from the AROYA portal CRM tab) before scheduling.
WP4 → WP5 OTAP firmware update · sample of 25/118 active devices on facility 2817 (ACK Natural: Nantucket) · classification scored against AROYA mesh go/no-go (online, battery ≥ 30 %, RSSI ≥ 5) · state persisted via https://aroya-report-sync.ciansul.workers.dev/2817 · per-entry timestamped last-write-wins · localStorage offline cache · re-verify in app.aroya.io before scheduling.