JohnD
|
|
June 14, 2014, 09:10:06 AM |
|
I know, then where is risk if I've given the bot for a time of 24 hours for example to buy low sell high ?
I can't get, really sorry.
The bot thinks the price is high now and sells everything you have. Then the prices rises and you have no chance to buy your coins back without loosing money. That is the risk.
|
|
|
|
svk31
|
|
June 14, 2014, 01:57:01 PM |
|
I bought the beginner license the other day and am currently testing it. It's having a hard time with Cryptsy, it's placing order's but when order's don't get filled rapdily they time out in the software and count as cancelled, but they remain open in Cryptsy.
I also lost one of my bots after restarting the server, which is quite annoying as it now has to rebuild all the transaction history. I also lost all the transaction history on the bot that remained, so now I'll need to deactivate it for several hours, bah..
Now another thing that's a major frustration, is the lack of flexibility in displaying transaction histories. Why can't I simply display the last 24 hrs; or 48hrs; or whatever timeframe I want? Surely that information can be downloaded somewhere and stored locally, so when you add a bot with a given pair on a given exchange, the software would download at the very least the previous 24 hrs of transactions!
It's also very frustrating to lose all the transaction history except for the last 480mins whenever you change any settings for an indicator, can't you store it locally and let us modify things as we want?
|
|
|
|
joshraban76
|
|
June 14, 2014, 02:10:22 PM |
|
I know, then where is risk if I've given the bot for a time of 24 hours for example to buy low sell high ?
I can't get, really sorry.
The bot thinks the price is high now and sells everything you have. Then the prices rises and you have no chance to buy your coins back without loosing money. That is the risk. At last I've got it, so it depends on speculation and luck.
|
|
|
|
JohnD
|
|
June 14, 2014, 03:04:22 PM Last edit: June 14, 2014, 05:05:44 PM by JohnD |
|
I cannot connect to CEX Api and i do not get prices/charts from Kraken.
i'm having the same issue with Kraken. Version 0.9.9.9 changelog states that Kraken is supported in beta stage... I can connect to CEX, and it works fine for a few hours to 1 or 2 days. Then, CEX tracking stops while other APIs continue to work fine. I have to restart HTS to get CEX to work again... CEX works for me now. It was only a temporary issue. Anyway... @dev: I would love to see full kraken support and i will definatly upgrade my license as soon as Kraken works. I do not really trust btc-e...
|
|
|
|
herbiehasher
Member
Offline
Activity: 100
Merit: 10
|
|
June 14, 2014, 09:42:43 PM |
|
Hey guys
I am continually getting Order failed or timed out on cryptsy and bitfinex, no matter the pairing of btc and alt coin. It was working 2 days ago, but not now. Shows as everything connected correctly on the API. I have been at it all day, and ready to give up on this bot. I have only been able to make 1 trade on 1 exchange, that's btce
|
|
|
|
herbiehasher
Member
Offline
Activity: 100
Merit: 10
|
|
June 15, 2014, 01:21:39 AM |
|
Hey guys
I am continually getting Order failed or timed out on cryptsy and bitfinex, no matter the pairing of btc and alt coin. It was working 2 days ago, but not now. Shows as everything connected correctly on the API. I have been at it all day, and ready to give up on this bot. I have only been able to make 1 trade on 1 exchange, that's btce
Changing from market order to limit order solved this issue for me.
|
|
|
|
svk31
|
|
June 15, 2014, 06:33:03 AM Last edit: June 15, 2014, 07:55:37 AM by svk31 |
|
Hey guys
I am continually getting Order failed or timed out on cryptsy and bitfinex, no matter the pairing of btc and alt coin. It was working 2 days ago, but not now. Shows as everything connected correctly on the API. I have been at it all day, and ready to give up on this bot. I have only been able to make 1 trade on 1 exchange, that's btce
Changing from market order to limit order solved this issue for me. I'm using limit orders but having issues with Cryptsy also. Here's an excerpt from my log from last night, the bot placed three orders to buy, all of which finally went through but the bot only registered one as successful., the last one. Which is why it kept buying when it shouldn't have.. 2014-15-06 02:10:01.404 |ORDER_STACK| {Cryptsy Buy 0.68302302 Drk @ 0.0178000 Btc/Drk} changed to status QUEUED 2014-15-06 02:10:01.443 |ORDER_STACK| {Cryptsy Buy 0.68302302 Drk @ 0.0178000 Btc/Drk} changed to status EXECUTING 2014-15-06 02:10:01.443 |ORDER_STACK| {Cryptsy Buy 0.68302302 Drk @ 0.0178000 Btc/Drk} changed to status EXECUTING 2014-15-06 02:10:01.804 |ERROR| Error executing public query: The remote server returned an error: (522) Origin Connection Time-out. 2014-15-06 02:10:36.863 |ERROR| Error executing public query: The remote server returned an error: (522) Origin Connection Time-out. 2014-15-06 02:10:52.084 |ERROR| Error executing public query: The remote server returned an error: (522) Origin Connection Time-out. 2014-15-06 02:11:06.956 |ORDER_STACK| {Cryptsy Buy 0.68302302 Drk @ 0.0178000 Btc/Drk} changed to status TIME_OUT
...
2014-15-06 04:22:49.090 |ORDER_STACK| {Cryptsy Buy 0.61973128 Drk @ 0.01765122 Btc/Drk} changed to status QUEUED 2014-15-06 04:22:49.092 |ORDER_STACK| {Cryptsy Buy 0.61973128 Drk @ 0.01765122 Btc/Drk} changed to status EXECUTING 2014-15-06 04:22:49.092 |ORDER_STACK| {Cryptsy Buy 0.61973128 Drk @ 0.01765122 Btc/Drk} changed to status EXECUTING 2014-15-06 04:22:50.507 |ERROR| Error executing public query: The remote server returned an error: (522) Origin Connection Time-out. 2014-15-06 04:23:05.548 |ERROR| Error executing public query: The remote server returned an error: (522) Origin Connection Time-out. 2014-15-06 04:23:40.610 |ERROR| Error executing public query: The remote server returned an error: (522) Origin Connection Time-out. 2014-15-06 04:23:55.647 |ERROR| Error executing public query: The remote server returned an error: (522) Origin Connection Time-out. 2014-15-06 04:24:06.073 |ORDER_STACK| {Cryptsy Buy 0.61973128 Drk @ 0.01765122 Btc/Drk} changed to status TIME_OUT
...
2014-15-06 04:36:05.275 |ORDER_STACK| {Cryptsy Buy 0.55760447 Drk @ 0.01765122 Btc/Drk} changed to status QUEUED 2014-15-06 04:36:05.278 |ORDER_STACK| {Cryptsy Buy 0.55760447 Drk @ 0.01765122 Btc/Drk} changed to status QUEUED 2014-15-06 04:36:05.278 |ORDER_STACK| {Cryptsy Buy 0.55760447 Drk @ 0.01765122 Btc/Drk} changed to status EXECUTING 2014-15-06 04:37:19.382 |ORDER_STACK| {Cryptsy Buy 0.55760447 Drk @ 0.01765122 Btc/Drk} changed to status COMPLETED 2014-15-06 04:37:19.391 |ORDER_STACK| {Cryptsy Buy 0.55760447 Drk @ 0.01765122 Btc/Drk} changed to status COMPLETED 2014-15-06 05:18:00.566 |ERROR| Error executing public query: The remote server returned an error: (520) Origin Error. 2014-15-06 05:19:05.747 |ERROR| Error retrieving wallet info from Cryptsy
Here's the trade log from the bot: PS. Notice that the bot sold at a loss even though the "overcome fee insurance" is activated. Gonna stop using Cryptsy I think.. Timestamp TradeType Buy Price Sell Price Last buy price Last sell price Earned Total earned Fee costs Total fee costs Total profit made 15/06/2014 00:05 Sell 0.0178110 0.018 -0.000000003953880 -0.000000003953880 0.00000004 0.00005011 -0.00005011 15/06/2014 04:36 Buy 0.01765122 0.0178110 0.00098424
|
|
|
|
svk31
|
|
June 15, 2014, 06:38:47 AM |
|
Another thing, I might be misunderstanding things here, but is there a reason why a buy signal should be blocked by a "last buy percentage drop loss" safety? 15/06/2014 08:06:24 Last buy percentage drop-loss: SELL 15/06/2014 08:05:43 Buy signal is being blocked by a safety signal. 15/06/2014 08:05:43 Last buy percentage drop-loss: SELL 15/06/2014 08:05:22 Last buy percentage drop-loss: SELL Coin position: sold, last buy at 581, two indicators producing a buy signal at 561; which was blocked by a sell safety??
|
|
|
|
krach
Legendary
Offline
Activity: 1851
Merit: 1020
Get Rekt
|
|
June 15, 2014, 08:17:16 AM |
|
It looks like your stop loss blocked a buy.
I suggest making a sperate bot only for drop loss- roof in so that it wont interfere with your other bots.
|
|
|
|
svk31
|
|
June 15, 2014, 10:26:27 AM |
|
It looks like your stop loss blocked a buy.
I suggest making a sperate bot only for drop loss- roof in so that it wont interfere with your other bots.
That doesn't make sense though, maybe you should add the "apply signal to sell/buy" like for the insurances. Tbh I'm less and less impressed by this bot, it keeps executing trades and thinking they timed out, while in reality the trades either went through or were partially filled. This just happened again on Bitfinex BTC/USD, and I'm not using big orders here, ~0.1BTC. So now it's basically stuck, and although it's in "bought" position edit:(might have been a UI bug, it's now correctly in "sold" position) and it's updated the last buy price, it's waiting on buy signals to fill the rest of the order, which it's tried to do twice but timed out every time once again.. I tried to use "force buy" as the price was now slightly lower than the original buy, but it failed because it's using an incorrect calculation of trade amount, not sure why, so an order got placed for more USD than I had left on the sold side. Should I be using market orders rather than limit orders to ensure the bot works correctly? Seems risky buy maybe not so much with tiny orders like mine..
|
|
|
|
BaseCrypt
Newbie
Offline
Activity: 56
Merit: 0
|
|
June 15, 2014, 12:13:32 PM |
|
Does this bot support trading a certain currency to another on an exchange when the price difference between two exchanges is less than or more than a set percentage?
|
|
|
|
krach
Legendary
Offline
Activity: 1851
Merit: 1020
Get Rekt
|
|
June 15, 2014, 12:30:13 PM |
|
It looks like your stop loss blocked a buy.
I suggest making a sperate bot only for drop loss- roof in so that it wont interfere with your other bots.
That doesn't make sense though, maybe you should add the "apply signal to sell/buy" like for the insurances. If the coin position was bought and a drop loss was triggered then the bot will sell, it should override the buy command in that case, I might be wrong but that is how I understand it. Since I have my personal stop loss on a seperate bot then I cant say exactly and have never had the problem you are talking about. Please open a ticket with the other issues regarding bitfinex. Thanks, Krach Does this bot support trading a certain currency to another on an exchange when the price difference between two exchanges is less than or more than a set percentage? No, this bot does not support interexchangeo arbitrage, however in the next release of the bot it will support "internal" arbitrage, arbitrage within one exchange.
|
|
|
|
JohnD
|
|
June 16, 2014, 06:13:17 AM |
|
Hi again, i am getting only failed orders on cryptsy now. It worked 2 days ago. 16.06.2014 08:09:01 Insurances agree on Buy command 16.06.2014 08:09:01 Buy signal produced by the trade indicator(s). 16.06.2014 08:09:00 Order failed or timed out: Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc. Reverting to previous position. 16.06.2014 08:07:58 Order failed or timed out: Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc. Reverting to previous position. 16.06.2014 08:07:57 Insurances agree on Buy command 16.06.2014 08:07:57 Buy signal produced by the trade indicator(s). 16.06.2014 08:07:57 Order failed or timed out: Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc. Reverting to previous position. 16.06.2014 08:06:54 Order failed or timed out: Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc. Reverting to previous position. 16.06.2014 08:06:53 Insurances agree on Buy command 16.06.2014 08:06:53 Buy signal produced by the trade indicator(s).
Debug Log: 2014-16-06 08:06:45.480 |ERROR| Der Index war außerhalb des Arraybereichs. 2014-16-06 08:06:53.981 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status QUEUED 2014-16-06 08:06:53.981 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status QUEUED 2014-16-06 08:06:53.981 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status EXECUTING 2014-16-06 08:06:54.437 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status FAILED 2014-16-06 08:06:54.443 |ORDER_STACK| Order Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc failed: Error placing Cryptsy order: Insufficient BTC in account to complete this order. 2014-16-06 08:07:57.935 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status QUEUED 2014-16-06 08:07:57.935 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status QUEUED 2014-16-06 08:07:57.935 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status EXECUTING 2014-16-06 08:07:58.408 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status FAILED 2014-16-06 08:07:58.414 |ORDER_STACK| Order Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc failed: Error placing Cryptsy order: Insufficient BTC in account to complete this order. 2014-16-06 08:09:01.539 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status QUEUED 2014-16-06 08:09:01.539 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status QUEUED 2014-16-06 08:09:01.539 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status EXECUTING 2014-16-06 08:09:02.712 |ORDER_STACK| {Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc} changed to status FAILED 2014-16-06 08:09:02.718 |ORDER_STACK| Order Cryptsy Buy 20,81142877 Ltc @ 0,0165040 Btc/Ltc failed: Error placing Cryptsy order: Insufficient BTC in account to complete this order.
Any ideas what is going on?
|
|
|
|
JohnD
|
|
June 16, 2014, 09:39:51 AM |
|
Seems like the bot is calculating wrong with the trade amount. I tried to trade with a fixed NXT amount and market orders on cryptsy but it does not work. Any ideas why? 2014-16-06 11:38:03.573 |BOT_INFO| Bot: Cryptsy Message: Insurances agree on Sell command 2014-16-06 11:38:03.578 |BOT_INFO| Bot: Cryptsy Message: Trying to sell the coins... 2014-16-06 11:38:03.583 |ORDER_STACK| {Cryptsy Sell 1000 Nxt @ Market Price} changed to status QUEUED 2014-16-06 11:38:03.588 |ORDER_STACK| {Cryptsy Sell 1000 Nxt @ Market Price} changed to status QUEUED 2014-16-06 11:38:03.588 |ORDER_STACK| {Cryptsy Sell 1000 Nxt @ Market Price} changed to status EXECUTING 2014-16-06 11:38:03.601 |BOT_INFO| Bot: Cryptsy Message: Order sent to TradingEngine: Cryptsy Sell 1000 Nxt @ Market Price 2014-16-06 11:38:03.719 |BOT_INFO| Bot: Cryptsy Message: Order failed or timed out: Cryptsy Sell 1000 Nxt @ Market Price. Reverting to previous position. 2014-16-06 11:38:03.725 |BOT_INFO| Order failed or timed out: Cryptsy Sell 1000 Nxt @ Market Price 2014-16-06 11:38:03.730 |ORDER_STACK| {Cryptsy Sell 1000 Nxt @ Market Price} changed to status FAILED 2014-16-06 11:38:03.740 |ORDER_STACK| Order Cryptsy Sell 1000 Nxt @ Market Price failed: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
|
|
|
|
trubar
Newbie
Offline
Activity: 37
Merit: 0
|
|
June 18, 2014, 07:02:39 PM |
|
I have insurance: Cancel open order after 10 minute(s). My order is not commited. Why? Does anyone have the same problems?
Bitfinex - log
18.6.2014 17:59:41 Order failed or timed out: Bitfinex Sell 2,03612148 Ltc @ 9,7462 Usd/Ltc. Reverting to previous position. 18.6.2014 17:59:41 Insurances agree on Sell command 18.6.2014 17:59:41 Sell signal produced by the indicator(s). 18.6.2014 17:54:53 Order failed or timed out: Bitfinex Sell 2,03612148 Ltc @ 9,7427 Usd/Ltc. Reverting to previous position. 18.6.2014 17:54:32 Order failed or timed out: Bitfinex Sell 2,03612148 Ltc @ 9,7427 Usd/Ltc. Reverting to previous position. 18.6.2014 17:54:32 Insurances agree on Sell command 18.6.2014 17:54:32 Sell signal produced by the indicator(s). 18.6.2014 17:49:44 Order failed or timed out: Bitfinex Sell 2,03612148 Ltc @ 9,73733333 Usd/Ltc. Reverting to previous position. 18.6.2014 17:49:24 Order failed or timed out: Bitfinex Sell 2,03612148 Ltc @ 9,73733333 Usd/Ltc. Reverting to previous position. 18.6.2014 17:49:24 Insurances agree on Sell command 18.6.2014 17:49:24 Sell signal produced by the indicator(s). 18.6.2014 17:44:35 Order failed or timed out: Bitfinex Sell 2,03612148 Ltc @ 9,74906667 Usd/Ltc. Reverting to previous position. 18.6.2014 17:44:15 Order failed or timed out: Bitfinex Sell 2,03612148 Ltc @ 9,74906667 Usd/Ltc. Reverting to previous position. 18.6.2014 17:44:14 Insurances agree on Sell command 18.6.2014 17:44:14 Sell signal produced by the indicator(s). 18.6.2014 17:39:26 Order failed or timed out: Bitfinex Sell 2,03612148 Ltc @ 9,77556667 Usd/Ltc. Reverting to previous position. 18.6.2014 17:39:06 Order failed or timed out: Bitfinex Sell 2,03612148 Ltc @ 9,77556667 Usd/Ltc. Reverting to previous position. 18.6.2014 17:39:06 Insurances agree on Sell command 18.6.2014 17:39:06 Sell signal produced by the indicator(s). 18.6.2014 14:50:11 The trade amount is invalid.
|
|
|
|
silverston
|
|
June 18, 2014, 07:58:48 PM |
|
18.6.2014 14:50:11 The trade amount is invalid. because
|
|
|
|
trubar
Newbie
Offline
Activity: 37
Merit: 0
|
|
June 18, 2014, 08:45:51 PM |
|
18.6.2014 14:50:11 The trade amount is invalid. because That was before I set "AllInWallet". Do I have to manualy set amount of cryptocoin? i dont think soo.
|
|
|
|
trubar
Newbie
Offline
Activity: 37
Merit: 0
|
|
June 19, 2014, 03:01:44 PM |
|
18.6.2014 14:50:11 The trade amount is invalid. because That was before I set "AllInWallet". Do I have to manualy set amount of cryptocoin? i dont think soo. I set amount manualy and there is still a problem.
|
|
|
|
krach
Legendary
Offline
Activity: 1851
Merit: 1020
Get Rekt
|
|
June 19, 2014, 04:09:38 PM |
|
Hi, If anyone is having trouble with bitfinex please open a ticket and you will get a link to an update that should solve the problem. -Krach
|
|
|
|
bigdave
|
|
June 19, 2014, 04:15:27 PM |
|
Hi, If anyone is having trouble with bitfinex please open a ticket and you will get a link to an update that should solve the problem. -Krach
Can you clarify what the issue with Bitfinex is?
|
|
|
|
|