Gekko shows advice only once

[skayred]

Hi!

I've tried to run Gekko, and it shown message about calculation and then advice, but then it stuck and showd nothing during the all night. Is it the issue or there are no messages when you shouldn't do anything?

Also, how often Gekko asks MTGoc about new information?

[cykedev]

Same for me

[leshow]

same problem here

[askmike]

I will look at this!

[nickoneill]

+1

[askmike]

It will check the price at Mtgox every interval in the config (on default every 60 minutes), if you want to see what Gekko is doing and whether or not it is still calculating you can set debug to true in the config which will make Gekko log all information regarding fetching trade data, calculating the EMA's and detecting trends.

Depending on your thresholds it can be quite possible that Gekko doesn't report new positions every day, but I will improve this logging on default.

[leefernandes]

#62 - Pull-request to configure any combination of "HOLD", "BUY", and/or "SELL" emails to send.

[kuzetsa]

@askmike -- on the subject of improved logging, see pull request #65 for a suggested logging improvement which already seems to uncover a bug where the portfolio / balance data never gets re-updated (refreshed) on one or more exchanges:

... for instance, when using CEX.IO as primary market, the GHS I have in my portfolio causes a steady trickle of new BTC and an ever-increasing balance, but gekko's internal in-memory value for the BTC account balance doesn't seem to track the reality of how much BTC is actually held on the exchange.

Edited to add:

bugfix for stale balance in pull request / issue #66, still unclear if this has any impact on #49 (I'm planning to look into this issue next)

[kuzetsa]

I experimented with removing some code in /methods/exponential-moving-averages.js which was preventing gekko from giving advice more than once at the high & low points during any single buy/sell cycle (one advice each for the high and low points respectively)

specifically, it's the code relating to:

this.currentTrend

for my own use case (as per: kuzetsa@916aab0) I decided to intentionally break (comment out) the logic which detects entering an uptrend from a non-uptrend state VS doing nothing if the uptrend is an ongoing, continued state.

Doing this allows for gekko running on cex.io to continually use any newly mined bitcoin to purchase additional GHS until the uptrend stops (at which point gekko would continue the usual logic for hold VS panic sell based on the config.EMA thersholds)

Note that without the code in #67 my patch doesn't work at all, since gekko didn't seem to be keeping track of the portfolio balance consistent with the realtime balance on the exchange itself.

[askmike]

@kuzetsa great point, in an uptrend we want to keep on buying at CEX.io (but note that CEX.io support is currently broken, you can open a new issue for this if you want).

As for the original issue, this has been fixed some time ago!