After update post Limit and Post power not working anymore

[NIKO-AT]

I tried to find out, why posting limit via API does not work after update.

i tried to send a post cmd from windows cmd console:

C:>curl -u "admin:password" http://192.168.xxx.xxx/api/limit/config -d "data={"serial":"xxxxxxxxxxxx", "limit_type":1, "limit_value":20}"
Result:
{"type":"warning","message":"Values are missing!","code":1005}

(instead of xxxxx i typed the real actual values!)

I also tried it with Postman - same result

Authorization is OK, otherwise no result would be sent.

I canot found in any docu which value is missing!

Same, when posting power on / off

thanks for any advise!

[ms49434]

Does
curl -u "admin:password" http://192.168.xxx.xxx/api/limit/config -d 'data={"serial":"xxxxxxxxxxxx", "limit_type":1, "limit_value":20}'
work?
Watch the different quotation marks.

[NIKO-AT]

No, Windows requires ", otherwise the following error occurs:
See:
curl -u "admin:password" http://192.168.xxx.xxx/api/limit/config -d 'data={"serial":"112xxxxxxxxx", "limit_type":1, "limit_value":20}'
curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535
curl: (3) unmatched close brace/bracket in URL position 15:
limit_value:20}'

Unfortunately not the solution.

[ms49434]

https://stackoverflow.com/questions/4514199/how-to-send-double-quote-in-d-parameter-for-curl-exe/15828662#15828662

i.e.
curl -u "admin:password" http://192.168.xxx.xxx/api/limit/config -d "data={[backslash]"serial[backslash]":[backslash]"112xxxxxxxxx[backslash]", [backslash]"limit_type[backslash]":1, [backslash]"limit_value[backslash]":20}"
or
curl -u "admin:password" http://192.168.xxx.xxx/api/limit/config -d "data={"""serial""":"""112xxxxxxxxx""", """limit_type""":1, """limit_value""":20}"
might work with this strange operating system.
It is not an OpenDTU issue.

[NIKO-AT]

for everyone who also uses Windows:
Use PowerShell. Then you can use the single quotes as shown in the examples.
When Content-Type is used, then it have to be: 'Content-Type': 'application/x-www-form-urlencoded'
This is default, so you don't have to set this by using -H parameter.

[NIKO-AT]

Problem with CURL (Windows) solved by using Powershell and it uses the correct default Content-Type.

[NIKO-AT]

Solution for ioBroker. I use following function (JavaScript):

// ioBroker JS function setLimit( AType, ALimit)

//////////////////////////////////////////////////////
const url = 'http://192.168.xxx.xxx/api/limit/config';
const username = 'admin';
const password = 'password';
const serialnr = 'xxxxxxxxxxxx'; 
//////////////////////////////////////////////////////

// TYPES:
// NON_PERSISTENT ///////////////////////
//  AbsolutNonPersistent = 0x0000, //   0
//  RelativNonPersistent = 0x0001, //   1

// PERSISTENT ///////////////////////////
//  AbsolutPersistent    = 0x0100, // 256
//  RelativPersistent    = 0x0101  // 257

// POST-Request configuration
const body = {
  serial:      serialnr,
  limit_type:  AType,  
  limit_value: ALimit,
};

const options = {
  url: url,
  method: 'POST',
  headers: {
    'Content-Type': 'application/x-www-form-urlencoded', 
  },
  body: 'data='+JSON.stringify(body),
  auth: {
    user: username,
    pass: password,
  },
};

// POST-Request
request(options, (error, response, body) => {
  if (error) {
    console.error('post-request error:' + error);
  } else {
    console.log('post-request answer: ' + body);
  }
});