Problem downloading from external SSD on the new A329S

[Shred99]

I have a new A329S 2CH dash cam, currently running the v2.0 beta firmware (but the behaviour of viofosync is the same under v1.2 firmware).

When I record to the microSD card, viofosync works as expected.

If I record to an external SSD drive, viofosync appears to read a directory of files from the microSD card, then it throws an error when it tries to download each file (e.g. WARNING: Could not download file.... HTTP Error 404"). I can see that viofosync obtains an XML directory by going to http://{IP address}/?custom=1&cmd=3015&par=1 If I put that URL in a web browser, I can see the XML directory for the microSD drive. None of the files that I know are present on the external SSD are listed. If I browse to the camera directly, I can see the usual DCIM directory containing files - but the files I see are only the ones on the external SSD drive.

There must be an alternative set of parameters to pass after "?custom" that fetches a listing of files on the external SSD, but I do not know what it is. Short of sniffing packets between my smartphone and the dashcam, does anyone know what it is?

[JenChampagne]

@Shred99 I use this dashcam and with SSD for storage as well. I've been trying out the API directly with curl and I noticed that all the file paths I receive from the same custom command as this repository uses start with B: but the code here is expecting to remove A:. I'm guessing microSD gets A: and SSD gets B: since I'm only using SSD and I do not see any A: drive file paths.

I haven't tested it myself, but I think you could change the filter on A: to a filter on B: to get your files off SSD. Or even better the code could filter either/any drive letter instead so that it is flexible with either storage method.

Hope that helps!

[Shred99]

Thanks @JenChampagne. That's useful information. I might need to tinker with it a bit more.

At the moment, I'm just using a rough wget script to scrape the files. It works, but it's not terribly efficient.

[RobXYZ]

Thanks @JenChampagne. That's useful information. I might need to tinker with it a bit more.

At the moment, I'm just using a rough wget script to scrape the files. It works, but it's not terribly efficient.

Sorry I've not looked at this project for a while. I don't have access to an A329S but I will try making some changes to accomodate the different path prefixes.

[Shred99]

I've just tried the "Improvements" version of the docker container.

It's still picking up file names that only exist on the micro-sd card and not on the SSD. It's also inserting a // between the IP address of the camera and the "DCIM".

2026-02-20 17:51:23,882: WARNING Could not download file : 2026_0211_145240_000124PR.MP4 from URL http://192.168.0.101//DCIM/Movie/RO/2026_0211_145240_000124PR.MP4; error : HTTP Error 404: Not Found; ignoring. 2026-02-20 17:51:23,902: ERROR URLError when trying to download file 2026_0213_194305_000125F.MP4 from URL http://192.168.0.101//DCIM/Movie/2026_0213_194305_000125F.MP4: HTTP Error 404: Not Found 2026-02-20 17:51:23,902: WARNING Could not download file : 2026_0213_194305_000125F.MP4 from URL http://192.168.0.101//DCIM/Movie/2026_0213_194305_000125F.MP4; error : HTTP Error 404: Not Found; ignoring. 2026-02-20 17:51:23,918: ERROR URLError when trying to download file 2026_0213_194305_000126R.MP4 from URL http://192.168.0.101//DCIM/Movie/2026_0213_194305_000126R.MP4: HTTP Error 404: Not Found 2026-02-20 17:51:23,918: WARNING Could not download file : 2026_0213_194305_000126R.MP4 from URL http://192.168.0.101//DCIM/Movie/2026_0213_194305_000126R.MP4; error : HTTP Error 404: Not Found; ignoring. crond[14]: crond (busybox 1.36.1) started, log level 8

[RobXYZ]

Ah that branch was just my personal test. I saw that bug but ran out of time.

Looks like I built that docker from the wrong commit. I've just rebuilt it so could you try again?

I'm interested to know whether the new html scrape works better than the xml as well.

[Shred99]

Ok. I've switched back to viofosync:latest and I still have the same problems:

• Viofosync is only attempting to download the files that are on the internal micro-sd card
• It's barfing on each file because there is a // after the IP address in the URL

2026-02-28 09:46:06,054: WARNING Could not download file : 2026_0213_194305_000125F.MP4 from URL http://192.168.0.101//DCIM/Movie/2026_0213_194305_000125F.MP4; error : HTTP Error 404: Not Found; ignoring. 2026-02-28 09:46:06,070: ERROR URLError when trying to download file 2026_0213_194305_000126R.MP4 from URL http://192.168.0.101//DCIM/Movie/2026_0213_194305_000126R.MP4: HTTP Error 404: Not Found 2026-02-28 09:46:06,070: WARNING Could not download file : 2026_0213_194305_000126R.MP4 from URL http://192.168.0.101//DCIM/Movie/2026_0213_194305_000126R.MP4; error : HTTP Error 404: Not Found; ignoring. crond[14]: crond (busybox 1.36.1) started, log level 8

[RobXYZ]

viofosync:latest hasn't got the fixes yet.

I've replaced the improvements tag with viofosync:dev to make the different versions clearer.

If you're able to confirm viofosync:dev is working for your camera I'll merge those changes into the main branch. Try setting the HTML env variable if it doesn't work from the XML

[Shred99]

Thanks - I've deleted the container image and switched to viofosync:dev.

The behaviour is still the same, in that the script continues to only list the files present on the built-in micro-sd card. It does not list any of the files that are on the SSD drive.

2026-03-06 17:50:14,591: ERROR Failed to download 2026_0211_142240_000121PF.MP4 after 1 attempts
2026-03-06 17:50:14,611: WARNING Download attempt 1 failed for 2026_0211_145240_000123PF.MP4: HTTP Error 404: Not Found
2026-03-06 17:50:14,612: ERROR Failed to download 2026_0211_145240_000123PF.MP4 after 1 attempts
2026-03-06 17:50:14,631: WARNING Download attempt 1 failed for 2026_0211_145240_000124PR.MP4: HTTP Error 404: Not Found
2026-03-06 17:50:14,631: ERROR Failed to download 2026_0211_145240_000124PR.MP4 after 1 attempts
2026-03-06 17:50:14,650: WARNING Download attempt 1 failed for 2026_0213_194305_000125F.MP4: HTTP Error 404: Not Found
2026-03-06 17:50:14,651: ERROR Failed to download 2026_0213_194305_000125F.MP4 after 1 attempts
2026-03-06 17:50:14,670: WARNING Download attempt 1 failed for 2026_0213_194305_000126R.MP4: HTTP Error 404: Not Found
2026-03-06 17:50:14,670: ERROR Failed to download 2026_0213_194305_000126R.MP4 after 1 attempts

If I manually connect to the camera via browser, I can see the current files listed. None of the file names listed in the output from Viofosync are shown in the web browser and it correctly lists the files that I know are on the external SSD.

If I browse to http://[192.168.0.101/?custom=1&cmd=3015&par=1](http://192.168.0.101/?custom=1&cmd=3015&par=1) The XML output DOES list the filenames that appear when I run Viofosync ( and that I know are on the MicroSD card ).

[RobXYZ]

I think this is normal. My camera reports files which aren’t there, at least not by the time it tries to download, so I get a few 404 errors for old files but it should carry on to the next available file.

Is it downloading anything? You could try setting PRIORITY = rdate to download the newest first.

Could you copy and paste an example urls for mp4s from the web interface just to make sure it's in the expected path? e.g. http://192.168.0.101/DCIM/Movie/Parking/2025_1120_122541_000002PR.MP4 . I was hoping the html scrape would get around this as it takes the url from the html interface so try HTML = 1 if you haven't already.

[Shred99]

The script doesn't download a single file. If I run my dodgy wget shell script, it spends a couple of hours downloading files (I only do a download once per week).

Here is the path for a recent .mp4: (and I verified that the link actually fetches a playable movie file):

http://192.168.0.101/DCIM/Movie/2026_0306_172816_007940R.MP4

And a still image / jpg:

http://192.168.0.101/DCIM/Photo/2026_0306_145135_007913PF.JPG

Edit: if it helps, this is how I currently download using wget:

  -nd -r --no-clobber \
  -e robots=off \
  --reject "index.html*" \
  -P /mnt/g/viofo \
  http://192.168.0.102/DCIM/Movie/

[Shred99]

I was hoping the html scrape would get around this as it takes the url from the html interface so try HTML = 1 if you haven't already.

Bingo. That fixed it. I've just run my weekly dump of files and starting the Docker container with "-e HTML=1" worked a treat. Thank you.