nemozny

You don't need to use /lib/orders, those are just for your convenience. You can construct the order by yourself, which is what I do. ``` const parent = orderId++ ib.placeOrder(parent,...

I think it is API version. I haven't seen a word about how this works, but from pilwon's comments somewhere in the code in here I've understood 76 is the...

There is 76, because nobody implemented the v100plus handshake. If you tell IB servers any higher version than 76, they will expect the handshake. I've switched my IB client and...

This I bothering me for a while and has to be fixed!

I just checked the gateway log and this crap is coming from IB itself. So this not a node-ib issue. 

@meteorpublish I tried, but I can't get v100plus handshake to work. This is above me. I took official Java client, official Python client and https://github.com/erdewit/ib_insync, but still no luck. Either...

@maxicus Great job! I am glad that you cracked the API handshake format!

I just tested outsideRth and it is working correctly, as @meteorpublish illustrated. I am using futures though. I am not 100% sure about the execution, but my MKT order got...

Verified STP LMT, both STP and subsequent LMT triggered outsideRth at 7:00 CT on GC contract, while trading hours start 8:30 CT.

OrderRef works, only you created two different ib.order objects and sent the second one. The correct sequence is: ```javascript let LMT = ib.order.limit('BUY', buyamount, the_price); LMT.orderRef = "Testing orderref abc123";...