FFmpeg isn't running!

[xtianpaiva]

Trying to use camera (YI Home) component, but having problems to start ffmpeg on Hass.io v1.1 and HA v0.61.1

`ffmpeg:

camera:

• platform: yi
  name: 'Portón'
  host: '192.168.1.223'
  password: !secret yi_porton
  ffmpeg_arguments: '-vf scale=800:450'`

WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!

Is there something I'm missing?

[kjacksonmusic]

Same issue with yi camera. My Ring camera works fine for a while then Hassio will show this and neither works. Heres a thread with further details:
https://www.reddit.com/r/homeassistant/comments/7rlq9x/anyone_using_ffmpeg_on_hassio/

[marcgarciamarti]

Hello, I do see the same statement in hassio logs. @xtianpaiva did you manage to solve this?

[pvizeli]

You need set it to debug and post the log to pvizeli/ha-ffmpeg

[marcgarciamarti]

Done: home-assistant-libs/ha-ffmpeg#22

thanks @pvizeli

[marcgarciamarti]

@pvizeli have you got around to looking into this one? any additional information that I may provide? please, just let me know :)

[fcollingwood]

Still an issue with 0.82:

2018-11-13 22:25:05 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!

[dp106]

Still an issue on 0.83.3

[cmatte]

Still an issue with 0.84.6 on Docker / Synology NAS:
2018-12-27 23:52:26 WARNING (MainThread) [haffmpeg.tools] Timeout reading image.
2018-12-27 23:53:09 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
However, after a couple of clicks the video appears.

[YoinkZed]

Same here on hassio 0.84.6

[manuel-jrs]

Same on hassio 0.87.0

[PDekker]

Same here on 0.87

[diogoribeiro09]

Same here on 0.87.1
Has anyone figured out how to solve it ?

[jeffl78]

I'm having the same problem but I just got around to putting my cameras in hass.io/docker on raspi 3b stretch and can't seem to get them to show up. I see them in developmer tools "states" but they say idle. I don't see any errors but haven't tried running the trouble shooting yet. I've tried on 0.87 and 0.87.1 with no change. These are D-Link 930, 932, and 933 cameras though and I'm running homebridge with ffmpeg at home/pi/ffmpeg but I still have ffmpeg_bin: set to /usr/bin/ffmpeg in my config.yaml

[alb147]

same in 0.88.2 with YI camera.

Log Details (WARNING)
FFmpeg isn't running!

[diogoribeiro09]

Hi,

This configuration made it work for me.

camera:

• platform: yi
  name: Camera
  host: 192.168.1.82
  password: !secret domePass
  path: /tmp/sd/record
  ffmpeg_bin: /usr/local/bin/ffmpeg
  ffmpeg_arguments: '-vf scale=800:450'

Hope it solves the problem for anyone else :)

EDIT: The path for the camera footage was identified by using ftp to access the camera and finding where it was being stored. It may be subjected to change on your particular camera. My camera is the 'Yi Dome'.

[alb147]

Hi,

This configuration made it work for me.

camera:

• platform: yi
  name: Camera
  host: 192.168.1.82
  password: !secret domePass
  path: /tmp/sd/record
  ffmpeg_bin: /usr/local/bin/ffmpeg
  ffmpeg_arguments: '-vf scale=800:450'

Hope it solves the problem for anyone else :)

EDIT: The path for the camera footage was identified by using ftp to access the camera and finding where it was being stored. It may be subjected to change on your particular camera. My camera is the 'Yi Dome'.

what it´s your HA version?
i have a 0.88.2 and don´t running. :(
have the same configuration

[jeffl78]

I just saw this, did you use ftp as a search term, or how did you determine the ftp file path? Will it run without the record path initially? I think the answer is yes, it being an optional parameter. I'll try it without ASAP.

[techdoutdev]

Take a look here: https://community.home-assistant.io/t/ffmpeg-isnt-running-problem/96172

I was able to get mine working by following the exact same config - apparently the docker version of home assistant is much more picky on how it's configured.

[jeffl78]

I have them loaded without error on a clean install, but they're state is idle and it they still won't show up in the frontend. I'm playing around with the options to see what works.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.