Skip to content
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

API to check miner status or configure mining pool #223

Open
PSLLSP opened this issue Nov 7, 2023 · 7 comments
Open

API to check miner status or configure mining pool #223

PSLLSP opened this issue Nov 7, 2023 · 7 comments

Comments

@PSLLSP
Copy link

PSLLSP commented Nov 7, 2023

Nerdminer has WiFi connectivity and it has IP address. I can ping it, ping works. Unfortunately, I cannot find any API to check status of the miner, to check firmware version, uptime, hashrate, temperature, number of solved blocks, etc, etc

There is well defined API for miners, it is documented here

I think that implementing such API will open new possibilities for NerdMiner. It will be possible to run local monitoring server that will report status of each miner, to save data to log file, to change configuration from user friendly UI...


cgminer has simple PHP page to access API, an example.There were advanced management systems for cgminer API, one of them was Minera. Unfortunately, Minera, it is not maintained anymore... It was replaced with systems like HiveOS those are more universal and with great support.


Another useful function for network API will be "identify", it could be that LED at NerdMiner will blink for few seconds or that API can define color of LED and LED will shine that color for few seconds. Could be useful to find a troublemaker. In the case you have just one NerdMiner, that is not really useful but one you have more, you will find such feature useful...

@sany3001
Copy link
Contributor

sany3001 commented Nov 8, 2023

I would love to have this status too. It would be nice to have it as another screen on device or accessible via REST API or both.

@Webranger2
Copy link

That would be great. then I could integrate that into the iobroker

@dwightmulcahy
Copy link
Contributor

I added #203 for something like this, too!

@ChimpRocket
Copy link

ChimpRocket commented Apr 18, 2024

+1 for this as well but it would be great if you return it using some of the bitaxe api naming conventions in api Bitaxe, then we can easily include in the same monitoring. :-)
Here's a sample

{
        "power":        13.359999656677246,
        "voltage":      4781.25,
        "current":      2795,
        "fanSpeed":     4503,
        "temp": 51,
        "hashRate":     655.23875991751333,
        "bestDiff":     "187M",
        "freeHeap":     177464,
        "coreVoltage":  1200,
        "coreVoltageActual":    1188,
        "frequency":    525,
        "ssid": "MySSID",
        "wifiStatus":   "Connected!",
        "sharesAccepted":       23563,
        "sharesRejected":       0,
        "uptimeSeconds":        287369,
        "ASICModel":    "Nerdminer?",
        "stratumURL":   "public-pool.io",
        "stratumPort":  21496,
        "stratumUser":  "bc1qy1111111111111111111111111111111111111.miner",
        "version":      "v1",
        "boardVersion": "1",
        "runningPartition":     "ota_0",
        "flipscreen":   1,
        "invertscreen": 0,
        "invertfanpolarity":    1,
        "autofanspeed": 0,
        "fanspeed":     60
}

I'm in the middle of writing a Netdata plugin to monitor the Bitaxe, so would be cool to standardise on api params for reuse within the OSMU projects.

Cheers

Thanks

@jeanfrodrigues
Copy link

its already been done?

@b-rowan
Copy link

b-rowan commented Jul 27, 2024

I am looking for this now as well, I have people asking about an integration with it. Happy to provide support on API design if needed, but my C is not the strongest...

Reference issue - UpstreamData/pyasic#176

@toberkel
Copy link

Any updates on this? Would love to have a little API

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants