Questions tagged with AWS IoT SiteWise
Content language: English
Sort by most recent
Hi,
I'm working on a test project involving Amazon Monitron Starter Kit and was wondering if there was a straight forward way to export data (measurements for vibration and temperature) collected and displayed on Amazon Monitron Dashboard out to Grafana?
I've tried using the live data export stream but didn't get too far.
I also couldn't find an option within Amazon Managed Grafana to add Monitron as a direct Data Source.
Any guidance on this would be much appreciated.
Thanks in advance.
Hi,
I have a customer who wants to store time series data (industrial IoT) in Redshift. Then query/push that data to IoT SiteWise for equipment monitoring.
My initial thought is - IoT SiteWise is already a time series data store with Hot & Cold Tiers, so it does not make sense to use Redshift as a data store. Instead they should use Redshift downstream of SiteWise. What do you folks think? Also, would appreciate some reasons for why Redshift is a good or bad candidate in this case.
Thanks!
I can't delete my workspace in AWS Twin Maker because I get the error "Workspace has syncJobs. Delete all resources in the workspace.". In the "Entity model sources" tab I have a IoT SiteWise source connected that is in "deleting" status. The "disconnect" button is unavailable. Can you help me with this?
I am trying to set a Custom Message Attribute on an IoT Sitewise Alarm to indicate which device name is generating an alarm. From what I can tell, the normal usage of the Custom Attribute is to provide a fixed default value like the other attributes on the Sitewise model. If there are multiple devices sending data to Sitewise from the IoT Core Sitewise rule, is there a way to provide that dynamic value as the custom message attribute. Here is the SQL that is sending the DeviceName to Sitewise on the IoT Core rule:
```
SELECT clientId() as DeviceName, state.reported.payload.temperature as temperature, state.reported.payload.humidity as humidity, state.reported.payload.VOC as VOC, state.reported.payload.CO2 as CO2 FROM '$aws/things/+/shadow/update'
```
I tried setting the DeviceName as a measurement in Sitewise, but I cannot link the measurement value to the custom message attribute value.
Thanks!
Hello,
I have deployed Greengrass as a Docker container from the official Docker Hub page: **amazon/aws-iot-greengrass:2.5.3-0**
I run it and deployed on it basics Greengrass components, it runs fine, and deployed also IoT SiteWise most recent components.
But the component SiteWiseEdgeCollectorOpcua is logging this error when it starts:
```
OpcUaManagedConnection - {"message":"Failed to start OPC-UA Connection for Source (OPC-UA): Failed to obtain Secret from Greengrass IPC"}
```
I am pretty sure the rest of the IoT SiteWise deployment is correct, since it's quite basic, and I already deployed the same things previously on a Linux deployed Greengrass and it worked fine.
I tried to understand what this could be related.
For sure it is not related with the permissions given to the IAM Role used by Greengrass, since it currently has all permissions to operate on my AWS account just for debugging this.
To avoid networking issue i also run the container with the option `--network host` so that it can open all needed local ports and connections.
My only suspect right now is the fact that I see the docker version of Greengrass is not updated since 1 year!
Is it supposed to work? Maybe it is not compatible with latest Greengrass components or SiteWise most recent ones?
Does someone know the solution to this?
Let me know in case I need to provide more information.
Thank you very much in advance for your support!
I am interested in managing a group of Raspberry Pi devices through IoT Sitewise and alerting on sensor data processed by the devices. What is not clear to me is how to report the device names into Sitewise through IoT Core. Right now, my devices are given unique names through the IoT ClientID (ex. RaspberryPi001, RaspberryPi002, etc.) and I am routing the ClientID and sensor payload data to Sitewise through a rule in IoT Core. However, there does not appear to be a way to add the ClientId as a measurement to the Sitewise model. The examples I see in the Sitewise documentation all have the device name added as a hardcoded attribute. But how does that approach work when you have potentially a fleet of devices reporting into Sitewise? Also, I would like to add the device name to the Alarm message so the recipient can know which device is the active alarm state.
I am trying to use /ClientID/ as the property alias in the IoT Core Sitewise rule with the following query, and then add ClientId as a measurement in the Sitewise Asset Model. But I am not receiving any values on the ClientID measurement in Sitewise.
SELECT clientId() as ClientId, state.reported.payload.temperature as reported.temperature, state.reported.payload.humidity as reported.humidity, state.reported.payload.VOC as reported.VOC, state.reported.payload.CO2 as reported.CO2 FROM '$aws/things/+/shadow/update'
In summary, I am looking for a way to add the IoT device name to the Sitewise model or asset and alarm message. Thanks!
Is it possible to alias the attributes of an IoT Sitewise asset, so that we can update the attributes dynamically for many devices ?
Say I have many IoT things , modelled as assets, iot-car. Cars have a 'color' attribute, string, which is updated very rarely, and so isn't really timeseries data, but a car an be painted once per year maybe.
I know I can manually change the attribute via the cli or console, and I know I can automatically update it from an IoT Rule if I specify the Asset ID and the property ID (and I can see that the 'color' property ID is the same for all my different cars).
Is it possible, using aliasing/substitution/similar, to have cars automatically update themselves, without requiring a different rule per car ? As I have to specify the property AND asset ID in the rule it seems like I can't.
Hi team,
We have been using lambda function for several months without any issues. Just 2 days ago suddenly I started to get "Task timed out" errors in my CloudWatch logs and as time goes they increase to the point where the function does not work anymore. So at beginning there are only a few happening during the first hours and as time goes on they increase to the point where the function does not work anymore. None of the settings for our Lambda function has changed or the data coming in from IOT sensors which via a rule it invokes the lambda function. So there are about 150 sensors streaming every 10-15 seconds and as each value comes in the AWS IoT Core rule invokes the lambda function that reads the value and processes it. The time out configuration is set to 60 seconds and for some reason it reaches that value. The Lambda functions does a few things. It uses AWS SDK to write to AWS Sitewise and also it writes to AWS Timestream. I have tried to set some print statements for each line in my code so I can see where the issue is happening. But the problem is when there is a task timeout it never shows any of the print outputs on the CloudWatch logs. I have looked to see if there was any updates to Lambda or Timestream but I did not find anything. I have also seen some suggestions to increase the memory but looking at the logs it does not even get close to max memory. The one thing I find very strange is that on the CloudWatch logs I can see the three events Start, End and report. The timestamp of the start is actually only about 2 seconds apart from the end and report event which says "Task timed out after 62.01 seconds". If the start and end of the invocation is about 2 second apart than how did it read the max timeout of the function which is set to 1 min. Also I have seen some articles about enabling X-Ray tracing on the function but so far I have not got any valuable information from it. I have posted the logs from CloudWatch for one of the many "Task timed out" logs below. Please let me know if I have missed anything or something I can try to fix the issue or investigate the cause better. Any help woolen be appreciated.
Thank you for your time,
Shervin

Hi ! Using SiteWise portals I can see an overview of my data in a dashboard, but I haven't been able to find where that data is being stored. I would like to find that data to generate a PDF report. Thanks!
Starting today, [AWS IoT TwinMaker](https://aws.amazon.com/iot-twinmaker/) will support asset synchronization with [AWS IoT SiteWise](https://aws.amazon.com/iot-sitewise/), making it easier for AWS IoT SiteWise customers to bring their assets and asset models into AWS IoT TwinMaker.
Now, customers can start using AWS IoT TwinMaker without having to recreate AWS IoT SiteWise assets and asset models, and any updates will be automatically synced. There is no charge for entities synced from AWS IoT SiteWise. If synced assets and asset models are no longer needed, customers can simply delete the sync setup.
Customers can enable the feature in the AWS IoT TwinMaker console by providing a workspace to host assets and asset models from AWS IoT SiteWise. To learn more, visit our [developer guide](https://docs.aws.amazon.com/iot-twinmaker/latest/guide/tm-sw-asset-sync.html) and [API reference](https://docs.aws.amazon.com/iot-twinmaker/latest/apireference/Welcome.html).
This feature is available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Europe (Frankfurt), and Europe (Ireland).
I followed step by step the tutotrial https://docs.aws.amazon.com/iot-sitewise/latest/userguide/ingest-data-from-iot-things.html but when I tried to do the **step 8** of section "**Running the device client scrip**" I received the error "Errno -2: Name or service not known". Apparently the problem is in **mqttClient.connect()**, but I haven't been able to fix it in a long time. Any help is welcome! Thanks!
I'm using Grafana Bitname image from catalog aws ec2 and I have configured Grafana and roles, policies to access Twinmaker and vizualize fetures. But I have this error on the screen below. Someone would have idea how figure out this?
