Login Error

[Atlantis1971]

The problem

Hi there, I own a tesla system that works perfectly. I already tested all the connections and the accounts and are ok. Some days ago, when I updated the Tesla integration, I noticed the counter weren't available so I deleted the Tesla integration and all the entities and I re-added the integration but at the first step, when it asked me to put my credential I wrote the IP and the password but I got this error:

I own the Powerwall 2 with Backup Gateway 2 and I tried to use as a password:

• the last 5 chars: didn't worked;
• the whole password: didn't worked;
• the serial number: didn't worked.

I tried also to put the IP with https:// and without it: didn't worked.

In this moment I'm not collecting any data.

Could you please help me?

Thanks

Alex

What version of Home Assistant Core has the issue?

core-2024.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tesla Powerwall

Link to integration documentation on our website

https://www.home-assistant.io/integrations/powerwall

Diagnostics information

home-assistant_powerwall_2024-02-12T08-21-36.345Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @bdraco, @jrester, @daniel-simpson, mind taking a look at this issue as it has been labeled with an integration (powerwall) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `powerwall` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign powerwall` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

powerwall documentation powerwall source _{^{(message by IssueLinks)}}

[Atlantis1971]

Hi there,

@bdraco please could you tell me anything about this problem, please?

I tried to come back to an old version by restoring a backup but the problem remains and I have a fail in configuration:

---

2024-02-27 08:20:55.269 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Laurenti Deborah for powerwall Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 444, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/powerwall/init.py", line 133, in async_setup_entry base_info = await _login_and_fetch_base_info( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/powerwall/init.py", line 219, in _login_and_fetch_base_info return await _call_base_info(power_wall, host) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/powerwall/init.py", line 241, in _call_base_info raise e.exceptions[0] from None File "/usr/local/lib/python3.12/site-packages/tesla_powerwall/powerwall.py", line 127, in get_batteries return [BatteryResponse.from_dict(battery) for battery in batteries] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/tesla_powerwall/responses.py", line 305, in from_dict grid_state=GridState(src["pinv_grid_state"]), ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/enum.py", line 744, in call return cls.new(cls, value) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/enum.py", line 1158, in new raise ve_exc ValueError: '' is not a valid GridState

---

Thank you.

Alex

[jrester]

Hey @Atlantis1971, the problem regarding the GridState is already known and should be fixed in https://github.com/home-assistant/core/pull/111418

[Atlantis1971]

Hey @Atlantis1971, the problem regarding the GridState is already known and should be fixed in #111418

Hi @jrester ,

thank you for your answering but the bug I wrote about is concerning the login, not the grid state. Is it new for the team?

Alex

[jrester]

Hey @Atlantis1971,

sorry for the confusion, I was referring to the second message you posted, including the error traceback.

Regarding your Login Problem, I am not aware of any current problems. With your credentials, can you log in to the Web UI of the Powerwall directly (It is available at https://192.168.1.80) ?

[Atlantis1971]

Hi @jrester ,

my Powerwall UI runs well. I would make notice that the password I normally use on the UI is the customer one. The supervisor password, the one written inside the Gateway, is the one I'm writing in the login mask of the powerwall integration but doesn't run. I tried to use the last 5 chars, as instructions: no results. So I tried the whole password... nothing. So I tried the same (last 5 chars and the whole one) of the serial number: nothing again.

Anyone could help me, please?

Alex

[Atlantis1971]

Hi @bdraco and @jrester ,

I got some news about the login.

I could install again the Powerwall integration without login problems, using the whole customer password but I got no entities and a configuration error. Is it due to the use of a customer password instead a supervisor one? If yes, my problem is that I tried to use the Supervisor password but it doesn't work.

Let me know, please.

Thanks.

Alex

2024-03-08 - Logs.txt

[JuhaSeppa]

I had similar problem today. I was able solve the issue by reconnecting the Powerwall to my wifi.

[Atlantis1971]

I had similar problem today. I was able solve the issue by reconnecting the Powerwall to my wifi.

Hi,

what do you mean with "reconnecting", about the Powerwall? It's enough switch off and on the Powerwall or I have to deconfigure and reconfigure the wifi on the Powerwall? Or what else?

[JuhaSeppa]

I had similar problem today. I was able solve the issue by reconnecting the Powerwall to my wifi.

Hi,

what do you mean with "reconnecting", about the Powerwall? It's enough switch off and on the Powerwall or I have to deconfigure and reconfigure the wifi on the Powerwall? Or what else?

I have two wifi networks. I used the app to connect the Powerwall to the other network and then back to the one I need it to be. In my case it seems to have been a networking problem of some kind, which resolved itself through these steps.

[Atlantis1971]

Hi @JuhaSeppa ,

thank you for your suggest but it didn't worked for me. I don't think my login problem is related to the network.

I hope in more help.

Alex

[BJReplay]

I used the app to connect the Powerwall to the other network and then back to the one I need it to be. In my case it seems to have been a networking problem of some kind, which resolved itself through these steps.

This was a really useful hint.

I just flashed my router to the latest OpenWRT, and my Powerwall (Gateway1) wasn't showing up in HA.

Long pointless irrelevant discussion: I only use Ethernet, not WiFi, and because my Gateway is in the same equipment cupboard as my WiFi, I have my gateway configured to use Ethernet, not WiFi, and have deliberately attempted to connect to WiFi with my router set to a bad WiFi channel, then disconnected from WiFi, then swap my router to Auto (which selects an uncrowded channel). The gateway stays on the bad (crowded) WiFi channel. This means that I don't have the gateway WiFi TEG access point swamping my own WiFi

Anyway, your suggestion of changing WiFi connections prompted me to see if I couldn't fix the problem in a similar way.

This is what I always see - even though I'm accessing the Gateway over the Ethernet connection that supposedly isn't working:

I went into Ethernet, hit Connect:

And went back to HA and hit Reload on the integration - the error status resolved.

The gateway still reports that Ethernet is Configured but not connected.

@jrester it might be worth noting that in cases when the Powerwall Gateway gui is reachable but the Tesla HA integration can't connect, refreshing the gateway network connection, then reloading the HA integration may be sufficient to resolve the problem.

[Atlantis1971]

Hi there,

I would like to come back to the focus point of my post: a login error.

As I explained before, my network is ok:

The point is the error on the auth when I add the Tesla Powerwall integration in HA. I used the Customer password and I had no errors but I got no devices configured

I reloaded the Powerwall integration: nothing done.

I tried to use the Supervisor password: nothing done.

This is the problem, not a connection one or a network configuration.

Thanks

Alex

[marmitetoad]

@Atlantis1971 - I've just had exactly the same issue, in that the integration had completely disabled - which happened I think when Tesla recently updated the API, but I haven't been in and looked at it for a while. It looks like when they changed the API, at least for me it expired my custom password I had set. I had to go into the Web Interface of the powerwall, and do a password reset using the change or forgot password under the customer login, you'll need the last 5 digits of your gateway password for the reset to work.

[Atlantis1971]

Hi @marmitetoad ,

thank you for your answer. I just recovered my customer password as you wrote before but the errors are the same. The last 5 chars gave me the same error as before (login error, see the first post) and I had to use the whole password to install the Powerwall integration. Unfortunately, I am in the same condition of my previous post (Configurazione non riuscita): I got no devices.

@bdraco , could you help me prease?

Thanks

Alex

[wandreis]

I'm having the same issue as you... any news on this?

[Atlantis1971]

Hi @wandreis , for now I got no news. I'm waiting the help by @bdraco . I hope he could!

Alex

[Roaders]

I've had a very similar issue. I was finally able to add the integration using the customer password and I though I'd cracked it! When I restarted my home assistant though I got errors telling me that the authentication had expired. I tried entering the password (many variations of the password) in the reconfigure dialog - that didn't work. I removed the integration and tried to re-add (again tried many variations of passwords) and I was back to the authentication error message. Seems this integraion is now broken.

[JuhaSeppa]

Seems this integraion is now broken.

The integration works in my setup. I'm on latest versions for all Home Assistant components. Powerwall software is 24.4.0.

Last week we had a brief power cut and the Powerwall stoped communicating over IP in my home network. The app was still working so it was communicating fine to the Internet. Router thought the Powerwall was there and everything seemed fine. I asked the router to reconnect the Powerwall and everything started working again.

[Roaders]

I wonder if you would be able to re-add the integration in a new HA install.

[Atlantis1971]

I wonder if you would be able to re-add the integration in a new HA install.

Yes but I think the problems remain.

[Atlantis1971]

Hi @bdraco and @jrester ,

any news about the login error on the Powerwall integration?

Thank you.

Alex

[lvoaks]

I also have this problem and would like to see it resolved

[jrester]

There is a possible fix in #117823, which should be included in the next home-assisant release. Once the release is available, please update your home-assisant instance and check again if the errors persist.

[Roaders]

There is a possible fix in #117823, which should be included in the next home-assisant release. Once the release is available, please update your home-assisant instance and check again if the errors persist.

Great, many thanks. Is there an easy way of finding out which version of HA this PR is included in when it has been released?

[Atlantis1971]

Thank you @jrester , I'll let you know.

C u soon.

Alex

[Atlantis1971]

Hi @bdraco and @jrester ,

I just upgraded to 2024.6.0 and nothing changed. I still got the same errors....

What can I do?

Thank you.

Alex

[BetoHydroxyButyrate]

I was unable to connect using the last-5 chars, so I tried the password I use to log into the WEB interface. That worked for me (well, ultimately: see below). My problem, now, however, is that the IP changed (I moved it to a fixed IP and it took forever for the TG to switch over), so now I just need to change the IP, but can find no way to do so, which is why I came here.

Anyway, log into the WEB interface the TG presents to you. Mine says `Switch to Tesla One for a better commissioning experience

The current experience is no longer supported`

Ignore that, and hit the CONTINUE. You will go to a https://${YourIP}/upgrade page. Ignore the upgrade now and look at the bottom of the page for UPGRADE LATER. Click on that any you will be at a login screen. For me, when my installer set it up, he facilitated me creating an account and password, which is saved in my password manager. That is the password I need to supply to register the instance.

Actually, come to think of it, the saved password did not work, and I had to go thru the password reset procedure you can get to on that page. It is all explained there.

Hope this helps someone.

(I'm on a TG2 just installed this week, in case that matters)

[sircoynie]

I was unable to connect using the last-5 chars, so I tried the password I use to log into the WEB interface. That worked for me (well, ultimately: see below). My problem, now, however, is that the IP changed (I moved it to a fixed IP and it took forever for the TG to switch over), so now I just need to change the IP, but can find no way to do so, which is why I came here.

Anyway, log into the WEB interface the TG presents to you. Mine says `Switch to Tesla One for a better commissioning experience

The current experience is no longer supported`

Ignore that, and hit the CONTINUE. You will go to a https://${YourIP}/upgrade page. Ignore the upgrade now and look at the bottom of the page for UPGRADE LATER. Click on that any you will be at a login screen. For me, when my installer set it up, he facilitated me creating an account and password, which is saved in my password manager. That is the password I need to supply to register the instance.

Actually, come to think of it, the saved password did not work, and I had to go thru the password reset procedure you can get to on that page. It is all explained there.

Hope this helps someone.

(I'm on a TG2 just installed this week, in case that matters)

Utter legend! Thanks

[Atlantis1971]

Hi there to all,

I have to say many thanks to @bdraco and all the staff. The issue is SOLVED, the only thing to know is to use the whole password instead the last fine chars. I used the customer password, not others.

Maybe could be a good idea to update the signing in label.

Thank you.

Alex

[permezel]

I have to say many thanks to @bdraco and all the staff. The issue is SOLVED, the only thing to know is to use the whole password instead the last fine chars. I used the customer password, not others.

That does not work for me. Each time I reset the password, I can authenticate, but within a few hours, the password no longer works to log me in to the local Tesla-gateway WEB page. The authentication for the integration keeps working for a day or so, but eventually goes bad again, and my saved password fails to re-authenticate, so I have to go thru the tiresome manual password reset.

Strangely enough, while trying to log in just now to the WEB page, it rejected my password, and I clicked on the "click to reset" and it took me to a reset page with "enter old password / enter new / enter new" and it took the last 5 chars of the SN. Really weird, but at least this time I did not have to walk outside and toggle a switch on a battery.

[permezel]

Just tried login to TUG WEB page. Rejected yesterday's reset and working password, but this time, I tried with the last 5 letters of the S/N and it worked. Seems like it does not want to remember custom reset customer passwords, and keeps reverting. The integration is still working with the creds created yesterday with the custom password, but next time it requires re-auth, I hope that the last 5 letters will remain good and I can set it once more and never again be harassed by that nasty device lurking just outside on the wall.

[daniel-simpson]

Just for context: I'm also just using the last five characters of the password printed on the Powerwall as my "custom password" and I've not have this issue before.

I had a similar issue a long while ago and just went with the defau.t password. I always assumed it was something to do with Tesla changing something around their provisioning, but needing to be "backwards compatible", so resetting the password after they change something.

Using the default password means I've effectively bypassed these issues.