AWS+Intel: Smart Greenhouse Demo
•
5 likes•1,762 views
This document discusses using AWS IoT to connect devices in an Intel greenhouse. It describes how sensors can collect data and send it to AWS IoT via MQTT. Rules in AWS IoT can then route data to services like DynamoDB for storage and Kinesis for analytics. Actuators like misters or fans can be automatically controlled based on sensor readings using device shadows to ensure reliable commands. AWS IoT provides device management, authentication, and rules processing to integrate physical devices into cloud applications.
More Related Content
What's hot
Viewers also liked
Viewers also liked (20)
Similar to AWS+Intel: Smart Greenhouse Demo
Similar to AWS+Intel: Smart Greenhouse Demo (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
AWS+Intel: Smart Greenhouse Demo
- 1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved. AWS Loft NYC Mackenzie Kosut Principal Startup Evangelist @ AWS @mkosut
- 2. Heart monitoring implants Biochip transponders on farm animals Electric clams in coastal waters Automobiles with built-in sensors DNA analysis devices for environmental/food/pathogen monitoring Field operation devices that assist firefighters in search and rescue operations Internet of Things?
- 3. AWS IoT DEVICE SDK Set of client libraries to connect, authenticate and exchange messages DEVICE GATEWAY Communicate with devices via MQTT, HTTP, Websockets AUTHENTICATION AUTHORIZATION Secure with mutual authentication and encryption RULES ENGINE Transform messages based on rules and route to AWS services AWS Services - - - - - 3P Services DEVICE SHADOW Persistent thing state during intermittent connections APPLICATIONS AWS IoT API DEVICE REGISTRY Identity and management of your things
- 4. Intel Greenhouse w/ AWS IoT
- 6. + - + - + - Sensors Actuators Intel Edison AWS IoT SDK Wireless Router AWS IoT Rules Engine Intel Greenhouse w/ AWS IoT
- 7. + - + - + - Sensors Actuators Intel Edison AWS IoT SDK Wireless Router AWS IoT Rules Engine Temperature 80.5 81 81.5 OK
- 8. + - + - + - Sensors Actuators Intel Edison AWS IoT SDK Wireless Router AWS IoT Rules Engine Temperature 60 80 100 !
- 9. Sensors & Actions Sensor & Threshold Action Room temperature exceeds 80.5F Turn on fan Soil moisture drops below 70% Turn on misters until 75% moisture level reached Room humidity drops below 80% Turn on room misters until humidity reaches 80%
- 11. Open source software development environment High performance, atom dual-core CPU (500MHz) and single core micro- controller supports complex data collection in a low power package Integrated Wi-Fi certified in 68 countries, Bluetooth® 4.0 support, 1GB DDR and 4GB flash memory simplifies configuration and increases scalability
- 13. Telemetry One of the first data-transmission circuits was developed in 1845 between the Russian Tsar's Winter Palace and army headquarters. In 1874, French engineers built a system of weather and snow-depth sensors on Mont Blanc that transmitted real-time information to Paris. In 1901 the American inventor C. Michalke patented the selsyn, a circuit for sending synchronized rotation information over a distance.
- 14. Administration Actuators Control automation AWS IoT Data storage & analytics Sensors Intel Greenhouse
- 15. MQ Telemetry Transport • Simple to implement • Provide a Quality of Service Data Delivery • Lightweight and Bandwidth Efficient • Data Agnostic • Continuous Session Awareness Also supported: MQTT over Websockets & HTTP Communicating
- 16. Send data PUBLISH aws-loft-nyc/sensors/123 (qos: 0) { "timestamp": "2017-06-29T10:00:00", "temperature": 55, "humidity": 39, "ph": 6.7 }
- 17. Single consumer (don’t do this) AWS IoT instance database PUBLISH sensors/123 PUBLISH sensors/456 SUBSCRIBE sensors/+ PUBLISH sensors/789
- 18. Don’t do this: scalability AWS IoT instance SUBSCRIBE #
- 19. Don’t do this: availability AWS IoT instance
- 20. Don’t do this: maintainability AWS IoT
- 21. Store it in the device shadow (don’t do this) Sensors DEVICE SHADOWS
- 22. 1. AWS Services (Direct Integration) Rules Engine Actions AWS IoT Rules Engine LambdaSNS SQS S3 Amazon KinesisDDB RDS Amazon Redshift Glacier EC2 3. External Endpoints (via Lambda and SNS) Rules Engine connects AWS IoT to External Endpoints and AWS Services. 2. Rest of AWS (via Amazon Kinesis, Lambda, S3, and more)
- 23. Example rule { "rule": { "sql": "SELECT * AS message FROM 'sensors/#'", "description": "Store all sensor data into dynamodb and firehose", "actions": [{ "dynamoDB": { "tableName": "sensor_data", "roleArn": "arn:aws:iam::123456789012:role/aws_iot_dynamoDB", "hashKeyField": "sensor_id", "hashKeyValue": "${topic(2)}", "rangeKeyField": "timestamp“ "rangeKeyValue": "${timestamp()}", } }, { "firehose": { "roleArn": "arn:aws:iam::123456789012:role/aws_iot_firehose", "deliveryStreamName": "my_firehose_stream" } }] } }
- 25. Administration AWS IoT Data storage & analytics Sensors Connected Greenhouse Actuators Control automation
- 26. Automated Misting Service Amazon Kinesis Amazon Machine Learning Amazon Redshift Rules Engine Device Gateway Sensor Mister Amazon Kinesis– enabledapp
- 27. Publish on/off to the mister (don’t do this) Device Gateway Mister Control logic SUBSCRIBE aws-loft-nyc/sprinkler-456
- 28. Publish on/off to the mister (don’t do this) Device Gateway Mister Control logic PUBLISH aws-loft-nyc/sprinkler-456 { "water": "on" }
- 29. Direct publishing: why not? Mister Control logic on off Device Gateway off on
- 30. Direct publishing: why not?
- 31. Direct publishing: why not? Device Gateway Mister (offline) Control logic PUBLISH aws-loft-nyc/sprinkler-456 { "water": "on" }
- 32. Direct publishing: why not? • Messages aren’t ordered • Connection blips So then what?
- 33. Device Shadows
- 37. AWS IoT Shadow - Simple Yet Powerful { "state" : { “desired" : { "lights": { "color": "RED" }, "engine" : "ON" }, "reported" : { "lights" : { "color": "GREEN" }, "engine" : "ON" }, "delta" : { "lights" : { "color": "RED" } } }, "version" : 10 } Thing Report its current state to one or multiple shadows Retrieve its desired state from shadow Mobile App Set the desired state of a device Get the last reported state of the device Delete the shadow Shadow Shadow reports delta, desired and reported states along with metadata and version
- 38. Device shadows and versioning Sprinkler Control logic on (version=1) off (version=2) Device Gateway off (version=2) on (version=1) (old message ignored by device)
- 39. Manual Control
- 40. Data storage & analytics Sensors Talking back to the sprinklers: manual override Control automation AWS IoT Administration Actuators
- 41. Wrap-up
- 42. AWS IoT Data storage & analytics Administration Sensors Actuators Intel Greenhouse Control automation
Editor's Notes
- Experts estimate that the IoT will consist of almost 50 billion objects by 2020. British entrepreneur Kevin Ashton coined the term in 1999 while working at Auto-ID Labs
- AWS Device SDK – this is what goes on the thing/sensor/unit Security is the priority for AWS – Authentication and Authorization - Mutual Authentication TLS granted via certificates deployed onto the devices Registry is the metadata store - when you deploy millions of devices you want to know what they are and what they do - devices register themselves with the registry Device Gateway - Millions of devices and apps can connect over MQTT, WebSockets, and HTTP 1.1 Powerful Pub/Sub Broker with Long-lived bi-directional messages Rules Engine - Match patterns and take actions to send data to other AWS services or republish Device Shadow - DEVICE connectivity is a trouble for developers - SHADOW IS VIRTUAL DEVICE - if device is connected is pass-thru otherwise is a reference for apps This is how applications communicate with devices, even without knowing if the device is online or not. Shadow will keep latest state of a device. IoT will know how to communicate with the device and send this state to shadow, applications will always have a state to work with
- What
- TELEMETRY – REMOTE MEASUREMENT
- TELEMETRY – REMOTE MEASUREMENT
- TELEMETRY – REMOTE MEASUREMENT
- TELEMETRY – REMOTE MEASUREMENT
- TELEMETRY – REMOTE MEASUREMENT
- TELEMETRY – REMOTE MEASUREMENT
- TELEMETRY – REMOTE MEASUREMENT
- TELEMETRY – REMOTE MEASUREMENT
- TELEMETRY – REMOTE MEASUREMENT
- Design a connected farm, where different IoT components and AWS services fit into the architecture
- TELEMETRY – REMOTE MEASUREMENT
- Quality of service QoS0 – fire and forget QoS1 – at least once QoS2 – at most once
- all traffic funnels into one instance, also one DB instance MQTT has these handy wildcard topics. Beware! Nicely horizontally scalable IoT platform. “Hey let’s feed 100% of the data coming into the platform down one TCP connection to one server”.
- Has to be running to process the data
- Operationally painful (not serverless)
- IoT comes with a free place to store state about each device in your system. We’ll go into it more in a bit. Useful for synchronizing state. Query the last known state of a device, communicate a desired state back to the device Only queryable by device id In other words, if you do this, you can’t get at your data the right way
- RULES: DESCRIBE WHAT MESSAGES TO MATCH, HOW TO TRANSFORM THEM, WHAT TO DO WITH THEM Simple SQL Translate keys TMP TEMP Math functions on inbound data (averages, sums, etc)
- Design a connected farm, where different IoT components and AWS services fit into the architecture
- Messages aren’t ordered “Turn on the sprinkler” “no wait turn it off” should result in “off”, not “on”.
- Messages aren’t ordered “Turn on the sprinkler” “no wait turn it off” should result in “off”, not “on”.
- When it’s offline, you don’t want your commands to be dropped forever When it re-connects, it needs to know what to do
- DEVICE connectivity is a trouble for developers SHADOW IS VIRTUAL DEVICE - if device is connected is pass-thru otherwise is a reference for apps This is how applications communicate with devices, even without knowing if the device is online or not. Shadow will keep latest state of a device. IoT will know how to communicate with the device and send this state to shadow, applications will always have a state to work with
- Messages aren’t ordered “Turn on the sprinkler” “no wait turn it off” should result in “off”, not “on”.
- Design a connected farm, where different IoT components and AWS services fit into the architecture
- Design a connected farm, where different IoT components and AWS services fit into the architecture