Author

Topic: [Open Source] MicroBT WhatsMiner Observability - Tooling/Help (Read 5 times)

?
Activity: -
Merit: -
Hiya Guys 

I switched from AntMiners to WhatsMiners (M30, M50) recently. If it wasn't for this forum and PlebMiners, I wouldn't be able to extract all I could from them and make them run smoothly. 

The issue: 

So, WhatsMiners tend to complain way more than AntMiners, especially about ambient temps and PSU temps. It seems to have more sensors though. Anyway, their UI is slow as heck, their software is Windows-only, and it isn't the prettiest thing ever. And again—gosh, why is it so slow? 

Anyway, my miners often stopped due to a bunch of errors, and I wanted to know exactly when and why it happened. So, during the weekend, I just glued some code together and wrote an observability tool for them using the regular API on port 4028 and added the much-needed Prometheus exports. 

[FREE AND OPEN SOURCE] 
You can check it out here: https://ubit.watch/ 
[FREE AND OPEN SOURCE] 

So, I need some help from programmers and non-programmers alike. If you have an M60, I would love the JSON dumps of the API. Also, if you're using an API version different from 1.4 and 2.1, I would be glad to receive them so I can improve my parser. 

Initially, this tool only watches your miner via the public API—it doesn't send any commands to it. But it would be cool to also work with their writable API. 

Anyway, I will say it again: IT IS FOSS (FREE AND OPEN SOURCE), which means it is NOT going to take your coins—it can't. You can audit it yourself. I've even hosted it on my own GitHub, etc. So basically, I am just seeking help and contributions. 

I've shared the software in some mining groups that I’m part of, mostly small miners like myself, and it was well received. Pretty sure this thing only targets small miners—huge miners have their own solutions, and we are often left in the dark or depend on some third party. 

I was tinkering with custom firmware too, but it is annoying, to be honest. Since I wanted to share it with a couple of friends, flashing a new/custom firmware would be a hassle. Doing it externally from a Raspberry Pi or old PC is much better. 

Whenever I release something open-source, there are tons of comments like "Garbage," "Trash," or "You should have done this instead." Honestly, I don’t care. The key is to cut through the noise; eventually, the right people show up, see the value, and join in to help. 

As it grows, I think we will be able to have an open-source solution for the shortcomings of MicroBT. And since it is highly customizable, it has the potential to become something pretty neat. 

Comments, help, and contributions are appreciated! 

Thank you, guys. 


Edit: Typos*
Jump to: