This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 12%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESJ%3C/text%3E%3C/svg%3E)
In my use case, I have a device worn by personnel that is Bluetooth enabled. As the person walks through the building I want his device to connect to BT-enabled IoT edge devices in protocol translation mode to upload telemetry data.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Hello @Stimpson, John Welcome to Microsoft Q&A Platform and thanks for your query. Community SME's on this topic or our team will review your scenario and circle back at the possible earliest time.
Meanwhile please go through the below document section:
Create a gateway hierarchy:
Hello @Stimpson, John ,
You are not doing transparent proxy, you need Identity translation:
This is something you have to create yourself:
What we are thinking is to manage the leaf devices decoupled from Azure IoT ecosphere the edge would be the only device.
Hello @Stimpson, John ,
Azure IoT supports this concept of leaf/child devices in combination with an edge. These child devices can only be attached to one edge device (parent). I'm not aware of any limitations (except for possible network address limitations).
Still, this is the transparent proxy scenario (so there is a certificate trust between parent and child during the communication).
You don't need that because you have this BT LE protocol switch.
You probably have to build your own 'bee-hive' of device clients for each azure IoT Hub IoT device to want to let communicate. This communication is not sent by the edgeHub, you have to make a connection for each device so you also need the credentials of each device locally.
As an alternative, this logic could be moved over to the cloud with eg. some Azure Function listening to IoT HUb messages and sending messages to the IoT HUb from there....
Just to make sure we both are on the same page.
**Transparent proxy or Transparent **
child devices connecting to edgeGW in Transparent mode can only be in a 1/1 relationship. A child cannot be associated with more than one edge at a time. Each child can only connect to a gateway via WIFI or LAN. Based on MS documentation each edge can only support about 100 clients.
In my case my child devices can only talk bluetooth and cannot support the IoT Device SDK, so based on the documentation I can only use protocal translation gateway.
I cannot find out any limits on protocol translation gateway
Identity translation gateway allows you to combine the downstream device and protocol translation to create an identity for the child. This again creates a relationship between the child and gateway and does not allow a roving BLE child to connect to the nearest gateway while walking through the building.
I drawing I provided above is about what we do today with a raspberry PI. We are looking at converting this PI to an Azure IoT device to better support the gateway with updates and trouble shooting.