Bittrex Plugin

Hi Forum, jcl

after a break from automated trading i was revisiting my bittrex stuff and found out it wasnt working anymore. Anything requesting historical tickdata, even one minute, returns the following error:

strategy compiling...........
Login 0 Bittrex 1.1.. at UTC 03-27 09:28
Load ETHUSDT prices..
Error 062: Can't open strategy361484.t1 (wb:22) - ETHUSDT history unavailable!
Error 055: No bars generated
Logout.. ok

I checked the asset and accountlists.
Scripts without Lookback are doing fine.
Calls with assethistory to use API 2 are fruitless, at least for me.
I received an email last year on ending support for API 1.


Any suggestions? Will there be an update to the Plugin?

Thomas

Update:
The problem appears also with Binance. It also appears on my vps with windows server instead of windows 8 on a virtual environment on my mac. experimenting with uac etc doesn't help.

However the problem disappears when switching to an old version of Zorro, here 2.18, instead of the newly installed beta as of today.

So the problem isn't gone, please suggest anything that comes to your mind:)

Thx Thomas

Well then, it likely has nothing to do with your plugin. You just repeated the behavior with two plugins. And more importantly, you got this message:
When Zorro launches, it usually loads history into a temporary history file with your strategy name. It could be a file access clash. Do you have multiple Zorro instances running simultaneously?

You can run detailed info by oP Group support and maybe they can determine the culprit.

Exactly.


I was thinking along those lines - i played around with moving zorro to different folders, also on another machine/ other operating system. Zorro normally behaves very good with multiple instances. But i didn't run another, no. Honestly i ran out of ideas for now.
I run zorro on a parallels virtual machine(Windows 8) on osx, and an ec2 instance. There was never a filesystem problem before.
I reinstalled Zorro clean. Tried a few different scripts, even Workshop Scripts, fumbled around with assetlists and accountlists.

Windows error 22 indicates a disabled device, or outdated driver.