You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
How’s the performance nowadays? I tried it a year ago with a Pi Zero W but it was just too slow and limited to 1 MB/s transfer speed no matter what settings I used. This despite having strong WiFi signal and my NAS hardwired to my router. It took 2-3 hours to finish transferring files from a brief drive back then. I got fed up waiting for a particular file I wanted to view and went back to an SSD. I read a Pi 4 transfers files at 4MB/s but even that is painfully slow by today’s standards.Hi @dub1ous ,
I have recently installed the Teslausb system on my 2018 Model X.
I am on 2022.4.5.21 and I have used the latest marcone github image.
It is teslausb-20211106
It was a pain to setup but it works well now...
He does support a partition for music files.
I followed the troubleshooting instructions with the files on Github.
I did need extra help because I am not an SSH person.
Marcone was very fast to respond to my rookie questions.
He has a WONDERFUL WEB INTERFACE... Easily accessed by the command http://teslausb
Where "teslausb" is the default name in the package or whatever you decided to name your Raspberry Pi
it in your setup file...
I use "cifs" to transfer the files using a Windows (10) file share on my laptop...
I used to use "Roadies" but the Teslausb is more robust and error tolerant.
I currently backup even the "RecentFiles" and I use Sentry to keep the power
on while the backup or transfer is occurring...
The software is currently compatible with Raspberry Pi Zero W, Raspberry Pi Zero 2 W,
and Raspberry Pi 4. There is a good equipment list under another project "Sentry DashCam for Teslas."
The app is in the Apple App store - I just used it for an equipment list.
I like the Raspberry Pi Zero 2 W...
Good luck,
Shawn
=============================================
Sat 1 Jul 20:30:11 EDT 2023: Time adjusted by 7969.076416 seconds after 0.170000 seconds
Sat 1 Jul 20:30:11 EDT 2023: not keeping car awake.
Sat 1 Jul 20:30:11 EDT 2023: Archiving...
Sat 1 Jul 20:30:11 EDT 2023: Ensuring cam archive is mounted...
Sat 1 Jul 20:30:11 EDT 2023: Mounting /mnt/archive...
Sat 1 Jul 20:30:11 EDT 2023: Mounted /mnt/archive.
Sat 1 Jul 20:30:12 EDT 2023: Ensured cam archive is mounted.
Sat 1 Jul 20:30:12 EDT 2023: Checking saved folder count...
Sat 1 Jul 20:30:12 EDT 2023: There are 0 event folder(s) with 0 file(s) and 0 track mode file(s) to move. 0 short recording(s) will be skipped.
Sat 1 Jul 20:30:12 EDT 2023: Ensuring cam file is mounted...
Sat 1 Jul 20:30:12 EDT 2023: Disconnecting usb from host...
Sat 1 Jul 20:30:12 EDT 2023: Disconnected usb from host.
Sat 1 Jul 20:30:13 EDT 2023: Mounting /mnt/cam...
Sat 1 Jul 20:30:13 EDT 2023: Mounted /mnt/cam.
Sat 1 Jul 20:30:13 EDT 2023: Ensured cam file is mounted.
Sat 1 Jul 20:30:13 EDT 2023: cleaning cam mount
Sat 1 Jul 20:30:15 EDT 2023: done cleaning cam mount
Sat 1 Jul 20:30:15 EDT 2023: Trimming free space in /mnt/cam, which has 5 extents
Sat 1 Jul 20:30:15 EDT 2023: Trim complete, image now has 5 extents
Sat 1 Jul 20:30:15 EDT 2023: Unmounting /mnt/cam...
Sat 1 Jul 20:30:15 EDT 2023: Unmounted /mnt/cam.
Sat 1 Jul 20:30:16 EDT 2023: Finished archiving.
Sat 1 Jul 20:30:16 EDT 2023: Music archive not configured or unreachable
Sat 1 Jul 20:30:16 EDT 2023: unmounting /mnt/archive
Sat 1 Jul 20:30:16 EDT 2023: Connecting usb to host...
Sat 1 Jul 20:30:16 EDT 2023: Connected usb to host.
Sat 1 Jul 20:30:21 EDT 2023: Waiting for archive to be unreachable...
====== summary ======
hardware: Raspberry Pi Zero W Rev 1.1
OS: Raspbian GNU/Linux 10 (buster)
CIFS archiving selected
lun0 connected, from file /backingfiles/cam_disk.bin
1 snapshots mounted
Gadget state: not attached. 44.9 seconds ago: mass storage ready, but not connected to host (check cable)
====== disk / images ======
Model: SD JD4RT (sd/mmc)
Disk /dev/mmcblk0: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 4194kB 266MB 262MB primary fat32 boot, lba
2 266MB 2414MB 2147MB primary ext4
3 2414MB 128GB 126GB primary xfs
4 128GB 128GB 105MB primary ext4
cam disk image has 5 extents
Model: (file)
Disk /backingfiles/cam_disk.bin: 114GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 114GB 114GB primary fat32 lba
no music disk image found
no boombox disk image found
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p1 247M 49M 199M 20% /boot
/dev/root 2.0G 1.2G 683M 63% /
/dev/mmcblk0p3 117G 895M 116G 1% /backingfiles
/dev/mmcblk0p4 95M 1.6M 86M 2% /mutable
TeslaUSB doesn't use a USB stick, it uses the SD Card installed in the rPi. What's probably happening with you is the car is using the USB Stick and ignoring your TeslaUSB, because it will be ready before the TeslaUSB, which has to boot Linux before it's ready. Unplug the USB stick, and it should start working.
Like I said, the rPi takes time to boot. a few minutes. I generally have to wait until I turn a corner or two before the x changes to a red light.That makes sense. Somehow I was under the impression that the SD card was used as intermediate storage between the raw files from the USB drive and the copying off the car via Teslausb.
Is there a process I show follow to have the car see the RPI and SD after I remove the USB key? Currently I get the x on the dash cam icon and pressing it says “Dashcam unavailable, check USB drive”
A bit of a late reply but I’ve only just got hold of a pi zero 2w and installed TeslaUSB tonight. I used the most recent marcone image which is teslausb-20211106 but I believe it downloads more recent updates when you install it on the SD card.Just found this thread after looking all over to see if a solution for this was still alive. Which version are you guys using that still works today?
# If you're a TeslaFi user, you may prefer to keep your car wake using TeslaFi API
# instead. The advantage is not having to expose Tesla's Token and other info in this
# file as plain text, which is a vulnerability should this file gets compromised.
# The TeslaFi API token can easily be revoked and a new one generated at anytime.
# TeslaFi also allows selective command(s) enablement (e.g. wake only), further
# decreasing vulnerability.
#
# GENERATE/REVOKE TESLAFI API TOKEN: To generate the token, log into your TeslaFi account.
# Navigate to Settings -> Tesla API -> API Token (tab)
#
# ENABLE/DISABLE TESLAFI API COMMANDS: Verify the command(s) of interest (e.g. wake) is
# Navigate to Settings -> Tesla API -> Commands (tab)