The lastConnection property of the Thing does not update
User Actions
The user must perform the following actions when faced with this error:
• Check whether the Thing was recreated with the same
modelNumber and
serialNumber but with a new Thing name. If so, the
ThingNameStash must be cleared. Follow the instructions in
Invoking ClearCacheEntry for ThingNameStash.
• Check whether more than on Thing exists with the same
modelNumber and
serialNumber. An eMessage agent must be mapped to a single Thing, using the
modelNumber and
serialNumber properties. Either delete one Thing or the other, or modify the
modelNumber and
serialNumber on one of the Things to produce a unique combination of
modelNumber and
serialNumber. Next, if the asset is not communicating, you need to clear the
ThingNameStash. Follow the instructions in
Invoking ClearCacheEntry for ThingNameStash.
• Check whether the identifier is set on the Thing. If the identifier is set, remove it. The eMessage Connector does not support identifiers.
• Check that the modelNumber and serialNumber properties are correctly set on the Thing. The eMessage Connector uses the values of these properties to locate the correct Thing and cannot communicate if these setting are incorrect.
If the
ThingNotFoundError event was sent to the Connection Services Hub, refer to
Event Notifications for more information.
• Verify that the token property of the Thing is set to match the token provided by the agent. For information about resetting a token, refer to
Resetting a Token.
• Check if any advisory events have been sent to the Connection Services Hub. For more information, refer to
Event Notifications.
• Check the agent log and verify that everything has been configured correctly. If possible, enable debugging log messages at the edge for the agent.
Administrator Actions
In addition to the steps that the user performs, the administrator must perform the following steps when faced with this error: