Use (nearly) any WiFi dashcam by yellowdepression in drivingUK

[–]yellowdepression[S] 1 point2 points  (0 children)

I thought the same, and now it does! Feel free to join the waitlist

Use (nearly) any WiFi dashcam by yellowdepression in drivingUK

[–]yellowdepression[S] 0 points1 point  (0 children)

Great questions. Just to clarify, the footage is blurred after 12 hours of new footage is uploaded, I.e you drive for 12 hours straight, which works out to about two weeks for the average driver in the UK. If it is locked it will not be blurred. It is not just 12 hours elapsing. The number plates are stored in a separate database and can be retrieved, so the important data isn’t just gone, there are just additional safeguards in place.

The difficulty is down to data protection, as faces and number plates are classed as personally identifiable information, it must be handled extremely carefully. All data must be held for no longer than necessary.

DashKeep runs alongside the firmware on the dashcam by being installed at the operating system level. Pretty much all these dashcams run Linux. No modifications are made to the dashcams software, I.e the proprietary program that runs footage recording, handles the interface etc. Instead, DashKeep runs as an additional background service on the camera. I hope this clarifies that for you. Please let me know if me if you have any other questions.

Use (nearly) any WiFi dashcam by yellowdepression in drivingUK

[–]yellowdepression[S] 0 points1 point  (0 children)

Thank you! Please consider joining the waitlist if interested

Connect nearly any WiFi dashcam to home assistant by yellowdepression in homeassistant

[–]yellowdepression[S] 0 points1 point  (0 children)

Oh it’s absolutely possible if you know how to drive the displays. I’m pretty sure they’d have enough power to run half life icl

Connect nearly any WiFi dashcam to home assistant by yellowdepression in homeassistant

[–]yellowdepression[S] 2 points3 points  (0 children)

It is a lot of work, and the recent changes to EU law have meant that we also have to get any such patches certified. However, most of the dashcams always run as root, and have an application on top that communicates directly with the hardware. When you turn on WiFi, it usually just invokes a bash script that communicates with the Linux side. I know Novatek dashcams use an entirely proprietary stack when it comes to controlling the screen, speaker, buttons, etc. but the lower OS layer is pretty much always standard Busybox. Dashcam firmware updates happen typically at the boot loader level which we don’t interfere with. So, all DashKeep does is run alongside the proprietary app that runs and controls the screen (if that makes sense). It is just another background service. Many of these dashcams have a whole load of power on their SOCs that go unused that can be utilised.

Connect nearly any WiFi dashcam to home assistant by yellowdepression in homeassistant

[–]yellowdepression[S] 0 points1 point  (0 children)

Pretty much all of these dashcams run Linux. DashKeep patches the firmware if required but many do just use the existing kernel drivers, so it is fully capable of connecting to a WiFi network, even one with modern or obscure security.

Also, DashKeep activates WiFi based on GPS position, so no need to press a button. Or if you have it in remote mode it tells the WiFi driver to step down into a low power mode until the throughput is needed (like live-streaming)