6.1Gateway console and logs

What each tab of the gateway console shows, and what to look for in the logs.

Every gateway serves a small web console for status, cloud registration, client approval and logs.

#Open the console

In a browser on the same network, go to:

http://<gateway-ip>:3127/

Sign in with the gateway account. On first use you will be asked to change the password. The console signs you out after 5 minutes of inactivity. The Password button changes your password; Logout ends the session.

#The tabs

Tab	What it shows
Overview	Address, uptime, serial number and board, and the status of the three services: Gateway runtime, KNX bridge and SIP gateway. All should read active.
Cloud	Cloud registration and sync, and Deploy Pairing (the deploy token for the Configurator).
Zigbee	The Zigbee coordinator, permit-join and the paired devices.
Clients	Client Devices (approve app devices) and Registered SIP Clients (which intercom extensions are online).
Voice	The voice gateway, Apple Home (Siri) pairing, Alexa and Google Home status.
Network	KNX interface status, network interfaces, time zone and the serial interfaces.
Monitor	Live KNX bus messages, server logs, a KNX Send Telegram form, maintenance actions and software updates.

#Cloud tab

Cloud Service lists the status (connected, disabled, registration_required or error), account, gateway ID, last heartbeat, project sync state and last error. The actions are Enable, Reconnect, Disable and Clear all cloud data on this gateway.

Enable opens the registration dialog (account email and password, plus a signup code only when creating a new account).

#Clients tab

This is the first place to look for intercom problems. Registered SIP Clients should list the door station (for example 901) and each app user that is online (for example 1001). An empty list reads No SIP clients registered.

#Monitor tab

Log source filters the log: every source, KNX, Cloud, Gateway runtime, SIP gateway, Logic calculator, Modbus, Zigbee or Storage. Server Logs shows the latest 80 lines and refreshes every 5 seconds.
Bus Messages shows KNX telegrams (time, sender, destination, data). No bus messages yet. means nothing has been seen on the bus.
Send Telegram writes to, or reads, a group address from the gateway.
Maintenance has Software restart (restarts only the Veltnova runtime), Full restart (reboots the gateway) and Shutdown.
Software Update shows the installed version and the latest available one. See Updating the gateway software below.

#Updating the gateway software

The gateway looks for a new version of its software by itself, a minute or two after it starts and then every six hours. When there is one, a bar appears at the top of the console: Version x.y.z is available, with Update now and Later. The same version is in Monitor > Software Update, with Check for updates to look at once.

Click Update now. The console shows what is new in that version and asks you to confirm. Nothing is installed before you confirm.
The gateway downloads the update, checks that it is genuine (signed by Veltnova) and not damaged, and keeps a backup of the current software.
It installs the update and restarts. It is offline for about a minute, and the console reloads by itself.

Projects, users, images and settings are kept. If the new version does not start properly, the gateway puts the previous version back by itself and the console says so under Software Update. The latest version number is also on the Downloads page. The gateway software is only updated this way, from the gateway itself.

#What to look for in the logs

Use Monitor > Log source to narrow the Server Logs to one area, then look for:

Modbus (source Modbus): lines such as timeout reading slave 3 function 4, or a Modbus exception code from the device.
KNX (source KNX): [knx] lines, including a watchdog message when the bus monitor restarts.
Intercom (source SIP gateway): Veltnova SIP REGISTER accepted from 901, ring group 9001 selected 1001, and target 1003 has no registered contact - skipped.
Missed-call snapshots (source Gateway runtime): lines starting with [intercom].

#Restarting

Changes to the web assets are picked up without a restart.
Software restart on the Monitor tab restarts the Veltnova runtime. It can take up to about 90 seconds to stop, which is normal. Use Full restart only if that does not help.

Still stuck? Open a ticket from the support portal and mention the page you followed.