Herostatus
Herominers Status and Alarm Notifier
This will provide an interface to monitor your miners in a terminal. It provides current hashrate, 1h,6h, and 24 hashrates and total number of hashes.
You can set from a number of alarm types for when a miner goes down.
Currently this chceks the if the 1 hour hashrate is 0. I noticed too many false alarms with my miners when checking if current hashrate was 0.
Requiremnts
pip3 install json
pin3 install requests
pip3 install pygame
sudo apt-get install portaudio19-dev python3-pyaudio
Installation
Via pip:
pip3 install herostatus
Via GitHub
git clone https://github.com/freQniK/Herostatus`
cd Herostatus
python3 herostatus.py
Install the above requirements and run herostatus.py with your python 3 interpreter.
Usage
(hero) freQniK>herostatus -h
pygame 2.5.2 (SDL 2.28.2, Python 3.8.10)
Hello from the pygame community. https://www.pygame.org/contribute.html
usage: herostatus [-h] [-s sound] [-t times]
Herominers Crypto Status and Alarm Notifier
optional arguments:
-h, --help show this help message and exit
-s sound, --sound sound
Choose Your Alarm: 1. Burglar Alarm (30s) 2. Car Alarm (33s) 3. Hip Hop Alarm (10s) 4. Nuclear Alarm (60s) 5. Siren Alarm
(16s) 6. Strong Bad Alarm (Default) (17s)
-t times, --times times
Number of times to sound the alarm before it becomes annoying
When you first run hersostatus it will prompt for the crypto you are mining. Be sure to enter the full name of the crypto, i.e., monero, dero, ergo, zephyr, etc.
It will also prompt you for your wallet address for your miners. Finally, it will prompt you for a refresh interval. Choose wisely. These settings are stored in ~/.herostatus/config.json and reused upon restart.
You can edit config.json if you feel like it to change any settings. It's a simple file.
Screenshot
Donations
Coding is a lot of work. Support your FOSS developers with a small contribution to keep them coding. Crypto is the easiest method to donate to your favorite FOSS project.
Bitcoin
bc1qjzrrqlk7t2pedfrnp25xqxru8nq3plv7ghkvag
DERO
dero1qyxctkgzee00jh3md4etc8kxkr8x4hh7cckezrhn7de39kj4xaf9xqqa6xeta
Monero
82sirs3qe2XCvytxCnkVyS5q6v18MN8vHgpU1hZECmnKQzzcVNB5vXiDMz1Ktdp4pgKKjK2vsWdGABN8AAtHbFAaDg7A63t
Pirate Chain
zs1uknhdwh306h3r08l3vvd29jz0a0ym3tpxtad6j3en82g24hnzpuknuwt25r7vpsh86ly23fgjwp
Zephyr
ZEPHs8jnJx1bKL6TdmDSfUZTMuWeFkVhye5JUg8g7QYUBizGB6u5scJixYPqLo4EQkCbjPKKxtpQJHHCEFf3qAP2QKCZBF9judW
Metadata
Release files for Herostatus 0.3.1
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 |
|---|---|---|---|---|
| herostatus-0.3.1.tar.gz | 17.0 MB | Without provenance | Details for herostatus-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| herostatus-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for herostatus-0.3.1-py3-none-any.whl |
Total release size: 34.1 MB
Release files / herostatus-0.3.1.tar.gz
| Download URL | herostatus-0.3.1.tar.gz |
|---|---|
| Size | 17.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4f3a9271f88700856db3d76534dfbb5852da10777fc18fad2f920b91e9fd729
|
|
BLAKE2b-256 checksum How to use checksums |
c1c77473f54eb47232f26f9e8412080489ccec0acb60b838933099a75309a8ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / herostatus-0.3.1-py3-none-any.whl
| Download URL | herostatus-0.3.1-py3-none-any.whl |
|---|---|
| Size | 17.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77e04e4a01c7ae2f66c89dbbf7fd3f093d0da59d317492096c14f8c590a7dc82
|
|
BLAKE2b-256 checksum How to use checksums |
27a5d89727c072f90f03960cf1228ab9cb848e24f46982d296972b8046e843d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for Herostatus 0.3.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.