Domoticz

Hi there,

I'm trying for a long time to control the room temperature setpoints via dzVents, for example to change the setpoint temperature when a switch is activated. I have an iSense thermostat and an Opentherm Gateway. This works fine for retrieving the OTGW data in Domoticz, and it also works to manually adapt the room temperature setpoint via the 'Utilities' tab in Domoticz. However, when I try to change the setpoint via dzVents, using: It gives me this error in the log:

Error opening url: http://127.0.0.1:8080/json.htm?param=ud ... &svalue=18

I have some experience in dzVents, but very little knowledge about json-commands, so I can use your help here. Some people found a solution in this thread last year: https://domoticz.com/forum/viewtopic.php?f=26&t=34506, but that didn't work for this case.
Who knows what goes wrong in the updateSetPoint command of dzVents? Or: because manually changing the temperature works in the utility tab: how can I actually reveal the commands that Domoticz is using for that route? Maybe I can copy that code to the dzVents script?

Thank you!

To reach the solution from a different angle: where can I find the Domoticz code that controls the Opentherm Gateway devices? I may be able to find back the correct code for updating the temperature setpoint in this Domoticz device code.

That question I can answer: https://github.com/domoticz/domoticz/tr ... t/hardware
There are several OTGW code files so you have to pick yours.

Regarding the link do you have 127.0.0.1 set as a registered security address in menu Setup-Settings (also mentioned on the DzVents documentation here https://www.domoticz.com/wiki/DzVents:_ ... h_Domoticz

Well, your suggestion about the security settings actually solved the problem! I did see that line in the manual, and I already had 127.0.0.* in the list of secure IP's, but apparently it didn't separate it well from the other IP's. There was a semicolon and a space (like 192.168.178.*; 127.0.0.*) and apparently the space is not allowed by Domoticz to catch the second IP. I've changed it to 192.168.178.*;127.0.0.*, and now it works!

Thanks!