iot connected device stuck on queued

Hello, can you confirm if you're trying to do deployments on an associated client device as part of the Greengrass group deployment? If so, it is not possible today. Only the core devices (where Nucleus is running) have out of the box deployment capabilities where the device can receive and process Greengrass deployments.

Based on the information provided, it seems you're experiencing an issue where your IoT connected device deployment is stuck in a queued state, while the Greengrass core device receives the deployment successfully. This can be a frustrating situation, but there are several steps we can take to troubleshoot the problem.

First, it's good that you've already verified network connectivity between the core and the connected device, and that you've set the permissions for IoT and Greengrass to be open. These are important initial steps in troubleshooting.

Since you mentioned that the IoT device can process direct IoT job deployments but gets stuck when deploying to the Greengrass group, the issue likely lies in the communication or configuration between the connected device and the Greengrass core. Here are some areas to investigate:

1. Check the Greengrass logs on the core device for any errors or warnings that might indicate why the deployment isn't being processed for the connected device. The logs might reveal issues with subscription, authentication, or component configuration.

2. Verify that the client device auth component on the Greengrass core is properly configured. This component is responsible for authenticating and authorizing client devices. Make sure it's deployed and running correctly on the core.

3. Double-check the cloud discovery configuration on the core. Ensure that the connected device is properly associated with the core device and that all necessary permissions are in place.

4. Review the MQTT connection between the connected device and the core. Even though you can run the basic_discovery.py script successfully, there might be issues with the MQTT connection when it comes to deployments. Check for any MQTT connection errors on both the core and the connected device.

5. Verify that the connected device is using the correct certificates and private key for authentication with the Greengrass core. Mismatched or expired certificates can cause connection issues.

6. Check that the Greengrass core device has the necessary policies to communicate with the connected device and vice versa. While you've set open permissions for IoT and Greengrass, make sure there are no conflicting policies that might be restricting communication.

7. Ensure that the connected device is subscribed to the correct MQTT topics for receiving deployment notifications from the Greengrass core.

8. If possible, try restarting both the Greengrass core software on the core device and the client software on the connected device. Sometimes, a fresh start can resolve communication issues.

If after checking these areas the issue persists, you may need to dive deeper into the logs and configurations of both the core and connected devices to identify any misconfigurations or compatibility issues. Additionally, consider checking if there are any version mismatches between the core and client software that could be causing communication problems.

Remember that troubleshooting IoT and Greengrass deployments can be complex due to the many moving parts involved. Systematic checking of each component and its configuration is often necessary to pinpoint the root cause of such issues.

Sources
Troubleshooting AWS IoT Greengrass V2 - AWS IoT Greengrass
Troubleshooting client devices - AWS IoT Greengrass