by Addium
Wirepas mesh & device health · Palladium · 2026-06-25

Palladium · 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.

FacilityPalladium (4699) Pulled2026-06-25 19:24 UTC SourceAROYA SPA /devices/?facility=4699 Rooms10 flower rooms, 51 zones

Executive summary

Wirepas 13-child slot limit is breached on 1 parent at this facility. The worst-loaded parent is H2200001022 (sink) carrying 14 children — 1 over the 13-slot limit. Total excess load across all over-subscribed parents: 1 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.
1 of 2 gateways are OFFLINE (H2200001029). With 2 gateways planned for redundancy at Palladium, losing one cuts mesh fail-over headroom in half. This is the single highest-leverage fix in the plan.
1 room (Room 8) has zero AROYA radios deployed. Either physically empty / in build-out, or device assignments were dropped. Confirm with operator before next batch flip into those rooms.
2 rooms running with ≥50% of radios offline: Room 9 (4/6 dark), Room 10 (6/8 dark). Substrate VWC + climate data is degraded in these rooms, so AROYA crop-steering recommendations cannot be trusted there until restored.
Battery health is excellent: every battery-powered radio is reporting ≥99% (recent deployment, fresh Li-SOCl₂ cells). No battery-driven dropouts expected for ~5 years on current cells.

13-child slot rule why this is the load-bearing metric

Each parent node in the Wirepas mesh — gateway sink 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. H3440017858 and H3440017858-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. (52 duplicate sensor-head entries collapsed for this facility.)

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

Unique radios

128 raw serials, −52 dash-2 dedup

Online

74% · 20 offline

1/2

Gateways

1 offline

Parents over 13

Wirepas 13-child limit

Parents 11–13

watch tier (no headroom)

Excess children

over 13-slot budget

9/10

Rooms instrumented

Room 8 dark

56/56

Batteries ≥ 99%

recent deploy — fresh cells

Per-gateway summary 2 gateways · saturation tier checked at the sink

H2200001022

id 219837 · ggVersion 2 · WP5 · online

🔴🔴 14/13 · Over-subscribed (+1)

14 hop-1 children

73 total radios in tree

55/73 online

Sink id 219836 (hop-0 anchor). Saturation tier checked at the sink, not the gateway itself.

H2200001029 OFFLINE

id 219853 · ggVersion 2 · WP5 · OFFLINE · last comm 444h ago

🟢 1/13

1 hop-1 children

1 total radios in tree

0/1 online

Sink id 219852 (hop-0 anchor). Saturation tier checked at the sink, not the gateway itself.

Mesh topology tree

Each column is one gateway. Sink box color = 13-child saturation tier. Children listed in sort order; numbers next to a child = its own child count (it's a relay). Capped at 30 children per gateway for legibility.

Telemetry map logical layout — AROYA exposes no spatial coordinates for these devices

Hub-and-spoke per gateway. Concentric rings = hop depth. Spoke nodes = direct h421/relay children. Spoke size proportional to grandchild count; small dots = grandchildren clustered around their relay. Color = online/offline status, with saturation tier overlay on relays carrying ≥11 kids.

Per-room device tables

Mesh infrastructure · 16 radios · 6/16 online — gateways, sinks, repeaters not bound to a grow room

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H2200001022	gateway	●	—	—	—	WP5	(root)	OK	gateway
H2200001029	gateway	○	—	—	—	WP5	(root)	CRITICAL	offline
H3400003318	repeater	○	100	1	100	—	H4210006891	CRITICAL	offline
H3400003322	repeater	○	100	4	100	—	H4210006891	CRITICAL	offline
H3400003323	repeater	○	100	8	100	—	H3440017861	CRITICAL	offline
H3400003324	repeater	○	100	8	100	—	H3440017861	CRITICAL	offline
H3440017861	node	○	100	1	76	—	H4210006595	CRITICAL	offline
H3440017871	node	●	100	1	100	—	sink/H2200001022	OK	node
H3440017875	node	●	100	2	100	—	sink/H2200001022	OK	node
H3440017917	node	○	100	1	100	—	H4210006891	CRITICAL	offline
H3440017918	node	○	100	8	100	—	H3440017861	CRITICAL	offline
H3440017919	node	○	100	8	100	—	H3440017861	CRITICAL	offline
H3440017925	node	●	100	5	100	—	H4210006899	OK	node
H3440017934	node	●	100	1	91	—	sink/H2200001022	OK	node
H3440017938	node	●	100	2	100	—	H4210006592	OK	node
H4210006593	h421	○	—	5	100	—	sink/H2200001029	CRITICAL	offline

Room 1 · 7 radios · 7/7 online

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H3440017867	node	●	100	2	100	—	H4210006604	OK	healthy
H3440017872	node	●	100	8	100	—	H3440017934	OK	healthy
H3440017874	node	●	100	1	96	—	sink/H2200001022	OK	healthy
H3440017879	node	●	100	2	100	—	H4210006601	OK	healthy
H3440017931	node	●	100	1	91	—	sink/H2200001022	OK	healthy
H4210006600	h421	●	—	2	100	—	H4210006601	OK	healthy
H4210006601	h421	●	—	1	96	—	sink/H2200001022	OK	healthy

Room 2 · 8 radios · 8/8 online

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H3440017914	node	●	100	3	100	—	H4210006601	OK	healthy
H3440017915	node	●	100	5	100	—	H4210006601	OK	healthy
H3440017921	node	●	100	5	100	—	H4210006604	OK	healthy
H3440017922	node	●	100	3	100	—	H4210006604	OK	healthy
H3440017924	node	●	100	1	100	—	sink/H2200001022	OK	healthy
H3440017932	node	●	100	6	100	—	H4210006597	OK	healthy
H4210006597	h421	●	—	2	100	—	H4210006899	OK	healthy
H4210006604	h421	●	—	2	100	—	sink/H2200001022	OK	healthy

Room 3 · 8 radios · 8/8 online

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H3440017910	node	●	100	1	100	—	H4210006902	OK	healthy
H3440017912	node	●	100	2	100	—	H4210006601	OK	healthy
H3440017916	node	●	100	1	100	—	H4210006899	OK	healthy
H3440017923	node	●	100	3	100	—	H4210006899	OK	healthy
H3440017926	node	●	100	2	100	—	sink/H2200001022	OK	healthy
H3440017927	node	●	100	3	100	—	H4210006604	OK	healthy
H4210006896	h421	●	—	3	100	—	H4210006899	OK	healthy
H4210006905	h421	●	—	3	100	—	H4210006896	OK	healthy

Room 4 · 8 radios · 8/8 online

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H3440017859	node	●	100	3	100	—	H4210006899	OK	healthy
H3440017862	node	●	100	5	100	—	H4210006899	OK	healthy
H3440017863	node	●	100	4	100	—	H4210006899	OK	healthy
H3440017864	node	●	100	2	96	—	H4210006595	OK	healthy
H3440017865	node	●	100	1	100	—	H4210006604	OK	healthy
H3440017868	node	●	100	3	100	—	H4210006899	OK	healthy
H4210006899	h421	●	—	1	95	—	H4210006604	OK	healthy
H4210006902	h421	●	—	2	100	—	H4210006604	OK	healthy

Room 5 · 7 radios · 7/7 online

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H3440017911	node	●	100	4	100	—	H4210006599	OK	healthy
H3440017929	node	●	100	2	100	—	H4210006899	OK	healthy
H3440017933	node	●	100	2	100	—	H4210006896	OK	healthy
H3440017935	node	●	100	2	100	—	H4210006899	OK	healthy
H3440017937	node	●	100	7	100	—	H4210006595	OK	healthy
H4210006595	h421	●	—	1	100	—	H4210006902	OK	healthy
H4210006599	h421	●	—	2	98	—	H4210006899	OK	healthy

Room 6 · 7 radios · 7/7 online

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H3440017913	node	●	100	3	99	—	H4210006595	OK	healthy
H3440017928	node	●	99	1	97	—	H4210006599	OK	healthy
H3440017930	node	●	100	1	98	—	H4210006599	OK	healthy
H3440017936	node	●	100	5	100	—	H4210006592	OK	healthy
H3440017939	node	●	100	4	100	—	H4210006595	OK	healthy
H4210006592	h421	●	—	2	100	—	H4210006902	OK	healthy
H4210006598	h421	●	—	1	98	—	H4210006899	OK	healthy

Room 7 · 1 radios · 1/1 online

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H4210006908	h421	●	—	1	78	—	H4210006601	OK	healthy

Room 8 · 0 devices — NO instrumentation

This room has zero AROYA radios assigned to it. Either physically empty (no plants), in build-out, or device assignment in AROYA is missing.

Room 9 · 6 radios · 2/6 online · 4 crit

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H4210006596	h421	●	—	1	89	—	H4210006891	OK	healthy
H4210006602	h421	●	—	1	96	—	H4210006908	OK	healthy
H3440017858	node	○	100	4	100	—	H4210006891	CRITICAL	offline
H3440017860	node	○	100	3	98	—	H4210006891	CRITICAL	offline
H3440017866	node	○	100	1	100	—	H4210006891	CRITICAL	offline
H3440017920	node	○	100	1	100	—	H4210006891	CRITICAL	offline

Room 10 · 8 radios · 2/8 online · 6 crit

Serial (base)	Model	On	Bat%	RSSI	LinkQ%	FW	Parent	State	Flags
H4210006603	h421	●	—	1	91	—	H4210006891	OK	healthy
H4210006891	h421	●	—	6	100	—	H4210006908	OK	healthy
H3440017869	node	○	100	1	47	—	sink/H2200001022	CRITICAL	offline
H3440017870	node	○	100	1	95	—	sink/H2200001022	CRITICAL	offline
H3440017873	node	○	100	1	84	—	sink/H2200001022	CRITICAL	offline
H3440017876	node	○	100	1	100	—	H4210006597	CRITICAL	offline
H3440017877	node	○	100	1	45	—	sink/H2200001022	CRITICAL	offline
H3440017878	node	○	100	3	19	—	sink/H2200001022	CRITICAL	offline

Prescriptive remediations 10 items · prioritized P0 → P3

GATEWAY P0 · Now #1

Restore offline gateway H2200001029

Finding

Gateway H2200001029 (id 219853) has been OFFLINE for 444h (18.5 days), last seen 2026-06-07. Its entire mesh subtree — every device routing through it — is dark. The 2-gateway design at Palladium means losing one gateway cuts active mesh redundancy in half.

Action

Onsite: verify gateway PoE power (gateways are PoE — no battery). Check ethernet link to the switch, switch port status, switch uplink. If the gateway is up but unreachable, restart the gateway and re-check 5min after boot. If power/network is fine but it stays down, RMA via AROYA support.

Expected outcome

Gateway returns to online. Its only descendant (H4210006593) rejoins within ~5min. Cross-gateway fail-over restored for the rest of the fleet.

TOPOLOGY P0 · Now #2

Redistribute 1 children off sink of gateway H2200001022

Finding

Parent H2200001022 carries 14 direct children, 1 over the Wirepas 13-slot limit. Excess children compete for non-existent slots → orphan attempts, multi-hop spillover, and growing data-gap rate on those devices.

Action

Move 1 children to alternate parent(s). In-room candidates with headroom (radios on same gateway, currently online, <11 children): H4210006596 (n=0/13), H4210006598 (n=0/13), H4210006600 (n=0/13), H4210006602 (n=0/13). Power-cycle the moved children so they re-join via the new parent (or wait for the next Wirepas route refresh ~30min).

Expected outcome

After rebalance: H2200001022 drops from 14/13 to ≤13/13. Retry rate on the rebalanced children falls toward fleet median within 24h; hop-1 latency on remaining children drops ≥30%.

COVERAGE P0 · Now #3

Room 8 has zero AROYA radios deployed

Finding

Room 8 (room_id 19949) shows 0 assigned devices in the AROYA inventory. The facility overview confirmed this room reports all-null on VWC/temp/VPD. Either it is physically empty / in build-out, or a previous deployment was un-assigned and never re-bound.

Action

Operator confirmation: is Room 8 an active grow room? If yes — schedule deployment of climate (h421) + substrate nodes per the standard 1× h421 + 5× nodes per room template. If no — mark room ARCHIVED in AROYA so the facility overview stops flagging it.

Expected outcome

No more null-data confusion in the facility overview. If activated: telemetry parity with sibling rooms.

ROOM P0 · Now #4

Room 9: 4/6 radios offline (67%)

Finding

Room 9 has 4 of 6 radios dropped. The dominant pattern: 4 of the offline radios route through parent H4210006891. This is consistent with either (a) the shared parent having a radio/PoE issue, or (b) a dead-zone in this room with weak signal to the only nearby relay.

Action

Onsite walk: verify parent H4210006891 is physically present and powered (h421 Climate One = PoE). Check the offline nodes for physical damage / displacement. If parent looks fine but children are clustered far away, add a mesh repeater (H4110*) midway. Confirm no metal racking has been moved between parent and children since deployment.

Expected outcome

After fix: Room 9 returns to ≥90% online. Substrate VWC + climate data resumes for any plants in those zones.

ROOM P0 · Now #5

Room 10: 6/8 radios offline (75%)

Finding

Room 10 has 6 of 8 radios dropped. The dominant pattern: 5 of the offline radios route through parent sink/H2200001022. This is consistent with either (a) the shared parent having a radio/PoE issue, or (b) a dead-zone in this room with weak signal to the only nearby relay.

Action

Onsite walk: verify parent sink/H2200001022 is physically present and powered (h421 Climate One = PoE). Check the offline nodes for physical damage / displacement. If parent looks fine but children are clustered far away, add a mesh repeater (H4110*) midway. Confirm no metal racking has been moved between parent and children since deployment.

Expected outcome

After fix: Room 10 returns to ≥90% online. Substrate VWC + climate data resumes for any plants in those zones.

TOPOLOGY P1 · This week #6

Watch parent H4210006899 — at 13/13 limit

Finding

Parent H4210006899 sits at exactly 13 direct children. ZERO headroom. Adding any device to its area pushes it over — and devices already attached will spill if a sibling rejoins or a Wirepas reshuffle occurs.

Action

No immediate action required. Block any new devices from binding to H4210006899 until you intentionally move one child off first. Add an alert at saturation ≥ 12.

Expected outcome

No future "why did Room X drop?" surprises tied to silent saturation.

INFRA P1 · This week #7

1 mesh repeater/h421 radios offline >24h with no room assignment

Finding

These radios appear to be in the mesh infrastructure pool (no room bound) but are NOT routing traffic. Either staged/spare devices that were never decommissioned, or in-room relays that lost their room binding. Either way they're dead weight in the AROYA inventory and may confuse future deploy planning.

Action

For each: confirm physical location. If staged spare — leave offline and tag in AROYA. If field-deployed but unbound — assign to correct room and verify power/signal. Decommission anything genuinely retired.

Expected outcome

Cleaner inventory. Accurate spare-pool count for future deployments.

MONITORING P2 · This quarter #8

Add early-warning alert for parent saturation ≥ 11 children

Finding

Saturation issues arrive silently — operators see "Room X has data gaps" days after the topology slipped over the line. Surface the leading indicator before children start dropping.

Action

Add a script that runs the saturation check from this report daily and pings #aroya-alerts when any parent crosses 11/13. Easy: re-use `_palladium_mesh_pull.py` + a small thresholding wrapper.

Expected outcome

You see saturation drift in the 11→12→13 progression before children fail. Reduces firefighting time by ~80% for this class of issue.

FIRMWARE P3 · Backlog #9

Both gateways are on WP5 — fleet is firmware-current at the root

Finding

Both Palladium gateways (H2200001022, H2200001029) report ggVersion=2 (Wirepas Profile 5). Node-level ggVersion is not exposed by the /devices/ endpoint, so per-node WP4-vs-WP5 status cannot be confirmed from this snapshot alone. The OTAP firmware push model means a sensor that was online during a previous push is on the same generation as its gateway.

Action

No action required for the network. If a node-by-node firmware audit is requested, that data lives in a different SPA endpoint (firmware status detail per device) and would need a separate pull.

Expected outcome

Continued WP4↔WP5 compatibility across the mesh. Future firmware pushes can be remote OTAP — no onsite needed unless a device is offline during the push window.

DOCUMENTATION P3 · Backlog #10

Document Palladium as-built mesh topology in customer wiki

Finding

No customer wiki entry exists for Palladium as of this audit. As a 2-gateway / 76-radio / 10-room facility, the as-built topology + parent→child map should live in the vault so the next mesh question doesn't require a full re-pull.

Action

Add `03-Clients/palladium/` org folder + per-facility file in claude-brain. Include this report's gateway-card data + topology tree. Update on every device add.

Expected outcome

Faster context for future audits. No "where was that parent change last month" thrashing.

Prioritized action plan

01 Restore offline gateway H2200001029 (dark 18.5d) Impact: High · Effort: Medium
02 Redistribute 1 children off sink of gateway H2200001022 Impact: High · Effort: Low
03 Watch parent H4210006899 at 13/13 Impact: Medium · Effort: Low
04 Resolve Room 8 zero-device state (deploy or archive) Impact: High · Effort: Medium
05 Restore 4 offline radios in Room 9 Impact: High · Effort: Medium
06 Restore 6 offline radios in Room 10 Impact: High · Effort: Medium
07 Triage 1 long-down infra radios Impact: Low · Effort: Low
08 Add saturation alert at ≥ 11 children Impact: Medium · Effort: Low
09 Create Palladium customer wiki entry Impact: Low · Effort: Low

Pulled live from AROYA SPA at 2026-06-25 19:24 UTC. Dash-2 deduped before counts. 13-child rule per Wirepas spec. Source: /devices/?facility=4699 · /rooms/[19942–19951]/v2/. Telemetry map is a logical (hub-and-spoke) rendering — AROYA does not expose physical lat/lon for these radios.