From b92de94a4b47da9a8f402c80e4becf8426cb1ec1 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Fri, 15 Dec 2017 16:35:13 +0100 Subject: [PATCH 01/10] Create homematic.markdown --- source/_addons/homematic.markdown | 41 +++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 source/_addons/homematic.markdown diff --git a/source/_addons/homematic.markdown b/source/_addons/homematic.markdown new file mode 100644 index 00000000000..50f5e2d9e95 --- /dev/null +++ b/source/_addons/homematic.markdown @@ -0,0 +1,41 @@ +--- +layout: page +title: "HomeMatic" +description: "HomeMatic hardware support to turn you Home-Assistant into a CCU." +date: 2017-04-30 13:28 +sidebar: true +comments: false +sharing: true +footer: true +--- + +Set up a [HomeMatic](https://github.com/eq-3/occu) hardware layer. At the moment we don't support hmIP but that is in progress. For learning and handling devices use our internal homematic panel and services (in progress) or use [Homematic-Manager](https://github.com/hobbyquaker/homematic-manager) > 2.0. + +The logic layer will be Home-Assistant. There is no ReGa or other logic layer installed. You can't import exists configuration, you need new learn it into Home-Assistant. + +Follow devices will be supported and tested: +- [HM-MOD-RPI-PCB](https://www.elv.ch/homematic-funkmodul-fuer-raspberry-pi-bausatz.html) + +```json +{ + "type": "CCU2", + "device": "device": "/dev/ttyAMA0" +} +``` + +Configuration variables: + +- **type** (*Require*): Device type for RFD service. Look into handbook of your device. +- **device** (*Require*): Device on host. + +## {% linkable_title Home Assistant configuration %} + +Use the following configuration in Home Assistant to use it: + +```yaml +homematic: + interfaces + BidCoS-RF: + ip: core-homematic + port: 2001 +``` From 898a12d7500bf1d2367b080cc8d3a847c0738ea6 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Fri, 15 Dec 2017 16:47:42 +0100 Subject: [PATCH 02/10] Update homematic.markdown --- source/_addons/homematic.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_addons/homematic.markdown b/source/_addons/homematic.markdown index 50f5e2d9e95..1104414c775 100644 --- a/source/_addons/homematic.markdown +++ b/source/_addons/homematic.markdown @@ -36,6 +36,6 @@ Use the following configuration in Home Assistant to use it: homematic: interfaces BidCoS-RF: - ip: core-homematic + host: core-homematic port: 2001 ``` From eebde05925a77851d8b9e59ffdde193f0ef65653 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Fri, 15 Dec 2017 19:30:36 +0100 Subject: [PATCH 03/10] Update homematic.markdown --- source/_addons/homematic.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/_addons/homematic.markdown b/source/_addons/homematic.markdown index 1104414c775..56e50a673e7 100644 --- a/source/_addons/homematic.markdown +++ b/source/_addons/homematic.markdown @@ -39,3 +39,10 @@ homematic: host: core-homematic port: 2001 ``` + +## {% linkable_title Raspberry Pi3 %} + +With HM-MOD-PRI-PCB you need add follow into your `config.txt` on boot partition: +``` +dtoverlay=pi3-miniuart-bt +``` From 4308e11a07bfa6540e5f190a0544a96664caeda4 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Fri, 15 Dec 2017 19:32:09 +0100 Subject: [PATCH 04/10] Update homematic.markdown --- source/_addons/homematic.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_addons/homematic.markdown b/source/_addons/homematic.markdown index 56e50a673e7..872b521d828 100644 --- a/source/_addons/homematic.markdown +++ b/source/_addons/homematic.markdown @@ -19,7 +19,7 @@ Follow devices will be supported and tested: ```json { "type": "CCU2", - "device": "device": "/dev/ttyAMA0" + "device": "/dev/ttyAMA0" } ``` From 90122dcff6e25fab42494e17e23dbfedcff16d41 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Sat, 16 Dec 2017 02:57:28 +0100 Subject: [PATCH 05/10] Update homematic.markdown --- source/_addons/homematic.markdown | 26 ++++++++++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/source/_addons/homematic.markdown b/source/_addons/homematic.markdown index 872b521d828..1f91fe3dc79 100644 --- a/source/_addons/homematic.markdown +++ b/source/_addons/homematic.markdown @@ -18,16 +18,38 @@ Follow devices will be supported and tested: ```json { - "type": "CCU2", - "device": "/dev/ttyAMA0" + "rf_enable": true, + "rf": [ + { + "type": "CCU2", + "device": "/dev/ttyAMA0" + } + ], + "wired_enable": false, + "wired": [ + { + "serial": "xy", + "key": "abc", + "ip": "192.168.0.0" + } + ] } ``` Configuration variables: +- **rf_enable** (*Require*): Boolean. Enable or disable BidCoS-RF. +- **wired_enable** (*Require*): Boolean. Enable or disable BidCoS-Wired. + +For RF devices - **type** (*Require*): Device type for RFD service. Look into handbook of your device. - **device** (*Require*): Device on host. +For RF devices +- **serial** (*Require*): Serial number of device. +- **key** (*Require*): Encrypted key. +- **ip** (*Require*): IP address of lan gateway. + ## {% linkable_title Home Assistant configuration %} Use the following configuration in Home Assistant to use it: From a835d5feda6cd5062dfb8a6e1e419792a34644de Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sat, 16 Dec 2017 02:57:55 -0800 Subject: [PATCH 06/10] Update virtual environment instructions (#4191) * Update virtual environment instructions * Add link to other guides --- source/_docs/installation/virtualenv.markdown | 130 +++++------------- 1 file changed, 35 insertions(+), 95 deletions(-) diff --git a/source/_docs/installation/virtualenv.markdown b/source/_docs/installation/virtualenv.markdown index 97a5f8c36f5..234ea989460 100644 --- a/source/_docs/installation/virtualenv.markdown +++ b/source/_docs/installation/virtualenv.markdown @@ -9,99 +9,39 @@ sharing: true footer: true redirect_from: /getting-started/installation-virtualenv/ --- -

-Beginners should check our [getting started guide](/getting-started/) first. + +If you alreacy have Python 3.5 or later installed, you can easily give Home Assistant a spin. + +It's recommended when installing Python packages that you use a virtual environment. This will make sure that your Python installation and Home Assistant installation won't impact one another. + +_(If you're on a Debian based system, you will need to install Python virtual environment support using `apt-get install python3-pip python3-venv`)_ + + 1. Create a virtual environment: + ``` + python3 -m venv homeassistant + ``` + 2. Open virtual environment: + ``` + cd homeassistant + ``` + 3. Activate virtual environment: + ``` + source bin/activate + ``` + 4. Install Home Assistant: + ``` + python3 -m pip install --upgrade homeassistant + ``` + 5. Run Home Assistant: + ``` + hass --open-ui + ``` + +### {% linkable_title Notes %} + +- In the future, if you want to start Home Assistant again, follow step 2, 3 and 5. +- If you want to upgrade Home Assistant, follow step 2 and 3 and 4. + +

+Looking for more advanced guides? Check our available guides.

- -There are several reasons why it makes sense to run Home Assistant in a virtual environment. A [virtualenv](https://virtualenv.pypa.io/en/latest/) encapsulates all aspect of a Python environment within a single directory tree. That means the Python packages you install for Home Assistant won't interact with the rest of your system and vice-versa. It means a random upgrade for some other program on your computer won't break Home Assistant, and it means you don't need to install Python packages as root. - -Virtualenvs are pretty easy to setup. We'll be using Debian in this example (as many Home Assistant users are running Raspbian on a Raspberry Pi), but all of the Python related steps should be the same on just about any platform. - -### {% linkable_title Basic guide %} - -The basic guide is for testing Home Assistant. Also check the advanced guide for instances used in production. - -## {% linkable_title Step 1: Install dependencies %} - -```bash -$ sudo apt-get update -$ sudo apt-get upgrade -$ sudo apt-get install python3-pip python3-dev python3-venv -$ sudo pip3 install --upgrade virtualenv -``` - -## {% linkable_title Step 2: Setup virtualenv %} - -```bash -$ python3 -m venv $HOME/homeassistant -``` - -## {% linkable_title Step 3: Install or update Home Assistant %} - -```bash -$ source $HOME/homeassistant/bin/activate -(homeassistant)$ pip3 install --upgrade homeassistant -``` - -## {% linkable_title Step 4: Run Home Assistant %} - -```bash -$ $HOME/homeassistant/bin/hass -``` - -### {% linkable_title Advanced guide %} -## {% linkable_title Separate user & group for Home Assistant (Basic guide step 2) %} - -It's a good idea to give services like Home Assistant their own user. It gives you more granular control over permissions, and reduces the exposure to the rest of your system in the event there is a security related bug in Home Assistant. This is a reasonably Linux oriented step, and will look different on other operating systems (or even other Linux distributions). - -```bash -$ sudo adduser --system homeassistant -$ sudo addgroup homeassistant -``` - -Home Assistant stores its configuration in `$HOME/.homeassistant` by default, so in this case, it would be in `/home/homeassistant/.homeassistant`. - -If you plan to use a Z-Wave controller, you will need to add this user to the `dialout` group: - -```bash -$ sudo usermod -G dialout -a homeassistant -``` - -## {% linkable_title Custom installation directory for Home Assistant (Basic guide step 2) %} - -This can be anywhere you want. We chose to put it in `/srv`. You also need to change the ownership of the directory to the user you created above. - -```bash -$ sudo mkdir /srv/homeassistant -$ sudo chown homeassistant:homeassistant /srv/homeassistant -$ python3 -m venv /srv/homeassistant -``` - -## {% linkable_title Install or update Home Assistant %} - -This is obviously only necessary if you created a `homeassistant` user, but if you did, be sure to switch to that user whenever you install things in your virtualenv, otherwise you'll end up with mucked up permissions. - -```bash -$ sudo su -s /bin/bash homeassistant -``` - -The `su` command means 'switch' user. We use the '-s' flag because the `homeassistant` user is a system user and doesn't have a default shell by default (to prevent attackers from being able to log in as that user). - -```bash -$ source /srv/homeassistant/bin/activate -(homeassistant)$ pip3 install --upgrade homeassistant -``` - -## {% linkable_title Run Home Assistant (Basic guide step 4) %} - -There are two ways to launch Home Assistant. If you are **in** the virtualenv, you can just run `hass` and it will work as normal. If the virtualenv is not activated, you just use the `hass` executable in the `bin` directory mentioned earlier. There is one caveat... Because Home Assistant stores its configuration in the user's home directory, we need to be the user `homeassistant` or specify the configuration with `-c`. - -```bash -$ sudo -u homeassistant -H /srv/homeassistant/bin/hass -``` - -The `-H` flag is important. It sets the `$HOME` environment variable to `/home/homeassistant` so `hass` can find its configuration. - -## {% linkable_title Starting Home Assistant on boot %} - -The [autostart instructions](/getting-started/autostart/) will work just fine, just be sure to replace `/usr/bin/hass` with `/srv/homeassistant/bin/hass` and specify the `homeassistant` user where appropriate. From 15e3857184883e36aa83de3cdfa77a96483e94f1 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sat, 16 Dec 2017 04:37:08 -0800 Subject: [PATCH 07/10] Revamp getting started (#4194) * Revamp getting started * Comments by Landrash * Add text editor to software requirements * Address comments --- source/_docs/installation.markdown | 14 ++++- source/getting-started/configuration.markdown | 54 ++++++++++++++++--- source/getting-started/index.markdown | 51 ++++++++++-------- 3 files changed, 90 insertions(+), 29 deletions(-) diff --git a/source/_docs/installation.markdown b/source/_docs/installation.markdown index 632457f28a9..4b54abe2d32 100644 --- a/source/_docs/installation.markdown +++ b/source/_docs/installation.markdown @@ -14,9 +14,21 @@ redirect_from: /getting-started/installation/ Beginners should check our [Getting started guide](/getting-started/) first. This is for users that require advanced installations.

-Home Assistant provides multiple ways to be installed. A requirement is that you have [Python](https://www.python.org/downloads/) installed. For Windows, we require at least **Python 3.5** and for other operating systems at least **Python 3.4.2**. +Home Assistant provides multiple ways to be installed. A requirement is that you have [Python 3.5+](https://www.python.org/downloads/) installed.
+ +
+ +
+
Hass.io
(Beginner friendly)
+ + +
+ +
+
On top of an existing Python 3.5+ installation
+
diff --git a/source/getting-started/configuration.markdown b/source/getting-started/configuration.markdown index 360ef56f009..5814b3c1cb1 100644 --- a/source/getting-started/configuration.markdown +++ b/source/getting-started/configuration.markdown @@ -9,19 +9,59 @@ sharing: true footer: true --- -When launched for the first time, Home Assistant will write a default configuration file, called `configuration.yaml`, enabling the web interface and [device discovery](/components/discovery/). It can take up to a minute for your devices to be discovered and appear in the user interface. +If you made it here, awesome! That means that you got Home Assistant up and running. It might have already found some of your networked devices. This is going to be fun! -The `configuration.yaml` is written in [YAML](/docs/configuration/yaml/), stored in [`.homeassistant`](/docs/configuration/), and can be modified with a text editor. +Home Assistant stores its configuration in a file called `configuration.yaml`. A default one is created when Home Assistant is started for the first time. Some of the things in the configuration file can be edited via the user interface, other parts require you to edit the configuration file directly. -See the [components overview page](/components/) to find sample entries for your devices and services. For a sensor that is showing [random values](/components/sensor.random/), the entry would look like the sample below: +There are two common approaches to edit your configuration: via Samba/Windows Networking and via the HASS Configurator. Both of these are [official add-ons for Hass.io](/addons/). + +## {% linkable_title Installing Hass.io add-ons %} + +Hass.io add-ons are installed from the add-on store embedded in the Hass.io panel: + + - Open Home Assistant by navigating to [http://hassio.local:8123][local]. + - Click on the menu icon in the top left and select Hass.io in the sidebar. + - The Hass.io panel opens, now open the add-on store by clicking the shopping bag. + +[local]: http://hassio.local:8123 + +

+ +From the Hass.io main panel open the add-on store. +

+ +### {% linkable_title Editing config via HASS Configurator %} + +The first add-on we should install is the HASS Configurator. With the HASS Configurator you'll be able to edit your Home Assistant configuration from the web interface. + +Go to the add-on store (see previous step), click on Configurator and click on INSTALL. When installation is complete the UI will go to the add-on details page for the configurator. Here you will be able to change settings, start and stop the add-on. + + - Change the settings to set a password and click on save + - Start the add-on + - You will be able to click the "WEB UI" link to open the Web UI + +Time for the first practice with the configurator. Add the following to `configuration.yaml` file to add a link to the Configurator in the sidebar: ```yaml -sensor: - - platform: random +panel_iframe: + configurator: + title: Configurator + icon: mdi:wrench + url: http://hassio.local:3218 ``` -The [Setting up devices part](/docs/configuration/devices/) contains the additional documentation details about adding devices and services and [customization](/docs/configuration/customizing-devices/). +Now restart Home Assistant for the changes to the configuration to take effect. You can do this by going to the config panel (Configuration in the sidebar) -> General -> Restart Home Assistant. -For further details about configuration, please take a look at the [configuration documentation](/docs/configuration/). +### {% linkable_title Editing config via Samba/Windows Networking %} + +Maybe you are not a big fan of our web editor and want to use a text editor on your computer instead. This is possible by sharing the configuration over the network using the Samba add-on, which can be installed from the Hass.io add-on store. + +After you have installed it, click on START. Hass.io should now be available in the networking tab on your computer. Use a text editor like the free [Visual Studio Code](https://code.visualstudio.com/) to edit `configuration.yaml`. + +## {% linkable_title Configuring integrations %} + +Now that you are able to edit the configuration, it's time to set up some of your devices and services. Each service and device will have its own instructions on how to be integrated. Find your devices and services on the [components overview page](/components/). + +

YAML can be a little daunting at first. A lot is possible! [Here is some more info.](/docs/configuration/devices/)

### [Next step: Automate Home Assistant »](/getting-started/automation/) diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index 6c15f7caac3..79d410fb25f 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -9,30 +9,39 @@ sharing: true footer: true --- -First you will need to install Home Assistant before we can get started: +The goal of this getting started guide is to install Hass.io on a Raspberry Pi 3. Hass.io is our own all in one solution that turns your Raspberry PI into the utlimate home automation hub. -We have developed **Hass.io** to turn your device into a dedicated Home Assistant hub controlled by a nice webinterface. -For Raspberry Pi and Intel NUC we offer configured images. Flash the image, setup WiFi (if required) and everything else can be done inside the Hass.io webinterface. Great, isn't it? +Follow this guide if you want to easily get started with Home Assistant or if you have none or little Linux experience. For advanced users, check our [alternative installation methods](/docs/installation/). -Also Home Assistant runs on any other device that supports **Python 3**. -
- -
- -
-
Install Home Assistant using Hass.io
- - -
- -
-
Install Home Assistant on your computer
- -
-
+### {% linkable_title Hardware requirements %} -For alternative installation methods, please take a look at the [installation documentation](/docs/installation/). +We will need a few things to get started with installing Home Assistant. Links below are linking to Amazon US. If you're not in the US, you should be able to find these items in web stores in your country. -If you run into any issues, please see [the troubleshooting page](/docs/installation/troubleshooting/) or [communication channels](/help/). It contains solutions to many commonly encountered issues. + - [Raspberry Pi 3 model B](http://a.co/gEfMqL4) + [Power Supply](http://a.co/cgKUgkt) (atleast 2.5A) + - [Micro SD Card](http://a.co/gslOydD). Get one that is Class 10 as they are more reliable. Size 32GB or bigger recommended. + - SD Card reader. Part of most laptops. Also available as [standalone USB sticks](http://a.co/5FCyb0N) (brand doesn't matter, just pick cheapest) + - Ethernet cable (optional, Hass.io can work with WiFi too) + +### {% linkable_title Software requirements %} + + - Download [Hass.io image for Raspberry Pi 3][pi3] + - Download [Etcher] to write the image to an SD card + - Text Editor like [Visual Studio Code](https://code.visualstudio.com/) + +[Etcher]: https://etcher.io/ +[pi3]: https://github.com/home-assistant/hassio-build/releases/download/1.1/resinos-hassio-1.1-raspberrypi3.img.bz2 + +### Installing Hass.io + + 1. Put the SD card in your SD card reader, + 2. Open Etcher, select the Hass.io image and flash it to the SD card. + 3. WiFi setup only: open the file `system-connections/resin-sample` with a text editor. Change `ssid` to be your network name and `psk` to be your password. + 4. Unmount the SD card and remove it from your SD card reader. + 5. Insert the SD card into your Raspberry Pi 3. If you are going to use an Ethernet cable to supply Internet, connect that too. + 6. Connect your Raspberry Pi to the power supply so it turns on. + 7. The Raspberry Pi will now boot up, connect to the Internet and download the latest version of Home Assistant. This will take about 20 minutes. + 8. Home Assistant will be available at [http://hassio.local:8123][local]. + +[local]: http://hassio.local:8123 ### [Next step: Configuring Home Assistant »](/getting-started/configuration/) From cfeb8fac3da37e05736c4818d27cbe86a0f1ece6 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 16 Dec 2017 15:07:24 +0100 Subject: [PATCH 08/10] Add 'force_update' (#4221) --- source/_components/sensor.mqtt.markdown | 42 ++++++++++++++++++++----- 1 file changed, 34 insertions(+), 8 deletions(-) diff --git a/source/_components/sensor.mqtt.markdown b/source/_components/sensor.mqtt.markdown index ca8be055d12..0fb3ab1175f 100644 --- a/source/_components/sensor.mqtt.markdown +++ b/source/_components/sensor.mqtt.markdown @@ -25,14 +25,40 @@ sensor: state_topic: "home/bedroom/temperature" ``` -Configuration variables: - -- **state_topic** (*Required*): The MQTT topic subscribed to receive sensor values. -- **name** (*Optional*): The name of the sensor. Default is 'MQTT Sensor'. -- **qos** (*Optional*): The maximum QoS level of the state topic. Default is 0. -- **unit_of_measurement** (*Optional*): Defines the units of measurement of the sensor, if any. -- **expire_after** (*Optional*): Defines the number of seconds after the value expires if it's not updated. Default is 0 (=never expire). -- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload. +{% configuration %} +state_topic: + description: The MQTT topic subscribed to receive sensor values. + required: true + type: string +name: + description: Name of the MQTT sensor. + required: false + type: string + default: MQTT Sensor +qos: + description: The maximum QoS level of the state topic. + required: false + type: int + default: 0 +unit_of_measurement: + description: Defines the units of measurement of the sensor, if any. + required: false + type: string +expire_after: + description: Defines the number of seconds after the value expires if it's not updated. + required: false + type: int + default: 0 +value_template: + description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the value." + required: false + type: template +force_update: + description: Sends update events even if the value hasn't changed. Useful if you want to have meaningful value graphs in history. + reqired: false + type: boolean + default: False +{% endconfiguration %} ## {% linkable_title Examples %} From de6ecd1d11eac742fe72ad84f8672ae941ca21a7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Przemek=20Wi=C4=99ch?= Date: Sat, 16 Dec 2017 19:04:04 +0100 Subject: [PATCH 09/10] Updated documentation about running local development instance. (#4205) * Updated documentation about running local development instance. * Make it venv only --- .../developers/development_environment.markdown | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/source/developers/development_environment.markdown b/source/developers/development_environment.markdown index d6779d701e6..d33521d5237 100644 --- a/source/developers/development_environment.markdown +++ b/source/developers/development_environment.markdown @@ -85,21 +85,23 @@ $ git remote add upstream https://github.com/home-assistant/home-assistant.git ### {% linkable_title Setting up virtual environment %} -If you plan on providing isolation to your environment using [`venv`](https://docs.python.org/3.4/library/venv.html). Within the `home-assistant` directory, create and activate your virtual environment. +To isolate your environment from the rest of the system, set up a [`venv`](https://docs.python.org/3.4/library/venv.html). Within the `home-assistant` directory, create and activate your virtual environment. ```bash -$ python3 -m venv venv -$ source venv/bin/activate +$ python3 -m venv . +$ source bin/activate ``` - -### {% linkable_title Setup and Run %} +Install the requirements with a provided script named `setup`. ```bash -$ cd home-assistant $ script/setup ``` -* Run `hass` to invoke your local installation. +Invoke your installation. + +```bash +$ hass +``` ### {% linkable_title Logging %} From 78573e962448cccd1a03822ee0362055974fd7e1 Mon Sep 17 00:00:00 2001 From: Jenya Y Date: Sun, 17 Dec 2017 11:29:34 +0200 Subject: [PATCH 10/10] Typo (#4224) --- source/_docs/installation/virtualenv.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/installation/virtualenv.markdown b/source/_docs/installation/virtualenv.markdown index 234ea989460..a1b4c25c876 100644 --- a/source/_docs/installation/virtualenv.markdown +++ b/source/_docs/installation/virtualenv.markdown @@ -10,7 +10,7 @@ footer: true redirect_from: /getting-started/installation-virtualenv/ --- -If you alreacy have Python 3.5 or later installed, you can easily give Home Assistant a spin. +If you already have Python 3.5 or later installed, you can easily give Home Assistant a spin. It's recommended when installing Python packages that you use a virtual environment. This will make sure that your Python installation and Home Assistant installation won't impact one another.