Visionect Software Suite Management Interface

Visionect Software Suite provides a graphical administration interface for managing your server deployment. The interface is accessible on port 8081 of your server (http://your_server:8081/). If it’s not, check your networking configuration (see: Networking and Security).

The default login username is admin and the password is admin123. We recommend that you change the password immediately after your first log-in.


Visionect Software Suite administration interface

The index page (Status sub-menu) gives an overview of the installation, such as the number of online devices, the Visionect Software Suite version, a list of registered HTML rendering backend services and their system load.

The servers load consists of two parts: average and deviation. The average load displays the average load of the server’s processor cores in the last 1 minute (i.e. average load would be ‘1’ if there’s 100% load on a single core) and is caused by active tasks. Deviation is the difference between 1 minute and 15 minute average load caused by active tasks.

Sessions active / maximum displays the current status about active sessions (the maximum value is set in Settings).

Managing a client device

All devices that connect to the Visionect Software Suite store their own data (device status, configuration and the device’s session) in the Network Manager. The device list can be sorted by name/UUID, battery level (%), state, signal strength, connection type, firmware or hardware revision.

A client device can be in one of the following states: online, offline, flashing, flashing complete, sleeping, charging, unavailable, sending or receiving. Current device status is displayed in the Devices sub-menu.

List of devices

The device page has four available tabs:

  • Status&Settings: the tab for changing the different settings of the selected devices. It is also possible to flash the selected device with a new firmware.
  • Device configuration: opens advanced device configuration for any supported and connected device.
  • Live View: shows what is currently displayed on the devices and shows the image of a session which might not yet have been deployed.
  • Charts: displays different charts for the devices selected.
  • Events: lists and displays different events (such as disconnects, reboots, displayed images etc.) that occurred while a device was connected.

Device overview - Status & Settings

The ‘Status&Settings’ sub-menu consists of different sections:

  • The ‘Status’ section displays general status information of the selected device together with an option to name it.
  • The ‘Sleep’ section consists of the Sleep Manager (if enabled) and manages sleep mode settings.
  • The ‘Session’ section consists of the choice of backend and application, the , automatic page reload option and other session-related settings.
  • The ‘Displays’ section includes different display related settings.

Live view feature


Charts example


Events example

The ‘Device management’ buttons at the bottom of the ‘Devices’ page manipulate the selected devices:

  • Pressing on the ‘Reboot device’ button will cause all the selected devices to reboot. The time it takes for the devices to reboot can vary.
  • Pressing on the ‘Restart session’ button will cause restart of WebKit services for all the selected devices, which means that the page will be reloaded.
  • Pressing on the ‘Clear web cache’ button will clear the session’s WebKit cache.


The ‘Clear web cache feature’ is only relevant if the device is using the HTML rendering backend.

The ‘Enable debugging’ button, when clicked, will initialize a debugging session for the selected device. A link will appear on the page with the URL of the debugging session. The URL provides a web inspection tool for the selected device, which means the developer has full access to the live device session and the HTML rendering backend, and the API functions. For example, calling console.out(okular.device_uuid); will print the device’s UUID to the console window.


The debugging feature might not work on hosted server instances due to firewall settings. For testing purposes it is recommended to use local Virtual Machine or Docker image instead.


Device management buttons


The ‘Enable debugging’ feature only works if you are browsing the web inspection URL with a WebKit-based browser, like Google Chrome , Apple Safari, or Epiphany .The inspector does not work on Firefox browsers.

Device Configuration

The Visionect Software Suite provides the capability to configure all aspects of device operation remotely, by using a simple Management Interface. Choose a client device from the list and select the ‘Device configuration’ tab.


The device configuration pane of the Management Interface.

‘Read from device’ will load the current settings on the device. The settings are separated into various categories, with ‘Basic’ shown by default. ‘All’ will show all the settings. Make sure you commit your changes with ‘Write to device’.


The device configurator is a very powerful tool that enables you to configure low level settings which will impact how a client device works. In some cases you could permanently damage the device. Please consult the explanation in ‘?’ (question mark) if you’re not sure what a setting does.

Alternative ways of configuring your client device are:

Device power management and Sleep Manager

Device power consumption, and consequently battery life, can be significantly reduced by turning the device off (i.e. sending it into sleep mode) for the time period in which the display content does not need to be changed. While the device is in sleep mode, its screen will continue showing the last image displayed.


While in sleep mode, devices will rely on an internal clock and it is not possible to wake them up remotely.

The Visionect Software Suite provides a Sleep Manager feature which implements basic usage of the sleep feature. Three options of sleep options are listed:
  • Periodical: the client device will go to sleep periodically, at time interval set.
  • At time: the client device will go to sleep at certain time of day
  • Working hours: the client device will go to sleep outside of the working hours set.


In case of high-grained control requirements the sleep feature can be also controlled directly from JavaScript (see Device power management and sleep).

To activate the the Sleep Manager feature, go under Settings ->Global-> Features in the Administration Interface and check the ‘Sleep Manager’ box..


Enabling the Sleep Manager in the Global settings

In the Devices sub-menu of the Management Interface (under Devices -> Status & Settings) you’ll see the sleep segment. Setting a time will enable sleep management from the Management Interface: the device will be in sleep mode until it reaches the predetermined time of day.

If you require the device to wake-up periodically, say, every 30 minutes, then set the time to 00:30 and Periodical to yes. The device will display the first picture immediately after connecting the the Suite, then it will switch into sleep mode and from that point on it will wake up every half hour.

Usage example:

A user sets the Sleep Manager on ‘Periodical: Yes’ and ‘Time: 0:30’ and saves the settings at 9:12 am. The first picture will be displayed in 1-2 minutes, then the client device will go to sleep and wake up (sending a new picture) at 9:30 am, after that at 10 am, then 10:30, and so on.


Sleep configuration in device pane


The clock will drift between devices due to temperature fluctuations and in 24hrs you can expect a difference of +/- 10 minutes in wakeup times in the group.

The sleep mode greatly impacts the power consumption of your client device. For more details on this topic, check power consumption documentation.


Any HTML-based web page can become a Visionect Software Suite application. Simply add the URL to the list of applications. The Visionect Software Suite will run the page using an industry-standard Webkit rendering engine, making most content render as is out of the box. For the best performance you’ll need to adapt the content to the limitations of the display medium.

The Apps section provides a list of the available web apps which can be selected from the Application drop-down in the Devices section of the Management Interface (for each selected device). By clicking the ‘Add new’ button at the bottom, a new row is added with entries for the app name, its URL and a short description.

Usage example:


Adding new app


Every change to existing Apps or every newly created App must be saved.

If there are no apps defined, the default URI is used from the global settings.


This is where you reconfigure how the Visionect Software Suite works.


The Settings menu of the Management Interface

Important configuration considerations are:

Display options, rendering and ghosting

By default, the Visionect Software Suite’s graphical engine will draw an inverse image before rendering the target image. This is done to reduce the ghosting effect on the screen occurring due to the nature of e-paper displays. The server configuration flags that configure the way the screen is updated can be found under ‘Display options settings’.

  • Clear screen - clears the screen with a white image before rendering the target image. If you are doing partial updates, please note that ‘Clear screen’ will wipe all display content.
  • Inverse updates - inverts the update before rendering the target image, removing ghosting at the cost of the update speed and flickering. This works well with partial updates (only the target region will be updated).

It is also possible to deal with image inverse feature directly in your app with the help of JavaScript (see Rendering performance and optimizations).


Some of the rendering related settings might not work correctly on older generation devices running very outdated firmware. Please contact our support at for more details.

Setting the maximum number of active sessions

You limit the number of active sessions (i.e. how many session can be spawned by the Suite) by setting the ‘Max Sessions’ value. Observe the current status in the ‘Status’ sub-menu of the Management Interface (Active session / Maximum).

When the number of active sessions reaches the limit, this prevents any new session from being created. For cleaning the old (unused) sessions, it might be necessary to restart services. Users should set the limit carefully, as it is related to the available memory of your server (more active sessions require more RAM).

Restarting services

It is possible to restart all the major components of the Visionect Software Suite remotely by pressing the red ‘Restart Services’ button. The services will be available again after a few seconds.


Restart Services button

Other important settings

  • Deployment Name: the name of the deployment.
  • Deployment Key: a unique identifier for the current Visionect Software Suite installation. It is generated automatically upon installation.
  • Timezone: the custom timezone drop-down menu.
Graphics Engine
  • Default Backend: choose either the HTML or HTTP backend as the default.
  • Max Sessions: sets the maximum number of sessions available to the HTML rendering engine. New session requests will be ignored if the number exceeds the limit.
  • Image Cache Size: set the maximum size in MB of the image cache.
  • Idle Threshold: sets the time in minutes after which an idle session is destroyed.
HTML Backend
  • Default URL: sets the URL of the default application.
  • Automatic page reload: sets the time in seconds in which the page will reload. Setting the value to 0 will disable the automatic page reload.
  • Web Session Memory Limit: sets the memory limit in MB that, when hit, will result in the Visionect Software Suite restarting each WebKit process to protect against memory leaks.
  • User Agent: sets the custom string to the user agent for identification
  • Render Timeout: how long the HTML rendering engine (formerly known as Okular) should wait for a rectangle region (in milliseconds) to be rendered before preprocessing the data for the device. Longer intervals are usually needed for rectangles with complex graphics, or if running HTML rendering engine on a slow machine,
  • Enable Font Antialias: configures if the fonts displayed on the device should be anti-aliased by the standard GTK+ anti-aliasing process. Set to ‘disabled’ if you’re using pixel-perfect fonts.
  • Enable Page Caching: sets if the loaded pages and resources should be cached or not.
Default Device Settings
  • Ignore Input I Device Not in Sync: ignores any new click requests from the client device in case there is unsent data in the device session. This means new clicks won’t affect the application and the old response will be sent instead,
  • Bit Depth: configures the default display bit depth. Valid values are 1 and 4. The 1-bit encoding reduces the refresh rate to 250 ms (the limitation of electronic paper technology), while 4-bit is the maximum bit depth. This value can be overridden by the HTML rendering backend (formerly known as Okular) Javascript Extensions in the web application,
  • Display Rotation: sets the default display rotation. Values are given in degrees and cover all four layouts.
  • Dithering: every web page has to be converted from color to grayscale or black and white (according to the Graphics Engine setting). You can choose the type of dithering based on performance and quality requirements. Currently supported (in order of quality): none, bayer and floyd-steinberg. Noise dithers will not be supported, as they negate the Graphics Engine render caching infrastructure.
  • Force Rectangle Support: Enables a partial screen update.
  • Force Group Synchronization: enables or disables the virtual screen synchronization.
  • Synchronize groups only if all of its devices are present: enables virtual screen synchronization only if all of the client devices are present.
  • Automatic Firmware Upgrade: automatically updates all new client devices with the newest firmware.
  • Automatic Bootloader Upgrade: automatically updates all new client devices with the newest bootloader.
  • Device State Polling: sets the time in minutes in which the Visionect Software Suite queries device for its status.
  • Firmware Repository: sets the default URL for a firmware repository server.

Users and API Keys

By default there’s always a default user admin and the password admin123.

To add a new user, click on ‘Add new user’ and type in the new username and password. To activate the user you must also tick the ‘Enabled’ checkbox, as disabled users are not permitted to login.

If you want to use the management features programmatically, you will need to create a new API key which your applications will use to access our servers. For more information on the management API and instructions on how to use the generated user/API secret, please consult the Visionect Software Suite API.