* Add unique id's to Vallox entities
* Cache uuid properties
Requested in code review.
Caching None isn't a problem as the underlying implementation of get_uuid
in the vallox_websocket_api library can never return None.
* Simplify get_uuid type check
Based on review comments.
* Set _attr_unique_id in init
* Import the library get_uuid under a different name
There are a few options here:
1. Rename the get_uuid method with a synonym
2. Import get_uuid under a different name
3. Convert get_uuid into a property
4. Rename get_uuid in the Vallox library
None of these options is that appealing. I'll start with option two,
anyways.
* Add Reauth flow to Wallbox integration
* Review comments processed
* Fixed tests
* Added test for reauth invalid
* Commit to compensate for timedrift, show changes
Compensating for timedrift in my devcontainer,
making a new commit with the right date/time. Requested changes
were done in a previous commit.
* remove reauth schema
* Update homeassistant/components/wallbox/__init__.py
Co-authored-by: J. Nick Koston <nick@koston.org>
Co-authored-by: J. Nick Koston <nick@koston.org>
* Pre-factor nest subscriber to library
Move the nest subscriber to a library that can be reused in a future PR:
- From ConfigFlow for creating subscriptions
- On nest removal to delete subscriptions
This is pulled out of PR #59260 to make that easier to review.
* Resolve pylint error in nest api subscriber
* Remove duplicate constants
* Fix vis and IAD for DS2438
* Fix IAD and vis for DS2438
* Fix IAD and vis for DS2438
* Fix IAD and vis for DS2438
* Fix IAD and vis for DS2438
* Fix IAD and vis for DS2438
* Fix IAD and vis for DS2438
* Fix IAD and vis for DS2438
* Fix IAD and vis for DS2438
* Add a check to verify if there is a passage
Late in the evening and at night, there can be no passages anymore, so check it to avoid an unnecessary exception
* One passage is enough!
Requesting minimum 2 passages was an error due to counting from 1 and not zero
* Invert check and put it out of the try-catch code
Adding also the KeyError in the log message
* Clean up
* Putting comment in the correct python syntax
* Clean up
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>