Common problems
Solutions to the most common problems during setup and operation.
Setup and network
I do not know the controller's IP address
You can find it via the nomos system app, in your router or at discover.nomos-system.com using the controller's serial number. Open the address in your browser. If the controller has not been set up yet, the interface guides you through the initial setup. See First Steps.
After changing the IP address I can no longer reach the controller
Open the configuration interface at the new address. If you do not know it, discover.nomos-system.com will help. Wiser SmartButtons have to be set up again after the controller's address has changed. See Network.
A user can reach the controller locally, but not when away
Check whether Remote Access is enabled on the controller and whether the user has Full Access for Remote Access on the Functions tab of their permissions. Without this permission the controller rejects sign-ins from outside. The app then shows the same message as for a wrong password. See Users.
The WireGuard configuration of a VPN client is gone
It can only be downloaded once. Create a new client with Add Client to VPN and remove the old one in the VPN Clients overview. Turning off the Direct VPN removes all clients. See Direct-VPN.
Devices and skills
A device shows “Device is not reachable”
The General tab shows when the device last communicated successfully. Check the power supply and the network, and use Log to jump to the messages of this device. With Wi-Fi devices such as Shelly, a change of address is the most common cause: set up a DHCP reservation in the router. See General.
ZigBee or Z-Wave devices have a poor connection or drop out
Move the radio dongle away from the controller with a USB extension cable at least 30 cm long, and place the controller as centrally as possible. With Z-Wave, a Network Update helps after repositioning. Changing the ZigBee channel requires all ZigBee devices to be paired again. See ZigBee.
A skill's device search finds nothing
The devices must be on the same network as the controller and must first be fully set up in the manufacturer's app, such as the Sonos app, the Eltako Connect app, the Feller app or the Nuki app. Shellys without mDNS or in a different network segment are entered by hand with their IP address. See Skills.
KNX values are displayed or switched incorrectly
Usually a wrong data point type (DPT) was stored in the ETS and taken over during the import. Correct it in the ETS or on the Addresses tab for the group address. So that the state is correct after a restart, enable RoS (Read on Start) for status addresses. See KNX Address Management.
The Eltako gateway reports “The stored code was rejected.”
Enter the device code printed on the gateway's housing again, not the password of the Eltako Connect app. Do not reconnect the gateway repeatedly to try things out: it hands out only ten accesses and never frees one. Once they are used up, the only remedy is resetting the gateway in the Eltako Connect app. See Eltako.
No further ecosystem can be paired via Matter
For each further ecosystem, first click Turn On Pairing Mode and then use the QR code or PIN code. Pairing mode closes again after 15 minutes. If the controller reports Maximum number reached, nine ecosystems are already paired: remove one first. See Matter.
An AI client does not connect to the MCP skill
The MCP skill must be switched on, the token must be valid and enabled, and the client must be on the local network, because access from outside is blocked. After a restart of the controller, quit Claude Desktop completely and start it again. See MCP.
I cannot get into Node-RED
Sign in with a user of the “admin” group who has Full Access for Node-RED in their permissions. There is no separate integrator account for this. See Node-RED.
Users and passwords
A user has forgotten their password
They choose Forgot password? on the login page, enter their username and click Request access. This only works on the local network. An administrator compares the code shown and approves the request in the nomos system app or under Administration → Users → Incoming requests. The user then sets a new password. See Login.
The only administrator has forgotten their password
Without an administrator, nobody can approve an access request. Write to support@nomos-system.com: nomos support restores access with a rescue USB stick.
The security check reports a weak password
The notice Weak or non-existent user account password appears for active users without a password, with their username as password or with an obvious password such as “admin”, “nomos” or “test”. Set an individual password under Administration → Users.
Updates and operation
“Security update can not be postponed again”
An announced security update can be postponed at most twice, by seven days each time. After that, it is installed in the next installation window. You can also install it immediately under Software Update. See Software Update.
A software update cannot be installed
Check the internet connection under Administration → Network and the free storage under Administration → Advanced → Performance. The update states how much storage it needs. Without internet, install an update file via Manual Upload. See Software Update.
“Emergency Mode” appears at the top and all skills are switched off
If the software crashes at least ten times within 15 minutes, the controller starts in emergency mode and switches off cloud access and all skills. First try a software update. Reset in the notice restores the previous state and restarts. If you only close the notice, emergency mode ends, but the skills remain switched off. If the problem persists, contact support@nomos-system.com.