API login/Basic fails on 1.50.1 for installer

[rstad944]

For the last 16 months I have been able to use /api/login/Basic with username=installer.

Yesterday my PW firmware was updated from 1.49.0 to 1.50.1 and my code fails at login with the response:
{"code":401,"error":"roles [Provider_Engineer] require physical access","message":"Login Error"}

There is also a new screen when installer is selected in the Kiosk. It states that the PW switch must be toggled (as proof of physical access, I presume).

Any ideas?

[spoonwzd]

I too had this issue yesterday when the new firmware went on. I don't think there's a way around it using the local gateway now they have introduced physical confirmation.

I've switched my code over to using the public API now, which actually seems to work better as the process doesn't stop the Powerwall from operating when making a change like with the local gateway. Changes to reserve seem to be instant too.

See: https://www.teslaapi.io/powerwalls/commands

API endpoint: https://owner-api.teslamotors.com/

• Use /oauth/token to get the authentication token (check the docs as there's some extra content that needs to go in the JSON)
• Get the info you need about your Powerwall from /api/1/products (you're after your energy_site_id)
• Use /api/1/energy_sites/energy_site_id/operation to set operation mode (if you need to)
• Use /api/1/energy_sites/energy_site_id/backup to set the backup reserve percent

I figured it would be tidy to revoke the token upon completion with /oauth/revoke but I just get a 404 at that URL.

Hope this helps.

[BJReplay]

@spoonwzd can you share how you do this? I assume that the reserve percentage is a parameter on the call? The API doco doesn't have this detail. e.g. is it /api/etc/backup?reserve=10 or api/etc/backup/reserve/10?

[HeraldCoupe]

This is so annoying but perhaps inevitable.

[spoonwzd]

You simply POST the backup_reserve_percent value in JSON to the /api/1/energy_sites/energy_site_id/backup API URL along with the authorization bearer @BJReplay

This is how I'm doing it in node-red with a custom JavaScript function:

msg.headers = {
Authorization: "Bearer " + MY_AUTH_TOKEN,
"content-type": "application/json"
}
msg.method = "POST"
msg.url = "https://owner-api.teslamotors.com/api/1/energy_sites/MY_SITE_ID/backup"
msg.payload = {
"backup_reserve_percent": 77
}

[HeraldCoupe]

You simply POST the backup_reserve_percent value in JSON to the /api/1/energy_sites/energy_site_id/backup API URL along with the authorization bearer @BJReplay

This is how I'm doing it in node-red with a custom JavaScript function:

msg.headers = {
Authorization: "Bearer " + MY_AUTH_TOKEN,
"content-type": "application/json"
}
msg.method = "POST"
msg.url = "https://owner-api.teslamotors.com/api/1/energy_sites/MY_SITE_ID/backup"
msg.payload = {
"backup_reserve_percent": 77

I don't suppose you've got something similar for changing modes have you?

[spoonwzd]

I don't suppose you've got something similar for changing modes have you?

I haven't tried changing the mode, but I'm going to assume it's just the same as the above example, just use /api/1/energy_sites/energy_site_id/operation and set "mode" in the JSON payload with "self_consumption" or whatever you're looking to set.

[BJReplay]

Ahh, so annoying. I'm testing using postman and I'm getting

{
    "response": null,
    "error": "https://powergate.prd.sn.tesla.services:443/api/powerwalls/MY_GATEWAY_ID/backup => Method Not Allowed",
    "error_description": ""
}

In response to:

Method: POST
URL: https://owner-api.teslamotors.com/api/1/powerwalls/MY_SITE_ID/backup 
Headers: as noted above (Bearer & auth token, content-type)
Body: {"backup_reserve_percent": 10}

[spoonwzd]

Is it that you need to be setting reserve at 'energy_sites' not 'powerwalls' @BJReplay ?

[BJReplay]

@spoonwzd Yes! Thanks! Right. powerwalls for getting status (or maybe that works with energy_sites too - will try), energy_sites for setting status.

[spoonwzd]

@spoonwzd Yes! Thanks! Right. powerwalls for getting status (or maybe that works with energy_sites too - will try), energy_sites for setting status.

Nice. :) I'm still getting live power flow stats from the local gateway as I don't want to be hammering the public API.

[BJReplay]

@HeraldCoupe Yes, I have:

POST to https://owner-api.teslamotors.com/api/1/energy_sites/YOUR_INTEGER_SITE_ID/operation
Headers:
Authorization Bearer as above
Content-Type application/json
Body:

{"default_real_mode":"self_consumption"}
or
{"default_real_mode":"backup"}

[spoonwzd]

Great work everyone :)

[HeraldCoupe]

Yes, great work and thank you. I'll have a go at this myself in the coming days.
The next question is.... how long before Tesla stop us from using this API too?

[HeraldCoupe]

@HeraldCoupe Yes, I have:

POST to https://owner-api.teslamotors.com/api/1/energy_sites/YOUR_INTEGER_SITE_ID/operation
Headers:
Authorization Bearer as above
Content-Type application/json
Body:

{"default_real_mode":"self_consumption"}
or
{"default_real_mode":"backup"}

Brilliant, thank you.
I've made progress today, I can get the token and energy_site_id so I'll move onto getting the mode then I'll attempt to set the mode.

[HeraldCoupe]

You can use "https://owner-api.teslamotors.com/api/1/energy_sites/YOUR_INTEGER_SITE/site_info" to get "backup_reserve_percent", "default_real_mode" as well as "storm_mode_enabled" and a bunch of other potentially useful bits of info.
It requires the usual authorization bearer stuff.