You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 6, 2026. It is now read-only.
Is your feature request related to a problem? Please describe.
Currently, Pyasic does not support Auradine’s AH3880 miners. This creates a limitation for operators who want to monitor and manage AH3880 devices alongside other supported hardware in a unified way.
Describe the solution you'd like
Extend Pyasic to include full support for Auradine AH3880 miners, including:
• Detection of AH3880 model type.
• Fetching hashrate, temperature, power usage, and other telemetry metrics.
• Support for pool connection and status reporting.
• Error and log parsing.
Describe alternatives you've considered
• Using vendor-provided Auradine tools directly (but this fragments monitoring and makes automation harder).
• Writing a wrapper to poll AH3880 locally, but this is not sustainable and duplicates effort.
Is your feature request related to a problem? Please describe.
Currently, Pyasic does not support Auradine’s AH3880 miners. This creates a limitation for operators who want to monitor and manage AH3880 devices alongside other supported hardware in a unified way.
Describe the solution you'd like
Extend Pyasic to include full support for Auradine AH3880 miners, including:
• Detection of AH3880 model type.
• Fetching hashrate, temperature, power usage, and other telemetry metrics.
• Support for pool connection and status reporting.
• Error and log parsing.
Describe alternatives you've considered
• Using vendor-provided Auradine tools directly (but this fragments monitoring and makes automation harder).
• Writing a wrapper to poll AH3880 locally, but this is not sustainable and duplicates effort.
Additional context
• Hardware model: Auradine AH3880