Frequently asked questions
Short answers to the questions asked most often during setup and operation.
If something does not work, you will find help under Common problems.
Network and remote access
Should the controller run with DHCP or with a fixed IP address?
The router must offer DHCP for the initial setup. For operation we recommend a fixed IP address. You set it under Administration → Network and apply it with Save and Restart. See Network.
What is the difference between remote access, Support VPN and Direct VPN?
- Remote Access: your customer operates their installation with the nomos system app while away. Only enable it with their explicit consent. See Remote Access.
- Support VPN: gives a support provider temporary access to the controller for as long as it is switched on. See Support VPN.
- Direct VPN: permanent access via your own WireGuard clients. See Direct-VPN.
How do I program a KNX interface or a serial bus system remotely?
Via the Support VPN or the Direct VPN, you share a single IP device with Expose local device to VPN. A USB serial adapter plugged into the controller is shared as a TCP port. On your computer you create a virtual COM port for it. Only one connection is possible at a time, and the baud rate must match. See USB Serial over VPN.
Devices and skills
How do I integrate a device for which there is no dedicated skill?
Via the Addons skill: load a suitable profile from the online library or by manual upload and create the device from it. If there is no profile, write to support@nomos-system.com with the manufacturer, the model and, if available, a link to the API. See Addons.
How do I connect Alexa, Google Home or Apple Home?
For Alexa and Google Home, link the controller to a cloud account under Cloud and then enable the nomos skill in the Alexa app or the service in the Google Home app. Apple Home and other ecosystems are paired via the Matter skill. See Cloud and Matter.
Can I specify my own MQTT broker?
No. Since version 3.0.0, nomos uses only the controller's broker. The MQTT settings show the address at which you connect your own MQTT client to the controller.
Which KNX connection type do I choose, and what do I need for KNX/IP Secure?
Tunneling connects to a KNX/IP interface, Routing uses multicast. For the Secure variants, upload the .knxkeys file exported from the ETS together with the export password. If the interface reports that the keyring file could not be loaded, check the export password or export the file again. See KNX Settings.
Users and permissions
How do I restrict a user to certain rooms or scenes?
Under Administration → Users → Permission, set Full Access, View only (rooms only) or Off for each entry on the Functions, Rooms and Scenes tabs. See Users.
What can the end customer change themselves?
You decide this through the permissions of each user, for example for scenes, schedules, automations, settings and remote access. Variables that you mark as Editable can be changed by them in the app. See Users.
How do I hand the installation over to the end customer?
First enter your contact details under Administration → Advanced → Integrator Info. They appear in your customer's app. Then, with Setup for new User under Administration → Configuration, you generate login details for the customer and pass them on as a document. Caution: this deletes existing users, signs out all users and resets remote access, signed-in devices and the Matter bridge. See Configuration and Integrator Info.
Updates and backup
How do automatic updates and security updates work?
Install security updates automatically is enabled by default. A security update is announced one week in advance, can be postponed at most twice by seven days and is installed on the chosen weekday in the installation window. Install all updates automatically additionally installs versions with new features. Create a backup before major updates. See Software Update.
When does the security check report that no backup has been created for a long time?
When no backup has been created in the last 120 days. Create a backup under Administration → Configuration and the notice disappears. See Configuration.
What do I need to bear in mind when restoring a backup?
The controller's software must be at least as recent as that of the backup, otherwise the restore is aborted. In that case, update the software first. The backup must come from a controller of the same product. After the restore, the controller restarts, the Direct VPN is switched off and its VPN clients are deleted. See Configuration.
What is the difference between the three reset options?
- Reset Data deletes all data of the installation, signs it off from the cloud and restarts. The network settings are kept.
- Reset all Data and Settings returns the controller to its factory state, including the network. The installation is not signed off from the cloud.
- Reset Cloud Settings only deletes the stored cloud connection. All other data is kept.
Create a backup before using the first two; they cannot be undone. See Configuration.
How do I move an existing installation to a new controller?
During the initial setup of the new controller, choose Restore from backup file in the Setup step, using a backup from Administration → Configuration. If the old controller is running on the same network, Migrate from a system over local network also works. See 5. Setup.
Which data leaves the controller?
The usage recording stays on the controller. Only if suggestions are to be phrased by a language model are the device name, the room and the reason for a suggestion sent via the nomos cloud to the language model provider. Diagnostic, usage and crash data are only sent if the corresponding options under Administration → Advanced are switched on. See Advanced.