2022.9: Home Assistant Birthday Release!

Woohoo! Fixed in 2022.9.4. My thermostat is working like a charm again.

Thanx all,

OLIVER

1 Like

Anyone else having problems with their enities not reflecting the customizations?

Yesterday all my friendly_name entries was showing up in the UI, but after upgrading from 2022.9.2 to 2022.9.4 earlier today, both custom naming and icons are goneā€¦

1 Like

problems with switchbot too, the bot turns unavailable after a whileā€¦

edit: turn unavailable around 10 minutes after reboot, if i use the bot or notā€¦

Please how do I create a full back-up for a set back if things go all belly up?
At the moment I run 2022.9.1 I did not dare update for I read that MQTT has been changed, i feel it breaks a lot. And now to make it worse i read friendly names get depreciated and names get changed, am I correct or do I read this wrong.
I use HA ever since mm version 0.35 i guess and I think it is superbly made it is awesome, but I keep commenting that if puritans who code like super proā€™s think something is an easy change and it makes it so more pure the code, it often makes me and I guess other less gifted programmers sweat, it will take us many hours if not days to correct the so called easy little things in the code.

So for me how to make a roll back backup? And is this new 2022.9.4 going to break my MQTT and all my customized and changed friendly names that would break my dash and well if names change I think I need to update all my automations too?

You use backups in the menu system. But HA has not broken mqtt. Bad configuration doesnā€™t work in 2022.9, but that has been signalled for a long time.

1 Like

I wonder if the new Schedule helper could be extended to not only hold on/off states but optionally also whatever values we define. For example we could hold a temperature value for each defined period, or a light temperature, or brightness, or any other value instead just turning it on or offā€¦ What do you think?

Currently, an off ā†’ on state-change represents the start of a time period and on ā†’ off the end of a period. In other words, on means a time period is in effect and off means itā€™s not.

How would what you proposed be used in an automation to indicate the start and end of a scheduled time period?

I would define a trigger on a state value of the schedule helper. If the state changes from one defined value to another at defined time it would start the automation and use the state value for the actions

Currently, itā€™s easy to tell if a schedule entity is within a scheduled time period because its state value is on. With your proposal, it might be a value like 23 which doesnā€™t communicate whether itā€™s in a time period or not.

Perhaps a compromise would be a schedule entity with two user-configurable attributes. For example the start_period attribute can be assigned whatever value you want for use when the schedule entity enters its from time (i.e. the start of the time period). Similarly, end_period can contain whatever value you want for when the time period ends.

The automation can be triggered by a simple State Trigger and then it can reference the values of start_period or end_period to set light brightness, thermostat temperature, etc. The attributeā€™s value can be referenced in the automation using trigger.to_state.attributes.start_period.

# Proposal demo
alias: example
trigger:
  - platform: state
    entity_id: schedule.your_schedule
condition: "{{ trigger.to_state.state in ['on', 'off'] }}"
action:
  - service: light.turn_on
    target:
      entity_id: light.your_light
    data:
      brightness_pct: "{{ trigger.to_state.attributes[iif(trigger.to_state.state == 'on', 'start_period', 'end_period')] }}"

EDIT

The attribute names I chose are for example purposes only. Maybe on_value and off_value are better. :man_shrugging:

I use the Samba Backup add-on to do a full backup every night at 1:00 AM to my NAS. I have so badly bricked my system a couple of times that all I needed to do to fix it was to restore the backup.

There is also a Dropbox backup add-on, but I havenā€™t tried it yet.

Been getting these Out of Memory Errors

is me

plus cant access anything past the System menu

:slight_smile: Well I know how to back up sorry, the only thing that goes wrong isā€¦ when you have many third party installs or when you made some own entities, which i have over de so many years that i use HA. Those often get lost in the back up. So often in the past I had back ups that were not accessible, like you make a BU reinstall everything and then it says sorry do not open the BU ??? or biggest problem was from a raspi 3 to a raspi 4 not to mention the update from HA 32 bit to HA 64 bit and a SSD, had to rebuild everything from scratch.
In this new build I read many things changed in names, MQTT a couple roll outs before gave me already a head ache :slight_smile: lucky enough people here are awesome although bit scattered lately over so many topics, that answering now is taking much more time then in previous years. But they are awesome, as are the developers of HA I seen this grow from a basic setup to what it is now, it is so versatile so ingenious en so well running. And yes I do understand the need of progress in this so many new add on, ā€¦ alas a few got shredded like gpio on the raspi and a few others.
It is just that for real great coders and we do have a lot here a nightly change is no sweat, but for some it is diving into the forum, for hours if not days to get things up and running again. owww and yes I always read the changes in the new version, but do not always comprehend what they mean or what is askedā€¦ all I want to say is that there are more like meā€¦ loving HA, but sometimes struggling to keep up with the changes

1 Like

Just a heads up that this add-on no longer works as Dropbox changed their API.

However, itā€™s been forked and updated by Matthew Hadley

https://github.com/matthewhadley/homeassistant-dropback/blob/77e5be254919928133e9fc96df90553828004f00/dropback/DOCS.md

1 Like

With 2022.9.5 (unreleased) and HAOS 9.0 Iā€™m getting connect times between 1-2s now.

2022-09-15 03:36:14.653 DEBUG (MainThread) [bleak_retry_connector] Tech Room Door (M1028U8) - /org/bluez/hci0/dev_78_9C_85_08_DE_21: Connecting (attempt: 1, last rssi: -70)
2022-09-15 03:36:15.705 DEBUG (MainThread) [bleak_retry_connector] Tech Room Door (M1028U8) - /org/bluez/hci0/dev_78_9C_85_08_DE_21: Connected (attempt: 1, last rssi: -70)
2 Likes

You can use the profiler integration to hunt down memory leaks.

Having some issues after installing this releaseā€¦

Why are these separate?

Can I u/g 1 at a time, or should I do both? HA Core seems to get 0.1+ updates every few days, does that mean I should wait a while for it to be stable? Iā€™m a newbie and canā€™t handle bleeding edge.

one is the operating system that runs home assistant (Home Assistant Operating System, HassOS), the other is home assistant (Home Assistant Core, HA).

1 Like

Well said! Itā€™s hard sometimes for developers to remember that not everyone lives and breathes every day to tinker with that one component they are working on. And yes, the changes are very often so cryptic I have no idea whether they apply to me or not. A lot of them look like ā€œBumped qxwlrtz to Ver 1.2.3.4.5.ā€ Huh? Should I be worried? What do I need to test?

To your question about backups, my solution is to copy the HA ā€œconfigā€ directory to my NAS as part of my normal daily backup routine. I donā€™t do regular HA backups. When itā€™s time to restore, the HA storage device is probably corrupt or will be overwritten as part of the restore process anyway. I run the HA backup before making any significant changes to HA, and immediately copy it somewhere I can grab it again if I need to restore.

One big automation looks very nice after updating the name

1 Like