search

potmat / homebridge-google-nest-sdm

A Homebridge plugin for Google Nest devices that uses the Google Smart Device Management API. Supports Cameras, Doorbells, Displays, and Thermostats. Includes support for HomeKit Secure Video.
ISC License
140 stars 17 forks source link

ERROR Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin. #59

Closed lizztheblizz closed 1 year ago

lizztheblizz commented 1 year ago

Only finding one prior reference to the error in the issue title, with no clear resolution. On closer inspection of open issues, this may be related to #53.

I am running the plugin on HOOBS, running on a Raspberry Pi 4. Configuration appears to be working correctly otherwise: I'm receiving motion notifications through my Home app, and I am able to view the camera's live stream directly. This appears to affect only the video capturing attached to those motion notifications.

The device in question is the Google Nest Doorbell (battery). All software versions are current: HOOBS 4.2.8, bridge version 1.1.9.

Full HOOBS logs:

1:04:44 PM Google Nest Sdm Bridge Loaded plugin 'homebridge-google-nest-sdm'
1:04:44 PM Google Nest Sdm Bridge Loading 1 platforms...
1:04:44 PM Google Nest Sdm Bridge homebridge-google-nest-sdm Loading accessory from cache: Entryway Doorbell
1:04:45 PM Google Nest Sdm Bridge Bridge is running on port 51886.
1:04:47 PM Google Nest Sdm Bridge homebridge-google-nest-sdm Restoring existing accessory from cache: Entryway Doorbell
1:11:41 PM Google Nest Sdm Bridge homebridge-google-nest-sdm ERROR Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.
1:11:55 PM Google Nest Sdm Bridgehome bridge-google-nest-sdm ERROR Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.
1:12:08 PM Google Nest Sdm Bridge ERROR [HDS ::ffff:192.168.1.138] Recording download stream 1 is still awaiting generator although stream was closed 10s ago! This is a programming mistake by the camera implementation which prevents freeing up resources.
1:12:08 PM Google Nest Sdm Bridge ERROR [HDS ::ffff:192.168.1.138] Recording download stream 1 is still awaiting generator although stream was closed 10s ago! This is a programming mistake by the camera implementation which prevents freeing up resources.
1:12:12 PM Google Nest Sdm Bridge ERROR [HDS ::ffff:192.168.1.138] Recording download stream 1 is still awaiting generator although stream was closed 10s ago! This is a programming mistake by the camera implementation which prevents freeing up resources.
1:12:12 PM Google Nest Sdm Bridge ERROR [HDS ::ffff:192.168.1.138] Recording download stream 1 is still awaiting generator although stream was closed 10s ago! This is a programming mistake by the camera implementation which prevents freeing up resources.

HOOBS runs each bridge in its own container. Could that be the culprit here?

tealtwo commented 1 year ago

Having the same issue here!

potmat commented 1 year ago

We've seen problems like this in the past with Homebridge running in containers that were resolved by running Homebridge on a host directly (such as an RPi) on the local network. It seems that the WebRTC stream has problems with the networking associated with such as setup: https://github.com/potmat/homebridge-google-nest-sdm/issues/43

potmat commented 1 year ago

Perhaps something here will help: https://forums.docker.com/t/understanding-docker-run-attach-option/134337

potmat commented 1 year ago

Closing due to lack of activity.

iknowdjz commented 7 months ago

Hi, I'm having the same issue/error as well. Everything was working fine for many months and recently added a couple more cameras so had to go thru the reauth process to enable them. Once I did they showed up right away, but don't get anything other than the Google logo to show up. Anytime I click on of the cameras it tries to refresh for about 30 seconds or so and then gets marked as No Response

I have a total of 8 nest cameras connected. Homebridge is running on my Mac Studio.

LMK if you need more details to deug.

Below are the errors:


[1/19/2024, 3:50:28 PM] [homebridge-google-nest-sdm] Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.
[HDS ::ffff:192.168.1.102] Recording download stream 1 is still awaiting generator although stream was closed 10s ago! This is a programming mistake by the camera implementation which prevents freeing up resources.
[HDS ::ffff:192.168.1.102] Recording download stream 1 is still awaiting generator although stream was closed 10s ago! This is a programming mistake by the camera implementation which prevents freeing up resources.
[1/19/2024, 3:50:47 PM] [homebridge-google-nest-sdm] Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.
[HDS ::ffff:192.168.1.102] Recording download stream 1 is still awaiting generator although stream was closed 10s ago! This is a programming mistake by the camera implementation which prevents freeing up resources.
[1/19/2024, 3:51:18 PM] [homebridge-google-nest-sdm] Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.
[HDS ::ffff:192.168.1.102] Recording download stream 1 is still awaiting generator although stream was closed 10s ago! This is a programming mistake by the camera implementation which prevents freeing up resources.
[1/19/2024, 3:52:11 PM] [homebridge-google-nest-sdm] Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.
[HDS ::ffff:192.168.1.102] Recording download stream 1 is still awaiting generator although stream was closed 10s ago! This is a programming mistake by the camera implementation which prevents freeing up resources.```