Version 3.2.0

14. October 2026

Added

• App: Places appear like other devices in their room. The tile shows e.g. "1 there" or "Nobody" and is highlighted while someone is there. The detail view shows the place as a circle on a map with the devices currently there, and lists which device has been there or away since when
• App: Vehicles have their own detail view: below the vehicle icon the licence plate, if entered, then the state of charge and range (for combustion cars fuel level and range), charging state with charging power and the time the vehicle will be fully charged, locked or open with a hint about open doors, windows, boot or bonnet. Below, depending on the vehicle, charging (start and stop, charge limit, charge mode), climate with set point, auxiliary heating and ventilation, vehicle state and position, which opens in the maps app with a tap. "Last reported … ago" shows how current the data is, "Refresh" asks right away, and a running command shows as "being sent …". The room tile shows the state of charge, the range and whether the vehicle is charging
• App: The new user manual is linked right from the app: "Help" on the start screen, even before the app is connected to a controller, and "User manual" under Settings → Infos. It opens in the app's language, inside the app in the built-in browser and in the browser in a new tab
• App: Sign-up for the nomos newsletter: in the settings under User → "Newsletter". The sign-up is confirmed by e-mail and can be cancelled at any time via the link in the newsletter
• App: Detail views with many values arrange them in sections, e.g. heat pumps and heating systems (Operation, Temperatures, Hot water, Heating circuits, Energy), inverters (Power, Battery, Today, Total), chargers (Charging, Energy, Measurements) and Home Connect and Miele appliances (Program, Options, Device)
• App: Android widgets for the home screen: Scenes, Favorite scenes, Devices of a room, Favorite devices, Rooms of a zone, Zones and Garage doors. Tapping a scene runs it right away without opening the app, also on the go via remote access; devices, rooms and zones open the app right there; a garage door opens and closes only after a confirmation and shows its state. From Android 12 the widgets take on the colours of the wallpaper, and the header appears in the app's accent colour
• App: nomos for Wear OS watches: the watch shows the scenes of your Controllers (optionally favorites only) and runs them with a tap, at home or on the go via remote access. The "nomos favorites" tile puts up to four favorite scenes right next to the watch face. The Controller's name appears in the app's accent colour, on the tile too. The data comes from the nomos app on the paired Android phone
• App: Android Auto: open and close garage doors and start favorite scenes with a tap on the car's screen, at home and on the go via remote access
• App: Cars with Google built-in (Android Automotive OS): the same garage doors and favorite scenes without a phone; the car signs in once on your home Wi-Fi with a QR code
• App: iPhone: open and close garage doors without opening the app: with the Garage Door Widget on the Home Screen (up to two doors) and on the Lock Screen, with the "Garage Door" control in Control Center and with Siri ("Open the garage door with nomos", "Close the garage door with nomos"). Each door has two fixed buttons, "Open" and "Close", and shows "Opened" or "Closed". On the Home Screen only a second tap within 8 seconds runs it; on the Lock Screen, in Control Center and with Siri on a locked iPhone only after Face ID or the passcode. If a command does not get through, the widget briefly shows "Failed"
• App: CarPlay (from iOS 26): the Scenes Widget, the Favorite Scenes Widget and the new Garage Door Widget (CarPlay) can be added to CarPlay. A tap starts the scene or opens or closes the door, as with garage doors in Apple Home, at home and on the go via remote access
• App: iPhone: scenes on the Lock Screen: the Scenes Widget and the Favorite Scenes Widget with up to two scenes, and the round widget "Scene" for a single scene. The iPhone asks for Face ID or the passcode before running it
• Backend: New exportKNXGroupAddresses API: returns the KNX group addresses as a file for importing into the ETS, as XML or CSV, optionally together with the addresses of the ETS projects
• Backend: New getPluginStatus API and new onPluginStatusChange event: report what a function is doing right now, e.g. which motion lighting instance has its lights on and for how long still, or today's plan of the presence simulation in vacation mode
• Backend: New function "Motion lighting" (staircase function): any number of instances connect motion sensors, buttons or door contacts with lights, switch them on at motion and off again after a follow-up time. Follow-up time, "Automatic active" and "Permanently on" are system variables per instance, can be changed by automations and released for the app. Optional: switch on only when it is dark (at night or by brightness sensor), warning before switching off, fixed switch-on brightness and lockout after a manual switch-off
• Backend: New function "Adaptive lighting": any number of instances make the colour temperature of their lights follow a curve over the day, e.g. warm white in the morning and evening, cool white at midday. The curve consists of points anchored at sunrise, sunset or a fixed time, each with an offset in minutes, a colour temperature in Kelvin and a brightness. Optionally, the brightness follows the curve too. When a light is adjusted by hand, the function leaves it alone until it is next switched off and on, but at most for the set time (4 hours by default). "Automatic active" is a system variable per instance, can be changed by automations and released for the app. The function works together with motion lighting: the lights get the matching colour temperature when they switch on, and the switch-on brightness of motion lighting is kept
• Backend: New function "Places": places such as home or work are defined as a circle with a radius of 50 m to 5 km. "Home" is built in, sits at the controller's location and has 150 m by default. Every device that reports a location, e.g. a vehicle, is assigned to the place it is at, with some leeway when leaving to absorb inaccurate GPS positions. Each place is a device with "Someone is there", "Number present" and, per device, "‹device› is there". Automations can react to them, e.g. "car arrives at work" or "car leaves home", and "Home" can be used as a source in presence detection
• Backend: New skill "Vehicles": electric, hybrid and combustion vehicles appear as a device, starting with Škoda through the MyŠkoda interface (API key from the MyŠkoda app); further brands will follow in the same skill. Depending on the vehicle, state of charge, range, fuel level, charging state and power, lock state, doors, windows, mileage, position and address as well as climate, auxiliary heating and ventilation are available. Charging, charge limit, charge mode, climate with set point, auxiliary heating (with S-PIN) and ventilation can be controlled, also from automations. The vehicle is queried every 15 minutes, every 5 minutes while charging or while climate control runs, and the manufacturer's query quota is respected. An expiring API key is reported 14 and 3 days in advance
• Backend: Zigbee: Support for the Danfoss Icon2 main controller (Basic and Advanced) for floor heating. Each room appears as its own thermostat with room temperature, adjustable setpoint, heating status, humidity, floor temperature, battery level and room status. An Icon2 that is already paired has to be removed and paired again
• Backend: Z-Wave: garage door openers and gates with Barrier Operator are supported. They appear as a garage door, can be opened and closed and report whether they are open, in the app, in Apple Home, in the iPhone widgets and with Siri
• Backend: Device profiles can assign their values to sections. The profiles for heat pumps, heating systems, inverters, chargers, appliances and vehicles already do
• Backend: Temporary files that are no longer needed are deleted automatically, e.g. leftovers of aborted backups, restores, uploads, imports and software updates. Previously such files could remain after a restart or power failure and gradually fill up the controller's storage
• Backend: New documentation APIs for integrators: getNotes, setNote and the event onNoteChange for notes on automations and schedules, scenes, variables, rooms, zones, devices, skills, functions and their instances, notifications, links and users. Administrators only; deleting an object removes its note as well (a skill keeps its note when it is switched off). The MCP server can read notes (note_list)
• Backend: New describeEvent and describeEvents APIs: describe an automation in one sentence in the language of the connection, also one that has not been saved yet, and also deliver it in parts (keywords, names) for highlighting. The new MCP tool event_describe uses them to explain automations
• Backend: New setSceneIcon API: changes only a scene's icon without re-creating the scene as setScene does; locked scenes stay unchanged, apps receive onSceneUpdated
• Backend: Wallboxes report "Charging", heat pumps "Compressor running", Home Connect, Matter appliances and robot vacuums as well as the Husqvarna Automower "Active" while they are at work. The values can also be used in automations
• Config/UI: On the KNX page under "Addresses", the manually added group addresses can be exported for importing into the ETS (XML or CSV), optionally together with the addresses of the ETS projects
• Config/UI: New page "Motion lighting" under Functions: create, edit and delete instances in a list, switch "Automatic active" and "Permanently on" right in the list. A status column shows live what each instance is doing, e.g. "On, 1:45 left", "Prewarning" or "Locked"
• Config/UI: New page "Adaptive lighting" under Functions: create, edit and delete instances, edit the curve as a table and preview it over the day with sunrise and sunset. The list shows the current target value of each instance, and the instance page shows for each light whether it is paused and until when
• Config/UI: New page "Places" under Functions: create, edit and delete places. The centre is set on a map, entered as coordinates or taken from a device's location, the radius with a slider or directly at the circle. The list shows live which devices are there and since when, a second list all devices with a location, each of which can be excluded from the assignment. "Automation arrives" and "Automation leaves" open the automation editor with a prepared trigger
• Config/UI: New skill page "Vehicles": manage accesses per brand with the API key's expiry date and renew the key, add vehicles with a wizard using the vehicle identification number and optionally give them a licence plate, edit charging profiles with target state of charge, charging windows and departure times, store the S-PIN for the auxiliary heating, switch the position off per vehicle, and see in the diagnostics when the vehicle last reported and how many queries are left
• Config/UI: New automation condition "Minimum duration": the actions only run if triggers and conditions stay true for the set time without interruption, e.g. a notification when the garage door has been open for 30 minutes. If the state ends earlier, nothing is run
• Config/UI: Vacation mode: a status box at the top of the page shows the state at a glance (vacation mode, period, control) together with the presence simulation and today's plan: the on and off time per device, which devices the simulation has switched on right now, and the next switching with a countdown. The simulation can thus be checked during the day instead of by watching in the evening
• Config/UI: The visualisation editor for rooms and zones shows the elements the way the app draws them: devices as buttons with their icon and current state (a light that is on in green, blind position, temperature value), rooms as a group of room, light, shading and music buttons with a status line. The size can be switched between S, M, L and XL as in the app; names appear on hover, while dragging or permanently with "Show names". Each element thus sits in the app exactly where it was placed
• Config/UI: Sign-up for the nomos newsletter: in the first-time setup with a checkbox in the "Diagnostics and Usage" step, later in your own account under Users in the "Newsletter" section, which shows the address the confirmation mail goes to. The sign-up is confirmed by e-mail and can be cancelled at any time via the link in the newsletter
• Config/UI: Light and dark appearance: under "Appearance" at the bottom of the sidebar, on the login page and in the first-time setup you can choose "Dark" (default), "Light" or "Automatic" (follows the operating system setting). The choice is stored in the browser
• Config/UI: In a device's "App Display" tab the elements appear in the same sections as in the app. Sections can be moved as a whole, elements within their section. In the profile editor the new field "Group" assigns a value to a section
• Config/UI: Yes/no, date and time variables have their own controls in automations: On/Off for yes/no, a date or time field with a picker instead of a free text field
• Config/UI: Notes for integrators: a note icon sits next to the name of automations, schedules, scenes, variables, rooms, zones, devices, skills, functions and their entries, notifications, links and users. It shows whether there is a note and when it was last changed, and opens a field to write it. In the lists notes can be edited right away, the search also finds their text, and duplicating an automation or scene copies its note. Notes do not appear in the app
• Config/UI: Every automation describes itself in one sentence, e.g. "When Motion (Hall) is on (only on change) and between sunset and sunrise, then Wall light (Hall): Turn On" or "Every day at 20:00, then Position of Awning (Garden) to 100". The sentence sits below the header in the editor and follows every change; in the list it appears as a tooltip on the name, and the search finds it
• Config/UI: Sonos: New automation actions "Play TuneIn Station" (starts a TuneIn radio station by its name) and "Play Stream URL" (plays an internet radio stream by its address, https included)
• Config/UI: Automations can be switched on and off in the editor with "Status: Active" under the name, like scenes and schedules. A switched-off automation stays saved but does not run; new automations are active
• Config/UI: When adding a user, "Status: Active" sets whether they can sign in right away, so a user can also be created disabled
• Daemon: Sonos: New command PLAYTUNEIN starts a TuneIn radio station by its name, without saving it as a favorite first. Every word of the search has to appear in the station name, case does not matter, and umlauts may be spelled out. If no station matches, the command reports ERR_NOT_FOUND; if TuneIn cannot be reached, ERR_NOT_AVAILABLE. Requires an internet connection
• Daemon: Mappings can compare a value with a list and turn it into yes/no (%in), e.g. {$STATUS$,%in2|3}

Changes

• App/UI: Extensive design refinements throughout the app, including a redesigned start and sign-in page, more consistent device views and controls, and a reworked screensaver
• App/UI: Pairing devices via Z-Wave and Zigbee: instead of the controller's raw messages, the dialog shows which step pairing is in (ready, device found, being included), with progress and remaining time. A newly found device is then selected automatically, and an error comes with "Try again". The same applies when removing a Z-Wave device. If the controller is still busy when pairing starts, e.g. with devices that do not respond, the dialog waits up to 90 seconds and says so
• App/UI: When the controller applies a changed configuration, the app no longer blocks with a full-screen "nomos Controller is configuring the system.". A slim note "Applying changes …" appears at the top instead, and only when it takes more than a moment; the app stays usable. If it takes longer than 30 seconds, the note says so
• App/UI: Translations refined – French, Italian and Dutch texts corrected
• App: Apple Watch: The Controller's name appears in the app's accent colour, the scene buttons are a neutral grey, as in the widgets
• App: iPhone: widgets, Control Center and Siri send commands directly via remote access as soon as the Controller cannot be reached on the same network: without Wi-Fi, but also on another Wi-Fi, e.g. with wireless CarPlay, which runs over the car's Wi-Fi. This needs remote access to be set up. Until now the app first tried the local connection on the go and waited up to 60 seconds on mobile data
• App: The tile is highlighted for more devices: appliances and robots while they are at work, wallboxes while charging, heat pumps while the compressor runs, thermostats while heating or cooling, TVs and receivers while switched on, on a water, gas, CO, frost or hail alarm, as well as binary inputs and armed alarm systems
• Backend: The controller saves its data to internal storage much less often. This considerably reduces the write load on the eMMC storage and extends its lifetime
• Backend: KNX garage doors with an impulse input (addon) now have "Open" and "Close" like every garage door and can therefore also be operated from Apple Home, the iPhone widgets and Siri. Both buttons send the impulse; whether the door opens or closes depends on its position, as before
• Backend: A device's quick config no longer offers actions that need an ID, a setting or a fixed mode (e.g. Wiser "Trigger Job", programs, HVAC mode); automations still offer them
• Config/UI: New, consistent look in the nomos design: type, colours and spacing as in the app, the website and the manual. In forms the label sits above the field, read-only information such as the device details appears as a two-column list, sections have uniform titles, and every view highlights exactly one main button. Rebuilt among others: Cloud, Cameras, user permissions, Software Update, a device's "Data Log" tab and pairing via Matter and HomeKit
• Config/UI: The scene selection when editing a schedule is easier to scan: scenes are laid out in several columns inside a scrollable area, can be filtered with a search field and narrowed down to the chosen ones with "Show selected only"; a counter shows how many scenes are selected
• Config/UI: System variables: the category is the first column, sorting is by category and name, and the search also matches categories
• Config/UI: The automation condition "Retarder" is now called "Run-on time". Both time conditions come with a short hint, and the time can be entered in seconds, minutes or hours
• Config/UI: Design adjustments to the skill device lists (e.g. Z-Wave, Zigbee, Matter, Philips Hue): the lists share one look, the buttons in each row are smaller, and device descriptions use the full width instead of being cut off early
• Config/UI: The Matter and MCP skills are no longer in beta: the label on the skill page is gone, for Matter also the beta note
• Config/UI: The maps in the settings under "Location" and in the initial setup use OpenStreetMap instead of Google Maps. The initial setup suggests the browser's time zone
• Config/UI: A device's tile is highlighted by the same rules as in the app, and devices with a malfunction appear red
• Config/UI: A device's Quick Config only shows values it makes sense to switch there. Settings, identifiers, status codes and the like remain available for automations. In the profile editor, the "Quick Config" column sets this per value
• Config/UI: Pairing devices via Z-Wave and Zigbee: instead of the controller's raw messages, the dialog shows which step pairing is in (ready, device found, being included), with progress and remaining time. A newly found device is then selected automatically, and an error comes with "Try again". The same applies when removing a Z-Wave device. If the controller is still busy when pairing starts, e.g. with devices that do not respond, the dialog waits up to 90 seconds and says so
• Config/UI: While the controller applies changes, user, search and help in the top bar stay usable; a calm note "Applying changes…" sits beside them, on a smartphone a turning icon that was missing there before. Short applies no longer show a note
• Config/UI: The Security page starts with a status head: it names the condition after the most severe finding (No issues found, Room for improvement, Action needed, Critical), counts the issues per level, shows when the check ran and offers "Check again". The table shows the severity as a level with its number, e.g. "Critical 10"
• Config/UI: Translations refined – French and Dutch texts corrected
• Daemon: Automations keep their state across a restart, a power failure and saving an automation. If a state changes during the interruption, e.g. presence, the related automation fires once after the start; without a change nothing fires. Until now such a change was lost. After an interruption of more than 2 hours, automations start without a saved state as before
• Daemon: Sonos: Favorites can also be started by part of their name. An exactly matching name still takes precedence; if several of the first 100 favorites match, the first of them is played
• NodeRED: Upgraded to version 5.0.8

Fixed

• Security: NOMOS-SA-2026-001, Backend, medium. Logged-in users without administrator rights and remote access clients could retrieve the Matter and HomeKit pairing codes and, shortly after its creation, the key of a direct VPN client. Affected: firmware up to 3.1.0. Fixed in 3.2.0. Please install the update and check under Matter which ecosystems the bridge is paired with.
• Security: NOMOS-SA-2026-002, Backend, medium. A device on the local network could trigger a restart of the backend without logging in and, by repeating this, force emergency mode. Affected: firmware 2.8.7 to 3.1.0. Fixed in 3.2.0. Please install the update.
• Security: NOMOS-SA-2026-003, Backend, medium. A logged-in administrator could use the addon profile interface to write files outside the addon library and replace built-in device profiles. Affected: firmware up to 3.1.0. Fixed in 3.2.0. Please install the update.
• Security: NOMOS-SA-2026-004, Backend, medium. On the local network, a connection without login could read device states and notifications. Logged-in users without administrator rights could retrieve credentials of integrated services and devices as well as cloud account details. Affected: firmware up to 3.1.0. Fixed in 3.2.0. Please install the update.
• Security: CVE-2026-48779, ws, high. A device on the local network could drive the controller into memory exhaustion via WebSocket fragments. Affected: firmware 2.6.5 and 2.8.2 to 3.0.1. Fixed in 3.1.0. Please install the update.
• Security: CVE-2026-31808, file-type, medium. A manipulated response from an integrated camera could block the sending of notifications until the next restart of the backend. Affected: firmware up to 3.0.1. Fixed in 3.1.0. Please install the update.
• App/UI: Relative times such as "a few seconds ago" were shown in English when the app was set to French, Italian or Dutch. They now follow the selected language
• App/UI: When remote access was withdrawn from an account, the app kept trying to connect on the go
• App/UI: An account without the remote access permission got "Invalid username or password" on the go, even with the correct password. The app now says that remote access is not enabled for this account. A wrong password is still reported as such
• App/UI: With some dimmers "Stop" appeared as an extra button below Brighter/Darker
• App/UI: The passcode only protected the entries in the settings, not the pages behind them. "Add Scene" and a long press on a scene opened the Scene Editor, the link in vacation mode the adjustable values and "Update available" under Infos the update page, right after starting the app even without any lock. Now each of these asks for the code first and then goes on to the page; "Add Scene" is hidden while the app is locked
• App: iPhone: After moving to a new iPhone, widgets, Control Center, Siri, CarPlay and the Apple Watch no longer worked on the go, while the app itself did: remote access rejected their commands. They now identify themselves to remote access with the same device ID as the app
• Backend: Minor fixes and optimisations in usage recording and the suggestions derived from it
• Backend: After an update from version 2.8.2 or older, individual commands to devices could be held back permanently and cause high CPU load on the controller
• Backend: The colour temperature of KNX, Wiser, Somfy and free@home lights arrived wrong in Matter (e.g. Apple Home), Amazon Alexa and Google Home; a KNX light at 4000 K, for example, appeared in Apple Home at about 2660 K. Colour temperature is now handled uniformly for all devices and converted correctly at these interfaces. Matter uses the actual range of each light, also for Philips Hue and Zigbee. Google Home can now also control the colour temperature of lights without colour, within the actual range of the light. For free@home lights, the gradient of the colour temperature slider in the app was also reversed
• Backend: Automations that compare a value on a reversed scale with "greater than" or "less than", e.g. the colour temperature of a KNX light or the position of some blinds, triggered in the wrong direction. This applies to existing automations once they are saved again. If such a comparison was deliberately entered the other way round so far, adjust it when saving
• Backend: Shelly: The setpoint of Shelly thermostats and the illuminance of Shelly sensors were converted incorrectly. 21 °C, for example, appeared as 10 °C, a setpoint set in nomos reached the thermostat with a wrong value, and automations using illuminance values did not trigger. Existing devices and automations are corrected automatically during the update; the displayed values are correct once the device reports next time
• Backend: "Setup for new User" did not reset the Matter bridge, although the hint announces it. Pairings made during the installation, e.g. with Apple Home or Google Home, remained after the handover to the customer. The Matter bridge is now reset; Matter devices integrated into nomos are kept
• Backend: Deleting a device could in rare cases, depending on the content of the system variables, cause the backend to restart
• Backend: Devices are now updated more reliably to a new version of their device profile. Until now a device could be lost in the process, addons in particular. Devices now keep their rooms, values, data logging and automations; addons take over the commands and polling intervals of the new device profile. An interrupted update is completed on the next start
• Backend: Zigbee: On devices with several channels, e.g. two-gang switches, commands to a single channel did not reach the device
• Backend: Z-Wave: newly included notification sensors (device class 0x07, e.g. door and window contacts) appeared as garage door openers, in Apple Home with buttons that did nothing. They are now recognized as sensors. Devices included earlier keep their category
• Backend: Z-Wave: devices of the device classes Window Covering, Controller and Entry Control without a device profile of their own got no category when included
• Backend: For users without administrator rights, camera images and cover images, e.g. of music, could stay empty in the app because the controller refused them access. Room permissions still apply
• Backend: Zigbee: Whether pairing could be started or stopped never reached the Config UI and the app; if starting failed, e.g. because the Zigbee stick was not ready, it went unnoticed. The controller now reports the result
• Config/UI: Added missing French, Italian and Dutch texts, among others in the KNX Secure settings, which showed in English there until now
• Config/UI: Z-Wave and Zigbee devices without a device description were missing from the "Manage Devices" list, which in the worst case stayed empty. They now appear as "Unknown device" with their node number or address and can be deleted; for Z-Wave a hint points to the interview, which can be started right there
• Config/UI: Relative times, e.g. under Administration > Mobile Devices, were shown in English ("2 months ago") when the UI was set to French, Italian or Dutch. They now follow the selected language
• Config/UI: Under Administration > Settings a manually picked date or time was never sent to the controller, only "Apply System Time" had an effect. The picked time can now be set with "Apply"
• Config/UI: Temperatures in the device settings carry the unit of the system setting, i.e. °F instead of a fixed °C when the system is set to Fahrenheit
• Config/UI: In automations, KNX switch values (DPT 1.001) showed "On/Off" untranslated in the other languages, the operator of a text variable rule stayed empty when the rule was stored with "==", and RGBA colours showed red in the colour wheel instead of the set colour
• Config/UI: Snapshot and MJPEG cameras show in Safari again. Until now only the warning icon appeared there, a snapshot at most once briefly
• Daemon: Automations with a run-on time (formerly "Retarder") now also work together with time triggers, time conditions or limits such as "Once a Minute". Until now the run-on time was ignored or another condition got lost. Long actions after the time has passed are no longer cut off. Applies to existing automations once they are saved again
• Daemon: Philips Hue: Identifying a group or room did not make the lights blink, although the command was reported as successful. Groups now blink; error messages from the bridge appear in the log
• Daemon: System variables were written to internal storage immediately on every change. Changes are now saved in batches
• Daemon: On every engine restart, e.g. after configuration changes, an addon's previous TCP connection stayed open and another one was added. The addon's "reachable" state could then keep flipping and put a heavy load on the controller
• Daemon: Sonos: Internet radio streams with an https address (PLAYURI) did not play, although the command was reported as successful. They play now; http addresses work as before
• Daemon: Sonos: Commands the speaker refuses were reported as successful, e.g. "Next track" during a radio stream. They now report an error with the speaker's code (e.g. ERR_UPNP_701); the speaker stays connected