Skip to main content

[IoT Home Project] Part 9 - Extending Azure Function to support Thieves Alarm

In this post we will discover how to
  • Crunch distance (sonar) information produced by a GrovePI sensor and send using Raspberry PI and Azure IoT Hub to backend
  • Add filters on top of Service Bus Topic Subscriptions to receive only information related to distance and temperature on each subscription
  • Add new functionality to the current portal to be able to display alarm and notify our user
In this moment we have a system that is able to collect metrics from Raspberry and process some of the data. We already have from GrovePI a sensor that calculate the distance from the sensor to an object. Why not to use it to detect is something is moving in front of it and create a simple alarm system.
Yes, this is not the best sensor that we could use, although this scenario is a great method to learn something new.

Previous post: [IoT Home Project] Part 8 - Connecting to Azure Function and to a virtual heat pump
GitHub source code:

What we have until now
We already developed a system that sends data from our sonar (distance sensor) to Azure IoT Hub. From there there is a Stream Analytic job query that push our data to Service Bus Topic. It means that we already have all that we need in Azur and we just need to interpret data and create a notification system.
Below is an overview of the components that are involved, where green border marks a component that needs to be developed.

Filter messages on Service Bus Topic per Subscription
The base concept is to add a filter on each subscription, that would allow only specific messages to pass through. The filtering concept is very powerful and allows us to remove message filtering on the consumer side - being sure all the time that a subscriptions has only specific types of messages.
Unfortunately, there is no support in this moment on Stream Analytics that allow us to set the message properties. When we are sending messages from Stream Analytics to Service Bus, we can specify only the body of the message.
We could find workarounds to it, like using Service Bus Queues or adding an Azure Function between Stream Analytics and Service Bus Topic, that would add the required properties.

Crunch sonar information
This step is done in a similar way as we already done for heating system. The only difference is that in his case we compare the value that is coming from Raspberry PI and compare it with a predefined value.
When we detect that the measured distance is lower than our threshold value we trigger the alarm, by updating a field in Azure Table.
module.exports = function (context, mySbMsg) {
     context.log('Message:', mySbMsg);
    var azure = require('azure-storage');
    var tableSvc = azure.createTableService();
    tableSvc.createTableIfNotExists('systemstatus', function(error, result, response){
                var motiondetectoron = "false";
                if(mySbMsg.avgdistance < 10)
                    motiondetectoron = "true";
                var entityToUpdate = new Object();
                entityToUpdate.PartitionKey= "system";
                entityToUpdate.RowKey = "motiondetectoron";
                entityToUpdate.Status = motiondetectoron;

                tableSvc.insertOrReplaceEntity ('systemstatus', entityToUpdate, function(error, result, response){
                    if(!error) {
                        context.log('motiondetectoron: ', mySbMsg.avgdistance);

Add new functionality in current portal to support Alarms
Similar to heating system, we will use the existing REST API that read data from Azure Table to check if an alarm was triggered. If yes, we will display a custom message on the portal.
    <div @*class="col-md-3" *@>
        <h2>Thief Alarm</h2>
            Alarm status: <b id="thiefAlarmStatus">@(Model.AlarmStatus? "ARMED" : "ACTIVE")</b>
            <img id="thiefAlarm" src="~/images/@(Model.AlarmStatus?"house-alarm.jpg":"house-secure.png")" height="200" />

What to remember

  • There is no support to specify message properties for Azure Service Bus from Azure Stream Analytics


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…