search

matfra / isitfoggy.today

Few scripts to setup a timelapse camera
11 stars 2 forks source link

new feature for Sfwem #24

Open mathisono opened 4 years ago

mathisono commented 4 years ago

Thanks for putting this on the mesh! I would like to build a setup on a rpi4.

Request: add archive upload of the daily video to a google drive, to keep an long running archive.

Request: Local access to the current image, and indicator showing when the next photo will be taken.

Idea: Setup the image flow that accepts, a multi camera photo merge to create a large panorama for the time laps?

Im wondering how long the on-board archiving lasts? If I can turn it off.

matfra commented 2 years ago

I'm only reading this now, but better late than ever I guess. Feature request 1: It would be nice to have the archive backed up on Google drive. This is very doable with a bit of python.

Feature request 2 For the local access to the current image, there is already download button, we could add a link to today's directory I guess. For the counter until the next image, we can certainly approximate it by publishing the sleeping time from snap.sh in a temporary text or json file in $TMP_DIR and link that to the html dir. From there a javascript running on the client side can read the info and display a countdown based on it. Not too difficult to implement. With the same principle, we could surface more even more things in the future if needed.

For the multi camera merge, I think this is a difficult endeavor, for having made panoramas myself, it requires quite a lot of processing and automating it would be challenging.

For the onboard archiving, 1 year of data takes between 30 and 40GB. So with a 200GB microsd car we can fit between 5 and 6 years. I figured that by that time I'd have a better archiving solution in place. The oldest directory will then be wiped out to make room for the new ones. Hence the importance of a backup.

matfra commented 2 years ago

By the way @mathisono If you are still interested to install a camera I would be happy to take some time to help you set it up. I know that a couple of friends were able to successfully set it up but there are still lots of little hard coded things and scripts to edit to make it work in a different environment than mine.

mathisono commented 2 years ago

I ended up writing a crawler script and a rendering script, One retrieves stills from various networked cameras starting every minute. Still imagery images gets rendered every hr, until the end of the day at midnight. I synchronize the the file system with syncthing between 5 computers, around the mesh, one is a hot backup for rendering(Rpi4 with external storage), 2 serve the stills and .mp4 on a web page, one crawls imagery with another checking on the first to see if its still reachable, if not its starts running the crawler script. The Rpi4 takes about 30min with ffmpeg to finish rendering ~12 cameras by the end of the day! I have a NUC that Im going to start transition to test rendering, I expect it to improve! I like a Rpi4 because I can run one with POE 24v passive. I have a script to cleanup min stills at the end of the day. Im still manually off loading the daily mp4's. (It gives me a chance to look thru some of the imagery) I thought I liked https://github.com/odeke-em/drive Do you have ant thoughts on google drive synchronization, for pushing the imagery to the cloud...!