Is it possible to get the current temperature type (Sleep, Away, Comfort, etc.) when weekly program is activated?
It seems that the only way to get this currently is by using the GET /weekly-program and find which timer is currently active, based on the current timestamp. Is that correct? If so, this increases the complexity on the client side, specially because we would need to poll on two endpoints (/control-status and /weekly-program) to continuously retrieve the current state of the heater.
I would expect this information exposed as a pre-calculated field in the response of GET /control-status, since the response already expose a summary of the current control status such as target temperature, operation mode, etc.
Is it possible to get the current temperature type (Sleep, Away, Comfort, etc.) when weekly program is activated?
It seems that the only way to get this currently is by using the
GET /weekly-programand find which timer is currently active, based on the current timestamp. Is that correct? If so, this increases the complexity on the client side, specially because we would need to poll on two endpoints (/control-statusand/weekly-program) to continuously retrieve the current state of the heater.I would expect this information exposed as a pre-calculated field in the response of
GET /control-status, since the response already expose a summary of the current control status such as target temperature, operation mode, etc.