Switch the active protocol and submit the wireless configuration

Safely release the old backend, load the protocol partition identity/channel/key, and project it as the active protocol only after the new backend is started and saved successfully.

Key Commitment

• There is only one active mesh backend at the same time.
• The switching protocol does not incorporate identities, NodeIds, keys or message deduplication spaces.
• Failure to start cannot show that the new protocol is available.

Drill down

• Protocol switching activity diagram
• Settings to backend timing