Azure IoT Central
Microsoft IoT Central is a fully managed IoT SaaS (software-as-a-service) solution that makes it easy to connect, monitor and manage your IoT assets at scale, so you can create deep insights from your IoT data and take informed action. Microsoft IoT Central dramatically lowers the barriers of entry for companies looking to revolutionize their business with IoT.
-
Provide public dashboards
A nice feature for IoT Central in my point of view would be the option to share telemetry and status dashboards with a public audience.
In my scenario I'd like to share e.g. the dashboard from the applications home page to an audience in my organization where I don't want to give each user individual access to my application.
This would also be a nice feature because it would enable me to embed the dashboards into individual built applications aside to IoT Central which use the data collected by IoT Central.
6 votesThank you for taking the time to submit feedback. The functionality you’ve requested is something that we’re currently considering. We’ll follow up once we have more updates.
-Luis
-
Device originated timestamp
For a batch and forward device telemetry, it is important to use the timestamp from origin instead of ingestion. as a suggestion reserve a keyword, example "TimeStamp" and if the payload contains it, then run the TSI queries on this field.
5 votesYou can use ‘CreationTimeUtc’ property to set the date and time the message was created on a device. Due to a bug this value is not getting set properly at our end. We are working on a fix that will be available soon. If you are already using this property in your device code then you will not have to change anything for it to work once we release the fix.
Thanks,
Ankit -
Please provide advanced rules settings
Please provide more options for setting up rules e.g. on telemetry data.
In my case I wanted to set up a rule when a condition lasts over a certain timeframe. I haven't found a way to do this with IoT Centrals rules management.
Another pain point I noticed was when I set up a rule with a threshold that should send me an e-mail when the rule is triggered, my mail account was spammed with many mails for historical occurences of the trigger. So it would be helpful to have an option whether a rule should be triggered on historical…
3 votesWe are adding support for Aggregate functions and Time windowing in Rules that will enable monitoring telemetry over a certain timeframe before alerting.
I will update the thread once the feature is available to try out.
Thanks
Ankit -
Correct IoT Central Pricing FAQ
The example calculations in pricing FAQ for IoT Central (https://azure.microsoft.com/en-us/pricing/details/iot-central/) are confusing and should be corrected:
The example calculation under "How is Per Device Pricing calculated?" does not use the "official" rates given - e.g. for € it uses 1.655€ per device/mo instead of the official 1.7€ per device/mo and €1.242 per device/mo instead of 1.3€ per device/mo. Are the official rates not the actually used rates?
Also, the calculation for "How is additional message pricing charged?" seems to be incorrect:
First of all, the calculations do not use the 730hr/mo factor that is supposed to be used…2 votesThanks for bringing this to our attention. We are looking into it and will update the article with the corrections.
Thanks
Ankit -
Trigger event based on offline devices
So what would be great is if there was some way to detect when devices haven't "reported in" within a specific time span to be alerted to offline devices. I haven't found a way to do it but I may be missing something.
2 votesThank you for taking time to submit the feedback. We are considering this functionality and will follow up once we have further updates.
Thanks,
Ankit -
Dashboard with multiple devices, group by "tag or property"
Nice if I was able to group different devices (models) in a single view.
For example:
By store, I have 3 refrigerators, one coffee machine, and one couponing station2 votesHi Uri,
Thanks for taking the time to provide us with feedback. We’ll consider this as we plan our future investments. We’ll post updates here as we learn more.
Thanks,
Luis on behalf of the Azure IoT Central team -
Save measurements selection for future navigation
If I leave the "Measurements" view and return, I lost the selected fields and settings. It reverts to the first 4 elements in the payload always in average.
It is clear this view is fluid and dynamic, but nice if it was able to remember where I left it.
2 votesHi Uri,
Thanks for taking the time to provide us with feedback. I understand that the lack of state can be frustrating. We’re actively working to enhance this experience, so stay tuned for updates.
Thanks,
Luis on behalf of the Azure IoT Central team -
OTA firmware update
As an Admin,
I need to set up a blob to upload all my firmware and browse available versions (filter grid by date, description and version numbers)
I need to run some query to identify all the devices that are "out-of-version" using the Version property.I need to start a Job to command all the devices in the query to UpdateFirmware to a particular version:
The command has 3 parameters:
1) File Path
2) SAS readonly token (expires in 8 hours)
3) MD5 (or another cyclical signature)The firmware will be intelligent enough to understand the UpdateFirmware command and download…
2 votes -
Support devices use X.509 certificates. Currently only SAS tokens are supported
X.509 is supposed to be more secure than SAS token based security
2 votes -
Distributor Role, Vender Role, User Role for Azure IoT Central
I want to use Distributor / Vender / User Role on Azure IoT Central.
for each devices ownor scenario.When the devices ownor is distributer, who manage the devices,
monitor these status, support, fix, as administrator.
at this time,
Vender just monitor only their devices,
and build some type devices,
at this time,
User just monitor only their devices.
and use some devices from some vender.2 votesHi Yoshihiro – we’re actually working on improving the RBAC experience in IoT Central. We’ll post more updates as we get closer to finalizing the experience. Stay tuned. Thanks again for the feedback.
Thanks,
Luis on behalf of the Azure IoT Central team -
Support adding AAD groups to an application
I'd like to use AAD groups to grant users access to IoT Central instead of adding or removing each user individually.
2 votes -
1 vote
-
Disable chat window for ex. all operators
I want a rule to disable the chat for some usergroups
1 vote -
Language
Possibility to change language in IoT Central. At the Moment only english is supported
1 vote -
1 vote
-
Show Dirty Settings when desired and reported don't match
1) You are applying a nested branch format for desired properties in the device twin and it does not match the reported JSON, that constrains your device partners. Mesh suggests that desired and reported properties to be identical in format and no nested objects. Or add documentation for your device partners.
2) Regardless of format, mark the property as dirty if reported and desired don't match values. Use a red font color or background for example.
It is expected for some devices not to be ready to ingest the configuration and even if the desired properties handshake completes, the reported…
1 voteHi Uri,
Thanks for taking the time to provide us with feedback. This is good feedback, and we’ll consider this as we plan our future investments.
Thanks,
Luis on behalf of the Azure IoT Central team -
Chart for measurements is misleading, should use only the selected decimals
See the attached chart. The voltage fluctuated a little, and it is great that the chart can provide so much detail. but if the selection was only 2 decimals, then the expected chart is a flat line.
4.18Volts
1 voteHi Uri,
Thanks for taking the time to provide us with feedback. I can see how this could be misleading, we’ll take a look to see how we can address this. We’ll post updates here as we determine next steps.
Thanks,
Luis on behalf of the Azure IoT Central team -
Support measurements, events and states to formulate a device set conditions
The current implementation only supports adding properties to the conditions for Device-Sets.
We recommend to Support
Last Known Values, Event, and State in the query predicate.1 voteHi Uri,
Thanks for taking the time to provide us with feedback. We’ll take this into consideration as we plan feature roadmaps. We’ll post updates here as we determine next steps.
Thanks,
Luis on behalf of the Azure IoT Central team -
Jobs for all the devices in a Device-Set
In the Device-Set dashboard allow setting commands and properties for all the devices in the query.
Example reset all the devices where runtime > 600, or update the desired threshold = 5 where the Model is Freezer.1 vote -
Virtual State and Event
Allow adding state and event fields to the model, even if these don't originate from the device. When a rule occurs on any telemetry field an action set the desired value into these virtual fields.
Example: When Temperature > 80 Deg, Set the Virtual Event vTemperatureEvent = IntoAlarm and the vTemperatureState = "Alarm"
When the temperature drops back to 65, vTemperatureEvent = OutOfAlarm and vTemperatureState = Normal1 voteHi Uri,
Thanks for taking the time to provide us with feedback. This is great feedback and we’ll consider this as we build our feature roadmap. We’ll provide updates here once we make any determinations.
Thanks,
Luis on behalf of the Azure IoT Central team
- Don't see your idea?