Replies: 4 comments 11 replies
-
See #38 and #58
(correct decimal position) |
Beta Was this translation helpful? Give feedback.
-
I did the following with success:
#!/bin/sh Obviously you will have to update the date manually and update /configs/.time_checkpoint (this is so you don't continue overwriting your SD card mp4 files if you have that turned on in the .user_config file). This is a complete offline solution. |
Beta Was this translation helpful? Give feedback.
-
be careful with the files in /configs/, some are generated unique for each camera. If these files (that have keys), are deleted or corrupted, in my testing the cameras will never connect to the cloud server (they will fail authentication, as the keys are generated by the factory for each camera uniquely), either initially or ever again. |
Beta Was this translation helpful? Give feedback.
-
Very true, the above is for a complete offline solution only as the OP requested. Do NOT ever mess with the .product_config file or it’s backup which has an MD5 hash in the filename. And if you decide to put cam online, before you do, remove only the following files from /configs: .wifi* Then disable wz_mini temporarily by renaming the factory* file on the root of the SD card then reboot and use the Wyze app as if it’s a brand new cam. After Wyze provisioning you can re enable wz_mini |
Beta Was this translation helpful? Give feedback.
-
Excuse the noob post but I have a brand new wyzecam v3 that has yet to be powered up and I'm wondering if i can use wz_mini_hacks to get the camera on my LAN and broadcasting via RTSP without installing the wyze app on my phone, setting up a wyze account, etc. Is this possible?
Beta Was this translation helpful? Give feedback.
All reactions