Hi, everyone.

It seems to be the same issue that @CyberAustin mentioned.

I’m using the Omada Cloud Controller with the mbentley/omada-controller:5.15.24.19 Docker image:

https://hub.docker.com/layers/mbentley/omada-controller/5.15.24.19

My n8n workflow tries to remove a rate limit for a wireless client and sends the following PATCH request:

{
  "body": {
    "rateLimitId": "",
    "enable": false,
    "upEnable": false,
    "upUnit": 1,
    "upLimit": 0,
    "downEnable": false,
    "downUnit": 1,
    "downLimit": 0
  },
  "headers": {
    "authorization": "**hidden**",
    "accept": "application/json,text/html,application/xhtml+xml,application/xml,text/*;q=0.9, image/*;q=0.8, */*;q=0.7"
  },
  "method": "PATCH",
  "uri": "https://omadacloud.************/openapi/v1/c***********************7/sites/6**********************7/clients/C*-**-**-**-**-*8/ratelimit",
  "gzip": true,
  "rejectUnauthorized": true,
  "followRedirect": true,
  "resolveWithFullResponse": true,
  "followAllRedirects": true,
  "timeout": 300000,
  "encoding": null,
  "json": false,
  "useStream": true
}

The response message is:

{
  "errorCode": -1001,
  "msg": "Parameter [mode] could not be null.\n"
}

I’m following this thread and really looking forward to a solution :)

  @O_Cabeca_BR Join the queue friend. Hopefully @Vincent-TP gets back soon about that bug report.

  @Vincent-TP awesome!

  @Vincent-TP I can confirm that this is fixed now. However, they removed the "enabled" part from the API documentation, and it is still very much a thing. When you set a rate limit now with the API, the overall rate "enabled" box still gets checked, but when you use the "upEnable" and "downEnable" and set both to false, the overall enabled is still checked. I tried add "enable": "false" in a few places and I couldn't seem to affect that check box. I don't think it's actually breaking anything, but maybe something to fix in the next release. JSON below for an example of what I'm talking about.