Solar PV Monitoring/Automation Thread

Seems to be an issue with the command-line as I got the same here.

I stuck it into a docker-compose.yaml file, touched the options.yaml file and it worked fine (as far as I can tell as I don't have a sunsynk).

me@server:/bigpool/1tb/portainer/stack/keller$ sudo touch options.yaml
me@server:/bigpool/1tb/portainer/stack/keller$ docker compose up -d
[+] Running 1/2
 ⠼ Network keller_default           Created                       0.4s 
 ✔ Container keller-sunsynk-multi-1 Started                       0.3s 
me@server:/bigpool/1tb/portainer/stack/keller$ ls
docker-compose.yaml options.yaml

me@server:/bigpool/1tb/portainer/stack/keller$ cat docker-compose.yaml 

version: "3"
services:
 sunsynk-multi:
   restart: unless-stopped
   image: ghcr.io/kellerza/hass-addon-sunsynk-multi/amd64:stable
   volumes:
     - /bigpool/1tb/portainer/stack/keller/options.yaml:/data/options.yaml

Yeah, setting the discharge times on the portal or your phone is probably easiest. Alternatively you could just use PowerShell with the token (from the website) and then have two Scheduled task on a machine connected to the web, one at 00:00 to tell it to start discharging and the other at 02:00 to stop.

Worth investing a little bit of time to learn/play around with using the powershell interface. Once you learn it (and it's pretty easy tbf) then you open up a lot of possibilities such as "if the battery is greater than 40% soc then dump at x kw for 90 minutes"

Here's a sample piece of PowerShell which sets the discharge limit. Change 2x things, the "token" (xxxxx) which you can get for your account from the Givenergy portal and the inverter name (yyyyy) again this is from the portal (something like SD12345678) and then run it and you should be able to see it change the "discharge rate" on the portal. (You can easily change the discharge rate back in the portal)

# Set system variables
$baseUri = "https://api.givenergy.cloud/v1/"
$json_extration_folder = "C:\Tools\GivEnergy\Cloud_Extract\"
$filename_Datetime = get-date -format "yyyyMMdd_HHmm"
$Inverter_date = get-date -format "yyyy-MM-dd"

$Bearer_Token =
"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

#---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
# Get the Current top level Inverter Status (Grid voltage, Battery SOC, Solar power, etc 
#---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
$loginUri = "https://api.givenergy.cloud/v1/inverter/yyyyyyyy/settings/73/write"

$headers = @{Authorization = "Bearer $Bearer_Token"}

$tokenRequestBody = @{
  'Content-Type' = "application/json"
  'Accept' = "application/json"
  'value' = '1234'
}

$lenght_token = $tokenRequestBody.Authorization.length

$output_filename = $json_extration_folder + "Set_Discharge_to_2600w_"+ $filename_Datetime + ".json"
$login_response = Invoke-RestMethod -Method 'POST' -Uri $loginUri -Body $tokenRequestBody -Outfile $output_filename -Headers $headers

A non-exhaustive list of the REST API's is

<#
{"data":[{
"id":17,"name":"Enable AC Charge Upper % Limit","validation":"Value must be either true or false"},{
"id":24,"name":"Enable Eco Mode","validation":"Value must be either true or false"},{
"id":28,"name":"AC Charge 2 Start Time","validation":"Value format should be HH:mm. Use correct time range for hour and minutes"},{
"id":29,"name":"AC Charge 2 End Time","validation":"Value format should be HH:mm. Use correct time range for hour and minutes"},{
"id":41,"name":"DC Discharge 2 Start Time","validation":"Value format should be HH:mm. Use correct time range for hour and minutes"},{
"id":42,"name":"DC Discharge 2 End Time","validation":"Value format should be HH:mm. Use correct time range for hour and minutes"},{
"id":47,"name":"Inverter Max Output Active Power Percent","validation":"Value must be between 0 and 100"},{
"id":53,"name":"DC Discharge 1 Start Time","validation":"Value format should be HH:mm. Use correct time range for hour and minutes"},{
"id":54,"name":"DC Discharge 1 End Time","validation":"Value format should be HH:mm. Use correct time range for hour and minutes"},{
"id":56,"name":"Enable DC Discharge","validation":"Value must be either true or false"},{
"id":64,"name":"AC Charge 1 Start Time","validation":"Value format should be HH:mm. Use correct time range for hour and minutes"},{
"id":65,"name":"AC Charge 1 End Time","validation":"Value format should be HH:mm. Use correct time range for hour and minutes"},{
"id":66,"name":"AC Charge Enable","validation":"Value must be either true or false"},{
"id":71,"name":"Battery Reserve % Limit","validation":"Value must be between 4 and 100"},{
"id":72,"name":"Battery Charge Power","validation":"Value must be between 0 and 2600"},{
"id":73,"name":"Battery Discharge Power","validation":"Value must be between 0 and 2600"},{
"id":75,"name":"Battery Cutoff % Limit","validation":"Value must be between 4 and 100"},{
"id":77,"name":"AC Charge Upper % Limit","validation":"Value must be between 0 and 100"},{
"id":83,"name":"Restart Inverter","validation":"Value can only be 100"}]}
#>

So depending on the setting you want to change , you modify the number below as follows

$loginUri = "https://api.givenergy.cloud/v1/inverter/yyyyyyyy/settings/73/write"

and that's it.

Wouldn't it just depend on which devices are monitoring (using a CT) at the closest point to the meter? I have a Shelly PM and it provides both "grid consumption" and "return to grid" from it (I just have a peak/offpeak tariff switch as a template):

Just wondering did any one add the standing charge as a sensor on the HA energy dashboard and how did you do it? Would be nice to get an accurate picture of the monthly cost

No, the house will take away from the export not from the grid. Only does that when you charge the batteries from the grid.

That's very like the NEXTION displays which were mentioned on here last week.

Integration was via ESPHOME, but the trick was that the ESP32 sent NEXTION commands over UART to the processor on the Nextion... That must also be what the ELECROW display is doing as ESP32 doesn't natively have that rendering capability.

Anyway, let us know how it goes.

Does the Nextion software not simplify that sufficiently? I was interested in getting one, are they just not mature enough?

And this part?

Set it to use a static price and it's just 0

Ok i got it the same as you now but now tell me how to get it to 0.78 🤣

Ok I had messed with the -472571 number and now I set it to the same as you, and yes I have the input number set to 0.78 and now it looks like this:

So it's at 0.833 already, maybe it will fix itself after midnight?