by Addium
Wirepas mesh & device health · POWRHOUSE · 2026-06-24
POWRHOUSE · Wirepas Mesh & Device Health
Live snapshot of every AROYA device at the facility — mesh parent linkages, child-slot saturation against the Wirepas 13-child rule, RSSI / link quality / battery health, and a prioritized remediation plan.
Wirepas 13-child slot limit is still breached on 4 parents at this facility. The worst-loaded parent is the H2100004676 sink carrying 16 children — 3 over the 13-slot limit (down from 17/+4 this morning). Total excess load across all over-subscribed parents: 6 children (down from 8). 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 parents, 1 more is in the 11–12 watch tier (H4210003243, 11 children, unchanged) — that parent is most at risk of crossing the line next.
Mesh is slightly more relaxed than this morning: 2 fewer excess children, and gateway H2200001033 has absorbed routing load (route_total 24 → 34, all online) that was previously sitting on H2100004676 and H2100005246 — the rebalance is doing its job.
13-child slot rule why this is the load-bearing metric
Each parent node in the Wirepas mesh — gateway or relay — 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.
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.
Dash-2 dedup: two AROYA serials sharing the same base number where one has a
-2 suffix (e.g. H4210005066 and H4210005066-2) are ONE
radio with two sensor heads, not two mesh nodes. They fill one slot on their parent.
This report deduplicates by base serial before counting — counts are per unique radio,
not per raw serial.
Counts are per-immediate-parent: n_children(P) = unique base serials whose nextHop == P.
🟢 ≤10 children headroom · 🟠 11–12 near saturation · 🔴 13 at limit ·
🔴🔴 >13 over-subscribed (orphaned devices & multi-hop spillover).
Changes since morning snapshot 2026-06-24 14:33:27 → 12:57:23 PDT
Headline: Mesh is slightly more relaxed. Same 4 gateway sinks still over the 13-child line, but the worst-loaded sink (H2100004676) shed 1 child (17 → 16) and the H2200001033 sink shed 1 (15 → 14). Total excess slots: 8 → 6. Gateway H2200001033 has absorbed routing load that was previously on H2100004676 and H2100005246 — the routing rebalance is doing its job. No new gateways, no recovered offline devices, no new saturation tier crossings.
Worst-loaded sink relieved: H2100004676 sink 17/13 (+4) → 16/13 (+3). One child re-routed away. Gateway tree total fell 29 → 26 devices (22 of 26 online vs 25 of 29 this morning — 3 of the 3 dropped were online devices that moved off the tree, not new offlines).
Second-worst sink relieved: H2200001033 sink 15/13 (+2) → 14/13 (+1). Same gateway, however, absorbed 10 more total downstream nodes (route_total 24 → 34, all online) — a hop-2/3 re-parenting from the other two trees. Net effect: this gateway is now carrying a larger but flatter sub-tree.
Other two sinks unchanged at 14/13 (+1): H2100005242 and H2100005246. H2100005246's tree shrank slightly (59 → 53 total routing, 52 of 53 online vs 59 of 59) — its previously fully-online tree now has 1 dropout and lost ~6 hop-2+ leaves to H2200001033.
Watch tier identical: H4210003243 still at 11/13. All 11 of its children online.
One new radio appeared (152 → 153 unique radios). Same 146 online, so headline online-rate drifted 96.1% → 95.4% — purely a denominator effect, not a real degradation. The same 6 radios that were offline this morning remain offline (H3310009633, H3440005758, H4210002601, H4210002602, H4210002607, H4210002620, H8100001475 — 7th is the persistent H8100001475 zero-battery puck). No recovered devices.
Mesh health KPIs
153
Unique radios
274 raw serials, −121 dash-2 pairs (+1 vs am)
146
Online
95.4% of radios (was 96.1%, denominator drift)
4/4
Gateways
online (unchanged)
4
Parents over 13
Wirepas 13-child limit (unchanged)
1
Parents 11–12
watch tier (unchanged)
6
Excess children
over 13-slot budget (was 8, −2)
Per-gateway summary
H2100004676
id 124662 · ggVersion 2 · online
🔴🔴 16/13 · Over-subscribed (+3, was +4)
16 hop-1 children
26 total routing
22/26 online
(no children resolved)
H2100005242
id 152540 · ggVersion 2 · online
🔴🔴 14/13 · Over-subscribed (+1)
14 hop-1 children
36 total routing
34/36 online
(no children resolved)
H2100005246
id 152550 · ggVersion 2 · online
🔴🔴 14/13 · Over-subscribed (+1, unchanged)
14 hop-1 children
53 total routing
52/53 online
(no children resolved)
H2200001033
id 222827 · ggVersion 2 · online
🔴🔴 14/13 · Over-subscribed (+1, was +2)
14 hop-1 children
34 total routing
34/34 online
(no children resolved)
Mesh topology tree
Each column is one gateway. Box color = sink's 13-child saturation. Edge color = child's RSSI tier. Devices listed in hop / signal order; capped at 50 per gateway for legibility.
Telemetry map logical layout — AROYA exposes no spatial coordinates for these devices
Hub-and-spoke layout per gateway, hop depth shown as concentric contours, node color = RSSI tier
(green ≥ −75 dBm · amber −75 to −85 · red < −85). Halo opacity shows weak-coverage envelope.
AROYA SPA returns latitude / longitude / what3words as
null on every device at this facility — open question for the customer is whether
to instrument physical positions in the portal so the map can become true-to-floor.
Prescriptive remediation
P0DEVICEImpact: High · Effort: Low
Replace batteries on 1 low-battery Node devices
Finding
1 Node devices below 30% battery, of which 0 below 15% (critical). Node Li-SOCl₂ cells fail to a complete dropout — no graceful degradation.
Action
Battery swap. Each Node uses Tadiran TL-5930 or equivalent C-cell. Schedule swap during next room walkthrough.
Expected outcome
Battery returns to 100%; device stays online with no further intervention for ~5 years.
Affected devices (1)
H8100001475 · bat 0% · room 13619
P0TOPOLOGYImpact: Medium · Effort: Low
Redistribute 4 children off sink of H2100004676
Finding
Gateway H2100004676 (id 124662) has 16 hop-1 children, 3 over the Wirepas 13-child slot limit (down from 17/+4 this morning — one child re-routed). Excess children compete for limited slots → increased latency, more retries, and growing data-gap rate.
Action
Move 4 children to an alternate parent. In-room candidates with headroom: H3440005720 (n=3/13), H3400001276 (n=2/13), H3440005738 (n=2/13)
Expected outcome
After rebalance: H2100004676 drops from 16/13 to 13/13. Retry rate normalizes, hop-1 latency drops ≥30%, data-gap rate falls toward fleet median within 24h.
Affected devices (4)
H3440005713 · node · RSSI 1 dBm · room 13619
H3440005756 · node · RSSI 1 dBm · room 13619
H3440005758 · node · RSSI 1 dBm · room 13619
H3440005762 · node · RSSI 1 dBm · room 13619
P0TOPOLOGYImpact: Medium · Effort: Low
Redistribute 2 children off sink of H2200001033
Finding
Gateway H2200001033 (id 222827) has 14 hop-1 children, 1 over the Wirepas 13-child slot limit (down from 15/+2 this morning — one child re-routed; this gateway has also absorbed deeper-tree routing load, 24→34 total devices). Excess children compete for limited slots → increased latency, more retries, and growing data-gap rate.
Action
Move 2 children to an alternate parent. In-room candidates with headroom: H3440005720 (n=3/13), H3400001276 (n=2/13), H3440005738 (n=2/13)
Expected outcome
After rebalance: H2200001033 drops from 14/13 to 13/13. Retry rate normalizes, hop-1 latency drops ≥30%, data-gap rate falls toward fleet median within 24h.
Affected devices (2)
H3410003355 · node · RSSI 1 dBm
H3410003365 · node · RSSI 1 dBm
P0TOPOLOGYImpact: Medium · Effort: Low
Redistribute 1 children off sink of H2100005242
Finding
Gateway H2100005242 (id 152540) has 14 hop-1 children, 1 over the Wirepas 13-child slot limit. Excess children compete for limited slots → increased latency, more retries, and growing data-gap rate.
Action
Move 1 children to an alternate parent. In-room candidates with headroom: H3440005720 (n=3/13), H3400001276 (n=2/13), H3440005738 (n=2/13)
Expected outcome
After rebalance: H2100005242 drops from 14/13 to 13/13. Retry rate normalizes, hop-1 latency drops ≥30%, data-gap rate falls toward fleet median within 24h.
Affected devices (1)
H3400001273 · repeater · RSSI 1 dBm
P0TOPOLOGYImpact: Medium · Effort: Low
Redistribute 1 children off sink of H2100005246
Finding
Gateway H2100005246 (id 152550) has 14 hop-1 children, 1 over the Wirepas 13-child slot limit. Excess children compete for limited slots → increased latency, more retries, and growing data-gap rate.
Action
Move 1 children to an alternate parent. In-room candidates with headroom: H3440005720 (n=3/13), H3400001276 (n=2/13), H3440005738 (n=2/13)
Expected outcome
After rebalance: H2100005246 drops from 14/13 to 13/13. Retry rate normalizes, hop-1 latency drops ≥30%, data-gap rate falls toward fleet median within 24h.
Affected devices (1)
H3440005734 · node · RSSI 1 dBm · room 13618
P1DEVICEImpact: Medium · Effort: Medium
Restore 4 offline devices on gateway H2100004676
Finding
4 devices route through gateway H2100004676 but are currently offline / stale (>24h since last comm).
Action
Physical check: verify gateway is online and antenna seated; swap battery on Node devices; for non-Node PoE devices verify power + Ethernet. List: H3440005758 (node), H4210002602 (h421), H4210002607 (h421), H8100001475 (node)
Expected outcome
After swap / power-restore: 4 devices return to online state within 5–15 min of physical fix; fleet online-rate climbs by 3 pp.
Affected devices (4)
H3440005758 · node · room 13619
H4210002602 · h421 · room 13617
H4210002607 · h421 · room 18777
H8100001475 · node · room 13619
P1DEVICEImpact: Medium · Effort: Low
Restore 2 offline devices on gateway H2100005242
Finding
2 devices route through gateway H2100005242 but are currently offline / stale (>24h since last comm).
Action
Physical check: verify gateway is online and antenna seated; swap battery on Node devices; for non-Node PoE devices verify power + Ethernet. List: H4210002601 (h421), H4210002620 (h421)
Expected outcome
After swap / power-restore: 2 devices return to online state within 5–15 min of physical fix; fleet online-rate climbs by 1 pp.
Affected devices (2)
H4210002601 · h421
H4210002620 · h421
P3PROCESSImpact: Medium · Effort: Low
Set up an early-warning alert for parent saturation ≥ 11 children
Finding
Several parents are at or above 11 children — the 'watch' threshold. Without a monitor, the next added device may silently push a parent over 13.
Action
Configure an AROYA computed alert that fires when any device parent count ≥ 11. Add to the facility's standard alert pack; review in the weekly device-health digest.
Expected outcome
Preemptive intervention before saturation creates measurable gap-rate degradation. Catches new-device adds that would over-subscribe.
P3PROCESSImpact: Low · Effort: Low
Document as-built mesh topology in customer wiki
Finding
Topology is not currently captured in the customer wiki — future device adds are blind to the existing parent loading.
Action
Add a 'Mesh topology' section to the facility's wiki with the parent → child table from this report and the per-gateway loading. Update on every device add.
Expected outcome
New-device decisions become topology-aware; saturation regressions become rare and easily diagnosed.
Prioritized action plan
01P0Replace batteries on 1 low-battery Node devicesImpact: High · Effort: Low
02P0Redistribute 4 children off sink of H2100004676Impact: Medium · Effort: Low
03P0Redistribute 2 children off sink of H2200001033Impact: Medium · Effort: Low
04P0Redistribute 1 children off sink of H2100005242Impact: Medium · Effort: Low
05P0Redistribute 1 children off sink of H2100005246Impact: Medium · Effort: Low
06P1Restore 4 offline devices on gateway H2100004676Impact: Medium · Effort: Medium
07P1Restore 2 offline devices on gateway H2100005242Impact: Medium · Effort: Low
08P3Set up an early-warning alert for parent saturation ≥ 11 childrenImpact: Medium · Effort: Low