diff --git a/atom.xml b/atom.xml index bdcd985199..99a5cdb95d 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ @@ -18,7 +18,7 @@ 2017-02-03T23:00:00+00:00 https://home-assistant.io/blog/2017/02/03/babyphone - One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available in the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home-Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (e.g., Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

+ One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.

@@ -26,15 +26,16 @@

Setup

-

We need an IP-camera that can capture sound in the baby’s room. It is also possible to use a Raspberry Pi with a microphone and send the audio to our Home-Assistant with ffmpeg -f alsa -i hw:1,0 -vn -f rtp rtp://236.0.0.1:2000 over multicast. We can set input option on Home-Assistant side to rtp://236.0.0.1:2000 in same network.

+

We need an IP camera that can capture sound in the baby’s room. It is also possible to use a Raspberry Pi with a microphone and send the audio to Home Assistant with ffmpeg -f alsa -i hw:1,0 -vn -f rtp rtp://236.0.0.1:2000 over multicast. We can set the input option on the Home Assistant side to rtp://236.0.0.1:2000 in same network.

-

Next, we attach a ffmpeg noise binary sensor to our IP-camera. The sensor has an output option that allows us to send the output to icecast2 server for playing over speakers integrated with Home-Assistant (e.g., Sonos). We can use the binary sensor in our automation. You can ignore the icecast2 setup if you don’t want to play the audio after the noise sensor trigger.

+

Next, we attach a FFmpeg noise binary sensor to our IP camera. The sensor has an output option that allows us to send the output to an icecast2 server for playing over speakers integrated with Home Assistant (eg. Sonos). We can use the binary sensor in our automation. You can ignore the icecast2 setup if you don’t want to play the audio after the noise sensor trigger.

We change the platform name for binary sensor in 0.38 from ffmpeg to ffmpeg_noise. Also all service going to component and was rename from binary_sensor.ffmpeg_xy to ffmpeg.xy.

-

On Raspbian Jessie, you can setup ffmpeg and install a icecast2 server using:

+

On Raspbian Jessie, you can setup FFmpeg and install a icecast2 server using:

+
$ sudo echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list
 $ sudo apt-get update
 $ sudo apt-get -t jessie-backports install ffmpeg
@@ -43,6 +44,7 @@ We change the platform name for binary sensor in 0.38 from /etc/icecast2/icecast.xml:

+
<mount>
     <mount-name>/babyphone.mp3</mount-name>
     <stream-name>Babyphone</stream-name>
@@ -53,23 +55,23 @@ We change the platform name for binary sensor in 0.38 from duration option. The sensor should wait 60 seconds before restoring and it prevent us that a wine break will triggering a new alarm.

+

Now we can add the noise sensor to Home Assistant. We can lower the sensitivity of the sensor (so that you are not inundated with notifications for every cough of the baby) to 2 seconds using the duration option. The sensor should wait 60 seconds before restoring and it prevent us that a wine break will triggering a new alarm.

-

We can optimize the audio stream for human voice by using a highpass filter with 300Hz and a lowpass filter with 2500Hz. This filters out all non-human sounds such as background noise. We can even add a volume amplifier if the microphone volume is too low (you can remove it from extra_arguments). For icecast2 we convert the audio stream to mp3 with samplerate of 16000 (which is the minimum for Sonos speakers). We use peak to set the threshold for noise detection, where 0 dB is very loud and -100 dB is low.

+

We can optimize the audio stream for human voice by using a highpass filter with 300 Hz and a lowpass filter with 2500 Hz. This filters out all non-human sounds such as background noise. We can even add a volume amplifier if the microphone volume is too low (you can remove it from extra_arguments). For icecast2 we convert the audio stream to mp3 with samplerate of 16000 (which is the minimum for Sonos speakers). We use peak to set the threshold for noise detection, where 0 dB is very loud and -100 dB is low.

binary_sensor:
- - platform: ffmpeg_noise
-   input: rtsp://user:pw@my_input/video
-   extra_arguments: -filter:a highpass=f=300,lowpass=f=2500,volume=volume=2 -codec:a libmp3lame -ar 16000
-   output: -f mp3 icecast://stream_user:stream_pw@127.0.0.1:8000/babyphone.mp3
-   initial_state: false
-   duration: 2
-   reset: 60
-   peak: -32
+  - platform: ffmpeg_noise
+    input: rtsp://user:pw@my_input/video
+    extra_arguments: -filter:a highpass=f=300,lowpass=f=2500,volume=volume=2 -codec:a libmp3lame -ar 16000
+    output: -f mp3 icecast://stream_user:stream_pw@127.0.0.1:8000/babyphone.mp3
+    initial_state: false
+    duration: 2
+    reset: 60
+    peak: -32
 
-

We use the option initial_state to prevent the ffmpeg process from starting with Home-Assistant and only start it when needed. We use an input_boolean to control the state of ffmpeg services using the following automation.

+

We use the option initial_state to prevent the FFmpeg process from starting with Home Assistant and only start it when needed. We use an input_boolean to control the state of FFmpeg services using the following automation.

input_boolean:
   babyphone:
diff --git a/blog/2017/02/03/babyphone/index.html b/blog/2017/02/03/babyphone/index.html
index d367532525..bca70aeb70 100644
--- a/blog/2017/02/03/babyphone/index.html
+++ b/blog/2017/02/03/babyphone/index.html
@@ -94,8 +94,6 @@
     
    -
  • Babyphone
  • -
  • How-To
  • @@ -111,7 +109,7 @@ -

    One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available in the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home-Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (e.g., Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

    +

    One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

    Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.

    @@ -119,15 +117,16 @@

    Setup

    -

    We need an IP-camera that can capture sound in the baby’s room. It is also possible to use a Raspberry Pi with a microphone and send the audio to our Home-Assistant with ffmpeg -f alsa -i hw:1,0 -vn -f rtp rtp://236.0.0.1:2000 over multicast. We can set input option on Home-Assistant side to rtp://236.0.0.1:2000 in same network.

    +

    We need an IP camera that can capture sound in the baby’s room. It is also possible to use a Raspberry Pi with a microphone and send the audio to Home Assistant with ffmpeg -f alsa -i hw:1,0 -vn -f rtp rtp://236.0.0.1:2000 over multicast. We can set the input option on the Home Assistant side to rtp://236.0.0.1:2000 in same network.

    -

    Next, we attach a ffmpeg noise binary sensor to our IP-camera. The sensor has an output option that allows us to send the output to icecast2 server for playing over speakers integrated with Home-Assistant (e.g., Sonos). We can use the binary sensor in our automation. You can ignore the icecast2 setup if you don’t want to play the audio after the noise sensor trigger.

    +

    Next, we attach a FFmpeg noise binary sensor to our IP camera. The sensor has an output option that allows us to send the output to an icecast2 server for playing over speakers integrated with Home Assistant (eg. Sonos). We can use the binary sensor in our automation. You can ignore the icecast2 setup if you don’t want to play the audio after the noise sensor trigger.

    We change the platform name for binary sensor in 0.38 from ffmpeg to ffmpeg_noise. Also all service going to component and was rename from binary_sensor.ffmpeg_xy to ffmpeg.xy.

    -

    On Raspbian Jessie, you can setup ffmpeg and install a icecast2 server using:

    +

    On Raspbian Jessie, you can setup FFmpeg and install a icecast2 server using:

    +
    $ sudo echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list
     $ sudo apt-get update
     $ sudo apt-get -t jessie-backports install ffmpeg
    @@ -136,6 +135,7 @@ We change the platform name for binary sensor in 0.38 from /etc/icecast2/icecast.xml:

    +
    <mount>
         <mount-name>/babyphone.mp3</mount-name>
         <stream-name>Babyphone</stream-name>
    @@ -146,23 +146,23 @@ We change the platform name for binary sensor in 0.38 from duration option. The sensor should wait 60 seconds before restoring and it prevent us that a wine break will triggering a new alarm.

    +

    Now we can add the noise sensor to Home Assistant. We can lower the sensitivity of the sensor (so that you are not inundated with notifications for every cough of the baby) to 2 seconds using the duration option. The sensor should wait 60 seconds before restoring and it prevent us that a wine break will triggering a new alarm.

    -

    We can optimize the audio stream for human voice by using a highpass filter with 300Hz and a lowpass filter with 2500Hz. This filters out all non-human sounds such as background noise. We can even add a volume amplifier if the microphone volume is too low (you can remove it from extra_arguments). For icecast2 we convert the audio stream to mp3 with samplerate of 16000 (which is the minimum for Sonos speakers). We use peak to set the threshold for noise detection, where 0 dB is very loud and -100 dB is low.

    +

    We can optimize the audio stream for human voice by using a highpass filter with 300 Hz and a lowpass filter with 2500 Hz. This filters out all non-human sounds such as background noise. We can even add a volume amplifier if the microphone volume is too low (you can remove it from extra_arguments). For icecast2 we convert the audio stream to mp3 with samplerate of 16000 (which is the minimum for Sonos speakers). We use peak to set the threshold for noise detection, where 0 dB is very loud and -100 dB is low.

    binary_sensor:
    - - platform: ffmpeg_noise
    -   input: rtsp://user:pw@my_input/video
    -   extra_arguments: -filter:a highpass=f=300,lowpass=f=2500,volume=volume=2 -codec:a libmp3lame -ar 16000
    -   output: -f mp3 icecast://stream_user:stream_pw@127.0.0.1:8000/babyphone.mp3
    -   initial_state: false
    -   duration: 2
    -   reset: 60
    -   peak: -32
    +  - platform: ffmpeg_noise
    +    input: rtsp://user:pw@my_input/video
    +    extra_arguments: -filter:a highpass=f=300,lowpass=f=2500,volume=volume=2 -codec:a libmp3lame -ar 16000
    +    output: -f mp3 icecast://stream_user:stream_pw@127.0.0.1:8000/babyphone.mp3
    +    initial_state: false
    +    duration: 2
    +    reset: 60
    +    peak: -32
     
    -

    We use the option initial_state to prevent the ffmpeg process from starting with Home-Assistant and only start it when needed. We use an input_boolean to control the state of ffmpeg services using the following automation.

    +

    We use the option initial_state to prevent the FFmpeg process from starting with Home Assistant and only start it when needed. We use an input_boolean to control the state of FFmpeg services using the following automation.

    input_boolean:
       babyphone:
    diff --git a/blog/archives/index.html b/blog/archives/index.html
    index b1f6f34292..1791beccdb 100644
    --- a/blog/archives/index.html
    +++ b/blog/archives/index.html
    @@ -3336,8 +3336,6 @@
         
      -
    • Babyphone
    • -
    • How-To
    • diff --git a/blog/categories/babyphone/atom.xml b/blog/categories/babyphone/atom.xml deleted file mode 100644 index 84b29c62aa..0000000000 --- a/blog/categories/babyphone/atom.xml +++ /dev/null @@ -1,156 +0,0 @@ - - - - <![CDATA[Category: Babyphone | Home Assistant]]> - - - 2017-02-04T09:07:32+00:00 - https://home-assistant.io/ - - - - - Octopress - - - - <![CDATA[Smart Baby Monitor]]> - - 2017-02-03T23:00:00+00:00 - https://home-assistant.io/blog/2017/02/03/babyphone - - -### Setup - -We need an IP-camera that can capture sound in the baby's room. It is also possible to use a Raspberry Pi with a microphone and send the audio to our Home-Assistant with `ffmpeg -f alsa -i hw:1,0 -vn -f rtp rtp://236.0.0.1:2000` over multicast. We can set `input` option on Home-Assistant side to `rtp://236.0.0.1:2000` in same network. - -Next, we attach a ffmpeg noise binary sensor to our IP-camera. The sensor has an output `option` that allows us to send the output to icecast2 server for playing over speakers integrated with Home-Assistant (e.g., Sonos). We can use the binary sensor in our automation. You can ignore the icecast2 setup if you don't want to play the audio after the noise sensor trigger. - -

      -We change the platform name for binary sensor in 0.38 from `ffmpeg` to `ffmpeg_noise`. Also all service going to component and was rename from `binary_sensor.ffmpeg_xy` to `ffmpeg.xy`. -

      - -On Raspbian Jessie, you can setup [ffmpeg](/components/ffmpeg) and install a [icecast2](http://icecast.org/) server using: -```bash -$ sudo echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list -$ sudo apt-get update -$ sudo apt-get -t jessie-backports install ffmpeg -$ sudo apt-get install icecast2 -``` - -We setup a icecast mount point for our babyphone and update `/etc/icecast2/icecast.xml`: -``` - - /babyphone.mp3 - Babyphone - - stream_user - stream_pw - -``` - -Now we can add the noise sensor to Home-Assistant. We can lower the sensitivity of the sensor (so that you are not inundated with notifications for every cough of the baby) to 2 seconds using the `duration` option. The sensor should wait 60 seconds before restoring and it prevent us that a wine break will triggering a new alarm. - -We can optimize the audio stream for human voice by using a highpass filter with 300Hz and a lowpass filter with 2500Hz. This filters out all non-human sounds such as background noise. We can even add a volume amplifier if the microphone volume is too low (you can remove it from `extra_arguments`). For icecast2 we convert the audio stream to mp3 with samplerate of 16000 (which is the minimum for Sonos speakers). We use `peak` to set the threshold for noise detection, where 0 dB is very loud and -100 dB is low. - -```yaml -binary_sensor: - - platform: ffmpeg_noise - input: rtsp://user:pw@my_input/video - extra_arguments: -filter:a highpass=f=300,lowpass=f=2500,volume=volume=2 -codec:a libmp3lame -ar 16000 - output: -f mp3 icecast://stream_user:stream_pw@127.0.0.1:8000/babyphone.mp3 - initial_state: false - duration: 2 - reset: 60 - peak: -32 -``` - -We use the option `initial_state` to prevent the ffmpeg process from starting with Home-Assistant and only start it when needed. We use an `input_boolean` to control the state of ffmpeg services using the following automation. - -```yaml -input_boolean: - babyphone: - name: babyphone - initial: off - -automation: - - alias: 'Babyphone on' - trigger: - platform: state - entity_id: input_boolean.babyphone - from: 'off' - to: 'on' - action: - service: ffmpeg.start - entity_id: binary_sensor.ffmpeg_noise - - - alias: 'Babyphone off' - trigger: - platform: state - entity_id: input_boolean.babyphone - from: 'on' - to: 'off' - action: - service: ffmpeg.stop - entity_id: binary_sensor.ffmpeg_noise -``` - -### Trigger a alarm - -Now we can make a lot stuff. Here is a simple example of an automation what should be possible with Sonos speakers. - -```yaml -automation: - - alias: 'Babyphone alarm on' - trigger: - platform: state - entity_id: binary_sensor.ffmpeg_noise - from: 'off' - to: 'on' - action: - - service: media_player.sonos_snapshot - entity_id: media_player.bedroom - - service: media_player.sonos_unjoin - entity_id: media_player.bedroom - - service: media_player.volume_set - entity_id: media_player.bedroom - data: - volume_level: 0.4 - - service: media_player.play_media - entity_id: media_player.bedroom - data: - media_content_type: 'music' - media_content_id: http://my_ip_icecast:8000/babyphone.mp3 - - service: light.turn_on: - entity_id: - - light.floor - - light.bedroom - data: - brightness: 150 - - - alias: 'Babyphone alarm off' - trigger: - platform: state - entity_id: binary_sensor.ffmpeg_noise - from: 'on' - to: 'off' - action: - - service: media_player.sonos_restore - entity_id: media_player.bedroom - - service: light.turn_off: - entity_id: - - light.floor - - light.bedroom -``` - -### Thanks - -Special thanks to [arsaboo](https://github.com/arsaboo) for assistance in writing this blogpost. -]]>
      -
      - -
      diff --git a/blog/categories/babyphone/index.html b/blog/categories/babyphone/index.html deleted file mode 100644 index b0b29f5f58..0000000000 --- a/blog/categories/babyphone/index.html +++ /dev/null @@ -1,271 +0,0 @@ - - - - - - - - - - Category: Babyphone - Home Assistant - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      - -
      - - - -
      -
      - -
      - - - - - -
      - - - - -
      -
      - - - - - - - \ No newline at end of file diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 1033994ab5..3c25123f0f 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: community | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index 10afde9001..e9b60fb1e7 100644 --- a/blog/categories/device-tracking/atom.xml +++ b/blog/categories/device-tracking/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Device-Tracking | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 6d2a67e234..b46157db1e 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index cf8e1e662e..9c8ae9e2bd 100644 --- a/blog/categories/how-to/atom.xml +++ b/blog/categories/how-to/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: How-To | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ @@ -18,7 +18,7 @@ 2017-02-03T23:00:00+00:00 https://home-assistant.io/blog/2017/02/03/babyphone - Setup -We need an IP-camera that can capture sound in the baby's room. It is also possible to use a Raspberry Pi with a microphone and send the audio to our Home-Assistant with `ffmpeg -f alsa -i hw:1,0 -vn -f rtp rtp://236.0.0.1:2000` over multicast. We can set `input` option on Home-Assistant side to `rtp://236.0.0.1:2000` in same network. +We need an IP camera that can capture sound in the baby's room. It is also possible to use a Raspberry Pi with a microphone and send the audio to Home Assistant with `ffmpeg -f alsa -i hw:1,0 -vn -f rtp rtp://236.0.0.1:2000` over multicast. We can set the `input` option on the Home Assistant side to `rtp://236.0.0.1:2000` in same network. -Next, we attach a ffmpeg noise binary sensor to our IP-camera. The sensor has an output `option` that allows us to send the output to icecast2 server for playing over speakers integrated with Home-Assistant (e.g., Sonos). We can use the binary sensor in our automation. You can ignore the icecast2 setup if you don't want to play the audio after the noise sensor trigger. +Next, we attach a FFmpeg noise binary sensor to our IP camera. The sensor has an output `option` that allows us to send the output to an [icecast2](http://icecast.org/) server for playing over speakers integrated with Home Assistant (eg. Sonos). We can use the binary sensor in our automation. You can ignore the icecast2 setup if you don't want to play the audio after the noise sensor trigger.

      We change the platform name for binary sensor in 0.38 from `ffmpeg` to `ffmpeg_noise`. Also all service going to component and was rename from `binary_sensor.ffmpeg_xy` to `ffmpeg.xy`.

      -On Raspbian Jessie, you can setup [ffmpeg](/components/ffmpeg) and install a [icecast2](http://icecast.org/) server using: +On Raspbian Jessie, you can setup [FFmpeg](/components/ffmpeg) and install a [icecast2](http://icecast.org/) server using: + ```bash $ sudo echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list $ sudo apt-get update @@ -43,6 +44,7 @@ $ sudo apt-get install icecast2 ``` We setup a icecast mount point for our babyphone and update `/etc/icecast2/icecast.xml`: + ``` /babyphone.mp3 @@ -53,23 +55,23 @@ We setup a icecast mount point for our babyphone and update `/etc/icecast2/iceca ``` -Now we can add the noise sensor to Home-Assistant. We can lower the sensitivity of the sensor (so that you are not inundated with notifications for every cough of the baby) to 2 seconds using the `duration` option. The sensor should wait 60 seconds before restoring and it prevent us that a wine break will triggering a new alarm. +Now we can add the noise sensor to Home Assistant. We can lower the sensitivity of the sensor (so that you are not inundated with notifications for every cough of the baby) to 2 seconds using the `duration` option. The sensor should wait 60 seconds before restoring and it prevent us that a wine break will triggering a new alarm. -We can optimize the audio stream for human voice by using a highpass filter with 300Hz and a lowpass filter with 2500Hz. This filters out all non-human sounds such as background noise. We can even add a volume amplifier if the microphone volume is too low (you can remove it from `extra_arguments`). For icecast2 we convert the audio stream to mp3 with samplerate of 16000 (which is the minimum for Sonos speakers). We use `peak` to set the threshold for noise detection, where 0 dB is very loud and -100 dB is low. +We can optimize the audio stream for human voice by using a highpass filter with 300 Hz and a lowpass filter with 2500 Hz. This filters out all non-human sounds such as background noise. We can even add a volume amplifier if the microphone volume is too low (you can remove it from `extra_arguments`). For icecast2 we convert the audio stream to mp3 with samplerate of 16000 (which is the minimum for Sonos speakers). We use `peak` to set the threshold for noise detection, where 0 dB is very loud and -100 dB is low. ```yaml binary_sensor: - - platform: ffmpeg_noise - input: rtsp://user:pw@my_input/video - extra_arguments: -filter:a highpass=f=300,lowpass=f=2500,volume=volume=2 -codec:a libmp3lame -ar 16000 - output: -f mp3 icecast://stream_user:stream_pw@127.0.0.1:8000/babyphone.mp3 - initial_state: false - duration: 2 - reset: 60 - peak: -32 + - platform: ffmpeg_noise + input: rtsp://user:pw@my_input/video + extra_arguments: -filter:a highpass=f=300,lowpass=f=2500,volume=volume=2 -codec:a libmp3lame -ar 16000 + output: -f mp3 icecast://stream_user:stream_pw@127.0.0.1:8000/babyphone.mp3 + initial_state: false + duration: 2 + reset: 60 + peak: -32 ``` -We use the option `initial_state` to prevent the ffmpeg process from starting with Home-Assistant and only start it when needed. We use an `input_boolean` to control the state of ffmpeg services using the following automation. +We use the option `initial_state` to prevent the FFmpeg process from starting with Home Assistant and only start it when needed. We use an `input_boolean` to control the state of FFmpeg services using the following automation. ```yaml input_boolean: diff --git a/blog/categories/how-to/index.html b/blog/categories/how-to/index.html index 09da482e7c..8de1f7c7ab 100644 --- a/blog/categories/how-to/index.html +++ b/blog/categories/how-to/index.html @@ -116,8 +116,6 @@
        -
      • Babyphone
      • -
      • How-To
      • diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index a2c9657325..4dc3a24ea5 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index 3c5104866e..99af6497e6 100644 --- a/blog/categories/internet-of-things/atom.xml +++ b/blog/categories/internet-of-things/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Internet-of-Things | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index 091a4a989f..22b05ec0c2 100644 --- a/blog/categories/iot-data/atom.xml +++ b/blog/categories/iot-data/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: IoT-Data | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index b28a3ae938..473f99d80c 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index 4a148a8caa..eac0484868 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index 4b5b2df490..1a41e42c91 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index a58fce9755..9b21ba3326 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index c7b221024e..85dcb214a4 100644 --- a/blog/categories/presence-detection/atom.xml +++ b/blog/categories/presence-detection/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Presence-Detection | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml index 15b76f22de..809166e29f 100644 --- a/blog/categories/public-service-announcement/atom.xml +++ b/blog/categories/public-service-announcement/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Public-Service-Announcement | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index 0dbcd275a4..8d05d000f6 100644 --- a/blog/categories/release-notes/atom.xml +++ b/blog/categories/release-notes/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Release-Notes | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 3fb2bd6e4c..7d1743d80c 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index c6e50e53be..1482846001 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index 00fff1249a..e19b722c7a 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index 0837ce35de..919aa7852e 100644 --- a/blog/categories/user-stories/atom.xml +++ b/blog/categories/user-stories/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: User-Stories | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index 65c0ab5f5f..b3dfb6856c 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 7e820df384..260631ce30 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2017-02-04T09:07:32+00:00 + 2017-02-04T09:14:18+00:00 https://home-assistant.io/ diff --git a/blog/index.html b/blog/index.html index 324c54b18f..52b74ebb2f 100644 --- a/blog/index.html +++ b/blog/index.html @@ -97,8 +97,6 @@
          -
        • Babyphone
        • -
        • How-To
        • @@ -115,7 +113,7 @@
          -

          One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available in the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home-Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (e.g., Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

          +

          One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

          Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.

          @@ -1163,8 +1161,6 @@ You have to note:
            -
          • Babyphone
          • -
          • Community
          • Device Tracking
          • diff --git a/blog/posts/10/index.html b/blog/posts/10/index.html index 2ebc5532c7..0acb632562 100644 --- a/blog/posts/10/index.html +++ b/blog/posts/10/index.html @@ -651,8 +651,6 @@ This article will try to explain how they all relate.

              -
            • Babyphone
            • -
            • Community
            • Device Tracking
            • diff --git a/blog/posts/2/index.html b/blog/posts/2/index.html index c728972761..903fe72454 100644 --- a/blog/posts/2/index.html +++ b/blog/posts/2/index.html @@ -1583,8 +1583,6 @@ So, part 1 of ESP8266
                -
              • Babyphone
              • -
              • Community
              • Device Tracking
              • diff --git a/blog/posts/3/index.html b/blog/posts/3/index.html index 1ccdea5aa5..8416e44ab3 100644 --- a/blog/posts/3/index.html +++ b/blog/posts/3/index.html @@ -807,8 +807,6 @@ One of the graphs created with this tutorial.
                  -
                • Babyphone
                • -
                • Community
                • Device Tracking
                • diff --git a/blog/posts/4/index.html b/blog/posts/4/index.html index c9f4677482..4c98ce4aa1 100644 --- a/blog/posts/4/index.html +++ b/blog/posts/4/index.html @@ -829,8 +829,6 @@ In the past month I was thinking about ways to integrate USB webcams into Home A
                    -
                  • Babyphone
                  • -
                  • Community
                  • Device Tracking
                  • diff --git a/blog/posts/5/index.html b/blog/posts/5/index.html index 8e36bb279c..cccae20098 100644 --- a/blog/posts/5/index.html +++ b/blog/posts/5/index.html @@ -767,8 +767,6 @@
                      -
                    • Babyphone
                    • -
                    • Community
                    • Device Tracking
                    • diff --git a/blog/posts/6/index.html b/blog/posts/6/index.html index 6acef569aa..84c93d2a24 100644 --- a/blog/posts/6/index.html +++ b/blog/posts/6/index.html @@ -907,8 +907,6 @@ Example of the new views in the frontend. Learn mor
                        -
                      • Babyphone
                      • -
                      • Community
                      • Device Tracking
                      • diff --git a/blog/posts/7/index.html b/blog/posts/7/index.html index febdc679dd..bfe51a3880 100644 --- a/blog/posts/7/index.html +++ b/blog/posts/7/index.html @@ -667,8 +667,6 @@ The InfluxDB database is a so-called time se
                          -
                        • Babyphone
                        • -
                        • Community
                        • Device Tracking
                        • diff --git a/blog/posts/8/index.html b/blog/posts/8/index.html index 4efad46f79..0b9ce1c47b 100644 --- a/blog/posts/8/index.html +++ b/blog/posts/8/index.html @@ -732,8 +732,6 @@ Inspried by a -
                        • Babyphone
                        • -
                        • Community
                        • Device Tracking
                        • diff --git a/blog/posts/9/index.html b/blog/posts/9/index.html index b72dc2cf21..95992c8c88 100644 --- a/blog/posts/9/index.html +++ b/blog/posts/9/index.html @@ -759,8 +759,6 @@ An initial version of voice control for Home Assistant has landed. The current i
                            -
                          • Babyphone
                          • -
                          • Community
                          • Device Tracking
                          • diff --git a/sitemap.xml b/sitemap.xml index d143425d23..660f0b430c 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -761,9 +761,6 @@ https://home-assistant.io/blog/categories/community/ -https://home-assistant.io/blog/categories/babyphone/ - - https://home-assistant.io/blog/posts/2/ @@ -2712,62 +2709,62 @@ https://home-assistant.io/demo/frontend.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/index.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-event.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-info.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-service.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-state.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-template.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/panels/ha-panel-history.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/panels/ha-panel-iframe.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/panels/ha-panel-logbook.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/demo/panels/ha-panel-map.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00 https://home-assistant.io/static/mdi-demo.html -2017-02-04T09:06:51+00:00 +2017-02-04T09:13:33+00:00