Powerwall Gateway 1 - Issues with Vitals - Firmware 24.36.1 #536
Comments
Oh no. I don't recall anyone testing the PW1. I'm not sure if/how this would work. But clearly there is something wrong:
I assume you are using something similar to the PW2 examples and the password is the one listed as the WiFi password on the QR code on the Powerwall? From what I see, it is ~10 characters, all upper case. |
PW2, but Gateway 1 - and early vintage - no reset button, for example.
Yeah, sort of 🤣 There's no WiFi SSID or password listed on the sticker that has a QR code on these early gateways, but through trial and error and google-fu, I can confirm that the WiFi password to use is the serial number of the gateway - and that's what I'm using. I can confirm that:
|
|
It would be interesting to see if you get a different response using the manual TEDAPI tools: https://github.com/jasonacox/pypowerwall/tree/main/tools/tedapi From the host that has access to 192.168.91.1: # First, install or upgrade if you haven't
pip install -U pypowerwall
# Run the tool
python3 -m pypowerwall.tedapiIt will prompt for the GW Password and should try to fetch the DIN and status. |
Will give it a try (may not be for a couple of days - have a few things on). I did note when looking for the error message that the code path appeared to be following the tools code rather than the https://github.com/jasonacox/pypowerwall/tree/main/pypowerwall/tedapi code (but that may well have been me mis-reading the code). |
jasonacox
changed the title
|
Note set up a venv as on Ubuntu 24.04 which requires venv or complains very loudly :) Also tried customer password. Same error. As noted, the password (serial number) does work for Tesla One, but only when I toggle the power switch as prompted by the Tesla One app. |
|
Further (with |
|
Somewhere between...
We would need to add a step to let you toggle the power. I wonder if once that is done, if there is a token/cookie that is used to "remember" it was authorized. Can you try some tests using curl? # Replace YOUPASSWD with the gateway password
curl -i -u Tesla_Energy_Device:YOURPASSWD -k https://192.168.91.1
curl -i -u Tesla_Energy_Device:YOURPASSWD -k https://192.168.91.1/tedapi/din |
|
After replacing After After I got: I tried toggling after the first call, but no luck. I also tried using Postman, but it didn't show me anything else (such as cookies received after the first call). |
|
I've also tried toggling using the Tesla One app but I now can't log in using that - I may need to back off for a while :). I don't even know enough to be dangerous, but I suspect that this may need:
I had a look at the WiFi connection established on my phone while logging in on Tesla One it says "TEG_nnn via Tesla One" and if I authenticate via my PIN to display the WiFi password for the WiFi connection, there isn't one - which isn't the case" so there's some real funkiness going on in the way the Tesla One app sets up the WiFi connection within the app.
|
|
I agree, there must be more communication happening. You would need a way to packet capture that (likely on the device you are using for Tesla One). |
I have an old Android phone that I have root access on where I can probably do some more "interesting" things. I am not sure if I will get a chance this week, but I will see if I can find out more. |
|
And just like that... Downgraded to 23.28.2. I suspect that 24.36.1 was a little undercooked. I also ran into problems with just the normal login from HA - it would seem to time out after (roughly 24 hours), would require re-authentication, but at that point, I couldn't log in with a known password, without going through the toggle process to reset the customer password. Now I'm in the process of backing up my cut down dashboard, so that I can re-establish my old dashboard with all the old vitals :) Feel free to close, and re-open in the future if this pops up again with a future version. Eye surgery tomorrow, I'll check back in a few days to let you know if I have any better luck with tedapi with this older version (b ut, given the testing I did with Telsa one, I doubt it). |
Wow! I haven't heard of that happening before. I hope all goes well with surgery. Take your time... rest and recover. 🙏 When you get back to checking, let us know what you find out. |
|
Just the same, I'm afraid (which, TBH, I expected - given the need to toggle the switch to use Telsa One): It is pissing down here (30mm of rain so far, and just had a severe thunderstorm warning) so I'm not going to attempt a toggle or any sort of MITM packet capturing any time soon - but might once the weather improves. Solar forecast has dropped from 25kWh (I only have a modest system that is almost 15 years old) to 4.3kWh today). |
|
Whoa! Stay safe @BJReplay ! Sadly, I think the only path to get it to work is to get a good packet capture of a toggle event with the Tesla app to see what is being set to allow login. |
|
Quick update - just updated to 24.36.2 46990655 (so an update from .1 to .2). Will be interesting to see if it is more stable. As noted above, there issues with 24.36.1 with being locked out from both HA and the local Powerwall UI. I've just re-tested using pypowerwall, and can't log in. Will wait until I have a full battery and can play around, and see how I go to see if I can packet capture, but I'm still about a month or so away from having proper vision, so may defer any serious investigation until then. On upgrade I have lost the alerts, temperature from vitals, and grid and home frequency:
|
|
Discussion also happening here for others seeing this: https://teslamotorsclub.com/tmc/threads/unable-to-log-into-gateway-after-24-36-2-update.336050/ @BJReplay I understand you may not be able to respond for a while, but some questions and comments:
|
I may be able to contribute to that - as I've had to reset my password so many times while on 24.36.1 I'm now an expert - I don't know if it will work on 24.36.2, though, but it's worth explaining what did work (eventually).
Yeah, I was lucky that I was on an old version for so long, that the jump to 24.x made me realise what I'd been lucky to keep.
With 24.36.1, it would lock me out in 24 hours after I successfully gained access, and then I was stuck until I went through an arduous reset process (which involved shutting down three things talking to the powerwall (including pypowerwall / Powerwall Dashboard) (so they wouldn't trip up with the reset password), then a toggle reset - which I'll report back on the TMC thread. It hasn't yet been 24 hours, so I don't know if I'll run into the same problems on 24.36.2 where it appears to work for 24 hours, then locks up.
|
|
Thanks @BJReplay
Does the TeslaOne app work? If so, you could use the same password you use for TeslaOne in: python3 -m pypowerwall.tedapi --debugIf that works edit the Is this what you did for the password reset? (from https://teslamotorsclub.com/tmc/posts/8483544/):
|
Only with a Powerwall switch toggle to log in. No other way to access it using Tesla One.
Still no luck - same error as before
Not quite - because I've got the route set up, I could bypass the TEG WiFi, but there's another part that I found differed - you have to leave the Powerwall Turned Off while changing the Password
|
|
In addition to above, where more than one Powerwall was attached to gateway, each was toggled in turn rather than just one. Otherwise the response was
The screen you are looking for has a green check mark with text "Password successfully updated", and a blue button "COMPLETE". Reported firmware version 24.36.2, Powerwall 2 x 3. |
@quozl I got the same error even with just one Powerwall if I toggled (turned off then on) before trying to change the password. I had to turn off, change password, COMPLETE, the turn on. Otherwise, I got the |
|
I have not gotten into this as I have other fish to fry right now and I am hoping you all find a solution. I have a late 2019 Gateway1 with 2-PW2's. Couple of comments:
|
LOL - funny because Telsa clearly don't understand consumer law in several of the jurisdictions that they sell into. In Australia, they'd be required to offer customers a refund of the original purchase price, make good of installation damage, remove the Powerwall ("The Backup Gateway communicates directly with Powerwall, allowing you to monitor energy use"). Sell a product with a 10-year warranty and remove a feature they advertised as what the user might have considered a key feature - well, sorry Tesla, you can restore it or refund the customer. It would cost me $57 and a bunch of time - which I've got - and it would cost Tesla a bunch of money for high priced lawyers, and bad publicity. |
I think you could crowd fund that in about 3 minutes. We could definitely cause pain for Tesla, but they can probably also argue that they are providing this data in their app. But maybe the ACCC would agree with us. Because it is after all, our data. |
No doubt they can, and if I went down this path, no doubt they would. But as you know (despite your username, I know you're not from the lone star state) consumer law is still on my side: if they provided a feature that they then removed, they can't then argue that they meant something else: the fact that they provided it allowed me to assume that they meant what they did. The fact that they did it for seven years and then decided to remove it makes it very hard for them to argue that they didn't ever intend to do it. The fact that I have seven years of six second monitoring data that I have used and obtained value from - and can demonstrate the value that I have obtained from it, will give them even more trouble. I hope the rumours are wrong, but if they're not, they've picked the wrong ex-IT, ex-energy transition strategy guy, ex-IANAL, but I know the law well enough to have defeated banks in litigation guy. |
|
Oh don't worry - I'm very with you as the squeaky wheel grind the bastards down type - at my most cheerful when I'm pointing a loaded ombudsthing at an organisation that is breaking either their own rules or consumer law. Like you, I hope the rumours are wrong, but I'll be happy to provide whatever support you need if it comes to it. (Hovering over my username will provide negative information, but will at least confirm that I come from a place where some of the states are in fact bigger than texas) |
This change was already made for Powerwall 3, so it's possible it will also happen for Powerwall 2. The change only affects the Gateway API however. There's also TEDAPI (the API used by Tesla One) that's still accessible and mostly gives the same information. |
@BJReplay reported:
No luck on the vitals.
In order to log into my system (Gateway 1 vintage) using Telsa One, I have to toggle the switch on the side of the Powerwall.
In order to make sure that I was doing a clean test, I cleaned up cookies from
.powerwalland.auth/.powerwall, stopped pypowerwall, changed my local customer password to one without an*(which was causing problems when testing on the command line), and re-saved the .env file, and restarted the pypowerwall docker container withdebug=yesin the .envI think the fact that I have to toggle the switch on the side of the Powerwall is a symptom that I'll not be able to get the TEDAPI working, but would be interested to see if there's more to be done to attempt to debug:
pypowerwall.env
Originally posted by @BJReplay in #109 (reply in thread)
The text was updated successfully, but these errors were encountered: