Skip to content

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

Open
HeatingFromHell opened this issue Nov 21, 2024 · 6 comments
Open

API Change in PUT RoomClimateControl/state? #116

HeatingFromHell opened this issue Nov 21, 2024 · 6 comments

Comments

@HeatingFromHell
Copy link

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

  • setpointTemperatureForLevelComfort
  • setpointTemperatureForLevelEco
  • schedule
  1. I can't find a changelog for these things, is there any?
  2. Is it possible to change these 3 settings otherwise by API?

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": []
}
]
}
}

@sebastianharder
Copy link
Contributor

sebastianharder commented Nov 21, 2024

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.

@HeatingFromHell
Copy link
Author

Hi Sebastian,
thank you.

I really miss an API changelog.

If an update break things, it is hard to debug...
So I would like to check for API changes before updating.

@HeatingFromHell
Copy link
Author

Hi Sebastian,
have you found the time to document the new API calls, maybe I missed them?
Or a sample (as replacement of the old call above) of how to set and delete values as an answer here?
Thanks

@HeatingFromHell
Copy link
Author

If it is now controlled by activeScheduleId - where is this schedule defined or managed?

@saithis
Copy link

saithis commented Dec 25, 2024

@sebastianharder I would also be interested in an updated documentation.

@HeatingFromHell
Copy link
Author

Hi, any Updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants