Duplicate MQTT messages being received at DynamoDB

Question

So I have some sensors that are sending MQTT data using the IOT Core  to DynamoDB. However I note that there are always 2 messages(duplicates). 
I am using Select for the topic, set up a Rule as was needed,etc. ITs all working fine, except for the duplicates. I looked through the questions but didn't find an answer.
Any suggestion to find the root cause appreciated. Regards

6/11/22 additional data 
Some additional info might be useful so I have provided it here.

Rule query statement The source of the messages you want to process with this rule.

Extract below.............

SELECT state.reported.value as state_reported_value FROM '#' Using SQL version 2016-03-23 Actions Actions are what happens when a rule is triggered.

Insert a message into a DynamoDB table

Extract end.................

Hope this helps in directing me. Regards

Accepted Answer

Hi fixingthingsguy. The issue is likely related to using a wildcard for the topic in the FROM statement of the rule. The state.reported.value property could be found in the message of more than one topic. Even amongst shadow topics and shadow documents.

In this case, it will likely appear in the shadow document for both the /update topic when the device publishes the new value and in the shadow document of the /updated/accepted topic when IoT Core responds. You probably want to change the FROM statement to use $aws/things/+/shadow/update if you're using the Classic shadow or $aws/things/+/shadow/name/<shadowName>/update if you're using a named shadow.

In this case, it will likely appear in the shadow document for both the [/update](https://docs.aws.amazon.com/iot/latest/developerguide/device-shadow-mqtt.html#update-pub-sub-topic) topic when the device publishes the new value and in the shadow document of the [/updated/accepted](https://docs.aws.amazon.com/iot/latest/developerguide/device-shadow-mqtt.html#update-accepted-pub-sub-topic) topic when IoT Core responds. You probably want to change the **FROM** statement to use `$aws/things/+/shadow/update` if you're using the Classic shadow or `$aws/things/+/shadow/name//update` if you're using a named shadow.

Answer

Greg_B. Thanks very much. I've been wracking my brains on this one. I just tested using your suggestion and the duplicates are not occurring.  So for any future user who sees the same problem, here's the before and after SELECT using Classic Shadow.
BEFORE:
SELECT state.reported.value as state_reported_value FROM '#'
AFTER Greg_B's suggestion:
SELECT state.reported.value as state_reported_value FROM '$aws/things/+/shadow/update'

Duplicate MQTT messages being received at DynamoDB

相關內容