I think it is neither related to the App (since I don’t use it) nor is it related to GET vs. POST. In my case I have the same page open in the browser. And I am clicking on the same UP button on a setpoint control. Sometimes it fails, and then later I can make it succeed. In both cases the browser sends an HTTP POST request, which you can see below are the respective WireShark traces of the two cases.
1. First Attempt: Push SetPoint Up Button (failure)
POST /rest/items/Front_Bedroom_Radiator_Target_Temperature HTTP/1.1
<headers>
Content-Length: 9
17 %unit%
HTTP/1.1 400 Bad Request
2. Second Attempt: Push SetPoint Up Button (success)
POST /rest/items/Front_Bedroom_Radiator_Target_Temperature HTTP/1.1
<headers>
Content-Length: 6
17 °C
HTTP/1.1 200 OK
So the issue is definitely and solely due to the ‘17 °C’ vs. the ‘17 %unit%’.
And so the question is: Why is the exact same button in the exact same browser page first sending a faulty request, and then sending a good one? Please look at the following sequence of screen shots…
- First load of the sitemap page | Press UP button | Fails!
- Move presence switch OFF (setpoint visibility is linked to this)
- Page reloads (setpoint not visible) | Move presence switch ON
- Page reloads | Press UP button | Succeeds!
FACIT: the page reload causes the same UP button in the same web page to go from failing to succeeding…