Azure Stream Analytics saving lives!

Solenoid Troubleshooting

After fitting I realized that my solenoid was leaking gas. I open it up and discovered hole in its disk. A little super glue fixed it.

use teflon tape and cotton thread to seal it

use two wrench to protect the plastic

This is how I tested it for leaks

Notice the flyback diode soldered directly on terminals

the problematic hole

the problematic hole

3D Printing

I needed a mount for flame sensor so that I can adjust it for best view of flame without getting lot of heat. 3D printing solved that issue. In addition the flame sensor needs to be protected from ambient sunlight. I 3D printed a cover for that purpose.

LCD mount was needed to raise it close to cover for easier readout.

Models to print

 Printing flame sensor mount

printing in progress

 Mounting flame sensor

Installing the mount

 Flame sensor cover back

 Flame sensor cover front

 Installing Flame sensor cover

 Installing Flame sensor cover

LCD mount

LCD is running screensaver. The code is part of my Sketch just not enabled in the final version.

Azure Cloud Setup

In order to run the applications you will need to do the following:

• Create an IoT hub that will receive data from devices and send commands back to it

• Create pair of Event hub and Stream Analytics job that will read data from the IoT hub and post alerts into the Event hub

• Create another pair of Stream Analytics job and Event hub for bridging controllers and devices.

• Create a Storage account that will be used by the worker roles.

• Deploy worker roles that will read alerts from the Event hubs and forward alerts to devices through the IoT hub and send Tweets.

Create an IoT Hub

• Log on to the Azure Portal.

• In the jumpbar, click New, then click Internet of Things, and then click IoT Hub.

• In the New IoT Hub blade, specify the desired configuration for the IoT Hub.

• In the Name box, enter a name to identify your IoT hub. When the Name is validated, a green check mark appears in the Name box.

• Change the Pricing and scale tier as desired. This application required a paid tier that allows multiple devices.

• In the Resource group box, create a new resource group, or select and existing one. For more information, see Using resource groups to manage your Azure resources.

• Use Location to specify the geographic location in which to host your IoT hub.

• Once the new IoT hub options are configured, click Create. It can take a few minutes for the IoT hub to be created. To check the status, you can monitor the progress on the Startboard. Or, you can monitor your progress from the Notifications section.

• After the IoT hub has been created successfully, open the blade of the new IoT hub, take note of the Hostname, and select the Key icon on the top.

• Select the Shared access policy called iothubowner, then copy and take note of the connection string on the right blade. Also take note of the Primary key

• Your IoT hub is now created, and you have the Hostname and connection string you need to update in software.

• For the creation of the Stream Analytics job Input, you will need to retreive some informations from the IoT Hub:

• From the Messaging blade (found in the settings blade), write down the Event Hub-compatible name

• Look at the Event-hub-compatible Endpoint, and write down this part: sb://thispart.servicebus.windows.net/ lets call this one the IoTHub EventHub-compatible namespace

• For the key, you will need the Primary Key read in step #6

Create two Event Hubs

• Log on to the Azure Management Portal.

• In the lower left corner of the page, click on the + NEW button.

• Select App Services, Service Bus, Event Hub, Quick Create

• Enter the following settings for the Event Hub (use a name of your choice for the event hub and the namespace):

• Event Hub Name: “myeventhubname”

• Region: your choice

• Subscription: your choice

• Namespace Name: “mynamespacename-ns”

• Click on Create Event Hub

• Select the mynamespacename-ns and go in the Event Hub tab

• Select the myeventhubname event hub and go in the Configure tab

• in the Shared Access Policies section, add a new policy:

• Name = “readwrite”

• Permissions = Send, Listen

• Click Save, then go to the evnet hub Dashboard tab and click on Connection Information at the bottom

• Write down the connection string for the readwrite policy name.

Create two Stream Analytics job

• Log on to the Azure Portal.

• In the jumpbar, click New, then click Internet of Things, and then click Stream Analytics Jobs.

• Enter a name for the job, choose your subscription, select the same resource group you created when creating the IoT Hub, Select the location, and click on Create.

• Once the job is created, click on the Inputs tile in the job topology section. In the Inputs blade, click on Add

• Enter the following settings:

• Input Alias = “gassense”

• Type = “Data Stream”

• Source = “IoT Hub”

• IoT Hub = “myiothubname” (use the name for the IoT Hub you create before)

• Shared Access Policy Name = “iothubowner”

• Shared Access Policy Key = “iothubowner Primary Key” (That’s the key you wrote down when creating the IoT Hub)

• IoT Hub Consumer Group = “” (leave it to the default empty value)

• Event serialization format = “JSON”

• Encoding = “UTF-8”

• Back to the Stream Analytics Job blade, click on the Query tile.

• The Query of gas sensor check and tweet job will be:

SELECT
  *
INTO
  gassense4phone
FROM
  gassense
WHERE
  gassense.gassense > 1500

• Back to the Stream Analytics Job blade, click on the Outputs tile and in the Outputs blade, click on Add

• Enter the following settings then click on create:

• Output Alias = “gassense4phone”

• Source = “Event Hub”

• Service Bus Namespace = “mynamespacename-ns

• Event Hub Name = “myeventhubname”

• Event Hub Policy Name = “readwrite”

• Event Hub Policy Key = “Primary Key for readwrite Policy name” (That’s the one you wrote down after creating the event hub)

• Partition Key Column = “4”

• Event Serialization format = “JSON”

• Encoding = “UTF-8”

• Format = “Line separated”

• Back in the Stream Analytics blade, start the job by clicking on the Start button at the top

• The query for the bridge job will simply be:

SELECT
*
INTO
gassense4phone
FROM
gassense

I also tried a Stream Analytics job to montor flame sensor with followin query:

SELECT
  *
INTO
  gassense4phone
FROM
  gassense
WHERE
  gassense.flamesense < 500

But end up not using it.

Please note that flame sensor value go down when it sees flame, while a gas sensor values go up when it smells gas.

Create a storage account

• Log on to the Azure Portal.

• In the jumpbar, click New and select Data + Storage then Storage Account

• Choose Classic for the deployment model and click on create

• Enter the name of your choice (i.e. “mystorageaccountname” for the account name and select your resource group, subscription,… then click on “Create”

• Once the account is created, find it in the resources blade and write down the primary connection string for it to configure the worker role

Deploy the worker role

Azure Worker roles are to trigger alerts through IoT Hub. To build and deploy the workers role here are the steps:

• Open the solution events_to_device_service.sln in Visual Studio 2015

• open the file app.config and replace the fields below with the connection strings from the event hub, the storage account and the Iot Hub

<add key="Microsoft.ServiceBus.ConnectionString" value="[EventHub Connection String]" />
<add key="Microsoft.ServiceBus.EventHubName" value="[Event Hub Name]" />
<add key="AzureStorage.AccountName" value="[Storage Account Name]" />
<add key="AzureStorage.Key" value="[Storage Account Key]" />
<add key="AzureIoTHub.ConnectionString" value="[IoT Hub Connection String]" />

Compile the project and publish to Azure

Create a new device identity in the IoT Hub

To connect your device to the IoT Hub instance, you need to generate a unique identity and connection string. IoT Hub does that for you. To create a new device identity, you can use Device Explorer tool (runs only on Windows for now)

Software

You need to install the following features in order to build and run the application and Azure web role projects.