Troubleshooting an AWS IoT SiteWise rule action - AWS IoT SiteWise

Troubleshooting an AWS IoT SiteWise rule action

To troubleshoot your AWS IoT SiteWise rule action in AWS IoT Core, you can do one of the following procedures:

  • Configure CloudWatch Logs

  • Configure a republish error action for your rule

Then, compare the error messages with the errors in this topic to troubleshoot your issue.

Configuring AWS IoT Core logs

You can configure AWS IoT to log various levels of information to CloudWatch Logs.

To configure and access CloudWatch Logs

  1. To configure logging for AWS IoT Core, see Monitoring with CloudWatch Logs in the AWS IoT Developer Guide.

  2. Navigate to the CloudWatch console.

  3. In the navigation pane, choose Log groups.

  4. Choose the AWSIotLogs group.

  5. Choose a recent log stream. By default, CloudWatch displays the most recent log stream first.

  6. Choose a log entry to expand the log message. Your log entry might look like the following screenshot.

    
              CloudWatch "AWS IoT Logs" screenshot.
  7. Compare the error messages with the errors in this topic to troubleshoot your issue.

Configuring a republish error action

You can configure an error action on your rule to handle error messages. In this procedure, you configure the republish rule action as an error action to view error messages in the MQTT test client.

Note

The republish error action outputs only the equivalent of ERROR level logs. If you want more verbose logs, you must configure CloudWatch Logs.

To add a republish error action to a rule

  1. Navigate to the AWS IoT console.

  2. In the left navigation pane, choose Act and then choose Rules.

  3. Choose your rule.

  4. Under Error action, choose Add action.

  5. Choose Republish a message to an AWS IoT topic.

    
              AWS IoT Core "Select an action" page screenshot with the Republish action
                highlighted.
  6. Choose Configure action at the bottom of the page.

  7. In Topic, enter a unique topic (for example, sitewise/windfarm/rule/error). AWS IoT Core will republish error messages to this topic.

  8. Choose Select to grant AWS IoT Core access to perform the error action.

  9. Choose Select next to the role that you created for the rule.

  10. Choose Update Role to add the additional permissions to the role.

  11. Choose Add action.

    Your rule's error action should look similar to the following screenshot.

    
              AWS IoT Core "Rule" page Republish error action screenshot.
  12. Choose the back arrow in the upper left of the console to return to the AWS IoT console home.

After you set up the republish error action, you can view the error messages in the MQTT test client in AWS IoT Core.

In the following procedure, you subscribe to the error topic in the MQTT test client. In the MQTT test client, you can receive your rule's error messages to troubleshoot the issue.

To subscribe to the error action topic

  1. Navigate to the AWS IoT console.

  2. In the left navigation page, choose Test to open the MQTT test client.

  3. In the Subscription topic field, enter the error topic that you configured earlier (for example, sitewise/windfarm/rule/error) and choose Subscribe to topic.

    
              AWS IoT Core "MQTT client" page screenshot with the "Subscribe to topic" button
                highlighted.
  4. Watch for error messages to appear and then expand the failures array in any error message.

    Next, compare the error messages with the errors in this topic to troubleshoot your issue.

Troubleshooting issues

Use the following information to troubleshoot rule issues.

Error: Member must be within 604800 seconds before and 300 seconds after the current timestamp

Your timestamp is older than 7 days or newer than 5 minutes, compared to current Unix epoch time. Try the following:

  • Check that your timestamp is in Unix epoch (UTC) time. If you provide a timestamp with a different timezone, you receive this error.

  • Check that your timestamp is in seconds. AWS IoT SiteWise expects timestamps split into time in seconds (in Unix epoch time) and offset in nanoseconds.

  • Check that you're uploading data that is timestamped no later than 7 days in the past.

Error: Property value does not match data type <type>

An entry in your rule action has a different data type than the target asset property. For example, your target asset property is a DOUBLE and your selected data type is Integer or you passed the value in integerValue. Try the following:

  • If you configure the rule from the AWS IoT console, check that you chose the correct Data type for each entry.

  • If you configure the rule from the API or AWS Command Line Interface (AWS CLI), check that your value object uses the correct type field (for example, doubleValue for a DOUBLE property).

Error: User: <role-arn> is not authorized to perform: iotsitewise:BatchPutAssetPropertyValue on resource

Your rule isn't authorized to access the target asset property, or the target asset property doesn't exist. Try the following:

  • Check that your property alias is correct and that you have an asset property with the given property alias. For more information, see Mapping industrial data streams to asset properties.

  • Check that your rule has a role and that the role allows iotsitewise:BatchPutAssetPropertyValue permission to the targeted asset property, such as through the target asset's hierarchy. For more information, see Granting AWS IoT the required access.

Error: iot.amazonaws.com is unable to perform: sts:AssumeRole on resource: <role-arn>

Your IAM user isn't authorized to assume the role on your rule.

Check that your IAM user is allowed iam:PassRole permission to the role on your rule. For more information, see Pass role permissions in the AWS IoT Developer Guide.

Info: No requests were sent. PutAssetPropertyValueEntries was empty after performing substitution templates.

Note

This message is an INFO level log.

Your request must have at least one entry with all of the required parameters.

Check that your rule's parameters, including substitution templates, result in non-empty values. Substitution templates can't access values defined in AS clauses in your rule query statement. For more information, see Substitution templates in the AWS IoT Developer Guide.