Pages:
Author

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

newbie
Activity: 16
Merit: 0
In the basis settings,you can fill in the last buy /sell price,is this the amount for 1 coin  or the amount you want trade ?i want to use static trade amount  50SMC.
Do i fill in the price for 1 SMC or the 50SMC price ?Or just the current price/coin ?

or does this not matter ?do i need to fill it in ?Or can i leave it empty ?
newbie
Activity: 16
Merit: 0
Bot: LTCbot Message: Checking at price 8,093
2014-01-05 03:10:18.676   |BOT_INFO|   Bot: LTCbot Message: Indicators are in agreement of a buy command.
2014-01-05 03:10:18.677   |BOT_INFO|   Bot: LTCbot Message: Buy signal produced by the trade indicator(s).
2014-01-05 03:10:18.678   |BOT_INFO|   Bot: LTCbot Message: Calculated fee costs (1 unit): 0,0310061450, current change in price: -0,66292750 (Overcome fee costs -Insurance)
2014-01-05 03:10:18.679   |BOT_INFO|   Bot: LTCbot Message: Insurance does NOT agrees with trade (Overcome fee costs -Insurance)
2014-01-05 03:10:18.680   |BOT_INFO|   Bot: LTCbot Message: Insurance does not agree, trade is blocked. (Overcome fee costs -Insurance)

Bot is trying to buy ! should it not worry about the fee costs when its trying to sell ? i dont get it..

On the Overcome Fee Costs - Insurance edit page there is the option to have the bot check the fees when it's both selling and buying.  I'm guessing that you have both of those checkboxes checked which is why you're seeing what your seeing in the logs.

Indeed i did,disabled the Check indicator(s) buy signals.
Hope to see some trades happen now,thank you !
newbie
Activity: 39
Merit: 0
Bot: LTCbot Message: Checking at price 8,093
2014-01-05 03:10:18.676   |BOT_INFO|   Bot: LTCbot Message: Indicators are in agreement of a buy command.
2014-01-05 03:10:18.677   |BOT_INFO|   Bot: LTCbot Message: Buy signal produced by the trade indicator(s).
2014-01-05 03:10:18.678   |BOT_INFO|   Bot: LTCbot Message: Calculated fee costs (1 unit): 0,0310061450, current change in price: -0,66292750 (Overcome fee costs -Insurance)
2014-01-05 03:10:18.679   |BOT_INFO|   Bot: LTCbot Message: Insurance does NOT agrees with trade (Overcome fee costs -Insurance)
2014-01-05 03:10:18.680   |BOT_INFO|   Bot: LTCbot Message: Insurance does not agree, trade is blocked. (Overcome fee costs -Insurance)

Bot is trying to buy ! should it not worry about the fee costs when its trying to sell ? i dont get it..

On the Overcome Fee Costs - Insurance edit page there is the option to have the bot check the fees when it's both selling and buying.  I'm guessing that you have both of those checkboxes checked which is why you're seeing what your seeing in the logs.
newbie
Activity: 16
Merit: 0
Bot: LTCbot Message: Checking at price 8,093
2014-01-05 03:10:18.676   |BOT_INFO|   Bot: LTCbot Message: Indicators are in agreement of a buy command.
2014-01-05 03:10:18.677   |BOT_INFO|   Bot: LTCbot Message: Buy signal produced by the trade indicator(s).
2014-01-05 03:10:18.678   |BOT_INFO|   Bot: LTCbot Message: Calculated fee costs (1 unit): 0,0310061450, current change in price: -0,66292750 (Overcome fee costs -Insurance)
2014-01-05 03:10:18.679   |BOT_INFO|   Bot: LTCbot Message: Insurance does NOT agrees with trade (Overcome fee costs -Insurance)
2014-01-05 03:10:18.680   |BOT_INFO|   Bot: LTCbot Message: Insurance does not agree, trade is blocked. (Overcome fee costs -Insurance)

Bot is trying to buy ! should it not worry about the fee costs when its trying to sell ? i dont get it..
newbie
Activity: 59
Merit: 0
Please note: Trading fees of 0.2% at Cex.IO
In the past hours Cex.IO has added trading fee to its exchange. The Haasbot does not yet read this fee percentage and therefore can give losses. In recommended to temporary use the PricePercentage Insurance to stay clear of those possible losses (setup to 0.2% for Cex.IO). We will adapt and update the software as soon as possible to support this trading fees.

Edit:
Minor update released
A minor update of the haasbot has been released, bringing us to version 0.9.9.6. This version will add the new fee percentages of Cex.IO to the software.

Thanks for the fast update!
newbie
Activity: 38
Merit: 0
How can I fix it ??

No tracker data yet for BitStamp. Please refresh in a few minutes.
No tracker data yet for BTCe. Please refresh in a few minutes.
No tracker data yet for CampBX. Please refresh in a few minutes.
sr. member
Activity: 449
Merit: 250
Software developer
Please note: Trading fees of 0.2% at Cex.IO
In the past hours Cex.IO has added trading fee to its exchange. The Haasbot does not yet read this fee percentage and therefore can give losses. In recommended to temporary use the PricePercentage Insurance to stay clear of those possible losses (setup to 0.2% for Cex.IO). We will adapt and update the software as soon as possible to support this trading fees.

Edit:
Minor update released
A minor update of the haasbot has been released, bringing us to version 0.9.9.6. This version will add the new fee percentages of Cex.IO to the software.
newbie
Activity: 44
Merit: 0
If i want to upgrade from beginner license to simple license do i have to pay the full license ? Sorry if this has been answered repeatedly.

Edit: never mind just answered it by searching your site Smiley.

License update

If you require more trade-bots then you can always update your license. Updating can be done using a support ticket.
sr. member
Activity: 449
Merit: 250
Software developer
A minor update has been released
A minor update to version 0.9.9.5 has been released. This update will solve the 417 html error of Cryptsy, it will make sure the FeeOvercome works properly for Cryptsy again and of course the latest coins are added again.

- Alt-coin added: Ac, Wc, Cinni, Comm, Dmc, Karm, Rbbt, Emc2, Flt, Mn2, and Mry
- Alt-pairs added: (too many to list)
- Changed: Fee reading at cryptsy improved (its 100% working at 0.2% and 0.3% now)
- Changed: Spread order is temponary disabled/removed, it will come back better at version 1.0
- Improvement: Classic interface - Trade-bot list is sorted (the web interface will follow later on)
- Improvement: FeeOvercome slightly adjusted to better support trade-amounts < 1.0 (the effect is minimal)
- Bugfix: Cryptsy 417 html read error solved

The execute the update you only have to restart the software. A update form will show itself and from there you can proceed with the update.

--------------

Next we target a big update and these are our targets for this big update:

- A new/better way to install and update the software.
This idea comes from the forum here to have a better look how to issue coin and exchange updates faster. At the next update will will go over to use ClickOnce as a installer and updater. In general this must improve the installation (.NET4.5 dependacy) and it will streamline the updates better. At the same time Microsoft unit testing will give us the improved way to unit test the software before each release, making the testing time required shorter on the end.

- A improved trading engine with better support for spread orders and improved partially filled order tracking.
Currently in the new update the spread option is disabled, this is because it does not preform the way is must. In order to make this work we need to improve the trading engine. While we are at this we will have another look how to track parially filled orders better. These are the 2 main targets to improve the engine.

- Internal arbitrage
This is something we have on our wishlist for a long time now. When we started to design this software we wanted to keep this option open and at the next big update we will make this a reality. We will introduce arbitrage bteween 3 trading pairs on and and the same exchange. By trading between 3 pairs it is possible to gain from the instability between the pairs. Compare it to normal arbitrage but without the security risks and without the long coin transfertime. This concept will give less profits per full run, but can run more times and this way its even capable to gain more then normal arbitrage.

The initial introduction at version 1.0 will support a concept we call "Press a button". It will be the first implementation and it will be availible in all the licenses. (from beginner to advanced)

--------------

BTW If somebody is having issues with the API, payment, account or download, please submit a support ticket. We still try to respond within 24-hours.

BTW I was forced to stop due cryptsy, but i have expanded the online help again. More descriptions about the messages, errorcodes, trade indicators and how to configure the trade indicators are added. Please have a look at this link for details: https://www.haasbot.com/trade-server-help/
legendary
Activity: 1851
Merit: 1020
Get Rekt
MBTY
Did you create a support ticket at the site?
newbie
Activity: 41
Merit: 0
newbie
Activity: 44
Merit: 0
Anyone trading BTC/USD @Biststamp?
If so, what's your strategies?

Cheers
sr. member
Activity: 449
Merit: 250
Software developer
Yes, i can confirm now that the protocol has changed very, very slightly. I can also confirm within the software the security was to tight to accept this change. At the moment we are a little delayed because of all the searching we had to do but we have it running again here. We are proceeding with the tests to ensure everything works properly. Once this is done an update will be released. (within the coming hours)

This will be a minor update to solve Cryptsy only.

BTW: BTCChina is expected to be removed to the supported exchanges list.
newbie
Activity: 59
Merit: 0
https://www.cryptsy.com/pages/privateapi

Looks like changes need to be made to make things work right.
hero member
Activity: 966
Merit: 513
Cryptsy API setup had a spot for "username". That seemed to disappear right about the time it stopped working. Was that removed in the last haasbot update?
newbie
Activity: 59
Merit: 0
So, if you hit the cryptsy API manually it seems to be working fine.

Ideas?
full member
Activity: 184
Merit: 100
will try it out
newbie
Activity: 17
Merit: 0
I am getting sick and tired of the problems with this tbh.   6 months of hassle and LOSSES.   Dont you guys ever test anything?

Ive just entered my bot settings and API keys for the zillionth time after a "sorry something has gone wrong" message.

Bitstamp and Crypsys are both not working with the 417 API key error.

The Classic interface crashes constantly requiring system reboot.

Insurances dont always work, charts dont refresh, trade log is never saved, bots to go bought position instead of sold, bots sell low and buy high, or just dont trade at all

Arrgh.  This thing just isnt reliable.  I spend so much time looking at it I might as well watch the charts and trade manually.

Test it, fix it, test it and test it again, and if it still doesnt work right issue refunds.

newbie
Activity: 38
Merit: 0
Hi, I've never been able to get the CEX.IO API working. I get a funky error when i submit my details. The problem is defintely not my API key because if I enter an invalid API key I get a different error telling me the API is invalid. Anyone seen this or have any idea what the problem might be?

It has never worked, my account is fine on CEX.IO, I can log in fine etc.

sr. member
Activity: 476
Merit: 250
I´ve got a picture! Haha!
Hi,

A couple of hours ago the API of Cryptsy went offline. We (and we think you to) have seen errorcode 417. This means something is wrong with the webtraffic, the API of Cryptsy does not respond the way it should. Because no changes are reported or announched of the protocols we expect something is wrong at the API itself.

We keeping a close eye to the situation to see if we can do anything to restore the trading at Cryptsy. But for the moment there is nothing yet what we can do except waiting. But if needed (and possible) then we can issue a update very fast, we are on standby at the moment.

As far as the software goes, the other exchanges will just remain working on the software. Those are running in seperate processes and Cryptsy can not take them done while it offline.

In general it is not needed to stop the trade-bots of cryptsy. Except a few error notifications inside the log nothing can go wrong.

If we have more news to share about this then it will be posted again.

Stephan


It seems that I am cursed somehow - evertime haasbot works fine and I decide to jump in, it will break badly...

Edit: After some praising / woodoo / threats CEX.IO bot finally started to work. Reason unknown..
Pages:
Jump to: