Skip to content

Conversation

@BJReplay
Copy link
Contributor

Add second entry for Tesla in the Hall of Shame - Tesla Powerwall

Description

The Tesla Gateway firmware versions after 24.36.2 cause Gateway 1 gateways to forget any customer password within about an hour of going through the I forgot my password password reset process.

This locks out Home Assistant once the login cookie expires (or HA is restarted), and requires turning off the Powerwall, going through the reset process again, and saving the new password. It effectively renders the HA Core Tesla integration useless for these devices.

Type of changes

  • Add/update an entry
  • Text cleanups/updates
  • Test updates

License Acceptance

  • This repository is Attribution-NonCommercial-ShareAlike licensed and by making this PR, I am contributing my changes to the repository under the terms of the CC BY-NC-SA license. See License for more details.

Checklist

  • I included a description and/or links in the new entry's garbage column describing why it is garbage.
  • All new and existing tests pass.
  • I have confirmed that the link(s) in my PR are valid.
  • I added my entries in alphabetical order
  • My entry is a single line. This makes it easier to keep the list sorted since we can use our editor's sort feature instead of having to manually move multi-line stanzas around.

Cosmetics

Please keep the entries in alphabetical order. Once the list gets larger, that'll make it easier for people to find things.

Make each entry a single line in the table. This lets me sort entries more easily since I can just use an editor's sort function instead of having to manually move entries around.

Add second entry for Tesla in the Hall of Shame - Tesla Powerwall.

Signed-off-by: BJReplay <[email protected]>
@BJReplay BJReplay force-pushed the BJReplay-patch-add-tesla-powerwall branch from 8f2d081 to dc821d9 Compare January 26, 2025 05:25
@lhovo
Copy link

lhovo commented Jan 26, 2025

Have you tried using the serial number as the password?
https://www.tesla.com/en_au/support/energy/powerwall/own/connecting-network

For Backup Gateway 1 and Non-Backup Gateway, your serial number (found in the Tesla app) is also the password.
Note: If you enter your password manually, it begins with the letter S. If the serial number on the sticker does not begin with the letter S, you must add the letter S before typing the serial number (e.g. STG123456789123).

@BJReplay
Copy link
Contributor Author

BJReplay commented Jan 26, 2025

Have you tried using the serial number as the password?

No, (well, other than to test if it works after the gateway has forgotten the password I have set - it does not).

The password was set by me on the day of installation roughly seven years ago.

It has been maintained by me as required, up until this firmware.

The issue is not that I don't know the password, or that I can't set the password, but rather that one set, I can only use it for about an hour until it is no longer recognised by the gateway.

@lhovo
Copy link

lhovo commented Jan 26, 2025

My suggestion is:
If the serial number works without preforming the reset, at least it’s a way forward.
It does suck that you are unable to use your own set password.

I feel like this is a bug / regression and not intentional feature. I would recommend reaching out to Tesla and see if they can fix it.

@BJReplay
Copy link
Contributor Author

If the serial number works

Sorry I wasn't clear - the Serial number does not work. Full Stop.
It doesn't work as a default password.
It doesn't work after a reset.
It doesn't work to log in.
It doesn't work if you attempt to set the password to the Serial Number - as it doesn't meet the complexity requirements for passwords.

I'm sorry @lhovo that you think my problem isn't real, but unless you have a Gateway 1 on firmware 24.36.2 or later, you won't have seen the problem.

Here's a seven page thread from other users with the same issue: https://teslamotorsclub.com/tmc/threads/unable-to-log-into-gateway-after-24-36-2-update-work-around-found.336050/

Here are specific posts about the specific issue and what it takes to reset it each time it fails: https://teslamotorsclub.com/tmc/posts/8553031/

And that it doesn't stick: https://teslamotorsclub.com/tmc/posts/8559236/ and https://teslamotorsclub.com/tmc/posts/8565577/

Copy link
Owner

@unixorn unixorn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@unixorn unixorn merged commit 5170646 into unixorn:main Jan 27, 2025
3 checks passed
@lhovo
Copy link

lhovo commented Jan 27, 2025

Just to clarify, it’s not that I think your problem is real. I’m just trying to help resolve it.
I’m an owner of gateway 2, and to restrict gateway 1 users but not gateway 2 seems a very strange. Thus I feel it’s a bug they have introduced and not intentional.
Hence my suggestion to report it.

I had a someone respond to me using the support link found on this page.
https://www.tesla.com/en_au/support/energy/powerwall/own/troubleshooting

Not sure if there is a similar page for your country.

@BJReplay
Copy link
Contributor Author

Not sure if there is a similar page for your country.

I'm in Aus, too. I've had support on this before, and it is not great, to put it kindly.

and to restrict gateway 1 users but not gateway 2 seems a very strange. Thus I feel it’s a bug they have introduced and not intentional.

Yeah, I get that. It could be just bad programming - and that's as likely as anything else.

If you haven't been through the support process, it is painful. Others have reported it, without success, and I don't have the stamina to go through a process to be told either it's by design, or we can't help you.

But some of what you see, when trying to change the password, is evidence of intent.

Reports elsewhere indicate that Tesla intends to remove all local access - I don't know if that's true, but that's what I've heard.

It's most likely a combination of bad programming, poor testing, and laziness in not responding to others who have reported the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants