Higher Error Rate After 2.14 Update

After updating to 2.14 I’ve noticed the error rate over time has increased. I have a 4 hour running average of the error rate for monitoring and its increases from 0.5% to 0.7% without changing settings. My average stat polls the API every 60 seconds.

I’ve seen people complain and revert to 2.13.x but I was wondering what is the reason for a higher error rate? Sometimes I feel like knowing the error rate is detrimental to the experience since I’m trying to min max the efficiency and error rate.

My rudimentary understanding would be the new websocket polling changes how often the error rate is computed. The actual error register value is the same but with faster updates the number of “good” hashes has decreased leading to a higher percentage.

Otherwise love the update!

1 Like

Internally in the ASIC the error rate is a counter. So it shouldn’t be different if the rate you read it is different. It’s possible the way it’s converted to a percentage is skewing the values now it’s read more often (once a second, instead once every 5 seconds before websockets).

1 Like

That’s nothing,My device show 100% error and 400Ths

Than the asic is defect. With the newest firmware versions we changed to actually read the asic registers and with that you now see issues that have not been visible before. Even if older versions show you hashrate that looks nominal it won’t show issues because we never read them previously