Interact with local IoT devices

This page was generated from content adapted from the AWS Developer Guide

Client device components

  • NoteSeveral AWS-provided components depend on specific minor versions of the Greengrass nucleus. Because of this dependency, you need to update these components when you update the Greengrass nucleus to a new minor version. For information about the specific versions of the nucleus that each component depends on, see the corresponding component topic. For more information about updating the nucleus, see Update the AWS IoT Greengrass Core software (OTA).

Connect client devices to core devices

  • ImportantThe core device must run Greengrass nucleus v2.2.0 or later to support client devices.

  • NoteWe recommend that you deploy only one MQTT broker component. The MQTT bridge and IP detector components work with only one MQTT broker component at a time. If you deploy multiple MQTT broker components, you must configure them to use different ports.

Relay MQTT messages between client devices and AWS IoT Core

  • NoteThe MQTT bridge uses QoS 1 to publish and subscribe to AWS IoT Core, even when a client device uses QoS 0 to publish and subscribe to the local MQTT broker. As a result, you might observe additional latency when you relay MQTT messages from client devices on the local MQTT broker to AWS IoT Core. For more information about MQTT configuration on core devices, see Configure MQTT timeouts and cache settings.

Interact with and sync client device shadows

  • Note The shadow manager component doesn't sync shadows with AWS IoT Core by default. You must configure the shadow manager component to specify which client device shadows to sync.

  • Note You can use these configuration examples in the AWS IoT Greengrass console. If you use the AWS IoT Greengrass API, the merge configuration update requires a serialized JSON object, so you must serialize the following JSON objects into strings. For more information, see Update component configurations.

Last updated