yes! thank you so much! Ive been looking for this for agesâŠ
I found that my TP-Link lights that were unavailable after the upgrade had a new entity id with [old entity id]_2. Check your entities, that may have happened to you as well. And of course, update any automations, light groups, etc. that may have used the old entity id.
1 Like
After upgrading the homeassistant core, the load on the cpu has increased significantly. There is nothing in the logs, everything works correctly, but the load average is around 1.3 (normally on my raspberry pi 4 it is around 0.2). I uninstalled the only custom component I was using (Overkiz). I canât figure out which HA operation in particular is occupying the CPU. I tried rebooting from a clean DB, but nothing has changed.
I use this integrations:
fritz!wlan
homekit controller
Daikin AC
Google Cast
Hacs
IPP
Kodi
Mosquitto Broker
Nest
Nmap
Philips Hue
Shelly
Sony Bravia
certificate expiration
waze
twinkly
wled
xiaomi miio
yeelight
Iâve tried to rollback to 2021.09.7, load average is 0.2, but all long term statistics disappeared
1 Like
Not sure if they are the same but there is a breaking change for tp-link kasa smart integration
Using MSSQL, getting this immediately after upgrading. I did it twice, so rolling back.
Logger: homeassistant.components.recorder
Source: components/recorder/util.py:116
Integration: Recorder (documentation, issues)
First occurred: 18:11:45 (1 occurrences)
Last logged: 18:11:45
Database error during schema migration
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1771, in _execute_context
self.dialect.do_execute(
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 717, in do_execute
cursor.execute(statement, parameters)
pyodbc.ProgrammingError: ('42000', "[42000] [FreeTDS][SQL Server]Incorrect syntax near '0'. (102) (SQLExecDirectW)")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/recorder/__init__.py", line 735, in _migrate_schema_and_setup_run
migration.migrate_schema(self, current_version)
File "/usr/src/homeassistant/homeassistant/components/recorder/migration.py", line 77, in migrate_schema
_apply_update(instance, session, new_version, current_version)
File "/usr/src/homeassistant/homeassistant/components/recorder/migration.py", line 562, in _apply_update
sum_statistics = get_metadata_with_session(
File "/usr/src/homeassistant/homeassistant/components/recorder/statistics.py", line 402, in get_metadata_with_session
result = execute(baked_query(session).params(statistic_ids=statistic_ids))
File "/usr/src/homeassistant/homeassistant/components/recorder/util.py", line 116, in execute
result = list(qry)
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/ext/baked.py", line 382, in __iter__
return self._iter().__iter__()
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/ext/baked.py", line 412, in _iter
result = self.session.execute(
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 1689, in execute
result = conn._execute_20(statement, params or {}, execution_options)
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1583, in _execute_20
return meth(self, args_10style, kwargs_10style, execution_options)
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/sql/elements.py", line 323, in _execute_on_connection
return connection._execute_clauseelement(
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1452, in _execute_clauseelement
ret = self._execute_context(
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1814, in _execute_context
self._handle_dbapi_exception(
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1995, in _handle_dbapi_exception
util.raise_(
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 207, in raise_
raise exception
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1771, in _execute_context
self.dialect.do_execute(
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 717, in do_execute
cursor.execute(statement, parameters)
sqlalchemy.exc.ProgrammingError: (pyodbc.ProgrammingError) ('42000', "[42000] [FreeTDS][SQL Server]Incorrect syntax near '0'. (102) (SQLExecDirectW)")
[SQL: SELECT statistics_meta.id AS statistics_meta_id, statistics_meta.statistic_id AS statistics_meta_statistic_id, statistics_meta.unit_of_measurement AS statistics_meta_unit_of_measurement, statistics_meta.has_mean AS statistics_meta_has_mean, statistics_meta.has_sum AS statistics_meta_has_sum
FROM statistics_meta
WHERE statistics_meta.has_sum IS NOT 0]
(Background on this error at: https://sqlalche.me/e/14/f405)
Tuya V2 is unreliable as it requires a connection to Tuya cloud servers, and devices running on it were unavailable for several hours earlier this week. They had to all be manually reset once the outage was over before Home Assistant could interact with them again. No word yet from Tuya on the active bugs related to this on the repo.
I feel like this integration is fundamentally at odds with the motivation that many users of Home Assistant had in the first place: to retain control of their devices, PRECISELY to prevent outages like this from making our smart homes come to a stop.
Are there any plans to remedy this longer-term? If not, I feel that we are about as exposed to Tuya whims as we are to TP-Link Kasa whims, yet the latter has an active alert warning users it may not be safe to use it.
5 Likes
Same. I lost these as well. I used these all the time.
kib_s_received
kib_s_sent
Same error on my side using MSSQL. Syntax error⊠should be
WHERE statistics_meta.has_sum <> 0
instead of
WHERE statistics_meta.has_sum IS NOT 0
i would add your issue here as it seems it known about. Schema migration error when upgrading to 2021.10 from 2021.9.7 using MSSQL · Issue #57194 · home-assistant/core (github.com)
Seems like it should be fixed in next update
Thanks! That was the case with mine as well.
The migration tool was only added in HA 2021.10 so yes you need to update first.
This new Tuya integration is totally broken for me and. All my Tuya stuff worked fine before. I uninstalled my Tuya integration before updating, updated, configured the new Tuya integration according to the instructions. My devices (smart plugs) was added to HA, but when I try to toggle the switch, the device toggles but the state doesnât change in HA. And it only works once the freezes up. When I restart HA, it now recognizes the new sate, but again I can only toggle it once the it freezes up. So completely broken and unusable. The fact that I could connect and pull my devices suggest I did my setting up rightâŠ
Also, a few weeks ago I bought Tuya compatible door and motion sensors. I just assumed it was supported by HA since my other Tuya stuff worked so well. But yeah it did not work, turned out they werenât supported. Now with all this talk about all âall Tuya devices will be supportedâ I thought they would be pulled into HA but they werenât, only my smart plugs. DisappointingâŠ
1 Like
Question. Why doesnât the new TUYA api support Covers. The old one did. Did the code just get missed in the new intergration??? I now have entities missing because the âCoversâ (Curtains and Garage Roller) No longer exist.
Okay, so itâs at least a few of us affected.
Is this worthy enough to be reported as an issue? I guess itâs not that widespread because isnât everyone else checking network traffic constantly like I am? 
1 Like
Have you tried this? Z-Wave JS - Home Assistant
Mine worked after re-formating the key as described there.
Exactly.
It seems odd to me that the HA devs have actively invited Tuya to develop and maintain a cloud solution when the entire point of HA is to not be cloud based. I would have thought they would have insisted on a local solution before releasing. 
11 Likes
While i agree that the Tuya integration goes against the principles of HA. The problem is as long as the integration meets the development spec it can be included like other integrations, otherwise we would have a lot of integrations that are cloud based not included by default because there is no local solution (which probably isnt a bad idea).
1 Like
Before upgrade I could see 11 tuya devices. After upgrade lost all tuya devices, then re-configures tuya integration and now⊠only 4 devices are available to control.
This is the worst upgrade ever!
Iâm using tuya local which has always worked well,hopefully will continue once I upgrade.
Certainly worth a look if you donât want to use the cloud api.
2 Likes
I agree. The shear quantity of Tuya devices available worldwide is massive and now that they have an official integration, why would they even bother to then allow full local control? They have already won by getting HA users to connect to their cloud.
4 Likes