If there is somehow an Internet Explorer involved on your side (or it could be some Wndows-Library, we do not know for sure), you may receive a status code 1223 (operation aborted) instead of a 204 (No Content).
That is not what we deliver as HTTP-header, this is "fake news" by your backend.
Unfortunately, we cannot do anything on our side to make sure you get the correct HTTP Status-Code, so you have to handle 1223 by yourself.
Make sure to handle 1223 the same as 204, so your solution does still work if this problem is fixed (it seems to be fixed in Internet Explorer 10).
Well, if you can update our language table with languages like chinese or russian, let us know.
Our translators do have access to the systems language table via browser, but we have not yet implemented an alerting system for translation jobs, that are triggered externally. And we have to let them know if there is work to do.
We must also talk about cost if you want to trigger translation jobs in our name. For us, there are still humans involved for translations.
This looks easier than it is. There is technical inheritance involved.
If you move a lamp to another node in the tree, this lamp may inherit an operation mode or other attributes from the actual node or from one above. This means, field communication must occur to update the device(s).
Security is another aspect. If you move one of the root nodes of a tree, there may be thousands of devices affected. We must first identify all possible scenarios.