Do you have coiot set up properly?
And can you please point to your GitHub issue.
Velux integration is out of order with this release as confirmed here
Were the Unifi and Unifi Protect integrations not fixed in 2024.5.1?
I still received the same error and I cannot authenticate.
1 Like
Just as an FYI, Velux Integration w. KLF200 is working fine for me regarding Velux Skylight shades and 2024.5.1
always had to re-authorize to Synology DSM regularly, but as of late is needs to be done upon each and every powerup (of the NAS).
wonder if other users see this too, and, if it has to do with the recent changes in core.
Dont have any logs yet, well, besides this:
synology_dsm.exceptions.SynologyDSMLogin2SARequiredException: {'api': 'SYNO.API.Auth', 'code': 403, 'reason': 'One time password not specified', 'details': 'Two-step authentication required for account: homeassistant'}
and the popup notification
I havent changed the login system on my Synology, so wonder why HA needs this now.
Suppose I could take out the 2FA, but that seems the wrong fixā¦
Note: I dont run HA on my Synology NAS, I merely have HomeAssistant connect to it and check its vitalsā¦
I love the new Tile card for Locks with unlatch (open door) function!
The card did not work 100% with version 2024.5.1. It worked, but it was not possible to add feaures, IE the lock, unloack and Open door buttons. Version 2024.5.2 fixed that.
(Nuki 3.0 Pro lock FW 3.9.5 connected with WIFI/MQTT)
I like the new category-feature within the automations, but how do I remove a category?
open the filters, expand category, click 3 dots ā remove
1 Like
Starting from 2024.5, my Shelly 3EM is also acting weird.
I must say that, as it usually reports some reactive power here at home, I had to do some templating kung-fu to compute a sanitized value of the power (basically, 100*power/power_factor). All perfect for more than a year till May 2nd, when I installed 2024.5. After that, I started seeing unreasonable spikes in power consumption (see screenshots below, where it gets -50000KW and +40000KW 
).
I was forced to adjust my templates to filter aways those unreasonable values (negative and super-high power), so Iām pretty much good now, but still thereās something fishy that needs to be fixed I guess.
otoh, my Shelly 3EM has been working flawlessly so far, without any kung-fu.
For info itās still running on firmware 1.12.1 of 2022, per āif aināt broke, donāt fix itā principle, and Iām using it via the Shelly integration.
So it might be something specific to your config.
HI,
same here. The newest version of HomeAssistant 2024.5.2 shows the following errors:
a.) "relative lightning seems not to work any more.
b.)
After second boot the errors are much less; before the boot (directly after update) I saw many shelly errors. Than I rebooted, and in the error only this is left
2024-05-08 07:39:36.754 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration waste_collection_schedule 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-05-08 07:39:36.755 WARNING (SyncWorker_2) [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-05-08 07:39:36.755 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration enigma 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-05-08 07:39:36.756 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration dwd_weather 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-05-08 07:39:36.756 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration relative_brightness_light_group 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-05-08 07:39:36.757 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration espsomfy_rts 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-05-08 07:39:37.705 ERROR (MainThread) [homeassistant.config] Platform error: cover - No module named 'custom_components.relative_brightness_light_group.cover'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config.py", line 1439, in _async_load_and_validate_platform_integration
platform = await p_integration.integration.async_get_platform(domain)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1074, in async_get_platform
platforms = await self.async_get_platforms((platform_name,))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1151, in async_get_platforms
import_future.result()
File "/usr/src/homeassistant/homeassistant/loader.py", line 1121, in async_get_platforms
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 1064, in _load_platforms
platform_name: self._load_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1238, in _load_platform
cache[full_name] = self._import_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1270, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/loop.py", line 144, 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 1324, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'custom_components.relative_brightness_light_group.cover'
2024-05-08 07:39:38.142 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-05-08 07:39:39.256 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from dwd_weather, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'dwd_weather' custom integration
2024-05-08 07:39:44.900 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from dwd_weather, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'dwd_weather' custom integration
2024-05-08 07:39:44.904 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from dwd_weather, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'dwd_weather' custom integration
2024-05-08 07:39:47.495 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 642: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
2024-05-08 07:40:02.496 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: template, climate, timer, cast.media_player, schedule, fritz.binary_sensor, http, bluetooth_adapters, espsomfy_rts.button, camera, kodi, valve, espsomfy_rts.update, ssdp, template.sensor, radio_browser, counter, input_text, unifiprotect.number, switch, cloud.binary_sensor, dwd_weather_warnings, relative_brightness_light_group.light, dlna_dms, mobile_app.notify, unifi.image, hassio.sensor, scene, auth, fritz.device_tracker, google_translate, shelly, notify, unifi, version.sensor, shelly.switch, unifiprotect.switch, mqtt.binary_sensor, shelly.climate, number, met.weather, group, shelly.light, shelly.binary_sensor, text, zone, cloud.stt, espsomfy_rts, stt, hacs.sensor, my, media_player, energy, binary_sensor, lovelace, co2signal, squeezebox.media_player, ffmpeg, sun.sensor, person, shelly.button, unifiprotect.button, logger, tts, recorder, map, image_upload, zeroconf, dwd_weather, assist_pipeline, todo, fritz.update, squeezebox, unifi.device_tracker, hassio, upnp.binary_sensor, webhook, fritz.switch, blueprint, utility_meter, utility_meter.sensor, frontend, conversation, unifi.sensor, fritz.sensor, unifi.update, device_automation, hassio.update, unifiprotect.camera, dwd_weather.weather, cloud.tts, input_select, bthome.sensor, dwd_weather_warnings.sensor, mqtt, unifi.switch, analytics, cloud, shopping_list, dwd_weather.camera, script, hacs, mobile_app.sensor, fritz.image, default_config, version.binary_sensor, automation, espsomfy_rts.cover, bthome.event, lock, unifiprotect.text, hardware, select, dhcp, button, met, unifiprotect.light, intent, upnp.sensor, upnp, tag, kodi.media_player, co2signal.sensor, energy.sensor, espsomfy_rts.switch, hassio.binary_sensor, fritz.button, mqtt.sensor, homeassistant.scene, network, shelly.cover, mobile_app, bthome.binary_sensor, repairs, input_datetime, trace, unifiprotect.sensor, shelly.valve, system_health, cover, persistent_notification, event, sensor, bluetooth, unifiprotect.lock, application_credentials, api, homeassistant, image, cast, system_log, shopping_list.todo, unifiprotect.select, shelly.event, rest, input_boolean, fritz, logbook, unifi.button, shelly.update, unifiprotect.media_player, weather, homeassistant_alerts, device_tracker, mobile_app.device_tracker, rest.sensor, media_source, mobile_app.binary_sensor, wake_word, espsomfy_rts.sensor, unifiprotect, update, hacs.update, google_translate.tts, input_button, backup, history, stream, shelly.sensor, unifiprotect.binary_sensor, bthome, onboarding, usb, version, config, diagnostics, input_number, search, file_upload, espsomfy_rts.binary_sensor, group.cover, sun, dwd_weather.sensor, light, websocket_api The system is waiting for tasks: {<Task pending name='Task-1997' coro=<async_discover() running at /usr/local/lib/python3.12/site-packages/pysqueezebox/discovery.py:98> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}
2024-05-08 07:40:05.651 WARNING (MainThread) [homeassistant.components.kodi.media_player] Unable to connect to Kodi via websocket
not to meā¦
SError: [Errno 113] Connect call failed (ā192.168.1.32ā, 51200)
and my KLF200 is working and well connected to the lanā¦ no problem with 2024.4
2024.5.2 is working better here.
2024.5.0 and .1 are running with high CPU and stucks at all so I canāt operate on frontend. With 2024.5.2 it seems OK now, also with some custom integration with debug errors or open necessary adjustments.
Someone else having problems with the crownstone integration?
After the latest update 2024.5.2 the integration broke and reloading it doesnāt solve it.
Version of what?
1 Like
Sorry, typo HomeAssistant 2024.5.2
Yeah, not sure whatās going on with my Shelly 3EM.
When I first installed this, I thought about a defective device; but after some follow-up with Shelly support, it seems it might be due to my electric system. Perhaps my UPS system or maybe induction devices (induction hob, LEDs spread thoughout my house, etc). In the end, I didnāt feel like rewiring the Shelly 3EM to then discover itās not due to a defective device. So I came up with some smart templates that can report pretty accurately the consumption of my home.
That said, my HA templates have been working flowlessly for more than a year, and only in 2024.5 Iāve started seeing signs of weirdness. Looking more closely at my data yesterday night, it seems that the high number is due to the fact that the division Iām doing (power/power_factor) is using a fresh power but a power_factor which is 1 second older. So, in presence of power edges (when I turn on the induction hob for instance), this gives a spike. Iāve fixed this by adding an extra line to my template that checks if the division gives a negative or unreasonably high number, I just filter that away, and it seems to be working fine now. Hope this suggestion might help other people facing similar issues.
1 Like
The same issues for this custom component are being reported in the forum on the link above.
If you canāt find a solution there, you might want to raise an issue with the author of the custom component on the link below.
the shelly 1 device was actually on the network (i use a linux box to monitor all wireless IPs, and shelly IP never dropped), but ha was not seeing it consistently with 2024.5.1. I rolled back to 2024.4.4 until Core 2024.5.2 and OS 12.3 came out and decided to update both and give it a try. the issue appears to be resolved.
You canāt have it both ways.
1 Like