Rendered at 10:21:41 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
thejazzman 1 days ago [-]
PSA: If your wall connector loses wifi, it'll just throw your charging schedules out the window and turn on/off sporadically. This is especially noteworthy if you have Time of Use billing :| SET THE TIMER ON THE CAR DIRECTLY!
eleveriven 1 days ago [-]
It also fits the broader theme here: too much important behavior seems to live in the "application layer" of the charger, while the more durable source of truth is elsewhere.
chrisandchris 3 hours ago [-]
I have a Volvo. Twice a year when DST changes, the schedule is afterwards one hour off. Been this for 3 years now.
rblatz 1 days ago [-]
I spent an hour yesterday getting the wall connector back on my wifi. Apparently last October when I added wifi 7 access points my network started working in WPA2/WPA3 mode and the wall connector wasn’t compatible with that. Ended up having to create a second SSID with WPA2 only support to get it back online.
Supposedly the newest update fixes that, but I haven’t taken the time to test that out.
But WiFi is shocking my fragile on these wall connectors, I’ve had a lot of trouble keeping it connected to my home network over the years.
f001 21 hours ago [-]
Does the tesla wall connector offer Ethernet? Honestly I feel like most devices that are not expected to move around should at least offer it as an option (exceptions being for things where it’s not feasible like smart bulbs, smart locks, etc). If anything it’ll remove congestion for things that can’t realistically be wired.
a10c 1 days ago [-]
or, use Home Assistant to handle your charging schedules.
Your comment makes no sense. The tesla wall connector is a home charging port you install in your garage.
compounding_it 1 days ago [-]
I knew this is about wall charger at home but I assumed ‘time of use billing’ was some kind of billing system for the charger that’s implemented.
lexicality 1 days ago [-]
some people have variable electrical tariffs, so electrical use in the middle of the night is usually much much cheaper than the middle of the day.
pjc50 1 days ago [-]
That's done on the property's electricity smart meter.
m463 1 days ago [-]
I hate the gen 3 wall connector.
It creates a wifi access point in your garage that you cannot turn off:
TeslaWallConnector_<unique-id>
some people were able to downgrade their firmware to a version that didn't do that, but i guess this article shows telsa got rid of that ability.
I would love to be able to hack any firmware to disable that.
I also read that a connected tesla car can force an over-the-air firmware update maybe through the charging cable or wifi, but I haven't verified that.
ralph84 1 days ago [-]
The SSID stops broadcasting after the unit is commissioned, unless you're using power sharing between multiple units. In that case the SSID is used for the units to communicate.
m463 1 days ago [-]
by commissioned you mean "connect it to your home wifi and let it talk to tesla"? (i won't do that)
because it hasn't gone away after configuring the setup stuff (amps, etc)
darkwater 23 hours ago [-]
Yes, obviously. If you didn't want that, you should have bought another charger, maybe Bluetooth only, and add your home-grown layer on top of it.
elteto 19 hours ago [-]
Can I ask why don't you want a Tesla charger talking to Tesla? Seems a bit odd if you already own a Tesla vehicle that is just piping the data to Tesla all the time.
BuildTheRobots 22 hours ago [-]
Is it possible to connect it to your wifi but block it talking to the internet? I'd be curious to know if that stops the built in SSID.
Rohansi 1 days ago [-]
Mine did
ralph84 1 days ago [-]
And make sure the firmware is up to date. Mine is at 26.2.2.
iugtmkbdfil834 1 days ago [-]
Thank you. This information is not listed anywhere and I am currently getting quotes for solar panel build.
jp191919 20 hours ago [-]
I put mine on an isolated IOT network.
1 days ago [-]
cryptoegorophy 1 days ago [-]
Why use Tesla wall connector in a first place and not just the standard nema/dryer outlet with the Tesla cord/charger? It seems like people are overpaying for nothing.
doublepg23 15 hours ago [-]
I did a lot of research on
home charging at r/evcharging and the consensus always favored hardwiring your EVSE if possible.
jp191919 20 hours ago [-]
It costed less for me to install a tesla wall connector over a NEMA receptacle, as the NEMA 14-30 and 14-50 require a neutral wire and a GFCI breaker.
tenuousemphasis 1 days ago [-]
I can do 48A @ 240V with my wall connector. It's also very convenient.
thechao 22 hours ago [-]
I do as well with a NEMA?
grosswait 22 hours ago [-]
I don’t think the mobile charger allows more than 32A continuous over NEMA, even on a 50A receptacle
bluGill 20 hours ago [-]
There are a lot of different mobile chargers, if you don't like the specs on the Tesla charger buy a different one. Though do beware that cheap 50A receptacles cannot handle 50 amps continuous. They are for stoves (max 40A), or welders (low duty cycle since you spend more time in setup then welding - assembly lines use better receptacles)
MiscIdeaMaker99 21 hours ago [-]
I can confirm this. Our Model 3 doesn't charge as fast using a NEMA 14-50 plug connected via the Tesla-provided mobile charger.
When we moved to a new house, we bought a Tesla wall charger, and it indeed charges at higher amps, but I don't know if the extra speed has necessarily been worth it since we primarily charge the car overnight.
elteto 19 hours ago [-]
Do dryer outlets work outdoors?
stronglikedan 19 hours ago [-]
You don't want to use a standard outlet, since it's not designed to handle full current(?) for hours. There are special outlets for EV charging, and they work outdoors. Just be very sure to have a GFCI breaker behind it.
jp191919 19 hours ago [-]
They do. As long as installed properly with a GFCI breaker.
spacebanana7 1 days ago [-]
One thing I'm really scared of is EV charger software being modified by users, hackers or bugs to pull max power at times that don't suit the grid.
In the UK, for example 10 million EVs all pulling 7kw would overwhelm the roughly 70GW potential of the grid. Even a million EVs charging at an inconvenient time could add a 7GW draw which is enough cause a problem.
neilalexander 18 hours ago [-]
Incoming voltage monitoring is a requirement for EV chargers in the UK. The sudden huge demand would result in a voltage drop, the chargers would then detect the under-voltage condition and they'd stop charging.
spacebanana7 17 hours ago [-]
Would the voltage drop before the fuse blew in local transforms?
Modern grids have batteries to manage instantaneous spikes of demand so there’d be a race.
ac29 18 hours ago [-]
I've never seen a charger in the US that doesnt operate 24/7 regardless of grid load, is this different in other countries?
braiamp 23 hours ago [-]
It will first damage the batteries very fast, second, most users don't want to mess with that, they want to plug and play. So, on both counts your fears are misplaced.
spacebanana7 22 hours ago [-]
In the event of an internet outage, wall box chargers are legally required to default on. In practice most chargers interpret this as taking the full 7kw - whether this is a bug or misreading of the intent of the law doesn't really matter from the perspective of the grid.
Large ISP outages that affect millions of people are not uncommon on a decade by decade basis, and I suspect an uncomfortable number of UK EV chargers are in some way linked to eu-west-2.
It sounds like a genuine attack vector to me. If someone hacked say teslas firmware supply chain and made all chargers pull max power at the same time, it could be a national infrastructure crippling attack.
throwway120385 18 hours ago [-]
Where would they dump the power? You need a load of some sort. 7kW requires a voltage drop between a hot and a neutral. If it's a 1V drop then you're going to get a hot load of amps.
alt227 17 hours ago [-]
Into what it was designed for, maybe.... a car?!
Im thinking in an attack situation hackers might plan for say a 3am mass dump and pull on the grid by all cars that are charging overnight. This would definitely be possible by altering firmware, and would be bad enough to blow some local substations for sure.
spacebanana7 17 hours ago [-]
I may be misunderstanding your concern but the idea would be for Tesla to dump the energy into car batteries or powerwall storage.
1 days ago [-]
mystraline 1 days ago [-]
Repeat after me:
An owner voluntarily downgrading firmware to gain control of your hardware IS NOT A HACK.
And if an adversary is doing this, then they have already breached yoir physical security.
wolrah 1 days ago [-]
This exploit is delivered through the charging cable to the wall box. These wall boxes are sometimes intentionally located in public spaces with the intent of allowing public charging, and Tesla has features specifically for that use case, so that cable is absolutely expected to be plugged in to untrusted vehicles.
_flux 1 days ago [-]
It clearly seems people have different meanings to the word, then.
For example, if I am able to gain root access to a WiFi access point I own, even though the vendor has tried to prevent it, then yes, I would call it a hack. To me, it doesn't matter why or who is doing the steps.
In fact, I believe I have never before heard someone combine the meaning of the word to be related to the ownership of the device being hacked.
I suspect the number of people understanding the word in your way is a minority. Redefining terms doesn't help build mutual understanding: here we are taking a word some think has negative connotations and then remove the thing they think should be cool and ok, and then suggest that this is actually the real meaning of the word. Personally I don't think this is how words should be wielded.
wtallis 15 hours ago [-]
> In fact, I believe I have never before heard someone combine the meaning of the word to be related to the ownership of the device being hacked.
Ownership implies authorization, and using the term "hacking" exclusively to refer to gaining unauthorized access to someone else's computer is a common usage that you must surely have encountered before.
oneshtein 1 days ago [-]
> For example, if I am able to gain root access to a WiFi access point I own, even though the vendor has tried to prevent it, then yes, I would call it a hack.
Yep. The owner of the device can sue you.
alt227 21 hours ago [-]
Why would they sue themselves?
NooneAtAll3 16 hours ago [-]
that's the point? it's not a hack because you own the device, thus it's nonsensical
abofh 1 days ago [-]
It's a car the charging port is a viable physical perimeter, letting people inject code at the pump is a risk of design, not user error.
zelon88 1 days ago [-]
I thought the same thing. How white hat do you have to be to consider ineffective DRM a vulnerability?
1 days ago [-]
kube-system 1 days ago [-]
Eh, that’s a bad generalization. defense in depth is a thing and there are many cases where you’d want to protect against attackers with physical access
zelon88 1 days ago [-]
This isn't designed to stop attackers with physical access. This is designed to stop casual tinkerers and shade tree mechanics.
You know what isn't vulnerable? A "dumb" offline charger. You know what doesn't make any money or turn the consumer into another product? A "dumb" offline charger.
If it were about physical security, the suggested fix would be to remove the communication from the port entirely.
Companies shouldn't get to make something simple and secure into something inherently insecure and then iterate security into it. Like drive by wire steering, or brakes. Nobody asked for these things and if you ask ANYONE who works on, builds, or actually enjoys cars the consensus is NOBODY wants it.
But there are enough sophomoric, pedestrian car owners out there who gawk at the senseless overdeployment of technology and think "this is so convinient" and don't see it as 1) regulatory barrier building and gatekeeping 2) enabling vendor lock in 3) overcoming right to repair legislation. So the knowledgeable and enthusiastic voices of reason who care about cars get drowned out by the hoard of pedestrian geeks who couldn't imagine operating a car without at least a 16 inch touchscreen.
In security, the best defense is not introducing a vulnerability at all. There is value in having less code. For example, if your PaaS doesn't collect user SSNs... then it can't lose SSNs in a breach.
The question here should not be "why is this not secure." The question should be "why does this even need to be secure in the first place?" We have a very simple task to do and we've complicated it so much we've introduced vulnerability that didn't exist previously.
kube-system 21 hours ago [-]
I was commenting on the hasty generalization, not this specific case.
> If it were about physical security, the suggested fix would be to remove the communication from the port entirely.
You can’t charge without negotiating charging rates. Communication is a requirement. Every EV does this. Heck, every cell phone does this.
> Like drive by wire steering, or brakes. Nobody asked for these things and if you ask ANYONE who works on, builds, or actually enjoys cars the consensus is NOBODY wants it.
Every hybrid and EV for the past 20 years has brake by wire. That’s how regenerative braking works.
AlotOfReading 1 days ago [-]
Any system where your defense in depth involves UDS is pretty much guaranteed to be broken though.
pram 1 days ago [-]
They shouldn’t be able to do it through the charging cable though lol
taneq 1 days ago [-]
Arguably it’s a crack. A good one, though.
aussieguy1234 1 days ago [-]
I mean its still technically hacking, but not all hacking is bad/illegal.
1 days ago [-]
486sx33 1 days ago [-]
Why would I want to hack the bootloader for a wall charger? Asking for a friend
culi 1 days ago [-]
You can bypass vehicle restrictions. You could potentially then use it for J1772-compatible EVs (like a Chevy Bolt or Nissan Leaf)
Or just for the spirit of actually owning the shit you pay for.
m463 1 days ago [-]
I don't think there are any restrictions. I think j1772 might just work with an adapter (adapt from the nacs plug to the j1772 plug)
I thought tesla even made a j1772 native wall connector.
mprime1 1 days ago [-]
There are some restrictions.
I had the foolish idea of installing a Tesla charger at home to charge my Bolt. I’ve been unable to ever use it.
The wall charger works fine with Teslas.
My car and adapter charge fine at Tesla superchargers.
But the home Tesla charger refuses to charge my Bolt.
(Yes I disabled vehicle restrictions and tried all sorts of combinations of settings for weeks before giving up. Tesla support was useless of course)
Restriction or bug, same difference.
doublepg23 15 hours ago [-]
A NACS to CCS (L3) adapter won’t work with L2 chargers, you’ll need a NACS to J1772 adapter.
They make a "universal charger" for this express purpose. It even has the adapter embedded in the holster, so you can either grab just the NACS connector, or the connector + J1772 adapter in one smooth motion.
Just don't try to use that adapter on another NACS connector like the Mobile Connector, it'll get stuck and you'll have to do some magnet shenanigans to get it off (ask me how I know...)
NACS on Level 2 has the same number of pins, but speaks a different protocol than J1772, so just a normal "dumb" adapter won't work. You either need a Connector that can speak J1772, or a TeslaTap.
tass 12 hours ago [-]
If you’re using the same adapter successfully at a supercharger, you have the wrong adapter for AC (level 1/2) charging.
cogman10 1 days ago [-]
Really gross. I have a gen 1 charger and it's dumb as bricks. Basically just a giant relay.
I guess I could see why you might want to restrict who can use your charger, but I really prefer the "dumb as bricks" version I currently have.
gwbas1c 21 hours ago [-]
> I thought tesla even made a j1772 native wall connector.
At least a few years ago, they would openly recommend it for non-Teslas.
I thought NACS brought some changes to Level 1 and 2 that aren't backwards compatible with J1772? I know there's an oddball voltage in there so you can put a NACS charger on a lamppost where J1772 would require a transformer; but I didn't think there were protocol issues too.
bluGill 20 hours ago [-]
J1772 is 120V or 208-240V. Those are by far the most common voltages in the US. (208 is what you get when you take a US 3 phase system and connect to two phases - this is somewhat common and most people don't know or care that their apartment is wired like that). I have seen other voltages at industrial sites, but I wouldn't expect that in a lamppost.
gwbas1c 9 hours ago [-]
277 volts, which is line to neutral in a 480 volt three-phase system. It's common for lamp posts in parking lots.
J1227 would require a transformer, but NACS doesn't.
akerl_ 1 days ago [-]
Can confirm. I've used an adapter to charge 2 different non-Tesla cars off my wall connector.
adamsb6 1 days ago [-]
I use my Gen 1 Tesla Wall Connectors to charge my NACS-native Lucid Gravity.
decimalenough 1 days ago [-]
What vehicle restrictions? This is for the Tesla home charger, not Superchargers.
culi 1 days ago [-]
Older models are locked to Tesla vehicles. Tesla has regional restrictions in many parts of the world.
You also never know when there could be another update and your region becomes one of those that has these restrictions.
Rebelgecko 1 days ago [-]
Some don't support j1772 adapters with non Tesla vehicles
brianwawok 1 days ago [-]
Exactly. Charge both my Tesla and my leaf with mine.
ashoeafoot 1 days ago [-]
[dead]
NewJazz 1 days ago [-]
Implement your own payment provider
fc417fc802 1 days ago [-]
To play doom on it?
kotaKat 1 days ago [-]
Publicly accessible piece of equipment that could have a pseudo-trusted connection to an internal network (since they're connected to the Tesla Cloud(tm)).
Picturing someone rolling up to a charger outside of a large office building, 'plugging in', exploiting the charger via the communications, then using the charger to pivot inwards.
Supposedly the newest update fixes that, but I haven’t taken the time to test that out.
But WiFi is shocking my fragile on these wall connectors, I’ve had a lot of trouble keeping it connected to my home network over the years.
It creates a wifi access point in your garage that you cannot turn off:
some people were able to downgrade their firmware to a version that didn't do that, but i guess this article shows telsa got rid of that ability.I would love to be able to hack any firmware to disable that.
I also read that a connected tesla car can force an over-the-air firmware update maybe through the charging cable or wifi, but I haven't verified that.
because it hasn't gone away after configuring the setup stuff (amps, etc)
When we moved to a new house, we bought a Tesla wall charger, and it indeed charges at higher amps, but I don't know if the extra speed has necessarily been worth it since we primarily charge the car overnight.
In the UK, for example 10 million EVs all pulling 7kw would overwhelm the roughly 70GW potential of the grid. Even a million EVs charging at an inconvenient time could add a 7GW draw which is enough cause a problem.
Modern grids have batteries to manage instantaneous spikes of demand so there’d be a race.
Large ISP outages that affect millions of people are not uncommon on a decade by decade basis, and I suspect an uncomfortable number of UK EV chargers are in some way linked to eu-west-2.
[1] https://www.legislation.gov.uk/uksi/2021/1467/regulation/7/m...
Im thinking in an attack situation hackers might plan for say a 3am mass dump and pull on the grid by all cars that are charging overnight. This would definitely be possible by altering firmware, and would be bad enough to blow some local substations for sure.
An owner voluntarily downgrading firmware to gain control of your hardware IS NOT A HACK.
And if an adversary is doing this, then they have already breached yoir physical security.
For example, if I am able to gain root access to a WiFi access point I own, even though the vendor has tried to prevent it, then yes, I would call it a hack. To me, it doesn't matter why or who is doing the steps.
In fact, I believe I have never before heard someone combine the meaning of the word to be related to the ownership of the device being hacked.
I suspect the number of people understanding the word in your way is a minority. Redefining terms doesn't help build mutual understanding: here we are taking a word some think has negative connotations and then remove the thing they think should be cool and ok, and then suggest that this is actually the real meaning of the word. Personally I don't think this is how words should be wielded.
Ownership implies authorization, and using the term "hacking" exclusively to refer to gaining unauthorized access to someone else's computer is a common usage that you must surely have encountered before.
Yep. The owner of the device can sue you.
You know what isn't vulnerable? A "dumb" offline charger. You know what doesn't make any money or turn the consumer into another product? A "dumb" offline charger.
If it were about physical security, the suggested fix would be to remove the communication from the port entirely.
Companies shouldn't get to make something simple and secure into something inherently insecure and then iterate security into it. Like drive by wire steering, or brakes. Nobody asked for these things and if you ask ANYONE who works on, builds, or actually enjoys cars the consensus is NOBODY wants it.
But there are enough sophomoric, pedestrian car owners out there who gawk at the senseless overdeployment of technology and think "this is so convinient" and don't see it as 1) regulatory barrier building and gatekeeping 2) enabling vendor lock in 3) overcoming right to repair legislation. So the knowledgeable and enthusiastic voices of reason who care about cars get drowned out by the hoard of pedestrian geeks who couldn't imagine operating a car without at least a 16 inch touchscreen.
In security, the best defense is not introducing a vulnerability at all. There is value in having less code. For example, if your PaaS doesn't collect user SSNs... then it can't lose SSNs in a breach.
The question here should not be "why is this not secure." The question should be "why does this even need to be secure in the first place?" We have a very simple task to do and we've complicated it so much we've introduced vulnerability that didn't exist previously.
> If it were about physical security, the suggested fix would be to remove the communication from the port entirely.
You can’t charge without negotiating charging rates. Communication is a requirement. Every EV does this. Heck, every cell phone does this.
> Like drive by wire steering, or brakes. Nobody asked for these things and if you ask ANYONE who works on, builds, or actually enjoys cars the consensus is NOBODY wants it.
Every hybrid and EV for the past 20 years has brake by wire. That’s how regenerative braking works.
Or just for the spirit of actually owning the shit you pay for.
I thought tesla even made a j1772 native wall connector.
I had the foolish idea of installing a Tesla charger at home to charge my Bolt. I’ve been unable to ever use it.
The wall charger works fine with Teslas. My car and adapter charge fine at Tesla superchargers.
But the home Tesla charger refuses to charge my Bolt. (Yes I disabled vehicle restrictions and tried all sorts of combinations of settings for weeks before giving up. Tesla support was useless of course)
Restriction or bug, same difference.
This is the one I use https://ev-lectron.com/products/lectron-tesla-to-j1772-adapt...
Just don't try to use that adapter on another NACS connector like the Mobile Connector, it'll get stuck and you'll have to do some magnet shenanigans to get it off (ask me how I know...)
NACS on Level 2 has the same number of pins, but speaks a different protocol than J1772, so just a normal "dumb" adapter won't work. You either need a Connector that can speak J1772, or a TeslaTap.
I guess I could see why you might want to restrict who can use your charger, but I really prefer the "dumb as bricks" version I currently have.
At least a few years ago, they would openly recommend it for non-Teslas.
I thought NACS brought some changes to Level 1 and 2 that aren't backwards compatible with J1772? I know there's an oddball voltage in there so you can put a NACS charger on a lamppost where J1772 would require a transformer; but I didn't think there were protocol issues too.
J1227 would require a transformer, but NACS doesn't.
You also never know when there could be another update and your region becomes one of those that has these restrictions.
Picturing someone rolling up to a charger outside of a large office building, 'plugging in', exploiting the charger via the communications, then using the charger to pivot inwards.