by Addium Wirepas mesh & device health · WellBred Cannabis · 2026-07-09Wirepas malla y salud de dispositivos · WellBred Cannabis · 2026-07-09
WellBred Cannabis · Wirepas Mesh & Device HealthWellBred Cannabis · Malla Wirepas y Salud de Dispositivos
Live SPA snapshot of every AROYA device at the facility — real mesh parent linkages (via nextHop), child-slot saturation against the Wirepas 13-child rule, RSSI / link quality / battery health, and a prioritized remediation plan.Snapshot en vivo del SPA de cada dispositivo AROYA — enlaces reales de padre-hijo (via nextHop), saturación contra la regla Wirepas de 13 hijos, RSSI / link quality / batería, y plan priorizado de remediación.
Wirepas 13-child slot limit is breached on 4 parent(s) at this facility. The worst-loaded parent is H1110005920 (repeater) in Flower 2 carrying 18 children — 5 over the 13-slot limit. Total excess load across all over-subscribed parents: 12 children. Each over-13 child contends for a slot that doesn't exist — devices either get pushed to a worse parent (extra hops, weaker signal) or fail to keep their slot, producing the data-gap pattern operators see.
Beyond the 4 over-13 parent(s), 2 more are in the 11–13 watch tier. These parents are most at risk of crossing the line next.
1 device flagged critical (H8100001475 · h421 puck reporting battery 0%). All other health flags are quiet — the failure mode at WellBred is topology saturation, not device attrition.
El límite Wirepas de 13 hijos está violado en 4 padre(s) en esta instalación. El padre más cargado es H1110005920 (repeater) en Flower 2 con 18 hijos — 5 sobre el límite. Total de exceso: 12 hijos. Cada hijo por encima de 13 compite por un slot que no existe — los dispositivos son empujados a un peor padre (más hops, señal más débil) o pierden su slot.
Más allá de los 4 padres sobre-13, hay 2 en la zona de observación 11–13. Son los próximos en cruzar la línea.
Flota total: 108 radios de malla (94 nodos, 8 repetidores, 3 gateways, 3 sinks). 70.4% en línea. 32 dispositivo(s) fuera de línea.
1 dispositivo crítico (H8100001475 · puck h421 con batería 0%). El resto de flags están tranquilos — el modo de falla en WellBred es saturación de topología, no desgaste de dispositivos.
13-child slot ruleLa regla de los 13 hijoswhy this is the load-bearing metricpor qué es la métrica más importante
Each parent node in the Wirepas mesh — gateway, sink, or repeater — supports at most 13 DIRECT children. Grandchildren count against their immediate parent's slots, NOT against the grandparent's. Mid-layer relays can be saturated even when the gateway above them has plenty of headroom — so saturation has to be checked at every level of the topology, not just gateway-level.Cada padre en la malla Wirepas — gateway, sink o repeater — soporta como máximo 13 hijos DIRECTOS. Los nietos cuentan contra los slots de su padre inmediato, NO contra el abuelo. Los repetidores intermedios pueden estar saturados aunque el gateway tenga espacio — la saturación debe revisarse en todos los niveles.
Once a parent crosses 13, additional devices either fail to join, get pushed to a worse parent at higher hop count, or thrash between slots — producing the long travel times, retries, and growing data gaps operators see.Cuando un padre cruza 13, los dispositivos adicionales no logran unirse, son empujados a un peor padre con más hops, o rebotan entre slots — produciendo travel-times largos, reintentos, y los vacíos de datos crecientes.
Mesh topology treeÁrbol de topología de mallareal parent-child edges from SPA nextHoppadre-hijo real desde nextHop del SPA
Each column is a gateway. Rows underneath are ALL descendants — hop-1 direct children, then their children indented, and so on. Dot color = the parent's own child-slot saturation. Offline devices marked ⚫.Cada columna es un gateway. Las filas debajo son TODOS los descendientes — hijos hop-1 directos, luego sus hijos con sangría, etc. Color del punto = saturación de slots del padre. Offline marcado ⚫.
Saturated parents detailDetalle de padres saturados
ParentPadre
ModelModelo
RoomSala
ChildrenHijos
OverSobre
StatusEstado
H1110005920
repeater
Flower 2
18
+5
OVER
SINKH2100002550
sink
—
16
+3
OVER
H1110005880
repeater
Flower 1
15
+2
OVER
H1110005752
repeater
Flower 3
15
+2
OVER
H1110005896
repeater
Veg and Clone
13
—
AT LIMIT
H1110005887
repeater
Flower 4
13
—
AT LIMIT
Weakest 20 links20 enlaces más débiles
Serial
Model
Room
RSSI
LinkQ
Bat %
Flag
Reasons
H3210010118
node
Dry Room 1
8
—
0
⚫ offline
not online
H3210010071
node
Dry Room 2
2
—
0
⚫ offline
not online
H3210010135
node
Dry Room 2
8
—
0
⚫ offline
not online
H3210010083
node
Dry Room 2
7
—
0
⚫ offline
not online
H3210010096
node
Dry Room 2
8
—
1
⚫ offline
not online
H3210010116
node
Flower 1
8
—
3
⚫ offline
not online
H1110005888
repeater
—
8
—
4
⚫ offline
not online
H3210010110
node
Flower 3
1
—
25
⚫ offline
not online
H3210018113
node
Flower 1
4
—
89
⚫ offline
not online
H3210010055
node
Flower 1
7
—
80
⚫ offline
not online
H3210009991
node
Flower 1
7
—
100
⚫ offline
not online
H3210018031
node
Flower 1
1
—
80
⚫ offline
not online
H3210010064
node
Flower 1
1
—
95
⚫ offline
not online
H3210010042
node
Flower 1
1
—
100
⚫ offline
not online
H3210009975
node
Flower 2
3
—
86
⚫ offline
not online
H3210010049
node
Flower 3
5
—
100
⚫ offline
not online
H3210010120
node
Flower 3
8
—
100
⚫ offline
not online
H3210010080
node
Flower 3
2
—
100
⚫ offline
not online
H3210009999
node
Flower 3
5
—
100
⚫ offline
not online
H3210010040
node
Flower 3
4
—
91
⚫ offline
not online
Battery lifecycle — 15 next to replaceCiclo de vida — próximas 15 baterías
Serial
Model
Room
Bat %
Est. months to replaceMeses est.
H3210010026
node
Flower 4
0%
< 30 days
H3210010118
node
Dry Room 1
0%
< 30 days
H3210010071
node
Dry Room 2
0%
< 30 days
H3210010135
node
Dry Room 2
0%
< 30 days
H3210010083
node
Dry Room 2
0%
< 30 days
H3210010096
node
Dry Room 2
1%
< 30 days
H3210010116
node
Flower 1
3%
< 30 days
H1110005888
repeater
—
4%
< 30 days
H3210010110
node
Flower 3
25%
1–3 months
H3210018107
node
Flower 2
35%
1–3 months
H3210010074
node
Flower 2
48%
3–6 months
H3210010108
node
—
50%
3–6 months
H3210010125
node
Dry Room 2
53%
3–6 months
H3210010106
node
Dry Room 2
54%
3–6 months
H3210010045
node
Dry Room 2
55%
3–6 months
Prescriptive remediationRemediación prescriptiva
P0Rebalance saturated parents in Flower rooms
4 parent(s) are over the 13-child limit — worst is H1110005920 at 18/13. Excess load is 12 children across the fleet. This is the ROOT CAUSE of data gaps at WellBred.
Recommendation
Contact AROYA support to trigger a Wirepas re-provisioning cycle. If a repeater is the saturated parent, physically move it to relieve subtree pressure, or add a second repeater in the same room to split hop-1 load.
P0Bring 32 offline devices back online
32 radios (29.6%) show online=false in the SPA snapshot. Some are historical (retired) — most are genuine dropouts. Every offline sensor is a blind spot for the irrigation team.
Recommendation
Walk each offline device with an installer: check LED, power (PoE / battery), and mesh join status. Compare against Rachel's WP4 firmware sheet before assuming physical fault.
P1Add sink or 2nd gateway in Flower 2
Repeater H1110005920 in Flower 2 is at 18/13 — the worst violator on-site. A repeater is not designed to carry 18 hop-1 children.
Recommendation
Options: (1) add a dedicated sink adjacent to Flower 2 to absorb hop-1 traffic; (2) install a second repeater at the far end of Flower 2 to halve the subtree; (3) if a gateway is available, relocate it into Flower 2's LAN drop.
P1Investigate H2110001497 gateway (offline)
One of your 3 gateways (H2110001497, id 223027) shows online=false. That's a single-point-of-failure for whatever subtree was rooted there. Every device that was routing through it has to find a new parent — probably explaining part of the saturation.
Recommendation
Verify the gateway's Ethernet + power at its physical location. If dead, hot-swap replacement scheduled. Note: this gateway may already be documented as offline in your ops log — cross-reference before rolling a truck.
P1Replace H8100001475 (battery 0%, only P0 device)
One device in the fleet reports battery=0% — an h421 puck. It is still online but is producing no useful battery telemetry. Almost certainly a battery-ADC fault, not literal 0V.
Recommendation
Include in next site visit swap batch. This is the only true P0 device-level failure on the site — every other 'red' flag on WellBred is topology, not hardware.
P2Second-pass 14-day pull for public-API health metrics
The SPA snapshot gives us a point-in-time mesh view. The 14-day public-API pull hit HTTP 429 on 111 of 200 devices — that longitudinal data is still valuable for battery-drift and gap-trend analysis, once we back off concurrency.
Recommendation
Re-run the 14-day pull with ≤6 workers off-peak. Target ≥95% device coverage. Merge with this SPA snapshot for a longitudinal + point-in-time joint view.
P3Firmware version audit
SPA ggVersion is exposed on some radios (mostly null on this facility). Cross-check against Rachel's WP4 firmware sheet at next site visit — this facility likely has a mix of WP4 and WP5 gateways given its ID range.
Recommendation
Add firmware column to next site-visit checklist. Any WP4 gateway is a candidate for upgrade to WP5 (auto-WP5 models: H34x, H810, H421, H412 — none of Wellbred's gateway serials match, so all 3 are WP4).
Prioritized action planPlan de acción priorizado
01Rebalance Flower 2 mesh (H1110005920 at 18/13)Same-day · P0