Unable to Log into Router After Firmware Update to V12.C.24.05.08 (KPN Box 12 / Sagemcom F@st 5359)

[remcoenden]

I’ve been using the Sagemcom F@st custom integration with Home Assistant to connect to my KPN Box 12 (Sagemcom F@st 5359) router. The integration previously worked flawlessly, but after my router firmware was updated to V12.C.24.05.08, I can no longer log into the router via the integration.

I’ve installed the latest version of the integration and attempted multiple troubleshooting steps, but the problem persists.

Steps to Reproduce

1. Set up the Sagemcom F@st integration with Home Assistant.

2. Attempt to log in to the KPN Box 12 router running firmware V12.C.24.05.08.

3. Observe that login attempts fail.

Expected Behavior

• The integration should allow me to log into the router and retrieve data, as it did with the previous firmware version.

Actual Behavior:

• The integration fails to log into the router.

Troubleshooting Steps Attempted

• Confirmed that the router’s credentials (username/password) are correct and work when logging in via the router’s web interface.
  -Reinstalled the Sagemcom F@st integration.
  -Checked the router’s firmware version to confirm the update to V12.C.24.05.08.
  -Verified that the issue started after the firmware update.

Additional Context

Router

• Model: KPN Box 12 (Sagemcom F@st 5359)
• Firmware: V12.C.24.05.08

Sagecom Fast Integration

• Version: v0.3.6
• Host: http://192.168.2.254/
• Username: Admin
• Password: <Router Password>
• Uses an SSL certificate: False
• Verify SSL certificate: False

Home Assistant

• Core: 2025.1.4
• Supervisor: 2024.12.3
• Operating System: 14.1
• Frontend: 20250109.2

Logs and Debug Information

from home-assistant.log:

2025-01-26 11:58:24.996 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-26 11:58:24.999 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sagemcom_fast which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-01-26 12:01:25.556 INFO (MainThread) [backoff] Backing off __post(...) for 0.4s (aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host http:80 ssl:default [DNS server returned answer with no data])
2025-01-26 12:01:25.994 INFO (MainThread) [backoff] Backing off __post(...) for 0.6s (aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host http:80 ssl:default [DNS server returned answer with no data])
2025-01-26 12:01:26.566 INFO (MainThread) [backoff] Backing off __post(...) for 2.5s (aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host http:80 ssl:default [DNS server returned answer with no data])
2025-01-26 12:01:29.045 INFO (MainThread) [backoff] Backing off __post(...) for 6.8s (aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host http:80 ssl:default [DNS server returned answer with no data])
2025-01-26 12:01:39.417 ERROR (MainThread) [backoff] Giving up __post(...) after 5 tries (aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host http:80 ssl:default [DNS server returned answer with no data])

Potential Cause

It appears that the firmware update may have introduced changes to the API or login mechanisms, breaking compatibility with the integration.

Request

Could you investigate whether this firmware update has affected compatibility with the integration? If additional information or testing is required, please let me know, and I’d be happy to assist.

[ShaggyBro]

Can confirm, same thing happened on my unsupported but at the time working f@st 5670 on the same timeframe.

[remcoenden]

Hey @iMicknl, is there any chance you can take a look at this issue? I would be happy to help you with as many details as you'll need. Without your integration my complete setup is almost useless, so I'm really looking forward to getting it all up-and-running again.

[iMicknl]

Do you get an error when you try to readd the integration? It might be that the firmware updated removed the endpoints used by these routers...

[remcoenden]

Hey Mick, thank you for getting back to me. I've tried some configurations - non of them working - and the results are shown below.

Configuration 1

Host: http://192.168.2.254/

Error Message

Failed to connect, please try again

Logs

Retieved from /homeassistant/home-assistant.log

2025-02-21 21:38:29.126 INFO (MainThread) [backoff] Backing off __post(...) for 0.2s (aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host http:80 ssl:default [DNS server returned answer with no data])
2025-02-21 21:38:29.308 INFO (MainThread) [backoff] Backing off __post(...) for 3.3s (aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host http:80 ssl:default [DNS server returned answer with no data])
2025-02-21 21:38:32.661 INFO (MainThread) [backoff] Backing off __post(...) for 6.6s (aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host http:80 ssl:default [DNS server returned answer with no data])
2025-02-21 21:38:43.071 ERROR (MainThread) [backoff] Giving up __post(...) after 5 tries (aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host http:80 ssl:default [DNS server returned answer with no data])

Configuration 2

Host: 192.168.2.254

Error Message

Your host does not support the Sagemcom API endpoint used by this integration. Make sure you have provided the correct host and that your router is supported.

Logs

No logs added to /homeassistant/home-assistant.log

[DunkieGaming]

The new web interface is actually using XHR requests. Seems to be a Flutter GUI.

For all the requests they use the same "http://192.168.2.254/ws/NeMo/Intf/lan:getMIBs" url but with different payloads

[remcoenden]

Hmm, this is some really usefull information. So it does seem like my gut feeling is indeed correct - the API has been changed to a level which is currently incompatible with the the Sagemcom F@ast integration.
@iMicknl, do you think it would be possible to modify Sagemcom F@ast to be compatible with these changes again? I would like to to do it myself, but at this moment my knowledge is quite limited on this level.

If you're willing to explain the current integration a bit to me I could also try to make a fork based on this project and implement it that way.

[DunkieGaming]

Changes old firmware vs new one:

Uses Flutter
Gets information using a XHR request on a specific url with different payloads for different information