We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I'm trying to automate my TV with Sinric Pro and Node.JS, but everytime i try to run my code on windows, it gives me this error:
node:events:306 throw er; // Unhandled 'error' event ^
Error: bind EADDRNOTAVAIL 224.9.9.9:3333 ←[90m at node:dgram:337:20←[39m ←[90m at processTicksAndRejections (node:internal/process/task_queues:81:21)←[39m Emitted 'error' event on Socket instance at: ←[90m at node:dgram:339:14←[39m ←[90m at processTicksAndRejections (node:internal/process/task_queues:81:21)←[39m { errno: ←[33m-4090←[39m, code: ←[32m'EADDRNOTAVAIL'←[39m, syscall: ←[32m'bind'←[39m, address: ←[32m'224.9.9.9'←[39m, port: ←[33m3333←[39m
}
I tried to run just the basic example in this repo and still appears that error.
Can anyone help me?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi, I'm trying to automate my TV with Sinric Pro and Node.JS, but everytime i try to run my code on windows, it gives me this error:
node:events:306
throw er; // Unhandled 'error' event
^
Error: bind EADDRNOTAVAIL 224.9.9.9:3333
←[90m at node:dgram:337:20←[39m
←[90m at processTicksAndRejections (node:internal/process/task_queues:81:21)←[39m
Emitted 'error' event on Socket instance at:
←[90m at node:dgram:339:14←[39m
←[90m at processTicksAndRejections (node:internal/process/task_queues:81:21)←[39m {
errno: ←[33m-4090←[39m,
code: ←[32m'EADDRNOTAVAIL'←[39m,
syscall: ←[32m'bind'←[39m,
address: ←[32m'224.9.9.9'←[39m,
port: ←[33m3333←[39m
}
I tried to run just the basic example in this repo and still appears that error.
Can anyone help me?
The text was updated successfully, but these errors were encountered: