-
Notifications
You must be signed in to change notification settings - Fork 17
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
open a discussion page #93
Comments
I still suggest to open a discussion page to have a spot for discussion on points below and beyond issue and feature request. For example: thanks a lot for your good work I just upgraded to grott ha 1.12 and that was a reminder to say thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
after the mess of the broken grott installation due to growatts resetting of the wifi sticks to their server I was looking now through a lot of other issues on the grott and grott ha integration side just to avoid that I have missed an important thing like this mess above.
While reading those other issues I recogniced that more or less 50% are no issues of the integration at all and usually belong to grott.
For new users a long list of still open and old(er) issues is not looking very good, not really inviting and therefore time to close those issues where users ask "how to compose or docker whatsoever".
They steal time from those who wanna be up to date.
And to avoid further stress I guess it would be usefull to open a "discussion" page where you should be able to move those issues simply to get a clean overview what is going on - for you and all others. I have read really a lot and started to comment that people should close it cause usually it was not a genuine HA grott integration issue.
This topic itself would also belong there and could be moved into the discussion.
Great work and progress especially in the discussion about the issue that appeared about 2 weeks ago where growatt deleted our grott server ids in the WiFi sticks. Quite long right now, but I found all the bits and pieces needed to solve that for me in a way that I can still edit my inverters, which usual users would not do, except those hybrid inverter owners that change the charging and discharging plans based on the hourly tarifs tomorrow and the forecast of tomorrows production.
thanks
The text was updated successfully, but these errors were encountered: