2023.12: Welcome home!

[mirekmal (Mirek Malinowski)]

@PedroKTFC

Secondly, the idea you don’t have to upgrade is unrealistic. Take the example of integrations, if the target of the integration changes, you have no choice but to upgrade to maintain compatibility.

So you contradict yourself. Do you want upgrade instantly, as soon as HA adopt to target integration changes or you prefer to lose specific functionality and wait 6 months for stable, updated relese?

[petro]

Not really, it seems more erratic for me. I do have a random huge 12 hour 3% increase yesterday.

The arrows are when I think I updated the first beta and the first .12 release.

[petro]

Please update to 2023.12.1. The buttons are back.

[tom_l]

Very slight increase over the long term average:

However I connected a UPS via the NUT add-on and integration and some new zigbee smart plugs since the update.

[Glasofruix]

The 2023.12.1 seems to have killed smappee integration…

[petro]

@Glasofruix

smappee

Whatever broke on your system is a coincidence. That integration hasn’t been updated in 3 months, and it was a minor change to attribute names.

[Glasofruix]

Haha coincidence indeed, the smappee cloud services have gone down while i was updating

Now the other problem is that i can’t charge my car properly, but that’s not HA’s fault

[Domoticon]

FYI, I just updated and no problems here (sofar).
I noticed your posting just before updating and I made a DSM Virtual Machine snapshot prior to the HA update (2023.11.3 → 2023.12.02), just to be sure. Didn’t need it (sofar).

(Synology RS820+ with DSM 7.2.1-69057 Update 3)

[jim_os]

Dto. No problems/errors with

DS720+
DSM 7.2.1-69057 Update 1
VMM 2.6.5-12202

HA VM:

Core 2023.12.0
Supervisor 2023.11.6
Operating System 11.2

Or now:
Core 2023.12.1
Supervisor 2023.11.6
Operating System 11.2

Sofar.

[Armenak]

I agree that while the new thermostat card looks very nice, love the animations when heating and cooling, etc…, I would like the option of being able to see the current temperature as the main component / more prominently as it used to show before. Current temperature now on the card looks miniscule. It would be great to have an option to be able to adjust this, etc… It would also be good to see the humidity percentage on the component as well when looking at our dashboards. Thanks.

[jazzyisj (Jason)]

Man I gotta step up my screenshot notations. You and petro are making me look lazy…lol.

After several updates with decreased mem/cpu usage I was surprised to see it go up but everything is still working swimmingly so I guess I won’t waste too much time looking into it. I really wish there was more info about how to use the profiler integration. I’ve run a memory report but I really have no idea what I’m looking at.

Thanks for the data though (petro too!).

BTW the heat map for mem use is very cool!

[datascope11]

Guess I’m holding off on this update until I have several hours to sit down and redo all my Harmony Switch stuff… Can’t even being to imagine the work here, automations, scripts, HomeKit, Alexa setups… Sheesh. Change for change sake, but what is the actual benefit here? Way to go.

[petro]

ShareX, free open source screen capture software w/ annotations.

[petro]

Take a look at my last post to replicate your old switches without changing anything else.

@petro

switch:
- platform: template
  switches:
    roku:
      friendly_name: Roku
      value_template: "{{ is_state_attr('remote.living_room', 'current_activity', 'Roku') }}"
      turn_on:
      - service: remote.turn_on
        target:
          entity_id: remote.living_room
        data:
          activity: Roku
      turn_on:
      - service: remote.turn_on
        target:
          entity_id: remote.living_room
        data:
          activity: PowerOff

@petro

image1248×525 25.4 KB

[jspanitz]

Agreed - MFA integrations could use a major overhaul and should have been part of this new “feature”.

[datascope11]

Thanks for this, I will use. However, I do have to point this out… Let’s remove the built in switches, and make users script in 15 lines of code per activity = 90 for me (6 activities). What was the actual point of this? And how does it benefit the user or platform? I’m not directing these questions at you of course, just venting some frustration around what appears to be change for the sake of change. Not really sure why this had to be removed. The “integration had multiple ways to control activities” doesn’t seem to justify it for me.

The funniest part of all this is that years ago when I first setup Harmony, there was no built in switches. So I had all this templated. Then they added the switches, and I had duplicates of every activity. So I removed the scripted ones in favor of the more user friendly switches. Now I’m back to where we were years ago. How this is user friendly is beyond me.

[stevemann (Stephen Mann (YAML-challenged))]

@arjankoole

It really would have been great if the migrations for homewizard plugs that made it to 2023.12.1 would have been in 2023.12, where it broke.

I tend to wait for the .1 release and consider the .0 release as a release candidate. If you have a spare Raspberry or Intel PC, install Home Assistant on it and become a beta tester. More beta testers means more obscure bugs will be uncovered earlier.

[nickrout]

Frankly i use my production machine on the betas.

[frenck (Franck Nijhof)]

Same! Running beta on my production to catch real world issues.

[bschatzow (Bill Schatzow)]

Also running the beta on your production machine allows you to interact with the developers and get problems that effect your installation resolved fairly quickly.