core icon indicating copy to clipboard operation
core copied to clipboard
Published 1 week ago • verified publisher icon home-assistant

Error of Timeout sending analytics

Open DChe47 opened this issue 7 months ago • 1 comments

The problem

After the last update to version Core 2025.4.4, Supervisor 2025.04.11, I see an error every day: "Timeout sending analytics to https://analytics-api.home-assistant.io/v1".

What version of Home Assistant Core has the issue?

core-2025.4.4

What was the last working version of Home Assistant Core?

core-2025.4.3

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

home-assistant_2025-05-12T18-36-27.456Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

DChe47 avatar May 12 '25 18:05 DChe47

Hey there @home-assistant/core, @ludeeus, mind taking a look at this issue as it has been labeled with an integration (analytics) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of analytics can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign analytics Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

analytics documentation analytics source (message by IssueLinks)

home-assistant[bot] avatar May 12 '25 18:05 home-assistant[bot]

Can you access that site (it should give you a 405 error)? Some DNS block list (like the ones that you can add to things like pi-hole and adguard) are blocking these, are you using that?

ludeeus avatar May 13 '25 08:05 ludeeus

Hi, Yes, I have access to site https://www.home-assistant.io/ https://www.home-assistant.io/. This may sometimes be disrupted for a short time if my ISP configures something ( DNS ). How often are statistics uploaded? Is it logged somewhere? Best regards, Dima 13.05.2025, 11:17, home-assistant/core < @.*** @.*** > ludeeus left a comment https://github.com/home-assistant/core/issues/144762#issuecomment-2875495039 (home-assistant/core#144762) Can you access that site (it should give you a 405 error)? Some DNS block list (like the ones that you can add to things like pi-hole and adguard) are blocking these, are you using that? — Reply to this email directly, https://github.com/home-assistant/core/issues/144762#issuecomment-2875495039 view it on GitHub, or https://github.com/notifications/unsubscribe-auth/AZ3QJBZROTAQ4CDYGGXN3H326GTCPAVCNFSM6AAAAAB46UJ5KCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZVGQ4TKMBTHE unsubscribe. You are receiving this because you authored the thread. Message ID: <home-assistant/core/issues/144762/2875495039 @ github. com>

DChe47 avatar May 13 '25 08:05 DChe47

I am not asking about the documentation, but the URL you posted. It is updated every 24h after startup.

ludeeus avatar May 13 '25 08:05 ludeeus

You're right, the page https://analytics-api.home-assistant.io/v1 https://analytics-api.home-assistant.io/v1 gives a 405 error. Has this been changed in the latest update? Or is it a coincidence with my DNS being blocked? Do I need to disable statistics to eliminate this error? Regards, Dima 13.05.2025, 11:49, home-assistant/core < @.*** @.*** > ludeeus left a comment https://github.com/home-assistant/core/issues/144762#issuecomment-2875592505 (home-assistant/core#144762) I am not asking about the documentation, but the URL you posted. It is updated every 24h after startup. — Reply to this email directly, https://github.com/home-assistant/core/issues/144762#issuecomment-2875592505 view it on GitHub, or https://github.com/notifications/unsubscribe-auth/AZ3QJBZIMKKD7OMOAJQ7BML26GWYPAVCNFSM6AAAAAB46UJ5KCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZVGU4TENJQGU unsubscribe. You are receiving this because you authored the thread. Message ID: <home-assistant/core/issues/144762/2875592505 @ github. com>

DChe47 avatar May 13 '25 09:05 DChe47

405 means it is not blocked (at least not on the device you tried that), this service has not changed since it was created 4 years ago, so something changed on your setup.

ludeeus avatar May 13 '25 09:05 ludeeus

Thanks for your help, I'll check my router again. Which ports are used by this service? 13.05.2025, 12:36, home-assistant/core < @.*** @.*** > ludeeus left a comment https://github.com/home-assistant/core/issues/144762#issuecomment-2875756195 (home-assistant/core#144762) 405 means it is not blocked (at least not on the device you tried that), this service has not changed since it was created 4 years ago, so something changed on your setup. — Reply to this email directly, https://github.com/home-assistant/core/issues/144762#issuecomment-2875756195 view it on GitHub, or https://github.com/notifications/unsubscribe-auth/AZ3QJB5JSVMU44OPCKJWG2326G4IZAVCNFSM6AAAAAB46UJ5KCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZVG42TMMJZGU unsubscribe. You are receiving this because you authored the thread. Message ID: <home-assistant/core/issues/144762/2875756195 @ github. com>

DChe47 avatar May 13 '25 09:05 DChe47

443 (default HTTPS port)

ludeeus avatar May 13 '25 09:05 ludeeus

Just to make it clear @ludeeus : 405 is the expected/ok HTTP code, when accessing the service directly, right?

abmantis avatar May 13 '25 13:05 abmantis

Yes.

ludeeus avatar May 13 '25 13:05 ludeeus

Hi, I think so. Everything was working until the last update and there was no such error. I haven't changed anything in the Home Assistant analytics settings. It's possible that something has changed with access to the external network ( my router or the provider's equipment ). Unfortunately, I'm far away from the device now and I can't check. 13.05.2025, 16:33, home-assistant/core < @.*** @.*** > abmantis left a comment https://github.com/home-assistant/core/issues/144762#issuecomment-2876546522 (home-assistant/core#144762) Just to make it clear https://github.com/ludeeus @ludeeus: 405 is the expected/ok HTTP code, when accessing the service directly, right? — Reply to this email directly, https://github.com/home-assistant/core/issues/144762#issuecomment-2876546522 view it on GitHub, or https://github.com/notifications/unsubscribe-auth/AZ3QJB5V2VEGMB5EWFKH5I326HYBJAVCNFSM6AAAAAB46UJ5KCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZWGU2DMNJSGI unsubscribe. You are receiving this because you authored the thread. Message ID: <home-assistant/core/issues/144762/2876546522 @ github. com>

DChe47 avatar May 13 '25 13:05 DChe47

I have now checked the connection to https://analytics-api.home-assistant.io/v1 directly from the Home Assistant server and I see a 405 error. I understand that there is a connection with the analytics page. The error is repeated once a day. Apparently, analytics are not being sent. What else can I check?

DChe47 avatar May 16 '25 17:05 DChe47

Try disabling all custom integrations if you have any, they might interfere.

ludeeus avatar May 19 '25 07:05 ludeeus

Try disabling all custom integrations if you have any, they might interfere.

Which integrations can affect? I only use mqtt2zigbee (two), Mosquito and ESPHome.

DChe47 avatar May 19 '25 08:05 DChe47

Those are add-ons, not custom integrations.

ludeeus avatar May 19 '25 08:05 ludeeus

What do you call custom integrations? Automations? I have many different ones, but it ensure the work of HA. I can't turn it all off.

DChe47 avatar May 19 '25 09:05 DChe47

I have disabled analytics. I have not found another way to eliminate this error. But I've never had such these errors before. I will periodically turn on analytics and monitor this error.

DChe47 avatar Jun 01 '25 13:06 DChe47

same problem to me aftet last 2025.7.2 update:

2025-07-19 19:32:14.491 ERROR (MainThread) [homeassistant.components.analytics] Error sending analytics to https://analytics-api.home-assistant.io/v1: ClientConnectorDNSError(ConnectionKey(host='analytics-api.home-assistant.io', port=443, is_ssl=True, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(None, 'Timeout while contacting DNS servers'))

No all the days, only a few days a week. My dns are working fine, and also can see process in my dns that its executed in 14 ms, as a everyday.

aperezva avatar Jul 20 '25 05:07 aperezva

more info

  • Host analytics-api.home-assistant.io:443 was resolved.
  • IPv6:xxxxxxxxx
  • IPv4: xxxxxxxxxxxxx
  • Trying [2606:4700:20::681a:4ee]:443...
  • Immediate connect fail for 2606:4700:20::681a:4ee: Network unreachable
  • Trying [2606:4700:20::681a:5ee]:443...
  • Immediate connect fail for 2606:4700:20::681a:5ee: Network unreachable
  • Trying [2606:4700:20::ac43:445a]:443...
  • Immediate connect fail for 2606:4700:20::ac43:445a: Network unreachable
  • Trying 104.26.4.238:443...
  • ALPN: curl offers h2,http/1.1
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • CAfile: /etc/ssl/cert.pem
  • CApath: /etc/ssl/certs
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
  • TLSv1.3 (IN), TLS handshake, Finished (20):
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
  • SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=home-assistant.io
  • start date: Jun 2 08:04:20 2025 GMT
  • expire date: Aug 31 09:04:18 2025 GMT
  • subjectAltName: host "analytics-api.home-assistant.io" matched cert's "*.home-assistant.io"
  • issuer: C=US; O=Google Trust Services; CN=WE1
  • SSL certificate verify ok.
  • Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256
  • Certificate level 1: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA384
  • Certificate level 2: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384
  • Connected to analytics-api.home-assistant.io (104.26.4.238) port 443
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://analytics-api.home-assistant.io/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: analytics-api.home-assistant.io]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.14.1]
  • [HTTP/2] [1] [accept: /]

GET / HTTP/2 Host: analytics-api.home-assistant.io User-Agent: curl/8.14.1 Accept: /

  • Request completely sent off
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): < HTTP/2 522 < date: Sun, 20 Jul 2025 05:09:56 GMT < content-type: text/plain; charset=UTF-8 < content-length: 15 < report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=bpf8QzFYyoaWfLrYmAU5%2FBsHmEH653uB93lZQQv2fu0AFL%2FnLHww%2F0TAlpTdQIrsgGhj7fDCcOUb6w35iLfwhJoNQAN9%2FAzBQS7OBVgS53tPgdcZInboL5YhagA4nlwqWIiZYFVPd0YoH0RsTomKDao%3D"}],"group":"cf-nel","max_age":604800} < nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} < x-frame-options: SAMEORIGIN < referrer-policy: same-origin < cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 < expires: Thu, 01 Jan 1970 00:00:01 GMT < server: cloudflare < cf-ray: 961ff3032e940359-MAD < alt-svc: h3=":443"; ma=86400 < server-timing: cfL4;desc="?proto=TCP&rtt=11054&min_rtt=10987&rtt_var=2447&sent=6&recv=9&lost=0&retrans=0&sent_bytes=4509&recv_bytes=1829&delivery_rate=392121&cwnd=253&unsent_bytes=0&cid=6fc355f3fc7edf19&ts=63&x=0" <
  • Connection #0 to host analytics-api.home-assistant.io left intact error code: 522#

aperezva avatar Jul 20 '25 05:07 aperezva

it´s seems analytics has a problem with cloudflare

after update to 2025.07.2, this error appears twice per week,

2025-07-19 19:32:14.491 ERROR (MainThread) [homeassistant.components.analytics] Error sending analytics to https://analytics-api.home-assistant.io/v1: ClientConnectorDNSError(ConnectionKey(host='analytics-api.home-assistant.io', port=443, is_ssl=True, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(None, 'Timeout while contacting DNS servers'))

Example YAML snippet

Anything in the logs that might be useful for us?

2025-07-19 19:32:14.491 ERROR (MainThread) [homeassistant.components.analytics] Error sending analytics to https://analytics-api.home-assistant.io/v1: ClientConnectorDNSError(ConnectionKey(host='analytics-api.home-assistant.io', port=443, is_ssl=True, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(None, 'Timeout while contacting DNS servers'))

Additional information

if I connect with curl -v https://analytics-api.home-assistant.io

  • Host analytics-api.home-assistant.io:443 was resolved.
  • IPv6: xxxxxxx
  • IPv4: xxxxxxxxx
  • Trying [2606:4700:20::681a:4ee]:443...
  • Immediate connect fail for 2606:4700:20::681a:4ee: Network unreachable
  • Trying [2606:4700:20::681a:5ee]:443...
  • Immediate connect fail for 2606:4700:20::681a:5ee: Network unreachable
  • Trying [2606:4700:20::ac43:445a]:443...
  • Immediate connect fail for 2606:4700:20::ac43:445a: Network unreachable
  • Trying 104.26.4.238:443...
  • ALPN: curl offers h2,http/1.1
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • CAfile: /etc/ssl/cert.pem
  • CApath: /etc/ssl/certs
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
  • TLSv1.3 (IN), TLS handshake, Finished (20):
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
  • SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=home-assistant.io
  • start date: Jun 2 08:04:20 2025 GMT
  • expire date: Aug 31 09:04:18 2025 GMT
  • subjectAltName: host "analytics-api.home-assistant.io" matched cert's "*.home-assistant.io"
  • issuer: C=US; O=Google Trust Services; CN=WE1
  • SSL certificate verify ok.
  • Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256
  • Certificate level 1: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA384
  • Certificate level 2: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384
  • Connected to analytics-api.home-assistant.io (104.26.4.238) port 443
  • using HTTP/2
  • [HTTP/2] [1] OPENED stream for https://analytics-api.home-assistant.io/
  • [HTTP/2] [1] [:method: GET]
  • [HTTP/2] [1] [:scheme: https]
  • [HTTP/2] [1] [:authority: analytics-api.home-assistant.io]
  • [HTTP/2] [1] [:path: /]
  • [HTTP/2] [1] [user-agent: curl/8.14.1]
  • [HTTP/2] [1] [accept: /]

GET / HTTP/2 Host: analytics-api.home-assistant.io User-Agent: curl/8.14.1 Accept: /

  • Request completely sent off
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): < HTTP/2 522 < date: Sun, 20 Jul 2025 05:19:41 GMT < content-type: text/plain; charset=UTF-8 < content-length: 15 < report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=3rYjjhVwo1ZmcVRe8FMONdnIZxg0XVOAi6BFAe2sqF2m4XyKeYq6no4F2vBPRsCoKf%2FrvrUtIh0AD4Rt8rrMrtbFyXyVo13%2BN%2BnCZFUpmVIds%2BrBeYnfYeyVMrJPNY90%2FBmnSAUoCmqpRhYhqqawPRQ%3D"}],"group":"cf-nel","max_age":604800} < nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} < x-frame-options: SAMEORIGIN < referrer-policy: same-origin < cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 < expires: Thu, 01 Jan 1970 00:00:01 GMT < server: cloudflare < cf-ray: 9620014efa92c6df-MAD < alt-svc: h3=":443"; ma=86400 < server-timing: cfL4;desc="?proto=TCP&rtt=11073&min_rtt=10999&rtt_var=2432&sent=7&recv=9&lost=0&retrans=0&sent_bytes=4511&recv_bytes=1829&delivery_rate=384889&cwnd=253&unsent_bytes=0&cid=813a307677cc2f66&ts=59&x=0" <
  • Connection #0 to host analytics-api.home-assistant.io left intact error code: 522#

aperezva avatar Jul 20 '25 05:07 aperezva

405 means it is not blocked (at least not on the device you tried that), this service has not changed since it was created 4 years ago, so something changed on your setup.

I have the same problem since one week ago. No changes, no blocks. I can see in my Adguard DNS thare are two connection , in the morning and in the afternoon, in the morning , everything works fine, or at least Idon´t have errors, in the afternoon, in the last week three errors. @ludeeus please could you check it?. In other case, iw will disabled too.

aperezva avatar Jul 20 '25 18:07 aperezva

I've had the same issue and it did turn out to be my pihole. Turns out the domain name was in hagezi's DNS-blocklists: https://raw.githubusercontent.com/hagezi/dns-blocklists/main/adblock/pro.txt matching entries: - ||analytics.home-assistant.io^ - ||analytics-api.home-assistant.io^

I whitelisted the domain-name now.

Pastaloverzzz avatar Nov 16 '25 22:11 Pastaloverzzz