Show Posts
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.
yes it would not buy a second time but that doesnt solve the issue since the problem is an order canceled that doesn execute and even if the price stays in sell range wont sell since it thinks it sold already.Well, it happened more than once but today I was able to notice what was going on.
It has bb for buying and gain for sell, no RSI indicator on-sell, not trailme, not nothing.
The bot made the buy order and went fine, but then it reached the exit price but did not sell, it even went over 0.40% over the exit but it did not sell then the price went down again and back to the entry and made a second buy without selling the 1st one.
I use DCA but the setting has buy down to 1% under the initial buy and this buy was almost exactly at the same price as the first buy it even bought higher than the first one.
Also the DCA is configured to place 1:0.5 ratio and the second buy was for the same amount.
The only clue I found was the bot indeed tried to sell at the exit but the order appeared on my binance account as canceled. but I did not cancel anything I wasnt even logged when that happened.
any report of the same problem with anyone else?
if so there is a posible cause, solution or workaround?
Have you tried using TRADES_TIMEOUT parameter? It set the minimum time it has to wait to buy again after a the bot buys. This usually fixes doble buys.
Well, it happened more than once but today I was able to notice what was going on.
It has bb for buying and gain for sell, no RSI indicator on-sell, not trailme, not nothing.
The bot made the buy order and went fine, but then it reached the exit price but did not sell, it even went over 0.40% over the exit but it did not sell then the price went down again and back to the entry and made a second buy without selling the 1st one.
I use DCA but the setting has buy down to 1% under the initial buy and this buy was almost exactly at the same price as the first buy it even bought higher than the first one.
Also the DCA is configured to place 1:0.5 ratio and the second buy was for the same amount.
The only clue I found was the bot indeed tried to sell at the exit but the order appeared on my binance account as canceled. but I did not cancel anything I wasnt even logged when that happened.
any report of the same problem with anyone else?
if so there is a posible cause, solution or workaround?
will give another try to the 21 with my current settings.I'm having a lot of issues with the ARM 21.0 version of the gunbot, I brings a new GUI which is nice, but is very buggy in many senses
1 Some overrides won't work for example the period override on bb strategy won't override the period setting I that strategy, (haven't tested somewhere else)
2 It gives an error every 30 seconds or so
TypeError: Cannot read property '-1' of undefined
at timeseries.SolveLE (/snapshot/node14Win/node_modules/timeseries-analysis/timeseries-analysis.js:993:22)
at timeseries.ARLeastSquare (/snapshot/node14Win/node_modules/timeseries-analysis/timeseries-analysis.js:942:20)
at /snapshot/node14Win/gain.js
at runMicrotasks (<anonymous>)
(synccing the clock of the pi wont fix the issue as stated here: https://gunbot.shop/fix-cannot-read-property-1-of-undefined-error-on-gunbot/)
tried syncing the time in both the pc using the web browser and the PI but no results.
3 The telegram doesn't work yet this is the main reason I would need to try another version of ARM
I'm using ARM because it draws low power and since my gaming computer draws a lot of power, i can't use the pc version.
I used version 18 like one year ago it had a lot of bugs too, but I was able to make it work almost fully. Had to disable the GUI since it crashed the bot a lot, but without using GUI it would be pretty fine.
is there any ARM stable version that could someone point at me to try?
it feels kinda weird that people rathers use the PC version since on pc you need to use a lot more power to keep it up feels inefficient also the alternative of setting a VPS sounds very very unsafe since you have many sensitive settings in a server remotely I ve seen the adminds of certain VPS companies to get in the VPS I ve rented.
v21.1.0 doesn't have ARM version yet.
Latest one with ARM is
https://gunbot.shop/gunbot-v21-download/
Some ARM customers told me that v18 worked better for them than v21, so it's up to you to try also:
https://gunbot.shop/gunbot-v18-8-8-download/
Loading exchange - binance
Loading data....
{ ExchangeNotAvailable: binance GET https://api.binance.com/api/v3/exchangeInfo system request to https://api.binance.com/api/v3/exchangeInfo failed, reason: getaddrinfo ENOTFOUND api.binance.com api.binance.com:443
at module.exports.initRestRateLimiter.executeRestRequest.fetchImplementation.catch (/snapshot/pi/Desktop/gb/node_modules/ccxt.pro/node_modules/ccxt/js/base/Exchange.js:390:35)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
constructor: [Function: ExchangeNotAvailable],
name: 'ExchangeNotAvailable' }
Fetching my trades again.{"name":"ExchangeNotAvailable"}
Error
at errorHandler (/snapshot/pi/Desktop/gb/ctx/js/binance.js:0:0)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
Error: {}
at errorHandler (/snapshot/pi/Desktop/gb/ctx-wrapper.js:0:0)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
Unable to connect to binance
Please if this error persists, stop Gunbot, wait a few minutes and then start it again...
Thanks Truitaman, thats what, I wanted to know i though it was 10% of the price just needed to clarify.
took your advice and turned off the Take buy and take profit, just left BB with trailme for buying which i think is the same as bb with tssl.Hi mate,
and for selling i'm using Gain with a fixed 0.5% also with trailme also like a gain with tssl right?
but the setting i dont understand is the lowBB in the indicator settings
1 - Low BB set to 0 = entry point 157.37193000 PAX
2 - Low BB set to -10 = entry point 156.94266000 PAX
The setting is not being ignored as I initially though but is not what i understood from the wiki
"When set to 0, the lower Bollinger Band is the target. When set to 30, the target is 30% above the lower Bollinger Band - the upper band is at 100% from the lower band. Negative values are allowed."
so if i'm not wrong if i set the value to -10 the target would be 10% under the "Low bb" but i dont see how 0.42927 PAX would be 10% of 157 PAX, may be is not 10% of the price??? what i am missing here?
negative signal value it means it will be - the lowest point (0) of the BB LOW_BB that also is calculated by the SMAPERIOD (number of candles gunbot will use to calc the lowbb and highBB , so if u set a -5 it will try to buy at -5% of low_bb based in your period and LOW_BB. A negative value in the LOW_BB can b extremely useful if market is bearish, so u buy post dump usually taking a good position then u can mix the strategy with a gain for sell and use stochRSI cross to sell your bag, that's just an example.
As well you can check BBTA strategy is slightly different behaviour, gunbot only will buy when price return to the low_bb, that one is even more effective in bearish market.
trick: you can change standard_deviation value to narrow or wide your bb.
so if u set a -5 it will try to buy at -5% of low_bb based in your period and LOW_BB.