Has anyone made an
infographic flowchart illustrating the confirmed design functionality of these cams and their features? I mean, making all these semi-informed assumptions and inferences which are sometimes confirmed and sometimes corrected and often not is, um, MADNESS.
What are the
base functions, how do the different parts work together, what is dependent on what, what is discrete, etc.
Lense > video
Mic > sound
RAM > volatile storage
SD > permanent storage
Wireless Comms > remote storage
I am willing to
pay $5 send a brand new Wyze Cam v2 Black to the person who creates an elegant, inclusive depiction of the design, functions and features of this little cube.
What are ya afraid of, fella? Clarity?
An ideally designed SD event detection system operating flawlessy would be effectively equivalent to SD continuous recording because motion within any single minute would be detected and recorded.
If motion visible but too subtle to register occurred during any minute nothing would be recorded during that minute and context it may have provided for the prior or succeeding minutes will be absent.
If continuous recording were made the only option the problem for the devs would be to make detecti…
It’s clear to me that the Wyze business plan (lowest price possible, highest customer interaction, i.e., make friends of your customers) effectively supports the low price of the hardware by leveraging the free labor of its customer base in the extensive troubleshooting (development) of its products.
So you are induced to purchase by the initial low price, are seduced by the friendly responsiveness to “help out” in product development/troubleshooting. You-can-pay-me-now (the real cost of a fi…
Hey Loki, do you happen to recall seeing a graphic flowchart one customer posted to a thread about 30-45 days ago? It addressed mainly necessary handshake interactivity between app, cam and servers if I remember correctly. Shoulda bookmarked it.
Sorry, no, don’t recall that.
If someone will provide the “confirmed design functionality” I can provide the graphic design part… not sure if you’d need to cut the cam in half vertically or horizontal tho
Joint custody? Visitation rights?
This is buried deep in TLDR territory, so…
I’m impressed with Wyze’ enthusiasm for direct, informed, public criticism. It makes claims and backs them up. Well done.
Is this essentially correct? What have I got wrong or left out?
Along these lines of needed graphics -
I’d really like to see a pdf of the directory structure and the menu structure.
Hardcopy can be helpful.
Hey gemniii, definitely agree. And hardcopy - I sketch it out in pencil (with a big gum eraser handy) before I start doing the digital.
Here’s a quick snapshot of the directory structure - there are sub-directories below these.
And the 3rd party app (an archiver with basic file management) the screenshot’s from. No ads and reasonable permissions:
Those rascals, they DO use graphics -
Somewhere (internally) lies the matrix from which stuff like this is spawned. ::sigh::
Thanks for contacting Wyze Cam Support
I looked over the RouteThis test and it is showing some slower speeds and connection quality issues.
Red lines are data loss (dropped packets)
This maybe due to the DSL connection you are using. DSL technology is around 20 years old and not setup for smart home technology. We have had some customers be able to use the Wyze Cam with some issues here and there on their DSL but it most cases it is slow. I know in some areas this is the only option and that can make things difficult.
Nice manual with graphics blooming here:
Well done, Matthew!