Camera Feed Delayed 10+ minutes #1042
Replies: 41 comments 52 replies
-
|
Do you have audio enabled? There's a muxing issue when audio is enabled and a frame is delayed causing the audio and video to go out of sync. One potential solution is to use environment:
...
- FFMPEG_FLAGS=-use_wallclock_as_timestamps 1 |
Beta Was this translation helpful? Give feedback.
-
|
Audio is enabled and noticeable delayed. didn't realize it would affect the video being delayed as well. Thought video would remain near live and the sound just comes in 10 seconds later. |
Beta Was this translation helpful? Give feedback.
-
|
I don't even know how to enable/disable audio in WyzeBridge. |
Beta Was this translation helpful? Give feedback.
-
|
So I disabled audio on the docker cause I don't use it and don't really need it for outdoor camera's. Noticed that today my camv3 (WYZE_CAKP2JFUS) are all live, but my v3 Pro (HL_CAM3P) has fallen back about 25 minutes. |
Beta Was this translation helpful? Give feedback.
-
|
Any ideas how to trouble shoot the v3Pro drifting out of sync? |
Beta Was this translation helpful? Give feedback.
-
|
Seeing this also, relatively recently. I have to restart the container every ~2 days to get it back up to live. I don't use audio. |
Beta Was this translation helpful? Give feedback.
-
|
Confirming that 2.8.1 appears to resolve my issue 👍 |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same problem. Trying to use this with frigate to detect people and a 25 minute delay makes it effectively useless... |
Beta Was this translation helpful? Give feedback.
-
|
Also seeing this issue. Sometimes they will randomly jump back up to the correct time, but most of the time they are anywhere from 5 to 25 minutes behind. Audio is disabled. |
Beta Was this translation helpful? Give feedback.
-
|
Same here |
Beta Was this translation helpful? Give feedback.
-
|
I'm now seeing this, especially on my v2 cameras, the time will 'drift'. I'm using Blue Iris and have the time stamp enabled. I've also enabled the timestamp on Wyze so on the camera feed I'm seeing two timestamps (Blue Iris is effectively the current/real-time, and Wyze would be 'camera time'). What I've been seeing is I restart the docker and every camera (I have 12) is around 2 seconds difference. That's no problem. After an hour, the v2 cameras will 'drift' at about a rate of 30 seconds per hour. A few hours in, and I'm a few minutes behind. If I restart docker, BAM, time is fixed. I'm entertaining the idea of a scheduled task to restart the docker every 60 minutes or something to keep the cameras 'in sync'. For me, I'm more concerned about real-time vs recording (recording can be delayed and doesn't really matter... cause.... it's recorded based on motion activation via Blue Iris). |
Beta Was this translation helpful? Give feedback.
-
|
my doorbell v1 was off about 10-15 min, restart doorbell with the android wyze app or within the the bridge webui corrected it for now but after some time will go out of sync again. i did not enable audio, unless its enabled by default but i did not do any audio config changes in the bridge, in the mobile app i have disabled the audio for the doorbell |
Beta Was this translation helpful? Give feedback.
-
|
this is weird, i have another doorbellv1 at another location but its time stamp is correct, the one at my house is off and keeps drifting longer oos the longer it runs |
Beta Was this translation helpful? Give feedback.
-
|
the dbv1 that is in sync has fw 4.25.1.316 |
Beta Was this translation helpful? Give feedback.
-
|
This does not require restarting the full bridge to get it back in sync - just reconnecting to the camera(s). If they're all out of sync it might be easier to restart the bridge, but you can also get back in sync by doing any of these:
The least intrusive (and fastest) version is the |
Beta Was this translation helpful? Give feedback.
-
|
Its not only doorbells what getting out of sync. |
Beta Was this translation helpful? Give feedback.
-
|
well its just weird. only one doorbell v1 goes oos, the other dbv1 doesnt and neither of my v3, panv2 or panv3 go oos. |
Beta Was this translation helpful? Give feedback.
-
|
I have to say I was going nuts looking for my issue but then I found this. Glad I wasn't alone. Here's my setup if it helps. Linux Ubuntu (22.04 LTS), Intei I5-7500 (Dell Optiplex SFF), 8GB, SSD Storage. Running in a Docker container. It's really the only container/reason for this PC. Things have been fine up until I did my last update Saturday. It now shows on the GUI that I'm on 2.6.0 but when I do a docker pull for the latest version it's not pulling/installing v2.7 that's recently out. Hope it pulls the newer version soon because the camera that's out IS my front door camera, a Wyze Pan V2. Been working flawless up till this last weekend. According to my (horrible) math, I'd say it's losing 1.4% in the first hour. |
Beta Was this translation helpful? Give feedback.
-
|
the dbv1 that is in sync has fw 4.25.1.316 |
Beta Was this translation helpful? Give feedback.
-
|
still oos |
Beta Was this translation helpful? Give feedback.
-
|
cause of oos could be enabling webrtc, ive since disabled it and its been a few hours and camera seems to be still in sync, and when i come to think of it its when i enabled webrtc is when i noticed i was getting oos on dbv1. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, how do you do this? I did notice my webrtc is set to true but the url is null |
Beta Was this translation helpful? Give feedback.
-
|
i spoke to soon, its getting oos as i writ, took a few hours but im now 30sec oos, ill see if it gets worse. |
Beta Was this translation helpful? Give feedback.
-
|
I don't even have a line for WebRTC in my yaml. I'm trying to nail down when the Sync issues happened here. I've been trying to update my instance, running the yaml which pulls :latest , I'm still stuck on 2.6.0 3 Cams, the only one out of sync is my Pan V2, which had custom firmware before I found WyzeBridge, but has worked flawless since I started using WyzeBridge nearly over a year ago now. This i s interesting. |
Beta Was this translation helpful? Give feedback.
-
|
Happy to report that running 2.6.0 has fixed my camera time slippage issues: I launch my docker a little differently (via command line (.CMD file), so I can run a scheduled task to restart the docker every X hours/minutes). Adding ":2.6.0" at the end 'downgraded' my docker version. "C:\Program Files\Docker\Docker\resources\bin\docker" stop |
Beta Was this translation helpful? Give feedback.
-
|
2.6.0 does seem to keep them very close in time, but I do have to restart the docker container at least once per day. I'd like to be able to have these on a monitor 24/7 without needing to babysit it, I guess the auto restart of the service would be the best route. |
Beta Was this translation helpful? Give feedback.
-
|
how often are you auto rebooting? |
Beta Was this translation helpful? Give feedback.
-
|
I'm playing around with it.... before I downgraded to 2.6.0, it was every 4 hours. Originally I was actually rebooting the whole VM, but by using this code in a CMD I can just have a scheduled task restart and it's much faster. Since I downgraded to 2.6.0, I stopped the task from restarting every 4 hours, and so far the cameras have held steady for well over 48 hours now. I was even going back and putting the old RTSP beta firmware back on the cameras that I could and was preparing myself to just deal with issues I've had with RTSP. Going back to 2.6.0 gave me new hope for stability. (VM running Blue Iris + 12 Wyze Cameras + VM running Docker Desktop) |
Beta Was this translation helpful? Give feedback.
-
|
2.6.0 was a magic bullet here. Time stamps here after running 10 hours are now less than 1 second from the RTC. Just make sure it's actually running and the container is properly updated |
Beta Was this translation helpful? Give feedback.
-
|
How does one install the docker wyze bridge in Home Assistant and get the working 2.6.0 version? 2.7.0 is completely broken, and mrlt8 is nowhere to be found. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not that familiar with git so not sure if you can load it directly from
the site. I had to go into "earlier versions" and download 2.6 to my
windows system, then transfer it over the my raspberry Pi via SFTP.
Possibly someone here can help with an easier method.
If you get stuck, I can send you a Dropbox link that contains 2.6
…On Wed, Feb 28, 2024, 5:53 PM superdong69 ***@***.***> wrote:
How does one install the dockey wyze bridge in Home Assistant and get the
working 2.6.0 version? 2.7.0 is completely broken, and mrlt8 is nowhere to
be found.
—
Reply to this email directly, view it on GitHub
<#1042 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGQKUWYS464DF24W4AIGI3LYV6YN7AVCNFSM6AAAAAA7K7JNIKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DMMRTHE2TI>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
You can specify in the compose file |
Beta Was this translation helpful? Give feedback.
-
|
There is no compose file in home assistant for addons. |
Beta Was this translation helpful? Give feedback.
-
|
+1 to this issue here. I actively monitor cameras to watch a dog elsewhere in the house, as well as for deliveries, so having feed delays are glaring issue here. I moved from RTSP firmware to the modern firmware + wyze bridge in hopes I could use new hardware a week or so ago and have been fighting this since. I currently have three v2 cams (only two active), two v3 cams, and one v2 doorbell deployed. I am running the wyze bridge in UNRAID backed by some number of Xeon X5680 cores. The wyze bridge feeds are being consumed by Frigate on the same UNRAID instance, with a GTX1650 forwarded and six CPU cores pinned to it. There are zero performance issues with Frigate that I can find, and I have gone as far as fully disabling object detection to test this. When running with audio enabled, AAC codec specified, I would get a lot of macroblocking on moving objects. I turned off audio a day or two ago and that appears to have been fixed, but the delay was not fixed. I restarted the bridge this morning and after 1-2 hours it was already out of sync by over a minute. After 1-2 days I approach 30 minutes on some cameras. The cameras that fall out of sync are seemingly random -- nothing to do with wifi signal, version, etc.. I do have a dedicated access point arriving later this week for the cameras to run on, but I don't expect that to fix anything. I have downgraded to 2.6.0 as of this writing and will monitor it throughout today. Currently, the cameras are reporting a spread of 10 seconds on their timestamps. |
Beta Was this translation helpful? Give feedback.
-
|
Downgrading to 2.6.0 fixed my delays. I'm running within 1 second on all my
cams, 6 V3s running off the bridge and my 4 ONVIF cameras connected
directly to Blue Iris.
The only pain is the V3s lose their "home" position and I have to spin up
their app to reset.it.I think the V3s have trouble detecting when the
stepper motors hit their stops and it gets bumped out of position 1 step at
a time.until position error accumulates to a point where the camera is off
90 degrees.
A rookie engineering deficiency since there are ways to prevent this in
either hardware or firmware.
…On Tue, Mar 26, 2024 at 11:16 AM Ian B ***@***.***> wrote:
+1 to this issue here. I actively monitor cameras to watch a dog elsewhere
in the house, as well as for deliveries, so having feed delays are glaring
issue here. I moved from RTSP firmware to the modern firmware + wyze bridge
in hopes I could use new hardware a week or so ago and have been fighting
this since.
I currently have three v2 cams (only two active), two v3 cams, and one v2
doorbell deployed.
I am running the wyze bridge in UNRAID backed by some number of Xeon X5680
cores.
The wyze bridge feeds are being consumed by Frigate on the same UNRAID
instance, with a GTX1650 forwarded and six CPU cores pinned to it. There
are zero performance issues with Frigate that I can find, and I have gone
as far as fully disabling object detection to test this.
When running with audio enabled, AAC codec specified, I would get a lot of
macroblocking on moving objects. I turned off audio a day or two ago and
that appears to have been fixed, but the delay was not fixed.
I restarted the bridge this morning and after 1-2 hours it was already out
of sync by over a minute. After 1-2 days I approach 30 minutes on some
cameras. The cameras that fall out of sync are seemingly random -- nothing
to do with wifi signal, version, etc.. I do have a dedicated access point
arriving later this week for the cameras to run on, but I don't expect that
to fix anything.
I have downgraded to 2.6.0 as of this writing and will monitor it
throughout today. Currently, the cameras are reporting a spread of 10
seconds on their timestamps.
—
Reply to this email directly, view it on GitHub
<#1042 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGQKUW7DXNDOK2IR76ALB4LY2GGNBAVCNFSM6AAAAAA7K7JNIKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSMJWHA2TQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
I updated in the issue here -- 2.6.0 was indeed the fix for me. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks all, I also locked to 2.6 for testing. so far so good. Here is how to do that in UnRaid |
Beta Was this translation helpful? Give feedback.
-
|
"dev" Branche is working i think: |
Beta Was this translation helpful? Give feedback.
-
|
@mrlt8 Done: |
Beta Was this translation helpful? Give feedback.
-
|
But still far behind (more then 10 minutes after more then 2 hours running this 'dev' branche |
Beta Was this translation helpful? Give feedback.
-
|
hmm should say something like |
Beta Was this translation helpful? Give feedback.
-
|
Also in the composefile, there is 'dev' |
Beta Was this translation helpful? Give feedback.
-
Everything i try, keeps saying: |
Beta Was this translation helpful? Give feedback.
-
|
I have determined that when I enable WebRTC, my cameras are nearly spot on once the feed loads in home assistant. I am also utilizing the feed in Mainsail/Klipper (3d printing), and am having very little lag issue there as well. |
Beta Was this translation helpful? Give feedback.
-
|
Did you give the WebRTC link to Scrypted? If so, where? |
Beta Was this translation helpful? Give feedback.
-
so far it is for me. looks like the freakout over "omg no updates, dev has abandoned, my hair is on fire" was unjustified. |
Beta Was this translation helpful? Give feedback.
-
|
I also tried the dev build yesterday, and my cameras were still getting delayed. I also noticed that the mqtt integration seemed to stop working in that time (I did remember to copy the yaml configs from the stable add-on to the dev add-on). I'm not sure why that would be the case, when it worked fine on the stable version. |
Beta Was this translation helpful? Give feedback.
-
|
Will have another look. Is it the audio or the video falling behind? As for MQTT, there were some breaking changes in the latest version of the paho mqtt dependency that needed to be updated. |
Beta Was this translation helpful? Give feedback.
-
|
If that was for me, I have audio disabled, so it should just be video. |
Beta Was this translation helpful? Give feedback.
-
Video falling behind See for your self: |
Beta Was this translation helpful? Give feedback.
-
|
Made a few adjustments to the latest dev build. would appreciate any feedback! |
Beta Was this translation helpful? Give feedback.
-
|
Hello all, I have the same issue with 2.7.0 and would like to try the new builds rather than revert to 2.6.0. I have docker Wyze bridge installed as an add on through HA and not as docker installation. How do I go about pulling the latest build through the add on repository? |
Beta Was this translation helpful? Give feedback.
-
|
I've added the dev builds to the repo, so you should see the option to use the dev image instead. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mrlt8, thank you very much. I see this in my Add-on Store now, with a separate Dev branch button. Going into it, it looks like it is a separate installation and I have to configure DWB all over again. Is this how it should be or am I doing this wrong?
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @mrlt8, I figured it out. I just copied the configuration yaml from the standard DWB and paste it in the Dev Branch version and it worked :) The Dev branch version seems to work much better and faster, with most cameras syncing properly. Only one camera, one of the V3 Pro that is now off by several minutes. My other V3 Pro is synced.
|
Beta Was this translation helpful? Give feedback.
-
|
Made a few adjustments to the latest dev build. would appreciate any feedback! |
Beta Was this translation helpful? Give feedback.
-
It look likes 10 seconds is 10.50 secconds. See for your self: http://j-mulderij.nl:5000/?video == version: '2.4' |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @JA16122000 is the audio drifting as well? Can you disable recording temporarily to eliminate any extra variables? Actually, can you remove/comment out everything after Would also appreciate if you could include the build number from the logs so I can try to pinpoint any negative changes. |
Beta Was this translation helpful? Give feedback.
-
🚀 DOCKER-WYZE-BRIDGE v2.7.0 ARMV7L DEV BUILD [2024-04-19t15:01:20.134z] ac54b8d Audio not testing, i'm not using audio. I have reremoved everything after 'NET_MODE=LAN' Check again: http://j-mulderij.nl:5000/?video Stil time drifting extremely |
Beta Was this translation helpful? Give feedback.
-
hmm, disabling audio seems to introduce some lag to the video. I've made some adjustments to check for slow frames even when the audio is disabled. |
Beta Was this translation helpful? Give feedback.
-
It looks like this is the perfect build @mrlt8 ! `2024-04-20T15:28:51.747220461Z [WyzeBridge] 173.239.217.170 - - [20/Apr/2024 15:28:51] "GET /signaling/achtertuin?webrtc HTTP/1.1" 200 - I DID AN REBOOT 2024-04-20T22:00:55.529257853Z |
Beta Was this translation helpful? Give feedback.
-
|
@mrlt8 timedrifting looks like its related to WebRTC:
You can try your self: http://j-mulderij.nl:5000/?video |
Beta Was this translation helpful? Give feedback.
-
|
Now 2.8.1 is perfect @mrlt8 So 1 is speedy forwarding recording, the otherone is in slomo 🤣 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. Can you open a new issue so we can track it there? |
Beta Was this translation helpful? Give feedback.
-
I'm running 5 Wyze camera's through this docker. Four v3 and one v3Pro. Recently every few days/weeks the camera feed will be delayed 5-15 minutes. The fix is to restart the container. Just updated to v2.5.1, so perhaps this is fixed?
Beta Was this translation helpful? Give feedback.
All reactions