A starting point is to turn off nodes 1, 2, 4 and 5.
Now test the coverage in all rooms.
This might be the simplest and most efficient solution (to quote Elon Musk " the best part is no part. The best process is no process. It weighs nothing, costs nothing, can't go wrong.").
Welcome @GavinM.
Feel free to ask questions or share your experiences 
Here is the output for 'uptime' for red 3: ' 16:45:49 up 1 day, 4:29, load average: 0.00, 0.01, 0.00'
and here is the output for dmesg: '[ 0.000000] Linux version 5.15.150 (builder@buildhost) (mipsel-openwrt-linux-musl-gcc (OpenWrt GCC 12.3.0 r23809-234f1a2efa) 12.3.0, GNU ld (GNU Binutils) 2.40.0) #0 SMP Fri Mar 22 22:09:42 2024
[ 0.000000] SoC Type: MediaTek MT7621 ver:1 eco:3
[ 0.000000] printk: bootconsole [early0] enabled
[ 0.000000] CPU0 revision is: 0001992f (MIPS 1004Kc)
[ 0.000000] MIPS: machine is ZyXEL WSM20
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] VPE topology {2,2} total 4
[ 0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[ 0.000000] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x000000000fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x000000000fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000000fffffff]
[ 0.000000] percpu: Embedded 12 pages/cpu s17808 r8192 d23152 u49152
[ 0.000000] pcpu-alloc: s17808 r8192 d23152 u49152 alloc=124096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 64960
[ 0.000000] Kernel command line: console=ttyS0,115200n1
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[ 0.000000] Writing ErrCtl register=00000c20
[ 0.000000] Readback ErrCtl register=00000c20
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 249092K/262144K available (7303K kernel code, 629K rwdata, 880K rodata, 1224K init, 225K bss, 13052K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] NR_IRQS: 256
[ 0.000000] clocksource: GIC: mask: 0xffffffffffffffff max_cycles: 0xcaf478abb4, max_idle_ns: 440795247997 ns
[ 0.000004] sched_clock: 64 bits at 880MHz, resolution 1ns, wraps every 4398046511103ns
[ 0.008057] Calibrating delay loop... 586.13 BogoMIPS (lpj=2930688)
[ 0.066220] pid_max: default: 32768 minimum: 301
[ 0.071639] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.078853] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.090518] rcu: Hierarchical SRCU implementation.
[ 0.096008] smp: Bringing up secondary CPUs ...
[ 0.101441] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[ 0.101469] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[ 0.101484] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
[ 0.101529] CPU1 revision is: 0001992f (MIPS 1004Kc)
[ 0.160798] Synchronize counters for CPU 1: done.
[ 0.193433] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[ 0.193455] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[ 0.193466] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
[ 0.193491] CPU2 revision is: 0001992f (MIPS 1004Kc)
[ 0.252361] Synchronize counters for CPU 2: done.
[ 0.283007] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[ 0.283029] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[ 0.283040] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
[ 0.283071] CPU3 revision is: 0001992f (MIPS 1004Kc)
[ 0.337544] Synchronize counters for CPU 3: done.
[ 0.367402] smp: Brought up 1 node, 4 CPUs
[ 0.376822] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.386628] futex hash table entries: 1024 (order: 3, 32768 bytes, linear)
[ 0.393717] pinctrl core: initialized pinctrl subsystem
[ 0.400571] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.407207] thermal_sys: Registered thermal governor 'step_wise'
[ 0.413143] FPU Affinity set after 11720 emulations
[ 0.431961] clocksource: Switched to clocksource GIC
[ 0.438230] NET: Registered PF_INET protocol family
[ 0.443352] IP idents hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.451530] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 0.459848] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.467552] TCP established hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.475180] TCP bind hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.482308] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.488740] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.495250] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.502580] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.508193] PCI: CLS 0 bytes, default 32
[ 0.515009] workingset: timestamp_bits=14 max_order=16 bucket_order=2
[ 0.526883] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.532761] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.544158] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 0.555674] mt7621_gpio 1e000600.gpio: registering 32 gpios
[ 0.561596] mt7621_gpio 1e000600.gpio: registering 32 gpios
[ 0.567600] mt7621_gpio 1e000600.gpio: registering 32 gpios
[ 0.573672] mt7621-pci 1e140000.pcie: host bridge /pcie@1e140000 ranges:
[ 0.580341] mt7621-pci 1e140000.pcie: No bus range found for /pcie@1e140000, using [bus 00-ff]
[ 0.589110] mt7621-pci 1e140000.pcie: MEM 0x0060000000..0x006fffffff -> 0x0060000000
[ 0.597212] mt7621-pci 1e140000.pcie: IO 0x001e160000..0x001e16ffff -> 0x0000000000
[ 0.961964] mt7621-pci 1e140000.pcie: PCIE0 enabled
[ 0.966779] mt7621-pci 1e140000.pcie: PCIE1 enabled
[ 0.971639] PCI coherence region base: 0x60000000, mask/settings: 0xf0000002
[ 0.978820] mt7621-pci 1e140000.pcie: PCI host bridge to bus 0000:00
[ 0.985112] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.990515] pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff]
[ 0.997369] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 1.003548] pci 0000:00:00.0: [0e8d:0801] type 01 class 0x060400
[ 1.009472] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x7fffffff]
[ 1.015710] pci 0000:00:00.0: reg 0x14: [mem 0x60600000-0x6060ffff]
[ 1.022005] pci 0000:00:00.0: supports D1
[ 1.025927] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[ 1.032494] pci 0000:00:01.0: [0e8d:0801] type 01 class 0x060400
[ 1.038479] pci 0000:00:01.0: reg 0x10: [mem 0x00000000-0x7fffffff]
[ 1.044732] pci 0000:00:01.0: reg 0x14: [mem 0x60610000-0x6061ffff]
[ 1.050969] pci 0000:00:01.0: supports D1
[ 1.054911] pci 0000:00:01.0: PME# supported from D0 D1 D3hot
[ 1.062816] pci 0000:01:00.0: [14c3:7916] type 00 class 0x000280
[ 1.068793] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit pref]
[ 1.075983] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x00003fff 64bit pref]
[ 1.083155] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x00000fff 64bit pref]
[ 1.090403] pci 0000:01:00.0: supports D1 D2
[ 1.094601] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 1.101181] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:00.0 (capable of 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
[ 1.117355] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[ 1.122565] pci 0000:00:00.0: bridge window [io 0x0000-0x0fff]
[ 1.128563] pci 0000:00:00.0: bridge window [mem 0x60000000-0x600fffff]
[ 1.135326] pci 0000:00:00.0: bridge window [mem 0x60100000-0x602fffff pref]
[ 1.142510] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 1.149348] pci 0000:02:00.0: [14c3:7915] type 00 class 0x000280
[ 1.155341] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit pref]
[ 1.162527] pci 0000:02:00.0: reg 0x18: [mem 0x00000000-0x00003fff 64bit pref]
[ 1.169664] pci 0000:02:00.0: reg 0x20: [mem 0x00000000-0x00000fff 64bit pref]
[ 1.176973] pci 0000:02:00.0: supports D1 D2
[ 1.181151] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 1.187784] pci 0000:02:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:01.0 (capable of 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
[ 1.203976] pci 0000:00:01.0: PCI bridge to [bus 02-ff]
[ 1.209138] pci 0000:00:01.0: bridge window [io 0x0000-0x0fff]
[ 1.215229] pci 0000:00:01.0: bridge window [mem 0x60300000-0x603fffff]
[ 1.221950] pci 0000:00:01.0: bridge window [mem 0x60400000-0x605fffff pref]
[ 1.229094] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 1.235728] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000]
[ 1.242268] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
[ 1.249156] pci 0000:00:01.0: BAR 0: no space for [mem size 0x80000000]
[ 1.255745] pci 0000:00:01.0: BAR 0: failed to assign [mem size 0x80000000]
[ 1.262670] pci 0000:00:00.0: BAR 8: assigned [mem 0x60000000-0x600fffff]
[ 1.269372] pci 0000:00:00.0: BAR 9: assigned [mem 0x60100000-0x602fffff pref]
[ 1.276571] pci 0000:00:01.0: BAR 8: assigned [mem 0x60300000-0x603fffff]
[ 1.283310] pci 0000:00:01.0: BAR 9: assigned [mem 0x60400000-0x605fffff pref]
[ 1.290454] pci 0000:00:00.0: BAR 1: assigned [mem 0x60600000-0x6060ffff]
[ 1.297226] pci 0000:00:01.0: BAR 1: assigned [mem 0x60610000-0x6061ffff]
[ 1.303962] pci 0000:00:00.0: BAR 7: assigned [io 0x0000-0x0fff]
[ 1.309980] pci 0000:00:01.0: BAR 7: assigned [io 0x1000-0x1fff]
[ 1.316063] pci 0000:01:00.0: BAR 0: assigned [mem 0x60100000-0x601fffff 64bit pref]
[ 1.323764] pci 0000:01:00.0: BAR 2: assigned [mem 0x60200000-0x60203fff 64bit pref]
[ 1.331419] pci 0000:01:00.0: BAR 4: assigned [mem 0x60204000-0x60204fff 64bit pref]
[ 1.339135] pci 0000:00:00.0: PCI bridge to [bus 01]
[ 1.344048] pci 0000:00:00.0: bridge window [io 0x0000-0x0fff]
[ 1.350070] pci 0000:00:00.0: bridge window [mem 0x60000000-0x600fffff]
[ 1.356835] pci 0000:00:00.0: bridge window [mem 0x60100000-0x602fffff pref]
[ 1.364013] pci 0000:02:00.0: BAR 0: assigned [mem 0x60400000-0x604fffff 64bit pref]
[ 1.371681] pci 0000:02:00.0: BAR 2: assigned [mem 0x60500000-0x60503fff 64bit pref]
[ 1.379399] pci 0000:02:00.0: BAR 4: assigned [mem 0x60504000-0x60504fff 64bit pref]
[ 1.387093] pci 0000:00:01.0: PCI bridge to [bus 02]
[ 1.392004] pci 0000:00:01.0: bridge window [io 0x1000-0x1fff]
[ 1.398022] pci 0000:00:01.0: bridge window [mem 0x60300000-0x603fffff]
[ 1.404783] pci 0000:00:01.0: bridge window [mem 0x60400000-0x605fffff pref]
[ 1.414527] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 1.425935] printk: console [ttyS0] disabled
[ 1.430245] 1e000c00.uartlite: ttyS0 at MMIO 0x1e000c00 (irq = 19, base_baud = 3125000) is a 16550A
[ 1.439320] printk: console [ttyS0] enabled
[ 1.447617] printk: bootconsole [early0] disabled
[ 1.460367] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xf1
[ 1.466795] nand: Toshiba NAND 128MiB 3,3V 8-bit
[ 1.471403] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.478969] mt7621-nand 1e003000.nand: ECC strength adjusted to 4 bits
[ 1.485602] 9 fixed-partitions partitions found on MTD device mt7621-nand
[ 1.493308] Creating 9 MTD partitions on "mt7621-nand":
[ 1.498570] 0x000000000000-0x000000100000 : "Bootloader"
[ 1.515497] 0x000000100000-0x000000200000 : "Config"
[ 1.532030] 0x000000200000-0x0000003c0000 : "Factory"
[ 1.556517] 0x0000003c0000-0x000002bc0000 : "firmware"
[ 1.978897] 2 fixed-partitions partitions found on MTD device firmware
[ 1.985513] Creating 2 MTD partitions on "firmware":
[ 1.990480] 0x000000000000-0x000000800000 : "kernel"
[ 2.079712] 0x000000800000-0x000002800000 : "ubi"
[ 2.419174] 0x000002bc0000-0x0000053c0000 : "Kernel2"
[ 2.841514] 0x0000053c0000-0x0000054c0000 : "persist"
[ 2.858326] 0x0000054c0000-0x0000058c0000 : "rootfs_data"
[ 2.906590] 0x0000058c0000-0x000007e80000 : "app"
[ 3.305136] 0x000007e80000-0x000007f80000 : "crt"
[ 3.465569] mt7530-mdio mdio-bus:1f: MT7530 adapts as multi-chip module
[ 3.479291] mtk_soc_eth 1e100000.ethernet eth0: mediatek frame engine at 0xbe100000, irq 21
[ 3.491456] mtk_soc_eth 1e100000.ethernet wan: mediatek frame engine at 0xbe100000, irq 21
[ 3.501604] i2c_dev: i2c /dev entries driver
[ 3.509237] NET: Registered PF_INET6 protocol family
[ 3.516903] Segment Routing with IPv6
[ 3.520649] In-situ OAM (IOAM) with IPv6
[ 3.524746] NET: Registered PF_PACKET protocol family
[ 3.529888] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 3.543536] 8021q: 802.1Q VLAN Support v1.8
[ 3.554023] mt7530-mdio mdio-bus:1f: MT7530 adapts as multi-chip module
[ 3.578740] mt7530-mdio mdio-bus:1f: configuring for fixed/rgmii link mode
[ 3.586537] mt7530-mdio mdio-bus:1f: Link is Up - 1Gbps/Full - flow control rx/tx
[ 3.593101] mt7530-mdio mdio-bus:1f lan3 (uninitialized): PHY [mt7530-0:01] driver [MediaTek MT7530 PHY] (irq=23)
[ 3.607147] mt7530-mdio mdio-bus:1f lan2 (uninitialized): PHY [mt7530-0:02] driver [MediaTek MT7530 PHY] (irq=24)
[ 3.619995] mt7530-mdio mdio-bus:1f lan1 (uninitialized): PHY [mt7530-0:03] driver [MediaTek MT7530 PHY] (irq=25)
[ 3.632867] DSA: tree 0 setup
[ 3.639007] UBI: auto-attach mtd5
[ 3.642416] ubi0: attaching mtd5
[ 4.312438] ubi0: scanning is finished
[ 4.333211] ubi0: attached mtd5 (name "ubi", size 32 MiB)
[ 4.338632] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 4.345517] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 4.352311] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 4.359248] ubi0: good PEBs: 256, bad PEBs: 0, corrupted PEBs: 0
[ 4.365253] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[ 4.372466] ubi0: max/mean erase counter: 7/3, WL threshold: 4096, image sequence number: 933195755
[ 4.381479] ubi0: available PEBs: 0, total reserved PEBs: 256, PEBs reserved for bad PEB handling: 20
[ 4.390702] ubi0: background thread "ubi_bgt0d" started, PID 328
[ 4.393619] block ubiblock0_0: created from ubi0:0(rootfs)
[ 4.402241] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[ 4.418108] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[ 4.429542] Freeing unused kernel image (initmem) memory: 1224K
[ 4.435521] This architecture does not have kernel memory protection.
[ 4.441979] Run /sbin/init as init process
[ 4.446059] with arguments:
[ 4.446064] /sbin/init
[ 4.446069] with environment:
[ 4.446074] HOME=/
[ 4.446079] TERM=linux
[ 4.911382] init: Console is alive
[ 4.915508] init: - watchdog -
[ 5.613250] kmodloader: loading kernel modules from /etc/modules-boot.d/
[ 5.673225] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 5.689525] init: - preinit -
[ 6.455636] random: jshn: uninitialized urandom read (4 bytes read)
[ 6.578279] random: jshn: uninitialized urandom read (4 bytes read)
[ 6.617034] random: jshn: uninitialized urandom read (4 bytes read)
[ 6.894359] mtk_soc_eth 1e100000.ethernet eth0: configuring for fixed/rgmii link mode
[ 6.907073] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 6.912463] mt7530-mdio mdio-bus:1f lan1: configuring for phy/gmii link mode
[ 6.923037] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 9.111652] UBIFS (ubi0:1): Mounting in unauthenticated mode
[ 9.117708] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 454
[ 9.200629] UBIFS (ubi0:1): recovery needed
[ 9.384275] UBIFS (ubi0:1): recovery completed
[ 9.388862] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[ 9.396685] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 9.406581] UBIFS (ubi0:1): FS size: 23871488 bytes (22 MiB, 188 LEBs), max 198 LEBs, journal size 1142784 bytes (1 MiB, 9 LEBs)
[ 9.418116] UBIFS (ubi0:1): reserved for root: 1127509 bytes (1101 KiB)
[ 9.424718] UBIFS (ubi0:1): media format: w5/r0 (latest is w5/r0), UUID 15F31CFD-ADAA-4604-8492-FF9C20D67080, small LPT model
[ 9.442486] mount_root: switching to ubifs overlay
[ 9.465632] urandom-seed: Seeding with /etc/urandom.seed
[ 9.583473] procd: - early -
[ 9.586598] procd: - watchdog -
[ 10.207073] procd: - watchdog -
[ 10.213797] procd: - ubus -
[ 10.270649] random: ubusd: uninitialized urandom read (4 bytes read)
[ 10.279432] random: ubusd: uninitialized urandom read (4 bytes read)
[ 10.290988] random: ubusd: uninitialized urandom read (4 bytes read)
[ 10.302576] procd: - init -
[ 10.915068] kmodloader: loading kernel modules from /etc/modules.d/*
[ 11.154795] Loading modules backported from Linux version v6.1.24-0-g0102425ac76b
[ 11.162340] Backport generated by backports.git v5.15.92-1-44-gd6ea70fafd36
[ 11.338781] pci 0000:00:00.0: enabling device (0006 -> 0007)
[ 11.344505] mt7915e_hif 0000:01:00.0: enabling device (0000 -> 0002)
[ 11.351403] pci 0000:00:01.0: enabling device (0006 -> 0007)
[ 11.357151] mt7915e 0000:02:00.0: enabling device (0000 -> 0002)
[ 11.637816] mt7915e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20220929104113a
[ 11.637816]
[ 11.974541] mt7915e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20220929104145
[ 12.012771] mt7915e 0000:02:00.0: WA Firmware Version: DEV_000000, Build Time: 20220929104205
[ 12.163614] urngd: v1.0.2 started.
[ 12.232548] PPP generic driver version 2.4.2
[ 12.240580] NET: Registered PF_PPPOX protocol family
[ 12.258059] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 12.531301] random: jshn: uninitialized urandom read (4 bytes read)
[ 13.103998] random: jshn: uninitialized urandom read (4 bytes read)
[ 13.123043] random: ubusd: uninitialized urandom read (4 bytes read)
[ 13.327772] random: crng init done
[ 13.331232] random: 32 urandom warning(s) missed due to ratelimiting
[ 13.543305] mtdblock: MTD device 'Factory' is NAND, please consider using UBI block devices instead.
[ 14.531515] mtdblock: MTD device 'Factory' is NAND, please consider using UBI block devices instead.
[ 20.806775] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
[ 20.836672] mtk_soc_eth 1e100000.ethernet eth0: configuring for fixed/rgmii link mode
[ 20.845092] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 20.854223] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 20.862886] mt7530-mdio mdio-bus:1f lan1: configuring for phy/gmii link mode
[ 20.872394] br-lan: port 1(lan1) entered blocking state
[ 20.877734] br-lan: port 1(lan1) entered disabled state
[ 20.886152] device lan1 entered promiscuous mode
[ 20.890853] device eth0 entered promiscuous mode
[ 20.930901] mt7530-mdio mdio-bus:1f lan2: configuring for phy/gmii link mode
[ 20.940444] br-lan: port 2(lan2) entered blocking state
[ 20.945977] br-lan: port 2(lan2) entered disabled state
[ 20.954449] device lan2 entered promiscuous mode
[ 20.973882] mt7530-mdio mdio-bus:1f lan3: configuring for phy/gmii link mode
[ 20.983689] br-lan: port 3(lan3) entered blocking state
[ 20.988987] br-lan: port 3(lan3) entered disabled state
[ 20.997918] device lan3 entered promiscuous mode
[ 21.026968] mtk_soc_eth 1e100000.ethernet wan: PHY [mdio-bus:00] driver [MediaTek MT7530 PHY] (irq=POLL)
[ 21.036587] mtk_soc_eth 1e100000.ethernet wan: configuring for phy/rgmii link mode
[ 22.466219] device lan1 left promiscuous mode
[ 22.471100] br-lan: port 1(lan1) entered disabled state
[ 22.564879] device lan2 left promiscuous mode
[ 22.569805] br-lan: port 2(lan2) entered disabled state
[ 22.679291] device lan3 left promiscuous mode
[ 22.684227] br-lan: port 3(lan3) entered disabled state
[ 22.753562] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
[ 26.740736] mtk_soc_eth 1e100000.ethernet eth0: configuring for fixed/rgmii link mode
[ 26.748661] device eth0 left promiscuous mode
[ 26.753414] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 26.757231] mt7530-mdio mdio-bus:1f lan1: configuring for phy/gmii link mode
[ 26.769931] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 26.776908] br-lan: port 1(lan1) entered blocking state
[ 26.782250] br-lan: port 1(lan1) entered disabled state
[ 26.789568] device lan1 entered promiscuous mode
[ 26.794318] device eth0 entered promiscuous mode
[ 26.824598] mt7530-mdio mdio-bus:1f lan2: configuring for phy/gmii link mode
[ 26.833516] br-lan: port 2(lan2) entered blocking state
[ 26.838779] br-lan: port 2(lan2) entered disabled state
[ 26.846175] device lan2 entered promiscuous mode
[ 26.860211] mt7530-mdio mdio-bus:1f lan3: configuring for phy/gmii link mode
[ 26.868807] br-lan: port 3(lan3) entered blocking state
[ 26.874186] br-lan: port 3(lan3) entered disabled state
[ 26.881544] device lan3 entered promiscuous mode
[ 26.897926] mtk_soc_eth 1e100000.ethernet wan: PHY [mdio-bus:00] driver [MediaTek MT7530 PHY] (irq=POLL)
[ 26.907465] mtk_soc_eth 1e100000.ethernet wan: configuring for phy/rgmii link mode
[ 86.857687] br-lan: port 4(phy1-ap0) entered blocking state
[ 86.863359] br-lan: port 4(phy1-ap0) entered disabled state
[ 86.869469] device phy1-ap0 entered promiscuous mode
[ 86.880276] device phy1-ap0 left promiscuous mode
[ 86.885310] br-lan: port 4(phy1-ap0) entered disabled state
[ 86.956709] br-lan: port 4(phy1-ap0) entered blocking state
[ 86.962392] br-lan: port 4(phy1-ap0) entered disabled state
[ 86.968556] device phy1-ap0 entered promiscuous mode
[ 87.240161] br-lan: port 5(phy0-ap0) entered blocking state
[ 87.245816] br-lan: port 5(phy0-ap0) entered disabled state
[ 87.251799] device phy0-ap0 entered promiscuous mode
[ 87.257138] br-lan: port 5(phy0-ap0) entered blocking state
[ 87.262784] br-lan: port 5(phy0-ap0) entered forwarding state
[ 87.268761] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 87.279142] device phy0-ap0 left promiscuous mode
[ 87.284150] br-lan: port 5(phy0-ap0) entered disabled state
[ 87.345442] br-lan: port 5(phy0-ap0) entered blocking state
[ 87.351049] br-lan: port 5(phy0-ap0) entered disabled state
[ 87.357345] device phy0-ap0 entered promiscuous mode
[ 87.362779] br-lan: port 5(phy0-ap0) entered blocking state
[ 87.368378] br-lan: port 5(phy0-ap0) entered forwarding state
[ 87.605245] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
[ 87.893406] br-lan: port 6(m-11s-0) entered blocking state
[ 87.898969] br-lan: port 6(m-11s-0) entered disabled state
[ 87.905508] device m-11s-0 entered promiscuous mode
[ 87.910828] br-lan: port 6(m-11s-0) entered blocking state
[ 87.916445] br-lan: port 6(m-11s-0) entered forwarding state
[ 87.930516] br-lan: port 6(m-11s-0) entered disabled state
[ 88.185800] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap0: link becomes ready
[ 88.192833] br-lan: port 4(phy1-ap0) entered blocking state
[ 88.198442] br-lan: port 4(phy1-ap0) entered forwarding state
[ 88.914838] br-lan: port 5(phy0-ap0) entered disabled state
[ 89.954820] br-lan: port 5(phy0-ap0) entered blocking state
[ 89.960437] br-lan: port 5(phy0-ap0) entered forwarding state
[ 90.104734] IPv6: ADDRCONF(NETDEV_CHANGE): m-11s-0: link becomes ready
[ 90.111818] br-lan: port 6(m-11s-0) entered blocking state
[ 90.117397] br-lan: port 6(m-11s-0) entered forwarding state
[ 100.761737] br-lan: port 3(lan3) entered disabled state
[ 100.833437] mt7530-mdio mdio-bus:1f lan3: configuring for phy/gmii link mode
[ 101.070369] br-lan: port 1(lan1) entered disabled state
[ 101.154153] mt7530-mdio mdio-bus:1f lan1: configuring for phy/gmii link mode'
I'm didn't restart it, I just noticed no Internet in the morning and later a changed MAC address.
Is there any way to "lock that down" in order to make it permanent on the nodes?
Yes exactly. I turned off WiFi and turned it back on again (Android). Same for my wifes iPhone. On my computer (Linux) I also had that issue, but it fixed itself after a few (maybe 20) seconds.
Done! I turned off 1, 4 and 5 only and left 2 online if that's OK. The reason is that this one also provides a wired connections (via its Ethernet ports) to one of my servers, a document scanner and a printer.
That's ok. The reason to turn some off is because they look redundant.
So the question is, can you connect anywhere in the flat with these turned off?
That is typical of CPD. I have OpenSuse Tumbleweed with Gnome desktop on my laptop and get the same delay when opening the lid in the morning.
The only way the mac can revert to the original duplicated mac is after either a restart of the mesh11sd service or a reboot. Then possibly, for just a few seconds, depending on the wireless driver/cpu speed etc, mesh11sd will start up and fix the issue.
To be clear, the bridge (br-lan) mac address should never change and it is this mac address that is used by the dhcp client to get an ip address, so the ipv4 should never change.
What can change is the meshnode mac address that HWMP uses and this is reflected in the output of mesh11sd connect and there can indeed be incorrect entries in the table, but they should disappear after a short while.
I asked for uptime, to see if it indicated if a crash and reboot had happened. Only you can tell if one node has been up a shorter time than the others..... if you see what I mean. The dmesg output was to see if mesh11sd had crashed and restarted - no sign of that.
It is locked down, in that it will always be the same once mesh11sd has started - it is not randomised.
Note that the mac address used for dhcp will be the mac that the bridge (br-lan) has. The mac address that the mesh interface has will be the locally administered/indexed version of the br-lan mac. It is recognisable, but different.
You can see the mac addresses if all the interfaces when mesh11sd is running by doing:
ip link
Here is the output of the portal node of my test system (a gl-mt1300, almost identical hardware to your ZyXEL WSM20).
root@meshnode-f5a4:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1504 qdisc mq state UP qlen 1000
link/ether 94:83:c4:29:f5:a4 brd ff:ff:ff:ff:ff:ff
3: wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 94:83:c4:29:f5:a3 brd ff:ff:ff:ff:ff:ff
4: lan1@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state LOWERLAYERDOWN qlen 1000
link/ether 96:83:c4:2c:f5:a4 brd ff:ff:ff:ff:ff:ff
5: lan2@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state LOWERLAYERDOWN qlen 1000
link/ether 94:83:c4:29:f5:a4 brd ff:ff:ff:ff:ff:ff
10: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 94:83:c4:29:f5:a4 brd ff:ff:ff:ff:ff:ff
18: phy1-ap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP qlen 1000
link/ether 96:83:c4:2b:f5:a4 brd ff:ff:ff:ff:ff:ff
19: phy0-ap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP qlen 1000
link/ether 96:83:c4:2a:f5:a4 brd ff:ff:ff:ff:ff:ff
20: m-11s-0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP qlen 1000
link/ether 96:83:c4:29:f5:a4 brd ff:ff:ff:ff:ff:ff
root@meshnode-f5a4:~#
Thanks @bluewavenet, just getting used to driving the interface 
I'm having issues in the rooms on the top, where 5 and 4 are located (but still turned off). WiFi connection is there (maybe 3/4 of the bars), but the Internet connection doesn't work.
Is it possible for me to assign fixed IP's based on that address then? I'm asking as you mentioned something like not to trust LuCi before (and that's where I'd look it up)
No, uptime looks correct. I'm not aware of any crashes or power outages (but I was sleeping), unlikely though.
Yes, you would assign static dhcp leases in your main router (is it running OpenWrt?)
Problem is you don't know which you are actually connecting to - depends on the user device whether you can see the essid-mac. That looks like more than enough signal strength. It is probably red3...
Can you mesh11sd connect into red 3?
If you can, try a ping and see what you get:
ping openwrt.org
This will test the ipv4 connectivity.
If it does not work, try:
ping -6 -I br-lan ff02::2
This is a multicast ping to all "routers" and will show many "dup" messages as all the meshnodes plus probably your main router reply. A good test of connectivity.
OK thanks I will do that. It's running OPNsense, I built it myself.
I can see it on my Linux computer, but not on the phones (I checked). I'm also only carrying around the phones, so only seeing the issue there. However, I'm also suspecting red-3 (as red-2 has all the stuff connected to it via Ethernet like a printer and such and it works).
Yes (SSHed into green, then used mesh11sd to connect to red-3. I probably could have SSHed directly into it too I think). Anyway, it works fine (atm): PING openwrt.org (64.226.122.113): 56 data bytes 64 bytes from 64.226.122.113: seq=0 ttl=55 time=23.100 ms 64 bytes from 64.226.122.113: seq=1 ttl=55 time=32.007 ms 64 bytes from 64.226.122.113: seq=2 ttl=55 time=17.024 ms etc. and --- openwrt.org ping statistics --- 14 packets transmitted, 14 packets received, 0% packet loss round-trip min/avg/max = 15.921/18.790/32.007 ms at the end.
I used ping -6 -I br-lan ff02::2 anyway and it also worked: 'PING ff02::2 (ff02::2): 56 data bytes
64 bytes from fe80::d61a:d1ff:fe12:af1c: seq=0 ttl=64 time=0.917 ms
64 bytes from fe80::5683:3aff:fe79:ac78: seq=0 ttl=64 time=3.846 ms (DUP!)
64 bytes from fe80::ea6a:64ff:feab:8aa2: seq=0 ttl=64 time=4.937 ms (DUP!)etc. and--- ff02::2 ping statistics ---
11 packets transmitted, 11 packets received, 34 duplicates, 0% packet loss
round-trip min/avg/max = 0.610/15.372/78.520 ms`.
BTW: I'm doing all the tests from my computer in the same room as red-2 (which it is connected to as evident by the BSSID). Should I do something like iwlist scanning via Termux from my phone in another room to confirm a connection to red-3 that way?
Yes. I'm not familiar with Termux, so I guess a "yes". I use PingTools on Android for things like that.
It didn't work unfortunately, as it needs root access. What did work however (I learned it via stackexchange) was just dialing *#*#4636#*#* in the phone app. This command reveals a lot of WiFi info and did confirm that I was connected to red-3. Everything was fine however and I had no network issues just now.
So I've been using this set-up as is (without turning red-1, red-4 and red-5 back on) for about a week now and so far it is working pretty well. I still have to manually turn off/on the WiFi in the two rooms on top, but not nearly as often as before (maybe twice in a full day). For 'fixed devices' such as the computers, smart speakers or the CoreELEC box no re-connection was necessary at all anymore. Due to this, I suspect the 'problem' now is with roaming.
Thank you @bluewavenet for all your support, patience, explanations and of course for running mesh11sd in general.
As you are most likely connecting your phones etc using 5GHz, they will be hanging on to the signal from Green regardless of 802.11r. Many devices react like this. There are numerous threads on this forum about "roaming" that you could read and @psherman has helped many on the subject.
I would recommend reducing the 5GHz transmit power on Green. The default is probably 20dBm or more. A good fist step is to reduce to 14dBm and see if it changes things.
Remember to use uci commands:
service mesh11sd stop
uci revert wireless
uci set wireless.radio1.txpower='14'
uci commit wireless
service mesh11sd start;exit
So I tried this and lost connection on all devices and had to restart the AP. Is there a command to check if txpower is still at 14dBm now?
LuCi shows both radios as disabled (which is probably incorrect).
Yes it will as it is only looking at the static config in /etc/config/wireless. Mesh11sd is managing a dynamic config.
To see the current state of the wifi interfaces, including the transmitted power, run:
iwinfo
Yes you will for a minute or so then the mesh should re-establish.
I assume you connected via ethernet to run luci? Or is green's access point working?
I can confirm it's still at 14 dBm, but I'm also still having issues especially in the room on the top left (with red 5). Should I lower tx power on the other two devices as well?
No, WiFi. It works again after the restart. No other issues anymore.
This is a trial and error thing on the 5GHz access point interfaces.
( For the benefit of others watching this thread, nothing to do with the actual mesh that is in this case on 2.4GHz ).
So yes, try reducing tx power on 5GHz on the other nodes as well.
I've marked your leech mode comment as the correct solution as I personally think it had the biggest impact on my situation, but of course the entire thread has been immensely helpful.
I did and I feel like the situation further improved, although it isn't totally painless yet. Generally I'm very happy with it though.
Red-2 is losing connection every once in a while still.
Most of the issues here have been due to the close proximity of the nodes to each other.
On Red-2, you could try adjusting mesh_rssid_threshold.
It is probably connecting to one of the other nodes apart from Green, on occasion.
See what the station list for Red-2 is:
mesh11sd stations
See waht the received signal strength for Green is.
View current setting:
mesh11sd mesh_rssi_threshold
Increase the rssi threshold "on the fly".
Increase it by 3dBm (making it less sensitive):
mesh11sd mesh_rssi_threshold +
Do this a few times to bring it within 3dBm of the received signal from Green.
See if this improves things.
If it does, make the changes permanent by doing:
mesh11sd commit_changes commit
=========================================================================== Stations connected to this node: Station 56:83:3a:79:ac:48 (on m-11s-0) inactive time: 60 ms rx bytes: 1729453 rx packets: 14639 tx bytes: 474721 tx packets: 3337 tx retries: 0 tx failed: 0 rx drop misc: 678 signal: -54 [-60, -55] dBm signal avg: -54 [-60, -55] dBm Toffset: 234819266493 us tx bitrate: 390.0 MBit/s 40MHz HE-MCS 8 HE-NSS 2 HE-GI 1 HE-DCM 0 tx duration: 14921316 us rx bitrate: 344.1 MBit/s 40MHz HE-MCS 7 HE-NSS 2 HE-GI 0 HE-DCM 0 rx duration: 167739 us last ack signal:-58 dBm avg ack signal: -57 dBm airtime weight: 256 mesh llid: 0 mesh plid: 0 mesh plink: ESTAB mesh airtime link metric: 23 mesh connected to gate: yes mesh connected to auth server: no mesh local PS mode: ACTIVE mesh peer PS mode: ACTIVE mesh non-peer PS mode: ACTIVE authorized: yes authenticated: yes associated: yes preamble: long WMM/WME: yes MFP: yes TDLS peer: no DTIM period: 2 beacon interval:100 connected time: 590 seconds associated at [boottime]: 61.273s associated at: 1719219905567 ms current time: 1719220495562 ms ===========================================================================
Change the mesh rssi threshold Current threshold for new connections [ -65 ] dBm Usage: mesh11sd mesh_rssi_threshold [+|-] [force] where "+" increments by 3dBm and "-" decrements by 3dBm The keyword "force" forces the new threshold on all peers
Change the mesh rssi threshold Previous threshold [ -59 ] dBm New threshold - [ -56 ] dBm
I did it until I reached -56 (green has -54). I then committed and will monitor the situation (I'm guessing I can go back with mesh11sd mesh_rssi_threshold - so no harm in committing right away).