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.