Using a Scan to Config project

A Scan to Config project allows a user to scan a QR code with an Android device to configure the Velocity client with host profiles, global settings, scripts, or additional files. By default, the configuration files are hosted by the Velocity Console and sent over HTTP.

When you create a Scan to Config project, it should contain ALL of the files that the device needs. When the Velocity client applies a Scan to Config project, all other profiles (including the Demo profile) are erased. If there are other files in the Android/data/com.wavelink.velocity/files directory that are not included in the Scan to Config project, those are also erased.

The Velocity Console can act as a web server and host the files, or you can host them on your own web server.

Hosting the files on the Velocity Console is easy, but since it requires the Console application to be open and hosting, it may not be viable in all situations.

Hosting the files on a web server allows you to set up a certificate and secure the connection, and it also makes the files available at any time. It requires more work to set it up, though.

By default, the Console uses the hostname for the localhost that it can determine and picks a port. You can change the hostname to an IP address or change the port if there are conflicts or if you choose to host the project on a web server somewhere else.

The Version field allows you to track changes to your Scan to Config project. Increment the version number when you make changes to the project. To see which version of the Scan to Config project a device already has, tap the Scan to Config button in the Velocity client and find the version number at the top of the screen.