Another try on Time Lapse - successfully ran a 3 hour time lapse that took up 193.17MB w/ 3 second interval.
Going for more.
1 Like
Thanks for catching that. I have corrected the title for both cameras. 
2 Likes
You’re welcome… 
1 Like
Thanks for posting about the new update. I always check to see the release notes, but most of the time there is nothing, so let’s PLEASE keep this trend going.
Have to say since switching from person/vehicle tagging to just person tagging it SUCKS! Does NOT pick up people like it should and they have to be very close it seems to be picked up. What should we expect with this new update?
Also, I notice that people tagging is only cloud rather than triggering motion recording to SD Card. Is this per design.
Of course it’s nice to see continued progress made and it’s easier to pick up on the issues rather than anything. There has always been a lot of good though too which is why we own quite a few of these guys…
The IR lights attract many bugs (insects/arachnids).
One idea to reduce this is to use a external IR illuminator and turn off the camera IR leds.
I think this has to do with the cool down period.
It detect motion (someone arriving in a car) and then by the time the cool down has happened, the person has left the scene.
This defeats the savings of getting the Wyze camera.
I’d like to see an option to exclude motion under X second(s).
All my bugs are quick sub-second blasts.
2 Likes
@mfroader is probably right about the cooldown period. It is supposed to be about five minutes…
I assume from your post you are using event recording instead of continuous to sd card. I use continuous and just use the events as markers to check on things I want to see. I’ve been able to pick up things before and after events I would have not had with event only recording. (Including 3 guys breaking into my car). just a thought.
3 Likes
Tried a 4 hr, it bombed download at 282.12MB
Wow, stress testing!
1 Like
@tom and @tomp
I think you are onto something with the cool down period, however has it been stated that person tagging is a cloud only feature and NOT relating to event recording in SD cards? I suppose that it’s in the “events” area suggests this as a fact.
I literally have “person” tags only when someone is really close to the camera such as leaving in the AM and coming home in the evening. It’s facing the street from the porch and never records a person tag on the sidewalk 40ft away…
If we can’t control the cloud event motion sensitivity or area, then the cloud events will ALL be eaten up by leaves moving in the wind with the cool down period. When the camera is inside it’s less effected, but things like the sun moving throughout the days, shadows triggers as well.
I’ve raised the motion sensitivity with no avail.
I definitely have had SD card recording set to event and not continuous. While that’s been dissapointing, I guess spent less time looking for nothing. At least now that I just changed it to continuous it’s going to be recorded, but finding it will be another story. Would be nice to have a motion graph to view based on higher levels then again probably won’t make a single difference…
Being able to select specific parts of view to track motion rather than just a square will be more effective. Basically blacklist any bush tree which is affected by the wind, etc.
Regardsles, seemed tagging was much more effective when it was both people/vehicles…
@WyzeTao, talk about it - once again it’s creating LARGE .xlog files in WyzePlatformKit. I’ve 4 files that sucked up 9.09 GB.
You know, a gig here, a gig there and pretty soon it adds up to no memory on the device.
There are several threads relating to this on the Forum wishlist. Please go there and vote for all that seem relevent. The wish under one-second-wish has been relegated tp"maybe later "status, so every vote helps
Forgive my ignorance, but do these beta being discussed here include RTSP function?
I’m running the latest RTSP BETA from the links provided in the RTSP thread and generally things are working well with Blue Iris, but all the cams (V2’s and Pan’s) cycle “No Signal” every few minutes. My other WiFi cams are rock solid as is my (UBNT) network. I suppose it could be a BI setting, but I’m running the recommended settings - pretty much what is detected from the RTSP connections.
hey @rjterry21 no worries, this is a learning community. this Beta post is basically for the regular Beta firmware. the Rtsp Beta is different ( as that is a flashed firmware.)
I don’t run the RTSP FW so I’m not going to be a great help to you, but if I’m understanding your issue correctly, maybe chime in on this topic. I did a quick search and these people might be talking about the same issue you are having. if it is the same issue, it looks like the last post was a fix using a different card.
1 Like
Thanks for the info!
The issue I’m having is not the same. The beta RTSP actually fixed the issue discussed in the thread (AFAIK) for me. 4.19.4.48 is the standard RTSP release. I’m on a higher version with the Beta RTSP code(s). Mine don’t require restart or anything, they just momentarily go offline, then come back.
FYI, for anyone interested, V2 is at 4.28.4.40, Pan is at 4.29.4.40
1 Like
Tried updating on my Fire TV Stick. Sorry to say it failed. Perhaps a fluke. I’ll try again in a day or so to see if it goes through at which time I’ll follow up.
Thanks for the wonderful equipment at a great price! It took a bit of research and manipulation to get this working on the Fire TV Stick which is perhaps why the update didn’t automatically work. I may have to go back and install from within ES Explorer.
Hi, the Wyze Skill only works with FTV Stick V2 or higher. Sorry it doesn’t work with FTV Stick v1. From Amazon engineers, the v1 stick has different hardware comparing to v2 or higher. Thanks!
Thank you for getting back to me on this. Yes. I know. However, with a little manoeuvring. I made it work. When I have a moment I’ll do the same with the new version. This time I’ll write down the steps and if it works, I’ll be sure to show you
Thanks again,
Howard
1 Like