Assign and verify —
right at the device. Just like ETS.

1. Is ETS6 running with the KNX2GO ETS app open?
2. Are phone and PC on the same network (Wi-Fi)?
3. Firewall: allow inbound access to port 8642 (or the process ets6c.exe) on the PC — on the private network profile.
4. Restart ETS — this rebinds the ETS app's listener freshly (helps after a network change).
5. Re-scan the QR — the token changes each ETS session.

The download is performed by ETS, not by the phone. So this function depends on the ETS pairing, not on the app's bus connection.

1. Is the connection to the ETS app live? Phone and PC on the same Wi-Fi, ETS6 open with the KNX2GO ETS app running. After restarting ETS, re-scan the QR.
2. Is an interface selected in ETS? ETS downloads over its own connection — without a selected interface it cannot start the download.
3. Does the device have a planned individual address? The function is only available for project devices that have an address assigned.
4. If the app reports "download failed" or "timed out", check on the PC whether the same download succeeds in ETS — if it doesn't, the cause is the bus, the device or the application, not the pairing.

Check the portal credentials (username + password) — after a reinstall they must be re-entered. Keep the SSL option enabled in the connection settings.

1. Is the printer switched on and in range?
2. Is Bluetooth on and the "Nearby devices" permission granted?
3. In Settings → Printer, turn on the "Printing" switch, then "Select printer".

The printer and the label template are set up once under Settings ▸ Printer — the template then applies to every label.

• Printing — the master switch that enables printing from the app
• Connection — pair via "Select printer". If the D110 doesn't show up: wake it, keep it in range and if needed use "No printer listed? Show all Bluetooth devices"
• Label template — width and height in mm, orientation (portrait/landscape), font size and intensity for contrast
• Second line — below the address, choose Off, Room, Name or free Text
• Logo — a single-colour line graphic can be stored
• Preview and Test print — check the template before you use up a roll at the cabinet

Without a bus connection no device can be programmed — so the buttons stay inactive until the app is connected to a KNXnet/IP interface or router.

1. Check the connection status on the Start tab.
2. If no connection is active: under Connection, search for interfaces or enter IP and port manually.
3. As soon as the connection is up the buttons become active right away.

Every device response carries a routing counter (shown as ↻N in the list). From it the app works out how many couplers the response passed and compares that with what the topology expects:

• Green — matches the topology or the deviation has been classified
• Red — unexplained mismatch, e.g. "⚠ 3 instead of 1 couplers"
• Grey — cannot be judged through this interface

Most common cause: line repeaters and segment couplers increment the routing counter but don't appear as a level of their own in the ETS topology. How to classify it: on a mismatch, a selector appears — "behind line repeater" or "behind segment coupler". It then counts as explained, the light turns green, and the classification is stored.

If discovery finds nothing, connect manually by IP and port. Some networks block multicast discovery — the manual connect still works.

The KNX2GO ETS app only serves the project currently open in ETS. If a different project is open, open the correct one in ETS and re-scan the QR.

Use the FDSK scan in commissioning. Captured certificates are collected and reported back into the ETS project.

Every captured certificate can be reviewed and removed individually at any time — so a mis-scan is nothing to worry about.

1. In the ETS tab, scroll to the bottom and open "View certificates".
2. The "Captured certificates" list shows the serial number and the FDSK per device.
3. Swipe the wrong entry to the left and choose Delete.
4. Scan the correct code again — the corrected FDSK is reported to ETS as usual.