- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
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'
Relevanter Inhalt
- Wie veröffentliche ich MQTT-Nachrichten von meinem Gerät auf AWS IoT Core, wenn ich Python verwende?AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr