The wanted to change out the api to have more security and control and used the idea of local control to get people to test it and point out problems.
This was likely about money and greed rather then working with the community to improve things for the buyers/users.
I would suspect local tuya going to get blocked soon as all they need do is block access to the local keys which is simple to do on their end.
Sadly HA catching lot of flak for this but they are not totally innocent either.
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.
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.
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.
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?
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.
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.
It seems as though the naming should be have been updated/changed to reflect the difference to avoid confusion.
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.
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.
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?
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
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.
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.
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??)
