SPH3000–6000 priority change (Grid First / Load First) via Modbus

[OliverLang123]

Hi,
does anyone know how to change PRIORITY on SPH3000–6000 in the same way it is changed via server.growatt.com?

When using the Growatt portal, the priority clearly changes (e.g. Grid First / Load First), but we haven’t been able to reproduce the same behavior via Modbus.

Is there a specific sequence of registers, timing requirement, or hidden flag that needs to be set together with the time slots?

This was discussed here, but I somehow couldn’t find an answer.

Any hints or reverse-engineering insights would be very helpful. Thanks!

[peteS-UK]

Hi @OliverLang123 . Same question for me on the same inverter. When you say you set this on server.growatt, do you just mean by setting a schedule and enabling it, or is there a way to set the priority directly (sorry, haven't found that one). I wonder if we need to try setting the times of one of the schedules and then enabling it instead of using the inverter priority, but that doesn't seem to work - as discussed, that might need the group setting approach.

[brad5505]

I am controlling battery charge/ discharge (battery first/grid first) directly (not through the growatt server) using modbus VPP settings. These modbus settings will be available in the next update.
The settings are turned on and off via automation to set time (time period for the battery to charge/ discharge), power(rate of charge/discharge as a percentage - negative value = grid first, positive value = battery first) remote enable, then VPP status to enable in this order.

Below is an example of the action part of the automation to start a grid first sequence:
sequence:
- action: number.set_value
metadata: {}
data:
value: "114"
target:
entity_id: number.growatt_inverter_vpp_time
- action: number.set_value
metadata: {}
data:
value: "-80"
target:
entity_id: number.growatt_inverter_vpp_power
- action: select.select_option
data:
option: Enabled
target:
entity_id: select.growatt_inverter_vpp_remote_control
- delay:
hours: 0
minutes: 0
seconds: 1
milliseconds: 0
- action: select.select_option
data:
option: Enabled
target:
entity_id: select.growatt_inverter_vpp_status

The battery charge/discharge stops (goes back to load first) after the time period enterd or you can use a second automation to set timers and power to zero, and VPP the VPP remote and status to disabled

[OliverLang123]

Hi,
thank you for the detailed explanation and the example - that helps a lot.

At the moment, I’m not able to find any mention of VPP in the Modbus documentation that I have available (GROWATT INVERTER MODBUS RTU PROTOCOL II, Version V1.37). Because of that, I’m missing the context for which specific registers are involved, their exact meanings, valid ranges, and any required write sequence or dependencies.

Could you please share the VPP-related documentation, if this is covered in a separate or extended Modbus document?
If it’s an extra document or part of a newer revision, having it would be extremely helpful.

Thanks in advance.

[peteS-UK]

Hi, thank you for the detailed explanation and the example - that helps a lot.

At the moment, I’m not able to find any mention of VPP in the Modbus documentation that I have available (GROWATT INVERTER MODBUS RTU PROTOCOL II, Version V1.37). Because of that, I’m missing the context for which specific registers are involved, their exact meanings, valid ranges, and any required write sequence or dependencies.

Could you please share the VPP-related documentation, if this is covered in a separate or extended Modbus document? If it’s an extra document or part of a newer revision, having it would be extremely helpful.

Thanks in advance.

I only have an even older version of that doc - do you have a link to 1.37 perhaps?

In the code for the growatt plugin, I see these selectors

	GrowattModbusSelectEntityDescription(
        name = "VPP Status",
        key = "vpp_status",
        register = 30100,
        option_dict = {
                0: "Disabled",
                1: "Enabled", },
        allowedtypes = GEN3,
        entity_category = EntityCategory.CONFIG,
        entity_registry_enabled_default = True,
        icon = "mdi:dip-switch",
    ),
    GrowattModbusSelectEntityDescription(
        name = "VPP Remote Control",
        key = "vpp_remote_control",
        register = 30407,
        option_dict = {
                0: "Disabled",
                1: "Enabled", },
        allowedtypes = GEN3,
        entity_category = EntityCategory.CONFIG,
        entity_registry_enabled_default = True,
        icon = "mdi:dip-switch",
    ),

and these sensors

	GrowattModbusSensorEntityDescription(
        key = "vpp_status",
        register = 30100,
        scale = { 0: "Disabled",
                  1: "Enabled", },
        allowedtypes = GEN3,
        internal = True,
    ),
    GrowattModbusSensorEntityDescription(
        key = "vpp_remote_control",
        register = 30407,
        scale = { 0: "Disabled",
                  1: "Enabled", },
        allowedtypes = GEN3,
        internal = True,
    ),
    GrowattModbusSensorEntityDescription(
        key = "vpp_time",
        register = 30408,
        allowedtypes = GEN3,
        scale = 1,
        internal = True,
    ),
    GrowattModbusSensorEntityDescription(
        key = "vpp_power",
        register = 30409,
        unit = REGISTER_S16,
        allowedtypes = GEN3,
        scale = 1,
        internal = True,
    ),

and perhaps some other bits. I believe they're planned for the next release from something I read earlier.

[OliverLang123]

Growatt Inverter Modbus RTU Protocol_II V1_37-English-20240130(1).pdf

Hi, here is the doc.

However, none of the mentioned registers are present in the documentation. It is likely that there is a separate document specifically for VPP. However, I do not want to write to registers blindly.

[brad5505]

The VPP register details are in the link below. This came from the discussion

#1631

The VPP code has been incorporated in the growatt plugin ready for the next releas. I hope this information helps.

https://growatt-support.com/media/files/be3387f3db485f11ae5243fc71dd7c423d4f2937b7f07b9bf88044b03562db3f/?name=Growatt%20Modbus%20protocols_2024_09.zip

[OliverLang123]

Thanks. And do these VPP registers relate to inverter settings that are configured by the installation company or by the end user?
I mean, for example: if I set the minimum SOC to 10% or the export limit to 80% via server.growatt.com, will I also see these values reflected in the VPP registers? And conversely, if I modify these values via the VPP registers, will the changes be reflected back in server.growatt.com?
Thank you in advance for your response and for the clarification — I am still a bit lost in this.

[brad5505]

I assume that VPP registers modified by modbus settings would be reflected by reading them through server.growatt.com and the shinephone app. However, as all the VPP registers that I use (to control battery first/ grid first - 30100, 30407 to 30409) do not show up in the shinephone app. I have not tried setting any of the other VPP registers.