2 Answers
- Newest
- Most votes
- Most comments
0
Hi scriobhneoir,
perhaps you can change the color attribute to a measurement. Then you can update the color with a property alias.
In case you want to modify the attribute via IoT Core you don't need one rule per car. You can use one rule and put the assetId and propertId into the payload for example:
{
"assetId": 1234,
"propertId: 5678,
"color": "gray"
}
Then you can use substitution templates in the IoT rule action, for example ${propertId}
or ${assetId}
.
Cheers,
Philipp
0
Hi scriobhneoir,
does this help: Mapping industrial data streams to asset properties?
Cheers,
Philipp
Relevant content
- asked a year ago
- asked 7 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
Hi Philipp, thanks for the link, though it doesn't help.
I read through all (I think) of the AWS docs related to ingesting sitewise data through IoT rules. The links there explain how to alias properties, but not attributes.
I would like to alias attributes, which are the non-time-series data associated with an asset. You can send data to them with an IoT rule, but you have to specify the exact asset ID and property ID. To use my example above, if I have two cars, with asset ID 1234 and another with 5678, I would have to create specific IoT rules targeting each asset, and new rules for any new asset, which isn't scalable.
Is there a way to use the substitution template to set to the asset ID for adding attributes to an asset ?
Hi Philipp, any update ?