ETS Group Monitor troubleshooting preview
The preview shows KNX source context and Control4 candidates side by side so telegram, feedback and routing evidence can be reviewed before export.
Prove the telegram before editing Composer
Composer shows the Control4 structure, but ETS Group Monitor can prove whether a KNX write, read or feedback telegram is actually present on the bus from the tested access point.
That evidence matters because the same symptom can come from different causes: missing feedback object, wrong DPT, blocked filter table, gateway route problem, or a generated device that needs review.
What evidence helps the review
The useful evidence is not just a screenshot that something happened. The installer should capture which group address was written or read, what value was seen, which DPT is expected and whether the feedback object answered.
CoduWorks can keep that source context next to the proposed Control4 device so the review is about real signals, not guesses from names alone.
- Command group address and value sent from ETS.
- Feedback group address and value returned on the bus.
- DPT and object role expected by the generated Control4 device.
The monitor only proves the path you are watching
A Group Monitor trace is only as useful as the access point used to observe it. Seeing a telegram on one line does not automatically prove that the Control4 KNX/IP route can see it across routers, VLANs or line couplers.
That is why group-monitor evidence should be read together with gateway, multicast and filter-table context before the .codu package is built in Composer.
Review first, then rebuild only if needed
If telegrams and feedback are correct and visible from the Control4 path, then mapping and device generation can be reviewed. If they are not visible, rebuilding Composer devices only creates the same problem again.
The goal is to know whether the failure belongs to KNX infrastructure, ETS flags, DPT mapping or the final Control4 structure before running the build.
Official references checked
Technical claims on this page are kept close to official KNX, Control4, or manufacturer documentation.
Related tools and documentation
FAQ
Does CoduWorks replace ETS Group Monitor?
No. ETS Group Monitor is still the installer tool for proving bus telegrams. CoduWorks uses the ETS project context to prepare a reviewable Control4 build.
Why can Group Monitor show a telegram but Control4 still miss it?
The monitor may be connected at a different point than the Control4 KNX/IP route. Routers, filter tables, VLANs or gateway configuration can still hide the telegram from Control4.
What should I check before rebuilding devices?
Check command telegrams, feedback telegrams, DPT, read/transmit behavior, gateway route and filter-table visibility before recreating devices in Composer.
Use telegram evidence before the Composer build
Import ETS, review group addresses and feedback context, then export .codu when the source behavior is clear.