From a286d4f38bc847bfbf50905b72279509957f2c5f Mon Sep 17 00:00:00 2001 From: Jason Rumney Date: Tue, 14 Jan 2025 22:35:20 +0900 Subject: [PATCH] Improve precision documentation --- custom_components/tuya_local/devices/README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/custom_components/tuya_local/devices/README.md b/custom_components/tuya_local/devices/README.md index 0a51f3be3b..6c9290a005 100644 --- a/custom_components/tuya_local/devices/README.md +++ b/custom_components/tuya_local/devices/README.md @@ -209,14 +209,14 @@ require it. Use this only where needed, and generally only on read-only dps. *Optional, default None.* -For integer dps that are sensor values, the suggested precision for -display in Home Assistant can be specified. If unspecified, the Home -Assistant will use the native precision, which is calculated based on -the scale of the dp so as to provide distinct values with as few -decimal places as possible. For example a scale of 3 will result in -one decimal place by default, (values displayed as x.3, x.7 rather -than x.33333333 and x.666666) but you could override that to 2 or 0 -with by specifying the precision explicitly. +The number of decimals which should be used in the sensor's state when +it's displayed. If unspecified, the Home Assistant will use the native +precision, which is calculated based on the scale of the dp so as to +provide distinct values with as few decimal places as possible. For +example a scale of 3 will result in one decimal place by default, +(values displayed as x.3, x.7 rather than x.33333333 and x.666666) but +you could override that to 2 or 0 by specifying the precision +explicitly. ### `mapping`