Dark
AROYA · Pre-WP5 Firmware Update Readiness · Device & Mesh AuditAROYA · Preparación para la actualización WP5 · Auditoría de dispositivos y malla

Goldkine 14401 Frazho · Facility 3108

Every device bucketed for the scheduled WP4 → WP5 over-the-air push — who receives WP5, who needs bring-up first, who stays on WP4 (not harmed), plus the TEROS One / Climate One trade-in plan. This facility runs a mixed gateway generation: the WP4 “hybrid” gateways were never updated and still report ggVersion 1.Cada dispositivo clasificado para la actualización WP4 → WP5 por aire — cuáles recibirán WP5, cuáles hay que reactivar antes, cuáles quedan en WP4 (sin daño), más el plan de canje TEROS One / Climate One. Esta instalación tiene generación de gateways mixta: los gateways “híbridos” WP4 nunca se actualizaron.
FacilityGoldkine 14401 Frazho (ID 3108) State / location14401 Frazho · state not in device snapshot Report date2026-07-14 Telemetry window2026-07-14 live SPA snapshot · no 24 h percentile window Gateways5 on record · 2 online (H2100002546 WP4-hybrid, H2100002581 WP5) · 2×WP4, 3×WP5 Devices406 physical · sensors folded into host rows WP4 cohort2 gateway(s) on WP4 (ggVer 1) — hybrids never updated; 3 on WP5 (ggVer 2). No WP4-sheet snapshot on record. Trade-in pool0 FREE TEROS One Single · 44 paid Climate One candidates
296
Will receive WP5Recibirá WP5
1
Should receive WP5Debería recibir WP5
43
At risk — bring up firstEn riesgo — reactivar antes
0
Likely to miss the pushProbablemente no la reciba
60
Offline — stays on WP4Fuera de línea — queda en WP4
6
Not assessableNo evaluable
406
physical devicesdispositivos físicos
297
WP5-readylistos para WP5
43
bring up firstreactivar primero
60
offline — stay on WP4fuera de línea — quedan en WP4
0
FREE TEROS One trade-incanje TEROS One GRATIS
44
paid Climate One upgrades avail.mejoras Climate One disponibles
Will receive WP5 online & healthyShould receive WP5 minor watch At risk bring up firstLikely to miss bring up / retire Offline — stays on WP4 not harmedNot assessable gateways / non-mesh

Readiness at a glancePreparación de un vistazo

Readiness by roomPreparación por sala

Fleet compositionComposición de la flota

Mesh backbone:Red troncal: 299 of 406 devices are online and communicating, so an online 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 offline simply stay on WP4 (unchanged — not harmed). This facility has 5 gateways on record across mixed generations: 2 report ggVersion 1 (WP4 hybrids, never updated) and 3 report ggVersion 2 (WP5). Online now: H2100002546 (WP4-hybrid), H2100002581 (WP5). Silent gateways: H2100002545 (ggVer 1) silent since 2023-12-14; H2100005066 (ggVer 2) silent since 2024-05-02; H2100005073 (ggVer 2) silent since 2024-05-02 — confirm in the AROYA app whether they are decommissioned before the push. The push is run remotely by AROYA; a site visit is the exception, not the default.

Fleet composition & sensor coverageComposición de flota y cobertura de sensores

Your fleet lists 400 mesh radios. By serial prefix and model: 337 substrate nodes (H3210, TEROS-12 host), 44 climate stations (H1110, a repeater-class radio with an Atmos-14 attached), and 19 range-extender / IO repeaters (H1100). There are also 5 gateways (H2100) and 1 AquaLab bench station (AQ-series, not part of the mesh push). Across the 337 substrate nodes, 244 have a reporting attached sensor, 88 are offline with the sensor, and 5 have no sensor paired. Attached sensors ride on their host radio for the WP5 push.Su flota tiene 400 radios de malla: 337 nodos de sustrato (H3210, TEROS-12), 44 estaciones climáticas (H1110, Atmos-14) y 19 repetidores (H1100). Además 5 gateways (H2100) y 1 estación AquaLab. De los 337 nodos, 244 tienen sensor reportando. Los sensores acompañan a su radio en la actualización WP5.

FREE TEROS One trade-in pool (retired hosts)Canje TEROS One GRATIS (anfitriones retirados)

Cross-referenced against the retired-device register (retired=true in this snapshot): the FREE 1:1 TEROS One Single replacement covers retired TEROS-12 hosts (H3210) that are off-air > 30 days with the sensor removed or de-paired. 0 devices qualify in this facility — no device in the snapshot is flagged retired. This is a customer-choice program; nothing needs to happen for the WP5 push.Comparado con el registro de dispositivos retirados (retired=true): el reemplazo TEROS One Single GRATIS 1:1 cubre anfitriones TEROS-12 (H3210) retirados y sin sensor. 0 dispositivos califican — ninguno figura como retirado en esta captura.

TEROS One & Climate One upgrade plannerPlanificador de mejoras TEROS One y Climate One

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).Marque “Mejora?” en cualquier sensor. TEROS-12 → TEROS One; Atmos-14 → Climate One. La cotización se calcula de sus selecciones. Precios fijos (abajo).
—
TEROS-12 sensors (→ TEROS One)
—
Atmos-14 sensors (→ Climate One)
0
Ticked for upgrade quote
$0
Total trade-in quote
TEROS One Dual $458 with trade-in · $608 new
TEROS One Single $319 with trade-in · $419 new
Climate One $479 with trade-in · $629 new
$0
TEROS One: 0 single + 0 dual — save $0
$0
Climate One: 0 × $479 — save $0
$0
Total saving vs new price ($0)

How the WP5 update works & how to prepareCómo funciona la actualización WP5 y cómo prepararse

The gateway updates to WP5 and pushes it to every device online and communicating at the scheduled time (go/no-go: online, battery ≥ 30%, healthy signal). Devices offline at that moment simply stay on WP4 — they are not 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 online at the push as possible. Because this facility runs a mixed generation, the WP4 hybrid gateways can be updated (or kept as-is during a transition) — keep the mixed WP4/WP5 window short. The update is run remotely by AROYA.El gateway se actualiza a WP5 y lo envía a cada dispositivo en línea en el momento programado. Los que estén fuera de línea quedan en WP4 — sin daño. El tema es compatibilidad, no daño. Esta instalación tiene generación mixta; mantenga corta la ventana WP4/WP5. AROYA ejecuta la actualización de forma remota.

  1. P0Bring as many devices online as possible before the push. Work the “At risk” and “Offline” lists — restore power and mesh coverage so each meets online + battery ≥ 30%. Every device up at push time receives WP5; every device down stays on WP4.
  2. P1Decide the hybrid-gateway plan. The 2 WP4 hybrid gateway(s) still report ggVersion 1 — confirm with AROYA whether they migrate to WP5 in this push or stay during a transition, and keep any mixed window short.
  3. P2Decide what to trade in instead of recovering. For legacy sensors you won’t bring back, mark them for a TEROS One / Climate One upgrade in the planner above.
  4. P3Confirm the gateways are online in the AROYA app. Verify the backbone (especially any silent gateways) before the scheduled update.
  5. After the push, recover any stragglers. Offline devices can 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.
  6. Note: existing WP4 gear keeps working as-is; new AROYA equipment requires WP5, which is the reason to update.

By roomPor sala

CLONE ROOM
10 0 0 0 1 0
DRY ROOM 01
33 0 0 0 0 0
DRY ROOM 02
22 0 0 0 0 0
DRY ROOM 03
32 0 0 0 1 0
FLOWER ROOM 01
2621 0 2 0 3 0
FLOWER ROOM 02
2521 0 2 0 1 1
FLOWER ROOM 03
2016 1 1 0 2 0
FLOWER ROOM 04
2724 0 3 0 0 0
FLOWER ROOM 05
86 0 0 0 2 0
FLOWER ROOM 06
2217 0 0 0 5 0
FLOWER ROOM 07
2420 0 0 0 3 1
FLOWER ROOM 08
2424 0 0 0 0 0
FLOWER ROOM 09
2624 0 0 0 2 0
FLOWER ROOM 10
2524 0 0 0 1 0
FLOWER ROOM 11
2423 0 0 0 1 0
FLOWER ROOM 12
2525 0 0 0 0 0
FLOWER ROOM 13
2320 0 0 0 3 0
FLOWER ROOM 14
1413 0 0 0 1 0
MOTHER ROOM
21 0 0 0 1 0
SECURITY ROOM
210 0 0 0 21 0
TRIM ROOM
22 0 0 0 0 0
VEG ROOM 01
42 0 0 0 2 0
VEG ROOM 02
21 0 0 0 1 0
(unassigned)
535 0 35 0 9 4

By device classPor clase de dispositivo

Substrate node (radio + TEROS-12)
337249 1 41 0 46 0
Climate station (radio + Atmos-14)
4435 0 1 0 8 0
Repeater (range extender)
1912 0 1 0 6 0
Gateway (mesh → cloud)
50 0 0 0 0 5
AquaLab station
10 0 0 0 0 1

Every device — readiness, sensor, action & your statusCada dispositivo — preparación, sensor, acción y su estado

Set “Your status” as you work the floor — revived items drop off the active list, and upgrade picks feed the planner above. Your marks sync live across every phone/computer that opens this link. Click Export for a JSON snapshot backup.Marque “Su estado” mientras trabaja. Sus marcas se sincronizan entre dispositivos.
Connecting…
0ticked for upgrade TEROS One $0Climate One $0 Total quote $0 Save $0 vs new price Resolved 0
Device (operator sees)ClassReadiness RoomSensor Batt %SignalGaps Last (h)Most-likely status / action Upgrade?Your status
Method & scope. One row per physical device; an attached sensor (TEROS-12, Atmos-14, ES-2) is folded into the radio it plugs into, and sensor-head serials are masked — locate hardware on the floor by the H-prefix radio serial only. Class by model + serial prefix (H3210 = substrate node, H1110 = climate station, H1100 = repeater, H2100 = gateway, AQ = AquaLab bench). Readiness reflects the WP5 go/no-go — a device receives WP5 only if it’s online with adequate battery/signal at the scheduled push; otherwise it stays on WP4 (unharmed) and can be recovered later via a WP4 gateway revert. These are live-snapshot values pulled 2026-07-14 from the SPA /devices/?facility=3108 endpoint — online flag, battery %, signal index (0–8), and last-communication timestamp. They are NOT 24 h telemetry percentiles. Fields the live snapshot does not carry (link quality, travel time, 60-min gap counts) are shown as blank rather than estimated. ggVersion is the authoritative banner source (admin-tier gated on the SPA; portal_api returns null). Priorities: P0 = act before the push, P1 = shore up, P2 = plan/trade-in, P3 = verify only. Cultivation metrics are covered in this facility’s cultivation audits, not here.
Cian Sullivan · Addium · Customer Success — AROYAÉxito del Cliente — AROYA
Report generated 2026-07-14 · AROYA brand styled · Goldkine 14401 Frazho (facility 3108) · live SPA snapshot pulled 2026-07-14Informe generado 2026-07-14 · estilo de marca AROYA · Goldkine 14401 Frazho (instalación 3108)
Operator checkmarks & upgrade picks sync across devices via aroya-report-sync (per-entry last-write-wins; localStorage offline cache; Export/Import backup). · app.aroya.io