core: Updater Dont Work
Home Assistant release with the issue: 0.81.1
Last working Home Assistant release (if known): 0.50
Operating environment (Hass.io/Docker/Windows/etc.): HassBian
Component/platform: https://www.home-assistant.io/components/updater
Description of problem: The updater component dont get updates.
If you try to make CURL with these parameters
curl -l -X POST -H "Content-Type: application/json" -d '{"test" : "123"}' https://updater.home-assistant.io/ -v
the output is
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 143.204.181.70...
* TCP_NODELAY set
* Connected to updater.home-assistant.io (143.204.181.70) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=home-assistant.io
* start date: Mar 31 00:00:00 2018 GMT
* expire date: Apr 30 12:00:00 2019 GMT
* subjectAltName: host "updater.home-assistant.io" matched cert's "*.home-assistant.io"
* issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x137de48)
> POST / HTTP/1.1
> Host: updater.home-assistant.io
> User-Agent: curl/7.52.1
> Accept: */*
> Content-Type: application/json
> Content-Length: 16
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
* We are completely uploaded and fine
< HTTP/2 200
< content-type: application/json
< content-length: 90
< date: Wed, 07 Nov 2018 14:15:58 GMT
< x-amzn-requestid: a5e5f412-e297-11e8-a9ae-bd40af2660b2
< x-amz-apigw-id: P_sAyE7EPHcFkbQ=
< x-amzn-trace-id: Root=1-5be2f39e-eb6910446bebc492685bc27c;Sampled=0
< x-cache: Miss from cloudfront
< via: 1.1 967425266468bd56bf14d0a928942c04.cloudfront.net (CloudFront)
< x-amz-cf-id: _6lVWQ1MLlyTesRcsVNuYMMRxATMsSolgk2L1mOurMOYOU8logaMyA==
<
* Curl_http_done: called premature == 0
* Connection #0 to host updater.home-assistant.io left intact
{"version":"0.81.6","release-notes":"https://www.home-assistant.io/latest-release-notes/"}l
Correct, I think.
If send curl with this parameters
curl -l -X POST -H "Content-Type: application/json" -d '{"huuid": "489a44ab96dc40cd8632bd64ad23d5f2", "hassio": False, "os_name": "Linux", "virtualenv": False, "python_version": "3.5.3", "timezone": "Europe/Lisbon", "arch": "armv7l", "dev": False, "os_version": "9", "version": "0.81.1", "docker": False, "distribution": "raspbian"}' https://updater.home-assistant.io/ -v
the output is
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 143.204.181.13...
* TCP_NODELAY set
* Connected to updater.home-assistant.io (143.204.181.13) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=home-assistant.io
* start date: Mar 31 00:00:00 2018 GMT
* expire date: Apr 30 12:00:00 2019 GMT
* subjectAltName: host "updater.home-assistant.io" matched cert's "*.home-assistant.io"
* issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x1fc5e48)
> POST / HTTP/1.1
> Host: updater.home-assistant.io
> User-Agent: curl/7.52.1
> Accept: */*
> Content-Type: application/json
> Content-Length: 276
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
* We are completely uploaded and fine
< HTTP/2 200
< content-type: application/json
< content-length: 4
< date: Wed, 07 Nov 2018 14:18:00 GMT
< x-amzn-requestid: ee80139b-e297-11e8-a9fa-85266ae6c5a4
< x-amz-apigw-id: P_sT0GhfPHcF-Mw=
< x-amzn-trace-id: Root=1-5be2f418-89b151206498b7e8726feb38;Sampled=0
< x-cache: Miss from cloudfront
< via: 1.1 089ee28df029aa2f4878a528c124aaf9.cloudfront.net (CloudFront)
< x-amz-cf-id: g1VK6XXc1pfyFi-5xdiZn5GVtMJW-KN4yM_vctB7fn1i_UgvtOItWg==
<
* Curl_http_done: called premature == 0
* Connection #0 to host updater.home-assistant.io left intact
nulll
Problem-relevant configuration.yaml
entries and (fill out even if it seems unimportant):
updater:
Traceback (if applicable):
2018-11-07 13:54:44 INFO (MainThread) [homeassistant.components.updater] Submitted analytics to Home Assistant servers. Information submitted includes {'huuid': '489a44ab96dc40cd8632bd64ad23d5f2', 'hassio': False, 'os_name': 'Linux', 'virtualenv': False, 'python_version': '3.5.3', 'timezone': 'Europe/Lisbon', 'arch': 'armv7l', 'dev': False, 'os_version': '9', 'version': '0.81.1', 'docker': False, 'distribution': 'raspbian'}
2018-11-07 13:54:44 ERROR (MainThread) [homeassistant.components.updater] Got unexpected response: None
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 38 (12 by maintainers)
Can we reopen this ticket? I’m on 0.91.2 and it’s still not working. My config is as follows:
Same error in version 0.85.1 using python.
I’ve opened a PR; not 100% clear I know why it broke, but as I can confirm that the huuid -> uid change causes notifications to show up, maybe someone from core will be able to confirm what the root cause was.
Problem is still present in 0.94.1 when
reporting = false
.I changed the component to submit a dummy JSON (by just adding
info_object['reporting'] = 'false'
after creating the emptyinfo_object = {}
) and it started working properly.From the command line, test the difference using:
curl -l -X POST -H "Content-Type: application/json" -d '{}' https://updater.home-assistant.io/
, this returnsnull
.When submitting “something”:
curl -l -X POST -H "Content-Type: application/json" -d '{"reporting" : "false"}' https://updater.home-assistant.io/
, the return is{"version":"0.94.1","release-notes":"https://www.home-assistant.io/latest-release-notes/"}
as intended.it does not work in 0.90 either:(
Yesterday I got same error on Hassbian 0.87.0 2019-02-09 19:52:27 INFO (MainThread) [homeassistant.components.updater] Submitted analytics to Home Assistant servers. Information submitted includes {} 2019-02-09 19:52:27 ERROR (MainThread) [homeassistant.components.updater] Got unexpected response: None
I have set in configuration.yaml: