Domoticz Community Forum - Support & Discussion

i'm using evo home for many years changing setpoint using json calls from a lua script with a black box model to smart heat my rooms.
recently i added a new domoticz server with a newer version of domoticz (Version: 2025.2) and the json call to update the temperature setpoint is different

i used to use
/json.htm?type=setused&idx=<idx>&setpoint=<setpoint>&mode=<mode>&used=true

what has now changed according to the documentation to
/json.htm?type=command&param=udevice&idx=IDX&nvalue=0&svalue=TEMP;SETPOINT

if i add ;PermanentOverride to the string, i do see the device updated in domoticz and data looks oke, but very shortly after it jumps back to the original setpoint

anybody using evo home with a recent domoticz build (Version: 2025.2 or higher) and got this working?

when i use the set temperature from the normal dashboard it does change the temperature setpoint correctly

This has also bewildered me. The thing is, the UI uses the JSON API to communicate with Domoticz under the hood, so in the browser dev tools network tab you'll see that the UI uses the likes of
and
What I find is that this works if I try it from within my local network/LAN, but if use it towards an Apache proxy that's called from an Amazon AWS Lambda function, it does not work. The error message provided by Domoticz is useless to debug. I never looked into it but I have a feeling some kind of http header issue is the problem.

i worked my way this now by making a bash script where i input the IDX and setpoint and what call domoticz with a simple curl to change my thermostat. this works fine for now.

so clear that the issue is in the way Lua in domoticz 2025.2 handles the JSON calls