Scheduler V1 issue setting ForceCharge / ForceDischarge modes
Posted: Mon Sep 01, 2025 11:04 am
I am attempting to set schedules on my inverters programatically and have hit an issue which seems to be affecting the OpenAPI endpoint, but also appears to be affecting the 2.0 app (Android - dont have an Apple device to check with)
I am able to retrieve the current schedule, and had one slot in ForceDischarge mode.
I was then able to reset the schdule to SelfUse for the whole day.
Upon attempting to set it back to the original schedule returned by the initial API call I get a 44098 Write Failed response.
I tried all the various WorkMode options as presented in properties.workMode.enumList. SelfUse and Feedin work fine, but ForceCharge and ForceDischarge return the same 44098 error.
I tried to set the value back to ForceCharge in the mobile app and got exactly the same 44098 error!
Feels like something broken on the backend - anyone else seeing this or is it just me?
For reference, i am POST querying /op/v1/device/scheduler/get to get the schedule. When I try to set the schedule, I disable the scheduler with a POST to /op/v1/device/scheduler/set/flag, set the schedule wth a POST to /op/v1/device/scheduler/enable, and then re-enable the scheduler
The POST body isI am sending is:
I am able to retrieve the current schedule, and had one slot in ForceDischarge mode.
I was then able to reset the schdule to SelfUse for the whole day.
Upon attempting to set it back to the original schedule returned by the initial API call I get a 44098 Write Failed response.
I tried all the various WorkMode options as presented in properties.workMode.enumList. SelfUse and Feedin work fine, but ForceCharge and ForceDischarge return the same 44098 error.
I tried to set the value back to ForceCharge in the mobile app and got exactly the same 44098 error!
Feels like something broken on the backend - anyone else seeing this or is it just me?
For reference, i am POST querying /op/v1/device/scheduler/get to get the schedule. When I try to set the schedule, I disable the scheduler with a POST to /op/v1/device/scheduler/set/flag, set the schedule wth a POST to /op/v1/device/scheduler/enable, and then re-enable the scheduler
The POST body isI am sending is:
Code: Select all
{
"deviceSN": "xxxxxxxx",
"groups": [
{
"startHour": 0,
"startMinute": 0,
"endHour": 15,
"endMinute": 59,
"enable": 1,
"workMode": "SelfUse",
"fdPwr": 0,
"fdSoc": 10,
"minSocOnGrid": 10,
},
{
"startHour": 16,
"startMinute": 0,
"endHour": 18,
"endMinute": 59,
"enable": 1,
"workMode": "ForceDischarge",
"fdPwr": 3000,
"fdSoc": 50,
"minSocOnGrid": 10,
},
{
"startHour": 19,
"startMinute": 0,
"endHour": 23,
"endMinute": 59,
"enable": 1,
"workMode": "SelfUse",
"fdPwr": 0,
"fdSoc": 10,
"minSocOnGrid": 10,
}
}
