* Use EntityFeature enum in vallox
* Use EntityFeature enum in velbus
* Use EntityFeature enum in velux
* Use EntityFeature enum in venstar
* Use EntityFeature enum in vera
* Use EntityFeature enum in verisure
* Use EntityFeature enum in vesync
* Use EntityFeature enum in vicare
* Use EntityFeature enum in vivotek
* Use EntityFeature enum in vizio
* Use EntityFeature enum in vlc
* Use EntityFeature enum in vlc_telnet
* Use EntityFeature enum in volumio
* 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.
* Vallox: Increase robustness on startup
Experiments showed that timing of websocket requests to the Vallox firmware is
critical when fetching new metrics. Tests on different Raspberry Pis and x86
machines showed that those machines with little processing power tend to fail
the timing requirments during the busy startup phase of Home Assistant,
resulting in the Vallox integration failing to set itself up.
This patch catches Websocket's InvalidMessage, which is a symptom of failing the
timing requirements. Experiments again showed that on the Raspberry's, this
exception is catched once at startup, but the integration is running fine
afterwards.
* Update __init__.py
* Bump to new 2.1.0 version of api.
* Bump to api 2.2.0
