Gunbot XT Heartbeat Message [SOLVED]

[Ladies]

Hello there,

I was looking through my logs and saw that while running BB, I am constantly receiving the heartbeat message.
I've tried everything in the troubleshooting page regarding the error, but nothing seems to work.

So far, there has been no trades done at all, since running it for 3 days.

Please advise.

Thank you.

[c64audio]

I have this problem as well. Turning debug on gives no more clues. It finds a trade opportunity, starts the trade process, and then... nothing happens except a heartbeat (unless the safety switch is on, in which case it prints that message).

(Bittrex, BBStepgain, 15 pairs all valid).

[Fathom500]

Same issue here. Reinstalled the bot from scratch and it seemed to go away. Also having issues with the Trend watcher saying the trend is up when it is clearly down. Playing with the period and SMA period per some recommendations. Does not seem to help. This is causing lost opportunities for gains left and right. Also TSSL is doing some crazy shit. Stop trailing stop loss is higher then the current price so every time something sells into BTC it gets sold into USDT right away. Every release seems to be a bigger shit show then the last. If the machine can't be trusted to trade buy and sell when it should then it is useless.

[c64audio]

I would note here that it not being able to buy doesn't affect it being able to sell, and it's not affected by the rate of the bot, so it's nothing to do with Cloudflare. This is purely internal stuff.

I had these problems off a fresh install on a fresh Linux machine.

I tried turning Okkies mode off just in case the bot was always thinking Bitcoin was under stress and avoiding pumping (this is one way the bot can suppress buying without putting anything in the log), but it didn't affect anything.

So after I turned the bot on, it bought for five minutes, then stopped buying and sold over a few hours.

What's the last version that worked?

Here's what happened from when I switched the bot on for the first time to now. As you can see, the non-buying started during the run (after the safety switch period), but is not due to cloudflare problems (which would have resulted in all traffic being blocked, not just buys).  There were no errors during the run.

CLOSED DATE   OPENED DATE   MARKET   TYPE   BID/ASK   UNITS FILLED   UNITS TOTAL   ACTUAL RATE   COST / PROCEEDS
12/14/2017 04:08:14 AM   12/14/2017 04:08:14 AM   BTC-XEM   Limit Sell   0.00003240   31.70577045   31.70577045   0.00003239   0.00102470
12/14/2017 01:33:49 AM   12/14/2017 01:33:49 AM   BTC-DASH   Limit Sell   0.05380000   0.01879874   0.01879874   0.05379988   0.00100885
12/13/2017 11:37:59 PM   12/13/2017 11:36:30 PM   BTC-ETC   Limit Sell   0.00181830   0.55558642   0.55558642   0.00181829   0.00100770
12/13/2017 10:43:01 PM   12/13/2017 10:43:01 PM   BTC-ARDR   Limit Sell   0.00005934   17.21466689   17.21466689   0.00005933   0.00101896
12/13/2017 10:09:09 PM   12/13/2017 10:09:09 PM   BTC-EDG   Limit Sell   0.00008450   12.12121212   12.12121212   0.00008449   0.00102168
12/13/2017 09:51:06 PM   12/13/2017 09:48:58 PM   BTC-EDG   Limit Buy   0.00008250   12.12121212   12.12121212   0.00008249   -0.00100248
12/13/2017 09:48:50 PM   12/13/2017 09:48:50 PM   BTC-XEM   Limit Buy   0.00003154   31.70577045   31.70577045   0.00003153   -0.00100248
12/13/2017 09:48:41 PM   12/13/2017 09:48:41 PM   BTC-WAVES   Limit Buy   0.00083600   1.19617224   1.19617224   0.00083498   -0.00100128
12/13/2017 09:47:58 PM   12/13/2017 09:47:58 PM   BTC-ARDR   Limit Buy   0.00005809   17.21466689   17.21466689   0.00005808   -0.00100248
12/13/2017 09:46:42 PM   12/13/2017 09:46:42 PM   BTC-DASH   Limit Buy   0.05319505   0.01879874   0.01879874   0.05319452   -0.00100248
12/13/2017 09:46:33 PM   12/13/2017 09:46:33 PM   BTC-ETC   Limit Buy   0.00179990   0.55558642   0.55558642   0.00179988   -0.00100248

[c64audio]

BTW, friend of mine lost a fair amount with the TSSL algorithm, should come with a wealth warning....

[Ladies]

Hey guys, I have gotten the bot to finally work.
All I had to do was, on the GUI head over to Settings > BOT > Bot Delay. Change Bot Delay: 1 to a higher number (mine is 25).
I believe why I was having the error is because, Poloniex bans the IP address for apprently checking too quickly (correct me if I am wrong).

Do let me know if that worked for you.

[c64audio]

I'm using Bittrex, and I upped the delay to 2 instead of 1. But this isn't a solution for my problem, since everything using the API (including selling) works, except for buy.
If the IP was banned, then everything would fail, not just one very specific thing.

This fault is in the build: it's quietly throwing away buys, and the only reason I can think of is something to do with okkies mode.

Chris

[c64audio]

Are we talking to ourselves?

I tried downgrading to 6.0.1, but that won't even run on Linux or Windows: just sits there. More testing needed.

[edit: old version cleared out. Config clean with API key, still just sits there.]

[c64audio]

Hey, the problem might be solved for you, but not for us. Now no one will come here. I'd better start another thread.

[c64audio]

I've taken this problem to the Github issues thing.

[sloaleks]

Are we talking to ourselves?

I tried downgrading to 6.0.1, but that won't even run on Linux or Windows: just sits there. More testing needed.

[edit: old version cleared out. Config clean with API key, still just sits there.]

601 doesn't work anymore, it's been about 2 weeks since it stopped.