Thank you. It's perfectly safe. The system is resilient to disconnections for any reason, and will resume where it left off at the first opportunity.@acolomba what is the result of "driving away" from home network while a cron/download is currently in progress? is it "safe" to do a dirty disconnect like this?
thanks for all the great work on this .. I can't wait to get this going.
This is awesome, works exactly as advertised.Thank you. It's perfectly safe. The system is resilient to disconnections for any reason, and will resume where it left off at the first opportunity.
This is awesome, works exactly as advertised.
I have 2 questions:
1) It is possible to obtain the battery voltage from the device somehow?
2) Is it possible to obtain the direction and magnitude of the "impact" forces for any particular "event"? Side/Front/Up?
Thanks
That's right. You would run one instance per dashcam. As long as the two instances write to different directories, they are completely isolated from each other.Thanks heaps for this, it works incredibly well with my new BlackVue 900x running in Docker on my UnRaid box.
I was wondering if it works with more than one dashcam at the same time? I would think you have to run 2 docker containers, one for each of the BlackVue's, and pointing to separate directories to save, but that should work, right?
2023-01-15 15:50:01,582: ERROR [Errno 17] File exists: '/recordings'
Traceback (most recent call last):
File "/blackvuesync.py", line 657, in run
ensure_destination(destination)
File "/blackvuesync.py", line 453, in ensure_destination
os.makedirs(destination)
File "/usr/lib/python3.9/os.py", line 225, in makedirs
mkdir(name, mode)
FileExistsError: [Errno 17] File exists: '/recordings'
Is that an extra colon after the word 'dashcam' there? That doesn't look right to me. Then the '/recordings' part after is being misinterpreted by the API call.volumes:
# Recording download destination. Change only the part before the colon.
- /mnt/dashcam:/recordings:rw
Thanks.
Thanks for looking.Is that an extra colon after the word 'dashcam' there? That doesn't look right to me. Then the '/recordings' part after is being misinterpreted by the API call.
# Recording download destination. Change only the part before the colon.
- /mnt/dashcam:/recordings:rw
Its all good; managed to figure it out. If anyone wants the script I can upload! Thank you so so much
Thank you for writing this, I needed something like this as the location the installer put the base in is very hard to reach.Hello All,
I made a new BlackVue recording LAN downloader. I've been using it for several months now, and it's ready for public consumption.
GitHub: https://github.com/acolomba/blackvuesync
Docker Hub: https://hub.docker.com/r/acolomba/blackvuesync
Features:
TL;DR: Set it up once, forget about it.
- Portable runtimes:
- A single, self-contained Python script with no third-party dependencies. It can be can be copied and run anywhere, either manually or periodically.
- A docker image that runs periodically via an internal cron job.
- Smart: Only downloads recordings that haven't been downloaded yet.
- Resilient: If a download interrupts for whatever reason, at the next run the script resumes where it left off. This is especially useful for possibly unreliable Wi-Fi connections from a garage.
- Hands-off: Optionally retains recordings for a limited amount of time. Outdated recordings are automatically removed.
- Cron-friendly: Only one process is allowed to run at any given time for a specific download destination.
- Safe: Stops executing if the disk is almost full.
- Friendly error reporting: Clearly communicates a range of known error conditions with sensible verbosity.
Should you find any bugs or wish to suggest new features, please submit an issue on GitHub (https://github.com/acolomba/blackvuesync/issues).
Edit: If you don't have GitHub account, feel free to respond here instead.
Enjoy!
___
Alessandro
Good afternoon. I am using Mint as my OS.Hello All,
I made a new BlackVue recording LAN downloader. I've been using it for several months now, and it's ready for public consumption.
GitHub: https://github.com/acolomba/blackvuesync
Docker Hub: https://hub.docker.com/r/acolomba/blackvuesync
Features:
TL;DR: Set it up once, forget about it.
- Portable runtimes:
- A single, self-contained Python script with no third-party dependencies. It can be can be copied and run anywhere, either manually or periodically.
- A docker image that runs periodically via an internal cron job.
- Smart: Only downloads recordings that haven't been downloaded yet.
- Resilient: If a download interrupts for whatever reason, at the next run the script resumes where it left off. This is especially useful for possibly unreliable Wi-Fi connections from a garage.
- Hands-off: Optionally retains recordings for a limited amount of time. Outdated recordings are automatically removed.
- Cron-friendly: Only one process is allowed to run at any given time for a specific download destination.
- Safe: Stops executing if the disk is almost full.
- Friendly error reporting: Clearly communicates a range of known error conditions with sensible verbosity.
Should you find any bugs or wish to suggest new features, please submit an issue on GitHub (https://github.com/acolomba/blackvuesync/issues).
Edit: If you don't have GitHub account, feel free to respond here instead.
Enjoy!
___
Alessandro
2023-11-15 22:30:37,256: ERROR [Errno 13] Permission denied: '/recordings'
Traceback (most recent call last):
File "/blackvuesync.py", line 657, in run
ensure_destination(destination)
File "/blackvuesync.py", line 453, in ensure_destination
os.makedirs(destination)
File "/usr/lib/python3.9/os.py", line 225, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/recordings'
crond[16]: crond (busybox 1.34.1) started, log level 8
Variable:
Value:
ADDRESS
192.168.1.132
CRON
1
DRY_RUN
GROUPING
KEEP
MAX_USED_DISK
PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PGID
100
PRIORITY
PUID
1000
QUIET
well I got around the issue using the docker compose file . I had to edit the destination location from /mnt/ to /share/CACHEDEV1_DATA/xxxxxxok, need a hand.....not sure what's broken but I seem to have a permission issue.
QNAP NAS pulling the docker from the library
I verified access to the dash cam . I'm using below for my environmental