Issue with Freebox integration installation

Jluc · July 31, 2026, 10:48am

Hello,

I tried the Freebox integration but couldn’t complete it with the following elements:

Will_71 · July 31, 2026, 10:50am

Can you give me the logs you find in the integration?

Jluc · July 31, 2026, 10:53am

Hi @Will_71,

Here’s the log, is this what you need?

Jluc · July 31, 2026, 11:07am

Hi @Will_71,

I’m not sure if this is what you need.

Will_71 · July 31, 2026, 11:08am

@Jluc you can paste the logs in text format instead of an image so it’s easier for me to copy. Thanks

Jluc · July 31, 2026, 11:15am

Sorry

[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/

Will_71 · July 31, 2026, 12:35pm

No problem. Thanks.
I’ll check tonight and let you know.

Will_71 · July 31, 2026, 5:37pm

Could you please give me the logs in Gladys when you try to add your player in Gladys?

If you don’t know how to retrieve the logs from the command line, you can download them directly from Gladys in the System settings and send them to me.

Thanks in advance

Jluc · July 31, 2026, 7:19pm

It’s me who thanks you,

I hope you can do something with these logs

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.

Will_71 · July 31, 2026, 7:32pm

Did you try adding your player again just before downloading them?

Jluc · July 31, 2026, 7:48pm

Yes, I clicked on all the tabs and got the same windows as the ones I pasted before.

Will_71 · July 31, 2026, 8:01pm

ok there’s nothing helpful in the logs. I’ll keep you posted.

Will_71 · July 31, 2026, 9:24pm

An update is in progress. Let me know as soon as you can test and send me the logs if you still have the issue.

Jluc · July 31, 2026, 10:08pm

The update to version 1.0.1 does not bring any improvements.

Are other users experiencing the same issue?

Good night

Will_71 · July 31, 2026, 11:01pm

are there more logs? on my end I don’t have a player available on my freebox so I can’t test as I would like

mutmut · August 1, 2026, 6:57am

I would have liked to test, but I have a POP and therefore can’t control the player
However, I will be able to test the pairing starting Monday morning only.

pierre-gilles · August 1, 2026, 7:52am

I think the external integration display could be more explicit; the UI shows a much too generic message, and users shouldn’t be asked to check the browser logs, it’s way too complex, especially for @Jluc who is a beginner

I suggest a fix

Terdious · August 1, 2026, 7:56am

I have a … I don’t know what … a Delta I think, I don’t use it anymore (at the price I paid for it though )
I’m looking

Well I don’t have these parameters … or rather I’m limited being in bridge mode

Jluc · August 1, 2026, 10:07am

Hi everyone,

I uninstalled the integration and then renewed the different operations with the same result. Here is the log:

[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: This application is not authorized to access this function
    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: This application is not authorized to access this function
    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
And the Gladys logs:
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

By the way, I notice fatal errors; what should I do?

pierre-gilles · August 1, 2026, 10:17am

For your information, I improved the interface which will be much clearer in case of an error when creating a discovered device

github.com/GladysAssistant/Gladys

Improve error messages for discovered device creation (#2733)

master ← claude/device-discovery-error-messages-mjheq9

ouvert 08:30AM - 01 Aug 26 UTC

Pierre-Gilles

+633 -32

### Description This PR enhances error handling and user feedback when creating… devices from the external integration discovery screen. Instead of a generic "error occurred" message, users now see: 1. **Specific error messages** for different HTTP status codes (400, 401/403, 404, 409, 422, 5xx, network errors) 2. **Detailed field validation errors** showing exactly which device feature failed and why (e.g., "Feature 'Temperature' — Minimum value: required field not provided by the integration") 3. **Technical details** for debugging and bug reports 4. **Localized error messages** in English, French, and German **Key changes:** - **Frontend**: Added `getDiscoveredDeviceCreateError()` function to parse HTTP error responses and extract validation details. Created `DeviceCreateErrorAlert` component to display rich error information with field-level details. - **Backend**: Enhanced error middleware to include `gladysContext` (feature name/external_id) in validation error responses, and wrapped feature creation in try-catch to tag validation errors with the offending feature's identity. - **Localization**: Added comprehensive i18n strings for all error scenarios and field labels in en.json, fr.json, and de.json. This makes the discovery experience much more user-friendly, especially when integrations publish incomplete or conflicting device data. ### Checklist - [x] Tests pass: Added unit tests in `errorMiddleware.test.js` and `device.create.test.js` covering error context tagging - [x] Linter and prettier pass - [x] No breaking changes https://claude.ai/code/session_01SHzAEM2ZWYDVrgKFx7Rvsy ## Summary by CodeRabbit * **New Features** * Added detailed device-creation error messages for network, permission, conflict, validation, server, and unexpected failures. * Error alerts now show rejected fields, affected device features, technical details, and reporting guidance when available. * Added localized messaging in English, French, and German. * **Bug Fixes** * Improved API error responses to identify the specific device feature causing validation or conflict failures.

It’s merged and it will be in the next release very soon (this weekend)

Topic		Replies	Views
Integration externe - Unify network Développement integration-externe	54	126	August 4, 2026
Semaine ultra intensive sur Gladys Actualités	25	269	August 1, 2026
Améliorations dans l'UI de l'intégration zigbee2mqtt Développement	20	533	November 1, 2023
Ajout d'un journal d’évènements Demandes livrées	32	243	July 10, 2026
Gladys Assistant v4.67 : Nouvelle intégration Nuki 🔐 Actualités	12	276	March 10, 2026

Issue with Freebox integration installation

Related topics