Issues with keeping streams #5
Comments
|
That auth error is interesting. |
|
I thought so as well... had authentication to Wyze failed, it couldn't have listed cameras, could it? Anything else I can provide? |
|
I believe the auth error could be some sort of rate limiting feature on wyze since we’re trying to authenticate all cameras at the same time. The script should pick that up and try to reconnect after cooling down for 10s. cameras.py authenticates once to get a list of cams, then runs wyzecam-to-rtmp.py for each of the cameras which does the authenticates again for each cam. As for the publishing error, it seems like ffmpeg or something upstream is freezing up causing that stream to die. I need to figure out a way to detect that so that I can restart the script. |
|
In now have two linux computers running the docker-wyze-bridge. I have 6 Wyze v3 cameras connected to them. 5 of the cameras run without issue. One consistently loses the ffmpeg stream, no matter which router it is connected to, no matter which computer running the bridge. There is no difference, in terms of firmware, between the cameras. All are configured for HD streams. Absent some advanced configuration I can't see right now, it would appear that this camera itself has some issue connecting to the docker-wyze-bridge which is unique to the camera itself. Get the exact same errors for the same camera on both bridge servers: rtsp-server | 2021/07/03 19:45:41 I [2/0] [RTSP] [session 3074560305] opened by 192.168.1.248:58775 The camera is one of 6 purchased brand new and shipped at the same time last December. Did not begin to use any of them until a couple of weeks ago. All on same firmware version. All connected to same AP/routers. Any ideas what the camera issue could be? |
maybe run ffprobe periodically? I do with my wyze RTSP stream in HA, if ffprobe doesn't see an RTSP stream within a minute I use smart plug to restart the wyze cam - real hammer solution :) |
I actually did this with the first wyze-to-rtmp bridge. Script is below (mines was checking the rtmp stream). Be careful, however, because I ran this every minute and forgot to remove a camera I wasn't using -- and it eventually filled up the memory. stream303=$(ffprobe -v quiet -print_format json -show_streams rtmp://192.168.1.197/show/wyzecam303) My experience so far, with 4 cameras, is that I have not needed to do this with docker-wyze-bridge |
|
On v.0.3.1 now, still seeing constant disconnects when I have more than 1 camera included. Doesn't seem to matter which of several v2 or v3 cameras I try. I'm consuming the feeds with Blue Iris. Below is typical: Starting rtsp-server ... done Any further logging or testing I can do to help? I really love this solution and would like to use it for all my Wyze cams. |
|
Interesting.. Is it somewhat stable if you just have one camera? You could add |
|
MUCH more stable - also added the FFMPEG debug flag. root@debian:/home/terry/docker-wyze-bridge# docker-compose up |
|
What's the host OS and specs? Could you try rebuilding and running the container with the arm library? build:
context: ./app
dockerfile: Dockerfile.arm then rebuild with |
|
This is an old Intel Celeron laptop, I think 3gb RAM. All it was doing previously was hosting my dev Home Assistant instance. root@debian:/home/terry/docker-wyze-bridge# uname -a I can't get the arm version to build: root@debian:/home/terry/docker-wyze-bridge# sudo docker-compose up --build Thanks for your help! As I said before, I'd LOVE to have this working for all my Wyze cams coming into BI! |
|
mrlt8 / others - Thankyou for this docker option - I "think" I have everything installed correctly, but am getting this error when trying to startup the processes | Error continue until I stop the docker processes - Any help / guidance would be a great help $ docker-compose up |
@terryhonn How is the CPU usage when adding multiple cameras? Could you try running docker on another system so we can figure out what is causing the issues.
@espressoant Looks like your v2 errors out because the rtsp server doesn't like the You can keep the current |
|
@mrlt8 - I have changed both of my camera name to only have letters or numbers Then it complains about needing a "/" Cam drive1 however wroks perfect so far :-) ---part of screen output |
|
That usually means that the camera hasn't started broadcasting yet. when the stream is up |
Hey @mrlt8 , I installed Docker (and WSL) on my Blue Iris machine, an Intel i7-6700 @ 3.40Ghz, 16gb RAM running Windows 10 Pro. Let me know how else I can help! |
|
@terryhon -
|
hmm, I don't think i've seen that error before..
@espressoant Could be a network/wifi issue? Some routers may not be able to handle multiple devices transmitting at the same time. Might want to check your router config? |
|
People having issues with multiple cameras may want to check their wifi access points for setting like airtime fairness. |
As you can see in the log below, it was very stable with one camera, but as soon as I add a couple more, it kinda falls apart: |
I'm fairly confident in my *nix skills but I'm running into issues keeping the two services continuing to serve up my streams.
I've got 11 cameras (10 are setup and powered on, WCO is sitting on my desk), a mix of v2, v3 and a doorbell. A few of the v2s have the RTSP firmware from Wyze. Both servers seem to start up fine, but I can't keep any streams going.
I had two of the cameras set up in Blue Iris, (backdoor-camera and front-porch) and initially the streams came through, but stopped, and that's why the "no one is publishing..." error messages are there.
Am I doing something obviously wrong with this, or what can I do to troubleshoot? Thanks
The text was updated successfully, but these errors were encountered: