Closed Scrumplex closed 4 years ago
Considering the accuracy of the DHT11 is ±2℃.
Having decimal precision for this sensor is pointless.
Considering it would be the spec for the chip I would still recommend implmenting this correctly, especially as ESPHome is reporting the value with 1 decimal accuracy.
[16:56:59][D][sensor:092]: 'temperature': Sending state 23.00000 °C with 1 decimals of accuracy
This is already implemented in the dev version.
https://community.home-assistant.io/t/esphome-and-dht11-sensor-only-displaying-full-degree-changes/134254/14 https://github.com/esphome/esphome/pull/861
I think you can run both versions alongside each other.
I just compiled my config file with the latest :dev docker container and it is working. Closing this as solved with esphome/esphome#861
Operating environment/Installation (Hass.io/Docker/pip/etc.): Docker with following command:
ESP (ESP32/ESP8266, Board/Sonoff): ESP8266, NodeMCU v1.1 (PlatformIO board: nodemcuv2)
Affected component: sensor -> plaform: dht -> model: DHT11
Description of problem: When dumping my MQTT output I only see integer precision float values for the temperature. While I was building my own code for reading the sensor I was able to extract information of up to one decimal precision (like 23.4°C instead of just 23.0°).
Problem-relevant YAML-configuration entries:
I removed unnecessary config sections like wifi or logger
Logs (if applicable):
Additional information and things you've tried: I wrote my own code once to read the data from the sensor and push it directly to an InfluxDB server. It is able to read 1 decimal precision values with Adafruit's DHT sensor library.
https://gitlab.com/Scrumplex/esp8266-dht11-influxdb-collector