diff --git a/components/binary_sensor.ffmpeg/index.html b/components/binary_sensor.ffmpeg/index.html
index 29efcf2638..b257af5121 100644
--- a/components/binary_sensor.ffmpeg/index.html
+++ b/components/binary_sensor.ffmpeg/index.html
@@ -89,10 +89,10 @@
- The ffmpeg
platform allows you to use every video or audio feed with FFmpeg for various sensors in Home Assistant. Available are: noise, motion. If the ffmpeg
process is brocken, the sensor going to unavailable. It exists a service to restart a instance with binary_sensor.ffmpeg_restart.
+ The ffmpeg
platform allows you to use every video or audio feed with FFmpeg for various sensors in Home Assistant. Available are: noise, motion. If the ffmpeg
process is broken, the sensor will be unavailable. To restart the instance, use the service binary_sensor.ffmpeg_restart.
-You need a ffmpeg
binary in your system path. On Debain 8 you can install it from backports. If you want Hardware support on a Raspberry Pi you need to build it from sourceby ourself. Windows binary are avilable on FFmpeg homepage.
+You need the ffmpeg
binary in your system path. On Debain 8 you can install it from backports. If you want Hardware support on a Raspberry Pi you need to build it from source. Windows binary are avilable on FFmpeg homepage.
Noise
@@ -123,7 +123,7 @@ You need a ffmpeg
binary in your system p
duration (Optional): Default 1 seconds. How long need the noise over the peak to trigger the state.
reset (Optional): Defaults to 20 seconds. The time to reset the state after none new noise is over the peak.
extra_arguments (Optional): Extra option they will pass to ffmpeg
, like audio frequence filtering.
- output (Optional): Allow you to send the audio output of this sensor to a icecast server or other ffmpeg supported output, eg. to stream with sonos after state is trigger.
+ output (Optional): Allow you to send the audio output of this sensor to an icecast server or other ffmpeg supported output, eg. to stream with sonos after state is triggered.
For playing with values:
@@ -134,7 +134,7 @@ You need a ffmpeg
binary in your system p
Motion
-FFmpeg don’t have a motion detection filter so it use a scene filter to detect a new scene/motion. In fact you can set how big a object or size of image they need change to detect a motion. The option ‘changes’ is the percent value of change between frames. You can add a denoise filter to video if you want a realy small value for ‘changes’.
+FFmpeg doesn’t have a motion detection filter, so it uses a scene filter to detect a new scene/motion. In fact, you can set how big of an object or the size of an image that needs to change in order to detect motion. The option ‘changes’ is the percent value of change between frames. You can add a denoise filter to the video if you want a really small value for ‘changes’.
To enable your FFmpeg with motion detection in your installation, add the following to your configuration.yaml
file:
@@ -157,14 +157,14 @@ You need a ffmpeg
binary in your system p
Configuration variables:
- - input (Required): A ffmpeg compatible input file, stream or feed.
+ - input (Required): A ffmpeg compatible input file, stream, or feed.
- tool (Required): Is fix set to
motion
.
- name (Optional): This parameter allows you to override the name of your camera.
- ffmpeg_bin (Optional): Default
ffmpeg
.
- - changes (Optional): Default 10 percent. A lower value is more sensitive. I use 4 / 3.5 on my cameras. It describe how much of two frames need to change to detect it as motion. See on descripton.
- - reset (Optional): Default 20 seconds. The time to reset the state after none new motion is detect.
- - repeat (Optional): Default 0 repeats (deactivate). How many motion need to detect in repeat_time to trigger a motion.
- - repeat_time (Optional): Default 0 seconds (deactivate). The time to repeats before it trigger a motion.
+ - changes (Optional): Default 10 percent. A lower value is more sensitive. I use 4 / 3.5 on my cameras. It describes how much needs to change between two frames to detect it as motion. See on descripton.
+ - reset (Optional): Default 20 seconds. The time to reset the state after no new motion is detected.
+ - repeat (Optional): Default 0 repeats (deactivate). How many events need to be detected in repeat_time in order to trigger a motion.
+ - repeat_time (Optional): Default 0 seconds (deactivate). The span of time repeat events need to occur in before triggering a motion.
- extra_arguments (Optional): Extra option they will pass to ffmpeg. i.e. video denoise filtering.
diff --git a/components/camera.ffmpeg/index.html b/components/camera.ffmpeg/index.html
index eb8ef68359..406a9825a9 100644
--- a/components/camera.ffmpeg/index.html
+++ b/components/camera.ffmpeg/index.html
@@ -89,7 +89,7 @@
- The ffmpeg
platform allows you to use every video feed with FFmpeg as camera in Home Assistant. The input for ffmpeg need to support that could have multiple connection to source (input). For every user in UI and all 10 seconds (snapshot image) it make a new connection/reading to source. Normally that should never be a trouble only in strange selfmade constructs can be make mistakes.
+ The ffmpeg
platform allows you to use every video feed with FFmpeg as camera in Home Assistant. The input for ffmpeg need to support that could have multiple connection to source (input) in same time. For every user in UI and all 10 seconds (snapshot image) it make a new connection/reading to source. Normally that should never be a trouble only in strange selfmade constructs can be make mistakes.
You need a ffmpeg
binary in your system path. On Debain 8 you can install it from backports. If you want Hardware support on a Raspberry Pi you need tobuild from source by yourself. Windows binary are avilable on the FFmpeg website.
diff --git a/sitemap.xml b/sitemap.xml
index 47c5cc55ef..b2bb55c582 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1980,62 +1980,62 @@
https://home-assistant.io/demo/frontend.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/index.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00
https://home-assistant.io/static/mdi-demo.html
-2016-09-02T09:23:32+00:00
+2016-09-02T16:17:33+00:00