2024.12: Scene you in 2025! šŸŽ„

You should migrate to the core Shelly integration.

2 Likes

Fix is comingā€¦

Done!

1 Like

I use the version 2.0.0b16 and how tried redownloading integraton too, have no idea why its not working. Only thing that worked for me was to roll back to older container image

ZHA and Overkiz are broken by 2024.12, reverting back to 2024.11 and no issues.

1 Like

Change to this updated and maintained version of SmartIR:

I have 2 of these and both triggered just fine last night and this morning.

Not the best experience if you are doing some midnight tinkering and accidentally activate a scene that turns on all the lights in the house, waking up everyone.

Damn, it really happened to me exactly like that (not turning on the lights but opening the shutters.

This would be a solution to the problem that the agent is not aware what the last prompt was but one of the benefits of trying it first locally is that it reduces costs. The LLMs are not (completely) free. For example the Google LLM is free for some amount of requests but if it is exceeded, it will cost you money.

I never tinker or update when its dark. Always wait to next morning! :slight_smile:

1 Like

Yeah - that is so annoying. Now it has been stable for a few weeksā€¦ :man_facepalming:

With 2024.12 if HA is set on Slovenian language interface some of the text is in scandinavian language.

How come NordPool integration is listed as a ā€œnewā€ integration in 2024.12 ??
Iā€™ve had the Nordpool integration for many years!

Alexa media player still broken in 2024.12?

It was custom before, now itā€™s built in. I do not know if the feature parity is the same as the custom integration. Your custom integration will overwrite the built in one, so thereā€™s nothing to worry about if you are still using the custom integration.

1 Like

My guess, not the same developer.

Also looks like different output, but I have not tried the ā€œbuild inā€

Yes, and itā€™s likely to be broken for some time.

Upgrading hass-core on a Raspberry Pi 3 running Raspbian/Debian Bookworm (i.e.: current stable) breaks on PyAV:

(venv-3.12) pi@hass:~/.homeassistant $ uv pip install -U homeassistant
[...]
      ^~~~~~~~~~~~~~~~~~~~~~~~~
            |
      AV_CODEC_FLAG2_NO_OUTPUT
      src/av/codec/context.c:15851:48: error: ā€˜AV_CODEC_FLAG_FRAME_DURATIONā€™
      undeclared (first use in this function); did you mean
      ā€˜AV_CODEC_CAP_FRAME_THREADSā€™?
      15851 |   __pyx_t_2 =
      __Pyx_PyInt_From___pyx_anon_enum(AV_CODEC_FLAG_FRAME_DURATION); if
      (unlikely(!__pyx_t_2)) __PYX_ERR(0, 76, __pyx_L1_error)
            |
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
            |
      AV_CODEC_CAP_FRAME_THREADS
      error: command '/usr/bin/gcc' failed with exit code 1
INFO:homeassistant.util.package:Attempting install of numpy==2.1.3

Incorrect config
  General Warnings:
    - Integration error: default_config - Requirements for stream not found: ['av==13.1.0'].

Successful config (partial)

And apparently we came from the Hass AV fork ha-av 10.1.1 and upgraded to upstream av 13.1.0. Unfortunately that depends on ffpmeg 7.1 while Bookworm comes with version 5.1.6.
Thereā€™s no newer ffmpeg version available in Debian Backports, so I might end up building the package from the source package in Debian testing. Now I only need some timeā€¦

1 Like

FYI you are correct, they are different developers

1 Like

True. Iā€™ve been told that some swedish guy was translating into slovenian file instead his ownā€¦ i changed to english for now. From what i saw on ā€œlokaliseā€ over 3000 words are overwritten, so unless thereā€™s any kind of backup there weā€™re fu**edā€¦