Site updated at 2016-09-29 04:44:35 UTC

components/camera.ffmpeg/index.html

@@ -91,10 +91,6 @@
 
   <p>The <code class="highlighter-rouge">ffmpeg</code> platform allows you to use every video feed with <a href="http://www.ffmpeg.org/">FFmpeg</a> 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.</p>
 
-<p class="note">
-You need a <code class="highlighter-rouge">ffmpeg</code> 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 <a href="http://www.ffmpeg.org/">FFmpeg</a> website.
-</p>
-
 <p>To enable your FFmpeg feed in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
 
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
@@ -102,7 +98,6 @@ You need a <code class="highlighter-rouge">ffmpeg</code> binary in your system p
   <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">ffmpeg</span>
     <span class="s">input</span><span class="pi">:</span> <span class="s">FFMPEG_SUPPORTED_INPUT</span>
     <span class="s">name</span><span class="pi">:</span> <span class="s">FFmpeg</span>
-    <span class="s">ffmpeg_bin</span><span class="pi">:</span> <span class="s">/usr/bin/ffmpeg</span>
     <span class="s">extra_arguments</span><span class="pi">:</span> <span class="s">-q:v 2</span>
 </code></pre>
 </div>
@@ -112,7 +107,6 @@ You need a <code class="highlighter-rouge">ffmpeg</code> binary in your system p
 <ul>
   <li><strong>input</strong> (<em>Required</em>): A ffmpeg compatible input file, stream or feed.</li>
   <li><strong>name</strong> (<em>Optional</em>): This parameter allows you to override the name of your camera.</li>
-  <li><strong>ffmpeg_bin</strong> (<em>Optional</em>): Default ‘ffmpeg’.</li>
   <li><strong>extra_arguments</strong> (<em>Optional</em>): Extra option they will pass to <code class="highlighter-rouge">ffmpeg</code>. i.e. image quality or video filter options.</li>
 </ul>
 
@@ -120,23 +114,7 @@ You need a <code class="highlighter-rouge">ffmpeg</code> binary in your system p
 
 <p>You can control the <code class="highlighter-rouge">image quality</code> with <a href="https://www.ffmpeg.org/ffmpeg-codecs.html#jpeg2000"><code class="highlighter-rouge">extra_arguments</code></a> <code class="highlighter-rouge">-q:v 2-32</code> or with lossless option <code class="highlighter-rouge">-pred 1</code>.</p>
 
-<h3><a class="title-link" name="troubleshooting" href="#troubleshooting"></a> Troubleshooting</h3>
-
-<p>In most of case, <code class="highlighter-rouge">ffmpeg</code> autodetect all needed options to read a video/audio stream or file. But it is possible in rare cases that’s needed to set a option to help <code class="highlighter-rouge">ffmpeg</code>. Per default <code class="highlighter-rouge">ffmpeg</code> use 5 seconds to detect all options or abort.</p>
-
-<p>First check, if your stream playable by <code class="highlighter-rouge">ffmpeg</code> with (use option <code class="highlighter-rouge">-an</code> or <code class="highlighter-rouge">-vn</code> to disable video or audio stream):</p>
-
-<div class="highlighter-rouge"><pre class="highlight"><code>$ ffmpeg -i INPUT -an -f null -
-</code></pre>
-</div>
-
-<p>Now you can see what going wrong. Following list could be help to solve your trouble:</p>
-
-<ul>
-  <li><code class="highlighter-rouge">[rtsp @ ...] UDP timeout, retrying with TCP</code>: You need to set RTSP transport in the configuration with: <code class="highlighter-rouge">input: -rtsp_transport tcp -i INPUT</code></li>
-  <li><code class="highlighter-rouge">[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size</code>: FFmpeg need more data or time for autodetect. You can set the <code class="highlighter-rouge">analyzeduration</code> and/or <code class="highlighter-rouge">probesize</code> option, play with this value. If you know the needed value you can set it  with: <code class="highlighter-rouge">input: -analyzeduration xy -probesize xy -i INPUT</code>. More information about that can be found on <a href="https://www.ffmpeg.org/ffmpeg-formats.html#Description">FFmpeg</a>.</li>
-</ul>
-
+<p>If you are running into trouble with this sensor, please refer to this <a href="/components/ffmpeg/#troubleshooting">Troubleshooting section</a>.</p>
 
 
 </article>
@@ -164,6 +142,9 @@ You need a <code class="highlighter-rouge">ffmpeg</code> binary in your system p
           <div class='section'>
           <h1 class='title delta'>Related components</h1>
           <ul class='divided'>
+        <li><a href='/components/ffmpeg/'>
+          FFmpeg
+        </a></li>
         <li><a href='/components/binary_sensor.ffmpeg/'>
           FFmpeg Binary Sensor
         </a></li>