Upcoming version · planned for 2027
BAVIS 4.0: what it brings and how to move from 3.x
BAVIS 4.0 builds on version 3.1 and contains all its fixes. It brings official support for Linux, Raspberry Pi and Docker, an optional PostgreSQL database, the project in Git and dozens of new drivers for buildings, energy and the smart home. Before release it went through an internal security audit and a code review. Data, configuration and projects from version 3.x are taken over without loss.
BAVIS 4.0 is in development. This description reflects the state in November 2026 and may be refined before release.
What it brings
What is new in version 4.0
Where BAVIS will run
- Linux: a .tar.gz or .deb package for Debian, Ubuntu and Raspberry Pi OS, a systemd service. HTTPS with your own certificate, with Let's Encrypt or behind a reverse proxy. Backups and updates work the same as on Windows.
- Raspberry Pi 4 and 5: the SD card profile stores data in batches and cuts writes to the card from 22.4 to 2.8 MB per hour (measured with 50 tags and a 1 s period). A power cut therefore loses at most the last minute of history. For production use we recommend an SSD instead of an SD card.
- Docker: an image for amd64 and arm64.
- Home Assistant OS: BAVIS as an add-on with its interface right in the Home Assistant sidebar.
- Windows stays unchanged: installer and service as before.
Data and project
- PostgreSQL: an optional main database for configuration and history, PostgreSQL 14 and later (we recommend 16). Data can be converted between SQLite and PostgreSQL. The load test with 50,000 tags ran on Linux with both SQLite and PostgreSQL.
- Project in Git: the project is stored as text files, each revision is a commit and changes are sent over HTTPS (push and pull). You can version and review the project just like a program.
- Documentation in English: 10 guides with an index – installation on Windows and Linux, licensing, alarms, API v1, MCP, BAVIS Central, Home Assistant, backups and S7 communication. In-app help with the “?” button or the F1 key, on Linux too.
New drivers by area
- Smart home: Matter (via Matter Server), Z-Wave (via Z-Wave JS), Philips Hue, SwitchBot, WiZ and Govee lights, WLED LED strips, iNELS, Daikin, Midea, Gree and Sinclair air conditioners and LG ThinQ, Xiaomi devices, wall tablets with Fully Kiosk and extended Tuya and Shelly.
- Buildings and security: Jablotron 100, 2N intercoms, NFC and RFID access cards, ONVIF cameras with events and PTZ, Reolink, Hikvision and Dahua, Domat, Merbon and Mervis (SSCP) and AMiT (DB-Net) controllers. The BACnet client reads more object types, writes with priority, subscribes to changes (COV) and imports EDE files; the BACnet server has a PICS.
- Energy and cars: Škoda, Kia, Hyundai, Genesis, Tesla, Volvo, BMW and MINI cars through the manufacturers' official APIs and other brands through the paid third-party service Smartcar, charging the car by departure time. Victron over VE.Direct and RS-485 and Victron ESS control, SMA Energy Meter, SunSpec over RS-485, EEBUS for heat pumps, SG Ready and heat pump profiles for NIBE, Stiebel Eltron, Mitsubishi Ecodan and Samsung, KEBA, ABB Terra AC and Alfen wallboxes and grid CO₂ data from Electricity Maps.
- IT and services: network (ping, TCP port, Wake-on-LAN), UPS via Network UPS Tools, ICS calendars (Google, Outlook, iCloud) and receiving data via webhook, for example from an Ecowitt weather station. For IT monitoring an SNMP v1, v2c and v3 agent and Prometheus metrics.
- Workshop and DIY: Prusa, Bambu Lab, OctoPrint and Klipper 3D printers and Raspberry Pi inputs and outputs (GPIO, 1-Wire, I2C).
- For every driver BAVIS shows whether it has already run on a real device or is still “beta”.
Operation, editor and features
- Templates: overviews, scenes and automations, object templates and faceplates, the “My home” and “Development test lab” projects with evaluation to the standard. Device sets insert a device together with its screen, and the network scanner suggests a driver for devices it finds.
- Digital input profiles: motion sensor, button, door, flooding and pulses.
- Alarm sorting: area tree, folders, origin, filters and views, colours by ISA-18.2 priority.
- Editor: faceplates in folders and a faceplate library, screens for selected users only and a usability check of screens (font size, touch targets, contrast).
- Who is home: presence by phone, alarm system, car or any tag, presence simulation and phone locations on the household map (OwnTracks, iOS Shortcuts, Tasker).
- Access cards: card register, readers, doors, arming the Jablotron and logging in with a card.
- Laboratory: the test report uses the instrument calibration valid on the test day; a later calibration does not change it retroactively.
- ISA-88 phases in the PLC: an SCL library for TIA Portal (intended for V18 to V21) with ISA-88 phase states and a step sequence. The phase runs in the PLC; BAVIS controls and displays it through a typed device with a faceplate. We will verify compilation in TIA Portal before release.
- Device simulators: car, 3D printer, Philips Hue, Shelly, Victron, 2N intercom, Jablotron, Domat and AMiT controllers, EEBUS, Reolink, SwitchBot and cameras. You can try the project and your own driver without hardware.
Integration, AI and BAVIS Central
- MCP server for AI agents: the agent works through API v1 under the same rules as the key it is given, so read-only or with write access. Writing from an agent must be explicitly allowed by the administrator. A remote agent connects through BAVIS Central with OAuth sign-in, and the installation itself decides whether it may only read.
- Help with NIS2 requirements: lossless event forwarding to a SIEM, also in LEEF format and encrypted with a certificate from the company certificate authority, plus locking of inactive accounts and API key expiry.
- BAVIS Central: a health overview of all installations in the fleet, including load and a disk space forecast.
Control room, faults and sectors
- Substations like in a dispatch centre: symbols to IEC 60617, a single-line diagram coloured by energised, de-energised and earthed state, interlocks and select → confirm → execute control with feedback and an audit log. A “22/0.4 kV substation” template.
- Power plants: templates for a “solar park with a battery” (power reduction levels, export limitation, P(f), power factor and Q(U)) and a “small hydro plant” (level control, connecting generator sets, synchronisation, screens) and a generator set faceplate.
- Control room on several monitors: screens adapt to wide 21:9 and 32:9 monitors and to three monitors side by side, a workstation with 2 to 4 panels (screen, faults, trend, overview) and windows on several monitors with one login.
- Fault analysis even without AI: for a fault: the first cause, the cascade of alarms before it, similar faults from the last 180 days with comments and work orders, and an instruction for the operator. With the AI assistant it is also explained in plain words, read-only.
- Water and wastewater: a daily operating log, inspection rounds with QR or NFC tags, lab analyses with limits according to the permit, records for the annual report in XLSX and an overview of telemetry sites.
- New sector templates: swimming pool and aquapark, dairy, district heating, data centre, compressor station, biogas plant, charging park, cleanroom monitoring in pharma, HACCP cold stores, a microbrewery and a beverage plant. Each runs in simulation right away.
Industry 4.0 and integration
- Carbon footprint: of a batch, production run and order in kg CO₂e in total and per piece, from line energy per quarter hour, grid intensity and the share of your own solar, following the GHG Protocol methodology.
- Asset Administration Shell (AAS): a digital nameplate, technical and operational machine data according to IDTA templates, a REST API, AASX export and nodes in the OPC UA server.
- Virtual commissioning: a “Tank and pumps” template with SCL source (control and process model in the PLC) and a screen for injecting faults, a procedure against S7-PLCSIM Advanced.
- MES, ERP and maintenance: an event catalogue (orders, downtime, scrap, batches, work orders) to webhooks, MQTT and the API, and an SAP PM preset: a fault in BAVIS as a maintenance notification with the status back. We will prepare links to other ERPs.
Hardware, drivers and unattended operation
- Industrial units: Revolution Pi (a driver for the piControl process image), SIMATIC IOT2050 and Unipi Patron; the installer detects the board by itself.
- New drivers: Zigbee via deCONZ / Phoscon, Nuki locks via Nuki Bridge, OpenTherm boilers (OTGW), CAN bus via SocketCAN (Linux only) and RuuviTag sensors.
- Long unattended operation: on Linux and Raspberry Pi a service watchdog and a hardware watchdog, a read-only system and updates from BAVIS Central.
- Voice alarm calls: via a SIP PBX or a GSM modem, acknowledged by a key press.
- Backups and diagnostics: a full backup including the data folder files and restoring trend history, a diagnostic bundle with an anonymised project for bug reports.
SDK and community
- The bavis sdk command in every installation (Windows, Linux, Docker), without the core source code.
- A package catalogue from trusted sources. Packages we have verified carry our signature and a “verified” badge in the application. Community drivers can be installed unsigned too, but only at your own risk.
- Nine sample packages in the public BAVIS-SDK repository (Hello, HTTP JSON, SCPI, UDP JSON, CSV, Modbus ASCII, Prometheus, NTP, P1/DSMR meter) and discussions.
Security
Security in version 4.0
In November 2026 we put BAVIS through an internal security audit and the new parts of version 4.0 went through a code review. The fixes are part of version 4.0. We develop security with IEC 62443-4-2 in mind.
- Encrypted device passwords. Passwords and tokens for PLCs, cameras and other devices are encrypted (AES-GCM) in the project and in older revisions. Anyone who gets only the project file cannot read them.
- Stronger user passwords. Passwords are stored with PBKDF2-SHA256 and 600,000 iterations. They are re-hashed automatically at the first sign-in.
- Sign-in never in the address. The session token never appears in the URL, so it cannot leak into browser history, proxy logs or a shared link. Images, downloads and live data use short-lived tokens.
- Limits for unauthenticated requests. Without sign-in the server accepts at most 512 kB per request and 120 writes per minute from one address.
- Permissions on every API route. Every interface route checks permissions, and an automated test enforces this for every new one too.
- Outgoing address checks. The core, drivers and project code send requests only to http and https, and not even after a redirect to other protocols or to cloud metadata service addresses. The check also recognises alternative IP address notations.
- Pinned certificates. The OPC UA client, Hikvision, Dahua and Reolink cameras, the 2N intercom, Philips Hue and Bambu Lab printers remember the device certificate. If it changes, the connection is refused until the administrator confirms the new fingerprint. BAVIS does not send credentials to a device with a different certificate.
- Device passwords only over a safe path. Hikvision and Dahua cameras and 2N intercoms get the password with Basic only over HTTPS, over HTTP only with Digest. ONVIF cameras sign in with Digest, and the older Shelly Gen1, which does not encrypt the password on the network, gets it only when the generation is explicitly selected. The client discards a spoofed SNMPv3 response with a bad signature.
- Signed packages. A project package must be signed. Our packages and the drivers we have verified carry a signature and a “verified” badge. The administrator can install an unsigned community driver only after confirming “at your own risk” with a password and a reason (electronic signature), and the installation is written to the operations log. The administrator can switch off installing unsigned drivers completely.
- Installation integrity check. A signed file list reveals a modified installation. A finding raises an alarm and a fault in BAVIS Central; it does not stop operation. Most PDF and XLSX reports and exports carry the licence identification in their metadata.
- Safe libraries. Third-party libraries are locked to specific versions with SHA-256 hashes, and build tools are pinned to a verified version. Every Windows release comes with a software bill of materials (SBOM). Imports and camera responses are read with a safe XML parser.
- Accounts and cards. A wrong card PIN locks the account just like a wrong password. When a role is deleted, its holders without another role get view-only access, and locking an account also revokes phone location keys. Car commands (unlock, start, charging) from logic, the calendar and tasks are written to the audit log.
- Operation. Switching between redundancy servers uses a one-time ticket. The Linux installer does not run code or settings that the service account can change with root rights. If installing libraries fails during an update on Linux, the previous version stays.
- Licence agreement. A new installation asks for consent to the licence agreement in the wizard. The consent is shown in System → Licence and in the operations log.
Report security issues to us privately as described on the Security page. Response times and supported versions are on the Versions and support page.
Security BAVIS versions and support BAVIS licence agreement How to verify a download
Upgrade
Moving from version 3.x to 4.0
BAVIS 4.0 takes over data, configuration and projects from version 3.0 and 3.1 without loss. New drivers and modules are switched off after the update, so the installation is operated and logged as before. A few things are worth knowing in advance. If you need long-term stability, you can stay on 3.0 LTS and later move straight to 4.2 LTS (we plan a direct upgrade from 3.0).
Before the update
- Make a backup. The encrypted BAVIS backup and the local daily backup also contain the key used in 4.0 to encrypt device passwords. An unencrypted backup has neither the key nor the device passwords; after restoring on another computer the device passwords must be entered again. If you back up the data folder another way, you must also back up the file with this key.
- Going back to 3.x only from a backup. At the first sign-in in 4.0 user passwords are re-hashed with a stronger method that version 3.x can no longer verify. You can therefore return to 3.x only by restoring a backup made before the update; otherwise the passwords would have to be set again.
- Check the licence tier. From 4.0 every tag of the installation counts towards the licence limit: connection and virtual tags, calculations, PLC tags loaded by a custom project application and measurement channels (NI cards, sensors). Built-in BAVIS status values do not count. System → Licence shows the tag count.
- Redundancy: update both servers.
- Support: with valid support you move to 4.0 at no extra cost.
What behaves differently after the update
- OPC UA server certificates: the client remembers the server certificate at the first encrypted connection. After the certificate is replaced on the server, the administrator confirms the new fingerprint.
- Shelly Gen1 with a password: set the generation to Gen1 on the connection, otherwise the connection with a password will not start.
- Custom integrations: a session token in the address (?token=) no longer works; use the Authorization header or an API key. Without sign-in the limits of 512 kB per request and 120 writes per minute apply; they can be set in the configuration. Outgoing requests go only to http and https.
- Project packages must be signed; an unsigned package works only in development mode. For community drivers see Security.
Verification status
What is not there yet and what awaits verification
For every driver BAVIS shows whether it has already run on a real device (“Verified on a real device”) or is still “beta”, i.e. verified against a simulator or in automated tests. Beta does not mean it does not work, only that nobody has run it against a real device yet. We will gladly test it with you.
Already run on a real device (at least reading values)
Modbus TCP, Siemens S7 (S7-1500 in operation at a construction products test lab), NI DAQmx card, MQTT, ESPHome and Tuya, and of the 4.0 additions WLED, Midea air conditioners, LG ThinQ and a Škoda car (only some values so far). The BAVIS 3.0 LTS core (screens, alarms, trends, history, test reports and exports, calibration) runs in operation at a construction products test lab on Windows.
Everything else is still beta, including
Linux, Raspberry Pi, Docker, the Home Assistant OS add-on, PostgreSQL, Matter, Z-Wave, Philips Hue, ONVIF, Reolink, Hikvision and Dahua cameras, Jablotron, the 2N intercom, card readers, AMiT, Bambu Lab, Victron, presence and phone location, other car brands, BACnet, KNX, Beckhoff, Rockwell, Omron, Mitsubishi, Schneider, WAGO, LOGO!, Foxtrot, Loxone and Unipi PLCs and the other new 4.0 drivers. The ISA-88 phase library has not yet been compiled in TIA Portal.
Known limitations
Waking a Tesla car (up to 45 s) delays processing of the project logic. The SMA Energy Meter does not read the grid frequency because SMA's documentation does not list it among the channels. The energy manager can pause charging only on the go-e wallbox; for KEBA, ABB Terra AC and Alfen it recommends OCPP. Try writes to inverters, wallboxes and cars carefully at first.
After 4.0
BAVIS as a Matter and HomeKit bridge for control from Apple Home, Google Home or Alexa including voice, ISA-88 batches and MTP, BACnet MS/TP, schedules and trend logs in the BACnet client and more drivers will come with 4.x versions. Revolution Pi, SIMATIC IOT2050 and Unipi Patron are so far verified in 4.0 only by simulation, not on real hardware.
BAVIS 4.0 FAQ
When will BAVIS 4.0 be released?
We are planning it for 2027; we are not promising an exact date yet.
Will I lose data when moving from 3.x?
No. Data, configuration and projects are taken over without loss. Make a backup before the update, though, because you can return to version 3.x only from it.
Will BAVIS 4.0 run on a Raspberry Pi?
Yes, on the Raspberry Pi 4 and 5. Until we verify it on a real device, we list it as beta.
Does moving to 4.0 cost anything?
With valid support you move to the new version at no extra cost. Without support you can keep using the version you have, including the maintenance releases and security fixes we issue for it while it is supported. For a new version with new features (4.0, 4.1 …) you then need support or a new licence. The Lite and Maker editions are free and get new versions without support.
Want to try BAVIS 4.0 earlier?
Tell us what you want to connect. We will gladly verify a driver with you on a real device or prepare the move from version 3.x.
Manufacturer and product names are trademarks of their respective owners. Siemens, SIMATIC, S7, LOGO!, TIA Portal and IOT2050 are trademarks of Siemens AG. Matter is a trademark of the Connectivity Standards Alliance. deCONZ, ConBee, RaspBee and Phoscon are trademarks of dresden elektronik, Nuki of Nuki Home Solutions GmbH, OpenTherm of The OpenTherm Association, Ruuvi and RuuviTag of Ruuvi Innovations Ltd., SAP and S/4HANA of SAP SE. BAVIS is not affiliated with them.