Owl Automata logo
  • Home
  • About Us
  • Services
  • Products
    Hotel As a Service
    Chameleon+
    Chameleon+From Room Design to Complete ETS Project - hotel automation made simple
    Fire Ant
    Fire AntAutomate the Tedious. Focus on What Matters
    Explore the HaaS concept
    Apps & Tools
    Pro Builder Ecosystem
    Pro Builder
    Pro BuilderETS app for importing generated .knxproj files into ETS.
    Application Template
    Application TemplateMicroapp for extracting, reusing, and sharing KNX application templates.
    SharkNX
    SharkNXConnect. Monitor. Control. ETS Mobile Toolkit on the Go
    View all products
  • Resources
  • Insights
  • Contact
Current versionv1.18.2
LanguageEnglishDeutschFrançaisEspañolItaliano
Documentation home

Getting Started with SharKNX

The SharKNX AssistantETS Projects in SharKNXKNX Data SecureKNX IP SecureThe Shark Hunt Concept

How to Use Assistant Aliases and ScriptsHow to Connect to a KNX GatewayHow to Create a Shark HuntHow to Export TelegramsHow to Inspect a Device's Communication ObjectsHow to Load an ETS ProjectHow to Program a Device Individual AddressHow to Read a Coupler Filter TableHow to Scan a KNX Bus LineHow to Send KNX CommandsHow to Set Up KNX Data SecureHow to Set Up KNX IP SecureHow to Use the Assistant

Project ConnectionsConnect PageDiagnostics PageMonitor PageProject PageSettings PageShark Hunts PageAssistant Page

Assistant CommandsAlias and Script File FormatDashboard File FormatExport FormatsFrequently Asked QuestionsLimitsSide Menu and ActionsMonitor Filter SyntaxSettings ReferenceSubscription PlansSupported Datapoint Types (DPTs)
How-To Guide

How to Read a Coupler Filter Table

Read the filter table of a KNX line coupler or IP router with SharKNX - see which group addresses pass, find blocked ones, and fix telegrams that don't reach another line.

On this page
  1. Before you start
  2. Read the filter table
  3. Understand the results
  4. Troubleshooting: a telegram doesn't reach another line
  5. Related

Line couplers, area couplers, and IP routers don't pass every group telegram from one line to the next. Each keeps a filter table - the list of group addresses it lets through - which ETS writes to it when you download the coupler. If a group address is missing from the table, its telegrams stop at the coupler.

SharKNX reads the filter table straight from the coupler's memory and shows it in your project's group address tree, so you can see at a glance what passes and what doesn't.


Before you start

  • Load the ETS project that contains the coupler - see Load an ETS Project.
  • Connect to a KNX gateway that can reach the coupler - see Connect to a Gateway.

Read the filter table

  1. On the Project page, open the Devices, Topology, or Buildings tab and tap the coupler. In the Devices tab, the Couplers filter under advanced filters narrows the list to couplers.
  2. In the device sheet, tap Read Filter Table. It is shown for couplers only - devices whose address ends in .0, such as 1.1.0 or 1.0.0.
  3. The Filter Table page shows the coupler: its name, address, manufacturer, IP address, and line.
  4. Tap Read Filter Table. The table is a few KB in size, so reading it takes around 20 seconds.
  5. SharKNX lists every group address the coupler passes, in the project's group address tree with names and datapoint types.
Filter Table page for an IP router before reading, with the Read Filter Table button and the note that reading takes around 20 seconds Filter Table results listing the group addresses the coupler passes, including one Not found in project

Understand the results

You see It means
A group address in the list The coupler passes telegrams to and from it
A group address missing from the list The coupler blocks it - telegrams on it don't cross this coupler
Not found in project The coupler passes an address that isn't in the loaded project - usually a leftover from an older project version, or a project that doesn't match the installation

Troubleshooting: a telegram doesn't reach another line

A switch on line 1.1 sends to 1/2/3, but the actuator on line 1.2 never reacts, although the Monitor shows the telegram being sent.

  1. Read the filter table of the coupler between the two lines - here the line coupler 1.2.0.
  2. Look for 1/2/3 in the list.
  3. If it's missing, the coupler blocks it. Usually the group address was linked after the coupler was last downloaded. Download the coupler again in ETS so its filter table is updated.

If the address is in the table and the telegram still doesn't arrive, check the coupler's own settings in ETS - couplers can also be set to block or pass all group telegrams regardless of the table.


Related

  • Project Page - the Filter Table page and device sheet
  • ETS Projects in SharKNX - what a loaded project unlocks
  • Scan a KNX Bus Line - check which devices answer on a line
PreviousHow to Program a Device Individual AddressNextHow to Scan a KNX Bus Line

On this page

  1. Before you start
  2. Read the filter table
  3. Understand the results
  4. Troubleshooting: a telegram doesn't reach another line
  5. Related

← SharKNX product page

logo

Solutions

  • Services
  • Products
  • HaaS

Company

  • About Us
  • Contact

Legal

  • Privacy Policy
  • Cookie Policy
  • Terms & Conditions

Contact

  • info@owl-automata.com
  • Athens, Greece

© 2026 OWL-Automata.com. All rights reserved OWL Automata

  • Terms & Conditions
  • Privacy Policy
  • Cookie Policy