andygrillo
commented
3 years ago Doesnt the MQTT broker automatically track devices that are connected to it ? isnt there an inbuilt heartbeat that is used by MQTT which we can simply read from node-red ?
On Thu, 10 Dec 2020 at 15:40, John Walicki notifications@github.com wrote:
Today, the sensor sends a MQTT message every second that contains accelerometer data. If we're getting data, we know the board is alive. If we implement an edge based STA / LTA algorithm, the sensor will process the accelerometer data at the edge. If there are no earthquakes, we might not hear from a board for weeks/months. We won't know its alive.
When we implement STA/LTA edge processing, we should also implement a heartbeat MQTT topic to replace the MQTT data. It does not need to be every second. The MQTT message would only need to send 1 byte of data. We can derive the macaddress from the device id (part of the Watson IoT headers). In the cloud, we could either update the Cloudant record with a last heartbeat timestamp. The OpenEEW dashboard could read that to indicate status. There's a Watson IoT Last Event rest api but the dashboard would need to know those credentials. I could find an example of that implementation too.
Maybe once a minute - would be 1440 messages/day Maybe once a hour - would be 24 messages/day
If we're worried about the IBM Cloud Watson IoT Platform lite tier, its limited to 200MB/month so we would want to keep our heartbeats small / sufficiently infrequent.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/openeew/openeew-sensor/issues/57, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABP5GHLYKHL5JWNIPQAHAFDSUE56PANCNFSM4UVURKEQ .
-- Andres Meira m +52 (55) 12246468 skype andresmeira
johnwalicki
Today, the sensor sends a MQTT message every second that contains accelerometer data. If we're getting data, we know the board is alive. If we implement an edge based STA / LTA algorithm, the sensor will process the accelerometer data at the edge. If there are no earthquakes, we might not hear from a board for weeks/months. We won't know its alive.
When we implement STA/LTA edge processing, we should also implement a heartbeat MQTT topic to replace the MQTT data. It does not need to be every second. The MQTT message would only need to send 1 byte of data. We can derive the macaddress from the device id (part of the Watson IoT headers). In the cloud, we could either update the Cloudant record with a last heartbeat timestamp. The OpenEEW dashboard could read that to indicate status. There's a Watson IoT Last Event rest api but the dashboard would need to know those credentials. I could find an example of that implementation too.
Maybe once a minute - would be 1440 messages/day Maybe once a hour - would be 24 messages/day
If we're worried about the IBM Cloud Watson IoT Platform lite tier, its limited to 200MB/month so we would want to keep our heartbeats small / sufficiently infrequent.