81
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 30, 2017, 09:48:28 PM »
Thanks to all of you that contribute testing adn reporting, we move to the 3.3 bugs tracker now
~Gun
~Gun
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Today my bot on strategy Stepgain bought crypto higher then BB and higher than each EMA. Previously bot works about 10 hours.
How can it be?
Hi @Gunthar,
referring to new stepgainHow does it work? You specify 2 levels of buy and 2 levels of sell (buy below EMA and sell above the price you bought). Say you set buy level 1 to 2% and buy level 2 to 5%: the bot will try to reach the level you set in "Level to use for buy orders" (1 or 2: in the example above would be 2% or 5%). If the price fails to reach that level, the bot will buy on the higher level you set or better price. Same happen with the sell part of it: say you set Sell level 1 to 3% and sell level 2 to 10%, the bot will try to reach 10% or better and if it fails, it will sell between 3% and 10%. In the Legacy-Stepgain strategy, there were 3 levels: now the third level is the BB. So basically let's make some examples:can you please elaborate on theQuoteIf the price fails to reach that levelpart?
what does it mean if it fail? for how long is it supposed to fail? by how far? Does the algo tries more than once?
thanks
Doc
~snip
Looks like on 3.2, at least on Kraken (the only 3.2 I'm running at the moment), when it gets a 502 error, the bot is dumping the HTML response to the console instead of catching it and just reporting the 502.Code: [Select][ --2017/05/18 07:33:33--kraken--BTC_DASH -- Gunbot v3.2 cycle #213 --------------- ]
::::: collecting market data...
2017/05/18 07:33:35 Error: Could not understand response from server: <!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if IE 7]> <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
<!--[if IE 8]> <html class="no-js ie8 oldie" lang="en-US"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]-->
<head>
<meta http-equiv="set-cookie" content="cf_use_ob=0; expires=Thu, 18-May-17 12:34:05 GMT; path=/">
<title>api.kraken.com | 502: Bad gateway</title>
<meta charset="UTF-8"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1"/>
<meta name="robots" content="noindex, nofollow"/>
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1"/>
<link rel="stylesheet" id="cf_styles-css" href="/cdn-cgi/styles/cf.errors.css" type="text/css" media="screen,projection"/>
<!--[if lt IE 9]><link rel="stylesheet" id='cf_styles-ie-css' href="/cdn-cgi/styles/cf.errors.ie.css" type="text/css" media="screen,projection" /><![endif]-->
<style type="text/css">body{margin:0;padding:0}</style>
<!--[if lte IE 9]><script type="text/javascript" src="/cdn-cgi/scripts/jquery.min.js"></script><![endif]-->
<!--[if gte IE 10]><!--><script type="text/javascript" src="/cdn-cgi/scripts/zepto.min.js"></script><!--<![endif]-->
<script type="text/javascript" src="/cdn-cgi/scripts/cf.common.js"></script>
</head>
<body>
<div id="cf-wrapper">
<div id="cf-error-details" class="cf-error-details-wrapper">
<div class="cf-wrapper cf-error-overview">
<h1>
<span class="cf-error-type" data-translate="error">Error</span>
<span class="cf-error-code">502</span>
<small class="heading-ray-id">Ray ID: 360ed87d7f50583d • 2017-05-18 12:33:35 UTC</small>
</h1>
<h2 class="cf-subheadline" data-translate="error_desc">Bad gateway</h2>
</div>
<div class="cf-section cf-highlight cf-status-display">
<div class="cf-wrapper">
<div class="cf-columns cols-3">
<div id="cf-browser-status" class="cf-column cf-status-item cf-browser-status ">
<div class="cf-icon-error-container">
<i class="cf-icon cf-icon-browser"></i>
<i class="cf-icon-status cf-icon-ok"></i>
</div>
<span class="cf-status-desc" data-translate="browser_desc">You</span>
<h3 class="cf-status-name" data-translate="browser_label">Browser</h3>
<span class="cf-status-label" data-translate="browser_status_label">Working</span>
</div>
<div id="cf-cloudflare-status" class="cf-column cf-status-item cf-cloudflare-status ">
<div class="cf-icon-error-container">
<i class="cf-icon cf-icon-cloud"></i>
<i class="cf-icon-status cf-icon-ok"></i>
</div>
<span class="cf-status-desc" data-translate="cloud_desc">Location</span>
<h3 class="cf-status-name" data-translate="cloud_label">Cloudflare</h3>
<span class="cf-status-label" data-translate="cloud_status_label">Working</span>
</div>
<div id="cf-host-status" class="cf-column cf-status-item cf-host-status cf-error-source">
<div class="cf-icon-error-container">
<i class="cf-icon cf-icon-server"></i>
<i class="cf-icon-status cf-icon-error"></i>
</div>
<span class="cf-status-desc" data-translate="server_desc">api.kraken.com</span>
<h3 class="cf-status-name" data-translate="server_label">Host</h3>
<span class="cf-status-label" data-translate="server_status_label">Error</span>
</div>
</div>
</div>
</div>
<div class="cf-section cf-wrapper">
<div class="cf-columns two">
<div class="cf-column">
<h2 data-translate="what_happened">What happened?</h2>
<p>The web server reported a bad gateway error.</p>
</div>
<div class="cf-column">
<h2 data-translate="what_can_i_do">What can I do?</h2>
<p data-translate="try_again_in_a_few">Please try again in a few minutes.</p>
</div>
</div>
</div>
<div class="cf-error-footer cf-wrapper">
<p>
<span class="cf-footer-item">Cloudflare Ray ID: <strong>360ed87d7f50583d</strong></span>
<span class="cf-footer-separator">•</span>
<span class="cf-footer-item"><span data-translate="your_ip">Your IP</span>: x.x.x.x</span>
<span class="cf-footer-separator">•</span>
<span class="cf-footer-item"><span data-translate="performance_security_by">Performance & security by</span> <a data-orig-proto="https" data-orig-ref="www.cloudflare.com/5xx-error-landing?utm_source=error_footer" id="brand_link" target="_blank">Cloudflare</a></span>
</p>
</div>
</div>
</div>
!!! Cycle 214 failed. Will repeat in 102.9763402239914s
Seems that maybe this should be caught by gunbot and just reported as a 502 or whatever.
@OutOfSync to me it looks like 3.2 BB needs 3 cycles to calculate its values!? but I might be wrong and the values showing up are ...?.. something else!
It shows BB values after 3 cycles because you need at least 3 values to calculate standard deviation. However, until stats are calculated (300 cycles with default settings) the bot does not use BB strategy but the GAIN value (2% as default). 300 cycles with default delay of 120 s is 10 hours untils BB stats are done. This is just quite long if you have to e.g. update the binary and hotconfig is therefore not possible...
~snip
gbot complains about "Missing boughtPrice" since it cannot find a record of this altcoin balance.
~snip
When one Pair places an order that is not yet executed, all the rest of the pairs pretend to have the same order for their currency.fixed in patch 2020
This holds all the other pairs to proceed normally
Settings:
Gunbot v3.2, win headless, Buy strategy: BB, 25%; sell strategy: GAIN 3%, bot delay: 60s
Details:
Gunbot placed a buy order for LTC that was processed with a delay of some minutes by Kraken.
Meanwhile, all the rest of the pairs that were about to proceeed with a buy/sell had the same message:
2017/05/12 00:40:10 Waiting for orders: 370.248 XLTC , for LTC
2017/05/12 00:26:33 Waiting for orders: 370.248 XXLM , for XLM
2017/05/12 00:26:07 Waiting for orders: 370.248 XETC , for ETC
etc. etc.
Tripple an quadruple buys on Patch 2019!statuscode 502, 429, 422 from poloniex caused this. Please apply patch 2020 to mitigate about 99% of these issues.
"BB" strategy, poloniex!
All pairs are set to "BTC_TRADING_LIMIT: 0.035"
2 issues to report:
1) "Altcoin on orders" is reported incorrectly in kraken market (did not check other markets):
Situation: I have some ETH that I manually placed a selling order for. Now I started a different pair in kraken from scratch with brand new config and no save file. The ETH on orders is now reported as "balance on order" for the newly started pair and the bot is confused because it thinks we have altcoins but no boughtPrice. This could be mitigated if the "balance on order" is reported correctly for the pair the bot is running.
2) I cannot find the Low BB and High BB values in the "-save.json" file.
Saving these important values would make it easy to write a GUI that reports them over time. I am thinking along the lines of an InfluxDB database with Grafana dashboard tracking all parameters. Would be really nice to tweak the bot.
Thanks Gunthar for an awesome update!
~snip
~snip
When the time to buy has come, gunbot puts market order to buy to a price that is in reality incorrect.
Settings:
gunbot v3.2, buy strategy: BB, 25%; sell strategy: GAIN3%5%, bot delay time: 60s
Description:
Having lower 'bought price' leads to inappropriate calculations of the GAIN % (sell strategy is GAIN). Afterwards, because sell orders are also market the result is unpredictable and at least in my case all trades lead to losses.