Keyboard Shortcuts
Likes
Search
The 'EtradeOnly' order attribute is not supported.
|
Hey everyone, today I just started getting this error message:
ERROR 355 2168 Warning: The 'EtradeOnly' order attribute is not supported. ERROR 72 2169 Warning: The 'FirmQuoteOnly' order attribute is not supported. I went and looked up? And you can see at the bottom of the page:
So... obviously... its no longer supported LOL... Everything seems to be working fine with my programs.. This error pops up now every time an order is sent to the API. I guess they updated something? I am running TWS Build 983.2i, Apr 20, 2021 7:56:36 PM This is new to me, are you guys running into this message as well. How do we correct this? Or is there nothing to correct? Looking for some advice and experience as to what happened, what changed, ect ect.? |
|
开云体育I first ran into the EtradeOnly error a few weeks ago when it was raising a fatal error in my Python code.? I restarted everytihng and it went away.? Then last week I started noticing it again (along with the FirmQuoteOnly error) as an error, but being ignored by my code.? I thought it might be caused by leaving TWS up all week, but today I started TWS anew and still see the erros popping up on order entry.Note I do not have a real error management routine yet so all errors are display only unless they cause a fatal error in my Python code. I was about to post a question about this issue myself, so I appreciate Patrick mentioning it.? Nothing else to offer, Hugh On 4/26/2021 8:43 AM, Patrick C wrote:
Hey everyone, today I just started getting this error message: |
|
|
Nick
开云体育If you moved to a new TWS version recently then that would be a likely culprit. IB used to have separate "auto-updating" and static TWS versions (don't know if they still do). If you are running the auto-update version then you might have a new TWS version without realizing it. The other part is the API library. Perhaps those fields are initialized by default to values no longer support. You might look to see if you can explicitly set them to empty/undefined in the Order. Sorry I can't be more specific but I'm going from memory since I
haven't used TWS in a while and never used the IB libraries. On 4/26/2021 9:43 AM, Patrick C wrote:
Hey everyone, today I just started getting this error message: |
|
|
We are using the Java API and have not seen the warning. So I took a quick look at the recent API code versions and it looks like the Python API does indeed initialize the eTradeOnly and firmQuoteOnly fields in order.py with True. That must have been there for a while since I saw it in 973.07, 974.01, 976.01, and 981.01. All other languages initialize the fields with false. This looks like a bug to me and you might want to file a report with IB, In the mean time you could obviously patch order.py to get rid or the message. JR On Mon, Apr 26, 2021 at 08:43 AM, Patrick C wrote:
|
|
|
I saw the same in C++ as well. Forgot why they were popping up. I use the LATEST ibkr library. - Bruce On Mon, Apr 26, 2021, 11:22 AM JR <TwsApiOnGroupsIo@...> wrote:
|
|
开云体育I don't think this is a bug. ? There was an update to the API repository called 'Desupport of ETradeOnly, FirmQuoteOnly and NbboPriceCap attribs. (#1032)' about a week ago. ? If you have access to the Github, you'll find it at : ? ? Richard ? ? ? From: [email protected] <[email protected]> On Behalf Of JR
Sent: 26 April 2021 16:22 To: [email protected] Subject: Re: [TWS API] The 'EtradeOnly' order attribute is not supported. ? We are using the Java API and have not seen the warning. So I took a quick look at the recent API code versions and it looks like the Python API does indeed initialize the eTradeOnly and firmQuoteOnly fields in order.py with True. That must have been there for a while since I saw it in 973.07, 974.01, 976.01, and 981.01. All other languages initialize the fields with false. This looks like a bug to me and you might want to file a report with IB, In the mean time you could obviously patch order.py to get rid or the message. JR |
|
|
You have to agree to license and get invited to be able to see that Github project. Browse to beta API. - Bruce On Mon, Apr 26, 2021, 7:25 PM Patrick C <zenfiretrading@...> wrote: Thanks everyone! |
|
|
This raises a very good next question. Do you guys lock in versions of TWS API, TWS, ect ect to avoid these problems in the future? Or is this just going to be the dance moving forward when they change things? I am new to programming, and I have a locked in Python Virtual Enviroment on my computer just incase anything on the programming end updates and causes some type of chaos lol because I am sure Python 3.8 is not the end of it LOL
JR what do you think changed that all of a sudden now the "True" is sending off this warning? And is there an offical like "update list" that I can keep track of any changes.. and for my future reference when we are speaking about "TWS API" here are we talking about all the code that is in the folder I downloaded called "ibapi"? HMTODD, just for curiousity.. do you know why it was raising a fatal error? the EtradeOnly is for electronic quotes? I think? Does anyone here know what that applies too? ... I figured it all electronic... hahah And.. I just patched order.py and it removed the warning |
|
|
It looks like one of the recent TWS versions must have removed support "Excluded Quotes" and must have started to send the warnings when orders set one r both fields to true. As you can see below, older TWS versions had configuration parameters related to the two order object fields, but they do not exist in my TWS 981.2w any longer. On Mon, Apr 26, 2021 at 06:52 PM, Patrick C wrote:
... |
|
HMTODD, just for curiousity.. do you know why it was raising a fatalerror? the EtradeOnly is for electronic quotes? I think? Does anyone here know what that applies too? ... I figured itall electronic... hahah I don't have the history to say why it was raising a fatal error.? I looked back and will say that first ocurrance was on April 16 and was preventing execution of some option orders.? When I restarted TWS I remember it went through an update cycle.? I assumed they recognized the problem and fixed it, but never followed up.? In hindsight I would guess the non-fatal errors continued and I just didn't notice them until maybe Thursday of last week. It was concerning at the time because my plan is for this system to run and trade without constant monitoring.? I run some models on QuantConnect and others directly on IB through the api.? I expect the api models to be at least as stable as the QC versions. Hugh |
|
|
Nick
开云体育If TWS allows a connection from your version of the API then the
attributes themselves are supported. It's particular values of the
attributes that are no longer accepted so setting to False is the
right thing to do. On 4/30/2021 3:55 PM,
neil@... wrote:
This is untested, but since the two attributes are unsupported, I feel comfortable just setting them to False when I create the order object. |
|