python-qnapstats
Library from obtaining system information from QNAP NAS devices running QTS.
Installation
This library requires xmltodict, so make sure you have that installed:
pip3 install xmltodict>=0.10.0
Then install this Python module:
pip3 install qnapstats
Usage Example
#!/usr/bin/env python3
from qnapstats import QNAPStats
from pprint import pprint
qnap = QNAPStats('192.168.1.3', 8080, 'admin', 'correcthorsebatterystaple')
pprint(qnap.get_system_stats())
pprint(qnap.get_system_health())
pprint(qnap.get_smart_disk_health())
pprint(qnap.get_volumes())
pprint(qnap.get_bandwidth())
Account
The account you connect with must have system monitoring permissions. The simplest option is to put it in the admin group; it doesn’t necessarily need to be THE “administrator” account, but you can use some account in the administrators group.
Alternatively you can configure a normal account and enable Delegated Administration in control panel, and activate “System Monitoring.”
Once the account is created, and/or you upgrade to a newer of like QTS 5, also be sure to log into your NAS and complete any agreements, warnings, wizards, etc. that may prevent this library from using the QNAP API.
MFA/2FA must also be disabled for that user for this library to work.
Device Support
This library has been tested against the following devices and firmwares:
Model |
QTS* Firmware Versions |
Notes |
|---|---|---|
D4 Pro |
4.5.1 |
User-reported: no automated tests |
TS-110 |
4.2.4 |
|
TS-112P |
4.3.3 |
This device does not report CPU temps |
TS-210 |
4.2.6 |
This device does not report CPU temps |
TS-219P II |
4.3.3 |
User-reported: no automated tests |
TS-251B |
4.4.3 |
|
TS-228A |
5.0.1 |
This device does not report CPU temps |
TS-233 |
5.1.x |
|
TS-251+ |
4.5.1 |
No information on dnsInfo |
TS-253 Pro |
4.5.2 |
|
TS-253D |
4.5.3 |
|
TS-332 |
5.0.0 |
|
TS-364 |
5.0.1 |
|
TS-269L |
4.3.3 |
User-reported: no automated tests |
TS-410 |
4.2.3 |
This device does not report CPU temps |
TS-412 |
4.3.3 |
This device does not report CPU temps |
TS-431P |
4.3.4 |
|
TS-439 Pro II+ |
4.2.6 |
|
TS-451 |
4.2.2 - 4.2.4 |
|
TS-453A |
4.3.4; 5.0.1 |
|
TS-453Be |
4.2.3; 5.0.1 |
|
TS-464 |
5.2.7 |
User-reported: no automated tests |
TS-639 |
4.2.3 |
|
TS-659 |
4.2.6 |
May report None for some disk temps |
TS-853 Pro |
4.5.4 |
|
TS-869 Pro |
4.3.4 |
|
TS-873A |
5.0.1.2248 |
|
TS-1677XU-RP |
4.5.2 |
|
TS-EC1280U |
4.5.2 |
|
TS-h886 |
QuTS h5.0.1.2376 |
|
TS-X53 |
4.5.4 |
|
TVS-672N |
5.0.1 |
|
TVS-1282 |
5.0.1 |
⚠️ QuTS is not currently supported - see [issue #84](https://github.com/colinodell/python-qnapstats/issues/84)
Other QNAP devices using these QTS firmwares should probably work fine, as should the devices listed above on newer firmwares. If you encounter any compatibility issues, please let us know (or better yet, contribute a patch!)
Upgrading to QTS 5? Make sure the account you connect with meets the criteria listed earlier in this README. Also be sure to log into your NAS and complete any agreements, warnings, wizards, etc. that may prevent this library from using the QNAP API.
Metadata
Release files for qnapstats 0.6.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qnapstats-0.6.2.tar.gz | 11.8 kB | With provenance | Details for qnapstats-0.6.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qnapstats-0.6.2-py3-none-any.whl | Python 3 | none | any | Details for qnapstats-0.6.2-py3-none-any.whl |
Total release size: 19.9 kB
Release files / qnapstats-0.6.2.tar.gz
| Download URL | qnapstats-0.6.2.tar.gz |
|---|---|
| Size | 11.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd494da87d7a668fdccbfff179fc4fcbe37b659a660c09376e792437ac6e4d5e
|
|
BLAKE2b-256 checksum How to use checksums |
854a0bf1ac4b1773a4348e7f2cbc1f6e2d8d414660dc7e4d1276363f4cfa9ac6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logRelease files / qnapstats-0.6.2-py3-none-any.whl
| Download URL | qnapstats-0.6.2-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d9d6c7999ff3808201fa9dc92029bb790d7a0b4280c1b0b6804a4f7ba6d7ca4
|
|
BLAKE2b-256 checksum How to use checksums |
e4033e317300a42030bbd968dbbac1b8f0d3d352a43214e39abb536df8fcbec2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logSecurity for qnapstats 0.6.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for qnapstats-0.6.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.