I’m one of the primary maintainers of the Growatt Integration for Home-Assistant. I’ve made various promises over the last year or so to implement various bits of missing functionality etc. etc.
I have finally found the time to sit down and collate all of the items and prioritise them based on 2 key factors:
Ease of implementation/fix
How long ago the issue was raised and promises were made about implementing it
For each item that is listed here there is a corresponding Github issue for it. I may need to reach out to various people in order to access their Growatt systems in order to make the integration work in their scenarios, if I’m delayed in being granted access then I’ll move onto the next item in the list.
I’d like to remind everyone that this is something I work on in my spare time only, I can’t promise timescales etc. but I can promise that I take this stuff seriously and want to get the most out of this integration for everyone.
My plan is to keep this top level post as something that I will continually edit with updates to priorities and implementation progress.
If there are items that I’ve missed then drop a comment below and I’ll work to get it prioritised. So, without further ado, the mega list (in priority order):
The following issue also deserves an honourable mention because I did take a crack at implementing a workaround for it last year and then gave up, but I’d like to track it:
Min/Mic & TLX systems have their lifetime_energy_output reset to 0 overnight and then back to the correct value in the day
Min/Mic & TLX
Closed - Inactivity
UPDATE - With recent challenges interfacing with Growatt I have made an additional post here: Growatt Integration - Roadmap outlining my plans going forward.
Edit/Update
Since 07/02/2023 (7th Feb) Growatt have started implementing rate limiting and blocking to user accounts that make excessive API calls i.e. this integration. There is an extended discussion around it here.
If you’re interested in the short version read these posts: first, second, third
The recent developments throw into question the long-term viability of this Integration, please see the ‘third’ link above for the proposed plan.
Hi muppet. thanks for doing this update… looking forward to the future of growatt HA interegration, any chance that you might look on implementing inverter settings and charging times from GitHub - muppet3000/PyPi_GrowattServer. That would be really nice
Do you know if anyone tried reaching out to the Growatt people see if they would be interested in supporting this work? Just thinking it might be good to have them helping, even if just with upcoming changes they might be planning to the server.
Hi to All.
First of All, thank you for your great work.
Sorry for my question, but I cannot find the Mod TL3-X converters or ARK HV battery Systems in the List. Can someone told me if this components are in the Integration List or should we Start a New github report? Sorry for my question, but i am realy New here. The actuel Integration of this products doesn’t Shows something about the battery State und also the converter data are very slim.
Thanks and greetings,
Markus
I’ve never tried reaching out to them, other than for support issues. AFAIK they’re a Chinese company with pretty shoddy customer support, so I’d be surprised if we ever heard an official response
The other risk is that if they actually engage with us and they don’t really like all the extra calls to their API then they find a way of shutting it down altogether.
It’s unlikely that we have support for that yet, however I can check if you can tell me what type of system the growatt UI shows you as having, this this:
That’s interesting, that’s a device we do have support for. I’d recommend adding a new report on Github detailing what the issue is and I’ll then add it to this list.
Okay.
I have 27 entries and 2 Devices, but no battery data and no historic values like own consumption, load consumption, feed into grid or something like that. Therefore, i have o lot of temperatures, voltages und frequenz for the both input strings.
As discussed in more detail here I have started the process of moving the Growatt Server integration out of Home Assistant Core and into a custom integration. This will allow for much faster responses when there are issues with authenticating against the Growatt Servers as we’ve seen in recent months.
Over the next few weeks I will be removing the Growatt integration from the Core repository of Home Assistant, however, to give people time to switch over to the new integration I have already published it here (new repo) with a comprehensive guide on how to install it (it’s quite straight forward).
Once you have it installed, delete the previous integration and then switch to using the new one, step-by-step with pictures here
IMPORTANT: The new integration is the only place that new fixes & features will be released
Next steps:
The documentation here (growatt_server) will be updated to recommend using the new integration instead
The existing bugs against the Growatt integration in Home Assistant will be migrated/copied to the new repository
New features & fixes will be worked on
I apologise for the inconvenience that this causes, however it’s in the interest of the stability of Home Assistant Core as well as the ability to provide swift responses to issues in the plugin that I’m making this change.
Any questions related to this, please add them as issues on the new repo here (issues) and I’ll respond as fast as I can.
