mirror of
https://github.com/esphome/esphome.git
synced 2024-11-23 15:38:11 +01:00
My Home-IoT
6f16365b2f
The old gain options were copied from the arduino-MLX90393 library. However, the library actually does the opposite thing from the sensor hardware. Low hardware gain settings are multiplied with large numbers, while high gains are multiplied with small numbers. This is done in order to get consistent readings in µT independent of gain setting. This is confusing from the user's perspective. The user configures the sensor, not the library. Therefore, this PR inverts (actually 5/x) all gain settings. This reflects the analog gain used inside the sensor. Furthermore, the resolution options are named more appropriately. The resolution is always 16 bit, we just choose which 16 bits we get. Additionally, the default values are changed. The old defaults offered high sensitivity, but caused integer overflows in strong magnetic fields. This easily happened when a neodymium magnet was held within a few cm of the sensor. The new default configuration prevents all integer overflows and can deal with strong fields easily. Higher sensitivity must now be explicitly configured by the user. The new documentation informs about integer overflows, mitigating the risk of false readings that existed previously. Finally, this commit exposes the already existing `hallconf` and `temperature_compensation` options. |
||
---|---|---|
.devcontainer | ||
.github | ||
.vscode | ||
docker | ||
esphome | ||
script | ||
tests | ||
.clang-format | ||
.clang-tidy | ||
.coveragerc | ||
.dockerignore | ||
.editorconfig | ||
.flake8 | ||
.gitattributes | ||
.gitignore | ||
.pre-commit-config.yaml | ||
.yamllint | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
LICENSE | ||
MANIFEST.in | ||
platformio.ini | ||
pyproject.toml | ||
README.md | ||
requirements.txt | ||
requirements_dev.txt | ||
requirements_optional.txt | ||
requirements_test.txt | ||
sdkconfig.defaults |
ESPHome
Documentation: https://esphome.io/
For issues, please go to the issue tracker.
For feature requests, please see feature requests.