You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is how routes are defined in the deployment file:
"ModbusClientToIdentityTranslation": "FROM /messages/modules/ModbusClient/outputs/modbusOutput INTO BrokeredEndpoint(\"/modules/IdentityTranslation/inputs/input1\")",
"IdentityTranslationToIoTHub": "FROM /messages/modules/IdentityTranslation/outputs/* INTO $upstream"
I would like to add a property with the deviceId value in the message transformed by the ModbusClient and read this property in the IdentityTranslation module.
Code sample exhibiting the issue
Here are the snippets of the code in the two modules:
Context
"azure-iot-device": "^1.18.2",
"azure-iot-device-mqtt": "^1.15.4"
Description of the issue
I'm using IoT Edge to connect Modbus devices to IoT Hub and I'm trying to implement protocol + identity translation modules.
I started with the example here
I have two modules:
ModbusClient, for the protocol translation, in C#
IdentityTranslation, in NodeJS
Here is how routes are defined in the deployment file:
I would like to add a property with the deviceId value in the message transformed by the ModbusClient and read this property in the IdentityTranslation module.
Code sample exhibiting the issue
Here are the snippets of the code in the two modules:
When the message arrives at the IdentityTranslation module, Properties are empty and I cannot get the deviceId value.
Console log of the issue
This is the content of the received message
Other references
I found this old issue Message properties seem to get lost after routing through edgeHub related to the python sdk that has been fixed. Maybe is there a similar problem on nodejs (or .Net)?
The text was updated successfully, but these errors were encountered: