DevicePilot is now responsive on mobile - this means you'll get a view of your dashboard in a clean, mobile-friendly view.
We've just worked on dashboards for now. Let us know which area you think we should work on next.
Along with this, we have a few other small enhancements to make life easier:
In the Cohort page, we now save the time range for KPIs as part of its definition. If you've used the KPI in a dashboard widget, then we've set the time to that, otherwise it's the default 24 hours. For now, you can still override that time in the widget.
We've also fixed a number of minor issues with selecting time, devices and properties in the View page - all to make it easier.
You can now add a comparison to a previous period in any KPI that is grouped by time. You can compare Day on Day, Month on Month, Quarter on Quarter and Year on Year.
You have three ways to display this:
One for the advanced users here. In the Cohort page, you can now use an expression instead of just a property in your metric definition. The syntax supports simple expressions with mathematical operators.
You can now show single value dashboard widgets as a gauge.
This is particularly suitable for values with expected ranges - you can specify the min and max and quickly visualise whether the value is expected. For percentage KPIs, we also use the RAG colours.
You can can setup a map widget with your KPI on your dashboard. Open the widget settings and choose the KPI.
In the View screen, when using our new KPI visualisation feature, you can toggle the RAG (Red Amber Green) bands off so you can focus on the devices your are interested in. You can also simply toggle off the devices that are either 100% or 0% working, since these also may be of less interest.
You can configure your RAG levels in the Cohort page, and we'll use then in the dashboard widgets and in this new View legend
We can now connect directly to your Google Cloud IoT Core instance, with no code for you to write. The process involves you creating a key in Google Cloud, and we take you through the process step-by-step. For more details, see How do I connect to Google Cloud IoT Core?
When analysing a KPI in view, we now display a timeline view showing the history of the KPI under analysis, just for the selected device. For more details, see View Timeline.
We have also updated our Google login buttons to match their new, strict brand guidelines.
You can now stream data directly from Azure IoT Hub, with an extremely simple setup. Read more about it here: How do I connect to Azure IoT Hub.
We'll continue to build more direct integrations - next up Google Cloud IoT Core.
From today, you can now see your KPIs down to the device level in View. This enables you to quickly see the worst performing devices and analyse those ones first.
You can select the KPI to analyse from the picker, or alternatively, you can drill down from a dashboard widget to open this view.
See Visualising your data for more details.
Some of our customers have data coming from in-building sensors. In those cases, even if the Google maps have good indoor coverage, they asked us to be able to draw data on top of a floorplan image.
So now, in the dashboard, you can add and configure this widget to show your devices like this:
A small thing, but important to make nice dashboards. The default behaviour of our map widget is to zoom to fit the extents of the data each time we update. Some of you told us that you would prefer to be able to set the boundaries of the map and have them fixed.
Now, when in edit mode on the Dashboard, you'll see that you can lock the view. This will remove the zoom icons and mean your view will stay as it is.
This is a feature for those with devices that move around. In the map, you can toggle between showing:
The big green dot is the latest location of the device.