Increase # runs kept?

123 · June 8, 2021, 11:23pm

I found this but haven’t tried it:

Related Pull Request:

github.com/home-assistant/core

Make number of stored traces configurable

dev ← emontnemery:configurable_stored_traces

opened 09:20PM - 26 Apr 21 UTC

emontnemery

+104 -23

## Proposed change Make the number of traces stored per automation or script …configurable through configuation variables. ## Type of change - [ ] Dependency upgrade - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [x] New feature (which adds functionality to an existing integration) - [ ] Breaking change (fix/feature causing existing functionality to break) - [ ] Code quality improvements to existing code or addition of tests ## Example entry for `configuration.yaml`: ```yaml automation: # Change the light in the kitchen and living room to 150 brightness and color red. trace: # Store 30 traces for this automation stored_traces: 30 trigger: - platform: sun event: sunset action: - service: light.turn_on target: entity_id: - light.kitchen - light.living_room data: brightness: 150 rgb_color: [255, 0, 0] script: trace: # Don't store any trace for this script stored_traces: 0 example_script: sequence: # This is written using the Script Syntax - alias: "Turn on ceiling light" service: light.turn_on target: entity_id: light.ceiling - alias: "Notify that ceiling light is turned on" service: notify.notify data: message: "Turned on the ceiling light!" ``` ## Additional information - This PR fixes or closes issue: fixes # - This PR is related to issue: - Link to documentation pull request: ## Checklist - [ ] The code change is tested and works locally. - [ ] Local tests pass. **Your PR cannot be merged unless tests pass** - [ ] There is no commented out code in this PR. - [ ] I have followed the [development checklist][dev-checklist] - [ ] The code has been formatted using Black (`black --fast homeassistant tests`) - [ ] Tests have been added to verify that the new code works. If user exposed functionality or configuration variables are added/changed: - [ ] Documentation added/updated for [www.home-assistant.io][docs-repository] If the code communicates with devices, web services, or third-party tools: - [ ] The [manifest file][manifest-docs] has all fields filled out correctly. Updated and included derived files by running: `python3 -m script.hassfest`. - [ ] New or updated dependencies have been added to `requirements_all.txt`. Updated by running `python3 -m script.gen_requirements_all`. - [ ] Untested files have been added to `.coveragerc`. The integration reached or maintains the following [Integration Quality Scale][quality-scale]: - [ ] No score or internal - [ ] 🥈 Silver - [ ] 🥇 Gold - [ ] 🏆 Platinum To help with the load of incoming pull requests: - [ ] I have reviewed two other [open pull requests][prs] in this repository. [prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io