Rate this page:

Build an SMS-Equipped Twilio Weather Station with an ESP8266, Amazon AWS IoT and Lambda

Twilio-Powered SMS sending Weather Station with Lambda, AWS IoT, and an ESP8266

Today we're going to look at how to build an ESP8266 weather station which uses Twilio Programmable SMS to send weather updates. Our station will reply to incoming SMS messages with weather reports as well as send daily scheduled outgoing SMS weather reports. We'll use AWS IoT as a persistent preference store and MQTT broker and a combination of AWS Lambda and API Gateway to send and receive messages with Twilio.


We will cover each of these in more detail as we go along, but to build the whole station you'll need:

  • Twilio Account
  • AWS Account
  • ESP8266 (Good options)
  • DHT11 (or 22) Humidity Sensor (Like this)
    • For a bare sensor, a 4.7k or 10k resistor is needed as well. (Included with the Adafruit product)
  • BMP180 (or 085) Barometric Pressure Sensor (Like This)
  • Male to Male Jumper Wires (Like these)
  • Solderless Breadboard (Like this)

Depending on your choice of ESP8266 development board (or breakout), you may also need:

And of course, our code: Click here for the repository.

Sounds Cool! Let's Begin.

Why a Weather Station?

We've written four guides about using Twilio (and in two cases, an ESP8266) with the AWS ecosystem:

This tutorial wraps all of them up with an end-to-end application that does something useful - watches the weather wherever you want it to. Remote monitoring is a major IoT application, and hopefully this station gives you some ideas for your own product.

This build allows us to put something together which incorporates the requirements of many applications you might end up building next. We're going to look at receiving messages via Webhooks from Twilio, sending messages via the Twilio Python Helper Library and AWS Lambda, persisting device state with AWS IoT, and connecting everything over MQTT topics.

Weather Station Architecture

Our architecture is unchanged from our Receiving and Replying to MMS and SMS messages with a ESP8266 and AWS post.

Sending Messages:

Sending Messages with AWS IoT, Lambda, and the ESP8266

Receiving Messages:

Receiving SMS and MMS Messages from Twilio with AWS IoT and Lambda

In addition, we'll be adding a handler for 'Help' and 'Set Preference' messages, which will come in over SMS. These will return TwiML to Twilio at the Lambda step in the above diagram. Any successful preference changes will happen in the background on the MQTT topic.

Jump In...

Sign Into a Twilio Account

Our weather station will communicate with you - or whomever you give the number - completely over SMS. We'll eventually have messages moving both ways - originating from the ESP8266 and pushed to you, as well as messages initiated by you to the 'weather station'.

Log into your Twilio account now - and if you don't have one here is a link to sign up for a free Twilio trial. Keep that browser tab handy - you will need to refer back to it later.

Find or Purchase a SMS Capable Number

For this demo, you'll require a SMS capable number you already own (or purchase now).

Go to the Twilio Console and select the hash tag/Phone Numbers ('#') section on the left side. Navigate to your currently active numbers.

Under capabilities, you'll want to look for one with SMS capabilities, as shown in the below image:

Active SMS Capable Numbers

If you don't yet have a number with the SMS icon, you'll need to buy one. Navigate to the 'Buy a Number' link and click the SMS checkbox:

Buy a number with sms capabilities

After purchasing, leave the Console tab open and you'll be ready to head to Amazon Web Services.

Log Into - or Sign Up For - Amazon Web Services

A lot of the weather station's infrastructure will use AWS products. AWS will handle passing messages to and from the ESP8266, persisting state in a power loss for the ESP, helping the end user change settings, and handling webhook requests from Twilio.

Let's Set Up AWS IoT

Supporting Your Things with AWS IoT

While our weather station server is the ESP8266, our station will be a lot more reliable if we have a service backing it. That's the role AWS IoT will play.

Importantly, IoT provides a way for us to save and persist preferences. When the ESP8266 power cycles, it will start up with whatever defaults are programmed into the flash. AWS IoT gives us the concept of Thing Shadows, where a Thing can query the current preferences whenever it needs to - and we'll use it to change the station settings at startup.

Also essential to our infrastructure, AWS IoT acts as the MQTT message broker. There will be multiple MQTT topics dedicated to AWS IoT reserved topics, and we will add the topics 'twilio' and 'twilio/delta' to handle messages and setting changes, respectively.

Set Up AWS IoT

If you haven't yet, you'll need to add a new 'Device' and a few other things to IoT. We discuss how to perform these steps in greater detail in our sending messages with IoT, Lambda and the ESP8266 article, but we'll cover the steps briefly now. If you have performed these steps already, feel free to skip ahead to Watching MQTT Cross-Traffic.

  1. In the left pane of the AWS IoT Dashboard, under 'Registry' select 'Things'.
  2. Name your Thing whatever you like. (e.g. “Twilio_ESP8266_Weather_Station”)
  3. Use the big grey back arrow at the top of the frame to go back to 'Things'.
  4. Click your newly created Thing.
  5. Click ‘Interact’ in the sidebar.
  6. Save the endpoint and “Update to this thing shadow” topic somewhere (text document?) for later use.

HTTPS Endpoint and MQTT Shadow Update

Keep this frame open to join the Twilio console frame, or copy those to a safe place - we'll be using them later (including later in IoT Setup).

Set an Initial Shadow State

The state itself doesn't matter, but we need to seed our thing with an initial shadow state.

  1. Click the 'Shadow' link on the left sidebar.
  2. Next to 'Shadow Document', click the 'Edit' button
  3. Paste in the following code:
  "desired": {
    "units": "imperial",
    "alt": 60,
    "tz": -500,
    "t_num": "+18005551212",
    "m_num": "+18005551212",
    "alarm": 1234567890

Save it and you'll have an initial policy - don't worry, we'll change to some suitable parameters later.

Add a Policy to PubSub on the 'twilio' and 'twilio/delta' Topics

Use the big grey arrow again and return to the main console.

Click 'Security' then 'Policies', then 'Create a Policy'. Name it something memorable, and use an action of 'iot:*' with a Resource ARN replacing the last bit with 'twilio'. This will allow your Thing to publish and subscribe to the 'twilio' channel, and should also allow the same rights on any channels nested under /twilio.

Create IoT Policy

Watching MQTT Cross-Traffic

When everything is eventually plumbed together, there will be a lot of action on the MQTT topics. While you're in the AWS IoT Console, you should add two new tabs to your persistant collection.

  1. On the left sidebar, select 'Test'
  2. Subscribe to the 'Update to this thing shadow' topic (from the above step)
  3. Subscribe to the 'delta' topic, which is the update topic with /delta appended
  4. Open a new tab to 'Test' to subscribe to more topics (leave the other open)
  5. Subscribe to the 'twilio' topic
  6. Subscribe to the 'twilio/delta' topic

Subscribing to Topics in IoT Test Client

Minding The Limited RAM

RAM on the ESP8266 is limited to 64 kB for instructions and 96 kB for data. The 'kilo' istead of 'giga' or even 'mega' is our hint to reduce the amount of data the ESP8266 is required to handle.

When there is an update to the Thing Shadow, AWS will send various parameters which are not needed in our setup. We're going to take advantage of an AWS IoT rule which allows us to extract only what's essential.

Under Rules, click the 'Create' button. Use a name of 'main_weather_preferences' and your choice of description. In the fields that follow, here's what to use:

  • Attribute: state
  • Topic: the same /delta topic as in the previous section, which is the update topic followed by /delta

You can see our delta topic for a Thing type named 'Twilio_ESP8266_Weather_Station':

Republishing a Stripped Down Message on a New MQTT Topic with AWS IoT

Add an action of "Republish messages to an AWS IoT topic" and provide "twilio/delta" as the topic name.

Create that rule and you'll be well on your way to having a user-adaptable weather station! Now updates to the weather station normally passed on the update/delta topic will have the core extracted for processing by the ESP8266.

Things Are Heating Up

Mocking an API With API Gateway

In the last section, you set up a framework for the ESP8266 to stay connected to AWS. We also need a plan for the outside world to talk to our weather station.

When you send a text message to a Twilio number, Twilio forwards it to a webhook at a URI you define. In order to expose a resource with AWS, we use the API Gateway service.

We first went covered this process in our receiving and replying to SMS and MMS messages using Amazon Lambda guide, but we will describe it briefly here.

  1. From the API Gateway console, use the 'Create API' button.
  2. Name and describe your API a friendly name and description (for your own reference), then create it.
  3. Create a new resource 'message' (at '/message')
  4. Create a 'POST' method on message.
  5. Select 'Mock' as your 'Integration type'.

Mock API Integration Type

For now, that's it for API Gateway. We'll be returning later when Lambda is ready.

Highly Suggested - Set Up a New IAM User

While you can use your main AWS account's credentials for the weather station, best practice with the ESP8266 is to create a new IAM user with IoT permissions. Go to the IAM console, select 'Users' in the left pane and click the blue 'Add User' button.

Name your user and click the box to add Programmatic Access:

Adding an IAM User for AWS IoT

Click through to the 'Permissions' step and select 'Attach Existing Policies Directly'. Add every IoT permission, as we did in this picture:

AWS IoT IAM User Permission

Download the CSV with the user credentials from the success screen. Those will be used in the settings at the top of the .ino file the ESP8266 uses.


Using Lambda To Send Outgoing Messages

While the ESP8266 does have the capability to use the Twilio API directly to send messages (with a few shortcuts, like verifying a certificate fingerprint), we're going to use the AWS infrastructure to send messages via a Lambda function. To demonstrate the flexibility of this approach, we're going to use the same setup as we did in the sending SMS and MMS Messages with the ESP8266 and Lambda article.

We'll discuss what you need to do briefly here, but for the full details of each step please visit that article.

Having Outgoing Messages Trigger Lambda

  1. Create a new Lambda function in the same region as you've set up AWS IoT (use the blank template). Configure it to use AWS IoT as a trigger.
  2. Check the box for 'Enable Trigger' and name it something memorable. 'IoT Type' should be 'Custom IoT Rule'.
  3. The SQL statement you should use to trigger Lambda is:
    SELECT * FROM 'twilio' WHERE Type='Outgoing'
  4. Here's how you do that from the configuration screen:

    Integrating Amazon Lambda and AWS IoT

  5. Hit 'Next' to go to the function stage.

Leave a Blank Function

  1. Change the runtime to 'Python 2.7'.
  2. Set the 'Handler' field to 'twilio_functions.iot_handler' in preparation for our upcoming code upload.
  3. Name the function 'myTwilioSendMessage' and use whatever description you desire.
  4. Use 'Create new role from template(s)' using the AWS IoT Button Permissions, and naming the role something memorable.

You're now ready - create the blank function!

Change the SQL Version

Return to the AWS IoT console briefly (perhaps even in a new tab) - we've got to do one more step so AWS and the ESP8266 play nicely.

  1. Click the 'Rules' link in the left sidepane.
  2. You should then see the new rule you've created for the send Lambda function; click it to see details.
  3. In the 'Rule query statement' section, click the 'Edit' link, and change the 'Using SQL version' to '2015-10-08':

Amazon SQL Version Selector in AWS IoT

Hit the 'Update' button and your ESP8266 will be ready to fire your rule!

Add some Python Code to Lambda

It's time to add some code.

  1. On your computer, create a new folder and install the Twilio Python Library manually inside.
  2. From the GitHub repository, bring in everything from the 'Lambda Function Send SMS' directory (see our earlier guide for detailed help on adding external packages, and read the companion article if you want more details on that function). Zip the contents of that directory up.
  3. Inside Lambda, select 'Upload a .ZIP File' on the 'Code' tab. Using 'Upload', select the zip file you just created and upload it by saving.
  4. Double check you're using the Python 2.7 runtime, and that the Handler is set to 'twilio_functions.iot_handler'.

You won't be able to edit the code inline with the newest helper library, so if you have issues make your updates offline then upload again.

Set the Environmental Variables

In Lambda, Environmental Variables are set on the 'Code' tab. From the Twilio Console (you do have the tab still open, right?), find your authorization token and account ID to populate:


And with that, you should have the plumbing set to send messages from the weather station. You can double check the 'Triggers' tab to make sure that IoT is triggering this function based upon the SQL query we already entered.

If that checks out, we can move on...

Let's Find Shelter Under an SMS-Tree

Using Lambda to Build a SMS-Tree

We're going to model the user facing portion of the Weather Station as a SMS-Tree, much like the Phone Trees Twilio makes so easy to create. Philosophically, our SMS-Tree will be stateless and idempotent - that is, performing actions will not require multiple steps and running the same command multiple times will leave the device in the same state.

For authorization and security we are employing a few mechanisms:

  • We use the Python Twilio Helper Library's assistance in to verify a Webhook originates from Twilio (see our detailed writeup).
  • We use a 'Master Number' that is allowed to make changes to the settings (although other users can see status other than the master_number).

Create a User Facing Lambda Function

Using similar steps, create a new blank Lambda function named 'twilioWeatherStation' with no trigger. The 'Handler' should be set to 'twilio_functions.twilio_webhook_handler', and create a zip file which contains the code in the 'Lambda Function Weather' directory and the Twilio Python Helper Library. For details on loading external libraries into Lambda, see this article.

This function needs five environmental variables:

  • AUTH_TOKEN - Twilio Auth Token, from the Console
  • AWS_TOPIC - 'twilio' without quotes
  • THING_NAME - whatever you named the thing, we used 'Twilio_ESP8266_Weather_Station'
  • AWS_IOT_REGION - the region of the Thing above
  • REQUEST_URL - This will be the request URL of API Gateway, and will exactly match Twilio - so leave it blank for now.

Under role, select 'Create a New Role From Template', selecting 'AWS IoT Button permissions'. Give that role a descriptive name - such as 'twilio_weather' - and continue. Next we'll give that role some special permissions.

Allowing Lambda to Post to MQTT Topics and Update the Device Shadow

Since this Lambda function is both publishing to MQTT topics as well as updating and checking the Thing Shadow, it is going to need extra permissions. We're going to enable them through IAM using an inline policy.

  1. Go to IAM by using the 'My Security Credentials' in your name pulldown:
    Go to Amazon IAM With The Menu Near Your Name
  2. Click on the 'Roles' link in the left sidebar.
  3. Find the role you assigned to this Lambda function and click on it.
  4. Click on the 'Create Role Policy' button under 'Inline Policies':
    Create Inline Role Policy in Amazon IAM
  5. add an inline policy which allows this function free reign in IoT:
        "Version": "2012-10-17",
        "Statement": [
                "Effect": "Allow",
                "Action": [
                "Resource": [

Now your Lambda function can perform every action it needs to in IoT - and for this weather station, we'll be using quite a few.

Next let's do a bit of a deep dive and highlight some of the features of the Lambda server code.

What Are Our SMS-Tree Functions?

Our SMS-Tree will help the user, let the user change settings, and send the user a weather report.


We build a number of 'Help' responses to guide our users when updating settings. There will be a general help message, individual help on each specific setting, and an overview of the currently set settings.

        Parse incoming 'help' messages and either return an overview or help on a single topic.

        Handle incoming 'help' messages

        Parse incoming 'help' messages and either return an overview or help on a single topic.

        Both '?' and 'help' are used to retrieve help. Note that by default for a ten-digit phone number Twilio will handle any incoming SMS with a body of 'help'. 'help' messages with multiple words will still be passed through to Lambda.


        If the user is authorized, we allow her to change the settings which affect the behavior of the station. We have included some very basic input validity checks to ensure, for example, that settings which require numbers are only set to numbers.

              Parse 'set' messages to change preferences and behavior of the weather station.

              Handle incoming 'set' messages

              Parse 'set' messages to change preferences and behavior of the weather station.

              Both 's' and 'set' are used to perform a set command.


              If the message is not a 'Help' or a 'Set' message, we pass it through to the ESP8266. The logic there is simple - for any SMS or MMS it receives, it will send back the last weather report.

                    Non 'set' or 'get' incoming messages will retrieve a weather report.

                    Get a weather report

                    Non 'set' or 'get' incoming messages will retrieve a weather report.
                    Back to the API Gateway

                    Triggering Lambda from API Gateway

                    Go back to the API Gateway console, and navigate to the API we were building up before. We're going to use it now to trigger our new Lambda function.

                    The receiving and replying to SMS and MMS messages from Lambda article has the full steps you'll need to perform to have a working API for Twilio to call, but we'll summarize here.

                    1. In 'Method Request', add X-Twilio-Signature HTTP Request Header to pass through to Lambda.
                    2. In 'Integration Request', remove any Body Mapping Templates and add one for application/x-www-form-urlencoded with a template of:
                      #set($httpPost = $input.path('$').split("&"))
                      "twilioSignature": "$input.params('X-Twilio-Signature')",
                      #foreach( $kvPair in $httpPost )
                       #set($kvTokenised = $kvPair.split("="))
                       #if( $kvTokenised.size() > 1 )
                         "$kvTokenised[0]" : "$kvTokenised[1]"#if( $foreach.hasNext ),#end
                         "$kvTokenised[0]" : ""#if( $foreach.hasNext ),#end
                    3. In 'Integration Response', remove any Body Mapping Templates and add a new one in HTTP status code 200 for application/xml. Use this two line template:
                      #set($inputRoot = $input.path('$')) 
                    4. In 'Method Response', for HTTP Status 200 remove any existing response bodies and add one for application/xml.

                    Now, from the 'Action' pulldown menu, 'Deploy API':

                    Deploy an API in API Gateway

                    Create a new stage with a name of 'prod' and your choice of description.

                    When you deploy, Amazon will assign a URL to the new /message route. Copy the entire thing, including the /message. Back in the weather station Lambda function's 'Code' tab, paste the exact URL into the REQUEST_URL environmental variable.

                    Next, even though we haven't even added our hardware yet(!), we're going to plug everything together and test it with Twilio.

                    Add Twilio to the Mix

                    Configure Your Twilio Webhook URL

                    In the Twilio Console browser tab, navigate to the Numbers Section in the sidebar (#). Select the number you set up in the beginning of this tutorial.

                    Under 'Messaging' and in 'A Message Comes In', select 'Webhook' and paste the API Gateway URL into the text box (highlighted below). Ensure 'HTTP POST' is selected.

                    Configure a Webhook

                    Backup Webhook URL

                    While in many applications you should plan for the failure of the first Webhook, for this weather station we're okay having a single point of failure.

                    Just be aware - when you are building a Twilio application and the primary Webhook fails (sends back a 5xx HTTP response or times out), Twilio will failver to the backup web hook. That extra piece of machinery is perfect for ensuring you maximize the number of 9s in your uptime.

                    Text Your Twilio Number for Help or Settings

                    As noted, we haven't added any hardware yet so the weather will have to wait... but we can try out the set/help machinery.

                    Try texting the number from your cell phone now, with a single question mark ('?') in the body.

                    If everything is working together, you should see the 'Hello, World!' of this application - a friendly (but terse, admittedly!) message from Lambda about the various help topics.

                    You can 'set' variables too, such as 'tz' for timezone (in minutes):

                    • set tz -480
                      (Pacific Standard time: -8 hours * 60 minutes).
                    • set tz 540
                      (Japan standard time: +9 hours * 60 minutes).

                    Hopefully you get something back!

                    If not, trace back through the chain, starting with the Twilio Debugger. For each step in the chain, check the logs - after the debugger, check CloudWatch for any Lambda or API Gateway logs, and finally (for 'set' messages only), check for MQTT messages in the Test MQTT clients.

                    If it all works, most of the software is done - it's time to move to the board. It's time - let's build the actual station itself!

                    Here Comes the Sun

                    The ESP8266 Weather Station - Board and Software

                    At this point, we're ready to put together the ESP8266 part of the chain. If you haven't yet purchased a board, the repository for Arduino on ESP8266 has a nice list of tested boards. We'll be building the weather station on a solderless breadboard with pre-made jumper wires. That in mind, we'd suggest sticking with a full sized development board until it's working... after that you can decide if you'd like to miniaturize the setup.

                    To develop this guide, we used a Sparkfun Thing and Sparkfun's Basic FTDI breakout. The Sparkfun Thing overloads the DTR pin for ease of programming. This causes problems with the hardware serial port when monitoring from inside the Arduino IDE. We find it easier to use SoftwareSerial for simple text debugging, but have left the choice of serial port (or none) as a setting in the code - you can use the USE_SOFTWARE_SERIAL and USE_HARDWARE_SERIAL to tell the preprocessor how to compile serial support in the code.

                    Arduino IDE

                    For the greatest ease of use, we developed the ESP8266 code for this tutorial in the Arduino IDE. Help building the station using another toolchain is outside the scope of this tutorial. While we encourage you to try, please use Arduino to get a working setup first.

                    Adding ESP8266 Support to Arduino

                    If you haven't added new board support to Arduino before, we'll walk through that now - feel free to skip ahead if the ESP8266 is already added to your setup.

                    In your preferences, add a new URL to the 'Additional Board URLs' section: "".

                    Add Board to Arduino

                    Next, in the 'Tools' menu, select 'Boards Manager'. It will automatically update - after a second, search for the ESP8266 and install the most recent version.

                    Adding Libraries to Arduino

                    We're relying on quite a few libraries for the guide today:

                    Using Arduino's Library Manager is possible for two of the libraries, but the others must be added manually. For a complete overview of library management on Arduino, see the official documentation.

                    Add Through Library Manager (Search)

                    • Adafruit BMP085 Unified
                    • Adafruit Unified Sensor
                    • DHT Sensor Library
                    • NTPClient
                    • ArduinoJSON
                    • WebSockets

                    Add Manually to Arduino

                    The easiest way to install these libraries in the Arduino IDE is to install from a downloaded zip file.

                    This can be done directly from the ZIP Library Installer in the Arduino IDE:

                    'Sketch' Menu -> 'Add .ZIP Library' -> select downloaded .zip file

                    Add ZIP Library to Arduino

                    Download links:

                    Compiling The Weather Station Code

                    We've bottled up much of the complexity of the weather station in the TwilioLambdaHelper (first seen in this article) and TwilioWeatherStation classes. In those classes, we manage a lot of the heartbeat functions which need to be fired off on certain timers. We also wrap up things like managing time and reading the sensors.

                          Editable preferences for the ESP8266 weather station.

                          Customize your weather station

                          Editable preferences for the ESP8266 weather station.

                          At the top of the .ino file, there are a number of settings you'll need to change before compiling.

                          Edit in your WiFi credentials, the AWS key & secret for a properly credentialed IAM user (did you create a new one earlier?), the AWS region of the IoT device, and the HTTPS AWS endpoint. Change the shadow_topic to the Thing Shadow update topic listed in the Interact tab of your IoT Thing (you probably still have that tab open).

                          Although it looks like there are a number of extra settings, they are actually optional. When the ESP8266 connects, it will report to AWS IoT with its current state. IoT will report back on what needs to change. The ESP8266 will change its settings, and send another report on state (which this time will be met with no changes).

                          We'd still suggest changing these to your preference, however - they are useful as a reference.

                                Reply to an incoming weather request with the most recent readings.

                                Respond to a weather report request

                                Reply to an incoming weather request with the most recent readings.

                                Try compiling - and with that, you're ready to build the hardware and flash the board!

                                Finally... Let's Build Some Hardware

                                The ESP8266 Weather Station - Hardware

                                This part might be a little tricky since we will all be using different boards. With the current setup, you will need to use I2C to connect the BMP Pressure sensor. If you need to move the DHT sensor, update the DHTPIN setting in the code.

                                DHT11 Data Pin ESP8266 GPIO0
                                BMP180 SCL Pin ESP8266 SCL Pin
                                BMP180 SCA Pin ESP8266 SCA Pin

                                Depending on the DHT11 sensor you purchase, you will need to add a 4.7kΩ resistor between data and 3.3 volts. These resistors start with Yellow, Violet and Red in a 4-band resistor, and it is drawn on the schematic. Don't add a second one if it is already onboard.

                                Remember: Change the exact setup to fit the board and parts you useyou use, and change the pins in the code if you move them around. We drew up a schematic and a possible breadboard layout with Fritzing - but this is based on what we purchased!


                                Note: this schematic is for the SparkFun Thing development board. You might have to vary it for your own hardware! Boards which don't relabel the pins should have a final circuit something like our diagram.

                                One colleague has a NodeMCU board and was succesful with the following setup (GPIO pins are in parentheses; they are not labeled on the board):

                                • D1 (GPIO5): SCL
                                • D2 (GPIO4): SDA
                                • D3: DATA pin of the DHT11

                                AWS Weather Station Schematic

                                One Possible Layout:

                                AWS Weather Station Breadboard

                                Plug it In and Upload Your Code

                                Triple check your connections, then plug everything in. If you don't let out any magic smoke, you're well on your way! (If you did, don't worry about it - it's a rite of passage with hardware - hopefully you've got extras.)

                                Use the 'Tools' menu in Arduino to select your ESP8266. We have had the most success keeping our station connected with a speed of 160 MHz. Choose the proper port and try a slower serial speed such as 115200 for uploading.

                                And with a compile and an upload hopefully everything just works the first time! You've now got a weather station which updates every 3 minutes with barometric pressure, humidity and temperature.

                                A Weather Station... If You Can Keep It

                                Changing Weather Station Settings

                                There are at least three avenues to change the settings on the station, and you should set the initial state depending on what seems easiest:

                                Through the Shadow State Directly

                                1. From the IoT Console, select 'Things' then click the Weather Station, and go to 'Shadow' on the left side bar.
                                2. Under 'Shadow Document', click the 'Edit' link.
                                3. Modify the keys and values directly (there are six, as seen in the Lambda code).
                                4. Upon 'save', the changes will be published to the various MQTT topics.

                                Through an SMS from the Master Cell Phone

                                1. Text into the weather station 'set <param> <value>' or 's <key> <value?'.
                                2. If authorized and making a valid request, the changes will be published to the various MQTT topics.

                                Publishing to the Shadow State Update Channel

                                1. Send properly formatted JSON to the /update topic.
                                2. If 'desired' is in the JSON object body as detailed here, the shadow state will update.
                                3. On update, the changes will be published to the various MQTT topics.
                                It Really Ties the Outdoors Together

                                Remote Monitoring: We've Got Weather Updates! What's Next?

                                This is where you come into play!

                                We've built this remote monitoring application together which will keep a close eye on the weather. The sky - whether blue or grey - is the limit, and the station is now yours to customize and make your own. Add voice, add MMS support with weather icons, even add video (got video working on an ESP8266? We're hiring...).

                                We've got a nice selection of Add-ons with some amazing partners as well. You'll really enjoy how easy the integration is - perhaps see if anything would work well for your application.

                                Whatever you build, we'd love to hear about it. Drop us a line on Twitter and show us what you've built!

                                Paul Kamp David Prothero Kat King Stephanie Marchante Ana Maria Benites Rodríguez
                                Rate this page:

                                Need some help?

                                We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.


                                      Thank you for your feedback!

                                      Please select the reason(s) for your feedback. The additional information you provide helps us improve our documentation:

                                      Sending your feedback...
                                      🎉 Thank you for your feedback!
                                      Something went wrong. Please try again.

                                      Thanks for your feedback!