-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG - [Work one day yes, one day no...] #52
Comments
I recommend reading the "IMPORTANT NOTICE" on the home page: https://github.com/muppet3000/homeassistant-growatt_server_api?tab=readme-ov-file#important-notice |
I use multiple visitor accounts which are set up inside and work fine with the pvplusanz (Jinko) portal. I assume this would also work with the Growatt portals. The HA integration easily accepts any of the visitor logins which I alternate to the next one each time the data stops flowing (I delete the entry and add a new one with the next credential in the list). Each visitor login can use the identical email address (see the image), so no need to have multiple email addresses, just portal logins as visitors. eg user 1, user 2, user 3, user 4 etc.
Currently I delete and then re-add here with the new visitor login every day or so, sometimes it lasts longer between changes. |
As I've announced on the landing page of this repo I have decided to stop adding features to this repo due to the various issues with the API integration. I have switched my focus to the Grott implementation and actively support and maintain that instead. However, if people wish to submit PRs to this repo I will happily review and release them. As I am no longer a user of the integration I have no way of testing it. |
For those interested I've updated the Growatt HA component with a bunch of features for controlling TLX inverters. It uses an updated version(v 1.6.0) of the https://github.com/indykoning/PyPi_GrowattServer package, see the README.md file. Most notably I might have been able to solve the issue with being constantly thrown out of from the app, and getting the account locked. This version only calls api.login() at startup and if/when the session expires, not before every api call. Will do a pull request to the official https://github.com/home-assistant/core after some more testing. |
Describe the bug
Hi. The application work fine, but work one day yes, one day no. I need to recharge the integration via home assistant and, sometimes, it restart. it does not have continuity of operation. Also, when it works fine on home assistant, I get blocked on the "shinephone" smartphone application
To Reproduce
Growatt Device Type
Device(s):
Home Assistant information
Additional context
N/A
The text was updated successfully, but these errors were encountered: