AROYA · Pre-WP5 Firmware Update Readiness

Allure Cultivation: 109 Hildreth Street · Facility 2878

Generated 2026-06-05 01:50 UTC · 29 devices · Telemetry snapshot 2026-06-04 01:42 UTC
28
Will receive WP5
0
Recoverable (action needed)
0
Offline — stays on WP4
1
Gateway — carries the push
0
Retired — upgrade pool
0
Legacy / RMA
Will receive WP5 online & reporting at the snapshot Recoverable action needed before the push Offline — stays on WP4 not bricked Gateway WP4 carrier — pushes WP5 Retired upgrade pool Legacy / RMA beyond field-recovery
Mesh backbone: All 27 sensor radios are reporting through the gateway/sink at the snapshot. Gateway H2100002394 is currently on WP4 and will carry the WP4→WP5 update; it pushes WP5 to every device online at the scheduled time. Devices that are offline at that moment stay on WP4 (unharmed) and can be recovered later by reverting a gateway to WP4, bringing them online, re-running the push.
Inventory method: Device inventory was derived from AROYA per-zone telemetry recency (public-API; get_current_readings + get_room_stats) at 2026-06-04 01:42 UTC because portal_api/devices/ was not reachable in this session. Every zone with a live reading is counted as a healthy radio + folded sensor. Exact serials, firmware strings, battery voltage, RSSI, and the retired/upgrade pool require a follow-up pull from the operator's portal.aroya.io session before the scheduled push.

TEROS One & Climate One upgrade planner

Tick the "Upgrade?" box on any sensor — including working ones. TEROS-12 → TEROS One (choose Dual or Single per sensor); Atmos-14 → Climate One. The quote totals exactly from your picks. Pricing is fixed (below).
—
TEROS-12 sensors (→ TEROS One)
—
Atmos-14 sensors (→ Climate One)
0
Ticked for upgrade quote
$0
Total trade-in quote
TEROS One Dual $458 $608 MSRP · save $150
TEROS One Single $319 $419 MSRP · save $100
Climate One $479 $629 MSRP · save $150
$0
TEROS One: 0 single + 0 dual — save $0
$0
Climate One: 0 × $479 — save $0
$0
Total saving vs MSRP ($0) — time-limited

How the WP5 update works & how to prepare

The gateway updates to WP5 and pushes it to every device that is online and communicating at the scheduled time (the go/no-go is: online, battery ≥ 30%, signal ≥ 50%). Devices that are offline at that moment simply stay on WP4 — they are not bricked or harmed, they just don't receive the new firmware. The catch is compatibility, not damage: a WP4 device needs a WP4-matched gateway to keep communicating, so the goal is to have as many devices as possible online at the push. Campus updates are normally run remotely; keeping the fleet online is the site's responsibility.

  1. Bring as many devices online as possible before the scheduled push. Replace batteries and shore up signal on anything in the "Recoverable" or "Offline" buckets so each meets online + battery ≥ 30% + signal ≥ 50%. Every device up at push time receives WP5; every device down stays on WP4.
  2. Decide what to retire or trade in instead of recovering. For sensors you won't bring back, mark them for a TEROS One / Climate One upgrade in the planner above rather than spending effort reviving them.
  3. Confirm the gateway is online in the AROYA app. Gateway H2100002394 carries the push; verify the backbone before the scheduled update.
  4. After the push, recover any stragglers. Devices that were offline can still be brought current later by reverting the gateway to WP4, bringing them online, re-running, then returning the gateway to WP5 — there's no time limit. Keep the mixed WP4/WP5 window short, though.
  5. Note: existing WP4 gear keeps working as-is; new AROYA equipment requires WP5, which is the reason to update.

By room

Veg 1
11 0 0 0 0 0
Veg 2
55 0 0 0 0 0
Flower 1
33 0 0 0 0 0
Flower 2
88 0 0 0 0 0
Flower 3
77 0 0 0 0 0
Flower 4
22 0 0 0 0 0
Dry Room
11 0 0 0 0 0
(infrastructure)
21 0 0 1 0 0

By device class

Substrate node (radio + TEROS-12)
1818 0 0 0 0 0
Climate station (radio + Atmos-14)
88 0 0 0 0 0
Irrigation sensor (FloraFlex)
11 0 0 0 0 0
Gateway (mesh → cloud)
10 0 0 1 0 0
Sink (mesh root)
11 0 0 0 0 0

Every device — readiness, sensor, action & your status

Set "Your status" as you work the floor — revived items drop off the active list, and upgrade picks feed the planner above. Your changes sync across every device that opens this link via a shared store (with a local cache when offline). Click Export to send the snapshot back for the next pull.
Connecting…
0ticked for upgrade TEROS One $0Climate One $0 Total quote $0 Save $0 vs MSRP Resolved 0
Device (operator sees)ClassReadiness RoomSensor BattRSSILast (h) Most-likely failure / action Upgrade?Your status
One row per physical device. A TEROS-12 / Atmos-14 is folded into the radio it plugs into (sensor.puck). Class by serial prefix (the API hides a climate station as a "repeater" when its Atmos-14 is offline): H31x = node, H111 = climate station, H110 = repeater (range-extender only), H21x = gateway, SINK = sink. TEROS One upgrade applies to TEROS-12 substrate sensors; the planner totals trade-in cost from what you mark. Your status edits and upgrade picks sync across every device that opens this link (shared store), with a local cache when offline; Export gives a JSON snapshot the next data pull reconciles against. Readiness reflects the WP5 go/no-go — a device receives WP5 only if it's online with battery ≥ 30% and signal ≥ 50% at the scheduled push; otherwise it stays on WP4 (unharmed). Offline devices aren't bricked — the constraint is WP4↔WP5 compatibility, not damage; stragglers can be recovered later via a WP4 gateway revert. Telemetry: AROYA public-API get_current_readings + get_room_stats at 2026-06-04 01:42 UTC.