Recent content by otherslackjaw

I'm reasonably confident that at some point Tesla will offer V2X on new cars. I hope they change their stance on it before too long as it's going be so important to the future grid.

Has this broken anyone else's boot? Mine is only opening an inch most of the time, it occasionally opens all the way but very aggressively. Then it slams shut. A two button rest hasn't fixed it so I'll put a service request in.. Thanks for the reminders to re enable camera based sentry on all...

Same here, from 28.1. No issues.

I think the sentence is the same in the Model 3 manual, but I always read it as if they would adjust. I assume that if you got pulled over (however unlikely) someone could take a dim view of the headlights 'not requiring adjustment' as the beam pattern would illuminate the opposing carriageway...

I know that has always been the case, contrary to what the manual says. I live in hope that one day an auto adjustment will sneak in with an update.

Glad you had a good time! So, did the headlights "mirror" themselves so that they flicked up on the right instead of the left?

They do not. They get a bit of regen but it is increasingly limited above 80% SOC.

Good news! I managed to get a manual backup to work by running it from the correct .yml directory thanks to the comment above. I now have a 138mb backup with all my data. And I managed to get my teslamate instance back up and running again. I'll have another play around with the automated google...

This jogged a memory and I ran the below to see what docker-compose files I've got where. root@teslamate:/usr/local/bin# whereis docker-compose docker-compose: /usr/local/bin/docker-compose /usr/local/bin/docker-compose.yml root@teslamate:/usr/local/bin# ls -l total 11980 -rwxr-xr-x 1 root...

I'm running it on Google Cloud. I appreciate it is a bit strange to use a pi style backup location, but I was trying to follow DaveW's guide and decided it was easier to keep as close as possible to how he'd written it, than to keep altering commands to suit my slightly different implementation.

Messing around with it and trying to get the backup script to run. I kept getting this error (below) and my docker-compose file seemed to not have an extension so I think I ended up duplicating it to docker-compose.yml. Unhelpfully I don't remember what I did. If I'd been taking snapshots of the...

Good catch, I've now done this but it's not made a difference to the backup via the normal pg_dump command. EDIT to say I should double check this in the morning just in case. Here is the output on pastebin as it was too big for the forum. I just used 'database', not 'db'.

Yeah that would make sense but it doesn't seem to. I've tried before but here it is written down: Here is what I've tried and what I get as an output: root@teslamate:~# docker-compose exec -T database pg_dump -U teslamate teslamate > /home/pi/tmbackup/teslamateA.bck Error response from daemon...

This looks to successfully give me an output of my data, line by line, thank you. The dates are all in the right period. Here's the header, I won't post a shot of the data in case the position IDs can be reverse-engineered somehow. Do you know how I can pull this as a CSV or something that I...

So you can, here it is properly as I can't edit my post any longer. Name Command State Ports ---------------------------------------------------------------------------------------------------------...