Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m frustrated

Relative temperature incorrect for demand response api

Hi,

We are testing the api to submit Demand responses and when we submit a demand response that sets a relative temperature, the value we set is not being use. For example, if I make the following call

{
"selection": {
"selectionType":"thermostats",
"selectionMatch":"xxx"
},
"operation":"create",
"demandResponse":{
"name":"Test",
"message":"This is a DR!",
"sendEmail":false,
"showIdt":true,
"event": {
"endTime":"15:45:00",
"endDate":"2016-08-25",
"name":"apiDR",
"type":"demandResponse",
"coolRelativeTemp":5,
"heatRelativeTemp":5,
"startDate":"2016-08-25",
"startTime":"15:25:00",
"isTemperatureRelative":true,
"isOptional":true,
"dutyCyclePercentage" : 100
}
}
}

In the portal it shows 'Relative Temp:: C: 1° / H:1°' and when the event actually kicks off it will only raise the temperature by 1 degree. We had submitted other tests, no matter what we change the coolRelativeTemp value to, it ends up doing making no change to the termostat or it ups it by 1 degree. It really seemed random on what it would actually do.

However, if we schedule everything with the portal it works fine but is not ideal for our situation.

Is there an issue with our api call or is this a bug in the system?
1 person has
this problem
+1
Reply