ENHANCEMENT - MAX/MID/MAC systems are not supported

[muppet3000]

Describe the bug See:

• Original - https://github.com/home-assistant/core/issues/51660
• Duplicate: https://github.com/home-assistant/core/issues/78117
• Duplicate: https://github.com/home-assistant/core/issues/84190

Growatt Device Type

Device(s): MAX/MID/MAC

Home Assistant information

• Home Assistant version: N/A
• Growatt Server API Integration version: N/A

Additional context

This bug has been duplicated from the originals in the Home Assistant Core repo and will be fixed here before before being merged up-stream. Everyone that has contributed to the bugs so far has been tagged in the comments so that they can receive updates from this repo.

[muppet3000]

Hi All, sorry for the mass-tagging but I wanted you all to know about the new ticket that I've raised in this repo for adding support for the MAX/MID/MAC type of inverter to the integration. As you're hopefully all aware I've moved the plugin out of Core and will primarily maintain it here because it's much easier and quicker to develop. When there are significant releases I will merge the changes up-stream into Home Assistant Core, but that will be much slower.

Now for the tags...... From https://github.com/home-assistant/core/issues/51660 @02dag @ciceroaferreira @MaoZ1993 @chrisp250 @MellowYingMarshmellow @RienduPre @chrisp250 @Benchamoneh @jkkataja @WTHStefan @pvhpsb @Jojotjo56 @Escooby @wurliwax @coleburg @shocker2

From: https://github.com/home-assistant/core/issues/78117 @rybber78 @IversenT @jolaca01 @affer @GerJanArts @epper202

From: https://github.com/home-assistant/core/issues/84190 @pvprodk

No need to add further comments, I have everything I need in hand to implement this. I've just been busy pulling the integration out of Core, I have 1 more bug to fix and then I'm straight on to this one!

[shocker2]

Hi @muppet3000 , Just switched to the new repo and for the invertor, everything works great! Thank you for your work! Hopefully, soon we will have the smart meter implemented and values populated :)

Cheers!

[muppet3000]

@horstefan - I recommend following this ticket.

[jkkataja]

@muppet3000 hi, just noticed your message about moving towards using Grott (https://github.com/muppet3000/homeassistant-growatt_server_api/issues/15#issuecomment-1487454839) (which isn't surprise considering the pain the Growatt servers seem to be causing :( ) and wanted to ask how this change will impact this issue?

That is, do you think you will work on this one afterwards or how will it go?

Thanks

[Saentist]

Grott is useful when ha is on location but absolutely unuseful for remote location. https://github.com/muppet3000/homeassistant-growatt_server_api/issues/31

[pmp02]

Integrating Grott would be great as we would get rid of the cloud accounts locking and throttling by Growatt. Maybe it could be done with "option" - use Grott or use Cloud poll - to cover both scenarios (both local and remote locations).

But totally +1 (or more) coffees for Grott integration and MAX/MID/MAC integration.

[turfsurf]

Grott is useful when ha is on location but absolutely unuseful for remote location.

Why? There is nothing preventing grott from running on a different location than the inverter. Or a basic ha with grott could run on the remote location and pointing grott to a local mqtt server.

[Saentist]

Grott is useful when ha is on location but absolutely unuseful for remote location.

Why? There is nothing preventing grott from running on a different location than the inverter. Or a basic ha with grott could run on the remote location and pointing grott to a local mqtt server.

More easy to re-route ip traffic or cheap to reflash wifi module

[muppet3000]

@muppet3000 hi, just noticed your message about moving towards using Grott (#15 (comment)) (which isn't surprise considering the pain the Growatt servers seem to be causing :( ) and wanted to ask how this change will impact this issue?

That is, do you think you will work on this one afterwards or how will it go?

Thanks

I'm not sure if you've tried using Grott at all yet, but it has support for pretty much every inverter and then it provides the output in a common format, so I'm hoping this issue just won't even exist with the new integration. If we still have issues we'll address it then.

[muppet3000]

Grott is useful when ha is on location but absolutely unuseful for remote location.

Why? There is nothing preventing grott from running on a different location than the inverter. Or a basic ha with grott could run on the remote location and pointing grott to a local mqtt server.

As you say, so long as you have grott accessible with a public IP you can configure the wifi dongle or shinelan box to forward the data wherever you want.

[jkkataja]

@muppet3000 hi, just noticed your message about moving towards using Grott (#15 (comment)) (which isn't surprise considering the pain the Growatt servers seem to be causing :( ) and wanted to ask how this change will impact this issue? That is, do you think you will work on this one afterwards or how will it go? Thanks

I'm not sure if you've tried using Grott at all yet, but it has support for pretty much every inverter and then it provides the output in a common format, so I'm hoping this issue just won't even exist with the new integration. If we still have issues we'll address it then.

I had not looked in to it before too much but looks good, can't wait to setup your integration soon, especially since Growatt has now blocked access two days in a row now 😅

[muppet3000]

Given the fact that the Growatt API is increasingly unreliable (see #15) I have slowly winding down support for this repo and instead directing people towards trying Grott instead: https://github.com/muppet3000/homeassistant-grott

I'm happy to help people out migrating over to the new method, it's far more reliable and I'm focussing all my efforts into making it the best possible option for everyone (including feeding back changes to the main developer)