2024.12: Scene you in 2025! 🎄

Blog
22

After updating to 2024.12 my Tado integration doesn’t load my “Tado X” anymore.
I get this error when reloading it:

How to solve this?

Logger: homeassistant.config_entries
Source: config_entries.py:640
First occurred: 23:25:18 (4 events)
Last logged: 23:32:51

Error setting up entry Home for tado
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 640, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tado/__init__.py", line 84, in async_setup_entry
    await hass.async_add_executor_job(tadoconnector.update)
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 184, in wrapper
    result = method(*args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/tado/tado_connector.py", line 79, in update
    self.update_devices()
    ~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/components/tado/tado_connector.py", line 142, in update_devices
    device_short_serial_no = device["shortSerialNo"]
                             ~~~~~~^^^^^^^^^^^^^^^^^
KeyError: 'shortSerialNo'
23

I’m not a HA internals expert but as a linux admin my first suggestion would be to check you haven’t run out of disk space.

24

Another release, another AMP failure

Sorry, I probably should have made an announcement but I forgot.

4 Likes
25

Is there a setting for how long I want to save state history?

Recently switched to an NVMe HAT for the rpi5 and an 500GB NVMe.
Not sure how much I was using before, but after the upgrade/issues I’m using 2.5%.

26

Guess I no longer need to maintain my Fallback Conversation agent: m50/ha-fallback-conversation: HomeAssistant Assist Fallback Conversation Agent

1 Like
27

Does Music Assistant support Alexa / amazon music yet? Without support for that it’s just not useful.

28

The issue has been logged with ‘alexapy’ seems it has a restrictive requirement for aiofiles <= 24.0.0, but with the new release of HA, aiofiles is now at 24.1.0

You can check on the progress here
 seems it was raised 5 or so days ago, but the maintainer is replying strangely
 :person_shrugging:t3:

29

after update to 2024.12, and test fallback agent with an ollama, i have an error with defaut sentences : “Unexpected error during intent recognition”

2024-12-05 01:36:23.253 ERROR (MainThread) [homeassistant.components.assist_pipeline.pipeline] Unexpected error during intent recognition
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/assist_pipeline/pipeline.py", line 1057, in recognize_intent
    intent_response := await conversation.async_handle_intents(
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        self.hass, user_input
        ^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/components/conversation/__init__.py", line 233, in async_handle_intents
    return await default_agent.async_handle_intents(user_input)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 1346, in async_handle_intents
    result = await self.async_recognize_intent(user_input, strict_intents_only=True)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 330, in async_recognize_intent
    result = await self.hass.async_add_executor_job(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 537, in _recognize
    strict_result = self._recognize_strict(
        user_input, lang_intents, slot_lists, intent_context, language
    )
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 773, in _recognize_strict
    return recognize_best(
        user_input.text,
    ...<5 lines>...
        best_slot_name="name",
    )
  File "/usr/local/lib/python3.13/site-packages/hassil/recognize.py", line 580, in recognize_best
    for result in recognize_all(
                  ~~~~~~~~~~~~~^
        text,
        ^^^^^
    ...<7 lines>...
        language=language,
        ^^^^^^^^^^^^^^^^^^
    ):
    ^
  File "/usr/local/lib/python3.13/site-packages/hassil/recognize.py", line 231, in recognize_all
    intent_sentence.compile(match_settings.expansion_rules)
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/hassil/expression.py", line 150, in compile
    self._compile_expression(self, pattern_chunks, expansion_rules)
    ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/hassil/expression.py", line 170, in _compile_expression
    self._compile_expression(item, pattern_chunks, rules)
    ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/hassil/expression.py", line 176, in _compile_expression
    self._compile_expression(item, pattern_chunks, rules)
    ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/hassil/expression.py", line 170, in _compile_expression
    self._compile_expression(item, pattern_chunks, rules)
    ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/hassil/expression.py", line 189, in _compile_expression
    raise ValueError(rule_ref)
ValueError: RuleReference(rule_name='lumieres')

is a specific error on my side ?

30

After this update, I’m seeing the smartweatherudp component fail to load unfortunately. Submitted an issue over here.

32

so is there still no way to actually edit a scene without activating it?

its not that uncommon to know what changes need to be made (especially if it is just adding static lights or changing other things that are on/off or limited options) so still needing to activate the scene to make those changes seemse silly.

the review mode also dosnt show you the actual state of any of the entities in the scene so its pretty useless for review beyond “what devices/entities does this scene use”

you can at least edit it in yaml without activating it now but that is far from ideal. it dosnt seem to make sense to force the scene to be active while editing rather than just having a “preview” mode you can turn on that activates the scene but dosnt change the actual edit capabilaties

6 Likes
33

Hello,
Do shelly devices are working after this update?

34

Thanks Guys

another 10 out 10

Did my first update while at work ( don’t tell the boss) came home everything was updated and working

1 Like
35

Has anyone else noticed that ‘sunrise’ based triggers aren’t working with HA 2024.12 ?

This morning I was still on HA 2024.12.b4 (or 5, can’t remember) and none of my sunrise triggers worked
 simply no trigger occurred. I’ve since updated to HA 2024.12.0 stable so will see what happens tomorrow morning.

This simply didn’t trigger:

platform: sun
event: sunrise
offset: '-00:15:00'


which has done perfectly for years.

In the meantime I’ll update the automation to the newer syntax.

1 Like
36

Translations are a mess in this update. I have some of my HA in slovenian (like it should be), some in english (well
acceptable) and some in 
 Swedish/Finnish/Norwegian (one of those) 
??? Yes, i did a total page refresh (with “empty cache and hard reload”).

And, was there any warning about “file” integration changing? After update i’ve got an error about non-existing entity (nofity.export_to_file).


so i’m back to 2024.11.x for now.

37

Hey, i also have a lot of sunrise / sunset automations, not updated yet
 have you found something? what new syntax you mean?

38

The solution, I think, is to always send the command to both placers and then whichever one finishes quickest “wins”.

39

Simply that no trigger occurred at sunrise.

The new (a few months ago) syntax for triggers goes from:

trigger:
  - platform: sun
    event: sunrise
    offset: '-00:15:00'

to:

triggers:
  - trigger: sun
    event: sunrise
    offset: '-00:15:00'

I’ll see what happens in the morning.

41

Ok, will update also today
 Maybe it’s the sun integration itself?do you see errors in the log?

42

My shelly devices stoped working after this update, anyone else that got t
this problem?

1 Like
43

Seems there is a bug here? i got integretation that stopped working with this version

[[homeassistant.setup] Setup failed for custom integration ‘dreame vacuum’: Unable to import component: No module named ‘py_mini_racer’