Skip to content
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

Open
sagara939 opened this issue Jun 19, 2024 · 6 comments
Open

BUG - [Work one day yes, one day no...] #52

sagara939 opened this issue Jun 19, 2024 · 6 comments
Labels
bug Something isn't working triage Needs to be triaged to determine if it's an issue

Comments

@sagara939
Copy link

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

  • Home Assistant version: 2024.6.3
  • Growatt Server API Integration version: 1.0.4

Additional context

N/A

@sagara939 sagara939 added bug Something isn't working triage Needs to be triaged to determine if it's an issue labels Jun 19, 2024
@muppet3000
Copy link
Owner

I recommend reading the "IMPORTANT NOTICE" on the home page: https://github.com/muppet3000/homeassistant-growatt_server_api?tab=readme-ov-file#important-notice

@caitotheonlypotato
Copy link

caitotheonlypotato commented Jul 3, 2024

@muppet3000

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.
HA login just uses the visitor user name (eg user1) and the password you've setup


Now if within the integration setup process we could specify a number/group of credentials and then auto rotate those credentials daily (eg at midnight or at a specified time), then I think all the issues would be solved for everyone.

image

Currently I delete and then re-add here with the new visitor login every day or so, sometimes it lasts longer between changes.

image

@caitotheonlypotato
Copy link

Setup is easy in the portal, just set user, can be anything.
Set passwords can be anything, but I keep mine the same
Add name and nickname if you like.

image

@muppet3000
Copy link
Owner

muppet3000 commented Jul 3, 2024

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.

@johanzander
Copy link

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.
I have been running this for a week now, and haven't been locked out once:
https://github.com/johanzander/core/tree/growatt_component_update/homeassistant/components/growatt_server
If someone wants to try it out, just copy the content of /components/growatt_server to the /custom_components/growatt_server and add a version to the manifest file (required for custom_components).

Will do a pull request to the official https://github.com/home-assistant/core after some more testing.

@caitotheonlypotato
Copy link

Seems great to me, I've had 2 weeks now without a disconnect, whereas previously 2-3 days was the max

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Needs to be triaged to determine if it's an issue
Projects
None yet
Development

No branches or pull requests

4 participants