DumbMonit

IntégrationsStockage et sauvegardes

Surveiller QNAP QTS / QuTS hero avec DumbMonit

Bêta

A QNAP NAS through the CGI pages of its web interface: volumes filling up, disks whose SMART health is no longer good or too hot, processor temperature, firmware updates.

DocumentationSite officiel : QNAP

Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.

Ce que DumbMonit surveille

This integration was built from the public references (the pages read by the Home Assistant qnap integration and the python-qnapstats library) and tested against recorded-style responses only, not against a real QNAP NAS yet. It only reads. Tell us what breaks. A QNAP NAS through the CGI pages of its web interface: volumes that fill up, disks whose SMART health is no longer good or that run too hot, processor temperature, memory, and the QTS or QuTS hero updates QNAP offers.

Usage typique. NAS (beta): volumes filling up, disk SMART health and temperature, firmware updates

Exemples

  • QNAP TS-453D
  • QuTS hero NAS
  • QTS 5.x

Comment il se connecte

Ce qu'il faut

  • User name and passwordThe dumbmonit account created on the NAS. The password is sent base64-encoded to the login page, as the web interface does.

Ports réseau à ouvrir

  • 443/TCPWeb interface (HTTPS, default)
  • 8080/TCPOnly with the HTTP protocol option
Étapes de mise en place: Create a limited account for DumbMonit
  1. Open Control Panel → Privilege → Users → Create → Create a User and create the account as follows, with a long random password. Tick no share and no application privilege.

    dumbmonit
  2. Add the account to the administrators group: QTS serves the system status, volumes and disks to that group only.

  3. Optional: under Control Panel → System → Security → Allow/Deny List, allow the web interface only from the DumbMonit server's address.

  4. In DumbMonit, enter the NAS address (for example nas.lan) with that user name and password. Choose http and port 8080 only if HTTPS is off.

À savoir. QTS has no read-only role for its system status, so the account sits in the administrators group: give it a unique password, and an account without 2-step verification. Over HTTP the password travels base64-encoded, not encrypted: prefer HTTPS.