Topic: margin terminal - over 25 spot and futures exchanges! Bots and more - page 58. (Read 268864 times)

1. How can I draw on the graphics?
2. How to fix the tool tips to make them display properly. They seem to be out of scale.

Okay, just used to trade new strat - 0.3 lost.
Must be bad configured :3

02/14 01:48:52 pm bittrex:BAT/BTC: no result in return message. Error string: "APIKEY_INVALID".
02/14 01:48:52 pm bittrex:BAT/BTC: Network error in buffer[2](active orders: LocalError (as Error): error querying active orders: Http post of method market/getopenorders failed, with error string "APIKEY_INVALID".
 -- erased old log entries --
02/14 01:49:23 pm bittrex:BAT/BTC: no result in return message. Error string: "".
02/14 01:49:23 pm bittrex:BAT/BTC: error parsing orderbook data: Http post of method public/getorderbook failed, with error string "".
02/14 01:49:23 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:24 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:25 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:26 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:27 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:28 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:29 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:30 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:31 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:32 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:33 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:34 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:35 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:36 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:37 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:38 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:39 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:49:40 pm bittrex:bot:BAT/BTC: [strategy-1] Could not check for sell signal: Could not estimate current price: Queried orderbook is empty
02/14 01:50:39 pm bittrex:BAT/BTC: [Method:public/getorderbook (params: &type=buy) ] error in DefaultMarketInterface::httpPOST: network error: [http code: 503(Service Unavailable)]: ServiceUnavailable (the server is unable to handle the request at this time.) (try 1 of 10), message received: http://www.w3.org/TR/html4/strict.dtd">

02/14 01:54:00 pm bittrex:BAT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post of method market/getopenorders failed, with error string "APIKEY_INVALID".
02/14 01:54:43 pm bittrex:BAT/BTC: [Method:market/getopenorders (params: ) ] error in DefaultMarketInterface::httpPOST: network error:  Timeout (the connection to the remote server timed out) (try 1 of 10)
02/14 01:54:44 pm bittrex:BAT/BTC: ticker data update failed (Error while parsing ticker: json2::TypeError: asObject called on non Object, message was: {
  "message" : "",
  "result" :     null,
  "success" : true
}
)



And this is how trades are missed. Because of this a 5% profit trade was missed.
@JON is there anything that can be done about this? For Bittrex to reply that the API is invalid it surely means that Leonardo is somehow sending an incorrect API?
I dont know if the errors afterwords have anything to do with that API INVALID error.

Unfortunately these were not end-for-end trades where leonArdo can keep track of where it was when it was shut down (don't worry I already put in a service request for that). I had updated leonArdo several times during the week, one to get current with production, another for a key change up and another update to grab some fixes. You are only seeing the top exchange there are actually 5 instances running for different exchanges but I still needed to stop them all for the updates.

For the most part the losses you are seeing is because it did not know where the original buy price was when I shut it down. Profitability is one of the things I need to figure out this week. I hesitate to make changes to the main server which is still running 3.6.0 with many more mArgin maker bots on other exchanges and they are doing pretty fair right now in this sideways slightly upward movement.

So many factors to consider Bittrex's tremendous loss of volume vs. Binance's credibility. Dang if you do dang if you don't. At present I do not have a clear answer for you on strategies or exchanges.

Dang man that looks like some wicked scalping your doing there, good luck with your taxes on that LOL 

But it looks like your just running BB and sometimes your selling at a small loss, in long run are you finding that BB strategy profitable?

Thanks a lot!

This is a long shot but i have 2 more questions.

1. How can I draw on the graphics?
2. How to fix the tool tips to make them display properly. They seem to be out of scale.

Right click on the "new strategy" icon. This saves all strategies currently running and it will restart them (albeit in "suspended" mode ) when Leonardo restarts.

Question.
My PC often freezes due to overheating problems (gotta find some time to clean it) and when i resume the session my saved strategies are gone.

Is there any way to save them ?

No, it's not, Leonardo has to fulfil the buy-part in total first. Or vice versa ...

Thank you for the info!

But, in my case there was a lot of money left for the trading Bot to run with.  Therefore, I feel my trouble is with communication from Binance to leonardo.  Binance is to slow or wrong parsing and than leonardo stops the Margin Bot.  But please note the manual trade setups work and are posted correctly by leonardo.

See log ...
02/12 12:53:26 pm binance:websocket:handler:EOS/ETH: Error parsing channel message for order book: Waiting for initial order book request to be answered
received document:
{"stream":"eoseth@depth","data":{"e":"depthUpdate","E":1518468806212,"s":"EOSETH","U":22307304,"u":22307304,"b":[["0.01042500","57.20000000",[]]],"a":[]}}
02/12 12:53:34 pm binance:websocket:base: No response received. Connection to server lost.
02/12 12:53:36 pm binance:websocket:base: Restored connection to the server.
02/12 12:55:24 pm binance:websocket:base: No response received. Connection to server lost.
02/12 12:55:26 pm binance:websocket:base: Restored connection to the server.

I'm not overly concerned, but I hope Dev team can't fix it in the next update.

I used to have similar problems with the margin maker on binance....

My problem was that the bot made the first buy order and was unable to set up a sell order for the exact same amount further on.

I mitigated it by having at least some small amount extra lying in the wallet for sales.

Had no time to get deeper into that but will probably try it out again when i go on to the next pair on binance.

I consider this just as a small glitch, because i know that leonArdo has trouble if you set up a bot for any pair where you have no coins at all beforehand.
EDIT: I meant, i know that leonArdo has trouble when you try to set it up to go 'all in' on any pair.


Greetings,

hacky

Can anyone tell me what would happen if order would fill partly in new trading strategy?
Would it try to sell if it's good time to do so?

Total difference calculations appear to be off in Bollinger Bands for binance, causing much of the other stats, on the Buy+NextSell tooltip, to be incorrect.  In my case with the ETH/USDT pair. It seems that Binance is a real problem child. The low fees are great and all, but I may have to head back to Bittrex. It's getting really messy.

EDIT: Many of the binance calculations appear to be off, so this may not specifically be a leonardo problem. I pulled up the website, and the trades look fine. I pulled up the mobile app, and some of the totals look pretty whacky. The problem may be within the api reporting.

+1. Running fine for me 24/7 from several days using many BB on linux too.
The only crashes that happened to me were always when I closed a margin maker window without stopping it first (because I forgot it).

There's a bug with DATETIME in russian translation - it says MM/dd hh/mm/ss instead of actual time in logs/history.
Don't you think Russians can guess time from static words? 

Yes, I have some time on the exchange with Bollinger Band Bots only running from my Linux laptop 24/7. No issues to report.

Here's my log for a typical Binance bot killing moment!

02/11 01:58:41 pm binance:EOS/ETH: Network error in buffer(active orders): LocalError (as Error): http error while requesting open_orders: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/11 01:59:21 pm binance:EOS/ETH: Network error in buffer(trades): LocalError (as Error): http error while requesting completed_trades: [http code: 400(Bad Request)]: ProtocolInvalidOperation (the requested operation is invalid for this protocol), Message: "Timestamp for this request is outside of the recvWindow." (Code: -1021)
02/11 02:07:39 pm binance:websocket:base: No response received. Connection to server lost.
02/11 02:07:54 pm binance:websocket:base: Restored connection to the server.

Hmm well, I haven't been trading a lot on Binance, only some manual trading and part-time bot trading, but haven't noticed any issues like that. The app itself is open 24x7, no crashes. I'm planning to setup some strategies on Binance for 24x7 bot trading, will report here if I encounter these problems.

Is anyone running Binance Bot trading working 24/7

Thanks a lot gnoe!

I'll let Christian know!