Input Slider and Equivalent as Custom Temperature Control about haaska HOT 7 OPEN

This is vastly better for absolute values than the current percentage implementation, but a potential problem is that changing the Alexa imperial/metric unit preference can cause unwanted conversion of input and output values.

from haaska.

For those of us on imperial units, alexa provides celsius measurements for all requests and we specify the unit in the response. So I don't see this as an issue.

from haaska.

@keatontaylor the API works exclusively in Celsius, we don't get to choose the unit in the response.
Edit: Oh, looks like they updated the API to report units ("scale") since I did the implementation; don't think we can tell if there will be conversion performed, though.

from haaska.

We could provide a config variable for users to tell us which unit their alexa is set to.

from haaska.

That seems reasonable.

from haaska.

Hmm, I was hoping this could be expanded for numeric sensors too, but it seems that querying state requires saying:
"Alexa, what is the 'device name' temperature"

but this still works well for input_sliders because the interactions will be limited to:

"Alexa, what is the 'input slider name' set to" and "Alexa, set the 'input slider name' to xxx"

I'm surprised that amazon hasn't released a framework for querying sensors, and setting values for devices as the temperature control framework is already so compatible. So it seems that a lot of that code in their backend could likely be reused.

from haaska.

My guess for the sparse API is that they are only releasing features that partners already have skills written for right now.

from haaska.