0

We have a Gateway device which is registered in IoT central application. This gateway device is connected to multiple similar Sensor devices such as Philips hue bulbs via ZigBee. We are sending telemetry from sensors to IoT central via simple JSON

{"mac":"<mac address>","illumination":"200","bulb_status":"1"}

In IoT Central, we have registered our Gateway device as the IoT device with a device template which has telemetry properties related to Philips bulb and other sensors as well.

Now the challenge we are facing is, how to differentiate the data that is being sent by Philips bulb in room1 and Philips bulb in room2 in the IoT central as we have only 1 device registered in IoT Central.

The JSON has similar properties for both the bulbs and the telemetry values in IoT Central are being replaced by whichever device sends the last message.

Please provide me with the correct scalable approach for this kind of scenario.

Note: Consider our gateway device can't run IoT Edge runtime as of now. So we can't use it as Edge device.

Hariharnath Paduchuru
  • 137
  • 6
  • Is your goal to see every lamp/sensor as a separate device in IoT Central, or do you want 1 device in Central that shows all the lamps/sensors? – Matthijs van der Veer Jul 17 '20 at 12:16
  • Yes, our goal is to have 1 device registered in IoT Central which shows all the lamp/sensors uniquely according to mac address or any identifier.in the dashboard – Hariharnath Paduchuru Jul 17 '20 at 12:39
  • @HariharnathPaduchuru, you can try the following: add a *Location* property with a *Geopoint* schema to the Capability type *Telemetry*. Assigned for each your lamp/sensors an unique location value. – Roman Kiss Jul 17 '20 at 15:53
  • @Roman Kiss, If we add location property to the device we have,wont the location telemetry values be overlapping in the iot central dashboard tile of the device as iot central dashboard is not allowing to differentiate sensors of the same device. I would be having only one tile created for this sensor and the values from same kind of sensors keeps on overlapping on this – Hariharnath Paduchuru Jul 18 '20 at 10:24

2 Answers2

1

There are two ways to tackle this. The first would be to program your gateway device to supply an identity to each of your bulbs. This means all your lamps will become a separate device in IoT Central (and you will be charged for them). Your gateway device will need to have the connection details for all of the devices it is sending telemetry for.

A second (not so pretty) way is to add a telemetry point to your interface for each lamp. So instead of brightness you would have lamp1_brightness and lamp2_brightness. I'm only including this in my answer because it is feasible and will result in seeing dashboard per lamp in IoT Central. It does not scale well either.

Eventually Azure IoT Edge will support Identy Translation, which can solve this and other questions

Matthijs van der Veer
  • 3,865
  • 2
  • 12
  • 22
0

I have put up an E2E example of Nano BLE devices with data captured via a Central Gateway based on a Raspberry Pi using the Azure IoT Python SDK. This example is "in-progress", but I think you might find two files useful...

Main Project https://github.com/Larouex/IoTCRaspberryPiProtocolTranslationGateway

BLE Project https://github.com/Larouex/IoTCNanoBLESense33

File you might want to check out...

scandevices.py

https://github.com/Larouex/IoTCRaspberryPiProtocolTranslationGateway/blob/master/scandevices.py

This script uses BLEScan to find the BLE devices matching a naming pattern and writes them to a configuration file.

provisiondevices.py

https://github.com/Larouex/IoTCRaspberryPiProtocolTranslationGateway/blob/master/provisiondevices.py

This script and associated class use the Azure IoT SDK for Devices to read the devices in the configuration file and provision them in Azure IoT Central. The current code does a transparent approach and uses the identity of the BLE Device to provision and looks like a real device in Iot Central.

Over the next couple weeks I will continue to add the other scenarios like Opaque and Protocol Translation (which looks like the scenario you are interested in).

You may want to consider your differentiations of the Hues by modeling the locations and separate the telemetry values (versus plotting mac addresses), but you will hit some brittleness in versioning as you add or try to delete bulbs.

I recommend identify translation and associate each bulb with a model. Use the Device Groups for aggregate views. Then device properties because useful for location, etc.

Larouex
  • 31
  • 2