🏡 Open source home automation that puts local control and privacy first.
304b9f47b4
The elkm1-lib autoconfigure set the `configured` flag based on an attribute of the element being changed. This approach misses counters and thermostats. It also does not work well well an "unconfigured" element's default value is different from what is on the panel. This was the case for zones (the `area` attribute was different). The fix in the library is to mark an element as `configured` when the element has a name associated with it. This change is technically breaking, although I imagine, few if any people will be affected as (1) they configure names on all elements (2) the functionality was not working properly, so element would not be missing. The HA docs will be updated to add a section on autoconfigure. It will describe that to have an element automatically configured then the element must be configured on the ElkM1 panel with a name. This particular patch is required for ElkM1 areas. The existing logic assumes that an area is configured if it has an associated keypad. Not all areas have keypads (I have an area only armable with HA). The library fix should catch all configured areas. |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| .vscode | ||
| docs | ||
| homeassistant | ||
| machine | ||
| rootfs | ||
| script | ||
| tests | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .hadolint.yaml | ||
| .ignore | ||
| .pre-commit-config.yaml | ||
| .prettierignore | ||
| .readthedocs.yml | ||
| .travis.yml | ||
| .yamllint | ||
| azure-pipelines-ci.yml | ||
| azure-pipelines-release.yml | ||
| azure-pipelines-translation.yml | ||
| azure-pipelines-wheels.yml | ||
| build.json | ||
| CLA.md | ||
| CODE_OF_CONDUCT.md | ||
| codecov.yml | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| Dockerfile.dev | ||
| LICENSE.md | ||
| MANIFEST.in | ||
| 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 | ||
| setup.py | ||
| tox.ini | ||
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://home-assistant.io/demo/>`__, `installation instructions <https://home-assistant.io/getting-started/>`__, `tutorials <https://home-assistant.io/getting-started/automation-2/>`__ and `documentation <https://home-assistant.io/docs/>`__. |screenshot-states| Featured integrations --------------------- |screenshot-components| 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/en/architecture_index.html>`__ and the `section on creating your own components <https://developers.home-assistant.io/docs/en/creating_component_index.html>`__. 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.github.com/home-assistant/home-assistant/master/docs/screenshots.png :target: https://home-assistant.io/demo/ .. |screenshot-components| image:: https://raw.github.com/home-assistant/home-assistant/dev/docs/screenshot-components.png :target: https://home-assistant.io/integrations/