Pages:
Author

Topic: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic] - page 78. (Read 416703 times)

member
Activity: 85
Merit: 10
sure, but if speed is the issue then the only way I see to make it faster is to lower your time, I might be wrong there though. There will be some changes that happen so fast that it will be hard for a bot or for a human to get the buy or sell order in fast enough.
Could be an issue, what did it look like on the bot graph? Did the colour reflect the same indication as in the bot signal graph?
I had ok results with 20 seconds but yea everyone should test it out for themselves.

I get "attempted to divide by zero" not sure what I did to get this notification in the debug log


I don't need it faster.  It Sold on interval 3 before the indicators had received all the data to generate any signal at all.  The bot signal was at the SELL position from interval 1-3 and the MACD didn't chart until interval 24 (as the Long was set to 24) which was correct and as programmed.  The RSI interval didn't chart until interval 13 as programmed.  The bot indicators shouldn't generate a signal until all the required ticker data has been received.
full member
Activity: 213
Merit: 100
The 600s interval I used was benchmarked over several days on PPC and worked well without issues.  It is however experimental, but has not simulated unprofitable results.

Is it possible for you to share your strategy or do you keep it secret? Grin
legendary
Activity: 1851
Merit: 1020
Get Rekt
sure, but if speed is the issue then the only way I see to make it faster is to lower your time, I might be wrong there though. There will be some changes that happen so fast that it will be hard for a bot or for a human to get the buy or sell order in fast enough.
Could be an issue, what did it look like on the bot graph? Did the colour reflect the same indication as in the bot signal graph?
I had ok results with 20 seconds but yea everyone should test it out for themselves.

I get "attempted to divide by zero" not sure what I did to get this notification in the debug log
member
Activity: 85
Merit: 10
"So...set a well benchmarked set of indicators including an MACD-MA Short 11 Long 24 for NMC/BTC.  Update timer at 600s.  Ticked Reset Last Buy and Sell.

Last sell price 0.00  Last Buy Price 0.00

Had sold some BTC to buy NMC/USD and PPC/USD expecting a strong upward trend (I was right on both counts).

Activated Bot and it sold NMC at 0.00801 at Interval 3 with two (of two) indicators on Yellow.  Was unable to buy back in quick enough as immediately afterwards, NMC/BTC went to 0.0085 then 0.00886.  Kinda bad luck combined with mental bot logic (or 'features' as some on here call them).

Missed out on a 10% profit.  Baaaa!

I take it the bot should not trade until the indicators have collected sufficient data according to their settings?

Stephan:  Can you reproduce/fix this?

K
"

-Was unable to buy back in quick enough-
Hi,
You have it set on 600 seconds so the bot will wait at least 600 seconds before the next action, I think.  I think Stephan has said many times, the bot is not faster than manual trading, the main advantage is that the bot does not have any emotions. If you want quick trades put it on 20 seconds, imo.



Thanks for your contribution, but not sure you have fully understood the issue I (and one other) are reporting.  I've been studying the bot for a few months, so not unfamiliar with its function.  The bot SHOULD NOT have sold whilst one of the indicators (let alone both) were not sending a BUY/SELL signal.  However, it did.  If this is indeed a bug...somebody might suffer a great loss if large amounts are committed to trading.  Luckily...I am a relatively 'poor' trader, so damage was quantitatively limited, though not really as a proportion of my total coin.  Life goes on however.

If my word is not sufficient, then I can show this with screen capture as soon as I find time to host the image.  An issue tracker would be helpful for a piece of development software like STB.

I couldn't buy back in manually around the same price (using BTC-E web ui) because the price jumped immediately after the bot sold (which is why I set the bot up to begin trading there) and didn't return which was a particularly annoying effect of the issue I am reporting (supported by one other user)...but not directly related to the bot.  I had to adapt a well thought out strategy to limit my losses...the outcome of which was not losing 10% of my investment with a panic buy...but by sacrificing the profit I would have made.

Stephan doesn't recommend the 20s Update Timer and has removed it in the coming release, so it would not be wise to recommend its use to other traders.  Longer intervals work better as has been reported.  The 600s interval I used was benchmarked over several days on PPC and worked well without issues.  It is however experimental, but has not simulated unprofitable results.

Yes the bot doesn't have any emotions and neither does it know when its coding has errors.  Only the developer can investigate this.

Cheers.

K
legendary
Activity: 1851
Merit: 1020
Get Rekt
"So...set a well benchmarked set of indicators including an MACD-MA Short 11 Long 24 for NMC/BTC.  Update timer at 600s.  Ticked Reset Last Buy and Sell.

Last sell price 0.00  Last Buy Price 0.00

Had sold some BTC to buy NMC/USD and PPC/USD expecting a strong upward trend (I was right on both counts).

Activated Bot and it sold NMC at 0.00801 at Interval 3 with two (of two) indicators on Yellow.  Was unable to buy back in quick enough as immediately afterwards, NMC/BTC went to 0.0085 then 0.00886.  Kinda bad luck combined with mental bot logic (or 'features' as some on here call them).

Missed out on a 10% profit.  Baaaa!

I take it the bot should not trade until the indicators have collected sufficient data according to their settings?

Stephan:  Can you reproduce/fix this?

K
"

-Was unable to buy back in quick enough-
Hi,
You have it set on 600 seconds so the bot will wait at least 600 seconds before the next action, I think.  I think Stephan has said many times, the bot is not faster than manual trading, the main advantage is that the bot does not have any emotions. If you want quick trades put it on 20 seconds, imo.

member
Activity: 85
Merit: 10
kalross
it was reply, yes. I have same issue.
 I dont like unprofitable trades  Smiley

Oh ok.  Looks like a bug then...easily fixed I would assume.
hero member
Activity: 952
Merit: 502
SAPG Pre-Sale Live on Uniswap!
kalross
it was reply, yes. I have same issue.
 I dont like unprofitable trades  Smiley
member
Activity: 85
Merit: 10

I do not understand how this is possible?
 Bot sold  earlier than necessary. But if I turn on the benchmark, then nothing happens ...
RSI standard and MACD-MA Short 26 Long 48, Signal 22.  Update timer at 180s
Second, bot do not buy, although the signal was in the benchmark. same settings
I do not know if I put the long timeframes  more than 5 minutes, the bot does not react at all.

Sorry.  Is this a reply to my issue or are you asking a question?

I have a screen shot to show the sell signal before indicator values were sufficiently supplied with data.

hero member
Activity: 952
Merit: 502
SAPG Pre-Sale Live on Uniswap!
Bot just sold before indicators had sufficient data (both yellow) and it happened right before a rocket in NMC (which I predicted).  Screwed me again!

Update:

Sorry...was repairing the damage like a headless chicken as you could imagine  :-S

So...set a well benchmarked set of indicators including an MACD-MA Short 11 Long 24.  Update timer at 600s.  Ticked Reset Last Buy and Sell.

Last sell price 0.00  Last Buy Price 0.00

Had sold some BTC to buy NMC/USD and PPC/USD expecting a strong upward trend (I was right on both counts).

Activated Bot and it sold at Interval 3 with two indicators on Yellow.

I take it the bot should not trade until the indicators have collected sufficient data according to their settings?

Maybe it is a 'feature', but I would consider it a bug.

K


I do not understand how this is possible?
 Bot sold  earlier than necessary. But if I turn on the benchmark, then nothing happens ...
RSI standard and MACD-MA Short 26 Long 48, Signal 22.  Update timer at 180s
Second, bot do not buy, although the signal was in the benchmark. same settings
I do not know if I put the long timeframes  more than 5 minutes, the bot does not react at all.
member
Activity: 85
Merit: 10
So...set a well benchmarked set of indicators including an MACD-MA Short 11 Long 24 for NMC/BTC.  Update timer at 600s.  Ticked Reset Last Buy and Sell.

Last sell price 0.00  Last Buy Price 0.00

Had sold some BTC to buy NMC/USD and PPC/USD expecting a strong upward trend (I was right on both counts).

Activated Bot and it sold NMC at 0.00801 at Interval 3 with two (of two) indicators on Yellow.  Was unable to buy back in quick enough as immediately afterwards, NMC/BTC went to 0.0085 then 0.00886.  Kinda bad luck combined with mental bot logic (or 'features' as some on here call them).

Missed out on a 10% profit.  Baaaa!

I take it the bot should not trade until the indicators have collected sufficient data according to their settings?

Stephan:  Can you reproduce/fix this?

K
legendary
Activity: 1851
Merit: 1020
Get Rekt
When bitcoin got around 300 I think the bitstamp api usage just got overloaded, they have not been able to totaly fix it since then, it doesnt have anything to with the bot, same with cryptsy. I have the same problems at cryptsy, it works well for a while then there are 50 open orders.
sr. member
Activity: 449
Merit: 250
Software developer
@throwaway222:
Its based on 2 times 0.2% fee because you need make a complete trade cycle (buy->sell->buy), so you need to trade twice and that needs to be taken in account to overcome the fee-costs.


Spoken about fee-costs... some users pointed me to a bug within the fee-overcome safety. I just released version 0.9.0.12 beta to solve this problem. If you use the safety then i recommend to update to this new version.

No other changes where made to this version. And version number 0.9.0.11 is skipped, in case you think you missed it
newbie
Activity: 15
Merit: 0
I can't figure out how the minimum raise and drop are calculated.

I'm using BTCe with 0.2% trade fees.

I would expect the minimum raise would be a factor of 1/(1-0.002^2) = 1.004012 times (or 0.4012% higher than) the buy price *just* to break even on the two 0.2% fees. If you were to split this into buying and selling then I'd expect factors equal to 1/0.998 or close to 0.2% on each.
The minimum raise and drop appearing in the bot are significantly lower than 0.2% for me.

I had a play around and it looks like your minimum raise/drop is based on my trade amount and twice the 0.2% fee. If this is the case, could you explain why? I'm having trouble understanding how this works.

I had the bot make unprofitable trades with higher sell than buy prices due to fees, hence the question.

Thanks
sr. member
Activity: 449
Merit: 250
Software developer
@dldavis007:
Very good analysis, my compliments for that.  Smiley

rzabol:
At the the current moment its still related to cryptsy his API, the past days i have seen some problems too. But yesterday i already saw some improvements. But i need to say cryptsy is on the nomination list to be deleted as a supported exchange. I am receiving to many complains about non-response in there API. My advice is to hold your trading for at least a day or two in the hope the API will be responsive again.

@testik1:
I know you love to complain, it so easy isn`t it? No, i have not 3000 users. Divide it by 3 or 4 and you are getting more close to the real number (registered users btw). Smiley But the point is, i know you having problems with Bitstamp. Some other do have this problem too. I am aware if this, this is a fact to me. Like it is also a fact there are hundreds of users who have no problems with Bitstamp.

No matter what kind of improvement i will introduce to solve issues like open orders and so on, it will never be 100%. Thats just totally impossible, yes we are getting closer and closer. But we will never make it totally perfect. Yes i am aware you think the API of Bitstamp is solid, but that is something that if not true. There are just things which i can not control. You noticed the two missing ticks, well this is a great example how solid the API itself is... why do you think 2 where missing? Exactly, because the API did not respond. No prices came back, so the software wait till its next interval. It only logical, keep on pushing to get prices will not solve the API issue. Time solves it, so waiting a few seconds is the most logical course of action. (it are also the rules at API of the exchange)

And like i told before, the bot send an order. If the order gets accepted then the coin position will switch. The position can not switch if the order is not accepted by the exchange. So i think bitstamp accepts your order but it does not get progressed for some reason. I will have a short look into the API if this is changed or something.

BTW This is that you know in advance; The core API DLL files of the exchanges are reused for the coming update.  Wink

 
newbie
Activity: 3
Merit: 0
Hi Stephan,

I have some problems with cryptsy. The bot make orders but on crytpsy that orders are not realize because of price changes and it stay in open orders. Problem occur with half orders so for that moment the bot is useless there. Additionally I don't know if it is ok but the bot make orders even if the previous is still in open orders what has effect like on image.
http://i.imgur.com/8O5ki6c.jpg

On btc-e that problem doesn't occur and there everything works fine.
Do you have any idea what is wrong with cryptsy or what I should to do to avoid that problem?
newbie
Activity: 8
Merit: 0
Fuck this..

The bot "trades" on bitstamp and shows that everything worked fine.. that I made some money..
http://i43.tinypic.com/xqj3b5.jpg

but when I look at bitstamp NO TRADES HAVE BEEN MADE.

This is the BOT'S FAULT! Even if bitstamp's api didn't work, which I don't believe, the bot should give the error.

It can't go on claiming I've made profits when it hasn't even realized the trade.

I hope the new version will fix crap like this. :\

Also, if this is true "3 comment which i am totally unable to solve" and "this is less then 0,1% of the users", there would be over 3000 STB users..which would mean a fortune for the seller of the software.

Also.. there is something more broken with the Bitstamp-connection.. The chart looks okay (1500 ticks, 100sec), but when I saved the data to a file the file contains TWO TICKS so it's totally worthless.. and now when I try to benchmark with the data seen in the chart (without opening a file) it only uses the timeframe since saving the file. There's some discrepancy between what is shown on the chart, and what the bot acually uses for tick data.
member
Activity: 66
Merit: 10
If I buy the software now will I get the upgrade that is coming out or should I wait?
Obviously you will get it mate
newbie
Activity: 30
Merit: 0
subhead,

Quote
can you please share your indicator combination with the public? i´m still trying to improve the outcome every day but i´m still not satisfied at all with the bot.

I like the PPO indicator and have tried using it several times, I've also tried using it with a stochastic indicator, but no matter what I do, it seems like it always buys in too late and sells too late.  I've also tried different trade intervals with the update timer.  Anywhere from 20 seconds up to 5 min, but still didn't have any luck.  The longer intervals seem to make the buy late and sell late problem even worse.

Another problem I've seen with using just these indicators, is that the bot would sometimes make a unprofitable trade (usually just a few cents).  I assume that when the bot sells, the price could fluctuate slightly, and the small difference causes the loss of a few cents. 

Anyway, I decided to try out the "Price Change Indicator" (for some reason the indicator list shows it as a "Price Difference Indicator").  I set the "Sell at Price:" to about 3 times the exchange fee, just to make sure that I would always make a profit.  I played around with the "Buy at Price:" and decided that it probably works best at a very low value.  The "Buy at Price:" requires that the market price drop below the last Sell price, so a lower value here will require less of a drop in case the trend continues to go up after the sell.

By itself, this indicator will make a few profitable trades, but it is limited by the fact that it will often Sell too soon (it will sell even if the price continues to climb), and it will often stop trading because the price does not always drop back below the last Sell price.

So, once I was happy that my trades would always be profitable, I decided to add the ROC Indicator.  The default values "Buy at -0.005" and "Sell at 0.005" are actually about right for most trading.  I usually tweak them slightly if it looks like the indicator is not selling and buying often enough.  I've used values from 0.0045 to 0.007 with good results.

The addition of the "ROC indicator" prevents the "Price Change Indicator" from immediately selling once it is satisfied, usually making trades more profitable.  The other benefit is that it waits for the price to start dropping before it indicates a sell.  This helps to ensure that the price is lower than the last Sell price which the other indicator wants before it will purchase.

So basically, the "Price Change Indicator" just makes sure that the trade is profitable, while the "ROI Indicator" Buys and Sells at the appropriate trend reversals.

The only problem I've seen so far is that the bot will sometimes get stuck in a sold position waiting for the price to drop below the last sell price.  I typically keep an eye on it and change the text box with the last sell price considerably above the current price.  This will cause the bot to begin trading again at the appropriate buy price.


Here are my settings for BTC-e trading LTC:

Update Timer       180 sec                           (3 minutes)
Trade Amount       20 ltc                              (or whatever you want, if BTC you will need to calculate a different Sell profit price for the "Price difference Indicator")
Last Sell Price      Current price + $5.00      (this will allow the "Price Change Indicator" to start trading)
Drop Loss             $20.00                            (or whatever you want)

In the advance settings, make sure you check the "Disable minimum raise/drop safety".  You can leave the other advanced settings at default. I believe that I set the "Drop Loss adjustment time out" to 3600 with a drop loss of 95%

The indicators are set up as follows:

Price Difference Indicator (Sell at profit price: 0.3, Buy at drop price -0.02)                                   (buy and sell trade fees will be around 10 cents for LTC)
Rate of Change Indicator (Offset 0, Reference 10, Buy level > -0.005, Sell level < 0.005)


Please try this with a small amount at first just to make sure it works like you want.  Also try it with the benchmark test.


Good luck.

Darrell





As far as improvements to the bot, it would be nice if the "Price Change Indicator" was named consistently in the lndicator list and it would also be great if the requirement for the price to drop below the last Sell price could be disabled.

The "Rate of Change Indicator" works okay, but it is confusing. I think that the negative and positive numbers are swapped in the settings displayed in the indicator list.  The Indicator list shows that Buying is a negative number, while the dialog box for set-up shows it as a positive number.









member
Activity: 75
Merit: 10
it happend again. buying works great but the selling part not. i stop using bitstamp right now.

cheers,
subhead

edit: i created an new api key. let´s see if the problem happens again.
sr. member
Activity: 449
Merit: 250
Software developer
It would be consistent with the reports i have, but that does not solve the problem itself.
Pages:
Jump to: