Generated 2026-06-05 01:33:24 UTC · 59 devices on file · 1 WP4 gateway (H2100002136)
0
GREEN — Will receive WP5
0
YELLOW — Recoverable
0
RED — Offline / stays on WP4
1
GATEWAY — WP4 to flash
0
Retired — Upgrade pool
0
Legacy — RMA
GREEN online & healthy → ready for WP5YELLOW bring up first (battery/signal) before pushRED offline — stays on WP4 unharmed; recover later or trade inGATEWAY WP4 gateway scheduled for WP5 pushRETIRED retired TEROS-12 / Atmos-14 → TEROS One / Climate One trade-in
Important — Facility status: All 59 devices in this inventory currently return no telemetry via the AROYA public_api chart endpoint across every window tested from June 2025 through June 2026. The 10 configured rooms (Veg, Flower 1, Dry Room, MGF Rooms A–I) all read null on temp / VWC / VPD over the last 24 h. This facility appears dormant on this token's view. All 58 non-gateway devices are flagged Pending verify in app — the live battery / signal / lastComm read must be pulled inside app.aroya.io before scheduling the WP4 → WP5 push. The retired-upgrade pool view (TEROS-12 / Atmos-14 retired but host node retired flag) needs portal_api access not available from this run.
Mesh backbone: 1 gateway (H2100002136), 1 sink, 4 repeaters, 25 substrate nodes, 25 TEROS-12 probes, 3 Atmos-14 sensors. 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.
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.
Go / no-go per device: online at push time, battery ≥ 30 %, signal (RSSI) ≥ 50 %.
Offline devices stay on WP4 — they are not bricked. They keep running on WP4 firmware. To bring them onto WP5 later, either (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, so stragglers can always be picked up later.
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
1
Open app.aroya.io · Facility 2553 · verify gateway H2100002136 + sink + 4 repeaters are online. Without the mesh backbone alive the push will not propagate.
2
Walk the 25 substrate nodes + 25 TEROS-12 probes in app — confirm each shows recent lastComm, battery ≥ 30 %, signal ≥ 50 %. Anything red gets one of: bring online, swap battery, replace, or accept it stays on WP4.
3
Schedule the WP4 → WP5 push for facility 2553 once the in-app verification confirms green-readiness counts. Mark devices to retire / trade in here using the checkboxes below; the state syncs across every device that opens this report.
Device inventory (59 devices)
Use the checkboxes to mark a device for upgrade (TEROS-12 → TEROS One, Atmos-14 → Climate One). The dropdown next to each row records the operator status (revived, scheduled, won't fix). All edits sync across devices via https://aroya-report-sync.ciansul.workers.dev/2553.
59devices on file
Marked for upgrade: 0
Marked revived: 0
Marked scheduled: 0
Marked won't-fix: 0
Loading…
Serial
Model
Class
Room
Bucket
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 (single sensor) Replaces an Atmos-14 sensor; PoE.
Data quality & what's missing from this view
portal_api retired-pool view not pulled: the retired-TEROS-12 / Atmos-14 inventory (with host-node retired-flag) lives in /portal_api/devices/?facility_id=2553&retired=true, which requires the portal.aroya.io browser-session token (not available in this run). The upgrade-pool figure should be re-pulled with opencli before the customer call.
Per-device firmware / battery / RSSI / lastComm not pulled: the public_api /devices/{id}/chart/ endpoint returned empty across every test window (June 2025 → June 2026). Per-device telemetry must come from the AROYA app or from /portal_api/devices/?facility_id=2553.
Room assignments incomplete: only 2 of 59 devices are assigned to a room (both in Veg); the other 57 are unassigned in this token's view. This is the strongest signal that the facility is partially or fully dormant.
Single token may have limited tenancy view: if a different operator token has authoritative access, repeat the inventory pull with that token before scheduling the push.
WP4 → WP5 OTAP firmware update. State persisted via https://aroya-report-sync.ciansul.workers.dev/2553 · per-entry timestamped last-write-wins · localStorage offline cache · this report was generated against the AROYA public_api token and should be re-verified inside app.aroya.io before scheduling.