PyPi_GrowattServer
PyPi_GrowattServer copied to clipboard
indykoning
Growatt blocking accounts
I think this the end of the Api. Growatt is locking accounts. Mine has been locked. API not working and shinapp says account locked.
Oh the positivity :P
I recommend taking a look over here: https://github.com/muppet3000/homeassistant-growatt_server_api/issues/15
I recommend reading my specific comment here: https://github.com/muppet3000/homeassistant-growatt_server_api/issues/15#issuecomment-1421417491
Use the FAQ I put together over there to set up an alternative account via the website.
Furthermore, if you switch back to using the "server.growatt.com" url (which seems to work again) it's works with the same credentials.
My original account still seems to be blocked on my phone but works fine on the website so I created myself a new login just for my phone and also one for my various automations so that one can't break another etc.
Note - my account was blocked on my phone yesterday and is unblocked again this morning.
Mine was unlocked this morning. But is locked again. As is said this could be the end of the API. Because Growatt is now blocking the accounts activly.
Mine was unlocked this morning. But is locked again. As is said this could be the end of the API. Because Growatt is now blocking the accounts activly.
Only on the shinephone app, not on the website and you can just change the endpoint to use the website again. Did you read my message from yesterday?
I don't think you understand the whole picture here. They activly Blocking accounts. So the API has become useluss. Website is not the problem.
I understand fine. Just change the endpoint URL, they provide exactly the same API endpoints.
Other than that they don't seem to be blocking for other URLs. We'll find out I suppose.
Everything has been very intermittent for the last 2 days, I suggest we just wait it out to see what changes they've got in store this time :P
I had to change the API endpoint to the original server.growatt.com as could never get the new one to work when I put my system together a couple of weeks back. Not had any account locking issues. For my use case (a Pi with a small display showing some stats) I only poll the API every 5 minutes, maybe they're stopping calls that are more aggressive. Let's see what happens over the next little while.
I reduced my polling to every 3 minutes earlier today and things stabilised (however the data that's available on the server itself has been very flaky all day, but that's a server problem).
I certainly had some rubbish figures on their normal website yesterday. All the "now" info was fine, but the "today so far" was all out.
I created extra accounts for app and API reader. Put the API reader on a 3 minute interval. Hopefully this will do the trick.
I reduced my polling to every 3 minutes earlier today and things stabilised (however the data that's available on the server itself has been very flaky all day, but that's a server problem).
Can you please tell me where I change the polling time. thx
I reduced my polling to every 3 minutes earlier today and things stabilised (however the data that's available on the server itself has been very flaky all day, but that's a server problem).
Can you please tell me where I change the polling time. thx
It depends how you're using this library, it's entirely dependent on how often whatever code you're using makes a call to this library.
I reduced my polling to every 3 minutes earlier today and things stabilised (however the data that's available on the server itself has been very flaky all day, but that's a server problem).
Can you please tell me where I change the polling time. thx
It depends how you're using this library, it's entirely dependent on how often whatever code you're using makes a call to this library.
Sorry, I'm not that deep into this. I'm using Home Assistant 2023.2.3 on a Raspberry PI 3.
I reduced my polling to every 3 minutes earlier today and things stabilised (however the data that's available on the server itself has been very flaky all day, but that's a server problem).
Can you please tell me where I change the polling time. thx
It depends how you're using this library, it's entirely dependent on how often whatever code you're using makes a call to this library.
Sorry, I'm not that deep into this. I'm using Home Assistant 2023.2.3 on a Raspberry PI 3.
In which case you'll be using the stock Growatt integration and that is currently fixed at every 5 minutes. I'd be VERY surprised if you've had your account locked with a 5 minute polling interval. Are you sure you've been blocked? What happens when you use the same credentials to log into the ShinePhone app? Do you get a pop up saying "this account is locked"?
I reduced my polling to every 3 minutes earlier today and things stabilised (however the data that's available on the server itself has been very flaky all day, but that's a server problem).
Can you please tell me where I change the polling time. thx
It depends how you're using this library, it's entirely dependent on how often whatever code you're using makes a call to this library.
Sorry, I'm not that deep into this. I'm using Home Assistant 2023.2.3 on a Raspberry PI 3.
In which case you'll be using the stock Growatt integration and that is currently fixed at every 5 minutes. I'd be VERY surprised if you've had your account locked with a 5 minute polling interval. Are you sure you've been blocked? What happens when you use the same credentials to log into the ShinePhone app? Do you get a pop up saying "this account is locked"?
Yes, account is also blocked in the app. But I installed your version via HACS.
Ok, so you're using the HACS version, which also defaults to 5 minutes unless you've followed my FAQ on how to increase the polling interval. In which case I recommend reaching out in the issues section over there rather than on this library, there is a chat going on on this ticket: https://github.com/muppet3000/homeassistant-growatt_server_api/issues/15
Basically you can create a new account and switch to using that for HA to work around the issue. I'd prefer to discuss specific issues related to the HACS/HomeAssistant integrations in their specific repos so it's all in the correct location.
This repo is the underlying library that is used by the Integration rather than the integration itself.
Hm, my ShinePhone-APP says: The current account is locked.
And my Python-code says: plant_list = api.plant_list(login_response['user']['id']) KeyError: 'user'
And that is whether I use server.growatt.com or server-api.growatt.com
I am not happy.
I recommend taking a read over here: https://github.com/muppet3000/homeassistant-growatt_server_api/issues/15 where there's a very detailed discussion about it. Specifically these two comments: https://github.com/muppet3000/homeassistant-growatt_server_api/issues/15#issuecomment-1423787751 & https://github.com/muppet3000/homeassistant-growatt_server_api/issues/15#issuecomment-1424810061
Note - when you poll at around 5 minutes your account doesn't seem to get blocked as quickly. Any more frequently than that and you get locked out.
As I've said in those comments above, you can create yourself another account through the web UI without any problem and use that. The lock seems to last approximately 24 hours.
Join the club. We all had that issue. Mine is good again. Interval 5 minutes and new account.
OK, I had my interval set on 120s. I just changed that to 300s. I will wait 24 hours before activating my script again. Hopefully I am unlocked by then. Thanks!
OK, I had my interval set on 120s. I just changed that to 300s. I will wait 24 hours before activating my script again. Hopefully I am unlocked by then. Thanks!
You can create a new sub-account under your existing one, follow the steps here: https://github.com/muppet3000/homeassistant-growatt_server_api/blob/dev/FAQ.md#how-do-i-share-my-credentials-with-you-for-testingadding-new-features-for-my-system-type
OK, I had my interval set on 120s. I just changed that to 300s. I will wait 24 hours before activating my script again. Hopefully I am unlocked by then. Thanks!
You can create a new sub-account under your existing one, follow the steps here: https://github.com/muppet3000/homeassistant-growatt_server_api/blob/dev/FAQ.md#how-do-i-share-my-credentials-with-you-for-testingadding-new-features-for-my-system-type
Great. Created an alternative account and it worked again with that! Thank you very much!
OK, I had my interval set on 120s. I just changed that to 300s. I will wait 24 hours before activating my script again. Hopefully I am unlocked by then. Thanks!
You can create a new sub-account under your existing one, follow the steps here: https://github.com/muppet3000/homeassistant-growatt_server_api/blob/dev/FAQ.md#how-do-i-share-my-credentials-with-you-for-testingadding-new-features-for-my-system-type
Stupid question: Where can I change the polling interval? I am using your HACS version homeassistant-growatt_server_api
OK, I had my interval set on 120s. I just changed that to 300s. I will wait 24 hours before activating my script again. Hopefully I am unlocked by then. Thanks!
You can create a new sub-account under your existing one, follow the steps here: https://github.com/muppet3000/homeassistant-growatt_server_api/blob/dev/FAQ.md#how-do-i-share-my-credentials-with-you-for-testingadding-new-features-for-my-system-type
Stupid question: Where can I change the polling interval? I am using your HACS version homeassistant-growatt_server_api
Unless you've changed it from the default using this how to guide: https://github.com/muppet3000/homeassistant-growatt_server_api/blob/dev/FAQ.md#how-do-i-increase-the-update-interval-to-be-more-than-every-5-minutes
then you'll be using the default of 5 minutes.
Yes I am using the default. But unfortunately my main growat user account is locked. I tried to create a new one but I don't receive any email.
So I checked your source and found in sensor.py at line 35 this:
SCAN_INTERVAL = datetime.timedelta(minutes=5)
I changed it to
SCAN_INTERVAL = datetime.timedelta(minutes=10)
Will this change the polling? Currently I am waiting until my account is unlocked. Fingers crossed.......
So you can't even log into the server.growatt.com website? That's the first I've heard of that happening.
You can change the code like that if you want, but 5 minutes should be enough.