Are you saying that the required change feature with indicators uses limit orders? It doesn’t make sense, as orders are sent after the condition triggers, not in advance 
I’m not sure any of these say coinbase for an exchange though. I filtered for coinbase* and I see some with coinbase as the exchange, but the timestamped logs only coincide with when the bot is restarted from what I can tell. I’ll let it run while I’m gone today and check again when I get back home.
Yes, required change is related to DCA volume, TP is a TP order. Rossano once asked about required changed, and its not what he meant it to be.
TP in your settings is a simple percenatge of 2%. Order placed in advance based on filled orders of the deal.
This is quite interesting. You said you deployed PRICE_CONNECTOR_EXCHANGES, but according to logs its not. Trades should be only for deals specified in the .env variable. Either container version is not up to date, or .env not applied. To apply you also need rebuild container, not simply restart.
Most likely live trades are not received by the price connector, but you can tell it for sure when deployed price container to have only coinbase.
We are talking about TP order, not DCA. The problem here is that TP order (possible all other types of orders too) not filled when its limit.
I had started all over with a brand new instance of Gainium from scratch with new bots, etc., so I think that should have rebuild the container?
So it’s LIMIT because TP percentage is LIMIT by default correct?
Then if we add a DCA using required change the limit order get cancelled and then uses market orders for the new TP
I’m a bit lost in your logic.
Required change only affects DCA order size, have no affect on TP order. TP order when its percentage and not trailing is always limit.
I assume you (also Aaron, based on his comments) expect it work a some kind different. You can create a feature request with logic description
Yes should work.
No, it’s like coinbase just isn’t getting a ticker feed like other exchanges. We may have to re-logic this TP strategy anyway though to work around limit orders so our funds aren’t tied up, and that means I could probably go back to PRICEROLE=candle anyway and that works fine and takes fewer server resources. I’ll ponder all this…
Ok, finally I found a typo.
Can you add to the env file
COINBASE_API_KEY=
COINBASE_API_SECRET=
with the same content as
COINBASEKEY=
COINBASESECRET=
This is a workaround before I made a fix. I’m currently working on adding another exchange and will fix it a release.
After you added vars, you can delete price connector and start it again, no need to reload the whole app.
Haha, sure, let me go try that!
Still seems like the problem remains. I duplicated COINBASEKEY= to COINBASE_API_KEY= and COINBASESCRET= to COINBASE_API_SECRET= with my data, but I left both in the .env file. I shut down the entire container and started it back up. I waited three hours. I see trades that have not closed at 2% TP. I shut down the entire docker image and started it back up, trades closed when the services started.
Ok, sorry to inconvenience. I just now was able to test it.
You can actually ingore those new .env values. I updated docker compose to map env vars names, and added supported exchanges
You don’t need to restart whole app, just pull latest commit and run
docker compose up -d price-connector
it will restart continer with correct env variables and ticker stream in coinbase should start work
Hmmm… I let it run for an hour, still didn’t seem to close anything new until I shut down and started back up and then another $1.57 or so closed and the total profit incremented again from a couple bots that were a bit over 2% and hadn’t taken profit yet. I haven’t added redis insight back or analyzed that again yet though, just let it run for an hour and came back to check.
I manually pulled docker-compose.yml again just to be certain it was updated, let me run this again for a bit and see…
Let me know the result
Still had the same problem. Gave up for the weekend to work on other projects though, hehe
Is your location is US?
I will try later with VPN
Yeah, USA. Not surprised if that’s the root of the whole problem, LOL!
I just tested with USA VPN. Started price connector with only coinbase support and It works from my side.