-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Errors hashboards VNISH #255
Comments
Result:
I just don't know how to make the error number |
The error number isn't important really, it's just there for some firmwares like Whatsminer stock that provide a code instead of a description, so that I can turn that code into a description. |
You have pretty much done all the work here, you might as well submit a pull request with this update. All you have to do is add the The only other thing to do is to update the Let me know if you have any questions or want me to open the PR, and thanks for the excellent feature request. |
Thanks for the clarification! I'd be happy to submit the PR with the changes. Could you please grant me access to open the PR, or let me know if you'd like me to proceed with it on my own? Once I have access, I'll make sure to add the Looking forward to your response! |
Shouldn't need any access? Just fork the project, make the changes on your version, then submit a pull request. |
Is your feature request related to a problem? Please describe.
Currently, there is no convenient built-in method for centrally retrieving and processing miner errors when working with VNish firmware. This makes it more difficult to automate monitoring and quickly respond to hardware issues, especially when running large-scale mining operations.
Describe the solution you'd like
I would like to see functionality similar to the
_get_errors()
method available for other miners, but specifically adapted for VNish firmware. Ideally, it would fetch data from the miner’s/api/v1/summary
, parse the state and description fields for each chain, and return a structured list of errors—following the approach used in other parts of the library.Describe alternatives you've considered
An alternative would be to parse the API data manually outside the library, but that adds complexity and maintenance overhead. Another option would be to rely on external scripts or plugins to handle error processing, which again increases development and maintenance costs.
Additional context
Implementing this feature would make it significantly easier to monitor and manage large fleets of miners. Rapid error detection and reporting are critical for operational stability and reducing downtime, and a built-in method would streamline these processes.
Below is the updated code snippet including the
_get_errors
method for VNish:/pyasic/miners/backends/vnish.py
And API json:
attention here:
The text was updated successfully, but these errors were encountered: