v2.0.0 Streaming Issues #554

ex725 · 2020-06-20T20:03:25Z

it was working fine before updating.

donavanbecker · 2020-06-20T20:28:16Z

did you update to v2.0.0?

ex725 · 2020-06-20T21:45:57Z

did you update to v2.0.0?

Yes. became inoperable after updating

MikeDProducer · 2020-06-21T01:04:59Z

Same.

AtomicLight · 2020-06-21T04:32:55Z

Same. My cameras just error out in the Home app.

sylwesterr · 2020-06-21T08:39:36Z

Same here - it does not seem to be loading at all...

vshurygin · 2020-06-21T10:42:41Z

Same, Two cameras, screenshots give out.

dehness · 2020-06-21T11:27:31Z

Same here. Two cameras using RTSP stream. Worked fine prior to 2.0.0 update.

thorstenman · 2020-06-21T11:29:29Z

Same here. Had 6 cameras connected. Worked perfect before updating. Now Homebridge completely stopped working. After deleting the whole plugin related config and adding one camera it works again... adding more let’s it break.

donavanbecker · 2020-06-21T12:28:30Z

Since this changes everything over to bridged cameras, did you all double check that you were viewing the bridged cameras? vs old non bridged cameras? The old non bridged cameras need to be manually removed.

vshurygin · 2020-06-21T12:32:50Z

Since this changes everything over to bridged cameras, did you all double check that you were viewing the bridged cameras? vs old non bridged cameras? The old non bridged cameras need to be manually removed.

I even uninstalled and reinstalled the plugin. The cameras of course the old ones were removed.

thorstenman · 2020-06-21T13:04:29Z

I deleted the camera configs in the config.json, deinstalled the plugin and reinstalled. Same behavior still.

Before v2.0.0 I saw all cameras next to directly to HomeKit integrated ones.

dehness · 2020-06-21T13:10:47Z

I removed the devices via the GUI. And since the new bridge camera mode doesn’t offer the option to “remove camera”, I’m certain I removed the right ones.

I tried several uninstall/restart/reinstall’s of the plugin and even tried the 2.0.1 beta 4 (I think) but to no avail. However, as soon as I downgraded to 1.3.0 and re-added the cameras they worked perfectly.

thorstenman · 2020-06-21T14:10:32Z

I downgraded to v1.3.0, re-implemented via old config.json, decoupled again via Homebridge UI prefs, deleted in parallel via Homebridge Camera Ffmpeg plugin GUI all cameras as well as the plugin itself. After that reinstalled v2.0.0. No change. Not even the Homebridge Config UI is accessible...

Is it maybe a problem that the cams are somehow connected via HomeKit basing on the pin integration (instead of QR code)?

bjornand1 · 2020-06-21T17:03:35Z

Just one more chiming in with the same problem. I have two cameras connected, after the latest update one of them, a KingCam, has stopped responding in HomeKit (it still works fine in the native app).

donavanbecker · 2020-06-21T17:05:57Z

Just one more chiming in with the same problem. I have two cameras connected, after the latest update one of them, a KingCam, has stopped responding in HomeKit (it still works fine in the native app).

If you are looking at the cameras you had before updating, they will be unresponsive. Homebridge will add the cameras bridged to homebridge. So I would check to see if your cameras are in the same room as your homebridge bridge?

bjornand1 · 2020-06-21T17:27:47Z

@donavanbecker Thanks for the tip, but I have noticed that. I have removed the old instances and moved the new ones to the correct rooms. One of these still work as before, but one says no response, and in the homebridge log, it says «exited with code 1 and signal null.

donavanbecker · 2020-06-21T17:36:03Z

@donavanbecker Thanks for the tip, but I have noticed that. I have removed the old instances and moved the new ones to the correct rooms. One of these still work as before, but one says no response, and in the homebridge log, it says «exited with code 1 and signal null.

Can you post your config?

bjornand1 · 2020-06-21T17:58:55Z

"name": "Camera ffmpeg",
"cameras": [
{
"name": "KingCam",
"videoConfig": {
"source": "-rtsp_transport http -i rtsp://xxx.xxx.x.xx/user=Xxxx_password=Xxxxxxx_channel=1_stream=0.sdp?real_stream",
"stillImageSource": "-i http://faster_still_image_grab_url/this_is_optional.jpg",
"maxStreams": 1,
"maxFPS": 15,
"maxBitrate": 300,
"vcodec": "copy",
"audio": false,
"debug": true

bjornand1 · 2020-06-21T18:25:04Z

@donavanbecker Posted now, does it provide any clues?

kontur11 · 2020-06-21T18:56:19Z

"name": "Camera ffmpeg",
"camera": [
{
"name": "KingCam",
"videoConfig": {
"source": "-rtsp_transport http -i rtsp: //xxx.xxx.x.xx/ user = Xxxx_password = Xxxxxxx_channel = 1_stream = 0.sdp? real_stream ",
" stillImageSource ":" -i http: //faster_still_image_grab_url/this_is_optional.jpg ",
" maxStreams ": 1,
" maxFPS ": 15,
" maxBitrate ": 15, " maxBitrate ": ,
"vcodec": "copy",
"audio": false,
"debug": true

" maxBitrate ": 15, " maxBitrate ": , ????

bjornand1 · 2020-06-21T19:20:13Z

Something went wrong when pasting, maxbitrate is set at 300, only one entry!

bjornand1 · 2020-06-21T19:23:03Z

"name": "Camera ffmpeg",
"cameras": [
{
"name": "KingCam",
"videoConfig": {
"source": "-rtsp_transport http -i rtsp://xxx.xxx.x.xx/user=xxxxxx_password=xxxxxx_channel=1_stream=0.sdp?real_stream",
"stillImageSource": "-i http://faster_still_image_grab_url/this_is_optional.jpg",
"maxStreams": 1,
"maxFPS": 15,
"maxBitrate": 300,
"vcodec": "copy",
"audio": false,
"debug": true

donavanbecker · 2020-06-21T20:54:35Z

@bjornand1 Can you try setting video processor from config ui? To ffmpeg.

vshurygin · 2020-06-21T21:05:12Z

@bjornand1 Can you try setting video processor from config ui? To ffmpeg.

It didn't help.

ex725 · 2020-06-21T21:27:00Z

You can fix the problem by going to the previous version for now.

sudo npm install -g --unsafe-perm [email protected]

MikeDProducer · 2020-06-22T02:39:47Z

I had the same problem. Yes, i removed the old cameras. The new ones show thumbnails but the streams don’t work. Ffmpeg exits and SIGTERM.

I wonder if the video codec has something to do with it. Has anyone tried not using “copy” as the codec?

tarbychark · 2020-06-22T04:42:40Z

Same problems here. Snapshots now rarely update and the camera's never go live.

[6/22/2020, 12:38:05 AM] [Camera-ffmpeg] [FFMPEG] ffmpeg exited with code: 1 and signal: null (error)

No issues with the previous version.

bjornand1 · 2020-06-22T08:01:15Z

I have run the command "sudo npm install -g --unsafe-perm [email protected]" to downgrade, but the plugin remains at version 2.0.0. Is there any advice on how to make the downgrade happen?

roomwillow · 2020-07-01T01:05:44Z

Just coming to add that I'm encountering the same problem, JideTech brand camera, that exact line in "source" works perfect in VLC, the phone shows a crossed-out camera "No Response" on preview and just infinitely loops when the camera is selected, will be following this issue

russoandrewrusso · 2020-07-01T19:27:38Z

I am having the same issue. I have Hikvision cameras and axis. also have the issue with rtsp stream coming out of Synology. plays fine in VLC but not in HomeKit.

Wildcat1 · 2020-07-01T21:28:26Z

@donavanbecker any thoughts on what we're all seeing currently with V2 vs v 1.3 ? Have a wide array of cams to test with so if there is a release that you think would be beneficial (beta etc) then please let us know. Thanks for your assistance. Hopefully we can get this resolved ASAP because it was working fantastically well until the V2 change(s)

donavanbecker · 2020-07-01T22:10:16Z

@donavanbecker any thoughts on what we're all seeing currently with V2 vs v 1.3 ? Have a wide array of cams to test with so if there is a release that you think would be beneficial (beta etc) then please let us know. Thanks for your assistance. Hopefully we can get this resolved ASAP because it was working fantastically well until the V2 change(s)

I am not currently experiencing these issues. I am open to a PR though if someone finds the problem.

donavanbecker · 2020-07-02T15:31:21Z

Please Test latest beta to see if this resolves any of your issues. [email protected]

This can be installed by running sudo npm install -g --unsafe-perm homebridge-camera-ffmpeg@beta

russoandrewrusso · 2020-07-02T15:37:28Z

just installed and doesn't seem to have fixed it. I can open the all of the sources in vlc and It plays fine.

[7/2/2020, 3:36:01 PM] [Camera-ffmpeg] Starting video stream (1280x720, 30 fps, 299 kbps, 1378 mtu)...
[7/2/2020, 3:36:01 PM] [Camera-ffmpeg] FFMPEG: received first frame
[7/2/2020, 3:36:01 PM] [Camera-ffmpeg] [FFMPEG] ffmpeg exited with code: 1 and signal: null (error)
[7/2/2020, 3:36:01 PM] [Camera-ffmpeg] Stopped streaming session!

DerrickGibbs1 · 2020-07-02T15:51:26Z

This might be related to #579. I was able to fix the issues I was experiencing by renaming my camera to a name I hadn't used before. I was able to observe the problem by changing ffmpegDebugOutput to true in the source.

russoandrewrusso · 2020-07-02T15:56:02Z

I just renamed a camera and it is working now.

Wildcat1 · 2020-07-02T19:16:19Z

@donavanbecker pasted this in my bug that I saw was closed but also wanted to cross post here as it does pertain to the latest beta you reference above for resolving streaming issues. Latest beta is definitely an improvement to solving the streaming issues BUT I'm noticing that once I add a cam in the latest v2.0.2 beta 39 that any subsequent changes to that cam through the Plugin's\Settings option results in Homebridge not being able to restart as it kicks out the error below. Only way to resolve is to remove Platform, remove cached device and start over. Thoughts on this ? Thanks again

Cannot add a Service with the same UUID 'xxxxxxxx7xxxxx5xx91' as another Service in this Accessory without also defining a unique 'subtype' property.
    at Accessory._this.addService (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:276:17)
    at PlatformAccessory.addService (/usr/local/lib/node_modules/homebridge/src/platformAccessory.ts:92:41)
    at FfmpegPlatform.configureAccessory (/usr/local/lib/node_modules/homebridge-camera-ffmpeg/src/index.ts:123:12)
    at /usr/local/lib/node_modules/homebridge/src/server.ts:307:25
    at Array.filter (<anonymous>)
    at Server.restoreCachedPlatformAccessories (/usr/local/lib/node_modules/homebridge/src/server.ts:270:69)
    at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:158:10)
    at cli (/usr/local/lib/node_modules/homebridge/src/cli.ts:80:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:1133:30)

sylwesterr · 2020-07-02T19:56:24Z

Hi y’all,

I was just playing with my old HP laptop (trying to make use of it - is it around 10 years old i5-480 (first gen i5) based, I installed Ubuntu on it and wanted to try installing homebridge on it, naturally it works so I decided to try installing this camera plugin to try debugging it. First thing: I noticed there is v2.0.1, second, I started copying config of my cameras working with on v1.3, and one by one I added them, omitting vcodec parameter and all work, there is native HikVision IP camera (streaming FullHD using rtsp h264), Dahua DVR, also streaming rtsp h264, then there are two RPi cameras, streaming mjpeg (mjpgstreamer in OctoPrint) over http and one other RPi camera streaming mjpeg over http (motionOS).
As they were all working I decided “to go for it” and:

Removed all cameras from home, as I noticed once homebridge is added to home and fresh installation of camera plugin is installed, the cameras that are added appear automatically in Home..
I did perform camera plugin upgrade on my Pi (without touching cameras config) and just restarted homebridge and.... BOOM!!!! after homebridge startup I opened home app and all cameras appeared and all are working!!!!

Wildcat1 · 2020-07-02T20:59:54Z

Thought I would add this update from me as well. I know this is crossposted to the other bug but seems this is related to the streaming setup as well.

I can now literally replicate this over and over. What is weird is it gets into that loop RE: (another service with same UUID) even if I use cam names I had before installing this beta. Steps to reproduce this and then fix are:

To Cause The Issue:
1 - Start with fresh plugin (beta 39 and all cached cams removed using Homebridge menu)
2 - Add camera
3 - Restart homebridge
4 - Camera appears without issue
5 - Go back into plugin settings OR config.json and adjust a setting OR add a new camera
6 - Restart Homebridge
7 - Homebridge never restarts getting stuck in the 'another service with same UUID.......' error

To Fix The Issue
1 - Go into Plugin\Settings
2 - Remove camera completely
3 - Go to Homebridge menu, remove cached camera(s), this leaves only "platform": "Camera-ffmpeg" in config.json.
4 - Restart Homebridge
5 - Homebridge restarts without issue

The problem of course is 1) somewhere, previous cam names are being stored so seemingly can only be used once and 2) that due to the error being seen, if you need to adjust ANYTHING or add a new camera you will be forced to remove the existing cameras completely, remove cached cams and start from scratch

Thoughts on how to get around this or can be fixed in the plugin @donavanbecker ?

m4ary · 2020-07-02T22:38:30Z

I just renamed a camera and it is working now.

this is working, thank you !!!

i think its related to HomeKit or Apple because even with new fresh server i cannot use the old camera name, i renamed it to something i never used it in any build and its working

rottylr · 2020-07-03T00:12:29Z

Uploaded v2.0.2-beta.39 and changed the camera name. Still not working for me. I do get a more detailed log. However, I don't know what it means. Anyone know who to decode this for me?

[7/2/2020, 7:41:26 PM] [Camera-ffmpeg] Starting qwerty123 video stream (1280x720, 15 fps, 299 kbps, 188 mtu)...
[7/2/2020, 7:41:26 PM] [Camera-ffmpeg] FFMPEG command: ffmpeg -rtsp_transport http rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0 -map 0:0 -vcodec copy -pix_fmt yuv420p -r 15 -f rawvideo -preset ultrafast -tune zerolatency -b:v 299k -bufsize 598k -maxrate 299k -payload_type 99 -ssrc 387771 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params EI0bzt1/qMZV+5bwGinPEsLRSXggiz3BeCODWIAI srtp://0.0.0.0:51403?rtcpport=51403&localrtcpport=51403&pkt_size=188 -map 0:1 -acodec libfdk_aac -profile:a aac_eld -flags +global_header -f null -ar 16k -b:a 24k -bufsize 24k -ac 1 -payload_type 110 -ssrc 3426820 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params ar7Zj3PY20il3CShxueHxpg9inf+sF1F5t34Xuoc srtp://0.0.0.0:65241?rtcpport=65241&localrtcpport=65241&pkt_size=188 -loglevel debug
[7/2/2020, 7:41:26 PM] [Camera-ffmpeg] [FFMPEG] Failed to start stream: spawn ffmpeg ENOENT
[7/2/2020, 7:41:26 PM] [Camera-ffmpeg] Stopped qwerty123 video stream!

[update: My camera plugin works. I’ve narrowed the cause of my issues to my VLAN Firewall settings. Devices on the same VLAN as the homebridge and camera work just fine. And Devices that connect via cellular work just fine.]

fparrav · 2020-07-03T02:17:43Z

I did Unpair Bridges / Cameras / TVs / External Accessories and Restart Homebridge Accessory, change camera names and now out of 3 only one xiaofang works for rstp, and a dcs-930L dlink failed that worked with mjpeg perfectly.I am using v2.0.2-beta.39.

1|homebridge  | 02-07-2020 22:12 -04:00: [7/2/2020, 10:12:29 PM] [Camera-ffmpeg] Starting Camara_Dormitorio video stream (1280x720, 15 fps, 299 kbps, 1316 mtu)...
1|homebridge  | 02-07-2020 22:12 -04:00: [7/2/2020, 10:12:32 PM] [Camera-ffmpeg] [FFMPEG] ffmpeg exited with code: 1 and signal: null (error)
1|homebridge  | 02-07-2020 22:12 -04:00: [7/2/2020, 10:12:32 PM] [Camera-ffmpeg] Stopped Camara_Dormitorio video stream!
1|homebridge  | 02-07-2020 22:12 -04:00: [7/2/2020, 10:12:37 PM] [Camera-ffmpeg] Starting Camara_Sala video stream (1280x720, 25 fps, 299 kbps, 1316 mtu)...
1|homebridge  | 02-07-2020 22:12 -04:00: [7/2/2020, 10:12:37 PM] [Camera-ffmpeg] [FFMPEG] ffmpeg exited with code: 1 and signal: null (error)

Aekung · 2020-07-03T02:20:52Z

Changing the camera name does really fix it for me too.

Thanks for the solution.

donavanbecker · 2020-07-03T02:23:06Z

Seems like most of these issues are being resolved by the latest beta. once we get the mqtt motion part finished from @fennec622. We will be releasing this in v2.1.0.

donavanbecker · 2020-07-03T02:37:01Z

I am closing this issue, if you have any other issues please report in beta testing issue #575.

myusuf3 · 2020-07-05T03:55:07Z

@donavanbecker that did it! thanks!!

…ridge-camera-ffmpeg#554)

Lucianoci · 2022-07-24T13:04:48Z

Thought I would add this update from me as well. I know this is crossposted to the other bug but seems this is related to the streaming setup as well.

I can now literally replicate this over and over. What is weird is it gets into that loop RE: (another service with same UUID) even if I use cam names I had before installing this beta. Steps to reproduce this and then fix are:

To Cause The Issue:

1 - Start with fresh plugin (beta 39 and all cached cams removed using Homebridge menu)

2 - Add camera

3 - Restart homebridge

4 - Camera appears without issue

5 - Go back into plugin settings OR config.json and adjust a setting OR add a new camera

6 - Restart Homebridge

7 - Homebridge never restarts getting stuck in the 'another service with same UUID.......' error

To Fix The Issue

1 - Go into Plugin\Settings

2 - Remove camera completely

3 - Go to Homebridge menu, remove cached camera(s), this leaves only "platform": "Camera-ffmpeg" in config.json.

4 - Restart Homebridge

5 - Homebridge restarts without issue

The problem of course is 1) somewhere, previous cam names are being stored so seemingly can only be used once and 2) that due to the error being seen, if you need to adjust ANYTHING or add a new camera you will be forced to remove the existing cameras completely, remove cached cams and start from scratch

Thoughts on how to get around this or can be fixed in the plugin @donavanbecker ?

Hi
I can remove de camera, but not the cached camera y hb settings, because only light bulbs appear
I have two camera ip: Gadnic and tapo, both stream through VLC, but hb also give the null error and can't stream . They both work with synology surveillance
Thanks

ex725 added the bug label Jun 20, 2020

donavanbecker added the v2.0.0 label Jun 21, 2020

This was referenced Jul 1, 2020

Unable to access rtsp stream in homebridge-camera-ffmpeg, but able to in VLC #584

Closed

Update completely broke my HomeBridge #559

Closed

DerrickGibbs1 mentioned this issue Jul 2, 2020

ERROR: FFmpeg exited with code 1 beele/homebridge-unifi-protect-camera-motion#53

Closed

This was referenced Jul 2, 2020

Only able to stream outside of network #563

Closed

ffmpeg EACCES error #561

Closed

Bars in Picture #558

Closed

donavanbecker closed this as completed Jul 3, 2020

donavanbecker unpinned this issue Jul 3, 2020

california444 mentioned this issue Jul 3, 2020

v2.1.0 Testers Needed - MQTT support for Motion Detect! #575

Closed

jkempinger mentioned this issue Jul 16, 2020

Streaming not working via homebridge, but can connect with VLC #661

Closed

beele pushed a commit to beele/homebridge-unifi-protect-camera-motion that referenced this issue Sep 20, 2020

Working again! (stream does not work due to: homebridge-plugins/homeb…

901c21b

…ridge-camera-ffmpeg#554)

v2.0.0 Streaming Issues #554

v2.0.0 Streaming Issues #554

Comments

ex725 commented Jun 20, 2020

donavanbecker commented Jun 20, 2020

ex725 commented Jun 20, 2020

MikeDProducer commented Jun 21, 2020

AtomicLight commented Jun 21, 2020

sylwesterr commented Jun 21, 2020

vshurygin commented Jun 21, 2020

dehness commented Jun 21, 2020

thorstenman commented Jun 21, 2020

donavanbecker commented Jun 21, 2020 • edited Loading

vshurygin commented Jun 21, 2020

thorstenman commented Jun 21, 2020 • edited Loading

dehness commented Jun 21, 2020 • edited Loading

thorstenman commented Jun 21, 2020 • edited Loading

bjornand1 commented Jun 21, 2020

donavanbecker commented Jun 21, 2020

bjornand1 commented Jun 21, 2020

donavanbecker commented Jun 21, 2020

bjornand1 commented Jun 21, 2020

bjornand1 commented Jun 21, 2020

kontur11 commented Jun 21, 2020

bjornand1 commented Jun 21, 2020

bjornand1 commented Jun 21, 2020

donavanbecker commented Jun 21, 2020

vshurygin commented Jun 21, 2020

ex725 commented Jun 21, 2020

MikeDProducer commented Jun 22, 2020

tarbychark commented Jun 22, 2020

bjornand1 commented Jun 22, 2020

roomwillow commented Jul 1, 2020

russoandrewrusso commented Jul 1, 2020

Wildcat1 commented Jul 1, 2020

donavanbecker commented Jul 1, 2020

donavanbecker commented Jul 2, 2020 • edited Loading

russoandrewrusso commented Jul 2, 2020 • edited by donavanbecker Loading

DerrickGibbs1 commented Jul 2, 2020

russoandrewrusso commented Jul 2, 2020

Wildcat1 commented Jul 2, 2020 • edited by donavanbecker Loading

sylwesterr commented Jul 2, 2020

Wildcat1 commented Jul 2, 2020

m4ary commented Jul 2, 2020

rottylr commented Jul 3, 2020 • edited Loading

fparrav commented Jul 3, 2020

Aekung commented Jul 3, 2020

donavanbecker commented Jul 3, 2020

donavanbecker commented Jul 3, 2020

myusuf3 commented Jul 5, 2020

Lucianoci commented Jul 24, 2022

donavanbecker commented Jun 21, 2020 •

edited

Loading

thorstenman commented Jun 21, 2020 •

edited

Loading

dehness commented Jun 21, 2020 •

edited

Loading

thorstenman commented Jun 21, 2020 •

edited

Loading

donavanbecker commented Jul 2, 2020 •

edited

Loading

russoandrewrusso commented Jul 2, 2020 •

edited by donavanbecker

Loading

Wildcat1 commented Jul 2, 2020 •

edited by donavanbecker

Loading

rottylr commented Jul 3, 2020 •

edited

Loading