BrownChiLD
Newbie
Offline
Activity: 18
Merit: 0
|
|
December 21, 2017, 12:29:00 AM |
|
Oh my, awesome release man!! It's a nice Christmas gift for us LeoNardo users/customers. However, I was hoping the following 2 features would be included already by now: MUST HAVE FEATURE: PING PONG Strategy with STOP LOSS! <-- like, seriously REALLY WANTED FEATURE: Margin Trade based on BTC amount... ie: Start a bot with specific BTC amount (0.1 btc for example) and let it buy and sell or play with 0.1btc only really hope you guys would look into this feature really soon Happy Holidays!
|
|
|
|
Kuku
Newbie
Offline
Activity: 8
Merit: 0
|
|
December 21, 2017, 12:40:30 AM |
|
leonArdo failed to place an order when BB Bot recognized the right time to buy. Tried to isolate the issue and created a manual order with leonardo which was successful. So leonArdo has no issues placing an order but in combination with BB Bot it does for me. 12/21 01:20:37 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:20:52 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:20:52 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:21:01 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:21:16 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:21:16 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:21:24 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:21:39 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:21:39 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:21:48 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:22:03 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:22:03 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:22:12 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:22:27 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:22:27 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:22:36 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:22:51 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:22:51 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:23:02 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:23:17 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:23:17 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:23:27 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:23:42 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:23:42 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:23:53 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:24:08 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:24:08 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:24:21 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:24:36 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:24:36 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:24:50 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:25:05 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:25:05 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:25:18 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:25:33 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:25:33 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:25:48 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:26:03 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:26:03 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:26:17 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:26:32 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:26:32 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:26:45 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:27:00 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:27:00 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:27:14 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:27:29 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:27:29 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:27:42 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:27:57 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:27:57 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:28:11 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:28:26 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:28:26 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:28:40 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:28:55 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:28:55 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:29:08 am poloniex:BCH/BTC: trying to recover order (try 1 of 2) 12/21 01:29:23 am poloniex:BCH/BTC: trying to recover order (try 2 of 2) 12/21 01:29:23 am poloniex:BCH/BTC: order recovery failed (returning null doc) 12/21 01:29:28 am poloniex:BCH/BTC: error placing order: json2::TypeError: asObject called on non Object :doc: null 12/21 01:29:28 am poloniex:BCH/BTC: spot order could not be placed due to error during order placement 12/21 01:29:28 am poloniex:bot:BCH/BTC: [BB-BCH] spot order could not be placed
BB Bot stopped itself after this log entry.
|
|
|
|
harmanq
Newbie
Offline
Activity: 27
Merit: 0
|
|
December 21, 2017, 01:04:08 AM |
|
I'm trying the ping-pong strategy in the new version 3.7.0 and now I can see that it respects the existing balance. However, you do not immediately place the sales order. The record shows the following information. 12/20 07:37:14 pm bittrex:bot:NXT/BTC: [NXT-PP02] transition to "creating order" 12/20 07:37:15 pm bittrex:bot:NXT/BTC: [NXT-PP02] transition to "placing order" 12/20 07:37:17 pm bittrex:bot:NXT/BTC: [NXT-PP02] transition to "waiting for order to become active" 12/20 07:37:27 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:38:08 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:38:31 pm bittrex:bot:NXT/BTC: [NXT-PP02] transition to "waiting for order settlement" 12/20 07:38:33 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:38:51 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:39:14 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:39:37 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:40:21 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:40:59 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:41:11 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:41:44 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:41:45 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:42:19 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:42:26 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:42:55 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:43:07 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:43:42 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:43:56 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:44:38 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:45:22 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:46:08 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:46:15 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:46:45 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:47:00 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:47:16 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:47:44 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:47:48 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:48:20 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:48:29 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. -- erased old log entries -- 12/20 07:49:00 pm bittrex:bot:NXT/BTC: [NXT-PP02] trying to use order-to-trade-association for order (ID:2178) 12/20 07:49:14 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:49:57 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/20 07:50:37 pm bittrex:NXT/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document
|
|
|
|
Amaralluis
Member
Offline
Activity: 132
Merit: 10
|
|
December 21, 2017, 01:10:30 AM Last edit: December 21, 2017, 01:32:36 AM by Amaralluis |
|
Awesome release thank you very much.
Is there some sort of guide of what the different options available for the new BB bot do? What does the BUY/SELL BAND (1/2/3) do?
I think I understand what the other options do its just the Band that Im not too sure about.
Hmm I guess I need some explanation about the Stop Loss Buying/Selling as well. Im not sure how it works.
It would been nice if we could update the BUY/SELL signal on the fly without having to stop the bot.
|
|
|
|
maximil
Newbie
Offline
Activity: 17
Merit: 0
|
|
December 21, 2017, 01:16:38 AM |
|
leonArdo 3.7.0 releasedIt's finally here, our Bollinger Band Bot!! This entailed a complete re-working of leonArdo's strategy framework and will mean that new strategies can be much more easily added in the future. We are also really excited to bring you HitBTC, which is definitely the fastest exchange we have ever worked with. And something else that a lot of customers were asking for, support for Raspberry Pi is now available! Bollinger Band Bot- Simple to use and beautifully rendered (see setup image below)
- Includes optional stop loss on both the buy and sell sides
- Force buy and sell options added
Major new features- Raspberry Pi (ARMv7) support added (beta, see release notes below)
- HitBTC market added (including websockets) - it's lightning fast
- Force index indicator added - an elegant indicator... for a more civilized age
Minor new features- Moveable currency pair/market tabs enabled
- Added csv-export for funds
Complete rework of leonArdo's strategy/bot framework- Each strategy instance is now now executed in a dedicated thread (removes linkages of strategy logic to the UI-thread)
- Added a new and more powerful hierarchical-state-machine (HSM) backend that will be used for new strategies
- Added the concept of indicator-based strategies
- Introduced a hierarchical definition of strategies for easier re-use of generic features such as stop-loss
- Implemented generic spot buy and sell orders (native spot orders will be added for exchanges that support this in the near future)
- Added symmetric stop-loss for the buy and sell side
- Added a concept of strategy-annotations that are locked to a certain chart-view and candle-width (added a small icon that indicates, to which view a strategy is currently linked to)
- Several improvements/extensions to the UI of strategies (such as sections of parameters or lines under component titles)
- Added an internal mechanism to augment existing time-aligned indicators with custom rows as linear-combinations of existing rows
- Optimized suspend/restore handling of strategies
- Used all these new features to implement the new Bollinger Bands strategy
- Furthermore, these changes will allow for much easier addition of new future strategies
General improvements and bug fixes- Improved handling of wrong API messaging in the Static Ping Pong Bot - should be useable again
- Better handling of Unicode characters in path names
- Fixed y-axis for some indicators
- New radio group appearance
- Order book decimal slider adapted to be more flexible
- Decimal places reworked
- Extended http class with additional functionalities
- Disabled the always-stay-on-top attribute of the login-window
- Fixed several smaller issues with our internal json-parsing module
- Fixed and tuned small issues with our special value-slider
- Fixed an issue with the internal association handling between orders and strategies
- Fixed background color of movable tabs
- Added 'About' tab to the settings-widget
- New license and disclaimer window style added
Market-specific improvements and fixes- On Bittrex, increased order book depth by querying asks and bids separately
- Change default list of currencies for Bittrex
- No longer show currency pairs that Bittrex marked as "disabled"
- On Poloniex, fixed minimum trading amount
- On Bitfinex, trailing stop and stop orders fixed (got deactivated with last websockets update)
Linux-specific improvements- Provide more meaningful error message if certain packages are not present
- Increase Linux distribution compatibility by providing libssl-1.0 if needed
Note: If anyone has an issue with the new version please let us know: support@marginsoftware.deThe previous 3.6.0 version is still available for download as a fallback option. How can you get your copy?If you are an existing customer you can simply click on the "update available!" link on the leonArdo login screen and download this version. Or if you are new just head over to website and click through to our Products section. You can also download a demo version of leonArdo from the website to try before you buy. Bollinger Band Bot setup Notes on the new ARM build- This is an ARMv7 binary that should run on ARMv7 and backwards-compatible ARMv8 SoCs like the Cortex-A8. The Linux distribution installed has to be an ARMv7 build, too, however. Systems that should be compatible include the Raspberry Pi 2 and Raspberry Pi 3
- This is a beta release! Please report any experiences with different ARM-based systems back to us
- Be aware of the hardware limitations of SoC systems! Use a reasonable number of currency pairs and strategies to avoid problems
- These limitations especially concern memory. Setting up a generous amount of swap space is advisable and/or use a service that dynamically allocates swap such as "swapspace"
- Before being able to use leonArdo on Raspbian or similar Debian-based distributions, a "sudo apt-get install libqt5websockets5" and a "chmod +x leonArdo.arm" is needed
Woah, it happened! Amazing work lads, very happy to see this! Don't get too drunk this friday
|
|
|
|
dbolivar
Member
Offline
Activity: 119
Merit: 10
|
|
December 21, 2017, 01:18:22 AM |
|
leonArdo 3.7.0 released
Oh YEAH!! Have I said you guys are AWESOME? I think so, but I'll say it again, just in case. And it was sooner than expected, a very welcome Christmas gift. The BB bot, together with the amazing visual interface that's leonArdo's showcase, is HUGE. And the other improvements/bug fixes are very welcome too. Will play with it soon.
|
|
|
|
wabbits
Newbie
Offline
Activity: 17
Merit: 0
|
|
December 21, 2017, 02:20:08 AM |
|
hi Team, quick question... i got margin maker setup to analyze every hour (short time frame) but i keep noticing that if the coin value averages upward, the BUY ORDER isn't adopted and gets tuck at previous buy order. Here's an example , happened just now: https://i.imgur.com/FC9bLQo.jpgBuy order's been stuck at that level for hours... shouldn't margin maker move it up based on analysis per hour? Leonardo could have made some nice trades already during these hours .. what am i doing wrong? yes it should, and it used to work as expected but lately (last few days) it's been doing this. I have noticed this as have others. It seems to be an issue with Bittrex API as far as I can tell. If you stop the bot and start it again, it usually fixes the issue for a while. Thanks for the head's up mate. strange though coz i think it's leonardo's task to analyze current prices/trend then remove order and replace it with new entry.. i dont understand how Trex api is causing this, unless trex is having problems cancelling and placing orders, which, i dont think it is coz i've also been trading manually, just fine. I'm new at this so I'll let someone more experienced chime in if necessary but I think it's the same issue posted about - it's most likely to do with the last sell price and your minimum effective gain - the bot is optimised for margin trading, so will compare the sell-to-buy ratio and keep the next buy within the minimum effective gain %. Setting the gain to negative allows the next buy to move "against" the previous sell, and vice versa. It is the min eff margin. Yes setting it to a negative will allow it to rise. https://www.google.com/search?client=ubuntu&hs=944&channel=fs&ei=upY6Wr-ROOnBjwSH9rjICQ&q=site%3A[Suspicious link removed]+min+eff+gain&gs_l=psy-ab.3...12629.14535.0.14962.6.6.0.0.0.0.233.719.0j4j1.5.0....0...1c.1.64.psy-ab..1.0.0....0.ZxreHxUc2G8 Here is a Mona example: https://image.ibb.co/bBUZAR/image.pngMin Eff Gain: https://image.ibb.co/cKsAjm/image.pngI have enough experience with setting the Statistics Window for each pair over a period of weeks as each coin appears to have its own vibration. After a couple of weeks I never nanny, only restart those that have stopped or received bad API feedback IE immediately opens the next sell 7% below the prior buy. I'm not experienced in this either, so forgive my ignorance. I think i may have misunderstood how the min. gain works. Is the min eff. gain, the min. effective gain on the entire purchase price or min. effective gain as a part of the effective gain? On what @Cryptojezza said: "it's most likely to do with the last sell price and your minimum effective gain - the bot is optimised for margin trading, so will compare the sell-to-buy ratio and keep the next buy within the minimum effective gain %. Setting the gain to negative allows the next buy to move "against" the previous sell, and vice versa. " wouldn't the bot be calculating the gain/loss on the preceding purchase only and not on the sale? As the margin is calculated on the difference between the purchase and sale price? If you were to set the min. effective gain @ 0 it shouldn't it still reset the purchase price within the statistical window? Thank you
|
|
|
|
harmanq
Newbie
Offline
Activity: 27
Merit: 0
|
|
December 21, 2017, 03:28:05 AM |
|
How can I install leonard on the raspberry? I have no experience with *. arm extension files Thanks in advance
|
|
|
|
Saturable
Newbie
Offline
Activity: 12
Merit: 0
|
|
December 21, 2017, 03:42:54 AM |
|
leonArdo 3.7.0 released
It's finally here, our Bollinger Band Bot!! This entailed a complete re-working of leonArdo's strategy framework and will mean that new strategies can be much more easily added in the future. We are also really excited to bring you HitBTC, which is definitely the fastest exchange we have ever worked with. And something else that a lot of customers were asking for, support for Raspberry Pi is now available!
*snip*
This looks great! Right now I can't stand Bittrex, so I'm trading on Binance. I hope support for that is in the next release. For now, I can't use leonArdo, but I'm excited to play with the BB bot in the future!
|
|
|
|
harmanq
Newbie
Offline
Activity: 27
Merit: 0
|
|
December 21, 2017, 04:48:54 AM |
|
I was testing the new version in bittrex demo mode and something weird happened. At the time of executing a purchase, the opening balance of 0.5 BTC was reduced to almost nothing, with no purchases presented in the registry. In reviewing the balances I note that the difference in BTC has disappeared, it does not correspond to any purchase. Could you check what's going on? And check if the same happens in other exchanges in demo mode. Or if it also happens in real mode.
|
|
|
|
hansng1988
Copper Member
Newbie
Offline
Activity: 11
Merit: 0
|
|
December 21, 2017, 05:49:47 AM |
|
After upgrading to 3.7.0 on macOS I can't see my completed orders for any coins. The log is below: 12/21 12:21:11 pm bittrex:gui:VTC/BTC: initializing orderbook 12/21 12:21:13 pm bittrex:gui:VTC/BTC: initializing active orders 12/21 12:21:14 pm bittrex:gui:VTC/BTC: initializing completed orders 12/21 12:21:40 pm bittrex:db:VTC/BTC: http request for database failed for currency pair VTC/BTC (please tell us by mailing contact@marginsoftware.de) 12/21 12:21:44 pm bittrex:VTC/BTC: Network error in init(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:21:44 pm bittrex:gui:VTC/BTC: initializing margin positions 12/21 12:21:56 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:22:42 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:23:29 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:24:15 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:24:58 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:25:42 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:26:28 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:27:11 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:27:55 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document.
For the time being, I'm back to 3.6.0 to see if it could help. Appreciate it if you can promptly check and update. Thank you.
|
|
|
|
leonArdo@margin (OP)
Legendary
Offline
Activity: 1989
Merit: 1008
|
|
December 21, 2017, 07:55:28 AM |
|
Good morning,
We will have a look at the reports asap and get back to you guys!
All the best,
Rene
|
|
|
|
biege
Newbie
Offline
Activity: 34
Merit: 0
|
|
December 21, 2017, 07:56:44 AM |
|
Hi. Sorry if I'm too lazy to back read. Are you guys having problems seeing the correct short running percentage when doing margin? Instead of the correct margin % i'm getting around 280% or so. thank you for your response.
Hi, can you send a mail with a screenshot and description to support@marginsoftware.de? We will then have a look asap! All the best, Rene Hi, so far I am not getting that issue with ver. 3.7.0. I'll let you know when it happens again. BTW, I don't see the bollinger bot to be fulfulling orders. What's the mechanism of this bot, can you provide a brief detail about how it does the trade? Thank you!
|
|
|
|
Helmer
Newbie
Offline
Activity: 11
Merit: 0
|
|
December 21, 2017, 07:58:57 AM Last edit: December 21, 2017, 08:34:45 AM by Helmer |
|
As other ppl has pointed out. Using the Boillinger bot - It does buy (havn't had any sales yet). But the Active orders doesn't show: Windows 10, Leo v. 3.7, Bittrix 12/21 08:27:29 am bittrex:gui:XMR/BTC: initializing orderbook 12/21 08:27:31 am bittrex:gui:XMR/BTC: initializing active orders 12/21 08:27:32 am bittrex:gui:XMR/BTC: initializing completed orders 12/21 08:27:59 am bittrex:XMR/BTC: Network error in init(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:27:59 am bittrex:gui:XMR/BTC: initializing margin positions 12/21 08:29:44 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:32:05 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:40:17 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:40:54 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:41:22 am bittrex:XMR/BTC: spot order cycle on XMR/BTC already bought:0 XMR desired: 0.02769344 XMR 12/21 08:41:23 am bittrex:XMR/BTC: the current balance of BTC was reduced by 2.0% to 0.00670771 XMR in order to ensure the order can be executed as spot order 12/21 08:41:24 am bittrex:XMR/BTC: we have: 0.00670771 BTC. The amount needed to ensure full buy at current price conditions is0.00073986 BTC 12/21 08:41:24 am bittrex:XMR/BTC: more BTC available than we need: checking whether the used price can be increased to insure the order gets fully filled 12/21 08:41:24 am bittrex:XMR/BTC: using better price 0.23677669 BTC 12/21 08:41:24 am bittrex:XMR/BTC: placing buy order: 0.02769344 XMR @0.23677669 BTC 12/21 08:41:35 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:41:57 am bittrex:bot:XMR/BTC: [strategy-7] handling event 0 in state 7 12/21 08:42:12 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:42:45 am bittrex:XMR/BTC: order placed successfully 12/21 08:42:45 am bittrex:XMR/BTC: as intended, order went through immediately 12/21 08:42:45 am bittrex:XMR/BTC: spot order execution successfull! got 100 % of the desired amount (0.02769344 XMR of 0.02769344 XMR) 12/21 08:42:49 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:44:22 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:44:49 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 08:56:29 am bittrex:XMR/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document.
*Edit* Boiling bot does sell OK: 12/21 09:17:36 am bittrex:bot:XMR/BTC: [strategy-7] successfully placed order :limit sell 0.027693 XMR(@0.027002 BTC per XMR)
|
|
|
|
leonArdo@margin (OP)
Legendary
Offline
Activity: 1989
Merit: 1008
|
|
December 21, 2017, 07:59:56 AM |
|
After upgrading to 3.7.0 on macOS I can't see my completed orders for any coins. The log is below: 12/21 12:21:11 pm bittrex:gui:VTC/BTC: initializing orderbook 12/21 12:21:13 pm bittrex:gui:VTC/BTC: initializing active orders 12/21 12:21:14 pm bittrex:gui:VTC/BTC: initializing completed orders 12/21 12:21:40 pm bittrex:db:VTC/BTC: http request for database failed for currency pair VTC/BTC (please tell us by mailing contact@marginsoftware.de) 12/21 12:21:44 pm bittrex:VTC/BTC: Network error in init(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:21:44 pm bittrex:gui:VTC/BTC: initializing margin positions 12/21 12:21:56 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:22:42 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:23:29 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:24:15 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:24:58 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:25:42 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:26:28 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:27:11 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document. 12/21 12:27:55 pm bittrex:VTC/BTC: Network error in buffer(trades): LocalError (as Error): Could not parse open orders list: Http post error for method account/getopenorders, got empty document.
For the time being, I'm back to 3.6.0 to see if it could help. Appreciate it if you can promptly check and update. Thank you. Hi, it could be just an issue with Bittrex's API. Can you send on the full logs to support@marginsoftware.de? We will then have a closer look. All the best, Rene
|
|
|
|
cryptojezza
Newbie
Offline
Activity: 4
Merit: 0
|
|
December 21, 2017, 08:21:55 AM |
|
Awesome release guys, talk about getting value for our money Thanks so much for such a great product, and the outstanding customer service! It's early days for me but I'm seriously impressed by my return percentages so far
|
|
|
|
miknl
Newbie
Offline
Activity: 8
Merit: 0
|
|
December 21, 2017, 08:24:44 AM |
|
Hi, it could be just an issue with Bittrex's API. Can you send on the full logs to support@marginsoftware.de? We will then have a closer look. All the best, Rene Same problem here on Bittrex but Poloniex also doesn't seem to work... Log says timeout: 12/21 08:48:17 am poloniex:XMR/USDT: http error acquiring ticker info [code: 4]: Timeout (the connection to the remote server timed out) 12/21 08:48:17 am poloniex:XMR/USDT: ticker data update failed 12/21 08:48:34 am poloniex:gui:XMR/USDT: initializing orderbook 12/21 08:48:35 am poloniex:gui:XMR/USDT: initializing active orders 12/21 08:48:36 am poloniex:gui:XMR/USDT: initializing completed orders 12/21 08:48:37 am poloniex:gui:XMR/USDT: initializing margin positions 12/21 09:14:41 am poloniex:XMR/USDT: http error while querying orderbook data: [code: 4]: Timeout (the connection to the remote server timed out) 12/21 09:17:00 am poloniex:XMR/USDT: http error while querying orderbook data: [code: 4]: Timeout (the connection to the remote server timed out) 12/21 09:22:33 am poloniex:XMR/USDT: http error acquiring ticker info [code: 4]: Timeout (the connection to the remote server timed out) 12/21 09:22:33 am poloniex:bot:XMR/USDT: [strategy-3] handling event 0 in state 15 12/21 09:22:33 am poloniex:bot:XMR/USDT: [strategy-3] handling event 0 in state 2 Interesting: the MarginMaker strategy works fine!
|
|
|
|
leonArdo@margin (OP)
Legendary
Offline
Activity: 1989
Merit: 1008
|
|
December 21, 2017, 08:43:30 AM |
|
why Leonardo sell coin in minus case. Limit sell: 4341 satoshi Limit buy: 4347 satoshi Is there any settings about it ? I dont want to sell if seliing price is under buying price https://ibb.co/d15KUmI see you are testing on the demo. Please see release notes. You are using the demo version and it does not support spot orders yet, which the Bollinger Band uses. We will release a patch for the demo ASAP. But in general there is no absolute protection on the situation you depict. There is as of yet no Min Effective Gain % parameter. Best wishes, Jonathan
|
|
|
|
leonArdo@margin (OP)
Legendary
Offline
Activity: 1989
Merit: 1008
|
|
December 21, 2017, 08:45:18 AM |
|
I was testing the new version in bittrex demo mode and something weird happened. At the time of executing a purchase, the opening balance of 0.5 BTC was reduced to almost nothing, with no purchases presented in the registry. In reviewing the balances I note that the difference in BTC has disappeared, it does not correspond to any purchase. Could you check what's going on? And check if the same happens in other exchanges in demo mode. Or if it also happens in real mode.
Please see the release notes! The demo version does not support spot orders yet, so the funds are messed up if you use the BB bot with the demo! All the best, Jonathan
|
|
|
|
gnoe
Newbie
Offline
Activity: 61
Merit: 0
|
|
December 21, 2017, 08:50:54 AM |
|
Great upgrade, support & prices! If someone performs any tests with Raspberry Pi, please share the results.
|
|
|
|
|