[Bug] Error trying to enable Grid Peak Shaving

[garganm]

Description

Whenever I try to enable Grid Peak Shaving I get the following Error:
Failed to perform the action switch/turn_on. Failed to set value for CID 636. Expected: 2081, got: 33

As a note the Activity Log also seems to show a new entry every time saying it has updated the Solis Solar Inverter Time just before the error message pops up

Logs

Please include relevant logs from Home Assistant. To enable debug logging for this integration:

1. Add the following to your configuration.yaml:

   logger:
     default: warning
     logs:
       custom_components.solis_cloud_control: debug

2. Restart Home Assistant

3. Reproduce the issue

4. Check the logs at Settings > System > Logs

2026-01-31 20:03:06.916 INFO (MainThread) [custom_components.solis_cloud_control.switch] Turn on 'Grid Peak Shaving' (value: 2081)
2026-01-31 20:03:06.916 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API request '/v2/api/control': {
  "inverterSn": "*********",
  "cid": 636,
  "value": "2081"
}
2026-01-31 20:03:15.129 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API response: {
  "code": "0",
  "data": [
    {
      "msg": "Send failed !****************    Communication error. Please refresh and try again later : The specified operation has failed. The device has timed out.",
      "code": 1,
      "command": "AT+TEST=GIN485:01 06 a8 66 08 21 8e 6d"
    }
  ],
  "time": "1769889787041"
}
2026-01-31 20:03:15.129 WARNING (MainThread) [custom_components.solis_cloud_control.api.solis_api] Retrying due to error: Control failed: Send failed !****************    Communication error. Please refresh and try again later : The specified operation has failed. The device has timed out. (API response code: 1) (attempt 1, elapsed time: 8.2s)
2026-01-31 20:03:16.130 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API request '/v2/api/control': {
  "inverterSn": "****************",
  "cid": 636,
  "value": "2081"
}
2026-01-31 20:03:16.527 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API response: {
  "code": "0",
  "data": [
    {
      "msg": "Send failed ! no response",
      "code": 1,
      "command": "AT+TEST=GIN485:01 06 a8 66 08 21 8e 6d"
    }
  ],
  "time": "1769889796153"
}
2026-01-31 20:03:16.528 WARNING (MainThread) [custom_components.solis_cloud_control.api.solis_api] Retrying due to error: Control failed: Send failed ! no response (API response code: 1) (attempt 2, elapsed time: 9.6s)
2026-01-31 20:03:18.528 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API request '/v2/api/control': {
  "inverterSn": "****************",
  "cid": 636,
  "value": "2081"
}
2026-01-31 20:03:19.377 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API response: {
  "code": "0",
  "data": [
    {
      "msg": "Send Success !****************    Time: 1769861050<br>NO: 1102<br>SN: ****************<br>Result: 0<br>Inverter1: <br>send: <br>recv: 0106A86608218E6D<br>",
      "code": 0,
      "recv": "0106A86608218E6D",
      "command": "AT+TEST=GIN485:01 06 a8 66 08 21 8e 6d"
    }
  ],
  "time": "1769889798550"
}
2026-01-31 20:03:19.377 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API request '/v2/api/atRead': {
  "inverterSn": "****************",
  "cid": 636
}
2026-01-31 20:03:20.290 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API response: {
  "msg": "success",
  "code": "0",
  "data": {
    "msg": "33",
    "yuanzhi": "33",
    "command": "AT+TEST=GIN485:01 03 a8 66 00 01 44 75",
    "needLoop": "false"
  },
  "orderId": "33",
  "time": "1769889799401"
}
2026-01-31 20:03:20.290 WARNING (MainThread) [custom_components.solis_cloud_control.coordinator] Retrying due to verification failed, current value: 33 (attempt 1/1)
2026-01-31 20:03:25.291 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API request '/v2/api/control': {
  "inverterSn": "****************",
  "cid": 636,
  "value": "2081"
}
2026-01-31 20:03:25.525 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API response: {
  "code": "0",
  "data": [
    {
      "msg": "Send failed ! no response",
      "code": 1,
      "command": "AT+TEST=GIN485:01 06 a8 66 08 21 8e 6d"
    }
  ],
  "time": "1769889805318"
}
2026-01-31 20:03:25.526 WARNING (MainThread) [custom_components.solis_cloud_control.api.solis_api] Retrying due to error: Control failed: Send failed ! no response (API response code: 1) (attempt 1, elapsed time: 0.2s)
2026-01-31 20:03:26.528 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API request '/v2/api/control': {
  "inverterSn": "****************",
  "cid": 636,
  "value": "2081"
}
2026-01-31 20:03:27.479 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API response: {
  "code": "0",
  "data": [
    {
      "msg": "Send Success !****************    Time: 1769861050<br>NO: 1108<br>SN: ****************<br>Result: 0<br>Inverter1: <br>send: <br>recv: 0106A86608218E6D<br>",
      "code": 0,
      "recv": "0106A86608218E6D",
      "command": "AT+TEST=GIN485:01 06 a8 66 08 21 8e 6d"
    }
  ],
  "time": "1769889806549"
}
2026-01-31 20:03:27.479 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API request '/v2/api/atRead': {
  "inverterSn": "****************",
  "cid": 636
}
2026-01-31 20:03:28.279 DEBUG (MainThread) [custom_components.solis_cloud_control.api.solis_api] API response: {
  "msg": "success",
  "code": "0",
  "data": {
    "msg": "33",
    "yuanzhi": "33",
    "command": "AT+TEST=GIN485:01 03 a8 66 00 01 44 75",
    "needLoop": "false"
  },
  "orderId": "33",
  "time": "1769889807497"
}
2026-01-31 20:03:28.280 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546802829568] Error during service call to switch.turn_on: Failed to set value for CID 636. Expected: 2081, got: 33

[config_entry-solis_cloud_control-01KGARTX3CGG9VK39K1M99SDJV.json](https://github.com/user-attachments/files/24985715/config_entry-solis_cloud_control-01KGARTX3CGG9VK39K1M99SDJV.json)

[config_entry-solis_cloud_control-01KGARTX3CGG9VK39K1M99SDJV.json](https://github.com/user-attachments/files/24985719/config_entry-solis_cloud_control-01KGARTX3CGG9VK39K1M99SDJV.json)

Diagnostics

Please download and attach the diagnostics file from the integration:

1. Go to Settings > Devices & services
2. Select "Solis Cloud Control" integration
3. Click on the device
4. Click "Download diagnostics"

Note

The diagnostics file is automatically redacted and does not contain sensitive information like API keys or full serial numbers.

{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2026.1.3",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.13.11",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Dublin",
    "os_name": "Linux",
    "os_version": "6.12.47-haos-raspi",
    "container_arch": "aarch64",
    "supervisor": "2026.01.1",
    "host_os": "Home Assistant OS 17.0",
    "docker_version": "29.1.3",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "browser_mod": {
      "documentation": "https://github.com/thomasloven/hass-browser_mod/blob/master/README.md",
      "version": "2.7.1",
      "requirements": []
    },
    "ui_lovelace_minimalist": {
      "documentation": "https://ui-lovelace-minimalist.github.io/UI/",
      "version": "v1.5.0",
      "requirements": [
        "aiofiles>=0.8.0",
        "aiogithubapi>=22.2.4"
      ]
    },
    "hon": {
      "documentation": "https://github.com/gvigroux/hon",
      "version": "0.7.22",
      "requirements": []
    },
    "cafe": {
      "documentation": "https://github.com/FezVrasta/cafe-hass",
      "version": "0.4.1",
      "requirements": []
    },
    "better_thermostat": {
      "documentation": "https://github.com/KartoffelToby/better_thermostat",
      "version": "1.7.0",
      "requirements": []
    },
    "hacs": {
      "documentation": "https://hacs.xyz/docs/use/",
      "version": "2.0.5",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "solis": {
      "documentation": "https://github.com/hultenvp/solis-sensor/",
      "version": "4.0.1",
      "requirements": [
        "aiofiles>=23.1.0,<25.0.0"
      ]
    },
    "solis_cloud_control": {
      "documentation": "https://github.com/mkuthan/solis-cloud-control",
      "version": "2.16.0",
      "requirements": []
    },
    "familylink": {
      "documentation": "https://github.com/noiwid/HAFamilyLink",
      "version": "1.0.1",
      "requirements": [
        "aiohttp>=3.8.0",
        "cryptography>=3.4.8"
      ]
    },
    "solis_modbus": {
      "documentation": "https://solis-modbus.readthedocs.io",
      "version": "4.0.1",
      "requirements": [
        "pymodbus>=3.11.1"
      ]
    }
  },
  "integration_manifest": {
    "domain": "solis_cloud_control",
    "name": "Solis Cloud Control Integration",
    "codeowners": [
      "mkuthan"
    ],
    "config_flow": true,
    "documentation": "https://github.com/mkuthan/solis-cloud-control",
    "iot_class": "cloud_polling",
    "issue_tracker": "https://github.com/mkuthan/solis-cloud-control/issues",
    "version": "2.16.0",
    "is_built_in": false,
    "overwrites_built_in": false
  },
  "setup_times": {},
  "data": {
    "inverter_info": {
      "serial_number": "**REDACTED**",
      "model": "3104",
      "version": "4D0051",
      "machine": "S5-EH1P5K-L",
      "energy_storage_control": "21",
      "smart_support": "0",
      "generator_support": "0",
      "collector_model": "WL",
      "power": "5.0",
      "power_unit": "kW",
      "parallel_number": "0.0",
      "parallel_battery": "0",
      "tou_v2_mode": "43605"
    },
    "coordinator_data": {
      "52": "190",
      "54": "190",
      "56": "2026-01-31 20:06:35",
      "636": "33",
      "5916": "1",
      "5946": "04:00-07:55",
      "5948": "75",
      "5928": "100",
      "5917": "0",
      "5949": "00:00-00:00",
      "5951": "50",
      "5929": "50",
      "5918": "0",
      "5952": "00:00-00:00",
      "5954": "50",
      "5930": "50",
      "5919": "0",
      "5955": "00:00-00:00",
      "5957": "50",
      "5931": "50",
      "5920": "0",
      "5958": "00:00-00:00",
      "5960": "50",
      "5932": "50",
      "5921": "0",
      "5961": "00:00-00:00",
      "5963": "50",
      "5933": "50",
      "5922": "0",
      "5964": "00:00-00:00",
      "5967": "50",
      "5965": "50",
      "5923": "0",
      "5968": "00:00-00:00",
      "5971": "50",
      "5969": "50",
      "5924": "0",
      "5972": "00:00-00:00",
      "5975": "50",
      "5973": "50",
      "5925": "0",
      "5976": "00:00-00:00",
      "5979": "50",
      "5977": "50",
      "5926": "0",
      "5980": "00:00-00:00",
      "5983": "50",
      "5981": "50",
      "5927": "0",
      "5987": "00:00-00:00",
      "5986": "50",
      "5984": "50",
      "376": "110",
      "499": "0",
      "6962": "0",
      "157": "80",
      "158": "20",
      "160": "10",
      "7229": "21",
      "7963": "100",
      "7224": "100",
      "7226": "100"
    }
  },
  "issues": []
}

Screenshots

If applicable, add screenshots to help explain the problem.

Possible Solution

Suspect it might be an issue with the CID code being sent for my particular model?

[mkuthan]

Thanks for reporting the issue!

The root cause of the error is "read after write" verification. The integration was trying to change storage mode (cid 636) from 33 (self-use + allow-grid-charging) to 2081 (self-use + allow-grid-charging + peak-shaving) and then read storage mode again to verify the change. For unknown reason the inverter returned 33 instead of 2081.

Could you enable peak shaving mode using official Solis app and check reported value for CID 636 in the home assistant diagnostic information, please?

NOTE: Updated information about inverter time in the activity log is an expected behavior. Every time you change inverter settings the integration refreshes all entities states, including inverter time.

[0000Max0000]

Why is grid peak shaving an on / off button ?
It should be a storage mode to select.

The button seems to be enabled when "self usage mode" is active. Which is strange.
When I change in the cloud app to "peak shaving mode" the button is grayed out.

Just for your information.
When "peak shaving mode" is selected in the cloud app the option "allow charging from grid" is off. That option is only visible in you integration.
But when you have a non hybrid inverter this option should be enabled. Because otherwise you cannot charge your battery. There is no solar input when you have a non hybrid inverter.

So in my opinion you should make a "peak shaving mode" with the "charge from grid" on and a "peak shaving mode" with the "charge from grid" off.

And it would be even better when the option "max usable grid power" is visible when the mode is activated. Because this is another option in the "peak shaving mode" which is not visible in your integration.

[mkuthan]

@0000Max0000 you are totally right, peak shaving should be the 4th storage mode instead of a switch. I was misled by UI controls presented for my inverter. As you can see Grid Peak Shaving is a switch, while Storage Mode has 3 options only: self-use, selling-first and off-grid.

Although, I would keep "allow charging from grid" as a separate switch. I optimistically assume that it will allow to change the setting regardless of selected storage mode.

I will be also glad to add "max usable grid power", just let me know CID behind it by inspecting web browser traffic from Solis web app :) I could only guess that "max usable grid power" is the equivalent of "Grid Peak Shaving" numeric field presented in my inverter.

BTW. I'm going to hold off on releasing the new version until Solis fixes its service #112. But the change is ready #113.

[garganm]

Thanks for reporting the issue!

The root cause of the error is "read after write" verification. The integration was trying to change storage mode (cid 636) from 33 (self-use + allow-grid-charging) to 2081 (self-use + allow-grid-charging + peak-shaving) and then read storage mode again to verify the change. For unknown reason the inverter returned 33 instead of 2081.

Could you enable peak shaving mode using official Solis app and check reported value for CID 636 in the home assistant diagnostic information, please?

NOTE: Updated information about inverter time in the activity log is an expected behavior. Every time you change inverter settings the integration refreshes all entities states, including inverter time.

I have Grid Peak Shaving enabled in the Solis App now and the diagnostics in home assistant are showing me this:
"636": "33",

If you have any sort of postman collection I can use to try and do a direct read of the value from solis cloud I am happy to do that so I can compare.

Also the value in Home Assistant shows off for grid peak shaving

[garganm]

@0000Max0000 you are totally right, peak shaving should be the 4th storage mode instead of a switch. I was misled by UI controls presented for my inverter. As you can see Grid Peak Shaving is a switch, while Storage Mode has 3 options only: self-use, selling-first and off-grid.

Although, I would keep "allow charging from grid" as a separate switch. I optimistically assume that it will allow to change the setting regardless of selected storage mode.

I will be also glad to add "max usable grid power", just let me know CID behind it by inspecting web browser traffic from Solis web app :) I could only guess that "max usable grid power" is the equivalent of "Grid Peak Shaving" numeric field presented in my inverter.

BTW. I'm going to hold off on releasing the new version until Solis fixes its service #112. But the change is ready #113.

If it helps the last two setting here on my android app for solis cloud are what I use to enable the grid peak shaving and to set the wats allowed (the app says the value needs to be multiples of 100)

[mkuthan]

Peak shaving mode is not so easy, look at this discussion for modbus control: Pho3niX90/solis_modbus#82

Could you check this version, please?
https://github.com/mkuthan/solis-cloud-control/releases/tag/v2.18.0-alpha.1

Peak shaving is exposed as 4th storage mode.

[garganm]

Still having the same issue when I try to enable with the alpha release

I managed to get a postman call setup so I can call the 636 cid in postman as I make changes in the app and I can see it correctly change as per the documentation from Solis when I adjust settings like enabling or disabling grid charging but changes to the Grid Peak Shaving setting in the app do not affect the 636 cid at all

I have opened a support ticket with Solis to see if they can provide some more insight into what the correct API call to view or change that setting might be and will let you know how I get on (assuming I get anywhere with that!)

[garganm]

OK - I have discovered through support tickets and my own digging that the cids for Grid Peak shaving (at least for my inverter) are 9021 to enable or disable (1 and 0 as the values) and to set the peak wats it is 9022.

If I set the value of cid 9022 to anything less than a 100 increment for the Watts it rounds down so if you set 95 it rounds down to 0 for example.

I have no idea how this compares to other inverters or if it is something that could be implemented but wanted to let you know what I had found

[mkuthan]

For my inverter S6-EH3P12K02-NV-YD-L, the Solis web app uses CID 6969 to toggle the peak shaving switch and CID 6970 to set the peak watts.

The current implementation follows the official specification for available CIDs: https://oss.soliscloud.com/doc/SolisCloud_control_api_command_list.xlsx.

As you can see, there are no CIDs 6969, 6970, 9021, or 9022 listed in the specification. The only documented way to enable peak shaving mode is CID 636, bit 11. I suspect this is a remnant of earlier versions, since I haven’t received any feedback that it works for anyone.

[garganm]

Ahhh lovely.. OK I guess for now I will look at using a rest call from home assistant to make the changes when needed..

[0000Max0000]

And what is a rest call ? Sorry it's new for me.

[garganm]

Setting up a restful command that I can use in an action to enable or disable things through the API:

https://www.home-assistant.io/integrations/rest_command/