18th November 2026 – The new version of the open-source API for Unipi controllers can communicate over MQTT and protect access with a token. It also tells you when each device last responded.
EVOK is open-source software that runs directly on Unipi controllers. It lets other applications work with the controller's inputs, outputs, and sensors – Node-RED, Python scripts, Mervis, and others. They communicate with it over REST, WebSocket, JSON-RPC, webhooks, and now MQTT as well.
Token-protected access
By default, EVOK accepts requests only from applications running directly on the controller. You enable network access in the configuration. A single line there also sets a token – a password that every application connecting to EVOK has to present. The token applies to all interfaces except MQTT, where access is managed by the broker.
Applications that only need to display data, such as dashboards, can be given a second, read-only token. It allows them to read values but not to control outputs.
EVOK does not encrypt communication itself. For access from outside a trusted network, we therefore recommend placing a reverse proxy with TLS in front of it.
You know when a device last responded
For values from the controller's inputs and outputs, extension modules, external Modbus devices, and 1-Wire sensors, EVOK reports the time of the last successful communication. An application can therefore tell that it is working with an old value – for example, when a sensor stops responding. EVOK also notifies the application when communication is lost and when it is restored, so you can tie an alarm to these events.
An unresponsive device does not hold up the others
When a module or an external device on the bus stops responding, communication with the others does not slow down. You can also set how long EVOK waits for a response and how many times it repeats a request.
Errors show up right away
When an application sends an invalid value, such as one outside the range of an analog output, EVOK rejects it and returns an error. You find out about a problem in your program immediately. EVOK writes configuration errors to a log, which you can also read remotely through the API.
1-Wire without an extra service
EVOK now reads 1-Wire sensors directly through the Linux kernel. It no longer needs the separate owserver service it used for this until now.
Installation and update
On Debian 13 Trixie, you install and update EVOK 3.1 with apt: sudo apt update && sudo apt install -y evok. Version 3.0 remains available for Debian 12.
If you already use EVOK, check these points in particular before updating:
- Network access. Do applications on other devices connect to EVOK? Allow their access in the configuration.
- WebSocket. Node-RED and web applications that connect over WebSocket must have their address listed in the
allowed_originssetting. - Output pulses. Switching an output on for a set time is now done through the sequencer. It replaces the
pulse_durationandtimeoutparameters. - Input and output names. Some of them have changed (the
circuitfield).
Other changes are summarized in the API changes overview. You can find the documentation at evok.readthedocs.io and the source code on GitHub.
