* Automatic fill of supported fan speed and hvac
Automatic fill of supported fan speed and hvac
* Update manifest of spiderpy to 1.5.0
Update manifest of spiderpy to 1.5.0
* Update spiderpy version to 1.5.0 in requirements files
* Code formatted using Black
* Move support fan and hvac values into a class variable
* Move convert to HA value to hvac_modes method
* Log a warning for any invalid operation mode
* Update homeassistant/components/spider/climate.py
Update as suggested by @mivn23
Co-authored-by: mvn23 <schopdiedwaas@gmail.com>
* PR feedback update + dependency update
* Remove logging
Co-authored-by: Bennert <info@bennert.nl>
Co-authored-by: mvn23 <schopdiedwaas@gmail.com>
* Migrate SimpliSafe to new web-based authentication
* Ensure we're storing data correctly
* Re-add support for realtime websocket in SimpliSafe
* Updates
* Better lock state from websocket
* Unknown states
* Streamline
* Unnecessary assertion
* Remove conditions we can't reach
* Require multiple error states from REST API before reacting
* Only disconnect when needed
* Typing
* Code review
* Update PyVicare to 2.x
With PyViCare 2.8.1 a breaking change was introduced which required changes on sensor and binary_sensor platforms:
- Circuit, Burner and Compressor have been separated out from the "main" device
- Multiple circuits and burners allow "duplicate sensors". We add the circuit or burner number as suffix now
At the same time the sensors are now created only when available:
During entity creation we can check if the value is provided for the user's device.
Sensors are not created by heating type anymore but instead the new API structure is reflected, providing device, burner or circuit sensors.
For details of breaking changes from PyViCare 1.x to 2.x please see https://github.com/somm15/PyViCare#breaking-changes-in-version-2x
* Integrate review comments
* variables cleanup
* Update unique ids
The unique ids shall not depend on the name but on the entity
description key (which should not change) and the id of the circuit,
burner or device.
Yandex recently switched to the new captcha page and the new version of aiomaps supports it.
The check for captcha is moved to platform setup.
Fixes#56035
