Wait I think you’re missing how this works. The calendar trigger fires when any event on the calendar starts. You don’t add an event to the calendar and then make an automation for that one event. That would be totally ridiculous, then you might as well just make input datetimes.
The reason this feature is powerful is because what you can do is do something like this:
Make a calendar called “my lights”
Add events for whenever you want the lights to be on
Make one single automation that has a calendar trigger for when an event starts and one for when an event ends in calendar.my_lights
Have it turn on the lights when it starts and off when they end
Now suddenly you’ve got a schedule for your lights. And even better it’s in a GUI that is user friendly enough for anyone in the house to change it.
Or if you want a task calendar that notifies someone 15 min before the task starts. Just make one single automation with a calendar trigger for that calendar that sends a notification when an event starts, like the one I showed right here. Then tell anyone in your house to add chores as necessary to the calendar and your automation sends notifications for them (no automation changes required). Or broadcasts them on Google home. Or changes a tablet to show the current task. Whatever you want.
Does that make the value clearer? Each event in the calendar is just that, an item in the schedule. You automate the calendar itself (the schedule).
From the breaking changes of the release notes for Mqtt
YAML configuration of MQTT entities under the platform key (e.g., light), which was deprecated in Home Assistant Core 2022.6, is no longer supported. The configuration must instead be done under the mqtt key.
The legacy MQTT device tracker is no longer supported. See the documentation for the supported MQTT device tracker configuration.
As of this release, you should now use the modern configuration schema for all manually configured MQTT entities. Please note that this does not impact MQTT discovery, for example, Zigbee2MQTT.
Have you been ignoring the repair telling you that you are using deprecated syntax for your Mqtt configuration? If so you can’t if ignore it anymore, we’ve reached the deprecation end date. You must migrate the config.
Thank you for the explanation. It makes sense. I’ll start experimenting with it (implementing garbage day alerts). It’s a very good first iteration.
For the future, i wish that there would be developed a second approach on top of it:
-instead of creating a new calendar for every kind of (recurring) event
-also having the option to utilize different kind of recurring events within a single calendar as separate triggers for automations.
The beauty of this hybrid approach would be the following:
-for the more “technical” schedules, it is very handy to have them in separate agendas, to prevent any clutter for the end-user.
-for the more “functional” schedules, it is very handy to have recurring events in a single agenda overview for human visualisation. Example: i would love to see paper-collection day, the chemical-collection day, generic garbage collection day in a single agenda overview. But for each of these recurring events, i would like to create different triggers (e.g. notification to mobile “chemical garbage collection today”).
This is not meant as criticism, i love this first iteration. Perhaps something for the future?
I also like the other suggestion proposed somewhere in this topic: it would be nice if a shortcut-button could be created from within the agenda event to “automations”, thereby opening a new automation window, having the event-trigger already filled in. A beautiful ‘nice to have’ feature to streamline the experience even more.
No no, I understand how it works. I just think that it is overkill to have a calendar integration to create a date and name entry. Might as well have been a helper.
And if you want the dedicated integration, then add the automation interface to it.
Thanks for this great release. This is the first time in a while that everything I use works right first time with my OS of choice and without anything to patch. Continue this way.
only issue left here is the grey not_home color, we can not adjust. the badge-person-not-home-color doesnt apply obviously, so please remember the request for the addition of state-person-not-home-color var:
Question on the new local calendar:
Can the entries be created using yaml?
It is not mentioned in the docs. I won’t be using it via the dashboard but it would be a useful helper/input_helper. But only if it can be defined via yaml as yaml is much faster than the UI currently is.
Basically instead of an input_text use input_calendar with name, date and frequency.
the colors might be valid for the badges on the tile card
though it is confusing to see the Library heater show the color of the bigger icon to be heating while in fact it is not. Maybe thats an integration thing, it does after all state ‘Verwarmen’ as Programmed, but that is not the actual state…
HA core thermostat card does not use the state color vars? That would be an issue probably.
I completely agree with you. At first, “local calendar” made me think of a standalone home assistant calendar, where you could add,edit,delete events. And, even more, use that calendar outside of HA.
Now, I created a local calendar. and then… nothing. Finally, I found it in when accessing the “calendar” menuitem at the left side of the page. I was added as one of the “calendars” in the “calender view”.
Create, edit? Nothing. Just delete the calendar event.
So, it’s actually a helper. But, even most helpers can be edited.
For now, I use google calendar. This way, I can add events as i like. Start automations based on events of that google calendar. It’s more capable than “local calendar”. At the moment, “local calendar” adds nothing to HA. Hopefully, it’s just a start, and many more options become available. But, like it is now, I see no reason to use it.
as a result for me was that zha - zigbee could not be loaded. then I reinstalled 2022.11.5 and I got this
WARNING: Error parsing requirements for async-upnp-client: [Errno 2] No such file or directory: '/srv/homeassistant/lib/python3.9/site-packages/async_upnp_client-0.32.2.dist-info/METADATA'
Installing collected packages: aiohttp, httpx, home-assistant-bluetooth, homeassistant
Attempting uninstall: aiohttp
Found existing installation: aiohttp 3.8.3
Uninstalling aiohttp-3.8.3:
Successfully uninstalled aiohttp-3.8.3
Attempting uninstall: httpx
Found existing installation: httpx 0.23.1
Uninstalling httpx-0.23.1:
Successfully uninstalled httpx-0.23.1
Attempting uninstall: home-assistant-bluetooth
Found existing installation: home-assistant-bluetooth 1.8.1
Uninstalling home-assistant-bluetooth-1.8.1:
Successfully uninstalled home-assistant-bluetooth-1.8.1
Attempting uninstall: homeassistant
Found existing installation: homeassistant 2022.12.1
Uninstalling homeassistant-2022.12.1:
Successfully uninstalled homeassistant-2022.12.1
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
music-assistant 1.8.7 requires pillow<=9.2.0,>=8.0, but you have pillow 9.3.0 which is incompatible.
aiogithubapi 22.3.1 requires backoff<2.0.0,>=1.10.0, but you have backoff 2.2.1 which is incompatible.
Successfully installed aiohttp-3.8.1 home-assistant-bluetooth-1.6.0 homeassistant-2022.11.5 httpx-0.23.0
2022-12-09 10:21:41.426 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xA314:1:0x0008]: async_initialize: all attempts have failed: [TimeoutError(), TimeoutError(), TimeoutError(), TimeoutError()]
2022-12-09 10:21:41.508 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xA314:1:0x0300]: async_initialize: all attempts have failed: [TimeoutError(), TimeoutError(), TimeoutError(), TimeoutError()]
2022-12-09 10:21:41.917 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xA314:1:0x0006]: async_initialize: all attempts have failed: [TimeoutError(), TimeoutError(), TimeoutError(), TimeoutError()]
2022-12-09 10:21:42.072 WARNING (MainThread) [homeassistant.components.zha.core.channels.base] [0xDB97:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>'), DeliveryError('Request failed after 5 attempts: <Status.MAC_NO_ACK: 233>')]
so after going back to 2022.11.5 still no zigbee anymore. and back to 2022.11.4 resolved it…
