-
Notifications
You must be signed in to change notification settings - Fork 177
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
Bot goes Idle and does not check once per minute the price #41
Comments
did u turn bot On in lower left corner .. see video in this case bot should do his work once a minute .. |
Yes I did turn the bot on, it checks the price once and adjust the order. The the bots goes into idle mode and does not awake again. |
https://pasteboard.co/J3i8ZhQ.jpg each minute bot should go from idle to working and there should be some output in console |
I got it working by creating a new API key with more permissions. One questions which does not belong to this ticket: Does the 10 min time frame from the UI apply to the bot, too? Like you can change the order price just once per 10 min? |
ill dblcheck what permissions bot needs and put in description but i assume manage orders for adjusting price and wallet for refilling .. as for adjusting price ... if lower price hash-power is available bot will try to decrease price every minute but it will be rejected by backend ... and order price will be actually preformed when backend will allow (this is once per 10 minutes) |
thanks for clarify and keep up the good work! |
Good job with the new bot! It's working (kinda) must a good tutorial to connect to the API.
When I place an order and active the bot, it checks the price once and adjusts my price. Afterwards, the bot goes into Idle and doesn't check the price any more. I expected the but to check the price once a minute (and see the output in the console). Do I need to do something to keep the bot running and check the price once a minute and adjust the price if necessary?
Edit: I run the Bot on win10 in a virtualbox
The text was updated successfully, but these errors were encountered: