I created a problem
2 Likes
Since the update last night I have had 2 crashes of HA on my Pi4. This morning I was getting memory alerts prior to the restart, but tonight there were no alerts and it just restarted.
Checked the logs and nothing untoward in there to indicate an issue. Pi4 itself is still stable.
My Pi3 running zigbee has been stable.
Anyone else had random restarts of HA ?
Iām having the same issue since updating HA Core to 2022.12
Iām running HA OS on a VM (Hyper-V) with 4 CPUs and 8GB RAM, and it got stuck twice for me with āno memoryā or related message on the console.
This system has been running for month without any issues until now.
I had to Power Off and back ON the VM about 3 hours ago, and I took the opportunity to increase the Memory to 12GB (not necessary, but buys me some time) and itās already using 4.6GB of memory.
Iāve never seen this before, so Iām assuming something is leaking memory really BAD 
Yes, I agree it does seem to be memory related. The memory history graph matches the times it crashed for me
Will set myself an automation to alert me when it starts to rise up again.
I definitely miss the cleaner look of device colors prior to this update. Consistency in device color doesnāt look quite as good as consistency of colors on a dashboard. Hopefully thereās a way to fix this soon.
2 Likes
Well, then as I was saying, it failed. It did not allow the user to run scheduled automations. It only adds a helper for automations. The calendar UI does not let you make automations. And thatās my criticism. Either allow creating automations from the calendar UI or remove the calendar and stumpy add a helper to the helper section.
It is a cluttering/ bulky implementation of a simple helper. Or: a really poor calendar. I would rather have it be a helper than a feature-poor, ancient calendar integration.
1 Like
Could it be easier? Sure. And Iām sure it will in the future. But the calendar trigger really isnāt that complicated.
- Select
calendarfor trigger - Select your calendar
- Select if you want it to trigger when an event starts or ends
- (Optional) provide an offset
It also seems like your main problem is with the dashboard? Basically that it says calendar in the sidebar
- As I said earlier, thatās unrelated to local calendar. It was added quite a while ago. Appears as soon as you have integrated any calendar, local or otherwise
- If you donāt like it, just hide it from the sidebar
4 Likes
No.
Go to a dedicated dashboard, use the calendar interface to create a simple entry, go to settings, automations and use that simple entry.
Completely against the official approach of streamlining UI.
The entire approach right now is inefficient and bloated.
Either make a full feature calendar or make a streamlined helper. Donāt make it half and half=neither.
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).
5 Likes
After update, All my MQTT devices are gone. Roll back to 11.5 MQTT devices are fine
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 themqttkey.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.
Yesā¦Mine has restarted several times today since I updated.
Keep an eye on your memory usage, did it go near to 100% before the crash ?
I would like to link to my issue here please:
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.
1 Like
When can we expect to see 2022.12.1 on Docker HUB ?
Oups, This update broke my Apex cards where I use statistics, they are just saying āLoadingā.
Code looks lite this:
type: custom:apexcharts-card
graph_span: 48h
all_series_config:
statistics:
period: 5minute
stroke_width: 2
...
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. 
About Tile Card:
if I would like to have a slider connected to an input.number, is it possible?
So I could have a tile to turn on my light with adjustable timer