Running hassio on an rPi 3B (non-plus). Not quite sure where I started, but was running on 0.90.1 for the last couple days just fine, and due to streaming problems tried updating to 0.90.2.
I gave it about an hour, and it was offline (no pings even), then power cycled.
It came back up as 0.90.1, with no apparent issues. I am unclear what to check (I frankly do not really understand the os/vm structure of the hassio mechanism).
The /config/home_assistant.log is only this current boot and normal.
The hass.io page system log is weird, it shows a starting time stamp of 18-06-22 which I gather is June 22, 2018? Probably due to no RTC on the Pi. Only error shown in it though relates, it shows:
18-06-22 11:12:20 INFO (SyncWorker_2) [hassio.docker.interface] Attach to image hassioaddons/node-red-armv7 with version v2.0.2
18-06-22 11:12:20 INFO (SyncWorker_5) [hassio.docker.interface] Attach to image homeassistant/armv7-addon-ssh with version 5.2
18-06-22 11:12:20 INFO (SyncWorker_7) [hassio.docker.interface] Attach to image homeassistant/armv7-addon-configurator with version 2.1
18-06-22 11:12:20 INFO (MainThread) [hassio.updater] Fetch update data from https://s3.amazonaws.com/hassio-version/stable.json
18-06-22 11:12:21 ERROR (MainThread) [asyncio] SSL handshake failed on verifying the certificate protocol: <uvloop.loop.SSLProtocol object at 0x74691a50>
transport: <TCPTransport closed=False reading=False 0x7517f7f0>;
Traceback (most recent call last): File "uvloop/sslproto.pyx", line 609, in
uvloop.loop.SSLProtocol._on_handshake_complete File "uvloop/sslproto.pyx", line 171, in
uvloop.loop._SSLPipe.feed_ssldata File "/usr/local/lib/python3.7/ssl.py", line 763, in
do_handshake self.
_sslobj.do_handshake() ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED]
certificate verify failed: certificate is not yet valid (_ssl.c:1056)
18-06-22 11:12:21 ERROR (MainThread) [asyncio] SSL error errno:1 reason:
CERTIFICATE_VERIFY_FAILED protocol: <uvloop.loop.SSLProtocol object at 0x74691a50>
transport: <TCPTransport closed=False reading=False 0x7517f7f0>
Traceback (most recent call last): File "uvloop/sslproto.pyx", line 504, in
uvloop.loop.SSLProtocol.data_received File "uvloop/sslproto.pyx", line 204, in
uvloop.loop._SSLPipe.feed_ssldata File "uvloop/sslproto.pyx", line 171, in
uvloop.loop._SSLPipe.feed_ssldata File "/usr/local/lib/python3.7/ssl.py", line 763, in
do_handshake self._sslobj.
do_handshake() ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED]
certificate verify failed: certificate is not yet valid (_ssl.c:1056)
18-06-22 11:12:21 WARNING (MainThread) [hassio.updater] Can't fetch versions from
https://s3.amazonaws.com/hassio-version/stable.json:
Cannot connect to host s3.amazonaws.com:443 ssl:True
[SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1056)')]
18-06-22 11:12:21 INFO (MainThread) [hassio.snapshots] Found 2 snapshot files
18-06-22 11:12:21 INFO (MainThread) [hassio.discovery] Load 0 messages
18-06-22 11:12:21 INFO (MainThread) [__main__] Run Hass.io`
I’m not sure if this matters or is just an aspect of the clock not being set (yet?). If I ssh into it (or into some container on it, I’m unclear) the clock is right, and I am using a local ntp server readily available.
There is no monitor on the rPi and none readily accessible from it. I could probably arrange something if that is necessary.
Are there any logs to check (or do the above log errors help)?
Note I am on Hass.io supervisor version 150 and HassOS version 2.11.
Thanks,
Linwood
PS. I added line breaks probably at bad places in the above trying to make it readable, sorry for any mis-formats, it did not cut/paste well.