home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.07k stars 31.09k forks source link

Integration with Home Assistant is unstable, it is not working. #129099

Open wagnerluis1987 opened 1 month ago

wagnerluis1987 commented 1 month ago

The problem

TUYA's integration with HA has been experiencing problems since yesterday, October 21, 2024. I was unable to connect (synchronize), and when I managed to connect (synchronize), the commands took more than 10 minutes to be executed and updated on the dashboard. Does anyone know if the TUAY integration with HA is experiencing problems? Everything is working normally through the SMARTLIFE app. @tuya, @zlinoliver, @frenck.

What version of Home Assistant Core has the issue?

2024.10.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tuya

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tuya

Diagnostics information

Imagem1

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 month ago

Hey there @tuya, @zlinoliver, @frenck, mind taking a look at this issue as it has been labeled with an integration (tuya) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `tuya` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tuya` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


tuya documentation tuya source (message by IssueLinks)

richard-fairthorne commented 1 month ago

Mine stopped working a few days ago.

wagnerluis1987 commented 1 month ago

Yes, it has stopped working since 10/21/2024

jon-moreira commented 1 month ago

Same issue here :(

rafaelsouzams commented 1 month ago

same problem here!!!

thos-edison commented 1 month ago

...also, no QR code appears during setup of new device. (mmWave).

visaodeempresa commented 1 month ago

Hi Guys,

I have the same problem! No new devices are added. When this problem happens I need to restart the Home Assistant.

image

rafaelsouzams commented 1 month ago

I noticed that @visaodeempresa and @wagnerluis1987 are Brazilians like me, is there any connection there? I don't know if @richard-fairthorne and @jon-moreira are Brazilian, but they could inform you to try to help find the problem.

premiero commented 1 month ago

Same here, integration stopped to work. I am not Brazillian, I come form Poland.

nathang21 commented 1 month ago

I've had luck maybe one out of every 10 times reloading the integration it would setup correctly, but then disconnect again after some delay.

visaodeempresa commented 1 month ago

Hi @rafaelsouzams and evereone,

I've encountered a rather inelegant and practical workaround. I removed the smart plug and re-registered it with Tuya Smart, then synchronised it. In this scenario it reappeared in the Home Assistant, but I lost the history of the voltage, power and current sensors. I noticed that after a recent Home Assistant update the plug-in had problems synchronising the entities when we changed their name in Tuya Smart.

The error message is still there, but at least I can add new devices, as well as recognise those with changed names in Home Assistant.

Another point of error is in the Core log in relation to Tuyalocal, because even if you disable the add-on the error continues as if the add-on were still running even though it was disabled.

Thanks Maycon

visaodeempresa commented 1 month ago

Providing more details, I have now cleared the system logs and rerun the tests, and I had the same problem. image

When I checked the logs, I got the following message

image

Looking in detail, I've seen that it fails to update entities, not recognising those whose names have been changed. Below is the old name of the kitchen temperature sensor image

image

Now the sensor has the name below and somehow it hasn't been able to link the old name and make the change as it did before

That may not be the problem, but I'd just like to share a few observations I've made

Thank you everybody and have a nice weekend! 🍺

visaodeempresa commented 1 month ago

Can anyone test a version before this change? https://github.com/home-assistant/core/pull/127399

sercada commented 1 month ago

Can anyone test a version before this change? #127399

I did test it with core 2024.10.0 and it didn't work.

wagnerluis1987 commented 1 month ago

Eu notei que@visaodeempresae@wagnerluis1987os brasileiros são como eu, existe alguma ligação aí? Não sei se@richard-fairthornee@jon-moreirasão brasileiros, mas poderiam te informar para tentar ajudar a encontrar o problema.

Sim @rafaelsouzams, sou Brasileiro... já fiz de tudo e não resolveu... até reinstalei o homeassistant do zero, reconfigurei tudo, e ainda continua com problemas.

Só pode ser problemas com a Integração da @Tuya. Pois se for dado o comando via Alexa para ligar ou desligar algo, o status na tela do HomeAssistant é alterado de imediato, mais se eu click no ícone da Luz por exemplo, ela demais quase 10 minutos para ligar ou desligar.

E só estou com problemas mesmo com a integração da @Tuya, as demias estão rodando lisas.

miguellandre commented 1 month ago

here with problems too. if you reload the integration it works but after a few minutes it doesn't do anything. and sometimes it shows this error. IMG_20241027_083008.jpg

alexandrersbr commented 1 month ago

I fixed 1 ipv6 address, instead of 3, and everything started working again.

Sem título

Tom-Bruise commented 1 month ago

US user here, with a Home Assistant Supervised VM setup. Disabling IPv6 in System > Network made the integration work again. Thanks @alexandrersbr for the nudge in the right direction!

sercada commented 1 month ago

Thanks @alexandrersbr, now we're back!

Disabling the IPv6 protocol on the network adapter makes it work back again.

Cheers,

rafaelsouzams commented 1 month ago

I disabled IPV6 here a few hours ago and for now everything is working as it should too! Thanks for the tip!

borto93 commented 1 month ago

Eu notei que@visaodeempresae@wagnerluis1987os brasileiros são como eu, existe alguma ligação aí? Não sei se@richard-fairthornee@jon-moreirasão brasileiros, mas poderiam te informar para tentar ajudar a encontrar o problema.

Sim @rafaelsouzams, sou Brasileiro... já fiz de tudo e não resolveu... até reinstalei o homeassistant do zero, reconfigurei tudo, e ainda continua com problemas.

Só pode ser problemas com a Integração da @tuya. Pois se for dado o comando via Alexa para ligar ou desligar algo, o status na tela do HomeAssistant é alterado de imediato, mais se eu click no ícone da Luz por exemplo, ela demais quase 10 minutos para ligar ou desligar.

E só estou com problemas mesmo com a integração da @tuya, as demias estão rodando lisas.

Recentemente, teve atualização do Alexa Midia Player, percebi os problemas após fazer essa atualização Fiz o lance de desabilitar o ipv6 e Funcionou normal

premiero commented 1 month ago

It's not IPv6 related, i had it always disabled and it stooped to work. I think there was some temporarily issue with tyua developper platform as it works ok now without touching anything.

miguellandre commented 1 month ago

It still doesn't work for me yet😭

YannGranger commented 1 month ago

Same here. I solved it by reloading the Tuta integration. But this only solved it for few days before stopped working again

devedsmith commented 1 month ago

We have the same issue. Reloading the integration resolves it for a few mins/hours and then in stops again. Our IPV6 is already disabled.

murph2481 commented 1 month ago

Same issue after a few hours, reloading or restarting home assistant works for a few hours. I get the same -9999999 sign invalid issue, tuya app works fine, internet connectivity and DNS work fine. I have tried disabling ipv6 and that didn't help it either

ange1us commented 1 month ago

I have a same issues but when I disable ipv6, it all work again.Thanks

linkian19 commented 1 month ago

Just adding my hat in for this issue as well. Noticed that my Tuya based lights weren't working as expected. Commands would take 10s of minutes to go through. Integration would fail to initialize often.

I followed the tip on disabling IPV6. Re-enabled the integration, restarted home assistant, and re-authed with the integration and everything seems to be working fine now.

Nothing has changed with my network or HA setup (aside from installing the updates presented to me).

Sir-Udo commented 3 weeks ago

Hier das selbe, keine Authentifizierung mit Tuya mehr möglich. Please Help

wagnerluis1987 commented 3 weeks ago

Bem pessoal, fiz conforme o amigo @alexandrersbr informou, desabilitei o IPV6 no HA e na minha placa de rede e tudo voltou a funcionar como deveria. Graças a Deus já tem quase 2 semanas que esta tudo bem. Sem mais problemas. Já reiniciei o HA varias vezes e não tive mais problemas com a integração da @tuya. Façam esse teste.

richard-fairthorne commented 3 weeks ago

Any word on this? Is anyone working on it?