[Tuya] [TuyaOpenAPI] Network error: . Retrying...

[bunbunpig]

Prerequisite

• Yes

Accounts

• Yes

Country Code

1

Region Code

AZ (West US)

Logs

[18/11/2024, 2:00:40 am] [Tuya] Child bridge process ended
[18/11/2024, 2:00:40 am] [Tuya] Process Ended. Code: 1, Signal: null
[18/11/2024, 2:00:47 am] [Tuya] Restarting Process...
[18/11/2024, 2:00:48 am] [Tuya] Launched child bridge with PID 150945
[18/11/2024, 2:00:49 am] Registering platform '@0x5e/homebridge-tuya-platform.TuyaPlatform'
[18/11/2024, 2:00:49 am] [Tuya] Loaded @0x5e/homebridge-tuya-platform v1.7.0-beta.54 child bridge successfully
[18/11/2024, 2:00:49 am] Loaded 18 cached accessories from cachedAccessories.0E5E91BC96A1.
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: Zigbee无线网关
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 人体红外传感器
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 廳燈
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 四鍵無線情景開關（Zigbee）
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: WifiSmartLock
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 萬用IR遙控器 2
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: Zigbee中繼器
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 萬用IR遙控器
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 廚房燈
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 六键无线开关-Zigbee
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: SMARTLIGHT
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: Zigbee门磁
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 双键开关
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 暖爐
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: Powerful button
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: 風扇
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: Living Room Air Condition
[18/11/2024, 2:00:49 am] [Tuya] Loading accessory from cache: Second Air
[18/11/2024, 2:00:49 am] [Tuya] Log in to Tuya Cloud.
[18/11/2024, 2:00:49 am] [Tuya] [TuyaOpenAPI] Login to: https://openapi.tuyaus.com
[18/11/2024, 2:00:49 am] [Tuya] [TuyaOpenAPI] Request:
method = post
endpoint = https://openapi.tuyaus.com
path = /v1.0/iot-01/associated-users/actions/authorized-login
query = null
headers = {
  "t": "1731866449666",
  "client_id": "********************",
  "nonce": "cad744cb-5499-4955-b721-a4f74a7502b9",
  "Signature-Headers": "client_id",
  "sign": "F347E39686E3CA429AF4B691DCFEF4D1FFE9885D432D5A71AFE7EE26483FD0F1",
  "sign_method": "HMAC-SHA256",
  "access_token": "",
  "lang": "en",
  "dev_lang": "javascript",
  "dev_channel": "homebridge",
  "devVersion": "1.7.0-beta.54"
}
body = {
  "country_code": 1,
  "username": "********@****.com",
  "password": "****************************",
  "schema": "tuyaSmart"
}
[18/11/2024, 2:00:49 am] Homebridge v1.8.5 (HAP v0.12.3) (Tuya) is running on port 38948.
[18/11/2024, 2:00:49 am] 

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[18/11/2024, 2:00:50 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
[18/11/2024, 2:00:51 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
[18/11/2024, 2:00:52 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
[18/11/2024, 2:00:53 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
[18/11/2024, 2:00:55 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
[18/11/2024, 2:00:58 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
[18/11/2024, 2:01:02 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
[18/11/2024, 2:01:09 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
[18/11/2024, 2:01:23 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
[18/11/2024, 2:01:49 am] [Tuya] [TuyaOpenAPI] Network error: . Retrying...
AggregateError: 
    at internalConnectMultiple (node:net:1118:18)
    at internalConnectMultiple (node:net:1186:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1712:5)
    at listOnTimeout (node:internal/timers:583:11)
    at processTimers (node:internal/timers:519:7)

Other Infomations

No response

[samralck]

Same issue started for me today. Tried uninstalling, reconfiguring, and no luck.

Central European server, located in aus.

[jadonbaker]

ping openapi.tuyaeu.com
PING openapi.tuyaeu.com (3.69.78.245): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
^C
--- openapi.tuyaeu.com ping statistics ---
6 packets transmitted, 0 packets received, 100.0% packet loss

[jadonbaker]

ping openapi.tuyaus.com
PING openapi.tuyaus.com (44.224.48.198): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
^C
--- openapi.tuyaus.com ping statistics ---
7 packets transmitted, 0 packets received, 100.0% packet loss

Same for your region

[amybiyuliu]

Same issue is happening for the EU data center.

[jadonbaker]

@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.

[fuhckos-98]

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.

#208

[bradleyayers]

I'm also experiencing this issue, I'm also in Australia.

[chewbanger]

Hey I fixed mine.

I think this is what fixed it… I tried a few things prior to this also. Like updating node js.
I went into the config and disabled IPv6

Goto terminal
Type sudo hb-config
Enter your password
Go in to network menu and edit the wired connection
Disabled IPv6
Restart homebridge server
Type sudo reboot

[fuhckos-98]

Hey @chewbanger - I just tried this and unfortunately it didn't work for me

[chewbanger]

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.

[fuhckos-98]

Just gave that a try and still didn't work - hopefully something changes soon

[mynameisbrendan]

Same issue for me has recently started, also located in Australia

[chewbanger]

Try unlinking your tuya account from the iot project, then link it back again. There restart HB

[fuhckos-98]

Still not working after trying that, still getting a network error

[mynameisbrendan]

Try unlinking your tuya account from the iot project, then link it back again. There restart HB

I am not sure where in the Dev Platform i do this? Is it from the project page?

[chewbanger]

@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.

[mynameisbrendan]

@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.

[emzpasha]

@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.

[chewbanger]

@emzpasha Ah great! Yes, should have clarified, restart whole server not Homebridge service. :)

[bradleyayers]

Disabling IPv6 worked for me too.

sudo hb-config
# disable IPv6 networking
sudo reboot

[fuhckos-98]

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.
I should note that my Homebridge is setup on a RPi with a wireless connection so I needed to change the network settings for my wireless connection, not the wired.

[andrewastley85]

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.

[jadonbaker]

I've disabled IPv6 and can also confirm that the plugin works again. Make sure you reboot after making the change.
Thank you to everyone in this thread for solving this problem.

[VioletArcade]

I’m also experiencing this issue on macOS. Should I disable IPv6 in the system settings?

[mynameisbrendan]

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.

[bobsmith523]

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?

[bunbunpig]

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: ***@***.***>

[mynameisbrendan]

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?

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?

[bobsmith523]

How did you change the network interface? Is that using hb-config? I tried that but it said command not found.

[mynameisbrendan]

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.

[chrisltft]

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.

[luxxed]

How did you change the network interface? Is that using hb-config? I tried that but it said command not found.

If you're using a raspberry pi, you can change it globally to removed IPv6 which worked for me instantly.