Would be nice to have ability to reload ALERTs YAML configuration.
At moment see no such a link under ‘YAML configuration reloading’.
rct
July 19, 2021, 3:12pm
2
I agree it would be nice if there was a reload option for the Home Assistant Alerts integration similar to the other YAML based configurations.
It would also be nice if alerts could be configured through the UI , (separate feature request thread).
I find it somewhat surprising that the Alerts integration isn’t more popular. The analytics say it is only currently used by 1.4% of home assistant users (a little over 800 installations at the time of writing).
Maybe I’m missing something obvious. I know the alert integration isn’t very flexible in terms of conditions, but they are nice and easy to get pretty good alerting functionality for important events with reminders, acknowledgements, etc.
How can this in July 2021 still not be possible…
This would increase the usage of this great integration massivley - at least for me speaking.
123
(Taras)
July 20, 2021, 12:24am
4
There are some requests (with far more votes than this one) that were made over a year ago (and longer) that have not been implemented. On rare occasions, a new request, with few votes, gets fulfilled relatively quickly. It all depends on the interest and availability of volunteers.
2 Likes
karwosts
(karwosts)
April 25, 2023, 11:49pm
5
Filed a pull request for a reload service; will see what the devs think:
home-assistant:dev
← karwosts:alert-reload
opened 11:48PM - 25 Apr 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
Add a reload service for Alert integration. Allows alert changes in YAML to be quickly reloaded instead of requiring a full HA restart.
As I write more complex notifications for my alerts, having to restart HA each time to test the new yaml is painful, this would make it much more user friendly.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue: https://community.home-assistant.io/t/alert-ability-to-reload-yaml-config/303996
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] 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`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
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+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[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
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
RezzZ
(ReneS)
September 6, 2024, 2:29pm
6
is it true that we still can’t reload alerts? it seems I need to completely restart in order to see any changes…
karwosts
(karwosts)
September 6, 2024, 4:39pm
7
Multiple core developers have commented that alert integration is basically considered a dead-end and is destined to be replaced with something like blueprints.
No new features for alert
are being accepted at this time.
e-raser
October 13, 2024, 11:18am
8
Yeah so where is the 1:1 blueprint replacement then dear core developers?