by Addium
Wirepas mesh & device health · Cannapproach — CCMS · 2026-06-24
Cannapproach — CCMS · 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.
1 of 6 gateways are currently offline. With no parent saturation as the lede, gateway-down is the leading mesh health concern — every device that routed through the offline gateway has no upstream path.
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).
Mesh health KPIs
21
Unique radios
29 raw serials, −8 dash-2 pairs
15
Online
71.4% of radios
5/6
Gateways
online
0
Parents over 13
Wirepas 13-child limit
0
Parents 11–12
watch tier
0
Excess children
over 13-slot budget
Per-gateway summary
H2100005595
id 192178 · ggVersion 2 · online
🟢 1/13 · Headroom
1 hop-1 children
2 total routing
2/2 online
(no children resolved)
H2110001266
id 202015 · ggVersion 2 · OFFLINE
🟢 3/13 · Headroom
3 hop-1 children
3 total routing
0/3 online
(no children resolved)
H2110001269
id 202116 · ggVersion 2 · online
🟢 0/13 · Headroom
0 hop-1 children
0 total routing
0/0 online
(no children resolved)
H2110001287
id 202052 · ggVersion 2 · online
🟢 1/13 · Headroom
1 hop-1 children
2 total routing
2/2 online
(no children resolved)
H2200001038
id 222833 · ggVersion 2 · online
🟢 2/13 · Headroom
2 hop-1 children
4 total routing
4/4 online
(no children resolved)
H2200001039
id 222789 · ggVersion 2 · online
🟢 2/13 · Headroom
2 hop-1 children
4 total routing
2/4 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
P1DEVICEImpact: Medium · Effort: Low
Restore 1 offline devices on gateway gateway-None
Finding
1 devices route through gateway gateway-None 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: H2110001266 (gateway)
Expected outcome
After swap / power-restore: 1 devices return to online state within 5–15 min of physical fix; fleet online-rate climbs by 7 pp.
Affected devices (1)
H2110001266 · gateway
P1DEVICEImpact: Medium · Effort: Low
Restore 3 offline devices on gateway H2110001266
Finding
3 devices route through gateway H2110001266 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: H3310009922 (node), H5200001002 (h520), H8200001003 (node)
Expected outcome
After swap / power-restore: 3 devices return to online state within 5–15 min of physical fix; fleet online-rate climbs by 20 pp.
Affected devices (3)
H3310009922 · node · room 19935
H5200001002 · h520 · room 19935
H8200001003 · node · room 19935
P1DEVICEImpact: Medium · Effort: Low
Restore 2 offline devices on gateway H2200001039
Finding
2 devices route through gateway H2200001039 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: H3440015299 (node), H3440015383 (node)
Expected outcome
After swap / power-restore: 2 devices return to online state within 5–15 min of physical fix; fleet online-rate climbs by 13 pp.
Affected devices (2)
H3440015299 · node · room 20154
H3440015383 · node · room 20155
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
01P1Restore 1 offline devices on gateway gateway-NoneImpact: Medium · Effort: Low
02P1Restore 3 offline devices on gateway H2110001266Impact: Medium · Effort: Low
03P1Restore 2 offline devices on gateway H2200001039Impact: Medium · Effort: Low