You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider a IoT heater. Setting it to 100ºF or 100ºC will cause very different results and possibly life-threatening accidents.
So when dealing with temperature, we'll need to know which unit is expected by the device and which unit is entered through the UX, then perform conversions as needed.
I'm not sure at which layer we need to do this.
The text was updated successfully, but these errors were encountered:
This seems like it would be handled taxonomically when each adapter/device-type specifies its interface. This issue is too broad to be actionable, can we close it and track the requirement elsewhere if necessary?
Consider a IoT heater. Setting it to 100ºF or 100ºC will cause very different results and possibly life-threatening accidents.
So when dealing with temperature, we'll need to know which unit is expected by the device and which unit is entered through the UX, then perform conversions as needed.
I'm not sure at which layer we need to do this.
The text was updated successfully, but these errors were encountered: