diff --git a/atom.xml b/atom.xml index 2f98806cf1..5342779231 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@
As an alternative to the router-based device tracking, it is possible to directly scan the network for devices by using Nmap. The IP addresses to scan can be specified in any format that Nmap understands, including the network-prefix notation (192.168.1.1/24
) and the range notation (192.168.1.1-255
).
If you’re on Debian or Ubuntu, you might have to install the packages for arp
and nmap
. Do so by running $ sudo apt-get install net-tools nmap
. On a Fedora host run $ sudo dnf -y install nmap
.
+If you are using Hass.io then just move forward to the configuration as all requirements are already fullfilled. +
Host detection is done via Nmap’s “fast scan” (-F
) of the most frequently used 100 ports, with a host timeout of 5 seconds.
To use this device tracker in your installation, add the following to your configuration.yaml
file:
# Example configuration.yaml entry
diff --git a/components/ffmpeg/index.html b/components/ffmpeg/index.html
index 5626cda933..884d89fee8 100644
--- a/components/ffmpeg/index.html
+++ b/components/ffmpeg/index.html
@@ -74,10 +74,13 @@
- The FFmpeg component allows other Home Assistant components to process video and audio streams. This component supports all FFmpeg versions since 3.0.0; if you have a older version, please update.
+ The ffmpeg
component allows other Home Assistant components to process video and audio streams. This component supports all FFmpeg versions since 3.0.0; if you have a older version, please update.
You need the ffmpeg
binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from debian-backports. If you want hardware acceleration support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are available on the FFmpeg website.
+
+If you are using Hass.io then just move forward to the configuration as all requirements are already fullfilled.
+
To set it up, add the following information to your configuration.yaml
file:
ffmpeg:
diff --git a/components/hdmi_cec/index.html b/components/hdmi_cec/index.html
index 8b296c5837..71c2d12f06 100644
--- a/components/hdmi_cec/index.html
+++ b/components/hdmi_cec/index.html
@@ -74,12 +74,15 @@
- The HDMI CEC component provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entites for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as Soundbars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use cec-client
(part of the libcec
package) to listen to traffic on the CEC bus and discover the correct numbers.
+ The hdmi_cec
component provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entites for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as Soundbars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use cec-client
(part of the libcec
package) to listen to traffic on the CEC bus and discover the correct numbers.
CEC Setup
Adapter
The computer running Home Assistant must support CEC, and of course be connected via HDMI to a device also supporting CEC. You can purchase a USB CEC adapter to add support if necessary. Note that all Raspberry Pi models support CEC natively.
libcec
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.
+
+If you are using Hass.io then just move forward to the configuration as all requirements are already fullfilled.
+
Symlinking into virtual environment
Create a symlink to the cec
installation. Keep in mind different installation methods will result in different locations of cec.
$ ln -s /path/to/your/installation/of/cec /path/to/your/venv/lib/python3.4/site-packages
diff --git a/components/image_processing.opencv/index.html b/components/image_processing.opencv/index.html
index b4edd2bda3..c737d636a2 100644
--- a/components/image_processing.opencv/index.html
+++ b/components/image_processing.opencv/index.html
@@ -76,7 +76,6 @@
OpenCV is an open source computer vision image and video processing library.
Some pre-defined classifiers can be found here: https://github.com/opencv/opencv/tree/master/data
- Configuration
To setup OpenCV with Home Assistant, add the following section to your configuration.yaml
file:
# Example configuration.yaml entry
image_processing:
diff --git a/components/image_processing.seven_segments/index.html b/components/image_processing.seven_segments/index.html
index 35196d017b..71013c5064 100644
--- a/components/image_processing.seven_segments/index.html
+++ b/components/image_processing.seven_segments/index.html
@@ -75,6 +75,9 @@
The seven_segments
image processing platform allows you to read physical seven segments displays through Home Assistant. ssocr
is used to extract the value shown on the display which is observed by a camera. ssocr
need to be available on your system. Check the installation instruction for Fedora below or use $ sudo apt-get install ssocr
on a Debian-based system:
+
+If you are using Hass.io then just move forward to the configuration as all requirements are already fullfilled.
+
$ sudo dnf -y install imlib2-devel
$ git clone https://github.com/auerswal/ssocr.git
$ cd ssocr
diff --git a/components/tradfri/index.html b/components/tradfri/index.html
index 175ddf381b..bffd09d365 100644
--- a/components/tradfri/index.html
+++ b/components/tradfri/index.html
@@ -76,6 +76,9 @@
The tradfri
component supports for the IKEA Trådfri (Tradfri) gateway. The gateway can control lights connected to it and Home Assistant will automatically discover its presence on your network.
For this to work, you need to install a modified lib-coap library.
+
+If you are using Hass.io then just move forward to the configuration as all requirements are already fullfilled.
+
Linux:
$ sudo apt-get install libtool
$ sudo apt-get install autoconf
diff --git a/sitemap.xml b/sitemap.xml
index bd73868c37..3fca7c3bca 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -3823,62 +3823,62 @@
https://home-assistant.io/demo/frontend.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/index.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2017-08-06T00:40:49+00:00
+2017-08-06T09:51:51+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2017-08-06T00:40:50+00:00
+2017-08-06T09:51:52+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2017-08-06T00:40:50+00:00
+2017-08-06T09:51:52+00:00
https://home-assistant.io/static/mdi-demo.html
-2017-08-06T00:40:50+00:00
+2017-08-06T09:51:52+00:00