DAVe3283
2f2f2f7d15
[absolute_humidity] Fix typo ( #10474 )
2025-08-29 10:04:19 +12:00
DAVe3283
06996def72
Use uint8_t instead of uint32_t for 8-bit values on mitsubishi ( #6824 )
...
This solves some printf formatting issues on ESP-IDF and saves RAM on all platforms.
2024-05-28 20:44:47 +00:00
DAVe3283
db6f6f0cb7
Fix compile errors on ESP32-C6 with latest ESP-IDF ( #6822 )
...
* Use <cinttypes> PRI macros to fix ESP32-C6 compile
* Fix compile error on latest ESP-IDF framework & platform
2024-05-28 14:40:34 -05:00
DAVe3283
4c9bcc71cb
Fix logger compile error on ESP32-C6 ( #6323 )
2024-04-04 18:12:27 +13:00
DAVe3283
b637fb3adc
Fix logger compile error on ESP32-C6 ( #6323 )
2024-03-21 12:57:27 +13:00
DAVe3283
f53f91e191
CSE7766 Apparent Power & Power Factor calculations ( #6292 )
2024-02-29 10:12:02 +13:00
DAVe3283
0c7a3d1fff
Revert "Remove state class from uptime sensor ( #4345 )" ( #4557 )
...
This reverts commit 36c2e770bfesphome/issues#4193 .
2023-03-14 14:11:55 +13:00
DAVe3283
a44e38300b
Revert "Remove state class from uptime sensor ( #4345 )" ( #4557 )
...
This reverts commit 36c2e770bfesphome/issues#4193 .
2023-03-14 00:52:19 +00:00
DAVe3283
b29cc58144
Add absolute humidity component ( #4519 )
...
* Import Absolute Humidity component
https://PigLab.ReaperLegion.net/home-automation/hass/esphome/custom-components/absolute-humidity
* Fix terminology, add some docstrings
* Switch from double to float
https://github.com/esphome/esphome/pull/4519#pullrequestreview-1327615169
The additional precision doesn't matter in practice.
* Address code review suggestions
* Lint code
2023-03-07 20:47:25 +00:00
DAVe3283 and Otto Winter
ed26c57d99
Rework NaN handling in sensor filters ( #3610 )
...
Co-authored-by: Otto Winter <otto@otto-winter.com >
2022-07-28 16:39:11 +12:00
DAVe3283
03944e6cd8
Fix bogus reading on no communication with MAX31865 ( #3505 )
2022-06-08 09:58:32 +12:00
DAVe3283
00aaf84c37
Fix uptime's state_class (esphome/issues#2337) ( #2205 )
2021-09-03 16:58:30 +12:00
DAVe3283
36ffef083b
Fix MAX31865 edge case. ( #882 )
...
In a heavy EMI environment, reading the current config from the MAX31865 can
fail, such as switching from a 4-wire sensor to a 3-wire sensor. This causes
the temperature value to be off wildly, but still technically valid, so it
doesn't get reported as a sensor failure.
Since we know what configuration we want, rather than send it to the MAX31865
on setup and ask for it over and over (propagating any error as we write it
back), instead store the base configuration and work from that to change modes.
This not only avoids propagating any error, it also saves a lot of unnecessary
reads from the MAX31865.
2019-11-26 18:31:33 +01:00
DAVe3283