-
Notifications
You must be signed in to change notification settings - Fork 1
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
what code base is addon-grott-beta relying and more open questions #61
Comments
Hi, I apologise for the confusing situation about the grott version, I'm trying to track the current version as there is not really a tag. If you look at the last commit message of this version : https://github.com/johanmeijer/grott/tree/c97bd8ca8c6b8dd778cd3a089711703e0a60bd7e it is noted 2.8.3. There was the grott-stable and beta a one point because there were 2 branch (2.7 and 2.8) but now there is only 2.8 so they are mostly identical. Thanks for showing me there is a new 2.8.3 release. I will update to the most recent code. For the grott-HA plugin, this has also changed, as it is now a pypi library and not just a copy and paste: https://pypi.org/project/grott-ha-plugin/ the correct version is 0.11.0. This part interprets the decode JSON from grott and generates directly the devices in a HA MQTT devices. So to resume:
I will update the doc to correct the typo |
I will try to take into account what you are suggesting, but it is probably going to take a couple of weeks as I don't have a lot of time at the moment. Meanwhile, you should switch to https://github.com/egguy/addon-grott/ as it is more up to date. The edge channel has not the latest 2.8.3 update. I will release it tomorrow as a tagged vesion. PS: I'm open to contributions, especially documentation and screenshots ;) |
Hi Etienne, thanks for all the explanations. I am thankfull for your quick and in depth reply. I can wait for the updates in the documentation but I simply wanna make sure how important it is to have a clean and straight line. Avoid beta cause the average user is not the risk taker to trust a beta which is not a beta cause your part of the code would be stable I guess. I hope we will see Simple and clean to explain for newbies: you have HA then go for all the HA stuff, otherwise Grott 3.0 is your first choice. CAN YOU PLEASE HELP ME WITH THIS PART !? I have no clue what is wrong or what I have to change ? I had followed your instructions months ago and it had been working so far till the "wifi stick IP deletion powered by Growatt" hit me hard. UPDATE: I have found it by visiting the addon store and there I found a version 0.1.10 which looks quite different from the first look . I will do a backup now and then change the repository to Regarding supporting you with some tasks: Again: I will try to help you out with documentation and screenshots especially the variety of growatt inverters I have here and have a reminder put in place for january 2nd 2025 to get in touch with you. |
And finally: What about a discussion page on github to avoid the flood of open issues that never had been open issues like this one I guess ? As a new users I tend to look first into the documentation, youtube and then dig into the open issues and look what is going on there. And therefore a clean and short list is better than a longer one with topics of low importance. |
Hi,
I had to fight a lot with the growatt deleted the grott ip in the wifi sticks adventure cause I was not aware of what was going on cause at the exact same time I had a maintenance week for my 8 inverters and got a new second distribution board and a complete AC re-wiring, then a new LAN cable and switches plus WLAN repeaters.
And when I came back with all my inverters everything was gone. And I had thought it must have been my fault cause the inverters were off grid and offline during all the rewiring. I had no clue what was going on except the growatt sensors were dead or depreciated and showed me a warning. Then I found out that the datalogger IP settings had been deleted which I had assumed was caused by the off grid situation for days.
Long story short it took me days or roughly a week to get behind and find the solution which seems to be reliable: I reentered the IP adresse in the datalogger and then had set the ggrowattip to 8.209.71.240
Growatt is no longer deleting my settings and I can still edit my settings of the SPH inverter especially discharging schedules and so on.
BUT: during all the mess when I was not aware what was going on I wondered about the basics like who can help me and what information would be needed. And of cause which version are you running was one of the first.
I had thought for whatever reason and believed I was running grott 2.8.3 as latest release but IS THAT REALLY true ?
And this is the weak or inconsistent point at least right now for me:
I have opened Grott addon and found this
![image](https://private-user-images.githubusercontent.com/20662430/353043315-b03f4c9f-060c-439c-a3f9-bc2d98ed9315.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM4NzIxMjgsIm5iZiI6MTcyMzg3MTgyOCwicGF0aCI6Ii8yMDY2MjQzMC8zNTMwNDMzMTUtYjAzZjRjOWYtMDYwYy00MzljLWEzZjktYmMyZDk4ZWQ5MzE1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE3VDA1MTcwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk0YzU0YWU3MjY2OGMxZTZkN2U5YThmZDI5MjMyY2JjMWY5YmZlMTdlMTcxZTNhMDI1NzBjYmE0YmM1ZWMwMDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.lBPC4_5d3y0Y7pP3rcYjeJq5nyl8_XiTvjSJhnCAv-M)
And now I am wondering what is wrong: Am I running grott 2.8.3 or just 2.8 ?
Big differences regarding the support of different new inverters but I am not sure.
Then there is the second line called "Current version 0.1.7" with a link to a change log but also a lot more times where you simply find "grott 2.8"
I suggest to reduce how often you mention the version cause you would have to maintain that too, over time a lot of work if you wanna change that everywhere.
I am assuming that this grott ha is already 2.8.3 cause all the new min sph and what not invertermodels are implemented in this addon which grott has released with 2.8.3 I guess - not sure, but I believe there was a major change.
Finally I like the 1.0.7 in the second line and the change log but I miss that same number here on github cause I could not find that or overlooked that.
But again the whole thing becomes confusing cause if I look on the top of this page I can read
"egguy / addon-grott-beta"
and if I open the main page what do I have to read there ?
Grott beta 2.8.x
It is time to find a less confusing naming sheme used everywhere which clearly shows the roots, history and where it is like
"GROTT BETA 2.8.3 - The HA ADD ON V1.0.7"
Not 2.8.x which is confusing if Grott is 2.8.1 or 2.8.2 or 2.8.3 cause people will ask Johan for advice like I did and he will ask first WHICH version and of cause I told him "2.8.3" in my deepest believe but I am still not sure if that is true or not.
And then all the references like "addon is based on the 2.8 Branch of grott" is obsolete cause the root and the right version are part of the project title.
Side node: on that Grott beta 2.8.x page there you can find this line
"The grott server decodes them andsendsd them to your HA instance."
where I suggest to correct the "andsendsd" to "and sends" plus to mention also mqtt as the transmitter and receiver cause right now grott server is handing those data over to mqtt and the sending is done by mqtt.
Tiny point but important for newbies to understand that this essential element mqtt is mentioned in the big picture. Otherwise you would not know about mqtt till you end in the configuration.
I know these are tiny points but I guess it is time to take care for these especially in times when things had gone wrong and nothing seems to work anymor where everyone is searching for advice and solutions.
You have achieved a lot and there are just tiny bits / pieces missing like using the same term every time like 2.8.3 instead of 2.8.x and so on.
Great progress regarding the updates that came along with 1.0.7
The text was updated successfully, but these errors were encountered: