Three radios, three responsibilities.

Choose the radio for the job, not the feature list.

A requirement-to-radio matrix should state payload, frequency, latency, distance and infrastructure availability. If two radios cover the same requirement, define the primary path and when fallback is allowed.

A disabled radio should remain disabled.

Define observable states: production, commissioning, normal operation, maintenance and recovery. During normal operation firmware enables only the required path and applies timeouts. Wi-Fi or BLE should not remain discoverable indefinitely merely because they might be useful one day.

Include scanning, association, handshake, receive windows and failures in the energy budget. In difficult environments, connection cost is not one successful transmission but the real distribution of attempts.

Every radio is also a trust boundary.

• Use separate identities and keys where protocols require them.
• Do not transfer Wi-Fi credentials in clear text during commissioning.
• Authorize commands, not only the radio connection.
• Define device revocation, update and recovery.
• Keep essential data and functions locally available where possible.

Multiple radios do not automatically make good RF.

ELPM-S3LW combines ESP32-S3 and SX1262, but antenna, matching, enclosure, ground plane, cables and supply noise belong to the final product. Test desense and coexistence even when radios are not intentionally transmitting together.