Upgrading to HA Core 8.2 from 8.1 caused all Growatt entities to become unavailable. Reverting to 8.1 did not fix

[NicolasAmbrose]

The problem

I just upgraded to Core 8.2 from 8.1. Once everything was up, the Growatt integration reported an issue and all points were unavailable. It said--Needs attention, failed to set up, check the logs. There was also an Add Entry button. I checked the logs. Add entry asks for Growatt username, password, and server. I tried that using the US server as had been used previously, and the generic server. This reported Unknown Error Occurred. Rolling back to Core 8.1 did not fix the issue. I logged into the Growatt server website directly from the browser using the same credentials and US server address and that worked fine.

What version of Home Assistant Core has the issue?

2025.8.2

What was the last working version of Home Assistant Core?

2025.8.1 but now it doesn't work either

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Growatt Server Integration

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

The log:

Logger: homeassistant.config_entries
Source: config_entries.py:749
First occurred: 3:42:35 PM (2 occurrences)
Last logged: 3:43:44 PM

Error setting up entry Growatt11223 for growatt_server
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/growatt_server/__init__.py", line 65, in async_setup_entry
    devices, plant_id = await hass.async_add_executor_job(get_device_list, api, config)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/growatt_server/__init__.py", line 36, in get_device_list
    user_id = login_response["user"]["id"]
              ~~~~~~~~~~~~~~^^^^^^^^
KeyError: 'user'

Additional information

No response

[home-assistant]

growatt_server documentation
growatt_server source

[jssting]

I'm having the same issue after updating Core to 2025.8.2, and I am using the AU API. I have also removed the integration and tried resetting it up and that also fails.

Original error log entry
Logger: homeassistant.config_entries
Source: config_entries.py:749
First occurred: 9:02:33 AM (1 occurrence)
Last logged: 9:02:33 AM

Error setting up entry Growatuser for growatt_server
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/growatt_server/init.py", line 65, in async_setup_entry
devices, plant_id = await hass.async_add_executor_job(get_device_list, api, config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/growatt_server/init.py", line 36, in get_device_list
user_id = login_response["user"]["id"]
~~~~~~~~~~~~~~^^^^^^^^
KeyError: 'user'

[jssting]

I have just tried the call directly in python using another library (but could be based of the same one) and it seems to be an issue/change on the Growatt side that has broken the integration .

[jssting]

@NicolasAmbrose I was also being locked out of the ShinePhone app on a regular basis. Which led me to deduct that is account related. I was able to get it working by creating a "visitor guest account" on the server.growatt.com portal and using that account for the integration rather than my primary account. Looks like they have changes the window for calls and it causes the account to be locked out.

[NicolasAmbrose]

@jssting Thanks for the info. I'll give it some time and see what happens later today, and based on that possibly try that method. I was able to log into my account via the US server web portal with no problem and view all of my plant data soon after having all of the issues described above, so my overall account access seemed to be fine. I was locked out once a long time ago but have not had that happen in recent memory. Anyway, we'll see.

[murrayktaylor]

I've had the same issue. I've just attempted to sign-in to the Shinephone app as was able to log in, but had to re-agree to the terms and conditions - which has then fixed the integration in HA. So it may just be that keeping you out!

[NicolasAmbrose]

@murrayktaylor Well, that's interesting as well. If it is a lockout and if memory serves they're 24 hours so I'll wait till ~4pm my time and see what happens when I do that. And then I guess the other question is, why would updating HA from 8.1 to 8.2 trigger that? I'm back on 8.1 right now, so if what you suggest works I may reinstall 8.2. If it happens again at least I have a couple things to try.

In all honesty I've had a lot of recent issues with web based integrations and HA updates since Core 7.0, some of which were not fixable. I'm slowly working toward everything being local only, and Growatt may be the next candidate. Battery voltage is the only critical data point for me, with three others being nice to have but not mandatory.

[Hassgitlabwilli]

Hi All,
I have the same issue.

• Same log output as Upgrading to HA Core 8.2 from 8.1 caused all Growatt entities to become unavailable. Reverting to 8.1 did not fix #150732 (comment)
• Web Login via https://server.growatt.com/index works.
• Using the shine App (Android) shows me a failure message:

• It helped for me to rebooting the HASS OS VM to get it working again the last three days.
• Restarting just HASS did not made any difference.
• Today I'm stuck and Rebooting the VM did not help anymore. Maybe I'm not past 24h yet.

For Me it seems to be, that 2025.8.2 changed something in fetching the data from Growatt, which Growatt isn't accepting and the user API access gets blocked.

Looking forward for the visitor workaround results. (My assumption is, that the visitor account will also be blocked by some time. Using a visitor account just starts the Growatt internal "blocking counter" by 0).

@johanzander Might it be possible to have a look in this topic?

[jssting]

@Hassgitlabwilli the guest account will limit the lockout as only HASS will use it and it will not lockout the account on the phone. The down side is that it is a read only account so you cannot run any API tasks that write back to the inverter/growatt i.e. changing the preference for generation to be battery first or load first

[gjaegy]

Same issue here, I haven't managed to fix the issue yet.

[NicolasAmbrose]

So after waiting like 30 hours without trying to log in to anything I was able to get everything back up using my primary account.

First, I tried to log in to the ShinePhone app. I was presented with the policy update screen, as others have mentioned. Instead of just clicking Accept, I clicked on and scrolled through the two actual policies that had been updated. I don't know if that was monitored by Growatt--it was just a hunch. Then I clicked Accept and it let me log in and view my data.

I quit the phone app and returned to the HA Growatt integration. I still was looking at the screen as shown in the picture of my original post. In the upper right was that Add Entry box, so I clicked on that, entered my credentials, and selected my US server. The message came back saying something like Device Already Configured. I had tried doing that before and did not see that particular message until now.

Everything else was still the same, but I went ahead and restarted HAOS. To my surprise, everything came back after the restart. It's been okay since. I'm still back on Core 8.1, and I think I'm going to leave it that way vs risking going through all of this again. Maybe it was just coincidence that Growatt had their policy update requirement at the same time I upgraded to 8.2, or maybe not, but I don't think I want to find out as long as it's all up.

As an aside, while I was waiting I built a solar battery voltage monitor using an old Shelly Uni device I had laying around. It's obviously not dependent on Growatt and it's been working great. This was the only critical piece of data I really needed for my automations in HA, so I edited those automations to use the voltage reported by the Uni. At least, should this happen again, I have a backup source for that info.

Anyway, thanks everyone for your input and suggestions. I hope you are able to get things working.

[jansenfd]

So after waiting like 30 hours without trying to log in to anything I was able to get everything back up using my primary account.

First, I tried to log in to the ShinePhone app. I was presented with the policy update screen, as others have mentioned. Instead of just clicking Accept, I clicked on and scrolled through the two actual policies that had been updated. I don't know if that was monitored by Growatt--it was just a hunch. Then I clicked Accept and it let me log in and view my data.

I quit the phone app and returned to the HA Growatt integration. I still was looking at the screen as shown in the picture of my original post. In the upper right was that Add Entry box, so I clicked on that, entered my credentials, and selected my US server. The message came back saying something like Device Already Configured. I had tried doing that before and did not see that particular message until now.

Everything else was still the same, but I went ahead and restarted HAOS. To my surprise, everything came back after the restart. It's been okay since. I'm still back on Core 8.1, and I think I'm going to leave it that way vs risking going through all of this again. Maybe it was just coincidence that Growatt had their policy update requirement at the same time I upgraded to 8.2, or maybe not, but I don't think I want to find out as long as it's all up.

As an aside, while I was waiting I built a solar battery voltage monitor using an old Shelly Uni device I had laying around. It's obviously not dependent on Growatt and it's been working great. This was the only critical piece of data I really needed for my automations in HA, so I edited those automations to use the voltage reported by the Uni. At least, should this happen again, I have a backup source for that info.

Anyway, thanks everyone for your input and suggestions. I hope you are able to get things working.

Same her

[jansenfd]

Same here, on the phone accepted the new policies 2x.

Then added the credentials again in HA with the message already configured, after that disabled and enabled the integration in HA and all is working again.

[NickZeke]

Hi All, I have the same issue.

• Same log output as Upgrading to HA Core 8.2 from 8.1 caused all Growatt entities to become unavailable. Reverting to 8.1 did not fix #150732 (comment)
• Web Login via https://server.growatt.com/index works.
• Using the shine App (Android) shows me a failure message:

* It helped for me to rebooting the HASS OS VM to get it working again the last three days. * Restarting just HASS did not made any difference. * Today I'm stuck and Rebooting the VM did not help anymore. Maybe I'm not past 24h yet.

For Me it seems to be, that 2025.8.2 changed something in fetching the data from Growatt, which Growatt isn't accepting and the user API access gets blocked.

Looking forward for the visitor workaround results. (My assumption is, that the visitor account will also be blocked by some time. Using a visitor account just starts the Growatt internal "blocking counter" by 0).

@johanzander Might it be possible to have a look in this topic?

I have exactly the same issue, however, my installation was still on 2025.8.1. So, in case the account got locked by Home Assistant, the cause was already present in the 2025.8.1 version. However, it was working for more the 48 hours, since I upgraded to 2025.8.1 about two days ago. It stopped working a couple of hours ago.