forum

Currently a 'set' to something like commandClasses.ThermostatSetPoint.Set(12,20) using 'GET' or 'POST' returns a 200 OK with the string "null
" as the body/payload.

It would be nice to have something a bit more meaningful and look at the GET/POST semantics.

Secondly - in most cases such sets will be accepted; but not yet effectuated/acted upon - as the device to be configured/changed is still sleeping. So it may be many seconds/minutes before you actually can ascertain if the 'set' was successful.

So it may be nice to get the GET/POST semantics right - as it is a *request* for a change - and distinguish between the type of replies/actual state changes.

These calls are JavaScript calls, so they return the result returned by those functions. Some functions have other result than null.

Also our system is asyncronous, we can not keep the request open while it is not executed yet, since most requests for sleeping devices are never executed in real time. We have a way to notify you once the request was handled, so use this API.