Totally right, but that’s the one and only incoming frame here. I have no explanation for that
This is not supported. Imho it’s not respecting Knx specifications, but that’s not the main issue here.
In your further logs there are now incoming frames shown. There should be even more, but there should be many more
Tbh I have no idea since there are some frames incoming and some not.
You could try UDP instead of TCP for a test, but usually TCP should be more reliable.
Maybe also check if there is a firmware update for your IP interface.
Yes, UDP was, until ~1-2 years, the only way to communicate with IP interfaces. You can set that when you manually configure the connection in the Knx integrations settings.
OK, I changed KNX integration configuration to UDP, which seems to result in some improvement, but still with some unpredictable delays (up to seconds) in the responses, and often no response at all.
Here is a small excerpt from the log, while i was playing around with the mezzanine light switch in the HA UI.
I also did an attempt to install tcpdump, but I’m not sure I did it at the right spot in the RPI.
Moreover, the HA doc (OpenWrt (ubus) - Home Assistant) tells me to start it “in another shell”… but I am not speaking linux, so I’m a bit lost.
Also, which directory and which port should I then put in the command?
sudo tcpdump -nnvXSs 0 -w /var/tmp/dt.out 'host <router_ip> and port 80'
Sorry, I have no idea how to do that on HA OS (supervised). You may find some hints in the forums here.
Maybe it is easier to install Wireshark on a local PC and MITM the connection or use a mirrored switch port or something like that.
Your logs look really awkward. The interface seems to immediately send an ACK to your requests - so does HA to the interfaces requests. So that would tell me this is not a networking thing.
But on the other hand - one layer up - the confirmations seem to take up to ~5 seconds.
Maybe just try to have ETS Busmonitor running (eg. from your USB interface) and see if the telegrams arrive on TP at the exact time they are sent from HA or just when the L_DATA_CON arrives at HA - you have some seconds so your systems clocks should suffice for that test. While you are at it, check the bus load.
Sorry that I can’t give you more solid suggestions, that is a really unique issue you are having there.
Another way to exclude some moving parts from the puzzle would be to run HA with only the KNX integration - or plain xknx if you know how to run python applications - on an other machine and see if it behaves the same.
… these are all things for which I have no clue where/how to begin. I’ve been reading quite a few things but either I’m rapidly lost, or I’m too afraid to do more harm than good to my LAN.
On the other hand, I’ve cabled the IP interface directly into the modem/router, and bypassed the switch.
I’ve also compared the ETS bus with the HA log. The only thing I did in the HA UI was pressing the button for lowering the living room sunscreen just once (GA 2/0/0).
Here is the HA log
2023-02-01 21:32:58.051 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.0.117:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="CONNECTIONSTATE_REQUEST" Reserve="0" TotalLength="16" /> body="<ConnectionStateRequest communication_channel_id="16", control_endpoint="192.168.0.187:47129/udp" />" />
2023-02-01 21:32:58.054 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.0.117:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="CONNECTIONSTATE_RESPONSE" Reserve="0" TotalLength="8" /> body="<ConnectionStateResponse communication_channel_id="16" status_code="ErrorCode.E_NO_ERROR" />" />
2023-02-01 21:32:58.201 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="15.15.241" destination_address="2/0/0" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />
2023-02-01 21:32:58.206 DEBUG (KNX Interface) [xknx.cemi] Outgoing CEMI: <CEMIFrame code="L_DATA_REQ" src_addr="IndividualAddress("15.15.241")" dst_addr="GroupAddress("2/0/0")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />
2023-02-01 21:32:58.207 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.0.117:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" Reserve="0" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="16" sequence_counter="35" cemi="1100bce0fff11000010081" />" />
2023-02-01 21:32:58.209 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.0.117:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" Reserve="0" TotalLength="10" /> body="<TunnellingAck communication_channel_id="16" sequence_counter="35" status_code="ErrorCode.E_NO_ERROR" />" />
2023-02-01 21:33:01.212 WARNING (MainThread) [xknx.log] L_DATA_CON Data Link Layer confirmation timed out for <TunnellingRequest communication_channel_id="16" sequence_counter="35" cemi="1100bce0fff11000010081" />
2023-02-01 21:33:09.316 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="15.15.241" destination_address="2/0/1" payload="<GroupValueWrite value="<DPTBinary value="True" />" />" />
2023-02-01 21:33:09.320 DEBUG (KNX Interface) [xknx.cemi] Outgoing CEMI: <CEMIFrame code="L_DATA_REQ" src_addr="IndividualAddress("15.15.241")" dst_addr="GroupAddress("2/0/1")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="True" />" />" />
2023-02-01 21:33:09.321 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.0.117:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" Reserve="0" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="16" sequence_counter="36" cemi="1100bce0fff11001010081" />" />
2023-02-01 21:33:10.324 DEBUG (KNX Interface) [xknx.log] Error: KNX bus did not respond in time (1.0 secs) to request of type 'Tunnelling'
2023-02-01 21:33:10.325 DEBUG (KNX Interface) [xknx.log] Did not receive a TUNNELLING_ACK within 1 second for frame with sequence_counter=36. Retrying a second time.
2023-02-01 21:33:10.326 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.0.117:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" Reserve="0" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="16" sequence_counter="36" cemi="1100bce0fff11001010081" />" />
2023-02-01 21:33:10.331 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.0.117:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" Reserve="0" TotalLength="10" /> body="<TunnellingAck communication_channel_id="16" sequence_counter="36" status_code="ErrorCode.E_NO_ERROR" />" />
2023-02-01 21:33:13.330 WARNING (MainThread) [xknx.log] L_DATA_CON Data Link Layer confirmation timed out for <TunnellingRequest communication_channel_id="16" sequence_counter="36" cemi="1100bce0fff11001010081" />
2023-02-01 21:33:15.158 DEBUG (KNX Interface) [xknx.knx] Received from 192.168.0.117:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_REQUEST" Reserve="0" TotalLength="21" /> body="<TunnellingRequest communication_channel_id="16" sequence_counter="10" cemi="2e009ce0fff11000010081" />" />
2023-02-01 21:33:15.158 DEBUG (KNX Interface) [xknx.knx] Sending to 192.168.0.117:3671: <KNXIPFrame <KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="TUNNELLING_ACK" Reserve="0" TotalLength="10" /> body="<TunnellingAck communication_channel_id="16" sequence_counter="10" status_code="ErrorCode.E_NO_ERROR" />" />
2023-02-01 21:33:15.160 DEBUG (KNX Interface) [xknx.cemi] Incoming CEMI: <CEMIFrame code="L_DATA_CON" src_addr="IndividualAddress("15.15.241")" dst_addr="GroupAddress("2/0/0")" flags="1001110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="1" />" />" />
2023-02-01 21:33:31.059 WARNING (MainThread) [pysaj] Connection to SAJ inverter is not possible. The inverter may be offline due to darkness. Otherwise check host/ip address.
And here is the KNX bus monitoring (sorry for the image format)
I don’t quite understand what this all means - e.g. why is the chronological order a little bit scrambled?
But anyway, there seems to be some 10 sec delay between HA and the KNX telegram, no?
sort that table by the first column # , not by Type
I think you have a basic bus problem there. There are a lot of repeated telegrams - while there should be basically none (Flags R) and I have never seen Type Immediate_* telegrams. LL_NACK also doesn’t sound that good.
There shouldn’t be any yellow (repeated) or green (not acked) telegrams in there.
Are these frames arriving also when you have HA shut down? If so, and I guess this is the case, you should find the source of that.
Might even be a closed ring in your bus or a malfunctioning device.
Also it can’t hurt to configure your tunnel endpoint address to someting like 1.1.x to be on the correct line (instead of 15.15.241).
But, the GOOD NEWS is that you were perfectly right that the cause was a <KNX bus/topology problem. And that it has now been identified, with the great help from Alexander Zokol at MDT Support, through a long Team Viewer session.
The origin of all the bus problems is that the power supply of 160mA was no longer sufficient after the addition of that last new device, i.e. the IP interface. Consequently, it would generate a lot of errors on the bus, etc…
To confirm this hypothesis, I installed a short test circuit with just the power supply and the IP interface and USB interface… and everything worked OK!
I then gradually connected an increasing number of KNX devices, and the problem reappeared with the last added device. I could to a certain extent mitigate the situation by cutting off two unused, “waiting” legs in the KNX cabling, and excluding a temp.CO2, humidity sensor positioned at the end of a 7m-long cable.
So, @farmio, a very big thank you for your wonderful and diligent help.
Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/0/33
Could not sync group address '3/0/33' (G225 Starlights Braai Stack Door - State)
Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/3/18
Could not sync group address '3/3/18' (G185 Downlight Boat - Brightness)
I have an MDT power supply 1280mA and the bus is below 600mA. See screenshot below:
XKNX Version 2.11.2
KNX-Frontend Version 2023.6.23.191712
Connected to bus Yes
Individual address 1.1.3
1.1.3 is a virtual address of the Gira X1 which is the device that links the KNX bus to IP/gateway/interface.
I am heading out now but when I am back I will do what you say - start ETS Diagnostics and reload KNX integration on the HA side. From what I can see in the logs it seems random…
You are mixing up error messages. Error: KNX bus did not respond in time is completely different from Can not process... Invalid payload length for DPTPower. Latter is a configuration issue - wrong GA (invalid DPT) for some config key.
I was out for a few hours and just refreshed the log without starting HA:
Logger: xknx.log
Source: runner.py:188
First occurred: 8:51:34 AM (113 occurrences)
Last logged: 12:51:58 PM
Could not sync group address '3/1/46' (G241 Kitchen Yard - Brightness)
Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/3/18
Could not sync group address '3/3/18' (G185 Downlight Boat - Brightness)
Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 2/1/33
Could not sync group address '2/1/33' (G180 BLOCK UFH Back Parents Bathroom - State)
Here are the detaild logs on the same GA as used before.
2023-12-27 08:51:45.337 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/1/46
2023-12-27 08:51:45.337 WARNING (MainThread) [xknx.log] Could not sync group address '3/1/46' (G241 Kitchen Yard - Brightness)
2023-12-27 09:51:47.340 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/1/46
2023-12-27 09:51:47.340 WARNING (MainThread) [xknx.log] Could not sync group address '3/1/46' (G241 Kitchen Yard - Brightness)
2023-12-27 10:51:49.342 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/1/46
2023-12-27 10:51:49.342 WARNING (MainThread) [xknx.log] Could not sync group address '3/1/46' (G241 Kitchen Yard - Brightness)
2023-12-27 11:51:51.344 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/1/46
2023-12-27 11:51:51.344 WARNING (MainThread) [xknx.log] Could not sync group address '3/1/46' (G241 Kitchen Yard - Brightness)
2023-12-27 12:51:53.758 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/1/46
2023-12-27 12:51:53.758 WARNING (MainThread) [xknx.log] Could not sync group address '3/1/46' (G241 Kitchen Yard - Brightness)
The power issue will investigate - looks like a mix up of length…sorry about that.
Here is a full log for the first few minutes after restart of HA filtered over xknx warnings:
2023-12-27 13:43:37.027 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/0/42
2023-12-27 13:43:37.027 WARNING (MainThread) [xknx.log] Could not sync group address '3/0/42' (G221 LED Bar Ceiling - Value)
2023-12-27 13:43:37.452 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/0/53
2023-12-27 13:43:37.452 WARNING (MainThread) [xknx.log] Could not sync group address '3/0/53' (G038 Braai Internal Lights - Value)
2023-12-27 13:43:39.258 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/0/13
2023-12-27 13:43:39.258 WARNING (MainThread) [xknx.log] Could not sync group address '3/0/13' (G041 Braai Wall Foot Light - Value)
2023-12-27 13:43:41.263 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/1/20
2023-12-27 13:43:41.263 WARNING (MainThread) [xknx.log] Could not sync group address '3/1/20' (G231 LED Kitchen Counter South - Value)
2023-12-27 13:43:41.364 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/1/55
2023-12-27 13:43:41.364 WARNING (MainThread) [xknx.log] Could not sync group address '3/1/55' (G281 LED Kitchen Counter East - Value)
2023-12-27 13:43:43.264 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/1/62
2023-12-27 13:43:43.264 WARNING (MainThread) [xknx.log] Could not sync group address '3/1/62' (G232 LED Pantry Counter - Value)
2023-12-27 13:43:46.343 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/0/33
2023-12-27 13:43:46.344 WARNING (MainThread) [xknx.log] Could not sync group address '3/0/33' (G225 Starlights Braai Stack Door - State)
2023-12-27 13:43:48.258 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/1/46
2023-12-27 13:43:48.258 WARNING (MainThread) [xknx.log] Could not sync group address '3/1/46' (G241 Kitchen Yard - Brightness)
2023-12-27 13:43:48.941 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/3/18
2023-12-27 13:43:48.941 WARNING (MainThread) [xknx.log] Could not sync group address '3/3/18' (G185 Downlight Boat - Brightness)
2023-12-27 13:43:53.051 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 2/1/33
2023-12-27 13:43:53.051 WARNING (MainThread) [xknx.log] Could not sync group address '2/1/33' (G180 BLOCK UFH Back Parents Bathroom - State)
And here the filtered diagnostics from ETS monitor:
I can only apologise - I have figured out those issues. They seemed random, but were not.
All of them were incorrect settings on my account - I unfortunately did all of the KNX integration by hand instead of exporting GA into Excel and making sure I had no typos.
Sorry about wasting your time, and thanks for pointing me in the right direction.
Anyone else ever having this issue where you can’t see the trees in front of the forest: Best is to test in diagnostics if the GA returns the response, do them one by one and then triple check the HA KNX integration. I simply had typos in there…
