I’m tempted to switch back to HAOS since I never ended up using the underlying Ubuntu for anything anyway
2 Likes
At the risk of sidetracking this thread. Since my Ubuntu is still working AND I can SSH into HA, I found that its a case of a storage file not being read after I tried to edit it. I’m struggling to get this sorted out so it there another way I can re-install HA? remove it first somehow? Unfortunately restoring a snapshot from the CLI isn’t working, I get an unknown error.
Can you restore the storage file from a backup?
I tried looking through my backup tar file and couldn’t find the storage data… I’m hoping it’s actually in there and not completely missed somehow (unless windows is hiding it…).
You could untag and remove all HA containers via SSH, then re-run the installation script. Backup your yaml first.
I think these are right, haven’t had to do it for a little while.
To find all the container IDs
docker images -a
Untag the Supervisor as it will want to keep on restarting
docker rmi -f d92961b7c9bb (image ID of the Supervisor - yours will be different)
Once that is done, you can use Portainer to delete every container, or do them one by one from the command line using the same command.
Ok. So. Crisis averted. 
After having the error staring me in the face regarding the core.entity.registry not being read I suddenly (after a few beers) had the thought to hunt for a JSON validator online. Sure enough it told me where my error was (a , where it should have been removed), rebooted the machine and HA is back in action… likely minutes before the missus gets home from work and loses her $#!t at me for breaking HA.
Note to self, don’t play with JSON files. In the meantime I have been readying my old NUC as a Debian based backup (since I can’t get the HAOS image to boot on it,gets stuck part way)
Thanks for the info guys, I’m sure it will come in handy at some point, just hopefully not too soon!
1 Like
Glad you got it sorted 
Does someone else have this error when opening the File Editor?
Is this installation the method by which I can get HA installed on an existing home server that already has docker running with plex and various other containers? And HA will just manage it’s own containers nicely and not touch the rest?
yes that’s correct!
Hi! Trying to update 114.4 Supervised (it’s running just fine) to 115.0\115.1 with no success.
My test rig is on Ubuntu 20.04.1 LTS. Other host on Ubuntu 18.04.5. Both updated but not able to start\run - gui lagging as hell and there is a lot of warnings in log (all related to networks - rest sensors, wifi lights, plugs etc)
It looks like it starts from zeroconf\discovery start
2020-09-19 20:06:48 INFO (SyncWorker_29) [homeassistant.components.zeroconf] Starting Zeroconf broadcast
2020-09-19 20:07:27 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /discovery request
2020-09-19 20:07:27 ERROR (MainThread) [homeassistant.components.hassio.discovery] Can't read discover info:
2020-09-19 20:07:46 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at http://bit.ly/2ogP58T : sensor.systemmonitor, image, hassio, timer, esphome, switch.mqtt, sensor.unifiprotect, person, search, onboarding, tts, sensor.github, proximity, light.mqtt, logbook, switch.unifi, switch.esphome, ssdp, notify.group, sensor.version, media_player.cast, binary_sensor.command_line, fan.xiaomi_miio, mqtt, camera.unifiprotect, auth, binary_sensor.mqtt, sensor.gismeteo, hacs, frontend, group, binary_sensor, start_time, binary_sensor.unifiprotect, input_datetime, zone, binary_sensor.template, binary_sensor.updater, sensor.darksky, sensor.sql, sensor.rest, camera.mjpeg, binary_sensor.esphome, device_tracker.unifi, sensor, wake_on_lan, script, media_player.mpd, persistent_notification, sensor.time_date, sensor.esphome, device_automation, binary_sensor.tod, unifiprotect, http, life360, light.esphome, input_number, telegram_bot, map, config, cast, system_health, binary_sensor.ping, utility_meter, websocket_api, sensor.start_time, upnp, counter, xiaomi_miio, light.xiaomi_miio, sensor.template, ios, notify.ios, api, media_player, homeassistant, history, logger, recorder, notify.telegram, sensor.unifi, fan, unifi, sensor.integration, sensor.min_max, sensor.statistics, ffmpeg, discovery, input_boolean, sensor.mqtt, ipp, sensor.command_line, zeroconf, lovelace, device_tracker, binary_sensor.yeelight, conversation, switch.xiaomi_miio, notify.file, automation, sensor.uptime, gismeteo, light.yeelight, sensor.utility_meter, switch.unifiprotect, updater, camera, yeelight, sensor.cpuspeed, notify, sensor.hacs, weather, homekit_controller, binary_sensor.workday, weather.darksky, sensor.nut, system_log, input_select, sun, switch, weather.gismeteo, switch.template, nut, binary_sensor.trend, sensor.ios, light
2020-09-19 20:08:37 INFO (SyncWorker_38) [mpd.base] Calling MPD disconnect()
2020-09-19 20:08:37 INFO (SyncWorker_38) [mpd.base] Calling MPD disconnect()
2020-09-19 20:08:37 INFO (MainThread) [homeassistant.core] Timer:starting
2020-09-19 20:08:37 WARNING (MainThread) [homeassistant.components.sensor] Updating gismeteo sensor took longer than the scheduled update interval 0:00:30
2020-09-19 20:08:37 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ping binary_sensor took longer than the scheduled update interval 0:00:33
2020-09-19 20:08:37 WARNING (MainThread) [homeassistant.helpers.entity] Update of binary_sensor.j3455 is taking over 10 seconds
2020-09-19 20:09:21 WARNING (MainThread) [homeassistant.components.media_player] Updating mpd media_player took longer than the scheduled update interval 0:00:10
2020-09-19 20:09:21 WARNING (MainThread) [homeassistant.components.sensor] Updating rest sensor took longer than the scheduled update interval 0:00:15
2020-09-19 20:09:22 WARNING (MainThread) [homeassistant.components.sensor] Updating rest sensor took longer than the scheduled update interval 0:00:20
2020-09-19 20:09:22 ERROR (MainThread) [homeassistant.components.nut] Timeout fetching NUT resource status data
2020-09-19 20:09:22 ERROR (MainThread) [homeassistant.components.nut] Timeout fetching NUT resource status data
2020-09-19 20:09:22 ERROR (MainThread) [homeassistant.components.nut] Timeout fetching NUT resource status data
2020-09-19 20:09:22 ERROR (MainThread) [homeassistant.components.nut] Timeout fetching NUT resource status data
2020-09-19 20:09:24 INFO (SyncWorker_11) [homeassistant.components.proximity] life360 Vova Tsymbal: proximity calculation complete
2020-09-19 20:10:34 WARNING (MainThread) [homeassistant.components.weather] Updating darksky weather took longer than the scheduled update interval 0:00:30
2020-09-19 20:10:36 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ping binary_sensor took longer than the scheduled update interval 0:00:29
2020-09-19 20:10:36 WARNING (MainThread) [homeassistant.components.switch] Updating xiaomi_miio switch took longer than the scheduled update interval 0:00:30
2020-09-19 20:10:36 WARNING (MainThread) [homeassistant.components.light] Updating xiaomi_miio light took longer than the scheduled update interval 0:00:30
2020-09-19 20:10:36 WARNING (MainThread) [homeassistant.components.fan] Updating xiaomi_miio fan took longer than the scheduled update interval 0:00:30
2020-09-19 20:10:36 WARNING (MainThread) [homeassistant.components.weather] Updating gismeteo weather took longer than the scheduled update interval 0:00:30
2020-09-19 20:10:36 WARNING (MainThread) [homeassistant.components.sensor] Updating rest sensor took longer than the scheduled update interval 0:00:30
2020-09-19 20:10:36 WARNING (MainThread) [homeassistant.components.sensor] Updating cpuspeed sensor took longer than the scheduled update interval 0:00:30
2020-09-19 20:10:36 WARNING (MainThread) [homeassistant.components.sensor] Updating systemmonitor sensor took longer than the scheduled update interval 0:00:30
2020-09-19 20:10:36 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ping binary_sensor took longer than the scheduled update interval 0:00:31
2020-09-19 20:10:41 WARNING (MainThread) [homeassistant.components.sensor] Updating gismeteo sensor took longer than the scheduled update interval 0:00:30
2020-09-19 20:10:41 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ping binary_sensor took longer than the scheduled update interval 0:00:32
2020-09-19 20:10:41 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ping binary_sensor took longer than the scheduled update interval 0:00:33
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating command_line binary_sensor took longer than the scheduled update interval 0:01:00
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ping binary_sensor took longer than the scheduled update interval 0:01:00
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.components.sensor] Updating rest sensor took longer than the scheduled update interval 0:01:00
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.components.sensor] Updating command_line sensor took longer than the scheduled update interval 0:01:00
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.main_input_boolean_sasha_tracker is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.main_state is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of binary_sensor.nuc is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.power_strip_s is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.gateway_plug_entrance_hb_usb is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.gateway_plug_entrance_hb is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.philips_e27_s is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.mirror_light_b is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.philips_e27_mb is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of fan.purifier2s is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of fan.humidifier2 is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of binary_sensor.usg_gateway is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of binary_sensor.google_dns is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of binary_sensor.h96_v is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of binary_sensor.tv_box is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.config_line_count_sh_code is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of binary_sensor.rpi is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.zigbee2mqtt_addon is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.supervisor_updates is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.set_utility_from_main is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.cpu_speed is taking over 10 seconds
2020-09-19 20:10:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.gismeteo_temperature is taking over 10 seconds
Any suggestions except of moving to Deb10?
Sounds like yiur templares might be faulty. See the 0.115 release thread. If I am right then moving to debian won’t help.
chief, you were absolutely right! it’s all about templates! thanks for heads up!!!
I have quite a few docker containers already and my host has multiple IP addresses. How can I set which IP address HA will get?
HA presents to the world as the IP address of the host.
The 172. addresses are internal to docker.
I don’t get why HA in docker on Ubuntu is “unsupported” though. Who’s gonna install only HA on something like a NUC with option to access the whole Ubuntu/server. Maybe I’m missing something.
Everybody starts on a Raspberry PI, but after a while (and more devices and integrations) the need if there to move so something more powerful. Unless Pi 4 is powerful enough, and SD cards have magically improved (or are people using SSD?).
It is also awesome that they made HassOS, don’t get me wrong. But it feels a bit constrained.
VMs are a thing too. For example I have a powerful server, but it’s running ESXi, so I can use HomeAssistant with the entire HAOS as a VM, and still have other VMs for a windows server, ubuntu, etc.
I hadn’t considered VMs to be honest. Not that I’m a Docker specialist, but I know more about it than Hypervisors.
So ESXi (or another hypervisor) on a host machine, and then run Home Assistant (full w/ supervisor) as a VM and you’ve hot yourself a support installation? Cool.
I see a lot of ESXi post when Googling. Might be personal, but is it overall the best Hypervisor (features vs ease of use)?
Might there be issues while running in a VM regarding access to USB (ie. zwave or zigbee) or network things?
Yup, it gives you a fully supported system running their OS.
As long as you don’t muck with the network settings or anything, it’s all good, and you can do USB pass-through etc as needed.
Definitely a personal opinion imho. Lots of people here use Proxmox to have a HA VM, for example.
Personally, I use ESXi at work a lot, so I’m just more familiar with it and didnt want to learn how to use another hypervisor for this purpose.
In ESXi (and proxmox, as I understand, and im sure other hypervisors) you can simply choose to pass the device through from the host to the VM and it works just fine. In the screenshot below, I have my Z-Wave stick and Zigbee stick passed through.
1 Like
So now we have a host, a hypervisor, to install HassIO, which installs another virtualization layer (docker)… seems silly. In any case, I’m going the VM route myself. Let’s hope HA Docker becomes a more “supported” option down the road.