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

I would like that as well, but for the Beginner licence 

Its finally getting better after few weeks 

You don´t understand me - I am already using dots as decimal places, but haasbot automatically changing dots to commas on various places. Its mainly to show how parameters are set, but also to count with them. Take a look at this screenshot as for an example - there is price change insurance set by 0(dot)5% but shown like 0(comma)5%. If I doubble click this insurance, next window with 0(comma)5% will appear:



Does not matter that price drop is not shown at all (another issue), when I now click "close", on next interface refresh 0.5% changes to 5%



This is rooted throughout whole haasbot, so it basically mean it's useless for EU non-dots countries

EDIT: New update released during my post, I´ll edit my post after some testing

Version 0.9.9.1 has just been released to solve all the recent reported problems.

This are the points that are changed within this version.
- New: Option added to the server settings to activate the trade-bots on start
- Improvement: More information added on insurance messages
- Bugfix: Missing signals page for the safeties added (applies only to web-interface)
- Bugfix: Speed problem is solved
- Bugfix: Backtest/benchmark issues with the all-in and percentages solved (for as far as possible)
- Bugfix: Usage of the comma decimal in the Classic Windows Interface is fixed (use dots!)
- Bugfix: Small improvement to the feeovercome insurance (it did fall back to 10% for some reason)

To install the update just restart the software and you will get the update form. It is not expected you may lose your trade-bots or settings on this update.

Is there anywhere somekind of guide to set up some basic strategies for simple trading bot?

Try to use dots as decimals characters. Most of the users are from the USA and so the dot is the base decimal character inside the software.

The high trade-amounts displayed at the backtest/benchmark where caused by another fall-back. I have changed it to the absolute values to "solve" this. But still i do not expect this will work out as everybody might expect. At All-in and Percentages the wallet amount does not get changed and so the trade-amount does not follow the changes caused by simulated trades.

@Demonxaian:
The activation of the trade-bots will be an option under the Server settings. If you want you can enable it here. Last buy ans sell price are saved and restored too now. (i undo these changes)

@kalross:
The roof-in problem requires more time from my side to backtrack the cause of that. I will continue the update first and then i get back on it. I am sorry i have to move this one for this moment.

It works well from beginning, eg. if I set trade amount to 90% and have 0,135 BTC on BTCe account, it will correctly count trade amount as 0,121 BTC. But after running backtest, I end up with trade amount of 8999999,1 BTC (and all test trades in tradfe log are made with this huge amount). I suspect this to be somehow caused by decimal place issue (. and ,) because numbers are shown with commas in Windows interface - If You set number as 1,5 then comma is ignored and number is changed to 15. So If You trade 0,121 then You will end with 121 instead. There is nothing I can do about that, as its fully automated process for example:

I have 1 BTC, set trade amount to 95% and result is 0,95 BTC which turns to 95 BTC..

Is this issue based on region? I mean if in US numbers are shown with dot and in EU with commas? And please note that this is related to windows interface - I dont know if its the same with web interface, because I dont have a time to play boring "click´n´wait" game.


With previous issue, while everything with decimal places separated with comma is turned to non-decimal numbers its quite dangerous (even percents are affected, so 0,5% changes to 5%)..

I am planning to fire up virtual machine with clean US version of W7 instalation to find out if this issue persist in different environment (and to test whether web interface is faster on clean PC). But I don´t know when, as I have little time

Good day to try out the new version...not ;-)

The percentage based trading amounts can go wrong...might just be the benchmark that messes up the calculation (eg.  9999999.0 Btc (AllInWallet))  I've only seen this in LTC/USD and BTC/USD on BTC-E

Also,  the Dynamic Roof In is triggering a Buy signal, but order is not being placed?  I also had two failed Buy and revert back  to Sold position (just before LTC/USD ramped up over $2 (now $3.20 swing...ouch).  Could have done with this working today :-(

The charts after a benchmark have a rogue value at the beginning of the plot which changes the scale of the chart to the extent it can not be read.

Also, links to Safeties Charts in Current Signals Page don't work at the moment.  They are fine from Configuration.

Last thing.  Chromium browser has a gap on the left side of the web gui.

Web interface is nice and fast.  Great...

Cheers.

K

@Demonxaian:
Those things that you reports are by design. The trade-bots do not get activated directly on start to prevent any unprofitable trades. (i have seen them happening over here) And the last buy and sell price are deleted for a reason. From the trade-bot side its impossible to see what you did in the time that trade-bot was deactivated. In the situation you have traded yourself then those last prices are not valid anymore.

About the alt-coins... those are not tracked from the main server. Only the high volume currencies are being tracked. (one exception; Doge/Btc is tracked too because i got a lot of requests to add this one)

@all:
Little update...
- I can confirm the , and . issue from the Windows Classic interface
- I can confirm the speed issue (its something that was left over from testing)
- I can confirm a problem with the feeovercome, the 10% fall-back becomes effective in some situations (the percentage price change is temponary adviced)

All reported issues are under control over here and i am on the watch if something else comes in the coming few hours. After this time i will issue a speed update to solve there reported issues directly.

Please know: there is no danger because of these reported issues.


I also got a small question, based on this comment:

At the current moment the time-out of all orders is 2 minutes. Once the time-out becomes effective the order gets cancelled and if the trade signal still exists then the trade-bot will place a new order. This new order is placed on the new market prices. Doing this gives a slight advantage because in general the new market prices are just a little bit better.

But what i want to know if there is interest to make this adjustable, and if so would that mean the time out itself become bigger or smaller?

im not really sure auto tune works on all altcoins.

Issues I have found in the new update so far:

- The bot does not automatically activate anymore, which is quite a problem if you have the setting activated that the launcher will run on start-up, everyone will think the bot is trading however its not activated at all... seems we will have to activate this manually until it is fixed.

- The total trades made, total profits made and last buy and sell price all seem to reset when the server is closed, thus when you restart the server this could result in losses. The Trade Logbook still records the prices so you can re-enter them manually.

- Auto-tuning of the tradebot does not seem to work on Cryptsy alt pairs, for example (dodge/LTC, dodge/BTC, FTC/BTC, FTC/LTC)

I hope these can be worked on since they might result in losses and decreased usability of the Trade-server.

Demonxaian

ok, after some test I see sell command work and new option like Order failed or timed out: Sell 0,1 Ltc @ 0,02919 Btc/Ltc. Reverting to previous position. working too. But, how I can setup the timeout for order. Sometimes @ slow pair ( Ltc/Btc) 5min is not big trouble.
@Stephan
Yes I confirme. Interface so slow in my i7, 8gb Ram and Google Chrome

Hey I forgot something. Sometimes you can get those trade ammount errors due to using a . or a ,
In europe people use a , where in the USA you use a . and vice versa. Go back and check what works , or .  -- that might be causing the problem.

@g0re79:
If you give the software a minute or so to collect the Fee and Wallet from the API then the first issue can not be happening. Updating this information is NOT instant to prevent flooding of a API/exchange, it asks a minute or so to fetch up. Only when really needed the software forces a update on those values for example just before trading. (this is made this way to prevent flooding of a exchange, you could get blocked if this happens from the software side)

I will have a look to the usage of . and , values. Thats indeed a flaw as you report. (edit: Confirmed inside the Windows Classic interface)


@g0re79 and @silverston:
Can you both post some details on the speed problems? I am very supriced to read this is not going faster then before because benchmarks here are showing me a different story over here. (testing on a both a crappy Intel Atom with 2GB and Core i7 with 8GB here)

I have special interest in knowing which APIs you are both connecting to.


Please know this is just a notification message, its not a blocker or insurane. The idea is that is shows you trade-amount is invalid, nothing more.

In general, if you have setup your trade-amount properly then this notification will not show itself. Unless the software is trading, at that moment this is a expected message.

The software itself does not do much with the wallet information. The only real effective way the wallet is used is as a 3-level fallback to confirm if a order is excuted and progress or not. (but this is only used of the first 2 methods of backtracking a order fails) Be right back on this...


About the "Overcome fee costs".... no changes where implemented inside that insurance so it should work exactly as before. The only thing that could go wrong in this insurance is that is does not know the exact fee percentage. But in that case the software simply takes 10% to be fully sure. Way to much of course, but it is a last line of defense against losses thats why its so high. The 10% should go away as soon as the real fee percentage is collected by the API itself. (normally after a minute after setting up the trade-bot)

Edit: i will have a look to the feeovercome... (a quickfix would be to fall-back to the percentage change insurance, it does the same but you can set the percentages yourself in this insurance)

What exchange are you having problems with?
Have you made sure that your API keys have proper permissions?

Try the following steps:

1) Open your debug log by rightclicking the system tray icon.
2) Make sure all messages are displayed.
3) Open the wallet inside of the bot and browse to your exchange, this should generate some readings in the debug log.

Check the above readings, post them here if you need help.

The bot was having some problems reading values from the wallets (especially BTCe) prior to the update but for me but this has been working flawlessly ever since.


Having the same problems as you regarding the "Overcome fee costs -Insurance" though, but I haven't really looked in to it yet.

I did a clean install - and downloaded the new version of the bot, downloaded the new API keys.

As for the sell signals, have you made sure to update your API keys?

Yeah, this version is full of bugs.
 All sale signals are blocked by insurance. When you try to sell writes that there is no money in you wallet, although the money in your wallet sees

How its possible, if ammout is 0.1 and bought @0.02799 and now price was 0.0285

 Its slow as hell as before (quad core CPU / 8G RAM) - confirmed

Furthermore all amounts with decimal places are shown as xx,xx (comma) but have to be set as xx.xx (dot). Pretty confusing, as when You want to change something, fields are prefilled with amounts with commas and have to be rewrited to dots before submitting.

Theese are just 3 flaws I found in ten minutes, so its probably even worse..

@silverston:
Your welcome.

---------------
@All:

Update to version 0.9.9.0 released.

Within this update there is a lot of improvement on the stability, order verification and speed and memory improvements.

These are the listed things from the change log:
- Exchange disabled: BTCChina has been temponary disabled (there is a backdoor to re-eneable this)
- Trade Indicator added: POC_Reversed (same as the POC, but the signal is reversed)
- Trade Indicator added: ROC_Reversed (same as the ROC, but the signal is reversed)
- Trade Indicator added: IndicatorEarningsProcentagePrice (enter the amount in percentage you want to earn on your trading)
- Trade Indicator added: Aroon
- New: Supported added for trade-amount in All-in and Percentages
- New: Support added for the beginner license
- Improvement: Weighted prices are used now. (EMA pattern)
- Improvement: Trading engine improved in general.
- Improvement: Error/warning messaging improved.
- Improvement: Web-interface renders 50 up to 200 times faster now.
- Bugfix: BTC-e BTC wallet reading fixed.
- Bugfix: No more possible virtual/ghost orders in the log

A few things that i totally forgot to add was the increasement in backtesting time (its now 48-hours) and a lot of small web-interface improvements. Just to make things easier and better to control. For example, i have extended the trade-bot overview so some things can be accessed a lot faster. Or there is now a shortcut inside the Current Signals -page to open directly the settings of the safety/indicator.

The only thing that we could not add in time was the login for the web-interface. This is delayed till the next update. I am really sorry for this but i wanted to make sure its really secure, not something that can be hacked very easy. Broadcasted solutions and/or VPS solutions are wanted targets for hackers after all.

Please note: Before you execute this update write first down your strategies. Because those will be deleted because of the nature of the changes inside this update.

For the next update we are planning to get back to adding new features, indicators and even a new exchange!

I (and my team) hope this update will really fix ALL the issues reported the past time. The testers agreed on this and we hope, you as end-users will to.