Cannot add Freebox Ultra

[bterrier]

The problem

I replaced my Freebox Pop with a Freebox Ultra.

I never add any issues adding the Freebox Pop to home assistant. The Freebox Ultra is detected and I have a new device notification. However, when I try to add it it fails just before the Freebox should display the pairing authorization request.

I cannot proceed further than the step "Lier le routeur Freebox" and I have the error message "Échec de l'inscription, veuillez réessayer".

In the logs I have:

2024-02-12 18:05:08.346 ERROR (MainThread) [homeassistant.components.freebox.config_flow] Starting session failed (APIResponse: {"uid": "...", "success": false, "msg": "Erreur d'authentification de l'application", "result": {"password_salt": "...", "challenge": "..."}, "error_code": "invalid_token"})
2024-02-12 18:05:08.346 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session
2024-02-12 18:05:08.347 ERROR (MainThread) [homeassistant] Error doing job: Unclosed connector

What version of Home Assistant Core has the issue?

core-2024.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

freebox

Link to integration documentation on our website

https://www.home-assistant.io/integrations/freebox

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @hacf-fr, @quentame, mind taking a look at this issue as it has been labeled with an integration (freebox) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of freebox can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign freebox Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

freebox documentation freebox source _{^{(message by IssueLinks)}}

[foXaCe]

hello i have same problem

[Seidel76]

Same for me...

[rrrrrraa]

Seems the integration does not handle invalid app_token (caused by change of freebox, revoked token, etc). The app_token is stored at .homeassistant/.storage/freebox/ in a .conf file. If you remove the .conf file and re-add the freebox integration it will create a new app token and then the authentication request should succeed.

[Seidel76]

I've this error on logs when I add Freebox. I've deleted token in freebox folder.

Logger: homeassistant.config_entries Source: config_entries.py:444 First occurred: 06:13:08 (2 occurrences) Last logged: 06:13:40

Error setting up entry 4d5qeioe.fbxos.fr for freebox Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 444, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/freebox/init.py", line 32, in async_setup_entry await router.update_all() File "/usr/src/homeassistant/homeassistant/components/freebox/router.py", line 130, in update_all await self.update_sensors() File "/usr/src/homeassistant/homeassistant/components/freebox/router.py", line 197, in update_sensors self.call_list = await self._api.call.get_calls_log() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/freebox_api/api/call.py", line 40, in get_calls_log return await self._access.get("call/log/") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/freebox_api/access.py", line 122, in get return await self._perform_request(self.session.get, end_url) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/freebox_api/access.py", line 114, in _perform_request raise HttpRequestError(err_msg) freebox_api.exceptions.HttpRequestError: Request failed (APIResponse: {"msg": "Erreur lors de la r\u00e9cup\u00e9ration de la liste des appels: Ce service n'est pas disponible actuellement", "success": false, "error_code": "service_down"})

[Quentame]

Hi ! Sorry for the long response time 🥲

Ok so it seems the issue occurs when you already setup the Freebox integration with the Pop, then move to the Ultra. Then the authentication between HA and the Freebox is lost.

Indeed, there are no reauth flow for the integration now.

So you should remove the integration, and add it again.

Be aware of automations or services that use Freebox sensors or device trackers.

Thanks for reporting 🙏

[jjdejong]

Seems the integration does not handle invalid app_token (caused by change of freebox, revoked token, etc). The app_token is stored at .homeassistant/.storage/freebox/ in a .conf file. If you remove the .conf file and re-add the freebox integration it will create a new app token and then the authentication request should succeed.

This fixes it.

[AuroreVgn]

Seems the integration does not handle invalid app_token (caused by change of freebox, revoked token, etc). The app_token is stored at .homeassistant/.storage/freebox/ in a .conf file. If you remove the .conf file and re-add the freebox integration it will create a new app token and then the authentication request should succeed.

Fixed it!