# External integration - Synology **URL:** \ **Category:** Développement\ **Tags:** integration-externe\ **Created:** [August 16, 2026, 10:35pm UTC](https://community.gladysassistant.com/t/integration-externe-synology/10635 "2026-08-16T22:35:04Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [August 16, 2026, 10:35pm UTC](https://community.gladysassistant.com/t/integration-externe-synology/10635/1 "2026-08-16T22:35:04Z")
Hello, Here is a new external integration that will soon be available on the store. It will allow you to monitor system metrics, volumes, SMART disk status, and backups of a Synology NAS > **[GitHub - prohand/gladys-synology: Gladys external integration to connect synology in...](https://github.com/prohand/gladys-synology)** > > Gladys external integration to connect synology in Gladys Assistant Edit: Made with codex ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [August 19, 2026, 9:41pm UTC](https://community.gladysassistant.com/t/integration-externe-synology/10635/2 "2026-08-19T21:41:31Z")
I had Claude check what Codex had done and here’s his feedback: > Robustness > > ``` > Timeout on each DSM request (AbortSignal.timeout, 20s by default, injectable via requestTimeoutMs). Dedicated message « Synology DSM did not answer within 20s » — a NAS that accepts the connection without responding no longer freezes inFlightRefresh or all subsequent polls. > Configuration error reported to the Gladys UI: the construction of the fleet is now in the try, the old connection is closed in all cases, and a ConfigValidationError (new class in src/config.js) is reported without scheduling a retry — only a new configuration can fix it. > The MFA token is no longer blocking: reading and writing to /data encapsulated, an EACCES/EROFS produces a logger.warn instead of failing a login that DSM has accepted. > Coalesced login (loginPromise + ensureSession(previousSid)): an expired session during a snapshot triggers a single authentication instead of five, and a concurrent call no longer overwrites a fresh session. > > ``` > > Data Accuracy > > ``` > Unified healthState() for volumes and disks: only explicitly healthy or explicitly failed statuses publish 1/0. A maintenance state (expanding, background_scrubbing, repairing, SMART not supported) publishes nothing and keeps the previous value — no more false alerts or false « all good ». > Partial failures visible: lastErrors becomes lastFailures ({ url, error }), and the runtime transforms this into a connected status + message naming the NAS in default (1 Synology NAS unreachable: https://nas2 (…)). The « Test connection » action also lists the unreachable NAS. > > ``` > > Minor > > ``` > 5% tolerance on the throttle (PUBLISH_THROTTLE_RATIO): a timer that triggers a few ms early no longer skips an entire cycle. > src/runtime.js: all orchestration extracted from index.js (which now only does the SDK wiring), with serviceFactory, backoff, and scheduler injectable → test/runtime.test.js covers invalid config, retry, degraded status, timers, clean shutdown, and test action. > CI in Node 20 + 24 matrix: the floor declared in engines is now actually verified, in addition to the Docker image version. > Temperature per disk (disk.temp), new DEVICE_TEMPERATURE_SENSOR feature. Network throughput and uptime left aside as requested — incidentally, two existing tests explicitly lock their absence, it was indeed an intentional choice. > > ``` > > Bonus noticed along the way: the connection test message displayed « DSM DSM 7.2.2 » (the firmware\_ver of DSM already contains « DSM »). Fixed via a dsmLabel() helper. Everything has been fixed in version 1.0.3 ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [August 20, 2026, 6:06am UTC](https://community.gladysassistant.com/t/integration-externe-synology/10635/3 "2026-08-20T06:06:42Z")
In the codex, did you choose a particular model? ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [August 20, 2026, 7:43am UTC](https://community.gladysassistant.com/t/integration-externe-synology/10635/4 "2026-08-20T07:43:40Z")
I had chosen 5.6 high elevation ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [September 23, 2026, 1:25pm UTC](https://community.gladysassistant.com/t/integration-externe-synology/10635/5 "2026-09-23T13:25:23Z")
Version 2 is out with widgets, triggers and actions 🙂 ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [September 23, 2026, 7:41pm UTC](https://community.gladysassistant.com/t/integration-externe-synology/10635/6 "2026-09-23T19:41:58Z")
What does this integration do? 😃 ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [September 23, 2026, 7:54pm UTC](https://community.gladysassistant.com/t/integration-externe-synology/10635/7 "2026-09-23T19:54:25Z")
Everything is indicated here 😉 : [GitHub - prohand/gladys-synology: Gladys external integration to connect synology in Gladys Assistant · GitHub](https://github.com/prohand/gladys-synology)