-
Notifications
You must be signed in to change notification settings - Fork 32
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
Sagemcom F@st 5655V2 Telekom support #81
Comments
Could you share the full error message you get? |
Sure, but it's not much. The output of the script attached is:
|
@iMicknl do you think it can be fixed? How can I provide more info for you? I started looking at some payloads and by eyeballing, they look OK, but must miss some fields or maybe they're not in an arrangement that's sufficient for this FW variant. |
@kobuki are you familiar with Python yourselves? I don't have time currently to work on this, and it is especially hard to debug your router from here. You could start with a debugger in VSCode, or just by putting print statements in the code. It would be good if you better understand the payload and where it is probably not parsing the payload correctly. The output you have shown above doesn't tell me anything unfortunately. It is weird that an exception is thrown with only the text 'id'. Best is to print the whole response there. |
@iMicknl sure, I'll dig into a bit more, but I'd appreciate some hints, based on the stack trace and the response below if your time allows.
So it seems the response is correct, but some other connection problem prevents the code to go further. It's either a genuine disconnect, or some other expectation in network code that fails. |
@kobuki I am using a Telekom router as well. you may need to increase the timeout try this:
|
|
I have the same problem with the official Proximus BBox3. Only a text 'id' is printed. Did you solved it ? |
The reason for "aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected" is because you are sending requests too fast. Just put 0.5s between requests and the problem will be solved. |
In my case it's on the first call, so no subsequent ones to repeat too fast. |
There are two independed problems here: The first one is that I wrote - when you send requests too fast, then it will end on ServerDisconnectedError exception. When this happens your session will stay logged on server and the second login attempt will end with 'id' Exception (and you need to wait couple of minutes in order to session expire). The reason is, that telecom firmware doesn't return XMO_* error descriptions but English translations. Just replace XMO_REQUEST_ACTION_ERR in const.py with 'Action error' and you will see the real login error reason. |
Sleeping between requests really helped in my case. Thank you very much! |
Model information
Describe the bug
Doesn't seem to work, using the sample code on the main GH page. An exception is caught in the
async with SagemcomClient
function that only prints the text'id'
. MD5 auth method is used, SHA512 times out.To Reproduce
Steps to reproduce the behavior:
Run the "long" sample code on https://github.com/iMicknl/python-sagemcom-api
Expected behavior
It runs and prints stuff in the router.
Screenshots
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: