Closed Nikey closed 1 year ago
I tested with the development branch and I can set slots sticky with the expected behaviour:
$ curl -d "sticky=true" -X POST http://192.168.YYY.XXX/rest/api/v1/display/slot/2
{
"data": {},
"status": "ok"
}
Which version do you use? Does the problem appears after restart in the first request or after some time?
okay i misunderstood the id param 🤦 i thought i have to use the id from the plugin... Sorry!
Describe the bug POST with sticky=true to /display/slot/{id} always returns
{ "error": { "msg": "Invalid slot id." }, "status": "error" }
even if the ID is correctTo Reproduce POST to /display/slot/{id}
Expected behavior Return code 200 with
{ "data": {}, "status": "ok" }