Re: [Awesome Miner]- Powerful Windows GUI to manage and monitor up to 5000 miners

Thanks a lot for getting back to me Patrike,

That made some sense now, to have a current entry and an x-minutes ago entry that need to match. I tried a few variations of that as well. Also just for the heck of it I threw a timer trigger in between them on another test ( I know you said its not necessary). I hate to be a bother but I looked thru my logs and within 10 minutes I dipped under 200 but only for a few seconds here and there and it triggered. Its frustrating, every variation of the rule I've tried still triggers even if I dip down under 200 for a few seconds, I'll attach those 2.

https://postimg.org/image/xns7ji6tn/

https://postimg.org/image/pjoos6hej/

I take this still as "currently" it dipped under 200, and "3 minutes ago" at some point it dipped under 200. I know for a fact it didn't stay under 200 for more than a few seconds so I have to be missing something or something else is going on.

Thanks again for the help!

I guess it's possible to have a dip both "now" and "3 minutes ago". Can you try to add a third trigger as well, where you also check for example "5 minutes ago"? Just to test the scenario.

Thanks Patrike,

I have 3 time triggers now, current, 1 minute ago and 3 minutes ago and tested for over 24 hours now. Its the same situation (of course triggered a little less often adding the 3rd time variable). Still though if I dip under 200 "3 minutes ago" and "1 minute ago", then again "currently" for even a second in all of those timeframes, it triggers. I cant believe no one has brought this up before.

Do you have any other thoughts on how to implement a simple trigger of below x hashrate for x time?

In my situation I was just after below 200MH/s for 30 seconds consecutive then trigger to restart the miner.

Thanks again.

I agree that it would be a nice improvement to add a trigger that is looking at hashrate for a specific time like you suggest.
If you look at the actual hashrate in your scenario, is it dropping below 200MH/s that many times within a few minutes? What's the standard hashrate when everything is working fine?