-
Notifications
You must be signed in to change notification settings - Fork 24
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
UE32J5200 - Handshake status 400 Bad Request when trying to get token #62
Comments
I have the same issue with UE55H6203AK model. I've tried everything from #61 with reverting latest fixes, changing the port to 8000, but still no luck. |
Hi @estevez-dev, |
Hi @EPMatt
and getting:
Should I add this info to #21 as well? |
Hi @estevez-dev,
|
Hi @EPMatt
I also tried to hardcode
So looks like |
Hi @estevez-dev,
Moreover, If you'd like we can move this issue to #21 and keep track of the progress there. :) |
Moved to #21. |
getting the same thing with my J6200 |
Hi @sermayoral,
I'm trying to connect a UE32J5200 TV with this integration. Unfortunately I'm stuck at the token retrieval.
Running
get_token.py --ip <myip> --port 8080
results in aconnection refused
error.I found that the procedure defined in
connect()
method of thePySmartCrypto
library is using the hardcoded port8000
, so that the port supplied via cli argument is not considered in the pairing section.This issue has been addressed in #61, but I still can't connect to my device.
Running
get_token.py --ip <myip> --port 8080
on the PR #61 results in a different error:I tried to debug the issue by myself without success, but I discovered that the value of
websocket_response
after its initialization is<Response [403]>
, while the value ofwebsocket_url
after its initialization iswhich I think it's not what it should be.
So the problem seems to be with the first request receiving a
Forbidden
response at line 95.I'd be glad to help you solving this issue. 👍🏻
The text was updated successfully, but these errors were encountered: