Description

When using --set to change power configuration values on a device with the ROUTER role, the CLI reports success but the values are silently ignored/overridden by role-enforced defaults.

Steps to Reproduce

1. Set device to ROUTER role: meshtastic --set device.role ROUTER
2. Attempt to disable light sleep: meshtastic --set power.ls_secs 0
3. CLI reports: "Set power.ls_secs to 0" and "Writing power configuration to device"
4. Verify the value: meshtastic --get power.ls_secs
5. Returns: power.ls_secs: 86400 (not 0)

Expected Behavior

The CLI should either:

• Warn that this value will be overridden by the current device role, or
• Refuse to write the value with an explanatory error

Actual Behavior

CLI reports success, device reboots, but the value reverts to the role-enforced default (86400 for ROUTER). This is confusing and leads to wasted debugging time.

Environment

• meshtastic CLI version: 2.7.5
• Firmware: 2.7.16
• Hardware: ESP32
• OS: macOS

Additional Context

The ROUTER role forcing is_power_saving is documented behavior, but users have no way to know from the CLI that their settings are being ignored. Related firmware issue: meshtastic/firmware#2203