Hot topics
The things that catch installers out most often. Read these before your first site.
These points explain most of the support questions we see. Each links to the page with the full detail.
#Everything on the gateway is off until you switch it on
In a new project, every component in the Server tree is Disabled: KNX, the RS485 and RS232 ports, Zigbee, MQTT, the SIP gateway and the managers. A component that is disabled is saved in the project but not started on the gateway. Turn Enabled on for each one you use.
See Your first project and KNX basics.
#One user, one approved device
Each app user is bound to a single approved device. When a second device signs in with the same user and you approve it, the first device is revoked and can no longer sign in. Create one user per person or per panel.
See Connecting the apps.
#Regenerating the deploy token breaks every paired Configurator
The deploy token on the gateway console is what lets a Configurator publish projects. Regenerate deploy token immediately invalidates the old one. Every Configurator that was paired has to paste the new token, or its deployments fail with A valid deploy token is required.
#Remote cameras need H.264 and two forwarded ports
Live camera viewing from outside the building needs an H.264 stream. For the Local + Remote connection type, the site router must forward 8889/TCP and 8189/UDP to the gateway. Without them, remote viewers only get cameras when Cloud is also enabled.
See Common problems and fixes.
#Away from home, the intercom only rings while the app is open
Over the cloud connection the app has no background ringing: it learns of a call while it is open. For a phone that should ring reliably, the call must reach it over the local connection.
See Intercom and door stations.
#Door release is not part of the SIP call
The intercom carries audio and signalling. To open a gate or door, wire the lock to a KNX relay and add a Switch or Action Button bound to that group address.
See Intercom and door stations.
#Save before you deploy
Save overwrites the project file in Documents\Veltnova Projects. The Configurator does not restore unsaved work after a crash. Use Export for a dated copy before large changes.
#Modbus is serial (RTU) and group addresses come from CSV
The Configurator configures Modbus RTU devices on the gateway's RS485 or RS232 port. KNX group addresses are imported from an ETS CSV export, not a .knxproj file. Plan the site around that.