IoSonoAndreaZ

about the “prefer handling commands locally” setting, I just found a drawback.

This is my test:

• Turn on kitchen light
  (assist will turn it on, not using chatgpt)
• Turn off the light that you turned on before
  (assist does not know the command, asks chatgpt but chagpt did not handled the other request, so It may turn off another light)

This is just an example, but it breaks conversations.

4 replies

IoSonoAndreaZ

another example:

Turn on kitchen light
(it turns the light on)

What was the last command you did?
(it reports the latest command done using chatgpt, not the one about kitchen light)

2 replies

pops106

Upgraded my test box without any issues, does feel snappier.

poudenes

Seems Alexa Mdia Player is broken with this version.

7 replies

demig

Yep broken for me as well. Nothing tremendously useful in the logs that I can see

1 reply

parautenbach

You can read all about it in the WTH announcement blog

@frenck this link gives me a 404.

FrancoLoco1234

(1) Beta 2024.12.0b0 breaks amp · Issue #2698 · alandtse/alexa_media_player

Error loading Alexa Media Player integration on the latest HA beta release 2024.12.0b0 which requires aiofiles>=24.1.0 (#33) · Issues · Keaton / alexapy · GitLab

1 reply

NathanCu

Yeahhh this would be completely breaking for me. I assume we can turn it off?

1 reply

gavinpbennett

Silly question: After updating, I do not see any way to get to the Scene > Review Mode. Scenes still launch when I try and view the scene. What am I missing?

1 reply

mcarty

Did you clear your cache or ctrl-F5?

1 reply

gavinpbennett

I did… Problem solved
Thanks.

rsonke

The stookwijzer integration is really nice now. Though the website of Atlas leefomgeving also gives a prediction of the next hours. Is that on the roadmap to be made visible (in attrributes or so)? It would be helpful that it remains oke for the rest of the evening for example.

1 reply

durd

This update seems to have deleted my configuration.yaml
Supervisor doesn’t seem to start properly either

Logger: homeassistant.components.recorder.core
Source: components/recorder/core.py:1176
integration: Recorder (documentation, issues)
First occurred: 21:57:14 (156 occurrences)
Last logged: 22:04:22

Error in database connectivity during commit: Error executing query: (sqlite3.OperationalError) unable to open database file (Background on this error at: https://sqlalche.me/e/20/e3q8). (retrying in 3 seconds)

and

Logger: homeassistant
Source: util/loop.py:200
First occurred: 22:00:09 (9 occurrences)
Last logged: 22:04:09

Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "src/habluetooth/scanner.py", line 514, in _async_restart_scanner
  File "src/habluetooth/scanner.py", line 526, in habluetooth.scanner.HaScanner._async_restart_scanner
  File "src/habluetooth/scanner.py", line 542, in _async_reset_adapter
  File "/usr/local/lib/python3.12/site-packages/habluetooth/util.py", line 13, in async_reset_adapter
  File "/usr/local/lib/python3.12/site-packages/bluetooth_auto_recovery/__init__.py", line 24, in recover_adapter
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
  File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1322, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1262, in _find_spec
  File "<frozen importlib._bootstrap_external>", line 1528, in find_spec
  File "<frozen importlib._bootstrap_external>", line 1502, in _get_spec
  File "<frozen importlib._bootstrap_external>", line 1605, in find_spec
  File "<frozen importlib._bootstrap_external>", line 1648, in _fill_cache
OSError: [Errno 5] I/O error: '/usr/local/lib/python3.12/site-packages/bluetooth_auto_recovery'

and

Logger: homeassistant.components.recorder.util
Source: components/recorder/util.py:202
integration: Recorder (documentation, issues)
First occurred: 21:57:09 (168 occurrences)
Last logged: 22:04:07

Error executing query: (sqlite3.OperationalError) unable to open database file (Background on this error at: https://sqlalche.me/e/20/e3q8)

and

Logger: homeassistant.components.recorder.core
Source: components/recorder/core.py:882
integration: Recorder (documentation, issues)
First occurred: 21:57:09 (1 occurrences)
Last logged: 21:57:09

Unrecoverable sqlite3 database corruption detected: (sqlite3.DatabaseError) database disk image is malformed [SQL: INSERT INTO states (entity_id, state, attributes, event_id, last_changed, last_changed_ts, last_reported_ts, last_updated, last_updated_ts, old_state_id, attributes_id, context_id, context_user_id, context_parent_id, origin_idx, context_id_bin, context_user_id_bin, context_parent_id_bin, metadata_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) RETURNING state_id] [parameters: (None, '-48', None, None, None, None, None, None, 1733345829.3116176, 39025954, 46266, None, None, None, 0, <memory at 0x7f4c49b7c0>, None, None, 1067)] (Background on this error at: https://sqlalche.me/e/20/4xp6)
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2116, in _exec_insertmany_context
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 924, in do_execute
sqlite3.DatabaseError: database disk image is malformed

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/recorder/core.py", line 882, in _process_one_task_or_event_or_recover
  File "/usr/src/homeassistant/homeassistant/components/recorder/tasks.py", line 297, in run
  File "/usr/src/homeassistant/homeassistant/components/recorder/core.py", line 1174, in _commit_event_session_or_retry
  File "/usr/src/homeassistant/homeassistant/components/recorder/core.py", line 1210, in _commit_event_session
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 2017, in commit
  File "<string>", line 2, in commit
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 1302, in commit
  File "<string>", line 2, in _prepare_impl
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 1277, in _prepare_impl
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 4341, in flush
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 4476, in _flush
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 4437, in _flush
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/unitofwork.py", line 466, in execute
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/unitofwork.py", line 642, in execute
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/persistence.py", line 93, in save_obj
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/persistence.py", line 1143, in _emit_insert_statements
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1418, in execute
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/elements.py", line 515, in _execute_on_connection
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1640, in _execute_clauseelement
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1844, in _execute_context
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2124, in _exec_insertmany_context
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2353, in _handle_dbapi_exception
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2116, in _exec_insertmany_context
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 924, in do_execute
sqlalchemy.exc.DatabaseError: (sqlite3.DatabaseError) database disk image is malformed
[SQL: INSERT INTO states (entity_id, state, attributes, event_id, last_changed, last_changed_ts, last_reported_ts, last_updated, last_updated_ts, old_state_id, attributes_id, context_id, context_user_id, context_parent_id, origin_idx, context_id_bin, context_user_id_bin, context_parent_id_bin, metadata_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) RETURNING state_id]
[parameters: (None, '-48', None, None, None, None, None, None, 1733345829.3116176, 39025954, 46266, None, None, None, 0, <memory at 0x7f4c49b7c0>, None, None, 1067)]
(Background on this error at: https://sqlalche.me/e/20/4xp6)

Among other sensor/integration errors.

Reboot/shutdown via GUI doesn’t work. Pulled the power of the rpi5 with no difference.
Can’t access backups to restore because supervisor doesn’t start (properly?).

Any ideas?

3 replies

durd

Hm, after the 2nd forced restart it seems to be working again.
Had the update available again, installing it this time worked.

1 reply

tom_l

Check if you have any history data.

1 reply

durd

I have history back until the 27th of november. Before that it’s empty

It seems I have certain history data earlier. Like temperature data, but state seems to only be available since the 27th.

1 reply

maumaumau

for what ever reason my knx secure tunneling connection does not work anymore.
Routing is no options, since I do not get any values.

1 reply

sdaltons

Glad I saw this before updating to 12.0. Following.

jaalperin

Yup. Went back to Core 2024.11.3. Want Alexa Media Player more than new features. Sounds like this could be an extended issue.

Emiel86

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'

bwduncan

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.

1 reply

petro Great contributor

Another release, another AMP failure

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

durd

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%.

2 replies

marisa

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

donaldtrump

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

grillp

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…

lightsabata

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 ?

beaulebens

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

TomW1605

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

1 reply

marnau

Hello,
Do shelly devices are working after this update?

6 replies

myle Guidance Counsellor

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

sparkydave Know-it-All

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.

4 replies

Protoncek Strokovni svetovalec

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.

pergola.fabio

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

1 reply

Chrisalbertson

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

1 reply

sparkydave Know-it-All

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.

5 replies

pergola.fabio

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

1 reply

Lugaid

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

3 replies

janip81

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’

2 replies

farmio Great contributor

Hi !
Try to reconfigure that connection.
If the issue persists, please create a GH issue or a new thread here for that. Feel free to @-ping me in there.

IoSonoAndreaZ

actually it is off by default, you have to edit assist settings to turn it on

pergola.fabio

report here: Issues · Tasshack/dreame-vacuum · GitHub

1 reply

IoSonoAndreaZ

same setting as you, my whole home assistant container is 1.8gb at the moment, but I never tracked its size

DataMeister

It is no secret: our voice hardware will be revealed on 19 December 2024.

What does that mean?

tom_l

All mine (sunrise and sunset triggers) have been working.

Check your underlying OS time (not HA system time). Check your HA location has not changed (unlikely).

1 reply

Renurios

My zha stoppt working. Downgraded to 2024.11.3 zha worked again.

2 replies

sparkydave Know-it-All

nothing relating to this issue.

1 reply

sparkydave Know-it-All

good point… looking at the Host log it is currently scrolling through log entries saying ~8:45am but it is currently 4:45pm (Perth, West Aus). Is that time supposed to be localised or is that supposed to be GMT? (if it’s GMT then that’s fine)

Time zone setting is fine:

1 reply

tom_l

Yes it is.

Thijmen

Seems to be a simple fix, simply add the context of the last few commands or the current conversation into the A.I. Would not be surprised if a developer reads this and adds this in the january release

thewizardfromoz

Do we not get a little teaser or preview of this big hardware announcement?

Mariusthvdb

those shouldnt be causing any change at all because:

this is not a breaking change , and there will be no deprecation

you can forever keep your former syntax, search elsewhere for your trouble

ColinRobbins

Please be aware this update breaks the Overkiz local integration.
Details here…

1 reply

GunterAv

Hello,

SmartIR are not working in this Version!

I have switched back to version 11.3.

Best regards
Gunter

1 reply

CChris

what version of Dreame vacuum (custom component) are you using?
I am on 2.0.0b16 and not noticed any issue with the integration.

If you are still on 1.0.4 I would recommend to switch to the current 2.0 beta version (which is quite stable) - since the 1.0.4 was not updated since may.

---

Thanks for the update, was a smooth one… it’s a bit odd, but somehow, I miss the work on adding new design options to my dashboards…

2 replies

guidok

With 2024.12.0 core update, my Shelly devices were no longer available in HA. After restoring my HA 2024.11.3 backup, the Shelly devices (Dimmers and Plugs) are available again in HA. I noticed a bug report on GitHub [BUG]update home assistant core to 2024.12.0 breaks em · Issue #782 · StyraHem/ShellyForHASS · GitHub

3 replies

pops106

I have 2 HA boxes, one is running 1.0.4 without any issues after the upgrade. Second box I am about to upgrade now.

The map takes a while to load in after a reboot, but that is on both boxes.

1 reply

CChris

the map will be extracted from the cloud, so I don’t think, that this is a HA or a topic specific for the integration…

But glad, that the 1.0.4 is working for you.
That indicates, the issue for janip81 is probably not an issue specific to the dreame integration, but might be a conflict with something else.

dana_se

ShellyForHass will no longer receive further development updates. This decision stems from the fact that its features and functionality have been seamlessly integrated into Home Assistant, making it redundant to maintain a separate plugin.
https://github.com/StyraHem/ShellyForHASS

Bieniu Shelly Integration Dev

You should migrate to the core Shelly integration.

1 reply

Bieniu Shelly Integration Dev

Fix is coming…

janip81

Done!

janip81

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

jurijvi

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

TimoJ

Change to this updated and maintained version of SmartIR:

HappyCadaver

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

refeu

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.

1 reply

Xitee

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.

mcarty

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

vacar

Yeah - that is so annoying. Now it has been stable for a few weeks…

mmatesic01

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

1 reply

Viking

How come NordPool integration is listed as a “new” integration in 2024.12 ??
I’ve had the Nordpool integration for many years!

2 replies

sd_dracula

Alexa media player still broken in 2024.12?

1 reply

petro Great contributor

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.

Michael_Dahl

My guess, not the same developer.

Also looks like different output, but I have not tried the “build in”

1 reply

petro Great contributor

Yes, and it’s likely to be broken for some time.

erikm

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…

3 replies

petro Great contributor

FYI you are correct, they are different developers

Protoncek Strokovni svetovalec

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…

3 replies

Waling

How can i migrate to the core Shelly integration?

1 reply

Bieniu Shelly Integration Dev

• remove from HA all Shelly devices
• remove/uninstall ShellyForHass integration
• restart HA
• configure Shelly devices

2 replies

pergola.fabio

My sunrise/sunset triggers are still working…

erikm

Quick scan, this is going to be dependency hell.

So ffmpeg 7.1 needs libsdl2-dev, which needs libudev-dev, which needs libudev1, and specifially version 252.31-1~deb12u1, but as I already need debian-backports packages for hass core, version 254.16-1 is installed.

But… I think I can disable the SDL feature for this particular use as SDL is used for native video playback so I’m going to recompile the package without support for SDL…

cerebrate

Looks like the relevant fix for alexapy just got merged over on Gitlab, so there’s definitely progress happening on the Alexa Media Player front.

Other integrations breaking with 2024.12, FYI: Anniversaries, Frigidaire, Grocy, and Schedule State.

mmatesic01

There has bo be somekind of backup in such cases.

robertwigley

Alexa Media Player 5.0.1 is released with the fix for this version and available to download/install/update to.

1 reply

petro Great contributor

Verified working

nighteyes

yep, same here.

nighteyes

i am using the core integration. none of my shelly devices are working anymore with this update. logbook shows multiple errors with the shellly core integration.

1 reply

Bieniu Shelly Integration Dev

Open an issue.

tom_l

The PRs can be reverted.

1 reply

hfeenstra

Had/have exactly the same. So went back to 2024.11.3
Will wait for update…

hfeenstra

Thanks for the heads up. Beside Shelly another integration that breaks. Just will be patience and wait

hfeenstra

Can we find the steps somewhere in the documents for this transition?

1 reply

Bieniu Shelly Integration Dev

No, HA documentation does not contain information about custom integrations.

1 reply

hfeenstra

Thought you mentioned in an earlier post it moved from custom to full integrated integration?
Just curious where I can find these heads up and the process to this new integration.
Thanks!

1 reply

Mariusthvdb

Had not notice before but experienced the same today. No automatic theme change, which has been reliable for years and years…

Haven’t found the trace yet to point to sun trigger 100%, so need to inspect further

1 reply

tilz0R

No issues for me. All works as expected.

smarthoo

all shelly are dead with the update. all unavailable. After restore the whole Home Assistant all shelly are working again. This update kills shellys!

1 reply

ShawnP

Same for me. Had to rollback.