Version 3.1.0

16. September 2026

Added

• Backend: Security updates are installed automatically by default. The controller checks for updates daily within the configured window and installs a security update of its release line on the chosen weekday; it is announced a week ahead in the event log and by push notification to administrators, and can be postponed by seven days twice. New versions with new features are still installed automatically only on request. Existing settings are kept: whoever had the automatic switched on keeps getting all updates, whoever had it switched off stays off. New API function postponeSoftwareUpdate; getAutoSoftwareUpdateInfo, enableAutoSoftwareUpdate, softwareUpdateCheck and installSoftwareUpdates now distinguish security from feature updates
• Backend: Socket APIs for KNX device management and commissioning without ETS: getKNXBusDevices, identifyKNXBusDevice, exploreKNXBusDevice, getKNXBusDeviceTables, getKNXDeviceMgmtState, setKNXDeviceMgmtState, getKNXCommissioningStatus, abortKNXCommissioning, getKNXCommissioningSettings, setKNXCommissioningSettings, proposeKNXPhysicalAddress, startKNXDeviceCommissioning, getKNXDeviceChannels, applyKNXDeviceChannels, previewKNXDeviceChannels, removeKNXDeviceChannel, decommissionKNXDevice; events knxBusDevicesChange, knxDeviceMgmtStateChange, knxCommissioningProgress, knxCommissioningFinished
• Backend: New KNX device type "RGBW 1" under Lighting for RGBW dimmers with one group address per colour channel (red, green, blue, white); "RGBW 2" remains for devices with a single combined colour object
• Config/UI: On the "Log" page, administrators can switch the recording of events on and off
• Config/UI: The "Software Update" page shows an available security update with the security advisories it resolves and the planned installation, with buttons to install it right away or postpone it by 7 days; the automatic now has the two levels "Install security updates automatically" and "Install all updates automatically"; below the status the page links to the release notes
• Daemon: KNX device management — an inventory of every device seen on the bus (DEVICES), identification of a single device or of all of them at once with manufacturer, order number, serial number and mask version (IDENTIFY), a listing of the interface objects with their properties (EXPLORE), and reading of the address and association tables (TABLES). Available over tunneling, tunneling secure, routing and routing secure. Off by default — without the DEVICEMGMT setting nothing changes in the existing behaviour
• Daemon: Individual device properties can now be written (WRITEPROP). Every write is read back and compared with what was written — a KNX device acknowledges a write telegram at the transport layer without thereby saying it took the value; the operation reports success only when the read-back matches. The properties through which a device is loaded and its tables are placed — load state, table reference and table — stay locked for this command and answer ERR_PID_LOCKED: they belong to a complete programming procedure, not to a single write
• Daemon: A device can now be told which group addresses to listen to (WRITETABLES) — commissioning without ETS. You give pairs of group address and communication object, for example WRITETABLES=1.1.3,4/4/41:1,4/4/42:9; the word CLEAR empties both tables and frees a device again. The existing tables are read before every write and travel in every result, a failed one included — otherwise nobody would know what was lost. At the end the daemon reads both tables back and compares them entry by entry; only then does the operation report success. The device is briefly out of service while this runs, as it is when programming with ETS
• Daemon: A device now gets its physical address from the daemon (WRITEADDR) — which completes commissioning without ETS: first the address, then the group addresses. Programming mode is always triggered by hand at the device, pressing the button as ETS requires, and exactly one device may be in programming mode; if the daemon finds more than one, it refuses. It searches for up to two minutes, and ABORT stops the search at any time. If the device found already carries the wanted address, it is only confirmed, not written again. If the address belongs to another device, the operation refuses with ERR_ADDRESS_IN_USE without writing anything. After the assignment the daemon checks that the device answers at its new address, and ends programming mode by restarting the device
• Daemon: Two-stage safeguard for device management. DEVICEMGMT;YES in the [CONFIG] section of the KNX configuration (knx.csv) only permits an installation to be armed; arming itself happens at runtime through the DEVICEMGMT command with the states OFF, READ and WRITE. After every start and every configuration reload the switch is OFF, and it falls back there by itself after a period of inactivity — DEVICEMGMT_TIMEOUT sets that period in seconds, 900 by default (15 minutes), 0 switches the self-disarm off. Writing requires the WRITE state and reading the READ state; JOBS and ABORT answer even at OFF, so a running job can always be stopped
• Daemon: KNX device management commands: DEVICES (inventory), IDENTIFY (one device or ALL), EXPLORE (interface objects and properties), TABLES (address and association table), WRITEPROP (write a property), WRITETABLES (write the group address tables), WRITEADDR (assign the physical address), JOBS (queue), ABORT (cancel running jobs) and DEVICEMGMT (the arming switch). They work in the background: the command reply only confirms that the job was accepted, the result is reported afterwards — for the longer jobs minutes later. Without the permission they answer ERR_NOT_PERMITTED, and when not armed ERR_NOT_ARMED

Changes

• App/UI: The support e-mail from the app settings attaches the diagnostic log as a file instead of putting it into the message text; the text briefly summarises app, device, controller and connection and leaves room for your own description of the problem. Errors that occurred travel with the mail and are no longer shown in the settings
• Backend: Software updates and update scripts are only installed with a valid nomos signature; unsigned or tampered packages are rejected
• Backend: Administrator accounts now require a password of at least 6 characters; empty passwords are no longer allowed for administrators. Existing accounts are left unchanged, the security check keeps pointing out missing passwords
• Backend: The event log now also records changes to users and permissions, backup restores and factory resets; recording can be switched off
• Backend: The usage analysis makes smarter automation suggestions. Habits that follow the sun are recognised as such and proposed with sunrise or sunset as the trigger instead of a clock time that drifts with the season; devices that move together arrive as one suggestion. Habits tied to somebody coming home or everyone leaving are recognised as well and proposed with presence as the trigger. Suggestions carry conditions such as "only while nobody is home", "only after dark", "only below 10 °C outside" or "only with solar surplus" when the observed behaviour clearly depends on it and the matching source (presence, weather station, inverter) is tagged. What an existing automation already does is no longer suggested. After the update the analysis rebuilds its statistics: time-bound suggestions appear only after five to seven weeks of recording, sun-based ones after one to two weeks
• Config/UI: On the "Internal service" page, Cmd+A / Ctrl+A now selects only the log output instead of the whole page including sidebar and header. With a filter active only the visible lines are selected; input fields keep their usual behaviour
• Config/UI: The KNX page is organised into the tabs "Devices", "Addresses", "Monitor" and "Settings"; the sub-pages can be linked to directly
• Config/UI: KNX status messages appear in every language; problems with the individual address are named instead of shown as a code
• Daemon: KNX device management uses extended frames and reads tables in larger blocks; longer answers are no longer discarded
• NodeRED: Upgraded to version 5.0.7

Fixed

• Backend: Minor fixes and optimisations in usage recording and the suggestions derived from it
• Backend: Camera images through the forwarder now also arrive from cameras that strictly check the requested path during Digest authentication; previously the wrong path was signed. The forwarder also now ends a request the camera refused cleanly instead of leaving the caller waiting until the timeout
• Backend: Connection errors towards gateways, devices or the cloud service could crash the backend or leave a request unanswered; an error message is shown instead
• Backend: Adding a Somfy gateway always ended with an authorisation error since version 2.8.3, even with correct credentials
• Backend: Improved the reliability of activating Direct VPN
• Backend: Deleting a device assigned to a room restarted the backend since version 3.0.0; a device with sub-components could be left only partially deleted
• Backend: Requests from the app with an expired session counted as failed login attempts and could temporarily block logging in from that device
• Backend: Matter devices offering a scenes cluster of their own were rated as poorly compatible during device detection; the cluster is no longer scored, since scenes are managed in the controller
• Backend: The systems list (getSystemsList) never answered when two addresses reported the same serial number or a device answered without one
• Backend: An unhandled error in a background task restarted the backend; it is now logged and reported as a crash report while the backend keeps running
• Config/UI: On the "Internal service" page, an active log session now resumes automatically after an engine restart; previously it switched to Stop on every restart
• Config/UI: On the "Cameras" page, a camera's dark title bar poked out past the rounded frame at the top corners; it now follows the rounding
• Config/UI: The Direct VPN switch snapped back to OFF after confirmation although the VPN was activated
• Config/UI: Centred content jumped sideways when the scrollbar appeared; its space is now reserved