Ikea Tradfri: Received Type.ACK from <aiocoap.transports.tinydtls.DTLSClientConnection

[Mariusthvdb]

The problem

this warning in the logs appear multiple times during startup.

What version of Home Assistant Core has the issue?

2022.1.0.dev20211215

What was the last working version of Home Assistant Core?

not sure

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ikea Tradfri

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tradfri/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2021-12-15 09:10:48 WARNING (MainThread) [coap] Received Type.ACK from <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f7c1c34f0>, but could not match it to a running exchange.
2021-12-15 09:10:48 WARNING (MainThread) [coap] Received Type.ACK from <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f7c1c34f0>, but could not match it to a running exchange.

Additional information

seems the latest Tradfri update of dec 13th made the Tradfri integration respond/behave better than before.
This warning is still quite obnoxious though. Not sure if it does any harm or not.

Not finding a match doesn't sound good ...

Ive mentioned this warning in other issues swell, but it might get buried, so a dedicated issue for the warning is justified.

[probot-home-assistant]

tradfri documentation
tradfri source
_{^{(message by IssueLinks)}}

[Ascariota]

Same issue

Keep-alive failed 09:07:58 – (ERREUR) IKEA TRÅDFRI - message survenu pour la première fois à 05:37:52 et apparu 152 fois. Received Type.ACK from <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7fe63d823220>, but could not match it to a running exchange. 06:32:51 – (ATTENTION) /usr/local/lib/python3.9/site-packages/aiocoap/messagemanager.py - message survenu pour la première fois à 00:02:16 et apparu 105 fois.

[Mariusthvdb]

and still happening in beta 2022.2.0b0, and dev dev20220127

shouldn't this have been mitigated by the new implementation of the #64166 ?

[ggravlingen]

@Mariusthvdb this experience this?

[Mariusthvdb]

Yes it's still there, on each startup:

[ggravlingen]

OK, still there. I've seen the error during testing when the gateway stops responding due to heavy traffic to i but I'm not sure it will be fixable here in Home Assistant.

[Mariusthvdb]

do you know what it means?

Maybe its a timing thing? we see many warnings in the startup log after all, and maybe its just too early in the process?

I did see a new update 21 feb in the Tradfri firmware regarding the Gateway and had hoped to to be related, but apparently not..

[Mariusthvdb]

Just as a FYI, I now noticed this during regular operation:

Logger: coap
Source: /usr/local/lib/python3.9/site-packages/aiocoap/messagemanager.py:217
First occurred: 09:11:57 (3 occurrences)
Last logged: 23:22:39

Received Type.ACK from <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7fa7c51160>, but could not match it to a running exchange.

so not only during startup...

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Mariusthvdb]

still happening, meanwhile on 2022.7.0.dev20220530

2022-05-30 09:21:18 WARNING (MainThread) [coap] Received Type.ACK from <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f661098e0>, but could not match it to a running exchange.
2

[dwd1]

Logger: coap
Source: /usr/local/lib/python3.10/site-packages/aiocoap/messagemanager.py:217
First occurred: 13:44:18 (1 occurrences)
Last logged: 13:44:18

Received Type.ACK from <aiocoap.transports.tinydtls.DTLSClientConnection object at 0x7f0e796a1cc0>, but could not match it to a running exchange.

[ekt-]

I systematically see the exact same message every time I restart hassio. gateway updated to version 1.19.26

[bbrendon]

@ekt- these started happening after upgrading coap past 0.3 . I had the same issue with my custom integration and I switched back to 0.3. I don't know enough about coap to the internals of the system to migrate to the newer versions.

[gmergulhao]

same issue with core-2022.7.6 on OS 8.2 on rpi3

[abdalians]

same issue with core-2022.7.6 on CentOS 7.9

[ddmmcz]

same issue.
always a temporary solution until the next Supervisor update. I add to variables in docker:
AIOCOAP_CLIENT_TRANSPORT tinydtls
AIOCOAP_SERVER_TRANSPORT tinydtls

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Mariusthvdb]

Trafdfri remains (or should say returned) throwing errors

there is a separate issue open for those frequent new issues:

#85254

[Mariusthvdb]

believe the actual issue on Received Type.ACK to not have appeared recently, so probably should close in favor of #85254

please @ggravlingen feel free to do so if you agree

[ggravlingen]

believe the actual issue on Received Type.ACK to not have appeared recently, so probably should close in favor of #85254

please @ggravlingen feel free to do so if you agree

I'm afraid I have no such permissions here. Isn't it possible for you to close it given that you opened the issue?

[Mariusthvdb]

sorry, forgot about that, closing as indeed this particular issues has not been spotted anymore. plenty of others though ....

#85254 is still very much alive, and remains a mystery. though I might be on to something (transitions in Tradfri)