* Initial commit
* Support changed API
Change sensor entity descriptions
* Fix sensor not handling coordinator update
* Implement re-authentication flow and handle token expiry
* Bump aioaquacell
* Bump aioaquacell
* Cleanup and initial tests
* Fixes for config flow tests
* Cleanup
* Fixes
* Formatted
* Use config entry runtime
Use icon translations
Removed reauth
Removed last updated sensor
Changed lid in place to binary sensor
Cleanup
* Remove reauth strings
* Removed binary_sensor platform
Fixed sensors not updating properly
* Remove reauth tests
Bump aioaquacell
* Moved softener property to entity class
Inlined validate_input method
Renaming of entities
Do a single async_add_entities call to add all entities
Reduced code in try blocks
* Made tests parameterized and use test fixture for api
Cleaned up unused code
Removed traces of reauth
* Add check if refresh token is expired
Add tests
* Add missing unique_id to config entry mock
Inlined _update_config_entry_refresh_token method
Fix incorrect test method name and comment
* Add snapshot test
Changed WiFi level to WiFi strength
* Bump aioaquacell to 0.1.7
* Move test_coordinator tests to test_init
Add test for duplicate config entry
* Check if message_text has a value instead of checking if its not None
* Strip message_text to ensure that its actually empty or not
* Add test with multipart payload having empty plain text
Avoid addtional timestamp conversion to set state
Since we already have the timestamp, we can pass it on to the State
object and avoid the additional timestamp conversion which can be as
much as 30% of the state write runtime.
Since datetime objects are limited to microsecond precision, we need
to adjust some tests to account for the additional precision that we
will now be able to get in the database
* Always do thread safety check when writing state
Refactor the 3 most common places where the thread safety check
for the event loop to be inline to make the check fast enough
that we can keep it long term. While code review catches most
of the thread safety issues in core, some of them still make
it through, and new ones keep getting added. Its not possible
to catch them all with manual code review, so its worth the
tiny overhead to check each time.
Previously the check was limited to custom components
because they were the most common source of thread
safety issues.
* Always do thread safety check when writing state
Refactor the 3 most common places where the thread safety check
for the event loop to be inline to make the check fast enough
that we can keep it long term. While code review catches most
of the thread safety issues in core, some of them still make
it through, and new ones keep getting added. Its not possible
to catch them all with manual code review, so its worth the
tiny overhead to check each time.
Previously the check was limited to custom components
because they were the most common source of thread
safety issues.
* async_fire is more common than expected with ccs
* fix mock
* fix hass mocking
Joakim Plate
Rami Mosleh
Matthias Alphart
Jordi
Robert Svensson
Michael Hansen
Gedaliah Knizhnik
Steven B
Mr. Bubbles
David Bonnes
J. Nick Koston
Marc Mueller
epenet
David Knowles
Maciej Bieniek
G Johansson
Åke Strandberg
Sebastian Lövdahl
Sid
Regin Larsen
Ernst Klamer