- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
From what you write in the question I understand that you wrote 2 actions for the same AWS IoT Rule, which means that the data extracted by the rule from the message will be pushed to both actions, explaining the observed behaviour.
In order to have the MediaLab
data sent to the ast-medialab
asset and the WOWLIC
data sent to the ast-wowlic
asset you need to create 2 rules.
For Medialab, for example, the rule SQL should be similar to
select * from "dt/hansang/library/dvc-ctc-hansang-dev-medialab/sta"
and have a single action sending the data to the ast-medialab
asset.
You have something similar for the Wowlic topic
Hi. Massi has identified your problem. As I've said in answering your other question (https://repost.aws/questions/QUv5liAyUhSHe6G-SKjLRzTQ/iot-sitewise-to-iot-core-rule), you can use substitution templates so that one rule (with one action) could potentially work for every topic/asset/stream.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thank you for your answer. Is is right that you mean that I make ONE IoT Core Rule with ONE action to send data to Each IoT Sitewise ASSET? If I do this, when I made 1000 assets then should i made 1000 IoT Core rule?