Trying to upgrade version of homeassistant from 100.3 to 101, but getting this errors before reboot:
19-10-31 06:24:37 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.101.0
19-10-31 06:24:37 INFO (SyncWorker_14) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.100.3 to homeassistant/raspberrypi3-homeassistant:0.101.0
19-10-31 06:24:37 INFO (SyncWorker_14) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.101.0.
19-10-31 06:27:13 ERROR (MainThread) [hassio.utils] Can't execute update while a task is in progress
19-10-31 06:30:08 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-10-31 06:32:01 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
19-10-31 06:32:05 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
19-10-31 06:32:06 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
19-10-31 06:32:16 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://version.home-assistant.io/stable.json:
19-10-31 06:32:39 INFO (MainThread) [hassio.store] Load add-ons from store: 61 all - 0 new - 0 remove
and after loading homeassistant:
19-10-31 06:49:00 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-10-31 06:49:00 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.100.3
19-10-31 06:49:01 INFO (SyncWorker_14) [hassio.docker.interface] Cleanup images: ['homeassistant/raspberrypi3-homeassistant:0.101.0']
19-10-31 07:12:01 INFO (MainThread) [hassio.host.info] Update local host information
19-10-31 07:12:01 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-10-31 07:12:01 INFO (MainThread) [hassio.host.services] Update service information
19-10-31 07:12:01 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-10-31 07:12:02 INFO (MainThread) [hassio.host.network] Update local network DNS information
19-10-31 07:12:02 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
19-10-31 07:25:09 INFO (MainThread) [hassio.api.security] /supervisor/logs access from core_ssh
I tried the update this morning 1/11/19 and RPi 3 just sat there for ages (30-40 mins) and there was no activity. Pi had lost IP address so I assumed Pi was totally hung so I reboot.
System came back up as the previous 0.100.3
but system seems confused as to what is latest version …see below
If you take a look at the logs under system it might say something with rollback (in yellow or red I think). Failing with the update will let the system boot the old version.
Maybe you might want to try the workaround from above. If you use only the web GUI you can also comment your whole config, reducing it to the default config part.
I checked the log and the only yellow was some warning
19-10-31 21:59:17 WARNING (MainThread) [hassio.dns] Ignore invalid DNS Server: dns://2001:8003:f00f:9f00::1
I had no idea where this came from but it looked like an IP6 address so I checked my WAN IP and it has this IP6 address in the service provider’s DHCP section of my router???
Beats my poor brain
Yes I can fiddle with the config as suggested but I really was trying to just use the GUI and set it up so that other family members who have less skills could operate it.
I had a look at the release notes and there is not much that I think I need so might wait and see what transpires.
I was hoping the system was a bit more robust for less skilled users.
Hm, seems like your hass.io installation has taken the v6-DNS-server from your provider. But I would say thats normal and this warning shouldn’t prevent from updating. Any errors?
Do you have an api-key defined in your config? If so please comment it, reboot and then try it again.
No, No API key.
Only key is HEX KEY for my Z-Wave USB Stick
This is my Config so far. I am a newby at all this so it’s pretty straight forward
I have xxx’ed out username/passwords/IPV4
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
#
## Camera configuration.yaml entry
#camera: !include cameras.yaml
#Front DoorCam
binary_sensor:
- platform: hikvision
host: 192.168.0.x
username: xxx
password: xxx
#ShedCam
- platform: hikvision
host: 192.168.0.x
username: xxx
password: xxx
#BackDoorCam
- platform: hikvision
host: 192.168.0.x
username: xxx
password: xxx
# Enphase Envoy configuration.yaml entry, limiting the metrics to production only
sensor:
- platform: enphase_envoy
ip_address: 192.168.0.x
monitored_conditions:
- production
- daily_production
- seven_days_production
- lifetime_production
#
# Moons Phase Sensor
- platform: moon
# Synology DSM216II
#
- platform: synologydsm
name: DSM216II
host: 192.168.0.x
username: xxx
password: xxx
monitored_conditions:
- cpu_total_load
- memory_real_usage
- network_up
- network_down
- volume_status
- disk_status
- disk_smart_status
- disk_temp
# ZWave
zwave:
usb_path: /dev/ttyACM0
network_key: "0x24, 0xcb, 0x1d, 0xa3, 0x5c, 0xfa, 0x00, 0x7b, 0x7d, 0xa2, 0xb8, 0xa9, 0x5c, 0xc6, 0xac, 0xeb"
# Example configuration.yaml entry
stream:
I am running Areila Android app on my Samsung s10e but don’t know what effect this would have.
using the Line crossing on one of my cameras to turn on/off an LED LAMP between sunset and sunrise
same camera but send a notification to Ariela when it’s between sunrise and sunset.
simple turn on/off of LED lamp for 2.5 hours after sunset +1 hr
I have not tried another update at this stage
I have run the check config in "Server Control’ and all good.
Anyway, If anything silly that I have done jumps out, let me know.
I will try fiddling next week when I have more spare time but as I cannot see what I have done that is overly complicated.
Thanks for your help.
Well after reading and researching I really could not diagnose what the problems was so I took the following steps.
I thought it might be disk space so I installed ssh and did a df and there was only 20% of the 16GB SD card used or 80% free. Did not look like a disk space issue?
The /dev/root was at 100% so I thought I would get a 32GB (as recommended, I was only using a 16GB) and rebuild. This was a great way to practise recovery as well.
I then took a snapshot of my old system and stored it on my PC.
I downloaded the latest image and burned it to the 32GB Micro SD, plugged it in and waited the 20 minutes until it came up.
I followed the initial install instructions until it was ready to use. Next I installed samba so that I could import the snapshot.
The big trick was to only do a selected restore as I did not want the old system and old samba.
This brought all my settings back and I was on the latest 0.101.2.
It also taught me how to maintain the system in case of a Micro SD failure.
Hopefully future updates will work.
Just for completeness this is the disk space on the 32GB. The /dev/root is still at 100%. Not being an big expert in unix or this image I am at a loss to explain this.
same issue, followed fix provided by Oliver and working now on raspi. Just had to re-run certbot to update python and certificate for ssl to work again.
