 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
Mintpal is on the up. I don't see an API currently though.
|
|
|
|
|
Is Bitfinex Margin Trading supported or is it just Exchange trading?
Getting a lot of freezing on the web interface (server CPU getting hogged and memory leak, maybe due to benchmark functions).
|
|
|
|
|
This may have been mentioned, but the Ask and Bid prices are wrong way round in rules.
Also, could there be a leverage setting for Bitfinex so rules can be better compatible with margin trading?
Does the Bitfinex API have a facility to close/claim orders? If so, could this be facilitated?
Cheers.
K
|
|
|
|
- Trade bots settings disappear after trade server restart
I saw a corrupted bot message. Maybe related??? |
|
|
|
after updating the bot can not sell at all. 19.03.2014 6:38:02 Order failed or timed out: Sell 0,1 Ltc @ 19,18131067 Usd/Ltc. Reverting to previous position.
19.03.2014 6:36:46 There are open orders.
19.03.2014 6:34:37 There are open orders.
.......
19.03.2014 2:42:35 Order failed or timed out: Sell 0,1 Ltc @ 19,18131067 Usd/Ltc. Reverting to previous position. but no one open order now  so all three bots edit. after server restart the settings are not saved I've had a couple of disconnects from BTC-E resulting in failed trades and have to re-enter key to connect. K Update: Getting lots of this?  ?? 19/03/2014 23:47:26 Order failed or timed out: Sell 89.41866610 Ltc @ 17.17416667 Usd/Ltc. Reverting to previous position. 19/03/2014 23:47:26 Insurances agree on trade command 19/03/2014 23:47:26 Sell signal produced by the indicator(s). 19/03/2014 23:39:20 Order failed or timed out: Sell 89.41866610 Ltc @ 17.29500367 Usd/Ltc. Reverting to previous position. 19/03/2014 23:38:11 Order failed or timed out: Sell 89.41866610 Ltc @ 17.29500367 Usd/Ltc. Reverting to previous position. 19/03/2014 23:38:10 Sell signal produced by a safety. 19/03/2014 23:38:10 Dynamic drop-loss: SELL 19/03/2014 23:38:10 Order failed or timed out: Sell 89.41866610 Ltc @ 17.3081755 Usd/Ltc. Reverting to previous position. 19/03/2014 23:37:01 Order failed or timed out: Sell 89.41866610 Ltc @ 17.3081755 Usd/Ltc. Reverting to previous position. 19/03/2014 23:37:01 Sell signal produced by a safety. |
|
|
|
|
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
|
|
|
|
.... but how much profit would this bot actually generate if mining scrypt coins......
Depends on your settings :-) Anything between 0-100000000% ;-) |
|
|
|
almost crying when checking my great profit HTS shows me.  i see it made 20+ trades with 10% profit today, let's check... on cryptsy i see on of the first sell's still pending in the cryptsy orderbook. because of the downtrend i will only lose value. why did HTS think it could still go on trading while it was pending as order price dropped as hell and the order will be never filled like that. on top of that i see HTS took a another trade with again the trade amount. so i have 2*trade amount on my loss  HTS is really buggy and making big losses for me, hope we get the stable rock HTS asap. thanks for listening to my frustrations... Sounds like HTS placed the order then? The currency was falling so fast, that the order was not filled maybe? This can indeed happen unfortunately. The same may have happened if you'd have placed the order manually. A bot can give no guarantee of an order filling, only the market can fill an order. Exchange API (lag) or internet connection issues may cause this also. Cryptsy API can be unreliable. I've just returned to trading there after several weeks as it seems better. I understand your frustration. Trading is stressful at times. Maybe I can suggest a solution. QtBitcoinTrader has a facility to place an order + or - a percentage. This way, they order is more likely to filled, particularly when a currency is falling as you describe. It may be useful to have this facility in HTS, though it can make profit/loss calculations inaccurate unless HTS retrieves the order history and makes the calculations. Stephan. Is it possible to have a percentage adjustment to placed orders? K |
|
|
|
Hey Ighor, zero profit price in 1.07.97 beta 4 for OSX still seems off. E.g. PPC bought for 3.466, zero profit price says 3.481 while fee is 0.002% at BTC-e. Is there still a bug in the application or am I calculating wrong? Isn't the fee 0.2%? |
|
|
|
lol I've been trying to get this information out of him for the past 2 pages. The rule statement seems like it's missing something. If the rule was written like this (which is something we cant do since my orders last buy/sell price isn't in the second rule column) then I think we could easily get our desired results.
If market bid price > .6% of my orders last buy price (plus exchange fee) sell amount .01BTC at Market bid Price
or
If market ask price < .6% of my orders last sell price (plus exchange fee) buy amount .01BTC at Market Ask Price
+1 I got no idea what the conditional statement is referring to. |
|
|
|
Thanks for the tip
sudo padsp nasd -local -b
plays wav files for me but "beep" still make just a crackling pop
tried loop:
if market last price threshold $0.10 play wav
enable all rules
seems that it triggers just once and stops the loop - just shows processing afterwards but:
if market last price threshold %0.01 play wav
enable all rules
works fine so it must be somthing with $ part..
Aaahhh...run nasd through padsp does it. Great thanks |
|
|
|
|
Apparently routing audio to padsp is a way to get sound from OSS apps.
eg. pacat /dev/urandom > padsp
Is there any way of tricking ubuntu to route audio from /dev/dsp to padsp?
padsp QtBitcoinTrader doesn't work.
Great software...just can't test out rules etc... until I can get audio working (Xubuntu 12.10)
Cheers.
K
|
|
|
|
I, like others, was running the new version and the old version at same time since the new seemed to be lacking some features the old did well. Last night at midnight the old stopped working, won't update from exchanges. anyone else having this problem?
I did contact support but figured I'd check community too.
Same here. Would have been nice to get some warning before spending hours troubleshooting NET, a 2 hour chkdsk and installing a fresh windows 7 virtual machine. :-) |
|
|
|
I agree with 9 and do the same, but 8, do you mean that you allow a reset or you do not allow reset? Normaly I dont touch the advanced settings at all and just wait.
Yes I tick the lower check box in advanced settings. It was a feature we requested a good few pages back and Stephan was kind enough to implement it for us. |
|
|
|
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?  Ha ha ;-) Stephan's guidelines a few posts back are a good start. To be honest....no one strategy fits all circumstances but I found than I learned rather quickly as the bot was haemorrhaging thousands of dollars due (mainly) to my inexperience in the beginning. :-) If you're serious and need some advice, then I am always happy to share what I have learned, but via PM please :-) If too many people traded with the same settings then we'd never get any trades :-) More generally. Early findings and mistakes were: 1. Using the default 20s timer (which will be removed). It is widely documented in this thread that longer intervals are best. 3-10 mins. 20s is next to useless and the indicators do not respond well or very predictably for me. 2. Watching the bot in the early days and intervening out of blind panic and inexperience/incompetence often making the wrong decision. Let the bot roll! 3. Bugs. Stephan has done an excellent job in resolving them and the bot is approaching perfection. The new releases might have a few teething problems, but we'll have to wait until the 20th to see. Maybe the logic is largely untouched, though I doubt it somehow. 4. I found using 'All In' was not as effective as spreading across a few viable and moving currencies. Three in my case. I trade on BTC-E as I had issues with Cryptsy which we thought was down to their server lag and API. 5. Trading in fiat currency pairs was not good for me as like to have my reward in Bitcoin then wait to sell some at a good price to cash out some profit. Occasionally I manually swing out to fiat to get out of a jam and then get back into to a BTC pair 6. Long intervals and update timer can mean you are waiting a long time before the bot has sufficient data to trade. This is annoying, but there is a planned online database of ticker data so that trading can be instant even with long duration settings. 7. I found the drop loss function a little too primitive as it is based on fixed intervals of time and tend to not use it. Same for the duration to reset last buy and sell. 8. The reset Last Buy and Sell check box is a must for me. 9. I don't disable minimum drop raize safety as I have a policy of never making an unprofitable trade. Hope that helps a bit anyway. K |
|
|
|
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. |
|
|
|
"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 |
|
|
|
kalrossit was reply, yes. I have same issue. I dont like unprofitable trades  Oh ok. Looks like a bug then...easily fixed I would assume. |
|
|
|
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. |
|
|
|
|
