-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tuya] [TuyaOpenAPI] Network error: . Retrying... #508
Comments
Same issue started for me today. Tried uninstalling, reconfiguring, and no luck. Central European server, located in aus. |
|
Same for your region |
Same issue is happening for the EU data center. |
@amybiyuliu have you found any resolution? I tried using a different data center and testing with an incorrect username and password and I'm getting the right authentication failure response. With EU data center there is no network response. |
I read an earlier thread that said this happened to them (months ago) and it was a network issue with Tuya I believe... Unfortunately I think this might be one of those wait for it to sort itself out situations. |
I'm also experiencing this issue, I'm also in Australia. |
Hey I fixed mine. I think this is what fixed it… I tried a few things prior to this also. Like updating node js. Goto terminal |
Hey @chewbanger - I just tried this and unfortunately it didn't work for me |
Hey @fuhckos-98 damn… before disabling IPV6, i did also update the hb-config tool - it’s one of the menu options in hb-config. |
Just gave that a try and still didn't work - hopefully something changes soon |
Same issue for me has recently started, also located in Australia |
Try unlinking your tuya account from the iot project, then link it back again. There restart HB |
Still not working after trying that, still getting a network error |
I am not sure where in the Dev Platform i do this? Is it from the project page? |
@mynameisbrendan Click on Cloud open your project, click Devices tab, Link App Account. Mine stopped working for a couple of days, I tried all these things I have mentioned above ... so difficult to tell which particular thing fixed it. Working now though. |
Thanks, unfortunately that hasn't fixed it for me. |
@chewbanger Disabling IPV6 fixed this discovery for me after I had to restart the whole HB Server, not just the HB service. However, just moments later, it keeps throwing the error again and Hombridge keeps restarting. so, couldn't fix still. |
@emzpasha Ah great! Yes, should have clarified, restart whole server not Homebridge service. :) |
Disabling IPv6 worked for me too.
|
Thanks, disabling IPv6 has now worked for me. I was only restarting the service not doing a full reboot, I'll report back if anything changes. |
Disabling IPV6 also fixed this for my setup. I am using an Orangepi Zero (some regrets) but incase anyone else is in the same boat you need to switch the terminal user using the switch user command "su", then use the "nmtui" command to change the netwok settings. Reboot and all is back to normal. |
I've disabled IPv6 and can also confirm that the plugin works again. Make sure you reboot after making the change. |
I’m also experiencing this issue on macOS. Should I disable IPv6 in the system settings? |
I already had IP6 disabled on my Synology container network when I got this issue. Not sure what action resolved it, but I think it was when I updated the available network interfaces in my Homebridge UI to only the local lan eth0. It may have just been the restart of the synology NAS that resolved it also. |
I'm running homebridge on docker and have tried running the container on a network I've created with IPv6 disabled (docker network create --ipv6=false disable_ipv6) but this hasn't seemed to fix the issue. In the UI I can see an IPV6 address is still assigned. Any ideas? |
There some problems with tuya api, no choice, we have wait until it resume
normal.
…On Wed, Dec 18, 2024 at 18:56 bobsmith523 ***@***.***> wrote:
I'm running homebridge on docker and have tried running the container on a
network I've created with IPv6 disabled (docker network create --ipv6=false
disable_ipv6) but this hasn't seemed to fix the issue. In the UI I can see
an IPV6 address is still assigned. Any ideas?
—
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AODMFLYIL7FWDFQRONR5HTT2GFIGJAVCNFSM6AAAAABR6FUQV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJRGAYDSMZYHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This is the same setup as me. I went into the setting in my Homebridge UI and selected the network interface I want (it was on auto before) then rebooted my parent docker server. No idea what change fixed it, but its now working. Maybe just try restarting your docker server? |
How did you change the network interface? Is that using hb-config? I tried that but it said command not found. |
In the homebridge UI. Settings > Network Interfaces. |
I am also in Australia, connecting via https://openapi.tuyaeu.com, getting the exact same errors as the OP continuously. I am using docker on hyper-v, it worked fine until a few weeks ago. I have tried everything listed here (except waiting longer) but nothing is working. I am now looking into Tuya alternatives since it is fully dead in the water at this point. |
If you're using a raspberry pi, you can change it globally to removed IPv6 which worked for me instantly. |
I'm running homebridge on a Ubuntu machine, disabling ipv6 worked well for me |
Mine is working now too, I am not sure what of the thousand things I did that helped. I removed the plugin, updated as many things in my Hyper-V docker as I could work out how to do, re-installed and re-setup the plugin from scratch. It has nicer icons and stuff now so something has definitely changed. Then finally I added the following lines to the homebridge web interface: settings -> startup script (inspired by Amy's comment above): sysctl -w net.ipv6.conf.all.disable_ipv6=1 Theoretically this should kill any attempt to use ipv6 right where I need it killed. I noticed that Hyper-V kept turning ipv6 back on in its windows network connections vethernet (default switch), no matter how many times I tried to remove it. Anyway I am happy now. Good luck to everyone else still struggling with this |
Prerequisite
Accounts
Country Code
1
Region Code
AZ (West US)
Logs
Other Infomations
No response
The text was updated successfully, but these errors were encountered: