@Jessica Bradford yeah this is actually a pretty well-understood pattern and the good news is BLE doesn't have a symmetric TX power requirement baked into the spec — the two sides are genuinely independent on that front. Connection parameters are negotiated, but TX power isn't part of that negotiation in any mandatory sense. Each side just controls its own output.
The place where asymmetry can bite you is on the uplink vs downlink RSSI balance. If your peripheral is pulling back TX significantly, the base station is receiving a weaker signal even though it can blast back at full power. What saves you here is that the MultiNav Pro+ is built around a high-sensitivity front end — the receiver sensitivity is the key spec on the base station side, and that's where RFOXiA has done a lot of the engineering work. So a lower-power peripheral paired with a high-gain antenna and sensitive receiver at the base should hold a reasonable link budget.
The STM32WB07 stack on the module side doesn't enforce any symmetric power relationship either — it's not going to fight you during connection setup. You can set the peripheral TX power independently in firmware. Worth pulling the firmware repo and looking at how the TX power control is exposed there since Moamen's been pretty explicit about that in the source — github.com/RFOXiA/MultiNav-Pro-Long-Range-BLE-Module-Firmware-STM32WB07.
The thing I'd actually watch for in your setup is connection interval and the peripheral's ability to respond reliably at low power — if you're also duty cycling aggressively on the peripheral side alongside the reduced TX, that's where you can get instability, not the power asymmetry itself.
