-
Notifications
You must be signed in to change notification settings - Fork 44
API Change in PUT RoomClimateControl/state? #116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @HeatingFromHell, I cannot provide you the whole details at the moment, but after the new schedule UI was implemented, there are no "ECO" or "COMFORT" temperatures anymore, because the schedule allows more than two temperatures now. I hope to find the time, to update the documentation in the near future. |
Hi Sebastian, I really miss an API changelog. If an update break things, it is hard to debug... |
Hi Sebastian, |
If it is now controlled by activeScheduleId - where is this schedule defined or managed? |
@sebastianharder I would also be interested in an updated documentation. |
Hi, any Updates? |
Hi,
something must have changed in the API since last year for
/devices/roomClimateControl_hz_xx/services/RoomClimateControl/state
I'm now on API Version 3.14 and it is not possible anymore to set
e.g.
URL: /devices/roomClimateControl_hz_xx/services/RoomClimateControl/state
WORKING
{"@type":"climateControlState","setpointTemperature":22}
NOT WORKING (HTTP Status Code: 500)
{"@type":"climateControlState","setpointTemperatureForLevelComfort":24}
NOT WORKING (HTTP Status Code: 500)
{
"@type": "climateControlState",
"schedule": {
"profiles": [
{
"day": "MONDAY",
"switchPoints": []
},
{
"day": "TUESDAY",
"switchPoints": []
},
{
"day": "WEDNESDAY",
"switchPoints": []
},
{
"day": "THURSDAY",
"switchPoints": [
{
"startTimeMinutes": 0,
"value": {
"@type": "temperatureLevelSwitchPointValue",
"temperatureLevel": "ECO"
}
},
{
"startTimeMinutes": 360,
"value": {
"@type": "temperatureLevelSwitchPointValue",
"temperatureLevel": "COMFORT"
}
},
{
"startTimeMinutes": 1080,
"value": {
"@type": "temperatureLevelSwitchPointValue",
"temperatureLevel": "ECO"
}
}
]
},
{
"day": "FRIDAY",
"switchPoints": []
},
{
"day": "SATURDAY",
"switchPoints": []
},
{
"day": "SUNDAY",
"switchPoints": []
}
]
}
}
The text was updated successfully, but these errors were encountered: