mirror of
https://github.com/esphome/esphome-docs.git
synced 2024-09-30 04:37:44 +02:00
Source for esphome.io documentation files.
21820a7c84
It's probably clear to most people that setting up a trigger for the 31st of every month will fail in February, but apparently triggers between 1am and 3am are also fragile once a year. For non-disruptive or regular triggers, this might not be an issue -- if you want to turn off a device at 2am using on_time, you should know that it will fail once a week. Similarly, if you want to do a daily trigger at 1am, you should know that it will trigger twice a day once a year. This does not seem super-obvious until you've run into it, so I propose adding a note to the documentation. It also doesn't feel like something that should be changed in the functionality to match cron's behavior, given that it would change the functionality of existing triggers. I'm not invested in the exact wording / location; I suspect pulling it out a bit into a more visible place makes it less likely for people to miss. (Brought to you by a trigger that turns off an expensive device at 2am, only for it to run a full day instead :-)). |
||
|---|---|---|
| _static | ||
| _templates | ||
| _themes/esphome | ||
| .devcontainer | ||
| .github | ||
| .vscode | ||
| changelog | ||
| components | ||
| cookbook | ||
| custom | ||
| guides | ||
| images | ||
| projects | ||
| script | ||
| svg2png | ||
| web-api | ||
| _redirects | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .gitpod.yml | ||
| .pre-commit-config.yaml | ||
| CODE_OF_CONDUCT.md | ||
| components.py | ||
| conf.py | ||
| Dockerfile | ||
| Doxygen | ||
| github.py | ||
| index.rst | ||
| LICENSE.md | ||
| lint.py | ||
| Makefile | ||
| markdown.py | ||
| netlify.toml | ||
| pagefind.yml | ||
| README.md | ||
| requirements_test.txt | ||
| requirements.txt | ||
| runtime.txt | ||
| schema_doc.py | ||
| seo.py | ||
| setup.cfg | ||
| sitemap.py | ||
| svg2png.py | ||
ESPHome-Docs 
Documentation: https://esphome.io/
For issues, please go to the issue tracker.
For feature requests, please see feature requests.