-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x.Stream.subscribe.getCandles bug (caused by xOpenHub server side logic) #17
Comments
Is there anything you can do on your library side that is not a tiny hack since the root 'cause is located on XTB side ? |
Hi @solarfrantz |
@solarfrantz btw they still didn't respond to me, I'm 100% they won't do any changes on their side:) |
That's weird because Python code works fine:
You need official wrapper (xAPIConnector) from here: http://developers.xstore.pro/api/wrappers/ |
@wtld I will check this later |
@peterszombati any info here? |
@peterszombati any update about this problem ? |
Thank you very much for this information. Thanks again for this information! |
2024 and found this issue is still alive. Using https://github.com/sgflt/xapi-websocket-client |
did you manage to solve the problem with Command: getCandles ? |
I just call getChartLastRequest before subscription and it seems to be working. |
Thanks, I changed the calling order as you wrote and it worked <3 |
I'm using python that not working for me too. I have the official wrapper but getCandles not working. Sent email to the support waitin for the answer. I'm the only one in this situation. I try call getChartLastRequest before nothing change. Sad |
@htimi You must use getChartLastRequest for M1 interval, before retrieving candles |
@damiancyrana thanks it works !!!! Maururu (thanks in Polynesia langage) |
x.Stream.subscribe.getCandles
doesn't working if you didn't do a price history request for specific symbolexample with
BITCOIN
:It won't work.
You have to do a request to BITCOIN price history then subscribe for candles
example with
BITCOIN
:The text was updated successfully, but these errors were encountered: