Once data reaches AWS IoT Core (on cloud), you can use IoT Core Rules to send data to a service that can store data in a database (DynamoDB, Timestream etc). From there it should be easy to visualize the data using QuickSight, Grafana etc
@ArchitectureBytes I was able to do the whole activity and worked well for me except the 'ggcoredevice' status changes to 'Unhealthy' because the component 'aws.greengrass.clientdevices.mqtt.Moquette' turns to 'Broken' status. Can you also suggest the cleanup or the ways to stop billing when not in use. Is there a way to detach/ unmount / disassociate the devices to stop the billing during testing phase? However the Pub/Sub works fine.
For the 'aws.greengrass.clientdevices.mqtt.Moquette' broken status, please check the Greengrass Logs for error messages: /greengrass/v2/logs AWS Greengrass pricing: aws.amazon.com/greengrass/pricing/
I am getting the error while executing the client device sample/discovery.py code which is [ERROR] [2023-10-31T03:10:13Z] [000070000c38f000] [socket] - id=0x7f8795128e10 fd=21: timed out, shutting down. [ERROR] [2023-10-31T03:10:13Z] [000070000c38f000] [channel-bootstrap] - id=0x600001780bd0: Connection failed with error_code 1048. Connection failed with exception AWS_IO_SOCKET_TIMEOUT: socket operation timed out. All connection attempts failed [ERROR] [2023-10-31T03:10:13Z] [00007ff848fe0e80] [mqtt-client] - id=0x7f879490a400: Connection is not open, and may not be closed
Please check if you have done the following: Attach Policies: 13:47, Greengrass Service Role: 14:26, Associate Client Device to Core Device: 15:19, Setup Cloud Discovery & Configure Components: 15:58
Crisp and clear explanation for anyone to understand! Thanks a lot!
Can you please create part 2 of this video showing data storage from greengrass and visualization.
Once data reaches AWS IoT Core (on cloud), you can use IoT Core Rules to send data to a service that can store data in a database (DynamoDB, Timestream etc). From there it should be easy to visualize the data using QuickSight, Grafana etc
@ArchitectureBytes I was able to do the whole activity and worked well for me except the 'ggcoredevice' status changes to 'Unhealthy' because the component 'aws.greengrass.clientdevices.mqtt.Moquette' turns to 'Broken' status. Can you also suggest the cleanup or the ways to stop billing when not in use. Is there a way to detach/ unmount / disassociate the devices to stop the billing during testing phase? However the Pub/Sub works fine.
For the 'aws.greengrass.clientdevices.mqtt.Moquette' broken status, please check the Greengrass Logs for error messages:
/greengrass/v2/logs
AWS Greengrass pricing:
aws.amazon.com/greengrass/pricing/
I am getting the error while executing the client device sample/discovery.py code which is
[ERROR] [2023-10-31T03:10:13Z] [000070000c38f000] [socket] - id=0x7f8795128e10 fd=21: timed out, shutting down.
[ERROR] [2023-10-31T03:10:13Z] [000070000c38f000] [channel-bootstrap] - id=0x600001780bd0: Connection failed with error_code 1048.
Connection failed with exception AWS_IO_SOCKET_TIMEOUT: socket operation timed out.
All connection attempts failed
[ERROR] [2023-10-31T03:10:13Z] [00007ff848fe0e80] [mqtt-client] - id=0x7f879490a400: Connection is not open, and may not be closed
The core device is unhealthy
Please make sure that you have the necessary certificates/keys on the client device.
invalid connect return code 4, disconnecting
Connection failed with exception AWS_ERROR_MQTT_PROTOCOL_ERROR: Protocol error occurred. I have a issue
At what step do you get this error?
Pls make sure that you have the necessary certificates/keys on the client device.
@@ArchitectureBytes after that , i have bug : awscrt.mqtt.SubscribeError
Please check if you have done the following:
Attach Policies: 13:47, Greengrass Service Role: 14:26, Associate Client Device to Core Device: 15:19, Setup Cloud Discovery & Configure Components: 15:58
can i use greengrass for the e-RT3 device?
Yes, you should be able to use GreenGrass with this edge device.
WHERE TO GET JSON for device configuration?
Added the information to Video description. Pls take a look.