Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic]

[cpusher]

• In the past weekend i was backtesting a lot. I got a lot "Haasonline Trade Server has stopped working"
  From the last 10 crashes i made screenshots from the Windows problem details like "CLR20r3" , "APPCRASH" (kernelbase.dll), "System.OutOfMemoryException" if Stephan needs this.
  
  I see the memory footprint of HTS is high mostly over 1700MB. I think it leaks lots of memory on backtesting/autotuning (30+ times) and then crashes.
  Mostly after autosetup/autotune and the values are negative. Because haasbot.com is not caching all alt-coins(it should if you really want to support alt) i have to wait hours to start and building hours of track... (i prefer a week/month of backlog!). maybe add an api to HTS to add my own ticks from my own (tobuild)caching server?
  
• The profits of Cryptsy are totaly wrong in the tradelog, it shows 10% feecost in the tradelog!?
• A lot of time after a save and restart or a crash i loose all my tradebot settings
• when my trade amount is higher then my wallet (because of losses), it blocks trading and i lose even more money.
• on windows start, i was stuck in the updater. HTS was not running for hours, losing money
• lots of time in the debug i see HTS thinking it had a succesfull trade, after hours i found out and had to correct(change coin position) manually.
• today HTS pages are not parsing and get the #indicator.data fields(now its ok again)
• using the HTS api from my own scripts is resulting in a lot of refreshes/unwanted redirections when i check the website manually the same time
• simulation time should be the time of the moment it was of the simulated trade, now its the time of the simulation action. (i really want to compare it to the real market)
• At the moment i get no Cryptsy tracking at all:

Code:

2014-03-03 09:41:27.870	|TRACKER_INFO|	Reading of Cryptsy failed, retrying....
2014-03-03 09:41:28.214	|TRACKER_INFO|	Reading of Cryptsy failed, retrying again....
2014-03-03 09:41:29.183	|TRACKER_INFO|	Reading of Cryptsy failed, next retry on next update.
2014-03-03 09:41:29.198	|ERROR|	The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
2014-03-03 09:41:29.292	|DEBUG|	System.Net.WebException: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
		   at System.Net.HttpWebRequest.GetResponse()
		   at Cryptsy.CryptsyAPI.CryptsyQuery(Boolean authenticate, Dictionary`2 args)
		   at Cryptsy.CryptsyAPI.GetOpenMarkets(Boolean basicInfoOnly)
		   at TradeServer.Trackers.API.CryptsyTracker.UpdateTracker()

Am i the only one with this Cryptsy problems?

Stephan, we have wonderfull features now, and if they worked stable they are very valueable. I hope you see its really time to put the next effort in fixing bugs and memory leaks. Also i hope the other customers agree to wait for new features in return for a stable release.

cpusher

[solarion]

Latest update seems to have nuked my setup. It seemed fine, but deleted all my api keys so I began adding them back in. Btc-e & cex.io went perfectly...then I tried cryptsy again(this has never worked) and everything went dark. Now nearly any interface selection results in the "something went wrong blah blah" message.

Edit: Deleted everything from directory save license file, extracted old version, and updated again. Everything works...but no apis. This time I added the cryptsy api key first.

It nuked that install too.

Done with cryptsy till this issue is addressed.

[Stephan224]

Small update released
An small update have been released to solve hopefully all the trading issues of Cryptsy and the recent ones of Bitstamp. Besides the API changes some minor things where done do. The new Aur and Nxt coins are added, the wallet shows how a total BTC amount of your wallet and the Windows Classic interface now supports setting up the API credentials.

As usual the update goes automatic. Just restart your software and you will be notified about the update.

Tests have shown all exchanges are fully operational again. But in rare cases the order tracking of Cryptsy will fail. We are looking still into this and if we found the case and solution then we will push another update. But because of the other issues we have already pushed this update.

The coming time i will spend most of my time on stability and durability of the software. I will put a temporary hold on the new features (except the web-login) until everything is stable as a rock.

[silverston]

Small update released
An small update have been released to solve hopefully all the trading issues of Cryptsy and the recent ones of Bitstamp. Besides the API changes some minor things where done do. The new Aur and Nxt coins are added, the wallet shows how a total BTC amount of your wallet and the Windows Classic interface now supports setting up the API credentials.

As usual the update goes automatic. Just restart your software and you will be notified about the update.

Tests have shown all exchanges are fully operational again. But in rare cases the order tracking of Cryptsy will fail. We are looking still into this and if we found the case and solution then we will push another update. But because of the other issues we have already pushed this update.

The coming time i will spend most of my time on stability and durability of the software. I will put a temporary hold on the new features (except the web-login) until everything is stable as a rock.

Great!
But my Simple trade bot dont working anymore. API connected but nothing show.

[krach]

update working well.
has anyone been able to trade on cex.io?

[Stephan224]

update working well.
has anyone been able to trade on cex.io?

Small tip: Using the Windows Classic interface you can press "Buy now" or "Sell now". This will force the trade-bot to respond and it will show you if trading is working or not. (i am trading at Btc/Ltc on Cex.IO)

About the STB... i will have a look this eve if i can make it working again. But the general recommendation is just to move over to the new software. There is a donation license at the ready to make this possible for free (for the old users!) and using the Windows Classic Interface you have the same kind of interface again. Functional and technical the new software is better.

[solarion]

I haven't tried cryptsy since the last update, but everything seems to be running smoothly on btc-e and cex.io with 0.9.8.2. Thanks Stephan, it's nice to see a dev that responds promptly to client complaints.

[krach]

cryptsy seems ok, but I have to go through and see if I spot a pair that is not working.
Where is the "classic interface" I cant get to it. It is the old school STB style interface ,right?

[Stephan224]

I haven't tried cryptsy since the last update, but everything seems to be running smoothly on btc-e and cex.io with 0.9.8.2. Thanks Stephan, it's nice to see a dev that responds promptly to client complaints.

Your welcome.

cryptsy seems ok, but I have to go through and see if I spot a pair that is not working.
Where is the "classic interface" I cant get to it. It is the old school STB style interface ,right?

You can change it in here:

[trubar]

Cryptsy still does not work (however it is reading prices in log).

Total in wallet on bought/sold side is 0. Walllet overview is empty (btc-e and cryptsy).

Going back to build 0.9.7.0. Can you desable autoupdate messages (somekind of a checkbox in settings)?

ftcBtc trade wont work... can you increase price decimals... i think because of that wont work.

[eyegoatboy]

update working well.
has anyone been able to trade on cex.io?

Small tip: Using the Windows Classic interface you can press "Buy now" or "Sell now". This will force the trade-bot to respond and it will show you if trading is working or not. (i am trading at Btc/Ltc on Cex.IO)

About the STB... i will have a look this eve if i can make it working again. But the general recommendation is just to move over to the new software. There is a donation license at the ready to make this possible for free (for the old users!) and using the Windows Classic Interface you have the same kind of interface again. Functional and technical the new software is better.

hi steph bot looking good ,so after picking what pair to trade what is the sequence of things to do before hitting the activate button,
what ive been doing is pick a pair(btc-e BTC-USD) to trade enter amount(1btc) pick insurance(overcome fee)
pick indicators(stochRSI AND MA-HISTOGRAM) then goto edit trade indicator select update speed( 2min stochRSI & 4min MA-HISTOGRAM )
then hit add last 480 save close then hit auto tune wait check trade book happy activate bot


https://i.imgur.com/WagwsuP.jpg

[throwaway222]

Hi Stephan,

I am having trouble with the safeties and also getting inconsistent results with the backtest feature.

- overcome fee costs will allow one trade then prevent subsequent buys for some reason (not because of the fees)
- only sell higher - I'm still getting trades that aren't profitable with this feature turned on
- only sell above double fee cost - as for the only sell higher. this is giving me unprofitable trades

- the backtest feature gives me different results each time I run it. This is after clearing statistics and last buy/sell each time.

I have a screenshot showing the unprofitable trades (at home, I'm at work now), and I'm happy to provide a trade log too.

Thanks

[silverston]

@Stephan
In classic interface I dont see a current price of currency

[throwaway222]

http://iforce.co.nz/i/c1gucjzt.sqn.png

This is a screenshot of using the percent price change with 1% wanted raise on sell. I get the same results using "NeverSellCheaper" and "SellAtDoubleFeeCosts". I'm just after an insurance that doesn't sell at a loss.

edit: I should also point out that the trades that are profitable *before* fees don't follow the 1% rule either. 1% of $5xx is around $5; most of those trades are within $2.

Thanks

[silverston]

This is a screenshot of using the percent price change with 1% wanted raise on sell. I get the same results using "NeverSellCheaper" and "SellAtDoubleFeeCosts". I'm just after an insurance that doesn't sell at a loss.

edit: I should also point out that the trades that are profitable *before* fees don't follow the 1% rule either. 1% of $5xx is around $5; most of those trades are within $2.

Thanks

if you want 100% profitable trades, use OvercomeFeeCost-insurance

[silverston]

@Stephan
I have issue with classic interface. Interval 30-60sec.

[trubar]

Cryptsy

Debug log:

5.3.2014 15:23:48 1000 coins bought for a price of 0,00006300, the last sell price was 0,00006361
5.3.2014 15:23:47 Order sent to TradingEngine: Buy 1000 Doge @ 0,00006300 Ltc/Doge
5.3.2014 15:23:47 Trying to buy the coins...
5.3.2014 15:23:47 Insurances agree on trade command

Trade log:

5.3.2014 15:23   Buy   0.00006300         0.00006361         -0.00630000      

BUT on cryptsy web page there is no such buy. It has happened 3 times today (before it didn't work).

[dszuecs]

Cryptsy

Debug log:

5.3.2014 15:23:48 1000 coins bought for a price of 0,00006300, the last sell price was 0,00006361
5.3.2014 15:23:47 Order sent to TradingEngine: Buy 1000 Doge @ 0,00006300 Ltc/Doge
5.3.2014 15:23:47 Trying to buy the coins...
5.3.2014 15:23:47 Insurances agree on trade command

Trade log:

5.3.2014 15:23   Buy   0.00006300         0.00006361         -0.00630000      

BUT on cryptsy web page there is no such buy. It has happened 3 times today (before it didn't work).

+1

Trades showing up in Debug Log are actually not taking place on cryptsy.

[Stephan224]

If you read something like this:

5.3.2014 15:23:48 1000 coins bought for a price of 0,00006300, the last sell price was 0,00006361
5.3.2014 15:23:47 Order sent to TradingEngine: Buy 1000 Doge @ 0,00006300 Ltc/Doge
5.3.2014 15:23:47 Trying to buy the coins...
5.3.2014 15:23:47 Insurances agree on trade command

Then there is something wrong with the API connection, or to be specific the API credentials. This is how a normal situation look like:

2014-05-03 09:32:03.069   |BOT_INFO|   Bot: New Trade-bot Message: Trying to sell the coins...
2014-05-03 09:32:03.070   |ORDER_STACK|   {Sell 0,5 Ltc @ 0,02467944 Btc/Ltc} changed to status QUEUED
2014-05-03 09:32:03.070   |BOT_INFO|   Bot: New Trade-bot Message: Order sent to TradingEngine: Sell 0,5 Ltc @ 0,02467944 Btc/Ltc
2014-05-03 09:32:05.861   |ORDER_STACK|   {Sell 0,5 Ltc @ 0,02467944 Btc/Ltc} changed to status COMPLETED
2014-05-03 09:32:05.864   |BOT_INFO|   Bot: New Trade-bot Message: 0,5 coins sold for a price of 0,02467944 and bought before for 0,0 making total profit of 0,0

As you can see this log shows the ORDER_STACK at work. The order was QUEUED first and then it was COMPLETED. (more info see: https://www.haasbot.com/engine-orderstack/)

I recommend to setup a new API key, check if you wallet works and try a manual trade. The manual trade can be done in the web-interface at the "Exchange now" -page and inside the Windows Classic interface that is still missing. But you could use the "Buy now" and "Sell now" buttons inside the trade-bot to work around it.

BTW Based on the log i also see a bug inside the software itself, the order should not have been reported as "bought". So the message "1000 coins bought for a price of 0,00006300, the last sell price was 0,00006361" is a bug from my side. This should have been blocked. I am looking into this.

[dszuecs]

hi Stephan

Thanks for your feedback.

Generating a new API Key doesn't change anything
Keep up your good work

Cheers