You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sagemcom F@st 5359 is not supported while is it listed on your repo #560
The Sagemcom F@st 5359 used as a KPN Box 12 appears to be listed as supported, but authentication fails when using sagemcom_api version 1.6.0.
The router is reachable at http://192.168.2.254, and its web interface responds with HTTP 200. Direct authentication against its internal SAH API using sah.Device.Information.createContext works. However, authentication through SagemcomClient fails with an empty exception message.
The login was tested using the admin username and EncryptionMethod.SHA512.
To Reproduce
Steps to reproduce the behavior:
Install sagemcom_api version 1.6.0 in a Python virtual environment.
Create a SagemcomClient for the KPN Box 12:
Host: 192.168.2.254
Username: admin
Encryption method: EncryptionMethod.SHA512
SSL verification: disabled
Call await client.login().
The login fails without a descriptive exception message.
Example result:
[STEP] Logging in to KPN Box
[WARN] Login failed (attempt 1/3):
[WARN] Login failed (attempt 2/3):
[WARN] Login failed (attempt 3/3):
[CRITICAL] Login failed after 3 attempts:
Thanks for the detailed report, and you're right that the README is misleading here.
The KPN Box 12 was added to the list back when its firmware still used Sagemcom's own /cgi/json-req API, which is what this library talks to. Recent KPN firmware replaced that with a SoftAtHome API (/ws, sah.Device.Information.createContext, X-Sah auth), the same one you got working directly. On current firmware, /cgi/json-req returns an empty 404. The library then tries its REST login, which also returns 404, and raises an UnsupportedHostException with an empty body. That's why your error message is blank. Changing the encryption method or username won't help, because the endpoint doesn't exist on this firmware.
Supporting the SoftAtHome API would mean a separate client, which is out of scope for this library (see also #391, where this was first investigated). I've opened #561 to update the README and note that recent KPN Box 12 firmware isn't supported.
Closing this as not planned. Sorry for the confusion!
Activity
iMicknl commentedon Oct 28, 2026
Thanks for the detailed report, and you're right that the README is misleading here.
The KPN Box 12 was added to the list back when its firmware still used Sagemcom's own
/cgi/json-reqAPI, which is what this library talks to. Recent KPN firmware replaced that with a SoftAtHome API (/ws,sah.Device.Information.createContext,X-Sahauth), the same one you got working directly. On current firmware,/cgi/json-reqreturns an empty404. The library then tries its REST login, which also returns404, and raises anUnsupportedHostExceptionwith an empty body. That's why your error message is blank. Changing the encryption method or username won't help, because the endpoint doesn't exist on this firmware.Supporting the SoftAtHome API would mean a separate client, which is out of scope for this library (see also #391, where this was first investigated). I've opened #561 to update the README and note that recent KPN Box 12 firmware isn't supported.
Closing this as not planned. Sorry for the confusion!
Mark KPN Box 12 with recent firmware as unsupported (#561)