Problème installation intégration Freebox

Bonjour,

J’ai essayé l’intégration Freebox sans pouvoir finaliser avec les éléments suivants :

Tu peux me donner les logs que tu trouveras dans l’intégration.

Salut @Will_71 ,

Voici le journal, c’est ce dont tu as besoin ?

Salut @Will_71 ,

Je ne suis pas sûr que ça corresponde à ce dont tu as besoin.

@Jluc tu peux coller les logs en format texte au lieu d’une image pour que cela plus simple a copier pour moi. Merci

Désolé ::slight_smile:

2026-07-31T10:32:49.034Z] [INFO] Starting the Freebox integration...
[2026-07-31T10:32:49.173Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-07-31T10:32:49.434Z] [ERROR] [freebox-devices] Unable to load Freebox home devices TypeError: tiles.forEach is not a function
    at FreeboxClient.loadDevices (file:///app/src/freebox/FreeboxClient.js:211:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async buildDiscoveredDevices (file:///app/src/devices.js:50:19)
    at async publishDevicesIfPaired (file:///app/index.js:59:19)
    at async GladysIntegration.<anonymous> (file:///app/index.js:218:5)
[2026-07-31T10:32:49.471Z] [INFO] [freebox-devices] Freebox discovery: 1 device(s) built
[2026-07-31T10:32:52.125Z] [WARN] [gladys-sdk] connection to Gladys lost (close code 1006)
[2026-07-31T10:32:52.125Z] [WARN] [gladys-sdk] not connected to Gladys (ws://172.30.0.1:80), retrying in 1000 ms (attempt 1)
[2026-07-31T10:32:52.135Z] [INFO] Received SIGTERM -> graceful shutdown
[2026-07-31T10:33:59.442Z] [INFO] Starting the Freebox integration...
[2026-07-31T10:33:59.656Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-07-31T10:33:59.917Z] [ERROR] [freebox-devices] Unable to load Freebox home devices TypeError: tiles.forEach is not a function
    at FreeboxClient.loadDevices (file:///app/src/freebox/FreeboxClient.js:211:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async buildDiscoveredDevices (file:///app/src/devices.js:50:19)
    at async publishDevicesIfPaired (file:///app/index.js:59:19)
    at async GladysIntegration.<anonymous> (file:///app/index.js:218:5)
[2026-07-31T10:33:59.954Z] [INFO] [freebox-devices] Freebox discovery: 1 device(s) built
[2026-07-31T10:34:17.466Z] [INFO] onScanRequest -> publishing discovered Freebox devices
[2026-07-31T10:34:17.484Z] [ERROR] [freebox-devices] Unable to load Freebox home devices TypeError: tiles.forEach is not a function
    at FreeboxClient.loadDevices (file:///app/src/freebox/FreeboxClient.js:211:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async buildDiscoveredDevices (file:///app/src/devices.js:50:19)
    at async publishDevicesIfPaired (file:///app/index.js:59:19)
    at async file:///app/index.js:67:3
    at async GladysIntegration._runHandler (/app/node_modules/@gladysassistant/integration-sdk/lib/

Pas de souci. Merci.
Je regarde ce soir je te tiens au courant.

Est-ce que tu pourrais me donner les logs dans gladys quand tu essais d’ajouter ton player dans Gladys ?

Si tu ne sais pas récupérer les logs en ligne de commande tu peux les télécharger directement depuis Gladys depuis les paramètres Systèmes et me les envoyés.

Merci d’avance

C’est moi qui te remercie,

J’espère que tu pourras quelque chose avec ces logs :slight_smile:

2026-07-31T19:10:30.573960233Z     at SonosHandler.setValue (/src/server/services/sonos/lib/sonos.setValue.js:13:36)
2026-07-31T19:10:30.573967561Z     at DeviceManager.setValue (/src/server/lib/device/device.setValue.js:22:24)
2026-07-31T19:10:30.573973787Z     at Object.music.play-notification (/src/server/lib/scene/scene.actions.js:635:23)
2026-07-31T19:10:30.573979743Z     at processTicksAndRejections (node:internal/process/task_queues:103:5)
2026-07-31T19:10:30.573985558Z     at executeAction (/src/server/lib/scene/scene.executeActions.js:34:7)
2026-07-31T19:10:30.573991495Z     at /src/server/lib/scene/scene.executeActions.js:75:9
2026-07-31T19:12:15.870646902Z 2026-07-31T21:12:15+0200 <info> externalIntegration.integrationDisconnected.js:16 (ExternalIntegration.integrationDisconnected) External integration ext-william-de71-gladys-freebox disconnected from websocket
2026-07-31T19:12:16.315830352Z 2026-07-31T21:12:16+0200 <info> externalIntegration.integrationConnected.js:19 (ExternalIntegration.integrationConnected) External integration ext-william-de71-gladys-freebox connected in websocket
2026-07-31T19:12:56.027956814Z 2026-07-31T21:12:56+0200 <info> device.getDuckDbMigrationState.js:11 (DeviceManager.getDuckDbMigrationState) Device : getDuckDbMigrationState
2026-07-31T19:12:56.046724415Z 2026-07-31T21:12:56+0200 <info> device.getDuckDbMigrationState.js:19 (DeviceManager.getDuckDbMigrationState) Device : getDuckDbMigrationState : isDuckDbMigrated: true
2026-07-31T19:12:56.046750108Z 2026-07-31T21:12:56+0200 <info> device.getDuckDbMigrationState.js:20 (DeviceManager.getDuckDbMigrationState) Device : getDuckDbMigrationState : duckDbDeviceStateCount: 32414257
2026-07-31T19:12:56.046856380Z 2026-07-31T21:12:56+0200 <info> device.getDuckDbMigrationState.js:21 (DeviceManager.getDuckDbMigrationState) Device : getDuckDbMigrationState : sqliteDeviceStateCount: 0
2026-07-31T19:12:57.333181658Z 2026-07-31T21:12:57+0200 <info> system.isDocker.js:13 (System.isDocker) System.isDocker: This system is running inside Docker.

Tu as bien réessayé d’ajouter ton player juste avant de les télécharger ?

Oui j’ai cliqué sur tous les onglets et obtenu les mêmes fenêtres que celles que j’ai collées avant

ok y’a rien pour aider dans les logs. Je te tiens au courant.

Une mise à jour est en cours. Tiens-moi au courant dès que tu as pu tester et envoie-moi les logs si tu as toujours le souci.

La mise à jour avec la version 1.0.1 n’apporte pas d’amélioration.

Est-ce que d’autres utilisateurs ont le même problème ?

Bonne nuit

Y a-t-il plus de logs ? De mon côté, je n’ai pas de player disponible sur ma Freebox, donc je ne peux pas tester comme je le voudrais.

Pour m’aider, il faudrait que tu ailles dans les outils de développement de ton navigateur (avec F12 généralement), aller dans l’onglet réseau, ensuite appuyer sur « Ajouter à Gladys » et me faire une capture d’écran. Cela pourrait peut-être permettre de voir le problème.

J’aurai bien aimé tester mais j’ai une POP et donc pas possible de piloter le player :frowning:
Par contre je pourrai tester l’appairage à partir de lundi matin seulement.

Je pense que l’affichage côté intégration externe pourrait être plus explicite, l’UI indique un message beaucoup trop générique et il n’y a pas à demander à l’utilisateur de regarder les logs du navigateur, c’est beaucoup trop complexe, surtout pour @Jluc qui est débutant :slight_smile:

Je propose un correctif

J’ai une … je sais plus quoi … Delta je crois, je ne l’utilise plus (au prix ou je l’ai payer quoi :scream:) :sweat_smile:
Je regarde

Bon bah je n’ai pas ces parametres … ou plutot je suis limité étant en mode bridge :sweat_smile::zany_face:

Salut à tous,

J’ai désinstallé l’intégration puis renouveler les différentes opérations avec le même résultat. Voici le journal :

[2026-08-01T09:53:18.823Z] [INFO] Starting the Freebox integration...
[2026-08-01T09:53:19.036Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-08-01T09:53:19.329Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:53:19.347Z] [INFO] Freebox: 0 device(s) published (core count: 0)
[2026-08-01T09:53:28.042Z] [INFO] onScanRequest -> publishing discovered Freebox devices
[2026-08-01T09:53:28.061Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:53:28.070Z] [INFO] Freebox: 0 device(s) published (core count: 0)
[2026-08-01T09:53:34.923Z] [INFO] Action reboot -> rebooting the Freebox
[2026-08-01T09:53:34.938Z] [ERROR] Freebox reboot failed Error: Freebox reboot refused: Cette application n’est pas autorisée à accéder à cette fonction
    at FreeboxClient.reboot (file:///app/src/freebox/FreeboxClient.js:328:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async file:///app/index.js:199:5
    at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1141:22)
    at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1079:9)
[2026-08-01T09:53:41.103Z] [INFO] Action reboot -> rebooting the Freebox
[2026-08-01T09:53:41.118Z] [ERROR] Freebox reboot failed Error: Freebox reboot refused: Cette application n’est pas autorisée à accéder à cette fonction
    at FreeboxClient.reboot (file:///app/src/freebox/FreeboxClient.js:328:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async file:///app/index.js:199:5
    at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1141:22)
    at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1079:9)
[2026-08-01T09:56:05.516Z] [INFO] onScanRequest -> publishing discovered Freebox devices
[2026-08-01T09:56:05.603Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:56:05.613Z] [INFO] Freebox: 0 device(s) published (core count: 0)
[2026-08-01T09:56:07.656Z] [INFO] onScanRequest -> publishing discovered Freebox devices
[2026-08-01T09:56:07.673Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:56:07.682Z] [INFO] Freebox: 0 device(s) published (core count: 0)
[2026-08-01T09:58:10.642Z] [INFO] onScanRequest -> publishing discovered Freebox devices
[2026-08-01T09:58:10.663Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:58:10.673Z] [INFO] Freebox: 0 device(s) published (core count: 0)
[2026-08-01T09:58:20.455Z] [INFO] Action pair -> requesting Freebox authorization
[2026-08-01T09:58:25.463Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:58:55.731Z] [INFO] onScanRequest -> publishing discovered Freebox devices
[2026-08-01T09:58:55.748Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:58:55.756Z] [INFO] Freebox: 0 device(s) published (core count: 0)
[2026-08-01T09:58:59.547Z] [INFO] Action pair -> requesting Freebox authorization
[2026-08-01T09:59:01.913Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:59:05.866Z] [INFO] Received SIGTERM -> graceful shutdown
[2026-08-01T09:59:06.302Z] [INFO] Starting the Freebox integration...
[2026-08-01T09:59:06.504Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-08-01T09:59:06.786Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:59:06.803Z] [INFO] Freebox: 0 device(s) published (core count: 0)
[2026-08-01T09:59:15.252Z] [INFO] onScanRequest -> publishing discovered Freebox devices
[2026-08-01T09:59:15.272Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
[2026-08-01T09:59:15.281Z] [INFO] Freebox: 0 device(s) published (core count: 0)
[2026-08-01T09:59:24.455Z] [INFO] Action pair -> requesting Freebox authorization
[2026-08-01T09:59:26.219Z] [INFO] [freebox-devices] Freebox discovery: 0 device(s) built
Et les logs Gladys :
2026-08-01T09:37:56.731388096Z 2026-08-01T11:37:56+0200 <error> index.js:53 (Timeout.syncAllUsers [as _onTimeout]) NotFoundError: [object Object]
2026-08-01T09:37:56.731409919Z     at CalDAVHandler.syncUserCalendars (/src/server/services/caldav/lib/calendar/calendar.syncUserCalendars.js:66:11)
2026-08-01T09:37:56.731427252Z     at Promise.map.concurrency (/src/server/services/caldav/index.js:46:13)
2026-08-01T09:51:10.959509060Z 2026-08-01T11:51:10+0200 <info> externalIntegration.integrationDisconnected.js:16 (ExternalIntegration.integrationDisconnected) External integration ext-william-de71-gladys-freebox disconnected from websocket
2026-08-01T09:51:45.668932102Z 2026-08-01T11:51:45+0200 <info> externalIntegration.integrationConnected.js:19 (ExternalIntegration.integrationConnected) External integration ext-william-de71-gladys-freebox connected in websocket
2026-08-01T09:52:37.129814884Z 2026-08-01T11:52:37+0200 <info> externalIntegration.integrationDisconnected.js:16 (ExternalIntegration.integrationDisconnected) External integration ext-william-de71-gladys-freebox disconnected from websocket
2026-08-01T09:52:37.607056740Z 2026-08-01T11:52:37+0200 <info> externalIntegration.integrationConnected.js:19 (ExternalIntegration.integrationConnected) External integration ext-william-de71-gladys-freebox connected in websocket
2026-08-01T09:53:13.078874614Z 2026-08-01T11:53:13+0200 <info> externalIntegration.integrationDisconnected.js:16 (ExternalIntegration.integrationDisconnected) External integration ext-william-de71-gladys-freebox disconnected from websocket
2026-08-01T09:53:13.564889660Z 2026-08-01T11:53:13+0200 <info> externalIntegration.integrationConnected.js:19 (ExternalIntegration.integrationConnected) External integration ext-william-de71-gladys-freebox connected in websocket
2026-08-01T09:53:18.303167253Z 2026-08-01T11:53:18+0200 <info> externalIntegration.integrationDisconnected.js:16 (ExternalIntegration.integrationDisconnected) External integration ext-william-de71-gladys-freebox disconnected from websocket
2026-08-01T09:53:18.911971308Z 2026-08-01T11:53:18+0200 <info> externalIntegration.integrationConnected.js:19 (ExternalIntegration.integrationConnected) External integration ext-william-de71-gladys-freebox connected in websocket
2026-08-01T09:54:31.670496104Z 2026-08-01T11:54:31+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: read ENETUNREACH
2026-08-01T09:54:31.979105748Z 2026-08-01T11:54:31+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:32.287933389Z 2026-08-01T11:54:32+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:32.595546971Z 2026-08-01T11:54:32+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:32.904362223Z 2026-08-01T11:54:32+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:33.212643740Z 2026-08-01T11:54:33+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:33.521100222Z 2026-08-01T11:54:33+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:33.829815819Z 2026-08-01T11:54:33+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:34.137381144Z 2026-08-01T11:54:34+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:34.443887849Z 2026-08-01T11:54:34+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:34.751980132Z 2026-08-01T11:54:34+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:35.057936963Z 2026-08-01T11:54:35+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:35.366333652Z 2026-08-01T11:54:35+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:35.672152573Z 2026-08-01T11:54:35+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:35.978816821Z 2026-08-01T11:54:35+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:36.287302838Z 2026-08-01T11:54:36+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:36.595716073Z 2026-08-01T11:54:36+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:36.904716769Z 2026-08-01T11:54:36+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:37.213689575Z 2026-08-01T11:54:37+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:37.521259790Z 2026-08-01T11:54:37+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:37.828147851Z 2026-08-01T11:54:37+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:38.135367728Z 2026-08-01T11:54:38+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:38.443498664Z 2026-08-01T11:54:38+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:38.749129577Z 2026-08-01T11:54:38+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:39.058241233Z 2026-08-01T11:54:39+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:39.366546827Z 2026-08-01T11:54:39+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:39.674955005Z 2026-08-01T11:54:39+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2026-08-01T09:54:39.983426080Z 2026-08-01T11:54:39+0200 <warn> message.connect.js:19 (TelegramBot.<anonymous>) Telegram polling error, code = EFATAL, message = EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org

Au passage, je constate des erreurs fatales; que faut-il faire ?

Pour information, j’ai amélioré l’interface qui sera beaucoup plus claire en cas d’erreur lors de la création d’un appareil découvert :slight_smile:

C’est mergé et ça part dans une prochaine release très vite (ce week-end)