It’s been a while since our last update, but worry not. We have been working on a brand new look and feel for the official HealthyPi GUI application. The new application uses the ControlP5 framework for the GUI and we think it looks great! Check out the short screencap below for the new application.
In one of our earlier updates, we had explained how the HealthyPi can be used to send data to an IoT platform and why you would want to do that. Following up on that, support for communication to a remote system using MQTT has now been added to the official HealthyPi application itself, without the need for anything else.
The Processing-based GUI application now has two new buttons at the top of the screen: one button to switch the MQTT client ON and OFF and one more to enter the MQTT settings, such as server name, security credentials and so on. These can be changed according to the requirements of your particular platform and application.
In this example, we use Adafruit’s awesome new io.adafruit.com platform. IO is Adafruit’s take on IoT. They have a free version as well as a paid IO+ version. The limitations in the free version are:
For this demo, we will send data to the cloud once every 5 seconds so that it falls within the free plan requirements.
The resulting Adafruit dashboard looks great. Below is an example dashboard showing 1 hour trends of heart rate, respiration rate, temperature, and SpO2.
This functionality is now available in the latest release and you just need to run the script to get the latest version.
curl -sS http://pi.protocentral.com/hpi3.sh | sudo bash
This will download and install the latest version of the HealthyPi GUI.
You can also download the latest release from our v2.0 release page on GitHub.
Some of the parameters for the MQTT library can be edited in the GUI “MQTT Settings” button itself, but more parameters such as feed name needs to be edited in the Processing code
If you have any suggestions, feature requests, bugs or anything else you would like to see in the HealthyPi or even contribute code to the project, please do so on our Github repo. We’d love to hear from you.