Synology DSM integration reports wrong information

BLUF: The Synology NAS integration does not appear to report true values for drives on bad sectors and remaining life.


Running Synology DSM DS1618+ version DSM 7.1.1-42962 (latest)

Drive 6 died three days ago suddenly.

Synology integration still reports that drive is fine.

type: entities
entities:
  - entity: device_tracker.synnas
    name: NAS
  - entity: binary_sensor.synnas_drive_1_below_min_remaining_life
    name: Drive 1 Below min remaining life
  - entity: binary_sensor.synnas_drive_1_exceeded_max_bad_sectors
    name: Drive 1 Exceeded max bad sectors

  - entity: binary_sensor.synnas_drive_2_below_min_remaining_life
    name: Drive 2 Below min remaining life
  - entity: binary_sensor.synnas_drive_2_exceeded_max_bad_sectors
    name: Drive 2 Exceeded max bad sectors

  - entity: binary_sensor.synnas_drive_3_below_min_remaining_life
    name: Drive 3 Below min remaining life
  - entity: binary_sensor.synnas_drive_3_exceeded_max_bad_sectors
    name: Drive 3 Exceeded max bad sectors

  - entity: binary_sensor.synnas_drive_4_below_min_remaining_life
    name: Drive 4 Below min remaining life
  - entity: binary_sensor.synnas_drive_4_exceeded_max_bad_sectors
    name: Drive 4 Exceeded max bad sectors

  - entity: binary_sensor.synnas_drive_5_below_min_remaining_life
    name: Drive 5 Below min remaining life
  - entity: binary_sensor.synnas_drive_5_exceeded_max_bad_sectors
    name: Drive 5 Exceeded max bad sectors

  - entity: binary_sensor.synnas_drive_6_below_min_remaining_life
    name: Drive 6 Below min remaining life
  - entity: binary_sensor.synnas_drive_6_exceeded_max_bad_sectors
    name: Drive 6 Exceeded max bad sectors

title: Synology NAS
state_color: true

HAOS Installation:

installation_type: Home Assistant OS,
version: 2024.9.1,
hassio: true,
arch: x86_64,
os_version: 6.6.46-haos,
supervisor: 2024.08.0,
host_os: Home Assistant OS 13.1,
docker_version: 26.1.4,

My two Synology drives are notoriously slow to report updates that have been completed on the DD-XXX drives. I complete the updates within 24 hours of them becoming available and sometimes it takes 6 or 7 DAYS until the integration reports back as SAFE.
It isn’t a big deal to me that it’s slow seeing the updates, but I can see how it may be a problem for a bad drive.
Maybe the integration owner can address it. Have you submitted a ticket on this issue?