Srdjan Veljkovic
Pubnub demo for AT&T IoT Starter Kit. Functionally similar to the Flow demo.
Dependencies: FXOS8700CQ MODSERIAL mbed
Pubnub demo for AT&T IoT Starter Kit
This demo is functionally similar to the Flow demo, so you can find general information here: https://developer.mbed.org/users/JMF/code/Avnet_ATT_Cellular_IOT/.
The only difference is that we use Pubnub to publish the measurements and subscribe to receiving the instructions to set the LED.
Settings
Pubnub related settings are:
Pubnub settings in `config_me.h`
PUBNUB_SUBSCRIBE_KEY PUBNUB_PUBLISH_KEY PUBNUB_CHANNEL
All are documented in their respective comments.
Pubnub context class
Similar to Pubnub SDKs, we provide a Pubnub context class. It is defined in pubnub.h header file and implemented in pubnub.cpp.
It provides only the fundamental "publish" and "subscribe" methods. They are documented in the header file.
This class is reusable in other code (it is not specific to this demo), it has a very narrow interface to the AT&T IoT cellular modem code. For example of use, you can look at the main() (in main.c).
Sample of published data
Published message w/measurement data
{"serial":"vstarterkit001","temp":89.61,"humidity":35,"accelX":0.97,"accelY":0.013,"accelZ":-0.038}
Don't worry, nobody got burnt, the temperature is in degrees Fahrenheit. :)
Publish a message (from, say, the Pubnub console http://pubnub.com/console) of the form {"LED":<name-of-the-color>} on the channel that this demo listens to (default is hello_world) to turn the LED to that color on the Starter Kit:
Turn LED to red
{"LED":"Red"}
Turn LED to green
{"LED":"Green"}
Turn LED to blue
{"LED":"Blue"}
Diff: config_me.h
- Revision:
- 81:a5df87708b9a
- Parent:
- 69:5a3414cc7531
--- a/config_me.h Tue Aug 16 13:55:59 2016 +0000 +++ b/config_me.h Fri Sep 02 17:44:55 2016 +0000 @@ -23,23 +23,31 @@ #define BUF_SIZE_FOR_N_MAX_SOCKREAD (10) #define MAX_WNC_SOCKREAD_PAYLOAD (1500) -// This is the server's base URL name. Example "www.google.com" -// Note that when you Fork a FLOW, it will typically assign either -// "run-east.att.io" or "run-west.att.io", so be sure to check this. -static const char * MY_SERVER_URL = "run-west.att.io"; +// This is the server's base URL name. Pubnub SDKs refer to this as "the origin". +// In general, you should leave this to "pubsub.pubnub.com", but in some cases +// you may want to user a different origin. +static const char * MY_SERVER_URL = "pubsub.pubnub.com"; -// These are FLOW fields from the Endpoints tab: -#define FLOW_BASE_URL "/1e464b19cdcde/774c88d68202/86694923d5bf28a/in/flow" -#define FLOW_INPUT_NAME "/climate" + +/** Put your publish key here. If you don't have one, "demo" is the default + public key. But, it has limitations. + */ +#define PUBNUB_PUBLISH_KEY "demo" -// Unless you want to use a different protocol, this field should be left as is: -#define FLOW_URL_TYPE " HTTP/1.1\r\nHost: " +/** Put your subscribe key here. If you don't have one, "demo" is the default + public key. + */ +#define PUBNUB_SUBSCRIBE_KEY "demo" -// This identifier specifies with which FLOW device you are communicating. -// If you only have one devive there then you can just leave this as is. -// Once your FLOW device has been initialized (Virtual Device Initialize clicked), -// the Virtual Device will show up in M2X. This is its "DEVICE SERIAL" field -#define FLOW_DEVICE_NAME "vstarterkit001" +/** Define the Pubnub channel to use here. For the "demo/demo" keys, a well-known + channel is "hello_world", but you can use any you like, channels are dynamic + on Pubnub +*/ +#define PUBNUB_CHANNEL "hello_world" + +// This identifier specifies a "device name" to be sent in the JSON message. +// You can also use it as the UUID, if you wish. +#define THE_DEVICE_NAME "vstarterkit001" // This constant defines how often sensors are read and sent up to FLOW #define SENSOR_UPDATE_INTERVAL_MS 5000; //5 seconds