Bus monitor
The Bus monitor tab shows decoded KNX telegrams from the bus — your first diagnostic stop when a device does not react. It shows a time window of recorded telegrams, not a continuous stream: with no dates set, the table lists the telegrams of the last 10 minutes.
What you need: a working KNX connection and the history database service enabled (see “History & Data Logging”). Without the history database the tab shows a notice instead of data. Telegrams are recorded only while the server is connected to the bus.
Each telegram row shows the Time, Source, Destination, DPT, Value, Raw and Group address name. Value is filled only when the datapoint type of the address is known; Raw always shows the bytes. Group address name shows the room, device and object bound to the address or, failing that, its ETS name. In the Detail column, the info icon shows the bound device, object and room.
- Filter by time: open the two Pick a date fields, choose a start and an end, and click Apply to inspect a period (last night's heating cycle, yesterday's alarm event). Both dates are needed, and the range goes back seven days at most. Clear returns to the last 10 minutes.
- Search: type in Search telegrams.... The search matches the source address, the destination address and the message type (
read,writeorresponse); it does not search names. It also matches part of an address:0/0/2lists10/0/2as well. - Paging: results are paged ("Page 1 of 4") with First / Previous / Next / Last controls.
- Chart: click Show chart (the trend icon in the Detail column) to plot that address over the same period. When the datapoint type of the address is unknown, the chart plots the raw bytes as a number.
- Refresh reloads the same time window. To see telegrams that arrived after you opened the tab, change the search text or leave the tab and open it again.
📘 Note: Telegrams are written to the history database in batches, so a new telegram appears in the monitor after about 15 seconds, not at once.
