Included here is a script to be used for testing of the pipeline in the absence of a real device to connect.
Run with the following command:
.\sendsensordata.ps1 -Hostname "<IoTHubHostname>" -SharedAccessKeyName "iothubowner" -SharedAccessKey "<iothubownerSharedAccessKey>" -DeviceId "<deviceID>" -SendCount <numberOfMessagesToGenerate>Before running, you will need to complete a few steps:
- Make sure you have NodeJS installed (for IoT Hub Explorer and the message generation script)
- Make sure you have IoT Hub Explorer installed (requires NodeJS). This cli tool, among other things, allows you to simulate a device connected to your IoT Hub.
- Navigate to your IoT Hub in the Azure portal. Copy your hostname from the 'Hostname' field in the Overview tab and use it as the 'Hostname' parameter (e.g xxxxx.azure-devices.net).
- Open up the Device Explorer from the menu on the left and click the plus button to add a device. Assign it a device ID and leave the rest of the fields as shown below. Use the device ID you just created as the 'DeviceId' parameter.
- On the newly created device configure device twin properly
Example (weather decoder for a device located in Wallisellen/Zurich):
"tags": {
"sensorDecoder": "SensorDecoderWeather",
"sensorName": "Weather",
"location": "47.4086576,8.5914313,16"
},- Navigate to the Shared Access Policies tab on the left. Click on the 'iothubowner' policy and use the primary key displayed as the 'SharedAccessKey' parameter.
Once these steps are complete, you can run the script to generate as many messages as required for testing.
Note: This will generate static data (see getTestData.js for details), however the timestamp will update to match the current time for visualisation purposes.