-
Notifications
You must be signed in to change notification settings - Fork 28
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
Connection refused #34
Comments
Same issue here.... |
I fixed this by powering the TV off at the wall and then when it came back on it worked. |
Yes, same for me, just unplug/plug TV |
Tried that, but it didn't work :( |
same issue here: ConnectionRefusedError: [Errno 111] Connection refused power cycling didn't help EDIT: |
I have the same issue as OP. A power reset of the TV did not fix my issue. My TV was purchased new last year. I notice that the pairing script is trying to connect on port 1926. I did an NMAP scan of the TV and found that the following ports (TCP) are open: 5555, 6466, 6467, 8008, 8009, 8012, 8443, 9000, 9080, 10101, and 33921. These UDP ports are open: 1782, 1900, 5353, 6050, 17332, 17505, 18134, 30697, 34570, 36945, 41967, 49158, 57958, 62677, and 64513. The errors I am getting FEELS like it may be the issue reported here: Any idea what can be done? It does feel like the firmware on the TV may be causing this, but I don't where to start. Thanks. |
if your port is not open, then your TV is probably using a different API. You can also try using the philips remote app and see if that works with your TV. Should use the same API. |
I'm not able to get a username/password :(
I installed the reqs on my mac. I'm trying it in a Philips 65pus6121
Do you have any idea or pointing direction? Is there something missing on my TV? I have EasyLink disabled.
The text was updated successfully, but these errors were encountered: