It was possible to simply migrate to the GUI 
Its not just me then, I kind of did to things at once moving my CCTV recording to a USB disk and also upgraded.
Things are much snappier and clicking on some sensors to bring up graph used to take a second or two. Now its instant.
Yes, I do thave that log, I canât say I really understand all of this log:
2024-02-08 08:24:46.898 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-02-08 08:24:46.900 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration octopus_energy which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-02-08 08:24:46.903 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tesla_custom which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-02-08 08:24:46.905 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration deltasol which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-02-08 08:24:46.907 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-02-08 08:24:46.909 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hikvision_next which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-02-08 08:24:49.216 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 221, 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 188, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 684, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in setup_and_run_hass
hass = await bootstrap.async_setup_hass(runtime_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 203, in async_setup_hass
await async_from_config_dict(config_dict, hass) is not None
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 319, in async_from_config_dict
await async_load_base_functionality(hass)
File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 296, in async_load_base_functionality
await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1354, in async_initialize
entries[entry_id] = config_entry
~~~~~~~^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1148, in __setitem__
self._domain_unique_id_index.setdefault(entry.domain, {})[
TypeError: unhashable type: 'list'
I seem to have issues with my Nest thermostat and perhaps also in combination with the mushroom cards. I am restoring a backup now as it was unworkable and very unresponsive.
1 Like
Unable to install package matplotlib: error: subprocess-exited-with-error Ă python setup.py bdist_wheel did not run successfully.
Anyone with an idea if that could be solved manually?
There is a solution in this issue for your problem:
1 Like
Drag and drop for automation items into other items is big. So many times Iâve had to recreate an action/condition or move it around in YAML just because I want to wrap it in a new conditional block etc.
H200, is partly a Wired(ethernet) Hub, but the main difference is the firmware, it uses HTTPS, instead of HTTP, and i believe another (new)more secure authentication process
I doubt The communication to the Devices attached to the hub is a problem, as both T100 and T310 is supported by H100 ( And HA has nothing to do with this communication )
It was the fact that it was a Wired Hub, and the efficient/stable signal-strength (great performance) 866MHz communication, which was the major cause for me to try this ( i want to reduce the communication on 2.4GhZ )
Cameras works great in Tapo: CameraControl Integration
Many thanks indeed for finding this solution for me. It was the HikVision integration that I had to remove, and of course the UK Met Office integration is no longer supported. Now I have to find how to restore the HikVision CCTV integration working again, but I am now running core 2024.2.0.
1 Like
I Know, i use that integration for all my Tapo strips and Plugs, The author is looking into changing/adding the protocol and auth-process to support the H200, not sure how it goes
I still live with a hope, in near future 
⌠so i can replace Basement and Garage with 866 / 920ghz(if in us/au) Devices
( Zigbee sensors seems to have âissuesâ with cold, humid environments, draining the batteries and weak signal )
Looks like it is (at least partially) related to the Hikvision integration from HACS.
I had that and after removing it, I have been able to update. Itâs possible other custom integrations trigger the same issue. There is a fix being proposed.
Unfortunately that means I have run into issues with the Omada integration that popped up in 2024.1.6:
Iâd been hoping the fix would have propagated through but not yet⌠so maybe I am rolling back to 2024.1.5
Thanks for Bring! integration, we have been waiting it for so long
However, i think you miss language configuration, because all my products are in german xD
1 Like
I was able to get the Omada integration working again on 2024.2 but had to delete the Omada hub and re-add it (with SSL disabled in my case)
1 Like
Yep - tried that and nothing .
I just tried this fix and it worked for me.
Had hoped this was included in 2024.2⌠but maybe not.
I might delete this⌠reboot and try again.
Just did that (delete the new custom version, reboot⌠not select the SSL verification) and it is installed.
Is there a web post available showing the statement from yesterdays release party regarding stopping multipan development and instaed use either zigbee or thread with a single radio?
Is there any change on the energy dashboard ?
yesterday before the update :
today after the update (late yesterday) :
Some interesting and useful changes. The ability to easily download csv files is brilliant. I have long wanted to analyse our home data to see how factors interact such as the amount of heating oil we use compared to windspeed,direction and temperature.
Also the ability to update (some) IOT firmware in ZHA is a good start - it is so annoying to have to keep loads of useless proprietary apps on my phone or reinstall them just in case thereâs a firmware update.
Nothing is perfect, (my Met Office integration is broken because of the python upgrade), but I wouldnât be using HA if it wasnât fun to play withâŚ!
Thank you.
Just make a template sensor that does the same thing
template:
- sensor:
- name: Internet Time
state: >
{% set time_bmt = now() + timedelta(hours=1) %}
{% set delta = timedelta(
hours=time_bmt.hour,
minutes=time_bmt.minute,
seconds=time_bmt.second,
microseconds=time_bmt.microsecond,
) %}
{% set beat = (delta.total_seconds() * 10) | int // 864 %}
{{ "@{0:03d}".format(beat) }}
Please do not respond back with âBut why???â. Iâm just providing an option to get beat time in the latest version. Iâm not interested in a conversation about the deprecation of the option, nor am I interested in the opinions about itâs deprecation. Thank you.
EDIT: The previous implementation didnât update every 86.4 seconds it updated once a minute, (EDIT: It did, looked in wrong spot in code) but to do this with a template sensorâŚ
template:
- trigger:
- platform: time_pattern
microseconds: \600
sensor:
- name: Internet Time
state: >
{% set time_bmt = now() + timedelta(hours=1) %}
{% set delta = timedelta(
hours=time_bmt.hour,
minutes=time_bmt.minute,
seconds=time_bmt.second,
microseconds=time_bmt.microsecond,
) %}
{% set beat = (delta.total_seconds() * 10) | int // 864 %}
{{ "@{0:03d}".format(beat) }}
This will force the entity to update every .6 seconds which will always fall on an increment of 86.4. IMO itâs not necessary, and a 1 second interval would also get the job done. Or you can just leave it with the minutely updates.
template:
- trigger:
- platform: time_pattern
seconds: \1
sensor:
- name: Internet Time
state: >
{% set time_bmt = now() + timedelta(hours=1) %}
{% set delta = timedelta(
hours=time_bmt.hour,
minutes=time_bmt.minute,
seconds=time_bmt.second,
microseconds=time_bmt.microsecond,
) %}
{% set beat = (delta.total_seconds() * 10) | int // 864 %}
{{ "@{0:03d}".format(beat) }}
2 Likes