Visualize Sensor Data from IoT Devices in Bluemix

Recently I learned about a nice application to visualize data from sensors (and events) of your Internet of Things devices that you’ve registered with the IoT Foundation in IBM Bluemix. This can be useful to see live changes of your data and it’s also possible to see historical data. For me this is easier than navigating manually one by one through the last 10 events that are displayed in the IoT Foundation user interface and easier to read than debug nodes in Node-RED.

Read the documentation to find out more about the visualization app. The documentation currently describes that you have to build the app via Node.js locally but luckily there is a much easier way. Since the app is on GitHub you can also use the Bluemix Deploy capability to deploy the app in your Bluemix organization via one click.

Deploy the visualization app.

After this you can either enter an app key manually or just bind your IoT service to the app so that the credentials and registered devices are picked up automatically.

The screenshot below shows the data from a Texas Instruments Board.

There is also a promising experimental service IoT Real-Time Insights which might help with visualizing data (and more) but it seems to work for smartphone data only at this point.

3 thoughts on “Visualize Sensor Data from IoT Devices in Bluemix

  1. Justin Thomas says:

    Nice shortcut! I’ve set this up yesterday but can’t see my devices in the dropdown, yet in the NodeRed screen I can see all the incoming data, any hints what’s wrong? I’ve torn the thing apart looking for the problem – no joy!

    1. Niklas Heidloff says:

      Justin, sounds like an issue with this app. Not sure why it stopped working. You might want to use the Insights service which has similar functionality.

      1. Justin Thomas says:

        I found the solution in the end. Because the article is quite old (I suppose), it didn’t take into account the possibility that I might have deployed it to a different zone. I deployed to GB but for whatever reason it only works in US South. So now I have redeployed it in that region it’s now working properly!


Leave a Reply