So just to clarify, you've added an integration layer on top of MQTT so that MCUs can publish to a topic (for external actions) and subscribe to a topic (for MCU-driven actions)?
1. Do you have an "unexpected exit" strategy that would allow users to use their own broker, and self-host your integration layer?
2. How does the firmware/infra currently handle failed connections to MQTT? Are you using LWT?
3. Are you using retained messages and/or QoS to ensure subscribers understand the correct "state of the world" after a reconnection?
4. Does the MCU firmware support queueing messages on its own for delivery after a disconnection is resolved?
So just to clarify, you've added an integration layer on top of MQTT so that MCUs can publish to a topic (for external actions) and subscribe to a topic (for MCU-driven actions)?
1. Do you have an "unexpected exit" strategy that would allow users to use their own broker, and self-host your integration layer?
2. How does the firmware/infra currently handle failed connections to MQTT? Are you using LWT?
3. Are you using retained messages and/or QoS to ensure subscribers understand the correct "state of the world" after a reconnection?
4. Does the MCU firmware support queueing messages on its own for delivery after a disconnection is resolved?