Everstra Hub — Release notes
Every release since the first version, newest first.
v0.3.0
2026-10-14
- Security: Other apps installed on the camera could until now reach this app's internal endpoints directly, without the camera's login check — the app's FastCGI socket was reachable for other local processes, a side entrance past the web server. It is now closed: access goes only through the camera's web server and its login.
- Privacy page: it now looks and works like in the other Everstra apps — the same table and cards, sorted active first, local paths marked “Internal only”, and for the first time Export PNG and Export CSV.
- Privacy page: the exports now show the encryption that the page shows — the CSV has the columns “protocol” and “encrypted”, and the PNG marks every connection that travels without encryption as “unencrypted”.
- Privacy page: a broker connection without TLS, or with TLS but without certificate check, is now shown as a yellow warning, and plain TCP to the broker is counted as unencrypted.
- New: The module tiles show how many of a module's FTP targets send without encryption, e.g. “Outbound active: 2 (1 unencrypted)”.
- Change: The light/dark choice is now kept on the camera, as in Everstra Live — it is the same in every browser. A choice this browser had kept until now is taken over once.
- Notices on the settings pages behave the same in every Everstra app: a success or info message goes after a few seconds, a warning or an error stays until the next message, so it cannot vanish before it is read, and a new message no longer hides a fresh error early. The light/dark switch shows the same symbol as in the other apps.
- Fix: “Copy” on the License page reported success even when the browser had not copied anything; it now says when copying failed. Restoring a backup shows the camera's reason when it refuses the file.
v0.2.0
2026-10-11
- New: Online activation. In the License tab, “Activate online” lets the camera fetch its licence key itself, in one click. The camera contacts activate.everstra.com once — only when you click — and sends its hardware ID, its model, its firmware version (e.g. 11.11) and the module name, plus an e-mail address if you enter one for a copy of your key. The hardware ID is used only to sign the key and is not stored. Offline activation with a key file works as before.
- Privacy: Activations are counted anonymously — only the module, the camera model, the firmware version (major.minor) and the day of activation, without time of day, to keep Everstra working on the cameras and firmware in use; no hardware ID, no IP address, no e-mail address. The License tab lists what is kept and what is used once and discarded. The privacy policy on everstra.com and the app's Interfaces page now list the activation connection. In operation the app does not contact Everstra.
- Licence: After an online activation the key is shown in the app and can be downloaded as a file; after a reinstall on the same camera it can be loaded again without any server contact. The licence agreement (EULA) is updated to version 1.1 accordingly.
- Licence: The app reads the new licence format issued by the online activation. Existing licence files remain valid — nothing to do.
- Licence: A licence key can also be pasted into the License tab instead of choosing a file. Licence files are now named with the camera's hardware ID and end in .lic (everstra_<module>_license_<hardware ID>.lic); existing .dat files still work.
- New: Update notifications (optional, off by default). Switched on in the License tab, the camera fetches a small file with the newest version number from updates.everstra.com once a day and shows a banner on every page when a newer version — or a security update — is available, with its release date and a Download button; a regular notice can be dismissed for that version, a security notice cannot. “Check now” in the License tab checks at once. Nothing about the camera is sent: no hardware ID, no model, not even its version. Switched off, no connection is made.
- Licence: Without a valid licence the start page now says so at the top — above every tab — with a button straight to the License tab.
- Licence: While the app is licensed, the License tab offers the licence key at any time — “Show license key” and “Download license file” (everstra_<module>_license_<hardware ID>.lic). The camera reads its own licence file; no server contact. So the key is never lost, even after an online activation without e-mail.
- Privacy: The Interfaces page lists the update check as a connection of its own — on or off, and what it sends.
- Fix: A licence file that is rejected on upload is no longer left in place — before, it kept Hub locked until the next valid upload.
- Licence: “Trial expired” is shown in red, as in the other modules.
v0.1.1
2026-10-03
- Security: An internal security review of Everstra identified weaknesses in how Everstra Hub handles the MQTT broker password and the settings interface. All of them are closed with this release. Automated tests now guard against these cases.
- Security: The MQTT broker password was stored in plain text in the settings file. It is now stored separately, readable only by Everstra Hub, and never sent back by the settings interface. Existing passwords are moved automatically on the first start.
- Security: When the broker address was changed, the stored password was reused for the new broker. Changing the broker address, port or encryption setting now discards the stored password; enter it again for the new broker.
- Security: The settings interface now only accepts requests in JSON format. This blocks a class of requests that other websites open in the same browser could send to the camera.
- Security: A malformed internal message could write camera access data to the system log. This is fixed.
- Changed: Scripts that send settings to Everstra Hub as form data must now send JSON.
- Fixed: Messages shown after saving settings or after uploading or removing a certificate were hidden immediately by the page reload. They now stay visible.
v0.1.0
2026-09-13
- Everstra Hub brings what your Axis camera knows and can do into Home Assistant — over MQTT, encrypted, and across sites through Tailscale if you want it. Hub makes no decisions of its own: it supplies the building blocks, sensors and switches, and you build the automations yourself. That goes far beyond what Home Assistant reads from an Axis camera on its own.
- New: module status in Home Assistant — whether Everstra Live, Overlay and Capture are installed and running, their version and licence state, how many Live streams are on air, and the state of Capture's jobs.
- New: camera metrics discovered per model — temperatures, CPU load and memory, network link, storage, I/O ports, tampering and day/night events, the stream settings of each view area such as resolution, frame rate and target bitrate, and image settings. Hub publishes only what the camera itself reports, and every value can be switched on or off individually.
- New: control back into the camera — start and stop Live streams, switch Capture jobs on or off, and set writable image settings. Each writable value has to be enabled deliberately: nothing is writable by default, and nothing that deletes can be reached.
- New: MQTT over TLS (LibreSSL) with certificate verification. For a self-signed broker such as the Home Assistant Mosquitto add-on, upload its certificate instead of switching verification off.
- New: across sites through the Tailscale app's HTTP proxy — the camera reaches a broker in another building or another town without opening a port.
- New: configuration export and import as one JSON file — connection, certificate and camera selection. The broker password is never part of the export.
- New: the Privacy page — every connection Hub opens, built from your actual configuration, exportable and always available.
- New: Everstra Hub is an Axis-signed ACAP application, countersigned by Axis Communications — it installs even on cameras configured to reject unsigned apps (AXIS OS 11.11 and later).