Skip to main content

 Kaluza access to your Tesla Account

Shouldn't they only need access to: charging location, commands to schedule, start, and stop charging

 

Rather than basically ownership of my car?

Kaluza for some reason needs access:

Vehicle Information

Vehicle live data, location, eligible upgrades, nearby superchargers, ownership, and service scheduling data

Vehicle Commands

Commands to access Sentry, *****add or remove driver, unlock, wake up, remote start, and schedule software updates****

Vehicle Charging Management

Vehicle charging history, billed amount

That’s just how the Tesla system works.

Just because Kaluza is allowed to do that, doesn’t mean it will. It’s up to you. Accept the permissions and use Charge Anytime, or deny them and don’t use it. In real terms, much of that actually makes sense given the use case. Kaluza can’t talk to a Tesla that’s gone into deep sleep after all… It’s possible that Wake Up is only accessible via that group and not by itself.

Likewise, the vehicle live data and location stuff is crucial to knowing what vehicle you’ve connected and whether it’s charging at home or not. Without that, CA won’t know what to do. By knowing whether the Tesla is at home, the system will know whether it should step in or not. If it knows you’re away, it’ll disable the schedule and let the Tesla charge immediately. If it knows you’re at home, the Smart Charging schedules will kick in and give you the cheap rate.

Vehicle Charging Management is required to schedule and manage Smart Charging, while Vehicle Charging History is required in order to access the data needed to calculate how much power the Tesla has used while charging at home.

Alternatively, connect to the Charger instead and Kaluza will have no access to your Tesla.

After looking at the Tesla email and follow the embedded link about permissions, you can unselect these options.

 

Just because Kaluza is allowed to do that, doesn’t mean it will.

Still is a security concerns, OVO would be in better stead should they advise the above if indeed it is a Tesla issue as they point out.

That’s just how the Tesla system works.

Thanks for your answer but it's inaccurate.

https://www.tesla.com/developer-docs

Users should be advised that they are able to remove some privileges.

 

Just because Kaluza is allowed to do that, doesn’t mean it will. It’s up to you. Accept the permissions and use Charge Anytime,

My question was not about Charge Anytime.

  deny them and don’t use it.

Its not an all or nothing option as you suggested 

In real terms, much of that actually makes sense given the use case. Kaluza can’t talk to a Tesla that’s gone into deep sleep after all… It’s possible that Wake Up is only accessible via that group and not by itself.

What are you even talking about here (citation required)

Likewise, the vehicle live data and location stuff is crucial to knowing what vehicle you’ve connected and whether it’s charging at home or not. Without that, CA won’t know what to do. By knowing whether the Tesla is at home, the system will know whether it should step in or not. If it knows you’re away, it’ll disable the schedule and let the Tesla charge immediately. If it knows you’re at home, the Smart Charging schedules will kick in and give you the cheap rate. 

I didn't ask this and I don't have a cheaper rate

Vehicle Charging Management is required to schedule and manage Smart Charging, while Vehicle Charging History is required in order to access the data needed to calculate how much power the Tesla has used while charging at home.

Alternatively, connect to the Charger instead and Kaluza will have no access to your Tesla.

What does this even mean?

 

 

'

Hi @coffeeunspilt,

 

I’ve asked the team about this. They’ve responded saying:

 

“Kaluza needs data so we can see if they're charging at home and their charging data. We need this as they're only eligible for CA credits for home charging and we need to see how much charge they have done on smart charge in order to credit effectively”.

 

Hope this is helpful.

Reply


Terms & ConditionsCookie settings