After upgrade to new v.1.58 under OANDA
All indexes are unavailable!

Load EUR/USD prices.. 2400 h
Load USD/CHF prices.. 2400 h
Load GBP/USD prices.. 2400 h
Load USD/CAD prices.. 2400 h
Load USD/JPY prices.. 2400 h
Load AUD/USD prices.. 2400 h
!Invalid instrument: NAS100 is not a valid instrument
!Invalid instrument: NAS100 is not a valid instrument
Error 053: NAS100 unavailable at this time
!Invalid instrument: SPX500 is not a valid instrument
!Invalid instrument: SPX500 is not a valid instrument
Error 053: SPX500 unavailable at this time
!Invalid instrument: US30 is not a valid instrument
!Invalid instrument: US30 is not a valid instrument
Error 053: US30 unavailable at this time
!Invalid instrument: GER30 is not a valid instrument
!Invalid instrument: GER30 is not a valid instrument
Error 053: GER30 unavailable at this time
!Invalid instrument: UK100 is not a valid instrument
!Invalid instrument: UK100 is not a valid instrument
Error 053: UK100 unavailable at this time
Load XAU/USD prices.. 2400 h
Load XAG/USD prices.. 2400 h

Hello! It can be easily fixed - in Z.ini select assets file named oanda.
I have another issue - in demo mode, Zorro shows trades but do not executes them on OANDA demo account. Hence, I cannot calculate P&L of the trades. Is it a correct behaviour of the demo mode on the OANDA demo account? I wanted to have a dry-run of a couple of weeks before going real, how it can be done with such a behaviour?

I am having a more annoying problem. The V20 API loads but it will not login. I get a message 'insuffcient information to Authorise. Invalid account. I follwed the manual directions to get a Token etc. and how to use it but it does not work. Any ideas?

- No trades on Oanda demo account: Zorro only shows trades when they are confirmed in the open trades list of the Oanda API. So they should be definitely open, but maybe you have several accounts and are not looking into the right one? Use the TradeTest script for making sure that you can trade on your Oanda account.

- Cannot login: Oanda does not accept the token for that account number. Either it's a V1 account, or the token is for a different account, or you have entered a wrong account number. Please check.