-
-
Notifications
You must be signed in to change notification settings - Fork 333
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
Error with tuya-cli link-wizard #51
Comments
As a quick fix, add "broadcasthost" with your local broadcast IP to your hosts file. Dirty, i know. |
Hey, that seems to work. Error: Timed out wating for device(s) to connect to cloud I am not sure, if I configured the tuya api correctly. I got both keys but I have not configured anything else in the portal. |
The broadcast IP you gave is right, assuming you have the network IP 192.168.0.xxx. |
Hey @moritzK (and anyone else who's getting this), sorry about the broadcast error. I'm pretty busy the next few days, but I'll try to look at it soon. I've only tried running @tuyapi/cli on a macOS device so far, so I'm guessing other OSes handle |
Yesterday I bought an identical device and it worked seemlessly with the broadcasthost addition to /etc/hosts @engelant : Yes, I am connected to the same access point that the devices should connect to; I am running kubuntu live; Here is the log: root@xubuntu:/usr/local/lib/node_modules/@tuyapi/cli# DEBUG=* ./cli.js link-wizard |
Okay, it worked also with the old one. I pressed the button for a longer time, until the led blinked faster... |
Thanks so for guys. Do you want me to close this now? This is my first encounter with github! :) |
Hey, thanks for your fantastic work.
I get an error using tuya-cli
I have no problems adding the plug with this app https://play.google.com/store/apps/details?id=com.tuya.smartlife&hl=de
✖ Device(s) failed to be registered! { Error: getaddrinfo EAI_AGAIN at Object._errnoException (util.js:1022:11) at errnoException (dns.js:55:15) at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26) code: 'EAI_AGAIN', errno: 'EAI_AGAIN', syscall: 'getaddrinfo', hostname: 'broadcasthost' }
The text was updated successfully, but these errors were encountered: