- Newest
- Most votes
- Most comments
Based on the information provided, it appears you're experiencing an issue where your AWS IoT TwinMaker scene rule isn't updating as expected, even though the data value itself is updating correctly through the SiteWise connector.
One common issue that can cause rules to fail is a data type mismatch between your rule configuration and the target asset property. When using AWS IoT SiteWise as a data source, ensure that the data type specified in your rule matches the data type of the SiteWise asset property.
For example, if your SiteWise asset property is defined as a DOUBLE type, but your rule is configured to use an Integer data type, the rule will not work correctly. You should verify that:
- The data type in your TwinMaker scene rule binding matches the data type of the corresponding SiteWise asset property
- If the property is a DOUBLE, ensure you're not inadvertently treating it as an Integer in your rule configuration
- Check that the value field in your rule uses the correct type specification
Review your rule bindings and compare them against the actual data types defined in your SiteWise asset properties to ensure they align properly. This mismatch is a frequent cause of rules failing to trigger or update correctly even when the underlying data is changing.
Sources
Troubleshoot an AWS IoT SiteWise rule action - AWS IoT SiteWise
Relevant content
- asked 4 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 10 months ago

Can confirm that in Sitewise the data type for current is double, however rule not working. When bound in annotation the live data updates.