No GoSungrow command

[TrueBlueRoo]

There is no GoSungrow command available on HA Supervisor. Couldn't locate it through a find as well.

Thanks

[Paraphraser]

Hi,

I know it’s not immediately obvious but there are a few thing you need to do before you can get this running on Home Assistant:

1. Follow the instructions at MickMake/HomeAssistantAddons. That gets you as far as having the GoSungrow add-on installed. But (and this is a key point), it will not work until you’ve done the next two steps.

2. If you have not already done so, install two other add-ons:

   • “Mosquitto broker”. The default configuration (which implies your Home Assistant username and password) is sufficient. If you have an existing MQTT broker, you can use that instead.
   • “Advanced SSH and Web Terminal”. It must be advanced. Nothing else will do. The configuration instructions for this are part of step 3 below.

3. Follow the steps in Part 2 of this Gist.

Why all the convolution? Well, I’m not the author of this site so I don’t really know but, at a guess:

• This repo is for the GoSungrow binary while the HomeAssistantAddons repo is where the GoSungrow binary is wrapped into a Docker container which can be deployed by Home Assistant.

  Other than testing GoSungrow, I don’t use HA for anything so I’m not really familiar with its norms and can’t say whether adding a repo’s URL to HA is something that is standard or unusual.

• In its “HA add-on” form, GoSungrow goes into MQTT mode so it needs an MQTT broker. Because GoSungrow sprays an absolute crate-load of MQTT messages on every update, it’s probably better to have the comms path as short as possible, and a broker on the same HA instance fits that bill. But, in principle, any broker will work.

• You need “Advanced SSH and Web Terminal” in order to be able to apply a patch to GoSungrow to get it to work. This is suboptimal but it’s the best we (the community around this site) can do until MickMake comes back. Strictly speaking, it’s a “hack”.

In essence, the “hack” works like this:

• The starting point is a broken version of GoSungrow add-on installed during step 1. This sort of primes the HA pump and sets up the necessary hooks.
• Then, a patched version of the GoSungrow add-on is downloaded from DockerHub. By itself, that won’t do anything.
• Then some Docker switcharoo is employed so that when HA goes looking for GoSungrow it finds the patched version.

There are still some wrinkles involving AppKeys and picking the correct URL for where your inverter is logging its data but, once that’s all sorted out, it (mostly) starts working. That’s all covered in the last part of the Gist.

I say “mostly” because I get the sense that people who have multiple Sungrow inverters have more trouble - possibly to the extent that they either get it working and don’t say how, or never get it working and give up without reporting that they’ve given up.

Hope this helps.

[TrueBlueRoo]

Thanks mate. Highly appreciated.

It got the GoSungrow running now. I run it in a VM on Windows Server.
That was excately that kind of tutorial what I couldn't find.

The next step I am stuck is the HA's Energy Dashboard. How do I get those sensors running like sensor.gosungrow_virtual_XXXXXXXXXXXXXX_grid_to_load_energy ?

Any help would be appreciated.

Cheers :)

[Paraphraser]

Sorry. Can't help you with that bit. You'll have to hope someone else with more experience chimes in to answer that bit.

In my own case, I just use the compiled binary running on a Mac (nothing to do with Home Assistant). Once a day a cron job fires to invoke GoSungrow to download "yesterday's" data at 5-minute resolution for the 12 metrics I need. I'm essentially continuing a time-series for an older SolaX inverter. I load the results of the GoSungrow fetch into an SQLite database. That's all I need and as far as I go. If I want to know what the Sungrow inverter is up to "now", I just use the iSolarCloud app.