A Yoctopuce web based app to draw sensors graphs

A Yoctopuce web based app to draw sensors graphs

The Yoctopuce business model is rather simple: Yoctopuce designs, manufactures, and sells electronic modules, provides the libraries necessary to exploit them, as well as support to help customers realize their projects. However, Yoctopuce doesn't provide turn key solutions. Nevertheless, Yoctopuce support regularly receives requests of the type: "How can I display a graph with the values of a Yoctopuce sensor?", or "How can I obtain the values of a Yoctopuce sensor in the CSV format?". So we decided, once will not hurt, to offer you a ready to use application to trace graphs with the values of Yoctopuce sensors.


The proposed application is based on HTTP callbacks, which are available to the VirtualHub and to all the YoctoHubs. It is actually a PHP script that you must put on a PHP server. At a regular interval, each hub contacts the server to communicate the value of each sensor and the server stores them. Then you only need to connect yourself on the server with a simple web browser to obtain a nice representation of the data. You can configure the interface rendering with a few clicks: style, color, size, position of the graphs, and so on.

Principle of the application
Principle of the application

The advantage of this architecture is that it allows you, among other things, to use a public server while keeping the sensors safely behind a NAT filter.


To trace nice graphs from your Yoctopuce sensors, you need:

  • Yoctopuce sensors, note that the application can also display the input state of YAnButton and YRelay.
  • A YoctoHub, you can choose among:

  • A PHP server, you can either

    • Use a pre-existing web hosting service to which you have access
    • Use a free host, at your own risk.
    • Install a web server such as MAMP or EasyPHP on one of your local machines

  • A web browser, never mind the platform or the operating system

Note that you don't need a database: to be as easy to install as possible, the application uses a file system to store the sensors data.


The application is designed to be as easy to install as possible. You only need a few PHP files that you can find here or on GitHub. There are 7 files: index.php, yocto_api.php, yocto_anbutton.php, yocto_network.php, yocto_relay.php, yocto_wakeupmonitor.php and yocto_wakeupschedule.php. Only index.html is new, the other ones are simple copies of those found in the PHP library.

To install the application, you only have to:

  1. Copy these files on your server, preferably in a sub-directory.
  2. Create a data sub-directory at the same level.
  3. That's it.

For purposes of demonstration, let's imagine that we copy these files on the www.yoctopuce.com web server in the YoctoCloud sub-directory. The result should more or less look like the image below:

Simply copy the files on your web server and create a data sub-directory
Simply copy the files on your web server and create a data sub-directory

Note that the server is going to create files in the data sub-directory, so make sure that the server has write permissions on this sub-directory.


Hub configuration

We are going to suppose that you want to use a VirtualHub to send the data of a Yocto-Meteo on your server, but the configuration of a YoctoHub would be exactly the same. Make sure that your VirtualHub is actually running and connect yourself to it with a web browser. The address is usually Open the configuration window and edit the Callback URL parameter in the outgoing callback section. Select a callback of the type "Yocto-API callback" and enter the URL of the index.php script. In our example it is www.yoctopuce.com/YoctoCloud/index.php.

Configuration of the callback
Configuration of the callback

When you have entered these parameters, simply click on the test button. You should obtain a message ending with "Done." as on the screenshot below.

It works
It works

If you obtain the message "url_fopen is not allowed, please fix server configuration.", create at the level of index.php a file named ".htaccess" containing the line:

php_flag "allow_url_fopen" "On"

If the .htaccess file already exists, don't erase it! simply add the line above in it. When it works, close the test window and save the configuration. That's it, the hub configuration is done. Note that you can configure as many hubs as you want on the same callback.

Application configuration

With a web browser, connect yourself on the server. In our example, the URL is www.yoctopuce.com/YoctoCloud/index.php?edit, note the ?edit at the end. Click on the "Got It" button and you obtain an empty page with a red menu on the top left. In this menu, select "new chart", and an empty graph appears in the middle of the page:

New graph
New graph

In the top left of the graph, there is an "edit" button which enables us to configure this graph: click on it to display an interface on the left of the page. This interface is composed of 4 sections:

  • Window, to modify the size, the position, and the appearance of the frame surrounding the graph
  • Data set, to define the lines displayed in the graph
  • Vertical axis , to define one or several vertical scales to be used
  • Legend, to display a legend, if need be.

All these options enable you to select almost all the aspects of your graph. Changes are applied in real time, playing with the options should enable you to understand the effect of each parameter. If you leave the mouse idle a few seconds on a parameter, a short description pops up. The minimal required action to configure your graph is to select the sensor to be displayed through the Data src parameter in the data sets section. Each "data src" corresponds to a channel of a Yoctopuce sensor.

Graph configuration
Graph configuration

You can define as many graphs as you wish, you can have up to 3 lines per graph. This limit is defined by a constant at the beginning of the source code, you can easily change it if need be.

Texts and variables

You can also define text blocks containing variables automatically taking the values of the sensors. You can define these text blocks in the main menu "New../Text block". Each text block can contain up to 6 distinct variables defined as {$1} to {$6}. You can define the different characteristics of the text blocks in the same manner as for the the graphs.

You can define text blocks
You can define text blocks

You'll soon notice that the interface panels tend to overlap parts of the screen that you are interested in. You can make them switch from one side to the other by clicking on the ↹ icon.

When you have configured your different items, reload the web page without the "&edit" parameter on the URL, which makes the configuration interface disappear.

You can configure almost everything without having to write a single line of code
You can configure almost everything without having to write a single line of code

The feeds

The system is based on the concept of feeds. A feed is a simple identifier which allows you to define a set of sensors to be displayed on the same page. This enables you to use the same script to display distinct sets of sensors. By default, the name of the feed is "default", but you can define other ones. You only need to define it on all the URLs used by the system. For example, if we want to define a set of sensor under the "mydata" name, the distinct URLs are:

  • www.yoctopuce.com/YoctoCloud/index.php?feed=mydata for the HTTP callback
  • www.yoctopuce.com/YoctoCloud/index.php?feed=mydata to view the interface
  • www.yoctopuce.com/YoctoCloud/index.php?feed=mydata&edit to edit the interface


On top of displaying graphs, the application also allows you to

  • Remotely define the HTTP callback frequency
  • Remotely define the wake up parameters of the YoctoHub-Wireless
  • and of the YoctoHub-GSM
  • Display the raw data of the sensors and to download them in the CSV format
  • Define a policy to erase the oldest data

Important remarks

We looked at all the main characteristics of this application, we only need to conclude with some remarks:


This application offers no authentication method. If you install it on a public server, we recommend that you protect its installation directory with a user name and a password. Usually, hosting providers have an interface allowing you to do so in a few clicks. Beware, you must then also indicate the user name and the password in the callback configuration of the hub.


This application was coded to be easy to install and easy to use, not to be scalable. You can easily manage about one hundred sensors. But if you have thousands of them, you should think of using a better suited commercial cloud solution, such as VALARM.


This application is based on the excellent Highstock library, published by HighSoft, which is free only for a non commercial use. If you intend to use this application to earn money, directly or indirectly, we suggest that you carefully read the Highstock terms and conditions and that you get a license. Trust us, these people have done a fantastic job and have earned their money.

1 - andr59 Friday,january 05,2018 20H08

Thank you! Great and very usefull job! Now i can forget Xively. one question, if it is possible, i want see pressure in mmHg. How can i do it?

2 - martinm (Yocto-Team)Saturday,january 06,2018 7H32

@andr59 : right now, you can't. The unit is automatically retrieved from the device. For this to work, we'll need to add mmHg support to the device firmware. Just contact support and appeal your case :-)

3 - andr59 Tuesday,january 16,2018 12H08

Good day! Tell me, please, how can i join data from yocto wireless and yocto ethernet in one web page. Or, may be, i have to use the second web page. F.e. Yoctocloud_1 for the second sensor. Thank you!

4 - martinm (Yocto-Team)Tuesday,january 16,2018 12H39

@andr59: it supposed to work out of the box, as long as you use the same callback URL for both YoctoHubs. Just contact support if you need more help.

5 - andr59 Tuesday,january 16,2018 13H51

I tried to use the same callback url for my METEOMK1-0B700 and METEOWLN-0C8FD - http://my webserver ip:my port/YoctoCloud/index.php.
METEOMK1 - work fine, but METEOWLN responsed - failed to connect.
Thak you foe any help!

6 - martinm (Yocto-Team)Tuesday,january 16,2018 15H03

@andr59: METEOWLN-0C8FD is a 5 years old beta-test unit for a device we never put on market, the firmware is probably too old/ too bogus to work with HTTP callbacks. You are out of luck with this one.

7 - andr59 Tuesday,january 16,2018 18H26

Thank you for answer, but this old device worked via Xivelly. I don’t know, may be it is different technology?

8 - mzubairsaleem Thursday,february 22,2018 20H44


I want to know if I'm already getting data in JSON format how can i use this server to plot graphs for me.

Thanks, any help will be appreciated.

9 - martinm (Yocto-Team)Friday,february 23,2018 7H27

@mzubairsaleem: As per Yoctopuce General Terms and Conditions, Yoctopuce software is supposed to be used with Yoctopuce hardware only. However, since the Yocto-Cloud source code is available on GitHub and as long you do it for your own personal use, you can do whatever you want with it. But don't expect us to help you with such a project.

10 - obseus Sunday,october 20,2019 17H44

Generating the YesIKnowThatHighStockLibraryIsNotFree.txt next to index.php doesn't remove the nag-message. "Next to" means probably in the same directory, right?
Is there any other way to get rid of that message?

11 - martinm (Yocto-Team)Monday,october 21,2019 5H21

@obseus: I just checked, it does work properly. Yes, you have to put it in the same directory as index.php. Make sure there is no typo in the file name, if you use copy/paste, make sure there is no extra spaces characters. Also make sure the file permissions and owner will allow PHP to see the file.

12 - mtf Saturday,december 03,2022 11H27

This is a great solution, and the ability to self-host is a game changer compared to many other sensor/gateway manufacturers.

However, the solution is hard to put into production and to promote among clients/collaborators without https support. Do you plan on adding this feature in the future?

I've had trouble with the HTTP authentication. Should we fill the password field in the Hub configuration with the actual password, or the base64 hash? I assume it requires the real password, but the callback test fails all the time. I'm using Caddy as my webserver, but I could confirm that the authentication setup on the server side is working by manually logging into it when browsing to that URL and filling my credentials. Does the YoctoHub try to reach the server using an URL in the form http://user:pass@domain.tld/index.php?

The data seems to be stored into binary files on the server. Is there a way to translate those into plain text?

Finally, my YoctoHub doesn't always succeed getting network and transferring the data. When it fails to transmit it, the data seems to be lost. Is there a way to make sure failed transmissions are stored locally in the hub (or its attached sensors) and are transmitted with the next connection attempt with the new data points?

13 - mtf Saturday,december 03,2022 12H25

Following my post above, I just found out about the new article on VirtualHub for Web, which may solve several of the issues I mentioned above, plus allow aggregating data points before transmitting them at a lower frequency then the recording frequency. I'll try to move to it instead of the legacy Yocto-API HTTP Callback.

14 - martinm (Yocto-Team)Sunday,december 04,2022 3H55

@mtf : the CPU used in the current YoctoHubs generation is not powerful enough to offer HTTPS connections. But we are working on a new generation with this requirement in mind. Don't ask for a release date, we don't have any :-)

However, while waiting for the YoctoHubs V2, you can use the VirtualHub V2 running on a baby-PC as a alternate solution.

Regarding your other questions, you should contact Yoctopuce support directly.

Yoctopuce, get your stuff connected.