ARCHIVED TRAINING / XKNX/xknx
xknx__xknx-1227
This is a preserved training example. Membership in the current training wave has not been verified.
Problem statement
2.6.0 filters telegrams from KNX gateway/tunnel device itself
**Description of problem:**
Since xknx 2.6.0, xknx no longer recieves/processes telegrams originating from the KNX gateway itself.
A RTU modbus device is connected directly to the gateway, which is why the packets originates from the gateway itself (address 1.1.255)
Other telegrams from the KNX/TP bus are received fine through the gateway.
- [X] using xknx standalone
- [X] using Home-Assistant knx integration
**Version information:**
- xknx / Home-Assistant release with the issue: xknx 2.6.0
- last working xknx / Home-Assistant release (if known): xknx 2.5.0
**KNX installation:**
Using a SE SpaceLYnk gateway, with a modbus based power meter connected. The gateway exposes the modbus data via KNX address 1/1/4 as a 4byte_float.
Other devices connected to the gateway over KNX/TP are unaffected by the update to 2.6.0 and still work.
Using https://github.com/XKNX/xknx/blob/main/examples/example_telegram_monitor.py to compare the versons.
With 2.5.0 i see telegrams from the modbus device, on 2.6.0 i don't.
Adding debug logging to the same script shows the frames being recieved, but ignored on 2.6.0:
`DEBUG:xknx.cemi:Ignoring own CEMI: <CEMIFrame code="L_DATA_IND" src_addr="IndividualAddress("1.1.255")" dst_addr="GroupAddress("1/1/4")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0xbe,0xa5,0xbb,0xb8]" />" />" />`
This change seems to be related to this commit:
https://github.com/XKNX/xknx/commit/996697ae8cce878aadfcbd95833b1fde3367008a
Is there a reason for these frames now being ignored? Is it possible to roll back this change?
Training membership
opd_e4b_cispo_v5 opd_e4b_pure_v6a opd_e4b_pure_v6b opd_e4b_pure_v7 opd_e4b_pure_v7b opd_e4b_self_audit_v4
Task issues extracted from preserved verified_rft_messages training examples. This is not a verified current RL wave manifest.
Task and snapshot provenance
Snapshot captured 2026-11-12T17:06:59.476467+00:00 · Autoresearch-Arena/gemma-4-developer-agent
{
"datasets": [
"opd_e4b_cispo_v5",
"opd_e4b_pure_v6a",
"opd_e4b_pure_v6b",
"opd_e4b_pure_v7",
"opd_e4b_pure_v7b",
"opd_e4b_self_audit_v4"
],
"examples": 32,
"instance_id": "xknx__xknx-1227",
"problem_statement": "2.6.0 filters telegrams from KNX gateway/tunnel device itself\n**Description of problem:**\r\n\r\nSince xknx 2.6.0, xknx no longer recieves/processes telegrams originating from the KNX gateway itself.\r\nA RTU modbus device is connected directly to the gateway, which is why the packets originates from the gateway itself (address 1.1.255)\r\nOther telegrams from the KNX/TP bus are received fine through the gateway.\r\n\r\n- [X] using xknx standalone\r\n- [X] using Home-Assistant knx integration\r\n\r\n**Version information:**\r\n- xknx / Home-Assistant release with the issue: xknx 2.6.0\r\n- last working xknx / Home-Assistant release (if known): xknx 2.5.0\r\n\r\n**KNX installation:**\r\nUsing a SE SpaceLYnk gateway, with a modbus based power meter connected. The gateway exposes the modbus data via KNX address 1/1/4 as a 4byte_float.\r\nOther devices connected to the gateway over KNX/TP are unaffected by the update to 2.6.0 and still work.\r\n\r\nUsing https://github.com/XKNX/xknx/blob/main/examples/example_telegram_monitor.py to compare the versons.\r\nWith 2.5.0 i see telegrams from the modbus device, on 2.6.0 i don't.\r\n\r\nAdding debug logging to the same script shows the frames being recieved, but ignored on 2.6.0:\r\n`DEBUG:xknx.cemi:Ignoring own CEMI: <CEMIFrame code=\"L_DATA_IND\" src_addr=\"IndividualAddress(\"1.1.255\")\" dst_addr=\"GroupAddress(\"1/1/4\")\" flags=\"1011110011100000\" tpci=\"TDataGroup()\" payload=\"<GroupValueWrite value=\"<DPTArray value=\"[0xbe,0xa5,0xbb,0xb8]\" />\" />\" />`\r\n\r\nThis change seems to be related to this commit:\r\nhttps://github.com/XKNX/xknx/commit/996697ae8cce878aadfcbd95833b1fde3367008a\r\n\r\nIs there a reason for these frames now being ignored? Is it possible to roll back this change?",
"repo": "XKNX/xknx",
"source": "v2/experiments/train_data/opd_e4b_cispo_v5/verified_rft_messages.jsonl",
"source_sha256": "a43610ad0dfb6ace95375cfae09000f41afc0338cc925af870a4ade7a9b20c4c"
}{
"captured_at": "2026-11-12T17:06:59.476467+00:00",
"membership": "archived training",
"membership_evidence": "Task issues extracted from preserved verified_rft_messages training examples. This is not a verified current RL wave manifest.",
"name": "Preserved post-training task archive",
"source": "Autoresearch-Arena/gemma-4-developer-agent",
"source_revision": "016496de222aaafca0d4ee4c18efc63ba616f76e",
"sources": [
{
"path": "v2/experiments/train_data/opd_e4b_cispo_v5/verified_rft_messages.jsonl",
"sha256": "a43610ad0dfb6ace95375cfae09000f41afc0338cc925af870a4ade7a9b20c4c"
},
{
"path": "v2/experiments/train_data/opd_e4b_hybrid_v3/verified_rft_messages.jsonl",
"sha256": "bd326303eb127e8e5e08f03daf97bb88d79d19709d59f3f93f348bc56686a8df"
},
{
"path": "v2/experiments/train_data/opd_e4b_onpolicy_v3/verified_rft_messages.jsonl",
"sha256": "960c680e797e823a0d3a22f4b1d5ef60a72971373d703b877340b0c9126aaf68"
},
{
"path": "v2/experiments/train_data/opd_e4b_pure_v6a/verified_rft_messages.jsonl",
"sha256": "f045b7ca5b3883a1e2eaee81e1c02a4a1b53dd7b7b36e98bacb2ba5823a15148"
},
{
"path": "v2/experiments/train_data/opd_e4b_pure_v6b/verified_rft_messages.jsonl",
"sha256": "0f62460a9706eea5e1605255896f191ab00cb5706c5f1f2e1c293e9a718218dc"
},
{
"path": "v2/experiments/train_data/opd_e4b_pure_v7/verified_rft_messages.jsonl",
"sha256": "e37f7bd675322f3f81500b73559d60d5f602ca0537bf19f5cb06332c728c7b72"
},
{
"path": "v2/experiments/train_data/opd_e4b_pure_v7b/verified_rft_messages.jsonl",
"sha256": "b864bdc8695183433eef6e31cb8d33fad44ba3aded2170c1ade4ad5b2944ce23"
},
{
"path": "v2/experiments/train_data/opd_e4b_self_audit_v4/verified_rft_messages.jsonl",
"sha256": "0026023745afb8f3dc1c176dc7f7171157b4ad5a66656b524af218e8e19ceee6"
},
{
"path": "v2/experiments/train_data/rft_e4b_aligned_v2/verified_rft_messages.jsonl",
"sha256": "92a4515fee9d152b0d4c510ee3ce4caaaffe2003ba7584469f8027f174aab18c"
},
{
"path": "v2/experiments/train_data/rft_v1/verified_rft_messages.jsonl",
"sha256": "a42453ccd7ac7680b0a03865e8e7080bc8bf74c8d9d193b440c441ed46f8512b"
},
{
"path": "v2/experiments/train_data/rft_v2/verified_rft_messages.jsonl",
"sha256": "18f4b3bd7e651f83c6acab479c9475e3fa50dc652a384f309e97146983ac85ba"
}
]
}