2024.11: Slick dashboards and speedy cameras

udar · November 16, 2024, 9:41am

Hi, I’m new here, wanted to add a +1 .
I since restarted HAOS (virtualized with proxmox, 4gb ram).
docker exec -ti /bin/bash into the homeassistant docker container
go2rtc uses up a lot of ram, and I don’t even have frigate or any camera integration installed.

Is there a way to disable at least meanwhile, go2rtc ? I’m really not using it AFAIK.
@petro can this be considered proof that go2rtc is causing issues ?

Later edit: I am very gratefull for home assistant and this community, this is great!
Later later edit: I am probably out of my depth on the above, reading up on different aspects …

Lode1 · November 16, 2024, 12:08pm

Another try after updating to 2024.11.2

Deleted default_config:
Added everything manually except go2rtc:
Addon RtspToWebrtc is running.
Restart HA
Cleared browser cache

Still slow and laggy camerastream.
They really messed up !!!


assist_pipeline:
backup:
bluetooth:
config:
conversation:
dhcp:
energy:
history:
homeassistant_alerts:
cloud:
image_upload:
logbook:
media_source:
mobile_app:
my:
ssdp:
stream:
sun:
usb:
webhook:
zeroconf:

petro · November 16, 2024, 12:21pm

I suggest you create a separate support thread then. Sorry I can’t help any further.

petro · November 16, 2024, 12:28pm

You can disable it by taking control of default_config. It’s highlighted in an earlier post in this thread.

dumaresq · November 16, 2024, 1:19pm

I have been unable to upgrade from 2024.10.4 I tried to upgrade to 11.1 and 11.2 and both time I get the following error:

024-11-16 08:13:15.427 ERROR (MainThread) [root] Uncaught exception
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
                ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/runner.py", line 157, in setup_and_run_hass
    hass = await bootstrap.async_setup_hass(runtime_config)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 326, in async_setup_hass
    await async_from_config_dict(config_dict, hass) is not None
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 458, in async_from_config_dict
    await async_load_base_functionality(hass)
  File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 427, in async_load_base_functionality
    await asyncio.gather(
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1977, in async_initialize
    entries[entry_id] = config_entry
    ~~~~~~~^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1618, in __setitem__
    self.check_unique_id(entry)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1659, in check_unique_id
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: The entry unique id ['[email protected]'] is not a string.

Any suggestions on what is wrong, or where I should report this bug?

extraordinaryzen · November 16, 2024, 5:41pm

For my scenario, after upgrading from 2024.10.4 to 2024.11 - I can see python crashing in the CLI within like 15 seconds of Core starting up integrations - would any of the guidance here help? 2024.5+: Tracking down instability issues caused by integrations - when I checked logs before (admittedly not in debug mode) I didn’t see anything obvious causing startup issues. Should I try and turn on debug mode before upgrading, then attempt the upgrade again?

YetAnotherDave · November 16, 2024, 10:16pm

WebRTC OMG!! I have a page with 13 camera views that I hardly ever used, but now: pop, pop, pop… all visible within 20 - 30 seconds. an awesome performance improvement. Thank you!!

TrustKomp · November 16, 2024, 11:43pm

Hi All,

Is here someone who is using USB Modem to sending messages ? After update 2024.11.2 I have lost this functionality and errors look like below. Also I have noticed, that all statuses of entities are now not in Polish but in English.

Rejestrator: homeassistant.config_entries
Źródło: config_entries.py:3249
Pierwsze zdarzenie: 00:12:03 (5 zdarzenia)
Ostatnio zalogowany: 00:23:12

Error occurred loading flow for integration sms: cannot import name 'GammuAsyncWorker' from 'gammu.asyncworker' (/usr/local/lib/python3.12/site-packages/gammu/asyncworker.py)

------------------ ALSO -----------------------------


Rejestrator: homeassistant.setup
Źródło: setup.py:334
Pierwsze zdarzenie: 00:08:59 (1 zdarzenia)
Ostatnio zalogowany: 00:08:59

Setup failed for 'sms': Unable to import component: cannot import name 'GammuAsyncWorker' from 'gammu.asyncworker' (/usr/local/lib/python3.12/site-packages/gammu/asyncworker.py)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1011, in async_get_component
    comp = await self.hass.async_add_import_executor_job(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1071, in _get_component
    ComponentProtocol, importlib.import_module(self.pkg_path)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/usr/src/homeassistant/homeassistant/components/sms/__init__.py", line 25, in <module>
    from .gateway import create_sms_gateway
  File "/usr/src/homeassistant/homeassistant/components/sms/gateway.py", line 6, in <module>
    from gammu.asyncworker import GammuAsyncWorker
ImportError: cannot import name 'GammuAsyncWorker' from 'gammu.asyncworker' (/usr/local/lib/python3.12/site-packages/gammu/asyncworker.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 334, in _async_setup_component
    component = await integration.async_get_component()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1031, in async_get_component
    self._component_future.result()
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1023, in async_get_component
    comp = self._get_component()
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1071, in _get_component
    ComponentProtocol, importlib.import_module(self.pkg_path)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/usr/src/homeassistant/homeassistant/components/sms/__init__.py", line 25, in <module>
    from .gateway import create_sms_gateway
  File "/usr/src/homeassistant/homeassistant/components/sms/gateway.py", line 6, in <module>
    from gammu.asyncworker import GammuAsyncWorker
ImportError: cannot import name 'GammuAsyncWorker' from 'gammu.asyncworker' (/usr/local/lib/python3.12/site-packages/gammu/asyncworker.py) >

Entities status in EN (was wykryto):
obraz

Lode1 · November 17, 2024, 9:55am

Maybe a last question.
Is it normal i see this after deleting go2rtc in the default_config ?
Or do i have to make some adjustments in the yaml file ?

go2rtc

TrustKomp · November 17, 2024, 2:47pm

I don;t know how to explain this but after few hours now the same values are in Polish again (without, restart or other action from my site)

obraz

Regarding issue with SMS Gateway, still the same

AlDek · November 17, 2024, 4:37pm

I have 5 cameras: 3 - H265 (Dahua) & 2 - H264 (Hikvision) with
picture-entity cards for direct video output from cameras.
Frigate ver. 0.14.1 is installed (incl. go2rtc).
HAOS, generic-x86-64, bare metal system.
Everything works fine on version 2024.10.4.
After the update on 2024.11.2, picture-entity cards do not work for H265 streams, even through the existing go2rtc in MSE(mp4) mode.
Picture-entity card shows ordinary snapshot picture, but on tab/click it just minimizes to “only header-show” mode.
There are no errors in the logs.
H265 cameras only work with a ‘custom:webrtc-camera’ after installation of a WebRTC Camera, but this does not suit me.
How can I configure go2rtc or something else so that picture-entity cards will work with H265 streams at 2024.11.2 core?

juergenjw · November 17, 2024, 8:10pm

Today i have upgraded to HA 2024.11.2 and wanted to try the logs streaming live!. Is this new feature reserved for HAOS or supervised installations? My installation is just HA in a docker container.

mephits · November 17, 2024, 8:55pm

Has anyone else had trouble with Zigbee since upgrading to 2024.11.2? ZHA integration completely failed to the point I thought my SkyConnect had died. The integration failed to load and all Zigbee devices were unavailable. I tried reboots, a different USB extender, different ports on my RPi, and finally in desperation replaced my install from a backup from before the last update. That fixed the problem immediately.

I tried looking through the logs to find any errors, but because the integration wouldn’t initialize the ZHA integration page couldnt access the logs, and I couldn’t figure out what to look for in the log viewer in System. Anybody have any thoughts?

Lode1 · November 18, 2024, 4:54am

Are you using the build in integration or Webrtc as custom integration?

mephits · November 18, 2024, 5:13am

Well, never mind. Rolling back to an old backup worked for a few hours, and then the ZHA integration failed again and I’ve lost connection to everything. Guess it’s not the new update, at least? I’ll start a new thread elsewhere.

Nick4 · November 18, 2024, 11:08am

No, that’s in the release notes.

TrustKomp · November 18, 2024, 11:30am

I have checked and now I know why issue with gateway is, becasue mnot exist python3 in lib:

Are you able to verify if you have the same situation?

YetAnotherDave · November 18, 2024, 2:23pm

I just use the built-in integration. All my camera cards are some variation of:

show_state: true
show_name: true
camera_view: auto
type: picture-entity
entity: camera.g4_instant_medium
name: G4

All RTSP connections: Amcrest, Reolink, Tenvis, Unifi, Wyze, Yi. A veritable dog’s breakfast of camera brands and models.

Lode1 · November 18, 2024, 2:52pm

And you are not using things like Reolink integration ?

Mariusthvdb · November 18, 2024, 3:05pm

back to some experimenting with the slick dashboards, and trying to feel some love for the new badges.

I so wish we could set the icon size to a few more pixels.

practically impossible to see the 64 in the processor badge.

this seems out of balance, particularly because there is so much empty space left.

the icon is set with the generic --mdc-icon-size, so we can not set it in a theme either (because it sets the size for all regular icons too.)

since card-mod cant touch it either, my older eyes are lost on this…

unless there could be an introduction for eg --ha-badge-icon-size ofc, and use that in the themes.

imho this should have a place in the accessibility contemplations of the Frontend team.
please.

so at least the users with +4 glasses (…) can do:

Schermafbeelding 2024-11-18 om 16.07.50

notice how the increase of the icon-size (In Inspector, not card_mod) hardly impacts the total size of the badge. cant be a reason not to do so

funny thing is we Can do

ha-badge-size: 48px

Schermafbeelding 2024-11-18 om 16.11.25

which blows up the badge, but leaves the icons untouched…