Unable to update to 0.88.0

Configuration
1

I’m not able to update to 0.88.0. Upon clicking UPDATE I get the swirling cursor then the UPDATE button turns red for a second then no more swirling cursor. At this point HA UI works as normal.
I’ve tried rebooting and powering the pi down (which take the same amount of time as it always has).
Under Hass.io I still see the Update available! menu. See the latest home-assistant.log file.

2019-02-20 20:39:22 ERROR (SyncWorker_6) [homeassistant.components.wemo] Unable to get description url for WeMo at: 192.168.1.113
2019-02-20 20:39:31 ERROR (SyncWorker_6) [homeassistant.components.wemo] Unable to get description url for WeMo at: 192.168.1.211
2019-02-20 20:39:34 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-20 20:39:34 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Unable to retrieve HUB id
2019-02-20 20:39:34 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-20 20:39:34 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 30 seconds.
2019-02-20 20:40:05 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-20 20:40:05 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Unable to retrieve HUB id
2019-02-20 20:40:05 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-20 20:40:05 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 60 seconds.
2019-02-20 20:40:05 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2019-02-20 20:40:05 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2019-02-20 20:41:06 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-20 20:41:06 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Unable to retrieve HUB id
2019-02-20 20:41:06 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-20 20:41:06 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 90 seconds.
2019-02-20 20:41:06 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2019-02-20 20:41:06 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2019-02-20 20:42:37 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-20 20:42:37 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Unable to retrieve HUB id
2019-02-20 20:42:37 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-20 20:42:37 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 120 seconds.
2019-02-20 20:42:37 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2019-02-20 20:42:37 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2019-02-20 20:43:31 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2019-02-20 20:44:38 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-20 20:44:38 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Unable to retrieve HUB id
2019-02-20 20:44:38 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-20 20:44:38 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 150 seconds.
2019-02-20 20:44:38 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2019-02-20 20:44:38 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2019-02-20 20:47:09 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-20 20:47:09 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Unable to retrieve HUB id
2019-02-20 20:47:09 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-20 20:47:09 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 180 seconds.
2019-02-20 20:47:09 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2019-02-20 20:47:09 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2019-02-20 20:50:10 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-20 20:50:10 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Unable to retrieve HUB id
2019-02-20 20:50:10 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-20 20:50:10 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 180 seconds.
2019-02-20 20:50:10 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2019-02-20 20:50:10 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2019-02-20 20:53:11 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-20 20:53:11 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Unable to retrieve HUB id
2019-02-20 20:53:11 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-20 20:53:11 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 180 seconds.
2019-02-20 20:53:12 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2019-02-20 20:55:38 WARNING (MainThread) [homeassistant.components.http.auth] You need to use a bearer token to access /api/ios/identify from 192.168.1.1
2019-02-20 20:55:38 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.1.1
2019-02-20 20:56:12 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Exception on post: 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-02-20 20:56:12 ERROR (MainThread) [aioharmony.hubconnector] 192.168.1.237: Unable to retrieve HUB id
2019-02-20 20:56:12 WARNING (MainThread) [homeassistant.components.remote.harmony] Harmony Hub: Unable to connect to HUB.
2019-02-20 20:56:12 WARNING (MainThread) [homeassistant.components.remote] Platform harmony not ready yet. Retrying in 180 seconds.
2019-02-20 20:56:12 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2019-02-20 20:56:12 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2

This is part of my system log file under hass.io

19-02-21 15:03:04 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.88.0 19-02-21 15:03:04 INFO (SyncWorker_7) [hassio.docker.interface] Update Docker homeassistant/raspberrypi3-homeassistant:0.87.1 to homeassistant/raspberrypi3-homeassistant:0.88.0 19-02-21 15:03:04 INFO (SyncWorker_7) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.88.0.
19-02-21 15:03:05 ERROR (SyncWorker_7) [hassio.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.88.0 -> 500 Server Error: Internal Server Error (“readlink /mnt/data/docker/overlay2/l: invalid argument”).
19-02-21 15:03:05 WARNING (MainThread) [hassio.homeassistant] Home Assistant is already running! 19-02-21 15:03:05 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.88.0
19-02-21 15:05:43 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/services access from core_configurator 19-02-21 15:05:44 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/events access from core_configurator
19-02-21 15:05:44 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from core_configurator 19-02-21 15:11:14 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.88.0 19-02-21 15:11:14 INFO (SyncWorker_5) [hassio.docker.interface] Update Docker homeassistant/raspberrypi3-homeassistant:0.87.1 to homeassistant/raspberrypi3-homeassistant:0.88.0 19-02-21 15:11:14 INFO (SyncWorker_5) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.88.0.
19-02-21 15:11:15 ERROR (SyncWorker_5) [hassio.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.88.0 -> 500 Server Error: Internal Server Error (“readlink /mnt/data/docker/overlay2/l: invalid argument”).
19-02-21 15:11:15 WARNING (MainThread) [hassio.homeassistant] Home Assistant is already running! 19-02-21 15:11:15 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.88.0
19-02-21 15:14:32 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-02-21 15:17:13 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/services access from core_configurator
19-02-21 15:17:14 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/events access from core_configurator
19-02-21 15:17:14 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from core_configurator
19-02-21 15:18:26 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/services access from core_configurator`

3

Issue #21249 has been opened

4

Hello Domenic,

After restarting the Pi 3 HA is not launching nor can I access the configuration files using Window’s Explorer. Any suggestions on how to recover? Thx Keith

5

I had this happen to me once before and after much knashing of teeth and pulling of hair, I copied my entire config folder, along with it’s sub-folders, to another puter, scratched the SD card and started with a fresh install… then moved my cofig folders back.
Yep, I gave up and started anew. It was a pain but less painful that tracking down the bug that originated my frustrations.

6

Thx Dixey, I too as well have had to do this a couple of times in the past and it is a real pain.
I’m hoping there is a less painful way before I go down this path again:-(

7

Plugging a monitor into the pi I’m getting these messages (last two lines)… They alternate every other pause.

device (vethb80c18b) left promiscuous mode
hassio: port 1(vethb80c18b) entered disabled state

hassio: port 1(vethc4b509e) entered blocking state
hassio: port 1(vethc4b509e) entered forwarding state

8

Ssh to your system and then: homeassistant update --options version=0.87.1

It will restore your hassio to the previous version then you should wait for a while and try to update to 0.88.1 or 0.88.2 if released.

9

Can I do this even though I never set the component up in HA?
Thanks for your help… Keith

10

Updated from 0.87 to 0.88.0 I’m lost… My Pi3 won’t load the frontend. I have tried to restore last version as shown, no go:

core-ssh:~# homeassistant update --options version=0.87.1
-bash: homeassistant: command not found
core-ssh:~#
1 Like
11

it something to do with remote:

I get the same thing…

image

1 Like
12

jeah basically i could try anthing and all i got was only a white page with a blue header… if I looked at it with an editors diagnostic in my browser, it hadd still all the objects in the code… so I cleared browser cash and after that it was totally gone, and now I am not even getting anything after another restart… well I guess its back to scratch then

weird tho that i got no isses with the configurator, it still can acess local or by duckdns domain… but the HA I cant reach, not local, not my duckdns and also not by IP

13

I’m getting lots of errors.

019-02-22 08:20:52 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: SSLV3_ALERT_BAD_CERTIFICATE
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.SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate (_ssl.c:1056)
2019-02-22 08:23:21 ERROR (MainThread) [homeassistant.components.hassio] INFO:homeassistant.util.package:Attempting install of colorlog==4.0.2
Testing configuration at /config
WARNING:homeassistant.helpers.config_validation:Your configuration contains extra keys that the platform does not support.
Please remove [command_topic]. 
Please remove [command_topic]. 
Please remove [command_topic]. 
Please remove [command_topic]. 
Failed config
  General Errors: 
    - Component not found: resources
Successful config (partial)
Connected
14

I was getting ssl errors, but I got the frontend to load locally after commenting out the ssl rules in my config.yaml (shown below # ssl…) Then removed “S” from https://myLocalHass:8123/lovelace/default_view

It’s the weekend, so I will prolly be up til 3AM again learning how to fix the last update :wink:

http:
  api_password: !secret http_password
  ip_ban_enabled: true
  login_attempts_threshold: 10
  base_url: !secret duckdns_url
#  ssl_certificate: /ssl/fullchain.pem
#  ssl_key: /ssl/privkey.pem
  cors_allowed_origins:
    - https://google.com
    - https://www.home-assistant.io
  use_x_forwarded_for: true   
  trusted_proxies:
    - 127.0.0.1
    - ::1
  trusted_networks:  
    - 127.0.0.1
    - ::1
    - 192.168.1.0/24
    - fd00::/8
15

Well! I’m still down… I have a TV connected to the pi HDMI port and got the scrolling to stop and now have a Hassos> prompt. Any suggestions??

16

try this:

hassio ha update --options version="0.87.1"

17

Thanks but I get an Unknown command ‘hassio’
I’m at HassOS> not hassio.

18

Well!! I had no choice but to start from scratch and re-image the micro SD card.
I’m slowly adding to the configuration.yaml file to make sure everything is happy:-)
I still have to reboot many times to get all four Wemo devices discovered. I am using static ip address.
Is anyone else seeing this same issue?