Get access to the new Intel® IoT Developer Kit, a complete hardware and software solution that allows developers to create exciting new solutions with the Intel® Galileo and Intel® Edison boards. Visit the Intel® Developer Zone for IoT.
This automatic plant lighting system monitor application is part of a series of how-tos for Internet of Things (IoT) code sample exercises using the Intel® IoT Developer Kit, Intel® Edison board, Intel® IoT Gateway, cloud platforms, APIs, and other technologies.
From this exercise, developers will learn how to:
- Connect the Intel® Edison board or Intel® IoT Gateway, computing platforms designed for prototyping and producing IoT and wearable computing products.
- Interface with the Intel® Edison board or Arduino 101* (branded Genuino 101* outside the U.S.) board IO and sensor repository using MRAA and UPM from the Intel® IoT Developer Kit, a complete hardware and software solution to help developers explore the IoT and implement innovative projects.
- Run these code samples in the Intel® System Studio IoT Edition (Eclipse* IDE for C/C++ and Java* development) for creating applications that interact with sensors and actuators, enabling a quick start for developing software for the Intel® Edison board or the Intel® Galileo board.
- Set up a web application server to set the lighting time and store this data using Azure Redis Cache* from Microsoft*, Redis Store* from IBM Bluemix*, or Elasticache* using Redis* from Amazon Web Services (AWS)*, different cloud services for connecting IoT solutions including data analysis, machine learning, and a variety of productivity tools to simplify the process of connecting your sensors to the cloud and getting your IoT project up and running quickly.
- Invoke the services of the Twilio* API for sending text messages.
- Connect to a server using IoT Hub from Microsoft Azure*, IoT from IBM Bluemix*, IoT from Amazon Web Services (AWS)*, AT&T M2X*, Predix* from GE, or SAP Cloud Platform* IoT, different cloud-based IoT platforms for machine to machine communication.
What it is
Using an Intel® Edison board or Intel® IoT Gateway, this project lets you create an automatic plant lighting monitor system that:
- checks if a separate automated lighting system is turned on or off based on a configurable schedule, by using a light sensor.
- can be accessed with your mobile phone to set the lighting periods via a built-in web interface.
- monitors water levels using a connected moisture sensor.
- logs events from the lighting system, using cloud-based data storage.
- sends text messages to alert the user if the system is not working as expected.
How it works
This lighting system has a few useful features.
You can set the lighting system schedule via a web page served directly from the Intel® Edison board or Intel® IoT Gateway, using your mobile phone.
If the lighting is supposed to be on but the light sensor does not detect light, the application sends an SMS alert to a specified number through Twilio*.
It also automatically checks the moisture sensor data at specified intervals and logs that information.
Optionally, data can be stored using your own Microsoft Azure*, IBM Bluemix*, AT&T M2X*, AWS*, Predix*, or SAP* account.
Grove* Indoor Environment Kit containing:
- Intel® Edison board with an Arduino* breakout board
- Grove Base Shield V2
- Grove Moisture Sensor
- Grove Light Sensor
- Grove RGB LCD
DFRobot* Starter Kit for Intel® Edison containing:
- Intel® Edison module with an Arduino* breakout board
- Moisture Sensor.
- Analog Ambient Light Sensor
- LCD Keypad Shield
- Intel® System Studio (Eclipse IDE for C/C++ and Java* development)
- Microsoft Azure*, IBM Bluemix*, AT&T M2X*, AWS*, Predix*, or SAP* account (optional)
- Twilio* account
How to set up
This sample is already one of the IoT examples included in Intel® System Studio. To start using it, follow these steps:
- From the main menu, select Intel® IoT > Import IoT Examples.
- Expand the tree view for C++ > How To Code Samples > Plant Lighting System and click Import Example.
- Select your developer board from the selection window then select Next.
- Select Intel® IoT C/C++ project from the Select a project type window then click Next.
- Select Yocto from the Selct target OS dropdown menu then click Next.
- The next tab will ask for connection name and target name. If you do not know these click Search Target.
- Select your Edison from the dropdown list. Select OK.
- Your connection name and target name should be filled in. Select Finish.
- A new window will open for you and you will need to choose a name for your project and click Next.
- Your project source files will now be available on the on the upper left of your IDE by default.
Connecting the Grove* sensors
You need to have a Grove* Base Shield V2 connected to an Arduino* compatible breakout board to plug all the Grove devices into the Grove Base Shield V2. Make sure you have the tiny VCC switch on the Grove Base Shield V2 set to 5V.
- Plug one end of a Grove cable into the Grove* Light Sensor, and connect the other end to the A0 port on the Grove Base Shield V2.
- Plug one end of a Grove cable into the Grove Moisture Sensor, and connect the other end to the A1 port on the Grove Base Shield V2.
- Plug one end of a Grove cable into the Grove RGB LCD, and connect the other end to any of the I2C ports on the Grove Base Shield V2.
Connecting the DFRobot* sensors
You need to have a LCD Keypad Shield connected to an Arduino* compatible breakout board to plug all the DFRobot* devices into the LCD Keypad Shield.
Plug one end of a DFRobot* cable into the Analog Ambient Light Sensor, and connect the other end to the A2 port on the LCD Keypad Shield.
Plug one end of a DFRobot* cable into the Moisture Sensor, and connect the other end to the A3 port on the LCD Keypad Shield.
Twilio* API Key
To optionally send text messages, you need to register for an account and get an API key from the Twilio* web site:
You can still run the example, but without a Twilio API key you cannot send SMS alerts.
Intel® IoT Gateway setup
You can run this example using an Intel® IoT Gateway connected to an Arduino 101* (branded Genuino 101* outside the U.S.).
Make sure your Intel® IoT Gateway is setup using Intel® IoT Gateway Software Suite, by following the directions on the web site here:
The Arduino 101* (branded Genuino 101* outside the U.S.) needs to have the Firmata* firmware installed. If you have IMRAA installed on your gateway, this will be done automatically. Otherwise, install the StandardFirmata or ConfigurableFirmata sketch manually onto your Arduino 101* (branded Genuino 101* outside the U.S.).
IoT cloud setup
You can optionally store the data generated by this sample program using cloud-based IoT platforms from Microsoft Azure*, IBM Bluemix*, AT&T M2X*, AWS*, Predix*, or SAP*.
For information on how to connect to your own cloud server, go to:
Data store server setup
Optionally, you can store the data generated by this sample program in a back-end database deployed using Microsoft Azure*, IBM Bluemix*, or AWS*, along with Node.js*, and a Redis* data store.
For information on how to set up your own cloud data server, go to:
Configuring the example for your hardware kit
To configure the example for the specific hardware kit that you are using, either Grove* or DFRobot*:
- From the main menu, select Project > Properties dialog box is displayed.
- Expand the section C/C++ General.
Click on the Paths and Symbols sub-section, and click on the Symbols tab.
- Now click on GNU C++, and click on the Add button.
- In the Name field, enter “INTEL_IOT_KIT”. In the Value field, enter either “GROVEKIT” (this is the default) or “DFROBOTKIT”, depending on which hardware kit you wish to use.
- Your new name symbol and value will now be displayed. Click OK.
- Another dialog box will appear asking to rebuild project. Click OK.
Connecting your Intel® Edison board or Intel® IoT Gateway to Intel® System Studio
If prompted for the username and password, the username is root and the password is whatever you specified when configuring the Intel® Edison board or Intel® IoT Gateway.
Running the example with the cloud server
To run the example with the optional backend data store, you need to set the
AUTH_TOKEN environment variables. You can do this in Intel® IoT Gateway to Intel® System Studio as follows:
From the Run menu, select Run Configurations.
The Run Configurations dialog box is displayed.
Under C/C++ Remote Application, click doorbell.
This displays the information for the application.
In the Commands to execute before application field, add the following environment variables, except use the server and authentication token that correspond to your own setup:
chmod 755 /tmp/watering-system; export SERVER="http://intel-iot-example-data.azurewebsites.net/logger/watering-system"; export AUTH_TOKEN="Enter Auth Token Here"; export TWILIO_SID="Enter Twilio SID Here"; export TWILIO_TOKEN="Enter Twilio Token Here"; export TWILIO_TO="Enter Number to Send to here Formattted 555-555-5555"; export TWILIO_FROM="Enter Number to be Sent From Here Formated 555-555-5555"
Click Apply to save your new environment variables.
Now when you run your program using the Run button, it should be able to call your server to save the data right from the Intel® Edison board or Intel® IoT Gateway.
Running the code on the Intel® Edison board
This compiles the program using the Cross G++ Compiler, links it using the Cross G++ Linker, transfers the binary to the Intel® Edison board or Intel® IoT Gateway, and then executes it on the board itself.
Regenerating HTML and CSS
If you make any changes to either the index.html or styles.css file, you need to regenerate the .hex file used to serve up the assets via the built-in Crow* web server. For help using the shell script, go to this link:
Setting the lighting schedule
The latest data values from the connected Grove* Moisture Sensor are displayed at the bottom of the web page.
The web server runs on port
3000, so if the Intel® Edison board or Intel® IoT Gateway is connected to Wi-Fi on
192.168.1.13, the address to browse to if you are on the same network is
IMPORTANT NOTICE: This software is sample software. It is not designed or intended for use in any medical, life-saving or life-sustaining systems, transportation systems, nuclear systems, or for any other mission-critical application in which the failure of the system could lead to critical injury or death. The software may not be fully tested and may contain bugs or errors; it may not be intended or suitable for commercial release. No regulatory approvals for the software have been obtained, and therefore software may not be certified for use in certain countries or environments.