2021.10.0: Z-Wave S2 support, Tuya, secure ESPHome and 400 new icons

[Magnus33 (Eric)]

They got what they wanted and left sadly.

[mftas]

I think that’s a naive view.

Tuya don’t need HA for anything. We’re a drop in the ocean in terms of consumers of their technology. They could have turned off the API we use tomorrow and 99.98% of users of their tech would never notice.

Don’t get me wrong, I think the process is totally botched, and after the outage and issues earlier in the week, I now consider Tuya too unreliable to put in my home until there is an easier way to do local integration and there is some sort of reassurance that the local control integration is not about to be sabotaged.

[Magnus33 (Eric)]

Look at the evidence first.

Tuya could not merely turn off the api as they need a replacement or they piss of a lot of people and more then a few companies.

What better way to get free testing and insure they get more control then to use people to test the product by promising something they never intended to deliver to get people to do the testing for them.

They already said now they have no plans for local tuya and all dev have no gone radio silent.

All evidence and behaviour points to this being the intended outcome from the start.

Given that they now have a more secure api and more control it likely they are now going to block other methods around there app.

I dealt with enough companies like apple to know that it what they want and as long as it doesn’t effect their bottom line they do what they want because they know they can.

i hope i am wrong but given their behaviour it seems like it a accurate assessment.

[ronbuist]

I’ve had the same issue. After reading the error messages, I managed to resolve this one for now by doing:

export CRYPTOGRAPHY_DONT_BUILD_RUST=1

And then doing the upgrade of home assistant. I’m saying “for now” because this method will no longer work when a newer version of cryptography is needed for home assistant.

[Magnus33 (Eric)]

Also if anymore evidence was needed posts in the github are being closed as soon as they are added.

That’s a intentional action and not merely ignoring or can’t respond which would possibly be explainable.

[rcblackwell (Robert Blackwell)]

@calisro

any lights that are part of a dimmer HS2xx don’t turn on anymore with the light_on nor through scenes for example.

I’m experiencing the same issue. I can control the switch off/on/dimming using it’s control but not via turn_on, scene, script or through a Node-Red call. Has anyone filed a bug report yet?

[keystone16]

Same here. I’ve created an issue.

With the 2021.10.0, only 5 of my 28 TP-Link Kasa HS105 & HS200 devices can be connected. The HS110’s are all found.

I’m reverting back to 2021.9.7 until this can be resolved.

[ManInSoho]

I doubt that there will ever be an official local API to Tuya.

Selling cheap hardware and a cloud service for free is just not sustainable. They are not Amazon or Google, they will need to make money.
I guess spending programming resources to Home Assistant just helps them to get more devices in the market and at some point they will charge for the cloud service in form of subscriptions or quotas.

If they are kind, it would only affect heavy users, but for the moment it is probably better to stay cautious and not buy any more devices.

[nickrout]

Weird that Tuya V2 custom component was the beta for what is now in core, yet the two of them are incompatible “and HA does not support custom components.”

So moving on from helping with the beta by installing Tuya V2, people are faced with a sudden need to disable V2, and the devs disavowing all responsibility for the beta being incompatible.

Wow.

[Eoin]

@teprrr

Yes, you can add devices one by one using their IP addresses.

I can see how you add the IP of a new device, however how do you edit the IP of an existing device?

[kanga_who (Jason)]

@nickrout

Come on, this is a major change in Tuya integration and no sign of any support.

@aidbish

not one Tuya dev has popped up to try and help people.

The silence is deafening.

@aidbish

People logging issues on the HA github have them closed off as soon as they mention they had the old other v2 integration as its a custom integration. These peopleas were many were under the impression the v2 there is what was in the core.

It seems as though the naming should be have been updated/changed to reflect the difference to avoid confusion.

@mftas

I’m prepared to give them more than 4 days.

If they had the time to go on a live stream and bang on about all the hard work they’ve been doing and how great the new integration is, they have time to be on the forums and helping resolve problems.

Not a single Tuya Dev has responded to anyone in this thread. The Tuya devs knew exactly when this was going live and should have expected problems, yet have provided no support or at the very least a “sorry, we are working on some fixes”.

I would have thought that if HA was going to allow an external company to write and maintain a new integration, they would also expect a certain level of support be provided by that company to users and for that integration to support the same number of devices that the replaced integration supported.

Poor form.

[Magnus33 (Eric)]

Agreed the silence is deafening.

Hopefully they are aware and are working like crazy to fix it before saying anything.

More likely though is they got what they want and are laughing themselves silly.

Here hoping for the former and fearing it’s likely the later.

[aidbish (Adrian)]

The Tuya/HA integration Dev/support office after shipping in 2021.10

[Eddie46848 (Eddie)]

Hi
Energy dashboard now allows you to select gas as kWh, but when you go to select a static price for monitoring cost. It asks you for the m3 price per unit.
Is this correct?
Surely we should be able to put the price per kWh.

[Speedtriple]

That will solve it yes. I see every major HA update may demand updated WS-server. I have now moved to MQTT instead for Zwave-over-IP. Will this be more redundant with regard to HA-updates?

[raman325]

I think you are referring to zwave_js over MQTT. MQTT as a platform won’t change, so it won’t change as often as the websocket integration. But I don’t understand why updating the server is too much to ask for? The zwave-js and HA integration are moving quickly from release to release, I don’t think it’s a lot to ask for to be on the latest version for each HA update. You certainly won’t get all of the benefits from the integration if you are using MQTT to control your devices

[Speedtriple]

Ok, I then understand it that WS-server approach is “better” than MQTT and should be the preferred way of using Zwavejs2MQTT from an external RPi3.
No, it is not a lot to ask for updating the docker conatiner etc, I just did not know until reading this thread.

[santirguez]

Strange then, I added all again, and now they are reporting device_class: power instead of energy

[DavyRoswinkel]

Got only 2 weird issues:

1. Some lights ( Z2M) are not showing the status icon in a correct way. Off it shows the blue icon, when on yellow is expected but there is no icon at all.

2. Most weird issue! The entity person.name is looking good when looking in the developertools, but when using it with a badge in lovelace it shows a moustache and a dot ( on the nose) Really I’m not joking!
   ( I know what this is…it’s the person icon showing over the avatar) ( maybe because i’m using a png??)

[nickrout]

What devices are you talking about.

Some Shelly devices have entities that are disabled by default.

For heavens sake give us more info!