VirtualHub version 2 finally emerges from its beta testing phase. After several years in development, we're releasing the first official version of VirtualHub-V2.
The first thing to notice is that we changed the name of the application and executables. We've decided to keep the same convention that we have with our modules, i.e. to add a suffix "-V2" to the product name. From now on, we'll refer to this new version of VirtualHub as VirtualHub-V2.
In the same way that the Yocto-Meteo-V2 is the successor to the Yocto-Meteo but remains compatible, VirtualHub-V2 is the successor to VirtualHub and offers the same functionalities but adds a series of new features such as
Other new features are still under development and should be announced in the near future.
Migration
The name change allows us to be clearer in our communications, but also to have both versions installed on the same machine without conflict. It's not possible to have both versions running at the same time, but you can switch from one to the other without any problem.
Executable names
We've also changed the name of the executables: the binaries are now called VirtualHub-V2. This allows you to have both versions in the PATH without conflict:
yocto@pi3:~ $ VirtualHub -version Version 1.11.8842 (Sep 5 2025 19:20:28) yocto@pi3:~ $ VirtualHub-V2 -version Version 2.1.9067 (Sep 16 2025 12:04:54)
Configuration files
Both applications have their own configuration files. In this way, parameter changes made on one version do not affect the other. The exception is the first run of VirtualHub-V2, which imports version 1 settings if a version 1 configuration file is detected. Thereafter, each version uses its own configuration files.
Under Windows, the configuration files are located in the C:\Users\username\AppData\Roaming\Yoctopuce\VirtualHubV2 directory. For Linux and macOS, files are stored in the ~/.virtualhubv2 directory.
Installation with APT
VirtualHub-V2 is now available on our APT repository. The package name is virtualhub-v2.
To use it, we need to add our repository to the machine.
wget -q -O - https://www.yoctopuce.com/apt/KEY.gpg | gpg --dearmor | sudo tee -a /usr/share/keyrings/yoctopuce.gpg > /dev/null echo 'deb [signed-by=/usr/share/keyrings/yoctopuce.gpg] https://www.yoctopuce.com/ apt/stable/' | sudo tee -a /etc/apt/sources.list.d/yoctopuce.list > /dev/null
When these two commands have been executed, VirtualHub-V2 can be installed with the following command:
sudo apt update sudo apt install virtualhub-v2
Windows installer
We've also added a Windows installer. Unlike version 1, which always installed the Intel 32-bit version, this new installer detects the machine's processor and installs the corresponding executable. This means that if you're using a Windows 11 machine with an ARM processor, the ARM version will be installed.
Downloads
All versions are available on the VirutalHub dedicated page: https: //www.yoctopuce.com/EN/virtualhub.php
Which version to use
Now that we've published VirtualHub-V2, which version should you use?
If you're starting from scratch, use VirtualHub-V2. This is the version on which we do our development and testing. It's also the most complete version, as it supports IPv6 and SSL/TLS.
If you're already using VirtualHub version 1, it all depends. If you find the new features useful, you can upgrade to VirtualHub-V2.
But if you want to stick with version 1, there's no problem. We're the first to criticize companies that stop supporting software to force migration to the new version. We will continue to maintain this version, and our modules will continue to work with this version.
