New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add device condition support to the calendar integration #26997
Comments
I'll take this one for |
Oh ha, I am actually thinking that this one was a mistake. As a calendar doesn't have devices 🙈 I do agree that a calendar should be able to have certain pre-made triggers ready. Hmmmzzzzz, I guess we do have AdGuard representing the service as a device, so we could do the same per calendar. |
@manekenpix I think that it's fine to add this to the calendar integration 👍 Note that we don't have any calendar platforms right now that have devices. |
Ok, I'll work on #26990 then |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Hi, I can take this. |
Add device condition support to the calendar integration.
Device conditions are part of Device Automations, a new concept that was recently launched to make automations more user friendly.
Device automations consist of three different parts: triggers, conditions and conditions. This issue is about the condition part.
To get started with this issue, you will need to set up a Home Assistant development environment. The easiest approach is to get started using a dev container.
Once you have a development environment set up, run the following and follow the instructions:
(This issue is part of #26994)
The text was updated successfully, but these errors were encountered: