Exporting logs

A support request usually needs logs, and getting them takes about a minute:

1. On the camera, open the advanced menu: press the Wi-Fi button twice.
2. Move to the About tab: short presses of the Wi-Fi button step through the tabs.
3. Double-press the LOCK button to open the log view.
4. A long log goes straight to the memory card, and the screen shows the filename, like dk20260919175951.log.
5. Power the camera off, put the card in your computer, and the file is at the root of the card.

Attach the file to your message in the support chat. The log contains technical events, such as upload attempts, connection errors, and restarts. The log never contains footage.

Cameras without a screen

The steps above use the advanced menu, which cameras with no screen, like the VS1, don’t have. Those cameras still write a few files to the root of the card on their own: boot.log, plus dashkeepagent-errors.log and dashkeep-malfunction.log if anything goes wrong. Copy those onto your computer and send them, and support can pull the full log from there.

Two more files can end up at the root of the card. dashkeepagent-errors.log shows up if the agent ever crashes, and dashkeep-malfunction.log records failures to talk to the camera’s own recording software. Send those too if they exist.

Files every camera writes to the card

Two small files at the root of the card record what happened on the last boot. Send both with any support request about a camera that will not start or will not connect:

• dashkeep-launcher.log: what the DashKeep launcher found when the camera powered on. One line says whether it verified the DashKeep app on the card and started it, or why it did not (for example, verify FAILED (code 3)), in which case the camera runs the maker’s own firmware as a fallback.
• dashkeep-status.txt: what the DashKeep app itself saw: its build, which camera model it detected, whether it read its settings file, what happened with each Wi-Fi attempt, and whether it reached the DashKeep cloud.

Both files are rewritten on every boot, so they always describe the most recent start. They never contain footage, Wi-Fi passwords, or device keys.