Crazy that they did this hard cutover without even feature parity.
This differs from many other integration changes like Z-wave where you could migrate when you were ready. If you upgrade to 2021.10 you WILL lose support for Tuya covers as well as other Tuya devices people have posted about.
Iām really disappointed in this decision to push an āupgradeā with reduced functionality and no transition period.
Also the release notes do a poor job of highlighting this limitation. It says Tuya is now V2 with the need to setup again but doesnāt mention the removal of the Tuya V1 integration explicitly.
Iāve been testing the v2 trough HACS since the beginning and itās been much better (than v1) and easier to setup (than Local Tuya) and Iāll keep using the HACS version while the native integration gets up to speed.
So it was weird to see this released and the fact that itās quite different from what is available through HACS, but I believe itāll be just some bumps on the road as the tuya devs learn how to work with HA (Some PRs had over a hundred comments and dozen of changes before getting merged). Now, if people will āforgiveā that or not, hard to say.
I didnāt watch the live stream yet, was basing myself by the info on the initial GitHub PR so this information makes it even weirder to launch without complete feature parity.
Paulus says in the live stream @25:22 that, āLocal is not planned right nowā¦no schedule for when a local API will come availableā. Disappointing.
For those that are having issues with the new Tuya integration in 2021.10 I found a reddit post where someone has created a HACS custom component from the 2021.9.7 Tuya integration to allow it to work in 2021.10. I will be testing later this evening but hereās the link: https://github.com/andrey-yantsen/home-assistant-tuya-old
EDIT: Have now tested this and it seems to work fine
So now we have Tuya - old edition, Tuya v2 - new and improved edition but less device support, Tuya V2 HACS edition, (different to core but presumed by everyone to be the same) and local tuya.
However it should be noted this is not available in 2021.10 without custom installation from HACS.
If you upgrade to 2021.10, by default, you only have āTuya v2 - new and improved edition but less device supportā and will lose the ability to control covers, regardless of if you had covers working with the existing Tuya integration on 2021.9.7
Poor experience.
Iāve created an issue to track this on the async_upnp_client repo. It is due to the ssdp component searching for devices on your network (once per minute), and one (or more) of the devices responding in an unexpected way.
Iām fine with having an official Tuya integration that requires the cloud. But leave the original FOSS Tuya integration there as well. Let us choose which one we want to use.
Fortunately, everything worked for me once I set up the API and edited all my dashboards.
Anyone else does have issues with ESPhome encryption? I did add it to my device and the reconfiguration message shows in HA but adding the key to the integration somewhat does not work. I always get an āCanāt connect to ESP. Please make sure your YAML file contains an āapi:ā line.ā error message and cannot connect encrypted whatsoever.
Last reset missing
The following entities have state class 'measurement' but 'last_reset' is missing:
sensor.gasverbrauch
It worked fine before. Also when manually editing these attributes to the sensor system complains that the unit ao measurement is wrong but it is not. Itās definitely set to mĀ³ which should work fineā¦ but somehow does not. Anyone else has similar problems?
This new Tuya integration is an interesting subject. Tuya generally has a weird tier based device model. They produce devices for hundreds of brands as a white label producer, but each brand has to define what tier (level of integration) they are paying for.
SmartThings does an integration model where the producer has to provide and maintain the code for the integration. The first Tuya brand was Globe Suite which was integrated to SmartThings. You could add Globe Suite devices to the original Tuya branded app and control them there, or add other (Tuya) branded devices to the Globe Suite app (skinned Tuya app) and control them.
But when the Globe Suite integration was added to SmartThings, it has turned out that only the Globe Suite branded devices were pulled from the API to the SmartThings system. Of course later on Tuya released a Tuya branded integration for SmartThings as well, but that doesnāt change the fact how it was visible where it works. The Tuya app provides a tab somewhere at the device level where you can see what services the devices works with, Google Home, Amazon Alexa, SmartThings, etc.
All of these integrations are separate tiers of the Tuya solution. Why wouldnāt be, pay for the code and server use as part of tier, and build it into the price of the device what you sell, easy enough.
It was a bit of similar story when Tuya was pulling out from the IFTTT integration, as they were not intended to pay for it. It was before IFTTT introduced their user payment model in 2020. Only one, as I can remember, some Australian skinned Tuya app was left which had the option to connect your devices with IFTTT.
I am just wondering where it will go with this Tuya maintained integration. Will Tuya introduce a tier for the Home Assistant integration where brands have to pay for that to be part of their product. Or is it even existing already and thatās why some people cannot see devices added as before.
I was never really a big fun of Tuya and their model. The cloud based overhead kills the device and leaves the buyer vulnerable to when a device will reach End Of Life or the cloud been shut down, firmware not updated etcā¦ I prefer more any Zigbee device, as this is a general issue with any WiFi based product, if it hasnāt got any local control. But that is part of Tuyaās model as well.
I have only two Tuya/DSC devices what I have never connected to any WiFi networks or wasnāt able to reflash as they donāt use ESP chips or not supported by Tasmota. I would love to use them locally, but I think more and more that they were just a wrong purchase years ago.
