I am now thinking that the device on boot-up should subscribe to a unique settings endpoint (something like /s-(device serial number)).Should then send the information packet.The server should then process this packet into the database, and if a configuration is needed to be sent to the device publish it to /s-(device serial number)There would need to be a delay in the device shutting down after sending the packet, to wait for a potential response being published to /s-(device serial number). Something like 10 seconds.While this sounds like it would work in theory, how reliable will this be once scaled? There is the potential for hundreds of thousands of devices... Can an MQTT message sit on the queue for a long period before being sent (longer than the shutdown delay)?It sounds like a scaling nightmare to me....Is there a better solution??
To learn more about MQTT please visit http://mqtt.org
You received this message because you are subscribed to the Google Groups "MQTT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mqtt+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mqtt/d6c49539-0bb8-4873-a7fb-3f5ba053046a%40googlegroups.com.