I found this series a HUGE help alongside the very disconnected AWS documentation/tutorials. just seeing someone actually do the things in realtime and figuring out what they need there and then is great, rather than just using the tutorials which seem to always end up with you stopping a step to start following a chain of definitions deeper and deeper till you start to forget what you were even trying to do... so thanks very much for these videos. a year out and they're still really helpful!
Very detail, in-depth, and easy to understand from A-Z on this series. Thank you. Looking forward to your next series. If you can show how to connect Home Assistant to Greengrass, that would be Awesome as the community for Home Assistant is huge. Another suggested Series might be Modbus TCP to greengrass or NodeRed to Greengrass. Thank you.
Thanks for the feedback, there is a nodered community component to run nodered within greengrass so that you can deploy the flows remotely. I will have to look into Home Assistant as currently i use NodeRed at home. Thanks for the suggestions i will put them on the list.
Hey your videos are so much helpful for me and my team... Could you please create new video on how can we connect aws IoT greengrass core to aws lambda function.
Great series! I was struggling with Greengrass and AWS workshops to make it work on my Pi, but your series made things so much clearer in no time. There's one thing that I got difficult to understand and make it work. How do you continuously publish data through MQTT to the IoT core for processing or logging in DynamoDB or S3. I got a DHT11 temperature and moisture sensor connected to Pi but I still don't know how to use Streams to push the data to AWS IoT without using callback or sending requests to components. Maybe something you could touch upon in the next video.
1. Using nearly exact same setup I still get authorization issues with a named shadow, not sure how to further debug. 2. Can you show how one would update the unnamed shadow? If I just leave shadow name blank will it assume the classic shadow?
It should just be a case of making sure that the topics for the classic shadow are added to the recipe file. I will check on monday and update the video and reply here if i hit an issue.
@@awsomeiot1448 thanks, I'll keep trying on the authorization for named shadow using your example. Was able to get it going while using an empty string for shadowname in the python script, but it did not appear to update the classic shadow in the AWS console, synchronization was enabled on shadowmanager.
