Growatt timeout - Error while setting up growatt_server platform for sensor: 'user' #141357
Comments
|
Hi, i got the same error. Shine app is working correctly. |
|
Same here. Mar 29 21:13:30 home-assistant homeassistant[761]: 2025-03-29 21:13:30.791 ERROR (MainThread) [aiohttp.server] Error handling request from 192.168.3.36 |
|
Same here, since a couple of day. Switching off the Growatt integration allows me to log on to the app and web interface without the message that my account has been blocked for 24 hours. The integration with HomeWizard also was not working. With the integration switched off in HA, all three (HomeWizard integration, the app and web interface) are working fine. It looks like the HA integration sends to many requests... |
|
Solved now. It was my container that restarted several times because of an other error. Then I got locked out because of to many requests. |
|
Short story: After multiple attempts, I finally removed the configuration, re-added the same configuration - instantly entities became available with proper values. Long story: last night, my HA instance (core-2025.4.1 running on HAOS 15.1) started misbehaving as well in the same way after restart HA (due to a config change). Rebooting the HAOS-instance didn't help as well, temporarily disabling any kind of activity towards Growatt's servers (disabling both growatt_server and noah2mqtt running at a 300-second-polling interval) before re-enabling growatt_server didn't help as well. 2025-04-07 19:15:58.545 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up growatt_server platform for sensor: 'user' Out of curiosity, I also temporarily disabled any growatt-related services and restarted them a few minutes after a full restart of HA (to wait until everything has settled after startup) - this didn't help as well. After multiple attempts, I finally removed the configuration, re-added the same configuration: and instantly entities started working again. |
|
my account is stil getting locked out. i used homey before with that homey integration, that stopped working months back, but now it seems that growatt has taken new measures to block data retrieval unless you have an agreement with them like some utility providers etc. what server address did you use? |
|
I‘m located in Europe and use the corresponding default (openapi.growatt.com). Maybe some of us are affected by different issues that still share the same symptoms. Recreating the configuration did work for me, but won’t work if your account is really locked or requests from your IP are temporarily rejected by Growatt’s Web Application Firewall. Those WAF-related responses may also cause a “failure to login”-symptom, though the actual account is possibly not locked and the exact error message is different from an actually locked account. |
|
i get the locked out message in shinephone 5-6 hours ago when i enabled it now 22:35 it started working again, did not have to remove and re-add. i also logged back into shinephone. they are just taking more and more measures to block everyone without a agreement to retrieve data. i have asked tibber if they could expose this data in their api, but last time i asked them they would not do that. |
The problem
Hello
I created a new user in Growatt - this user prescribed an integration - everything worked excellently as an apot received a user block for 24 hours
Perhaps the plugin sends many requests?
Here is the error code
(I have 2 inverters)
Error while setting up growatt_server platform for sensor: 'user'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/growatt_server/sensor/init.py", line 88, 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/sensor/init.py", line 51, in get_device_list
user_id = login_response["user"]["id"]
~~~~~~~~~~~~~~^^^^^^^^
KeyError: 'user'
What version of Home Assistant Core has the issue?
core-2025.3.4
What was the last working version of Home Assistant Core?
never
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
rror while setting up growatt_server platform for sensor: 'user'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/growatt_server/sensor/init.py", line 88, 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/sensor/init.py", line 51, in get_device_list
user_id = login_response["user"]["id"]
~~~~~~~~~~~~~~^^^^^^^^
KeyError: 'user'
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: