Hassio 0.81.1 dead

Installation Home Assistant OS
1

Tried to update hassio to 0.81.1 but keep getting “IndexError: list index out of range”.

How do I get back to a working version via the command line. Still have access to my pi but can’t reboot via hassio ho reboot.

Thanks

82018-10-30 11:08:35 WARNING (MainThread) [homeassistant.components.http] legacy_api_password support has been enabled. If you don’t require it, remove the ‘api_password’ from your http config.
2018-10-30 11:08:35 DEBUG (MainThread) [homeassistant.components.mqtt] Transmitting message on tele/hass1/LWT: Online
2018-10-30 11:08:39 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=3 from 2018-10-30 17:56:16.377445)
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to checkin/nodeRED
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to wallpanel/mywallpanel/sensor/battery
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to home/alarm/set
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Transmitting message on home/alarm: disarmed
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on home/alarm/set: b’DISARM’
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to sensor/garage/state1
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to stat/sonoff4ch/POWER1
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to stat/sonoff4ch/POWER2
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to stat/sonoff4ch/POWER3
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to stat/sonoff4ch/POWER4
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to stat/sonoff1/POWER
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to stat/sonoff2/POWER
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to stat/sonoff3/POWER
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to stat/sonoffsinklights/POWER
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to stat/budslamp/POWER
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on stat/sonoff4ch/POWER1: b’OFF’
2018-10-30 11:08:44 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on stat/sonoff4ch/POWER2: b’OFF’
2018-10-30 11:08:45 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on stat/sonoff4ch/POWER3: b’OFF’
2018-10-30 11:08:45 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on stat/sonoff4ch/POWER4: b’OFF’
2018-10-30 11:08:45 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on stat/sonoff1/POWER: b’OFF’
2018-10-30 11:08:45 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on stat/sonoff2/POWER: b’OFF’
2018-10-30 11:08:45 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on stat/sonoff3/POWER: b’OFF’
2018-10-30 11:08:45 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on stat/sonoffsinklights/POWER: b’ON’
2018-10-30 11:08:45 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on stat/budslamp/POWER: b’ON’
2018-10-30 11:08:47 WARNING (SyncWorker_13) [pysonos.discovery] Can’t make a discovery socket for 104.239.207.44: OSError: [Errno 99] Address not available
2018-10-30 11:08:47 WARNING (SyncWorker_13) [pysonos.discovery] Can’t make a discovery socket for 198.105.254.130: OSError: [Errno 99] Address not available
2018-10-30 11:08:54 WARNING (MainThread) [homeassistant.setup] Setup of amcrest is taking over 10 seconds.
2018-10-30 11:09:47 ERROR (MainThread) [homeassistant.components.sensor] amcrest: Error on device update!
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 251, in _async_add_entity
await entity.async_device_update(warning=False)
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py”, line 349, in async_device_update
await self.hass.async_add_executor_job(self.update)
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/sensor/amcrest.py”, line 103, in update
sd_used = self._camera.storage_used
File “/usr/local/lib/python3.6/site-packages/amcrest/storage.py”, line 39, in storage_used
status = [s for s in ret.split() if ‘.UsedBytes=’ in s][0]
IndexError: list index out of range
2018-10-30 11:09:55 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform amcrest is taking over 10 seconds.
2018-10-30 11:10:59 ERROR (MainThread) [homeassistant.components.sensor] amcrest: Error on device update!
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 251, in _async_add_entity
await entity.async_device_update(warning=False)
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py”, line 349, in async_device_update
await self.hass.async_add_executor_job(self.update)
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/sensor/amcrest.py”, line 103, in update
sd_used = self._camera.storage_used
File “/usr/local/lib/python3.6/site-packages/amcrest/storage.py”, line 39, in storage_used
status = [s for s in ret.split() if ‘.UsedBytes=’ in s][0]
IndexError: list index out of range

2

Can’t you disable in HA the device giving you grief (Amcrest), then HA should boot/finish update normaly. Then roll back through hassio snapshot?

3

can’t get ha to even come up. It bombs on the error and never gets going. I thought I should be able to roll back a level via command line using homeassistant update --options version=0.80.0 but all I get is ok then nothing.

4

If you have ssh access, or access to samba share, comment out section in .yaml file where you have declared that device. Then reboot and try again. If you lucky HA will come up with some errors about using some undeclared entity, but you should be able to roll back from there…

5

Deleted all reference to my camera’s and tried hassio ha restart. Sat there for about 15 minutes and then looked at the logs and there was a syncworker error trying to get to my sonos devices. Have to leave office but will try hard reboot when I get home. There should be a way to fall back to a level that was working without having to get hassio all the way up. I have never had to fall back before without having Hassio up but have read that you can from the command line. As I stated before tried “homeassistant update --options version=0.80.0” but all I got was ok and then nothing.

Thanks for you replies but as of now no luck. My wife is going to be very unhappy as we use Amazon Alexa to turn on and off lights. Without hassio up no go on that front.

6

Probably there is, but I am new to Hassio too, so cant help you. Had Hass on ubuntu for 3 years, never had a problem which wasn’t my fault.
Never had to roll back from CLI, but also never had a failure on update. What I had though was a SD card failure, so I feel your pain. Months of configuration, all backups, on that single SD card! Lesson learned, backups are now on external server and I am using two SD cards, alternating between them.

Hopefully someone else will be able to help you get it going…

7

Try flashing a fresh card with the hassio firmware and restoring from a snapshot (except uncheck the home assistant version) so you restore all your settings.

Recently I had an issue where it upgraded then hang, I had to reboot mid upgrade which screwed me.

8

Well, when I got home I unplugged the pi and then plugged it back in and it came up without a problem. I had removed all my amcrest camera’s before I had rebooted. I put the camera’s back in and from the command line did an hassio ha restart and all web perfectly. Had dinner and then because I just got a new Iphone XR that appears to find it’s way to connection via ipv6 in my router which I suspect is causing it not to be recognized by hassio known devices, I did another command line hassio ha restart. and once again camera’s seem to be causing an error. Once again hard reboot (unplug and plug pi). After hard reboot came back up without camera’s. I am updating to 0.81.2 to see if this is more stable and then will add the camera’s back in. Camera’s have been working fine up until 0.81.1 then all hell broke loose.

9

Sorry, not an answer, but if a Hassio programmer is reading… Isn’t it possible that when you update there automatically a backup (Snapshot) is made? So when this happens the user can go back to a working version within half a hour? (Install fresh HA and import the Snapshot)

10

Need to close this as updates to Hassio has corrected the problem.