Bugs/Issues tracker v4.0.1

[Gunthar]

I'm going to read this user-generated tracker every 5 minutes.
Thanks!
~Gun

[lazken]

Honestly not sure if a bug, or if logging needs configured seperately in the config.
Still not creating log files under Ubuntu or amazon linux as per 3.3.5.
Users running the binary have full perms to the directory it's running as.

[Gunthar]

Honestly not sure if a bug, or if logging needs configured seperately in the config.
Still not creating log files under Ubuntu or amazon linux as per 3.3.5.
Users running the binary have full perms to the directory it's running as.

no ti is not a bug: we are creating websockets, so no logs.

[lazken]

Perfect - Thank you. I'll wait for the documentation on that.

It seems buggy with bittrex - connections hanging between 1 minute and 5 minute after starting, with no further activity within the console.
Wireshark shows no further connections out.
Forcing a HUP will kick it back in to life for a further few minutes before hanging again.
Have tried both on linux and win10.

[WGXtreme]

Perfect - Thank you. I'll wait for the documentation on that.

It seems buggy with bittrex - connections hanging between 1 minute and 5 minute after starting, with no further activity within the console.
Wireshark shows no further connections out.
Forcing a HUP will kick it back in to life for a further few minutes before hanging again.
Have tried both on linux and win10.

Seconded, Windows 10

[baronga]

Same hang on Bittrex, Windows 2012 R2

[LenardBang]

Selling at bittrex seems off.

While the sell order in the log seems fine, the amount of sold currency (placed order) at exchange is smaller than that.
(It certainly is NOT timedout/unfilled order).

For example:

Log says: 

Strategy BB for BTC-PAY on bittrex -| Selling 22.221235 of BTC-PAY at rate 0.00101941

But order placed at Bittrex is for :

16.44371390

[WeissJT]

Perfect - Thank you. I'll wait for the documentation on that.

It seems buggy with bittrex - connections hanging between 1 minute and 5 minute after starting, with no further activity within the console.
Wireshark shows no further connections out.
Forcing a HUP will kick it back in to life for a further few minutes before hanging again.
Have tried both on linux and win10.

Same on ubuntu 16.04 with 1 pair bb default on Bittrex for the last 10 hours, in my case seems like it updates once every 1 hour or 1 hour and a half.
Can't say if it's doing updates in the background, cpu usage it's at 0% all the time.
This is the log: https://hastebin.com/iyixipeqir.sm
The vps is on UTC 0.

[Freak on a Reef]

Perfect - Thank you. I'll wait for the documentation on that.

It seems buggy with bittrex - connections hanging between 1 minute and 5 minute after starting, with no further activity within the console.
Wireshark shows no further connections out.
Forcing a HUP will kick it back in to life for a further few minutes before hanging again.
Have tried both on linux and win10.

This idle thing is happening to me too. It can be a minute, seconds, or as much as an hour before it scans for opportunities again. While using Polo and Bit, it only seems to ping Bit. The great thing is that the double up is working perfectly and it self corrected picking up bags. However, you have to be cautious because LTC took a dive all night and double up bagged up 1.5BTC worth ... Gotta be careful with that setting for sure!

[danialt]

i've had the same but within 2 mins almost constantly
changed the following to the 3.3.5 numbers and been running ok so far for longer
      "period_storage_ticker": 300,
      "interval_ticker_update": 10000,

leaving it running now to see what happens

[danialt]

its not looking up/calculating bought price, so having to override every pair that I had prior to using 4.0.1

[Freak on a Reef]

Perfect - Thank you. I'll wait for the documentation on that.

It seems buggy with bittrex - connections hanging between 1 minute and 5 minute after starting, with no further activity within the console.
Wireshark shows no further connections out.
Forcing a HUP will kick it back in to life for a further few minutes before hanging again.
Have tried both on linux and win10.

This idle thing is happening to me too. It can be a minute, seconds, or as much as an hour before it scans for opportunities again. While using Polo and Bit, it only seems to ping Bit. The great thing is that the double up is working perfectly and it self corrected picking up bags. However, you have to be cautious because LTC took a dive all night and double up bagged up 1.5BTC worth ... Gotta be careful with that setting for sure!

If it would just keep running it would be trading like crazy. Every time I update the config it starts another cycle and either buys or sells it seems. All at a profit

[danialt]

I'm also noticing that the full amount of coins held are not being sold, thus leaving an amount under the min exchange trading amount

[krixt]

Please bring back 3.3.2-style console output (ie: per-coin per-window). I do not like seeing every coin on every exchange all cluttering 1 scrolling box. Makes it difficult to "watch" what GB is thinking about a specific coin.

Additionally, "v4.0.1  Tips&Tricks: USDT_XRP can be sold!!!"

I don't like seeing this message because it presents a false sense of the bots actions. If sold now, it would sell at a huge loss. This message tells me GB is thinking of selling it now.

[krixt]

Proper formatting of float's still having issues. I reported this a while back: https://github.com/GuntharDeNiro/BTCT/issues/9

Code: [Select]

2017/08/11 21:58:16: There are some trading opportunities for BTC_DOGE at poloniex. Scanning Trade History
2017/08/11 21:58:16: Last Bid price BTC_DOGE: 5e-7 | Last Ask: 5.1e-7
2017/08/11 21:58:16: Balance BTC: 0.53753830

Code: [Select]

Nothing changed in BTC_DGB: Bid/Ask is 0.00000446/0.00000449. Entry points are: 0.0000043659959/0.0000052815


Code: [Select]

Nothing changed in BTC_DOGE: Bid/Ask is 5.1e-7/5.2e-7. Entry points are: 5.1538332e-7/5.355e-7


[Degenere]

Selling at bittrex seems off.

While the sell order in the log seems fine, the amount of sold currency (placed order) at exchange is smaller than that.
(It certainly is NOT timedout/unfilled order).

For example:

Log says: 

Strategy BB for BTC-PAY on bittrex -| Selling 22.221235 of BTC-PAY at rate 0.00101941

But order placed at Bittrex is for :

16.44371390

+1 On this bug. Bot says it is selling all available balance but ends up selling less than that and order executed immediately, no timeouts or anything. This is resulting in over spending of transaction fees.

[krixt]

Code: [Select]

Processing strategy BB for USDT_XRP on poloniex
------------------------------------------------------------------------------------------------
 ɢƱÑƁØŁ v4.0.1  Scanning poloniex for trading opportunities 2017/08/11 22:35:46
------------------------------------------------------------------------------------------------
No new opportunities found...
2017/08/11 22:36:06: Kicking poloniex, receiving new tickers...
------------------------------------------------------------------------------------------------
 ɢƱƝɮǾŁ v4.0.1  Scanning poloniex for trading opportunities 2017/08/11 22:36:06
------------------------------------------------------------------------------------------------
No new opportunities found...
------------------------------------------------------------------------------------------------
 ɢՍҊƁѺŦ v4.0.1  Scanning poloniex for trading opportunities 2017/08/11 22:36:12
------------------------------------------------------------------------------------------------
Error on strategy BB for BTC_GAME on poloniex while getting order book -| Error: Cannot read property 'error' of undefined
2017/08/11 22:37:12: Kicking poloniex, receiving new tickers...
Getting tickers for poloniex catch error: Cannot read property 'error' of undefined


[Cryptic]

Getting only errors.

Code: [Select]

Loading config...
Loading exchange kraken
2017/08/12 01:52:27: Kicking kraken, receiving new tickers...
--------------------------------------------------------------------------------
----------------
 ?????T v4.0.1  Scanning kraken for trading opportunities 2017/08/12 01:52:29
--------------------------------------------------------------------------------
----------------
Error on strategy BB for XXBTZEUR on kraken while getting order book -| Error: F
UCK KRAKEN


Code: [Select]

Loading config...
Loading exchange kraken
2017/08/12 01:56:42: Kicking kraken, receiving new tickers...
--------------------------------------------------------------------------------
----------------
 ??Ñß?? v4.0.1  Scanning kraken for trading opportunities 2017/08/12 01:56:44
--------------------------------------------------------------------------------
----------------
C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodash.js:13379
        baseAssignValue(result, key, iteratee(value, key, object));
                                     ^

ReferenceError: p is not defined
    at module.exports.Market.returnTradeHistory.setTimeout.kraken.api._.mapValue
s (C:\snapshot\c3,3,6_POLONIEX\kraken.js:0:0)
    at C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodash.js:13379:38
    at isBind (C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodash.js:4944:15
)
    at baseForOwn (C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodash.js:300
1:24)
    at Function.mapValues (C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodas
h.js:13378:7)
    at KrakenClient.module.exports.Market.returnTradeHistory.setTimeout.kraken.a
pi (C:\snapshot\c3,3,6_POLONIEX\kraken.js:0:0)
    at Request._callback (C:\snapshot\c3,3,6_POLONIEX\kraken-api\kraken.js:159:2
2)
    at Request.init.self.callback (C:\snapshot\c3,3,6_POLONIEX\kraken-api\node_m
odules\request\request.js:188:22)
    at emitTwo (events.js:125:13)
    at Request.emit (events.js:213:7)
    at Request.<anonymous> (C:\snapshot\c3,3,6_POLONIEX\kraken-api\node_modules\
request\request.js:1171:10)
    at emitOne (events.js:115:13)
    at Request.emit (events.js:210:7)
    at IncomingMessage.<anonymous> (C:\snapshot\c3,3,6_POLONIEX\kraken-api\node_
modules\request\request.js:1091:12)
    at Object.onceWrapper (events.js:312:19)
    at emitNone (events.js:110:20)
    at IncomingMessage.emit (events.js:207:7)
    at endReadableNT (_stream_readable.js:1045:12)
    at _combinedTickCallback (internal/process/next_tick.js:102:11)
    at process._tickCallback (internal/process/next_tick.js:161:9)
Loading config...
Loading exchange kraken
2017/08/12 01:56:52: Kicking kraken, receiving new tickers...
--------------------------------------------------------------------------------
----------------
 ?????T v4.0.1  Scanning kraken for trading opportunities 2017/08/12 01:56:53
--------------------------------------------------------------------------------
----------------
Error on strategy BB for XXBTZEUR on kraken while getting order book -| Error: E
rror: ESOCKETTIMEDOUT

Code: [Select]

Loading config...
Loading exchange kraken
2017/08/12 02:00:15: Kicking kraken, receiving new tickers...
--------------------------------------------------------------------------------
----------------
 ?????T v4.0.1  Scanning kraken for trading opportunities 2017/08/12 02:00:18
--------------------------------------------------------------------------------
----------------
C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodash.js:13379
        baseAssignValue(result, key, iteratee(value, key, object));
                                     ^

ReferenceError: p is not defined
    at module.exports.Market.returnTradeHistory.setTimeout.kraken.api._.mapValue
s (C:\snapshot\c3,3,6_POLONIEX\kraken.js:0:0)
    at C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodash.js:13379:38
    at isBind (C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodash.js:4944:15
)
    at baseForOwn (C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodash.js:300
1:24)
    at Function.mapValues (C:\snapshot\c3,3,6_POLONIEX\node_modules\lodash\lodas
h.js:13378:7)
    at KrakenClient.module.exports.Market.returnTradeHistory.setTimeout.kraken.a
pi (C:\snapshot\c3,3,6_POLONIEX\kraken.js:0:0)
    at Request._callback (C:\snapshot\c3,3,6_POLONIEX\kraken-api\kraken.js:159:2
2)
    at Request.init.self.callback (C:\snapshot\c3,3,6_POLONIEX\kraken-api\node_m
odules\request\request.js:188:22)
    at emitTwo (events.js:125:13)
    at Request.emit (events.js:213:7)
    at Request.<anonymous> (C:\snapshot\c3,3,6_POLONIEX\kraken-api\node_modules\
request\request.js:1171:10)
    at emitOne (events.js:115:13)
    at Request.emit (events.js:210:7)
    at IncomingMessage.<anonymous> (C:\snapshot\c3,3,6_POLONIEX\kraken-api\node_
modules\request\request.js:1091:12)
    at Object.onceWrapper (events.js:312:19)
    at emitNone (events.js:110:20)
    at IncomingMessage.emit (events.js:207:7)
    at endReadableNT (_stream_readable.js:1045:12)
    at _combinedTickCallback (internal/process/next_tick.js:102:11)
    at process._tickCallback (internal/process/next_tick.js:161:9)
Loading config...
Loading exchange kraken
2017/08/12 02:00:25: Kicking kraken, receiving new tickers...
--------------------------------------------------------------------------------
----------------
 ???ß?L v4.0.1  Scanning kraken for trading opportunities 2017/08/12 02:00:25
--------------------------------------------------------------------------------
----------------
Error on strategy BB for XXBTZEUR on kraken while getting order book -| Error: F
UCK KRAKEN

[krixt]

Please create different verbosity levels. I have no clue what the bot is doing. Print out things like "Passed Step-Gain Level 1!! (X%)" when it passes that level, etc for each level and for buys too. X% represents the % gain.

Print out things like 'LowBB is 0.xxx; Looking for target (20%) of 0.yyyy' (where 20% is what they have set for LOWBB)

Print out status of the trend watcher like in 3.3.2: Price is going up (+3), Price is steady(0), Price falls (-2)

[n30]

Hello Gunthy, reporting double buy at Poloniex, btc/dbg pair, sold correctly, then bought again but double. Two identical buys.
Nice weekend to you all.