True) or are temporary (False).Temperature settings from Home Assistant will be sent to thermostat and then hold at that temperature. Set to False if you set a thermostat schedule on the thermostat itself and just want Home Assistant to send temporary temperature changes.
This will download + start a virtual machine using Virtualbox, which will internally setup the development environment necessary to start Home Assistant process and run test suite as well. After the VM has started succesfully, Home Assistant frontend will be accessible locally from your browser at http://localhost:8123
+This will download and start a virtual machine using Virtualbox, which will internally setup the development environment necessary to start Home Assistant process and run test suite as well. After the VM has started succesfully, the Home Assistant frontend will be accessible locally from your browser at http://localhost:8123
The root home-assistant directory on your workstation will be mirrored with /home-assistant inside the VM. In virtualization/vagrant there’s also a config folder that you can use to drop configuration files (here you can find more information on how to configure HASS).
The root home-assistant directory on your workstation will be mirrored with /home-assistant inside the VM. In virtualization/vagrant there’s also a config folder that you can use to drop configuration files (Check the Getting started section for more information about how to configure Home Assistant).
Any changes made to the local directory on your workstation will be available from the Vagrant host, so to apply your changes to the HASS process, just restart it:
+Any changes made to the local directory on your workstation will be available from the Vagrant host, so to apply your changes to the Home Assistant process, just restart it:
touch restart ; vagrant provision diff --git a/getting-started/updating/index.html b/getting-started/updating/index.html index b4dd2f4c05..0b36635ec9 100644 --- a/getting-started/updating/index.html +++ b/getting-started/updating/index.html @@ -97,7 +97,7 @@
Different installation methods as Raspberry Pi All-In-One Installer, Vagrant, or Virtualenv may have a alternative way for updating Home Assistant.
+Different installation methods as Raspberry Pi All-In-One Installer, Vagrant, or Virtualenv may have an alternative way for updating Home Assistant.
After updating, restart Home Assistant for the changes to take effect. This means that you have to restart hass itself or the autostarting daemon if you use any.
homeassistant: # Name of the location where Home Assistant is running - name: My Hass Instance + name: My Home Assistant Instance # Location required to calculate the time the sun rises and sets latitude: 37 longitude: -121 @@ -155,7 +155,7 @@While some of these components can technically be moved to a separate file they are so small or “one off’s” where splitting them off is superfluous. Also, you’ll notice the # symbol (hash/pound). This represents a “comment” as far as the commands are interpreted. Put another way, any line prefixed with a
-#will be ignored. This makes breaking up files for human readability really convenient, not to mention turning off features while leaving the entry intact. (Look at thezigbee:entry above and the b entry further down)Now, lets assume that a blank file has been created in the hass configuration directory for each of the following:
+Now, lets assume that a blank file has been created in the Home Assistant configuration directory for each of the following:
automation.yaml