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.
The CAM folder doesn't mount anywhere... the pi makes a connection to your shared folder and then transfers the files to the shared folder.Anyone who has this working on a Mac care to share their config? I can't for the life of me get a CAM folder to mount in my shared directory using CIFS 3.0, 2.1, 2.0 and 1.0. Maybe I'm doing something wrong on the server side? Thanks.
The CAM folder doesn't mount anywhere... the pi makes a connection to your shared folder and then transfers the files to the shared folder.
So on your mac, you share a folder, then in your teslausb config you give it the IP address of your mac, the username and password of a mac user that can access the shared folder.
What does the log say on the pi?
Well, specifically, I think you also have to drill into System Preferences and turn on (I think) File Sharing under the Network applet. I'll try to remember to dig out my Mac and get some screenshots for you to help with enabling CIFS shares.
That's not how it will work. You will need to set up the folder share on the Mac, then add the settings in the tesla config file on the Pi with all the details to point to the Mac folder.Anyone who has this working on a Mac care to share their config? I can't for the life of me get a CAM folder to mount in my shared directory using CIFS 3.0, 2.1, 2.0 and 1.0. Maybe I'm doing something wrong on the server side? Thanks.
# Default variables for CIFS (Windows/Mac file sharing) setup
export ARCHIVE_SYSTEM=cifs
export archiveserver=[IP Address of Your Mac]
export sharename=[Name of the Shared Folder You Created]
export shareuser=[Mac User That You Gave Access to the Shared Folder]
export sharepassword=[Password of the Mac User]
# export cifs_version="3.0"
Yes. That is correct.the Pi will automatically clear out (delete) recordings once they have been archived to my network storage?
The firmware update solved it for me as well.I was using this setup for a while but like many, started getting the bandwidth error almost consistently (lucky to get 1 hour of use before the error). This was with a Samsung Endurance SD card and Buster on a Zero W. However, a few weeks ago I followed the recommendation of performing a firmware upgrade and configuring the cam and music partitions to still leave some unused space on the card and that fixed it! Not a single bandwidth error since then! Only issue is twice the pi appeared to have crashed during bootup as the dashcam never started recording (car never saw the drive appear). A quick unplug/plugin and it was back to normal. Overall, I'm very happy with this solution. Way better then the previous setup I had with a Verbatim WiFi dongle that I had to switch on at home and have a service running on my home network to detect and pull files. Having an automated solution is great!
Nobody has implemented that yet to my knowledge. You would have to do the following...Quick question (sorry if it has been asked and answered): Can I view these video files from the Pi Zero in Tesla's browser? i.e. load a list of the videos and instead of just offloading to a remote drive/computer/cloud - actually view them in the browser. I think that is more useful to many if you want to view your sentry videos when you see the notification in the car.
There's one more thing. The car will not connect to a wireless network that does not provide Internet access.Nobody has implemented that yet to my knowledge. You would have to do the following...
- Redirect the car to connect to your Pi Zero over wifi. And if you shift from Park to Drive you have to reconnect manually every time you drive. Bonus points if your Pi Zero has a mobile SIM and can still pass thru regular traffic.
- Install a local web server on the Pi Zero. And build a page that can see the local files.
- Use an HTTP layer on the Pi Zero that allows for remapping of a URL. And remap one URL to the local server. Essentially a man-in-the-middle attack.
Seems someone has done it, sort of. On a non-Pi Pi-ish thing.
Little project by me (with TeslaCam Browser) to … - teslamotors - Reddit
Sounds like they just had to provide fake DNS results in addition to running an access point so that the test for internet connectivity succeeds.
Of course there's the hassle that probably this interrupts all network functionality in the car (since it would try to use this connection that isn't really connected), so you'd have to then disconnect when done, and ensure somehow that it doesn't automatically connect repeatedly due to seeing the AP there...
They haven't yet provided any details on their setup but it sounds like they intend to eventually release the code and/or image for the device.
This is something I wanted to test out myself but haven't gotten a chance to do so.
The car is likely doing more than just a DNS resolve check. The car could be using a hardcoded IP to check for connectivity. I'll wait to see how the person is doing it from the Reddit post.It's easy enough to look those up and hard-code them in a DNS server such as bind. Or it might be as easy as throwing them into the hosts file, depending on how the system does the DNS check.
You'll need to run your own DNS server on the Pi that the DHCP service tells the Tesla to use when it connects to the AP, and configure it to hand out pre-defined results (i.e., the Pi's address) for those queries, and then have whatever relevant service responding (likely simple ping, or perhaps HTTP - clearly not HTTPS as otherwise it wouldn't be spoofable).Here are the servers the car attempts to reach. Both the 3 and the X hit these addresses when coming online.
www.teslamotors.com
str01-prd.vn.tesla.services
maps-prd.go.tesla.services
telemetry-prd.vn.tesla.services
connman.vn.tesla.services
hermes-prd.vn.tesla.services
hermes-stream-prd.vn.tesla.services
I threw these into the Pi's hosts file as loopbacks (127.0.0.1) and the car still won't connect to a non-Internet enabled wireless network on the Pi.