Skip to content

IoT Core Message routing Rules does not receive topic event, but can received connectivity events.

0

Hi, I am using MQTT test client to subscribe wildcard topic "node/+/#" that same as Rule, can received "node/silabs19a270/config" event. IoT Core Message routing Rules does not, but can received connectivity events. Any idea? Thanks!

asked 2 years ago344 views

3 Answers
1

Hey..

Check your IoT Rule SQL query. It should match the topic correctly. For example, to capture messages from "node/silabs19a270/config", your rule SQL should be:

SELECT * FROM 'node/+/config'

Make sure the rule is enabled and the correct actions (like Lambda, SNS, etc.) are set for routing, ensure IAM permissions allow IoT to route the message correctly.

EXPERT

answered 2 years ago

0
Accepted Answer

Hi All, Open IoT Core log, then finally found the error: { "timestamp": "2024-09-09 05:06:37.355", "logLevel": "ERROR", "traceId": "69143cb2-7818-8f0f-a21b-685a1a9addf1", "accountId": "xxxxxxxxxxxxxxxxxx", "status": "Failure", "eventType": "RuleExecution", "clientId": "silabs19a024", "topicName": "node/silabs19a270/config", "ruleName": "amzpt_iot_reporting", "principalId": "94795544f643e3ac4d6ae3ab6c9288106ba9a15f94ff74d517876fe172235fde", "reason": "JsonParseError", "details": "Error parsing message for rule 'amzpt_iot_reporting'" }

answered 2 years ago

0

Hi Kranthi,

The SQL statement is SELECT *, topic() as topic FROM 'node/+/#' It is work on MCU device 1.5 years ago; Now, I am trying new MCU of another product.

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.