libcec must be installed for this component to work. Follow the installation instructions for your environment, provided at the link. libcec installs Python 3 bindings, by default as a system Python module. If you are running Home Assistant in a Python virtual environment, make sure it can access the system module, by either symlinking it or using the --system-site-packages flag.
ln -s /usr/local/lib/python3.4/dist-packages/cec <your venv>/lib/python3.4/site-packages
In the following example, a Pi Zero running Home Assistant is on a TV’s HDMI port 1. HDMI port 2 is attached to a AV receiver. Three devices are attached to the AV receiver on HDMI ports 1 through 3.
diff --git a/components/sensor.onewire/index.html b/components/sensor.onewire/index.html index 1e54c5fff2..f8af3747cf 100644 --- a/components/sensor.onewire/index.html +++ b/components/sensor.onewire/index.html @@ -111,6 +111,7 @@ platform: onewire names: some_id: your name + mount_dir: "/mnt/1wire" @@ -119,6 +120,7 @@The configuration.yaml file a plain-text file thus it is readable for everyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. This separation can also help you to keep easier track of your passwords and API keys (as they are all stored at one place and no longer spread across the configuration.yaml file) if you don’t want to split up your configuration.
The configuration.yaml file a plain-text file thus it is readable for everyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. This separation can also help you to keep easier track of your passwords and API keys (as they are all stored at one place and no longer spread across the configuration.yaml file) if you don’t want to split up your configuration.
The workflow for the outsourcing in the secrets.yaml are very similar to the splitting of the configuration. Create a secrets.yaml file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it’s ~/.homeassistant and on Windows it’s %APPDATA%/.homeassistant).
The workflow for the outsourcing in the secrets.yaml are very similar to the splitting of the configuration. Create a secrets.yaml file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it’s ~/.homeassistant and on Windows it’s %APPDATA%/.homeassistant).
The entries for password and API keys in the configuration.yaml file usally looks like the example below.