AROYA · WP5 Firmware Status & Device Connectivity

Nascent Verdure · Facility 3766

Generated 2026-06-16 19:19 UTC · 70 physical devices (131 raw rows incl. folded sensors) · live AROYA app status snapshot

On WP5 · online & healthy

On WP5 · online (watch)

On WP5 · at-risk (signal/battery)

On WP5 · critical

Offline (connectivity)

Verify in app

On WP5 · healthy onlineOn WP5 · watch minor At-risk battery/signalCritical Offline connectivityVerify in app

✓ Already on WP5 — no WP4→WP5 push applies here. Every device class in this fleet ships auto-provisioned on WP5 — H34x nodes, H421 Climate One stations, H130 repeaters, sinks (plus H810/H412 models) — and the gateways confirm WP5 (ggVersion=2). All 70 of 70 physical devices are on WP5. The buckets below are live connectivity health, not firmware push-readiness.

Connectivity backbone: 53 of 70 physical devices are online and communicating now; 17 are offline or absent from the live device view. Firmware is settled (WP5) — the items to work are connectivity (battery, mesh signal, coverage), not a firmware push. Confirm gateways/sinks stay online in the AROYA app.

Fleet composition & sensor coverage

Nascent Verdure is a current-generation AROYA install: 44 substrate nodes (H34x radio + ter15 TEROS One-class probe), 17 Climate One stations (h421 + ee894 CO₂/climate), 3 repeaters, 3 gateways, 3 sinks (one row per physical radio; sensors folded into their host). Of 44 nodes, 43 have a reporting probe, 0 are alive but the probe isn't reporting, 1 are dark with the node. Of 17 Climate One stations, 7 fully report, 8 have the CO₂/climate sensor offline while the radio is up, 2 are dark.

Device upgrade capability

Upgrade capability assessment. This fleet is on current-generation AROYA hardware — Climate One stations (h421) and TEROS One-class substrate probes (ter15). The TEROS One / Climate One trade-in programs upgrade legacy TEROS-12 / Atmos-14 fleets, of which Nascent Verdure has none (0 eligible), so the planner correctly reads $0. There is no sensor upgrade to make here.

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 × $419 — save $0

Total saving vs MSRP ($0) — time-limited

Firmware status — already on WP5

Nascent Verdure is fully on WP5. Its 44 nodes (H34x), 17 Climate One stations (H421), 3 repeaters (H130) and 3 sinks all ship provisioned on WP5 automatically, and its 3 gateways report WP5 (ggVersion=2) — all 70 of 70 devices. There is no WP4→WP5 update to schedule for this facility — this report confirms firmware status and surfaces live connectivity health and (zero) upgrade capability.

No WP4→WP5 migration is required for the node + Climate One fleet. H34x nodes and H421 stations ship on WP5 automatically — there is no firmware push to schedule for them.
Gateways are confirmed on WP5 (ggVersion = 2); sinks ship on WP5 too. Keep gateways/sinks online in the AROYA app — the sinks aren’t in the live device view, so their live connectivity is unconfirmed here.
The actionable layer is connectivity, not firmware. Work the Offline / At-risk lists below to restore coverage; those are battery/signal/connectivity items and the devices stay on WP5 throughout.

By room

Alhambra Room 2B	6	1 3 2 0 0 0
Alhambra Dry Room	1	1 0 0 0 0 0
Alhambra Room 1	9	5 2 1 0 1 0
Alhambra Room 1 Top	6	3 1 2 0 0 0
Alhambra Room 2	8	5 2 0 0 0 1
Alhambra Room 3	13	5 1 1 0 1 5
Nursery Babies	8	3 2 3 0 0 0
Nursery Moms	5	3 1 1 0 0 0
(infrastructure)	14	1 0 2 0 3 8

By device class

Substrate node (radio + TEROS One-class probe)	44	20 11 12 0 1 0
Climate One station (radio + CO₂/climate)	17	6 1 0 0 2 8
Repeater (range extender)	3	1 0 0 0 2 0
Gateway (mesh → cloud)	3	0 0 0 0 0 3
Sink (mesh root)	3	0 0 0 0 0 3

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): H343… = node (battery radio + ter15 substrate), H421… = Climate One station (radio + ee894 CO₂/climate), H130… = repeater, H210… = gateway, SINK… = sink. Firmware: H34x/H421/H130/H810/H412 + sinks auto-provision on WP5. 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. Buckets reflect live connectivity health (online · battery · signal). Firmware is by hardware model: H34x / H421 / H130 / H810 / H412 and sinks are auto-provisioned on WP5, and gateways confirm WP5 via ggVersion=2 — this fleet needs no WP4→WP5 push. Source: live AROYA app device API status snapshot (online · battery %% · signal · linkQuality · ggVersion). Flags (telemetry proxy for the go/no-go): connectivity flags: node battery < 30%% or mesh signal < ~50%% (rssi < 4 of 8) = at-risk; offline / last-seen > 48 h = connectivity issue (firmware stays WP5).