Don't try to update CT clamp's state with NaN values returned from the
underlaying sensor. A single IO error in the sensor code will cause a
NaN to be returned and if we use that in CTClampSensor's floating point
maths both sample_sum_ and offset_ will become NaN and from there every
future calculation will use the NaN offset_ and return NaN too.
* Add RFBridge component
* Fix format issues
* Rename methods
* More formatting
* Fix line length
* Apply suggestions from code review
Co-Authored-By: Otto Winter <otto@otto-winter.com>
* Check uart settings on dump
* Make receiving local to the loop
* FIx code order and schema
* Add rf_bridge to test file
* Apply suggestions from code review
Co-Authored-By: Otto Winter <otto@otto-winter.com>
* Handle yaml merge keys correcly.
* Removed old debug bool.
* Deleted after request from @OttoWinder.
* Small refactoring.
Removed unused variable `value`
Small refactoring to make the code clearer.
Added comments.
* Fix merge sequence edge case
* Update ESP32 BLE ADV parse to match BLE spec
* Update xiaomi
* Update ruuvi
* Format
* Update esp32_ble_tracker.cpp
* Fix log
* Format
* Update xiaomi_ble.cpp
* Add support for Sensirion SPS30 Particulate Matter sensors
* Remove blocking of the main thread on initialization;
Improve wording on the debug messages;
Add robustness in re-initialization of reconnected or replaced sensors;
* Fix code formatting;
Co-authored-by: Nad <valordk@github>
* Add QMC5883L and Updated HMC5883L
* add tests
* changed to oversampling
* fix pylint
* fix private method
* typo fix
* fix protected method
* Clean up code and PR recomendations
* fix tests
* remote file
* fix qmc oversampling unit
* Remove hmc5883l config logging
Either the units are converted to the user values like 1x, 8x oversampling or not printed at all. Printing the machine-value of these is only confusing users.
* Changes for validate_enum
Move stuff that can be done beforehand out of the bound function, use text_type for py2/3 compatability.
* Remove unused constant
* Remove duplicate tests
* Repeat remove config print
* remove changes to test2 since bin is to large
* Add comment to HMC5583L
Co-authored-by: Timothy Purchas <timothy@TPF.local>
Co-authored-by: Otto Winter <otto@otto-winter.com>
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.
* added idle
* more clear state description
* Also add drying/fan
Putting it in this PR because it will be put in the same aioesphomeapi release anyway.
* Update bang_bang for idle action
Co-authored-by: root <root@mail.danman.eu>
Co-authored-by: Otto Winter <otto@otto-winter.com>
* Added more data to atm90e32 component
* ignore
* correction
* Delete 6chan_energy_meter.yaml
* PR request changes
* repository test branch
* Update setup.py
* Update const.py
* delete test yaml
* fix chip_temperature_sensor
This was throwing an error if chip_temperature was used. It needed to be changed from temp to temperature.
* default
* Update test1.yaml
* Decode DHT11 decimal part
* Fix comment
* Fix comment
* Handle negative temp for some DHT11 - code from the DHT12 component
* Don't use the fractional part if the checksum is the 2 bytes one
* Fix logger uart conflict check
* Fix class for check func
* Fix syntax
Hope lint is OK with moving the end of the conditional outside the #IFDEF
* Move end of conditional inside ifdef and remove extra whitespace
* Simplify
clang-format did not like the ifdefs and was reformatting in a way that killed clang-tidy.
Simple solution is to use logger's hw_serial as source of truth
Also simplifies the code - uart doesn't need to know what the logger uart settings mean
