Replies: 5 comments 1 reply
-
@balloob suggested that the way to implement this is not in the iOS app but in This is low priority for me though. |
Beta Was this translation helpful? Give feedback.
-
Not sure I see why the client app would need to pass anything. Since |
Beta Was this translation helpful? Give feedback.
-
We (iOS app) needs to provide relevant units, not just the system. e.g. you want distance in feet, not inches, but HA isn’t smart enough to know that |
Beta Was this translation helpful? Give feedback.
-
Even if HA can sort the conversion, the app should (must) provide units otherwise there is an assumption and the whole thing will fall over in the morning. Personally I think the whole units could be looked at better. At the moment units are simply strings which is open to confusion. Personally I would favour implementing a simplified version of astroPy. That then could properly exploit unit preferences in HA |
Beta Was this translation helpful? Give feedback.
-
I find this annoying, as well. It would be nice to have a configuration on the sensor in HA for m/ft. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Both sensor.distance and sensor.average_active_pace return their data in meters. It'd be great if these respected the HA config value for imperial/metric.
Beta Was this translation helpful? Give feedback.
All reactions