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

Version 5.0.0 is making my GoodWe inverter offline #106

Open
danwinp opened this issue Mar 28, 2024 · 11 comments
Open

Version 5.0.0 is making my GoodWe inverter offline #106

danwinp opened this issue Mar 28, 2024 · 11 comments

Comments

@danwinp
Copy link

danwinp commented Mar 28, 2024

After upgrading from 3.7.4 to 5.0.0 my SEMS portal app and web interface started going offline. When I downgraded to 3.7.4 it has fixed it.

I have tried different intervals too. Longest interval I tried was 10 minutes and it still broke in 5.0.0.

I am currently using 60 seconds interval in 3.7.4 and that seems to work fine.

@TimSoethout
Copy link
Owner

I don't have any issues in my log though.
Do you mean the HASS component breaks your regular sems site/app?

@danwinp
Copy link
Author

danwinp commented Mar 28, 2024

Yep it makes the sems site/app go offline after a certain time and it won't go back online unless I restart the inverter physically.

@danwinp
Copy link
Author

danwinp commented Mar 29, 2024

I installed this using HACS on my home assistant container in Truenas Scale.

@TimSoethout
Copy link
Owner

TimSoethout commented Mar 29, 2024 via email

@danwinp
Copy link
Author

danwinp commented Mar 29, 2024

I think it was ok with V4.0.0. I had it in V4.0.0 for a little more than a day or so and I don't remember it being an issue. It only started when I upgraded to V5.0.0.

I did make a separate guest/visitor account for it.

@danwinp
Copy link
Author

danwinp commented Mar 29, 2024

I just went straight to 3.7.4 as I have been on that for awhile without any issues. I needed my inverter to be working in the next several days as I use the automation to charge my EV car. I can try upgrading to V4 maybe after a week or so and report back to you if there is any issues.

@danwinp
Copy link
Author

danwinp commented Mar 29, 2024

Also do you know if there are settings to prevent it from rate limiting me?

@TimSoethout
Copy link
Owner

No settings unfortunately. It seems the switch PR (5.0.0) includes some non-optimal code that calls the API twice for each sensor. Maybe that results in you being rate limited. I'm currently coding something up, but will need to test it first. I'll try to do that over the weekend.

@TimSoethout
Copy link
Owner

Maybe combining it with #89 and #91.

@danwinp
Copy link
Author

danwinp commented Mar 29, 2024

Awesome. No rush, I really appreciate the work you've done for this!

@jonathansiero
Copy link

I'm also getting this.

Seems to have be happening with version 6.0.0 for me as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants