Skip to main content

[IoT Home Project] Part 5 - Send data to Azure IoT Hub, control time interval and refac the configuration information

In this post we will discover how we can:
  • Send all device sensor data that are read from GrovePI to Azure IoT Hub
  • Read sensor data at a specific time interval
  • Extract all configuration data in a separate file

Send all device sensor data that are read from GrovePI to Azure IoT Hub
This is a simple task. The function that reads sensor data from GrovePI already returns all the sensor data. The only thing that we need to do is to put this information in the message that is send to Azure IoT Hub.
In the future it is pretty clear that we will have different type of messages that we send over IoT Hub. Because of this we shall add a property to the message that is send to IoT Hub that specifies the message type - in our case we'll call the message that contains sensor data 'sensorData'.
var dataToSend = JSON.stringify({
    deviceId: "vunvulearaspberry",
    msgType: "sensorData",
    sensorInf: {
        temp: sensorsData.temp,
        humidity: sensorsData.humidity,
        distance: sensorsData.distance,
        light: sensorsData.light
    }
});
deviceCommunication.sendMessage(dataToSend);

Read sensor data at a specific time interval
In this moment we have a 'while(true)' that reads sensor information and send data to IoT Hub. This works great, but what if we want to control how often data is read.
To be able to do this, we can use 'setInterval' function from node.js. This function allows us to specify a time interval when a function is called. The time interval is specified in milliseconds. 
The nice thing is that the functions will not be executed in parallel if the first call didn't finished yet. This is important when we specify a small time interval like 100 ms and the read sensor information and send data operations takes more than 100 ms.
function collectSensorData(grovePiSensors, deviceCommunication) {
    var timeIntervalInMilisec = 5000;  // 5s
    setInterval((grovePiSensors, deviceCommunication) => {
        var sensorsData = grovePiSensors.getAllSensorsData();

        var dataToSend = JSON.stringify({
            deviceId: "vunvulearaspberry",
            msgType: "sensorData",
            sensorInf: {
                temp: sensorsData.temp,
                humidity: sensorsData.humidity,
                distance: sensorsData.distance,
                light: sensorsData.light
            }

        });
        deviceCommunication.sendMessage(dataToSend);
    }, timeIntervalInMilisec, grovePiSensors, deviceCommunication);
}

Extract all configuration data in a separate file
In this moment we have configuration data in multiple modules. If we want to change something, we need to search where the configuration is stored, some information like device id string is duplicated.
The code is not so nice and a change can be buggy and time consuming.
To avoid all this problems, we ca create a config.json file in our application where all configuration data is added. For each module I prefer to create a section where I group specific configuration for that that module ('deviceCommunicationConfig' and 'grovePiConfig').
{
    "debug" : true,
    "sensorDataTimeSampleInSec" : 5,
    "deviceCommunicationConfig":
    {
        "deviceId" : "vunvulearaspberry",
        "azureIoTHubMasterConnectionString" : "HostName=vunvulear-iot-hub.azure-devices.net;SharedAccessKeyName=iothubowner;SharedAccessKey=+whKMyd08PLDNoaR+yEmToJcHL6wsFo36tAyDBU8Qr0=",
        "azureIoTHubHostName" : "vunvulear-iot-hub.azure-devices.net"
    },
    "grovePiConfig":
    {
        "dhtDigitalSensorPin" : 2,
        "ultrasonicDigitalSensorPin" : 4,
        "lightAnalogSensorPin" : 2,
        "soundAnalogSensorPin" : 0
    }
}

Once we have all this configuration, we will need to access it. For this we can load the JSON in our application and access the properties of the configuration file.
var Config = require('./config.json');
...
var grovePiSensors = new GrovePiSensors(Config.grovePiConfig);
...
this.debug = debug;
this.registry = AzureIoTHub.Registry.fromConnectionString(Config.deviceCommunicationConfig.azureIoTHubMasterConnectionString);
this.deviceId = Config.deviceCommunicationConfig.deviceId;
this.azureIoTHubHostName = Config.deviceCommunicationConfig.azureIoTHubHostName;

In each module we don't need to specify all the configuration file. We can only specify the section that is specific to that module ('Config.deviceCommunicationConfig'). For this you can take a look in the source file.

Conclusion
Mission complete for now. See push all sensor data to Azure IoT Hub and we have the flexibility to change configuration more easily. Additional to this we have control on how often data is pushed to Azure IoT Hub.

Next Step
In the next post we will start to store the data that is pushed to Azure IoT Hub to blobs. On top of this we will take a look on how we can calculate the average values for read data.

Next post: [IoT Home Project] Part 6 - Stream Analytics and Power BI

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP