- Le plus récent
- Le plus de votes
- La plupart des commentaires
Nucleus 2.6 will support interpolation in component configuration (currently it is only supported in the component recipe Lifecycle section). That will enable you to use the {iot:thingName}
variable in the mqttTopic
config. Unfortunately, this hasn't been released yet and I can't share a release date. But once that happens, this will definitely be the easiest way.
In the interim, you can either create individual Thing deployments containing only the aws.greengrass.telemetry.NucleusEmitter
component. Or, you can write your own custom bridge component that forwards messages from $local/greengrass/telemetry
to an MQTT topic of your choice. This component can read Nucleus ThingName information from environment variables.
This does not appear to be working yet as far as I can tell. I have a deployment that includes the NucleusEmitter component, as well as Nucleus 2.6.0. I have the configuration for mqttTopic
set to device/{iot:ThingName}/telemetry
. However using the MQTT test client subscribed to device/+/#
, I can see that the thing name is not being interpolated.
Contenus pertinents
- demandé il y a un an
- demandé il y a 9 mois
- Réponse acceptéedemandé il y a 7 mois
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 4 mois
Or, you can write your own custom bridge component that forwards messages from $local/greengrass/telemetry to an MQTT topic of your choice.
--> I'm try to write a custom bridge component that forwards messages. But My conpponent can't subcribe to topic $local/greengrass/telemetry. When I read document about mqtt topic it said that: "Topics that start with $ are reserved by AWS IoT Core. They are not supported for publishing and subscribing except for using the specific topic names defined by AWS IoT Core services (for example, the AWS IoT Device Shadow service)." (https://docs.aws.amazon.com/whitepapers/latest/designing-mqtt-topics-aws-iot-core/designing-mqtt-topics-aws-iot-core.pdf#mqtt-design-best-practices)