I have been using the beta smartlife integration via hacs in place of the Tuya one for a while. I see the “official” tuya integration is now using the same much simpler authentication. Does this mean the entire new integration in the beta smartlife version is now live in the tuya one, or is there still a difference between them? The beta smartlife integration has been rock solid for me after the months of failed status updates etc. from the Tuya one, so I don’t want to go through converting back to the “official” integration only to find it’s only the authentication that has been updated.
I’ve installed 2024.2.1 and I’ve been informed I have a firmware update for one of my ZigBee devices. I tap on install but it fails. The device is a ZBMINIL2
by SONOFF. It is a no neutral light switch. I’ve tried doing an update with it being on and off, neither works. Any suggestions? Here’s the log which doesn’t particularly help me unfortunately.
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:240
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 08:38:45 (6 occurrences)
Last logged: 08:52:53
[546893482432] Update was not successful - result: <Status.FAILURE: 1>
[547684506304] Update was not successful - result: <Status.FAILURE: 1>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 240, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2279, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2316, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 892, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 962, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 161, in async_install
await entity.async_install_with_progress(version, backup)
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 465, in async_install_with_progress
await self.async_install(version, backup)
File "/usr/src/homeassistant/homeassistant/components/zha/update.py", line 177, in async_install
raise HomeAssistantError(f"Update was not successful - result: {results}")
homeassistant.exceptions.HomeAssistantError: Update was not successful - result: <Status.FAILURE: 1>
I’ve just installed 2024.2(.1) and all seems good. Well done to everyone who contributes.
As an added bonus, the number of items in my system log after startup is now down to an all-time record of 1!
1 Like
After the update, everything works fine. But I have one error in the log. Does anyone have a similar experience? What to do with this?
Logger: homeassistant.helpers.translation
Source: helpers/translation.py:288
First occurred: 11:05:49 (1 occurrences)
Last logged: 11:05:49
Validation of translation placeholders for localized (pl) string component.energy.issues.entity_unexpected_unit_gas_price.description failed
Never had issues with Core Updates but this time.
When i update from 2024.1.6 to 2024.2.1 all my automation just disappear.
I can still see all of them in automations.yaml but the Automations Tab is empty and automations are not working.
I really dont know how to fix that.
I have Home Assistant OS installed in Proxmox, after the update the following problems appeared:
Invalid config
The following integrations and platforms could not be set up:
* [xiaomi_airfryer](https://github.com/tsunglung/XiaomiAirFryer) ([Show logs](https://myhassioserv.duckdns.org/config/logs?filter=xiaomi_airfryer))
* [roborock](https://www.home-assistant.io/integrations/roborock) ([Show logs](https://myhassioserv.duckdns.org/config/logs?filter=roborock))
* [xiaomi_miio](https://www.home-assistant.io/integrations/xiaomi_miio) ([Show logs](https://myhassioserv.duckdns.org/config/logs?filter=xiaomi_miio))
* [xiaomi_miot](https://github.com/al-one/hass-xiaomi-miot) ([Show logs](https://myhassioserv.duckdns.org/config/logs?filter=xiaomi_miot))
Please check your config and [logs](https://myhassioserv.duckdns.org/config/logs).
Two custom integrations and two - Roborok and xiaomi_miio stopped working.
The problem is “Error occurred loading flow for integration xiaomi_miio: No module named ‘imp’”.
One of the integrations that resonates most with me is xiaomi_miio:
Logger: homeassistant.config_entries
Source: config_entries.py:2275
First occurred: 12:03:00 (3 occurrences)
Last logged: 12:12:28
Error occurred loading flow for integration xiaomi_miio: No module named 'imp'
and custom Air Fryer
Logger: homeassistant.setup
Source: setup.py:251
First occurred: 11:58:42 (4 occurrences)
Last logged: 11:58:57
Setup failed for custom integration 'xiaomi_airfryer': Unable to import component: No module named 'imp'
Setup failed for 'roborock': Unable to import component: No module named 'imp'
Setup failed for 'xiaomi_miio': Unable to import component: No module named 'imp'
Setup failed for custom integration 'xiaomi_miot': Unable to import component: No module named 'imp'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 251, in _async_setup_component
component = integration.get_component()
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 827, in get_component
ComponentProtocol, importlib.import_module(self.pkg_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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 994, in exec_module
File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
File "/config/custom_components/xiaomi_airfryer/__init__.py", line 29, in <module>
from miio import DeviceException
File "/usr/local/lib/python3.12/site-packages/miio/__init__.py", line 12, in <module>
from miio.device import Device, DeviceStatus # isort: skip
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/miio/device.py", line 13, in <module>
from .miioprotocol import MiIOProtocol
File "/usr/local/lib/python3.12/site-packages/miio/miioprotocol.py", line 13, in <module>
import construct
File "/usr/local/lib/python3.12/site-packages/construct/__init__.py", line 22, in <module>
from construct.core import *
File "/usr/local/lib/python3.12/site-packages/construct/core.py", line 3, in <module>
import struct, io, binascii, itertools, collections, pickle, sys, os, tempfile, hashlib, importlib, imp
ModuleNotFoundError: No module named 'imp'
I use Home Assistant OS and I do not have full access to Debian to solve the problem myself, I hope the developers will see my messages and this will help fix the problem.
* Core 2024.2.1
* Supervisor 2024.01.1
* Operating System 11.5
* Frontend 20240207.1
There is a section in developer tools > assist which you can use to debug that. It sounds like it used the intent to set the brightness of your lights.
If you use something light set <area> to 50 it will probably get confused with the intent to set the lights on that area to 50%
Edit:
Oh sorry, seems you already found that
just discovered that yesterday. first sentence went ok, but entering a second there hang the system…
apparently it is a costly process, might be related to Increased processor use from Assist Pipeline · Issue #110112 · home-assistant/core · GitHub
Not running on a beast of a system, but a miniPC should be decent enough. still, its crunching.
I got this in my log when I updated today:
aiohttp.client_exceptions.ClientResponseError: 429, message=‘This request has been throttled due to an excessive amount of traffic to our service.’, url=URL(‘https://app.melcloud.com/Mitsubishi.Wifi.Client/Device/Get?id=xxxxxxxxxx&buildingID=xxxxxx’)
I have inactivated the integration and will resume it tomorrow to see if it was a temporary problem.
The only issue I found with the Tuya integration is not all entities work properly. I have several fans and only the light entity works. The fan entity errors out.
Awesome new build 2024.2.x
I was wondering if more people are having this issue;
I’ve got 4 camera streams all working for over a year.
Four picture glance cards in Lovelace… Since 2024.2.x some of them don’t load / showing video. Got to refresh/f5 but really since 2024.2 downgraded/ restored backup 2024.1 and no issue. Loading then also takes card empty for a second or so but it shows up. Then updated again, and one of them again don’t shows up on first page load.
Really weird…
4 cam streams are rtsp… H264 And all were working before and seems one of them on new version struggling to show up
1 Like
Having the exact same issue. This was working previously for over a year on 5 different casted Google Hub’s around my house but now the streams are freezing entirely, do not appear or are many minutes/hours behind.
I’m going to roll back for now until this is fixed
1 Like
Has anyone had issues with Google TTS since the update? My automations are making the speakers go “splang”, but not producing any speech.
Getting the same behaviour if I open the device, Browse Media -> Text to speech -> Google and ask it to say something.
Yeah really weird…
I downgraded / restored 2024.1.x (latest) really like five times and updated to 2024.2 again… changed nothing and it’s really happening only on 2024.2
Not really much going on in logs though
Are you also using Frigate for the streams?
No I’m not using that… Look interesting though
This may be worth posting an issue on Home Assistant GitHub Core …
I came across the following:
1 Like
It’s not so much an issue of the OS, but more related to the database functionnality and if it was decided to implement free-form geometry fencing.
I would say there is a solution for the databases that are used:
- sqlite3: Spatialite extension for sqlite3
- mysql/mariadb: native geometry functionnality.
The areas can be recorded in a separate table. Circles need to be converted into consecutive segments to do spatial indexing on them as well. Once a spatial index exists, the database engine can do the job of efficiently finding the areas that contain the position.
I thing my issue with rtsp streams has to do something with updated HLS.js package used in frontend.
Issue comes up when updated to 2024.2 but only when new frontend is loaded by notification that there is a new frontend to load… Then page force refreshed by home assistant, and then issue is popping up.
Is there a way to debug hls? 
same here, going to roll back to 2024.1.6 until it gets sorted