From what I see on Oleok’s and zlinoliver’s “marketing postings” on that tuya thread I believe the HA devs were sweetly talked into this by tuya marketing staff promising heaven is coming down to earth and that there surely will be excellent support from the tuya support team etc. And they simply fell for those blatant lies. Now there is no going back anymore …
As for Tuya: Mission accomplished.
I have to agree with you. The silence from all involved is a little staggering.
When the HA devs gave 3 Tuya devs the first 30 mins of the release party stream to discuss and sell the new integration, I think they have to take some responsibility and be accountable. They have obviously had a fair degree of involvement in the process.
I really struggle with the fact that the HA devs didn’t make Tuya devs commit to a date for local control at a bare minimum, let alone push for to be included at the start. Perhaps they did, but this hasn’t been shared. HA is supposed to be a locally focused platform and then they go ahead and push out a major and completely cloud based integration, happily.
If the timeline for shutting down the old API is at least 6 months, as shared in the live stream by the Tuya devs, there was no need to push out an updated integration that is less capable than the one is was replacing.
Beggars belief.
If the fuel injection pump of my Mercedes is broken I’ll ask Mercedes for repair, not Bosch.
And as for Tuya: They simply give a s**t on the frustration of the little (HA-)user base. User data is all that counts.
Well it seems some, not all of the issues on github have been given some response from a tuya dev, mainly to tell them it isnt supported and will be added in a future update or asking them to help build the driver
slow start
This gets my goat. So the Tuya devs don’t know how their system works? Astounding. One wonders how much time they have spent on this project.
What I don’t quite understand is why the built-in one is not on par with the V2 they put on HACS, tbh.
I have a single tuya device, a smoke detector. It works on V2 but not on built-in with the same account.
yeah is bizarre, and yet i saw a PR sitting there that re-enables dimmer support that was supported in the previous version and the dev was told it wont be merged until next months version of HA as its a new feature in this borked version.
The situation with this Tuya integration is a mess, People updated and have less functionality with a new improved integration than the previous one.
I think some people may be right and that HA have been a bit naïve with their Tuya friends and been a bit to hasty in allowing this integration in, not just for the local control but it being a worse experience for those HA community members who use Tuya devices
If this were a truly open platform the correspondence with tuya would be released.
Damn, forget about local control. I will NEVER be supported.
Agreed. Not sure what they had in mind releasing the integration in this state.
I’m totally sure it’s not naivety, though, as they knew some pieces were missing.
Maybe a case where rules overrule common sense 
I am starting to think you are being generous (or perhaps diplomatic).
As I said in another post I have no Tuya but this whole episode leaves a very nasty taste in my mouth. Ever since I started with HA 4(?) years ago I was surprised at the ‘focus’ on Google and Amazon but this is on another level.
As far as Tuya local control goes I watched the bit of the launch party linked to by tom_l in another post and saw Frenck shrug off the fact that this most important of all features was missing with words to the effect of, ‘So that is not a no. It might be coming in the future we just don’t know when’.
That means he either was surprised it wasn’t here now, which would in itself be surprising and surely impossible seeing as where Frenck sits in the HA organisation, or he knew and was simply placating the viewers. Which begs the question, why?
This is starting to smell very much of greased palms. If I were a cynical betting man, and I’m not either of those things, I could imagine believing there is an exit strategy formulating in the minds of those in control of HA.
Just to be clear, I am a huge supporter of HA, I use Nabu Casa when I don’t need to (blah blah) and I still trust the ‘vision’, but this has concerned me.
Sale to Tuya?
Not sure if sale to Tuya, possibly a monetary contribution to Nabu Casa per new signup via Tuya integration?
All speculation I guess, but the radio silence from them doesn’t help. Maybe they know they stuffed up and hoping it will just did down, who knows
That was about “official” local tuya, IIRC, not about missing features at all.
And guys, do not start semi-delirious conspiracy theory out of a borked release, please 
Ok, if I misunderstood I take that back.
I didn’t mean too, I am just stating my opinion which is that of concern, not panic. I really want to be very, very wrong.
Borked is one thing, borked by an outside party (with lots of money, influence, clout - call it what you will) who was invited in, is something else.
Where did you get they were “invited”?
Not saying it’s not the case but I like facts. Without evidence, I’ll just assume Tuya decided they wanted their V2 to be first-class citizen, in Core.
So invited they were.
Lol. That makes it even more ridiculous to invite them in, then only release part of what they wanted them to include 
I would be Tuya, I would be infuriated by the bad buzz that it’s provoking, and I wouldn’t be keen to assist any further, tbh.
Same could be said for the HA team
Why? I understand it’s the HA team that postponed part of the features, making the current one half-assed.
Am I wrong?
