1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hello,
The only way to achieve what you're looking for is for the ultimate destination to send a response back to acknowledge receipt. For example, sending an MQTT message on /send from the device, then a lambda in the cloud sends another message on /acknowledge which the application on the device has subscribed to. This validates that the message is truly received by your cloud application and the device side can forget about the message.
Cheers, Michael
Contenuto pertinente
AWS UFFICIALEAggiornata 10 mesi fa- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks Michel, I agree that in the end this is the only way to be absolutely sure. I have seen that when the MQTT connection is lost greengrass shows in the log [INFO] (Thread-5) com.aws.greengrass.mqttclient.AwsIotMqttClient: Connection interrupted while when the connection returns it shows [INFO] (Thread-5) com.aws.greengrass.mqttclient.AwsIotMqttClient: Connection resumed. Do you know if there is any way for a component to know these circumstances apart from monitoring the greengrass log ? Is there any way for a component to have an IPC subscription that informs it whether the MQTT connection is active or not ?
Sorry, but no, those disconnect/connect events are not exposed in any way for you to use.