i said, you can use the old tuya folder and load it as custom
Yes you can do that but someone has already done it. Itâs in hacs
was the previous tuyav1 release local control? i thought only localtuya was really local
Ok i will give it a try again with hacs. thank you
No clue, donât have tuya. From what I understand about the situation is that tuya is removing the old api and adding a new one that doesnât have local control currently. But I could be wrong.
The old had a classification of cloud_poll, the new have cloud_push
Glad to see the Kasa-python integration now and that thee devices are getting love. However, any lights that are part of a dimmer HS2xx donât turn on anymore with the light_on nor through scenes for example. They need to be turned on manually then theyâll adjust brightness to a scene. i had to roll back as well.
1 Like
Mine did this too. Its an easy fix though. Just remove the ones without the â_2â (duplicates from the old integration) and then in the entities, you can rename the â_2â to the original by removing the _2. I still had to roll back but I was able to fix this in a few minutes for 26 devices.
1 Like
Direct after update⌠whatâs this about?
Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:324
Integration: Sensor (documentation, issues)
First occurred: 14:35:10 (1 occurrences)
Last logged: 14:35:10
Entity sensor.relay_2_energy_4 from integration esphome has state class total_increasing, but its state is negative. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+esphome%22
only the localtuya integration provided local control no other past or present tuya integration did
1 Like
Iâm getting the same message when entering the encryption key.
I just re-added one of my zwave nodes to test. The wizard showed that my device supports both S0 and S2. When I added it, all seems okay. But is there any way to see that it is actually using S2 in favor of S0? It just says âSecure: Yesâ
Yes - Over 3k errors so far!
I updated HA to the latest version and I configured Tuya with its Tuya IoT Platform. I have 2 Thermostats linked through the SmartLife App which shows this (On Tuya IoT Platform and on HA). Obviously I donât have 3°C at Home. Moreover, I cannot switch on/off from HA (I donât know from Tuya Iot Platform), whilst itâs perfectly working from SmartLife.
Translated they lied to us.
just searched for my statistics (integration) sensors in the Statistics tab and lovelace statistics-graph cardâŚ
only to find:
and Statistics - Home Assistant doesnt say we can set the appropriate device_class or state_classâŚ
Happening with all tuya devices in home assistant.
With the entity card you can get it to turn off by clicking it off and then doing so again before it can flip back to on. The device will go off but still show as on in HA .
Seems the reporting and on screen control are broken in this version although they did get the light bulb colours correct lol.
Otherwise node-red and routines seem to function normally.
I would expect a very quick update to address this rather large bug as it breaks too much .
So, my TP-Link devices would regularly become unavailable (just one or two here and there) requiring me to reload the integration. There does not seem to be a way to do that now. How do we get a device reloaded if/when it drops?
1 Like
I have no axe to grind regarding Tuya in particular as I donât use it but these quotes seem somewhat incongruous to me considering the HA ethos.
Such a big fanfare for a third party (developed) integration that appears from what I have read here to not have been particularly well received.
If it werenât Home Assistant who I (still) trust it would conjure up images of some kind of backroom deal.
Just sayingâŚ