The add-ons and snapshot function are only available for hass.io.
I have hass.io installed on Ubuntu Server 16.04 so that is a possibility for you as well.
Instructions are here https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio.
I’ve installed Home Assistant not HASS,io… this is the point…
As in the page you mentioned the supported manchines are only:
raspberrypi
raspberrypi2
raspberrypi3
qemux86-64
qemux86
intel-nuc
… and I’ve an Atom board.
Yes that is exactly what I mentioned in my post. You can install hass.io on Ubuntu. Without hass.io you don’t have the snapshot and add-ons.
So… also Atom is supported?
Guess not according to the documentation.
When I answered your first post the remark that you are using Atom was not there yet 
You can install Hass.io using the manual install steps. I did that to install in a VM, and it worked.
Which is an x86-64 bit processor
In this case I will install Home Assistant, not HASS.io … so would mean that I would not have addons and other special features of HASS.io… it’s correct?
You could install in a vm, but at that point why are you running hass.io on an ubuntu server. You were obviously running hass.io on a Pi before, so I’d just go back to that over a vm.
There are no plugins for home assistant, and the configs for the plugins are not really useful outside of hass.io. So, you’ll have to install each component you want and configure it.
If you want an easier way to setup samba, ssh, fail2ban, and more, you could install webmin which I really like for configuring my ubuntu server.
Hass.io is just a Docker management tool, so it should be possible to manual run the same Docker images that are used by the hass.io addons.
Or, choose a different management tool, for instance Rancher, like I’m doing (Rancher as an alternative to HASS.io).
Correct. You don’t get the add-ons, but you do get the ability to do all those (and other) things yourself - it’s just not point and click.
Next time I will trying to run HASS.io on a VM as described here https://resin.io/blog/no-hardware-use-virtualbox/
Now I would want to try the Home Assistant on Ubuntu Server… for the moment I’ve Home Assistant running on this machine and I’ve already copied all the config files that I’ve on the HASS.io on RPi3 but I got some error that I can’t explain:
2018-01-02 11:39:14 ERROR (MainThread) [homeassistant.loader] Unable to find component hue
2018-01-02 11:39:14 ERROR (MainThread) [homeassistant.setup] Setup failed for hue: Component not found.
2018-01-02 11:39:16 ERROR (Thread-5) [homeassistant.components.notify.nma] Wrong API key supplied: Your IP exceeded the maximum number of API calls per hour allowed.
2018-01-02 11:39:16 ERROR (MainThread) [homeassistant.components.notify] Failed to initialize notification service nma
2018-01-02 11:39:19 ERROR (Thread-11) [homeassistant.util.package] Unable to install package https://github.com/jabesq/netatmo-api-python/archive/v0.9.2.zip#lnetatmo==0.9.2: Command "/home/igor/homeassistant/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-x6otmjl1-build/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-ikgs6h17-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/igor/homeassistant/include/site/python3.5/lnetatmo" failed with error code 1 in /tmp/pip-x6otmjl1-build/
2018-01-02 11:39:19 ERROR (MainThread) [homeassistant.setup] Not initializing netatmo because could not install dependency https://github.com/jabesq/netatmo-api-python/archive/v0.9.2.zip#lnetatmo==0.9.2
2018-01-02 11:39:19 ERROR (MainThread) [homeassistant.setup] Setup failed for netatmo: Could not install all requirements.
2018-01-02 11:39:19 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of sensor.netatmo. Setup failed for dependencies: netatmo
2018-01-02 11:39:19 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform sensor.netatmo: Could not setup all dependencies.
2018-01-02 11:39:23 ERROR (Thread-9) [homeassistant.util.package] Unable to install package google-api-python-client==1.6.4: Command "/home/igor/homeassistant/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-uex0kl7g/httplib2/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-s53c5zjp-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/igor/homeassistant/include/site/python3.5/httplib2" failed with error code 1 in /tmp/pip-build-uex0kl7g/httplib2/
2018-01-02 11:39:23 ERROR (MainThread) [homeassistant.setup] Not initializing google because could not install dependency google-api-python-client==1.6.4
2018-01-02 11:39:23 ERROR (MainThread) [homeassistant.setup] Setup failed for google: Could not install all requirements.
Why I’m unable to install AVM, NetAtmo and so on?
There will be actual errors elsewhere in the log, that would tell us more, however.
[homeassistant.components.notify.nma] Wrong API key supplied: Your IP exceeded the maximum number of API calls per hour allowed.
That one is easy - check the API key and if it’s right you just need to wait until you’re no longer exceeding the rate limit
[homeassistant.util.package] Unable to install package https://github.com/jabesq/netatmo-api-python/archive/v0.9.2.zip#lnetatmo==0.9.2: Command "/home/igor/homeassistant/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-x6otmjl1-build/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-ikgs6h17-record/install-record.txt --single-version-externally-managed --compile --install-headers /home/igor/homeassistant/include/site/python3.5/lnetatmo"
failed with error code 1 in /tmp/pip-x6otmjl1-build/
That (and one of the others) is a permission denied error, which almost always means you forgot to run something as homeassistant. Try:
sudo chown -R `homeassistant` /srv/homeassistant
If you’re not using /srv/homeassistant as the base of your environment, use the location you built your venv in.
1 Like
Many thanks @Tinkerer! now is almost all working fine… remain Philips Hue that won’t work… why?
2018-01-03 10:06:34 ERROR (MainThread) [homeassistant.loader] Unable to find component hue
2018-01-03 10:06:34 ERROR (MainThread) [homeassistant.setup] Setup failed for hue: Component not found.
2018-01-03 10:06:38 WARNING (Thread-2) [pyW215.pyW215] Failed to open url to 192.168.1.41
2018-01-03 10:06:45 WARNING (MainThread) [homeassistant.setup] Setup of switch is taking over 10 seconds.
2018-01-03 10:06:45 WARNING (MainThread) [homeassistant.setup] Setup of device_tracker is taking over 10 seconds.
2018-01-03 10:06:47 WARNING (MainThread) [homeassistant.components.switch] Setup of platform fritzdect is taking over 10 seconds.
2018-01-03 10:07:10 WARNING (Thread-10) [pyW215.pyW215] Failed to open url to 192.168.1.41
2018-01-03 10:07:23 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from fritz took longer than the scheduled scan interval 0:00:12
2018-01-03 10:07:25 WARNING (Thread-9) [netdisco.ssdp] Error fetching description at http://192.168.0.254:49152/wps_device.xml
2018-01-03 10:07:28 WARNING (Thread-9) [netdisco.ssdp] Error fetching description at https://192.168.1.40/HNAP1/
Why “unable to find Hue component”?
https://home-assistant.io/components/hue/ is what you’ve enabled?
There should be more errors further up, near the beginning of the startup, that help identify it. You may want to use the likes of https://hastebin.com/ to share the first 50 lines or so after startup.
Philips Hue and Netatmo it’s the only two component that are not working for me.
This is all the logs that I saw from “Info” page:
https://hastebin.com/qutiliwezi.sql
Try hassio homeassistant logs - it might give you more
I have found this post Hue component failing to load - hass.io 59.2 - #4 by Mariusthvdb where it say …
This mystery is solved. ‘hue:’ in config is not valid until v.60. For older versions use
light:
- platform: hue
host: 192.168.1.39
allow_hue_groups: true
Later I will try… maybe is the same issue for the Netatmo component? The Home Assistant version is still to 0.57.3 instead of 0.60 of HASS.io
… well … using the config above Hue component now works… and I don’t know why… also the Netatmo component begin to work!