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(137.6, 70%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Hi, I have a simulated device on IoT Central. I was wondering if it's possible to change the range of the telemetry data? For example, having heart rate always stay between 90-100. I'm using the healthcare app template in IoT Central
![](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(214.4, 74%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
MUHAMMAD SALMAAN BIN AHMED NUSRATH Welcome to Microsoft Q&A forum!
Did you try creating a custom rules on a device data to trigger appropriate alerts?
You can create a new rule and set the condition for when the telemetry data for heart rate falls on the desired range (e.g. greater than 90 or less than 100)
Please check Create a rule and let us know if it helps.
![](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(19.2, 71%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
IoT Central doesn't expose any controls for the simulated devices it creates.
However, you could try setting maximum and minimum values for the heartrate telemetry in the device template - it's possible that the IoT Central uses these values when in creates a new simulated device. This is just a suggestion, you'll have to try it out to see if it works.
I've done a quick test - and it looks like the simulator does use the maximum and minimum values in the device template :). It appears to do this dynamically, so as soon as you publish an updated template, the simulated devices adjust themselves.