There is an abundant `put` in the introduction being used twice right after each other. Most probably this is an oversight / typo. This removes one instance of the word, to make the sentence better readable and grammatically correct.
* Cleaned up Docker Run Command under "Z-Wave" & "Bluetooth" section
Need to make it match the format of the other run commands in the page.
* ✏️ Tweak
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Minor textual fixes and readability improvements.
Additionally, is the part for the Raspberry Pi Docker container also correct for a RasPi 4? The 'docker pull' commands suggests it's for a RasPi 3...
* Add clarification about docker installation
Adding a note about the core docker installation vs the supervised docker installation.
* ✏️ Tweaks
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
* Update synology.markdown
It is also possible to run Hass.io in a VM on Synology using the VDI image.
* Update source/_docs/installation/synology.markdown
Co-Authored-By: Klaas Schoute <klaas_schoute@hotmail.com>
Co-authored-by: Klaas Schoute <klaas_schoute@hotmail.com>
With this instruction a have an error after starting service:
```
# sysrc homeassistant_enable="YES"
homeassistant_enable: -> YES
# service homeassistant start
install: : No such file or directory
Starting homeassistant.
daemon: open: Permission denied
/usr/local/etc/rc.d/homeassistant: WARNING: failed to start homeassistant
```
There is needs to define logfile variable in rc.d script
* updated rc.d script
Add extra_commands
check_config - checks config using `hass --script check_config`
upgrade - stops HA / upgrade / checks config / starts HA (only starts if config check passes)
test - simple test to check directories / activate venv / check version of python and homeassistant
restart - (modified) check_config / stop HA /start HA (only restart if config check passes)
NOTE: All extra_commands REQUIRE bash to be installed
`pkg install bash`
I also removed the check_config from the pre_start function because because it will prevent HA from starting
if the configuration is missing (Like a clean install from example). NO BUENO!
Another case to consider haveing no configuration even after initial install is troubleshooting or testing.
For instance with rc.d script createing a fresh config is simple.
Let's suppose my working config is at
`/home/hass/homeassistant`
Now to get a clean configuration I can just do this
service homeassistant stop
sysrc sysrc homeassistant_config_dir="/home/hass/ha_test_config"
service homeassistant start
That's it! Configuration wise, it's a clean install. To switch back to working config I just
service homeassistant stop
sysrc sysrc homeassistant_config_dir="/home/hass/homeassistant"
service homeassistant start
Awesome right?! But that doesn't work if check_config fails during pre_start
* add pkgs
These are not required to install HA but they are quickly missed once you start to actual use it. Let's just avoid
some fustration from the start. I don't think this list should be all inclusive but these basic things seem to be
frequently needed from the start.
autoconf |
gmake | - looking at you Z-Wave, Stream, IKEA Tradfri
pkgconf |
bash - Give me bash or give me death! Seriously, it makes life easier. There's not alot of *BSD focus
around HA. I only use *BSD because of FreeNAS -- Typically (with the exception of jails) FreeNAS is webui.
I'm ok with Linux cli and it's very similiar to FreeNAS but not the same. It's not bash. I don't think it
needs to be for the root user either. But having bash installed and used by the HA user makes it easier
to follow along with exising documentation for other virtualenv type installs when trying to further expand
your HA installation
* give me bash or give me death!
Most people won't notice a differene but we'll know in our hearts we did the right thing.
* fix typo
I'm lucky I can spell my name
* whitespace
* use venv
Use the built-in venv instead of virtualenv which must be installed seperate.
By including the prompts in the shell commands, it breaks the copy/paste functionality provided on the webpage https://www.home-assistant.io/docs/installation/raspberry-pi/. I understand it was to indicate a change for the user but that should be in the surrounding text.
* Tell people they need opensslv.h and cffi.h in order to use
pip install homeassistant (at least on armv7/armhf).
* ✏️ Tweaks
Co-authored-by: null <mfkyle@yahoo.com>
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
* Remove host/netsh commands from docker directives
Added -p 8123:8123 to the Windows docker command line. Seems more reliable and easier for users.
Add ports to docker-compose.yaml files for easier launches..
* revert requested items.
* ✏️ Tweaks
* centos
* Update source/_docs/installation/centos.markdown
Fine with me. I did like having the "venv" in there to make it more obvious as to what is going on.
Co-Authored-By: Fabian Affolter <mail@fabian-affolter.ch>
* Update source/_docs/installation/centos.markdown
Co-Authored-By: Fabian Affolter <mail@fabian-affolter.ch>
* Update with working instructions
Old instructions failed to include virtualenv, also failed to actually start HA as the config directory it default creates was wrong, and empty.
* Minor changes
