AROYA · Pre-WP5 Firmware Update Readiness

Zugatti: 14th Street · Facility 2704

Generated 2026-06-02 04:08 UTC · 161 physical devices (301 raw rows incl. folded sensors) · 30-day window, sampled at 4 points

Will receive WP5

Should receive WP5

At risk — bring up first

Likely to miss the push

Offline — stays on WP4

Not assessable

Will receive WP5 online & healthyShould receive WP5 minor watch At risk bring up firstLikely to miss bring up / retire Offline — stays on WP4 not brickedNot assessable gateways

Mesh backbone: 90 units are online and communicating, so the gateway can push WP5 to them at the scheduled update. The gateway updates to WP5 and pushes it to every device online at that moment; devices that are offline simply stay on WP4 (unchanged — not harmed). Verify the sinks/gateways in the AROYA app first.

Fleet composition & sensor coverage

Your fleet lists 20 radios as “repeaters”, but the serial prefix tells the real story: 6 are range-extenders only (H110…) and 14 are climate stations (H111…) — a repeater-class radio with an Atmos-14 attached. Of the 14 climate stations, 5 are fully healthy, 1 have the Atmos-14 offline while the radio is up (reseat/replace the sensor — the radio still takes firmware), and 8 are entirely dark. Across the 130 substrate nodes, 68 have a reporting TEROS-12, 12 are alive but the probe isn’t reporting (reseat the probe), 46 are dark with the node, and 4 have no probe paired.

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)

Ticked for upgrade quote

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

TEROS One: 0 single + 0 dual — save $0

Climate One: 0 × $479 — save $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 get 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.

Bring as many devices online as possible before the scheduled push. Work the "Offline" and "At risk / Likely to miss" lists — replace batteries and shore up signal so each meets online + battery ≥ 30% + signal ≥ 50%. Every device up at push time receives WP5; every device down stays on WP4.
Decide what to retire or trade in instead of recovering. For dead/legacy 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.
Confirm the gateways/sinks are online in the AROYA app. The gateway carries the push; verify the backbone before the scheduled update.
After the push, recover any stragglers. Devices that were offline can still be brought current later by reverting a 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: mixed firmware on one network long-term can cause connectivity issues.
Note: existing WP4 gear keeps working as-is; new AROYA equipment requires WP5, which is the reason to update.

By room

Dry Room	6	1 0 0 0 5 0
Flower 1	32	7 9 8 2 6 0
Flower 2	36	17 3 1 0 14 1
Flower 3	35	10 9 3 1 12 0
Flower 4	29	3 8 2 4 12 0
Unassigned	11	1 0 0 0 9 1
Veg	7	0 0 0 0 7 0
(infrastructure)	5	1 0 0 0 3 1

By device class

Substrate node (radio + TEROS-12)	130	30 29 14 7 50 0
Climate station (radio + Atmos-14)	14	6 0 0 0 8 0
Repeater (range extender)	6	3 0 0 0 3 0
Gateway (mesh → cloud)	3	0 0 0 0 0 3
Sink (mesh root)	3	1 0 0 0 2 0
Unpaired sensor	5	0 0 0 0 5 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 save in this browser; click Export to send the snapshot back for the next pull.

Upgrade-eligible only (TEROS-12 + Atmos-14) Hide resolved Connecting…

0ticked for upgrade TEROS One $0Climate One $0 Total quote $0 Save $0 vs MSRP Resolved 0

Device (operator sees)	Class	Readiness	Room	Sensor	Batt	RSSI	Gaps	Last (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/H32x/H34x = node, H111 = climate station, H110 = repeater, 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, 30-day window sampled at four 2-day windows; silent devices re-pulled on a clean recent window. Flags (telemetry proxy for the go/no-go): battery crit<3.0/warn<3.2 V; RSSI crit<-95/warn<-85 dBm; link crit<40/warn<60; travel crit>60/warn>30 s; last-seen >48 h = offline.