🏡 Open source home automation that puts local control and privacy first.
6fbdcac323
* Check if changing TO a color mode Changing brightness alone does not change work mode, but changing brightness with a color value will keep the light in white mode. By verifying the new state has color or not, rather than the existing state being in color work mode, the light will change to color correctly. Tuya interprets HSV as including the brightness in the (v) value (which is generally what that's used for when setting HSV values). The brightness value given by Home Assistant is still used in this case. * Fix brightness-only turning colour mode to white This will take into account the case where brightness is the only parameter for both the case of colour mode and white mode. Tests passed after this change: * Brightness only (colour mode) ✅ * Brightness only (white mode) ✅ * Colour only (colour mode) ✅ * Colour only (white mode) ✅ * Colour temp only (colour mode) ✅ * Colour temp only (white mode) ✅ * Colour + brightness (colour mode) ✅ * Colour + brightness (white mode) ✅ * Colour temp + brightness (colour mode) ✅ * Colour temp + brightness (white mode) ✅ * Fix code formatting |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| .vscode | ||
| docs | ||
| homeassistant | ||
| machine | ||
| pylint/plugins | ||
| rootfs | ||
| script | ||
| tests | ||
| .core_files.yaml | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .hadolint.yaml | ||
| .pre-commit-config.yaml | ||
| .prettierignore | ||
| .readthedocs.yml | ||
| .strict-typing | ||
| .yamllint | ||
| build.yaml | ||
| CLA.md | ||
| CODE_OF_CONDUCT.md | ||
| codecov.yml | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| Dockerfile.dev | ||
| LICENSE.md | ||
| MANIFEST.in | ||
| mypy.ini | ||
| pyproject.toml | ||
| README.rst | ||
| requirements.txt | ||
| requirements_all.txt | ||
| requirements_docs.txt | ||
| requirements_test.txt | ||
| requirements_test_all.txt | ||
| requirements_test_pre_commit.txt | ||
| setup.cfg | ||
Home Assistant |Chat Status| ================================================================================= Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Check out `home-assistant.io <https://home-assistant.io>`__ for `a demo <https://demo.home-assistant.io>`__, `installation instructions <https://home-assistant.io/getting-started/>`__, `tutorials <https://home-assistant.io/getting-started/automation/>`__ and `documentation <https://home-assistant.io/docs/>`__. |screenshot-states| Featured integrations --------------------- |screenshot-integrations| The system is built using a modular approach so support for other devices or actions can be implemented easily. See also the `section on architecture <https://developers.home-assistant.io/docs/architecture_index/>`__ and the `section on creating your own components <https://developers.home-assistant.io/docs/creating_component_index/>`__. If you run into issues while using Home Assistant or during development of a component, check the `Home Assistant help section <https://home-assistant.io/help/>`__ of our website for further help and information. .. |Chat Status| image:: https://img.shields.io/discord/330944238910963714.svg :target: https://discord.gg/c5DvZ4e .. |screenshot-states| image:: https://raw.githubusercontent.com/home-assistant/core/master/docs/screenshots.png :target: https://demo.home-assistant.io .. |screenshot-integrations| image:: https://raw.githubusercontent.com/home-assistant/core/dev/docs/screenshot-integrations.png :target: https://home-assistant.io/integrations/