Hi @nate,
Thanks again for the detailed logs and your patience here, they made triage easy.
What you are seeing is actually a driver issue where it is forcing the TX power to the regulatory maximum for that particular channel.
The good new is that now that we have people asking for reduced power (not a common request for Wi-Fi HaLow!) we have fixed this in the driver. Your configured TX power via the UI will now be respected with the channel’s regulatory max only behaving as the upper limit.
This fix is introduced in 2.0 drivers and should be included in the next HaLowLink 2 release. I don’t have any immediate timelines for you at this point but it is something my team is actively working on right now.
Until then, the only workaround is the one discussed above where you set the power with iw after the interface is fully up and re-apply it after any channel changes or reboots (it is non-persistent as you have seen yourself).
One small thing to note is that the iw dev ... set txpower ... command you have been using is fully functional but the GUI uses iw phy ... set txpower ... under the hood. In practice on the HaLowLink 2 (and all other current Morse Micro devices) this distinction doesn’t change anything but it is worth noting.
I apologise for the friction in the meantime and thank you for flagging it.
Cheers,
Lyall