Closed benfrancis closed 6 years ago
Really appreciate this. I’m currently running Qubino, Secure, Horstmann and virtual thermostats so I’m happy to test.
What would you need for this? I'd like to get my Nest connected.
With the upcoming 0.5 release, we're switching from a system of static web thing types to a capability-based system, as it's much more flexible. That being the case, there are 2 paths forward. If possible, it would be great to pursue both at the same time.
TemperatureProperty
, HumidityProperty
, HVACModeProperty
, and maybe some additional properties for target temperatures, etc., and then a ThermostatCapability
. Our current schema repository can be found here, with an easier to read version here.number
property will be given a generic number input. For instance, we don't yet have any relevant types defined for a weather station, but @freaktechnik built an awesome add-on for Netatmo weather stations.On the topic of nest, someone seems to be trying to get at least some nest devices connected: https://discourse.mozilla.org/t/nest-oauth-flow/29913
I am strongly in favour of adding additional properties for target values. Separating actual values from target values ensures a trust in the actual values to become inputs for rules. If the Web Thing would immediately reply with a target temperature, it might trigger unexpected actions in a gateway or be less valuable as an input because of this missing separation.
Closed in favor of mozilla-iot/schemas#13
We should define a web thing type for thermostats