Re: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic]
currently my bot is trading with cryptsy same way like previous post with my little profits. Now I cant even say if it was cryptsy or STB... 
I am now on MACD 2min, StochRSI 2min and changed Stochastic Oscilliator 4 min (test).
Only change one value at the time and then compare the trade signals in live trading to have them give signals at the same time. Stephan explained that in a very early post.
Yes some orders are placed and not filled yet cause of cryptsy candle movement. At least the bot is not stuck now and keeps placing order at the right time and I just wait that the orders are fulfilled. In the last 2 days I didn't need to take any losses by manual manipulation.
Further I feel I keep it going like this for a while and get ready to buy the full version to trade all pairs on cryptsy that I have available.
I am now on MACD 2min, StochRSI 2min and changed Stochastic Oscilliator 4 min (test).
Only change one value at the time and then compare the trade signals in live trading to have them give signals at the same time. Stephan explained that in a very early post.
Yes some orders are placed and not filled yet cause of cryptsy candle movement. At least the bot is not stuck now and keeps placing order at the right time and I just wait that the orders are fulfilled. In the last 2 days I didn't need to take any losses by manual manipulation.
Further I feel I keep it going like this for a while and get ready to buy the full version to trade all pairs on cryptsy that I have available.
Hmmm... And how the hell You did it?
Code:
2014-28-02 02:37:51.676 |TRACKER_INFO| Reading of Cryptsy failed, retrying....
2014-28-02 02:37:51.897 |TRACKER_INFO| Reading of Cryptsy failed, retrying again....
2014-28-02 02:37:52.134 |TRACKER_INFO| Reading of Cryptsy failed, next retry on next update.
2014-28-02 02:37:52.258 |ERROR| The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
2014-28-02 02:37:52.361 |TRACKER_INFO| The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
2014-28-02 02:37:52.460 |BOT_INFO| Checking trade-bot: Cryptsy - DRK / BTC
2014-28-02 02:37:52.566 |BOT_INFO| Bot: Cryptsy - DRK / BTC Message: Polling failed, no prices are availible for Cryptsy at DrkBtc.
2014-28-02 02:37:51.897 |TRACKER_INFO| Reading of Cryptsy failed, retrying again....
2014-28-02 02:37:52.134 |TRACKER_INFO| Reading of Cryptsy failed, next retry on next update.
2014-28-02 02:37:52.258 |ERROR| The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
2014-28-02 02:37:52.361 |TRACKER_INFO| The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
2014-28-02 02:37:52.460 |BOT_INFO| Checking trade-bot: Cryptsy - DRK / BTC
2014-28-02 02:37:52.566 |BOT_INFO| Bot: Cryptsy - DRK / BTC Message: Polling failed, no prices are availible for Cryptsy at DrkBtc.
BTW: That same happens when I switch to wallet overview in web interface - same errors as above and
EDIT: My final conclusion - Haas can connect to Cryptsy, read wallets stats (and maybe even place orders), but can´t read any actual prices. Its strange, because according to a log print screen on my first post in this page Haas was able to read prices..