-
Notifications
You must be signed in to change notification settings - Fork 137
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
ERROR — Cannot subscribe to K-Line: No right to subscribe #45
Comments
Hello @munum , thank you for submitting an issue! 👍 We highly appreciate it if you work on it as well. |
Hmm from the error message, I think there may be an issue with the stock code you've provided. If you want to subscribe HK.00001, need to input "HK.00001" instead of "00001" only, cuz this error message may be thrown either if you are illegible to subscribe (e.g., used up all the subscription quota) or providing an illegal stock code. Let me know if you have any issue after changing the stock code. Thanks for using FutuAlgo! |
I've been working on this issue for a while now. I can confirm that "HK.00001" is the input. Is it essential to have LV2 for it to behave correctly? Is BMP adequate? |
No, BMP level subscription is sufficient to do paper trading, historical data download (with limited quota) and other functions like stock filtering.
This error code was thrown by Futu library, and I suspect it is because of incorrect stock code was provided so they cannot download/subscribe any data of this ticker.
…On 25 Mar 2023 at 00:43 +0800, Michael ***@***.***>, wrote:
I've been working on this issue for a while now. Is it essential to have LV2 for it to behave correctly? Is BMP adequate?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
But doesn't
|
Hi there. I'm trying to run the
main_backend.py
but I keep getting an error:ERROR — Cannot subscribe to K-Line: No right to subscribe 00001
I have a subscription quota of 300 according to OpenD and subscription status query also shows 300:
INFO — Query Subscription Quota: {'total_used': 0, 'remain': 300, 'own_used': 0, 'sub_list': {}}
Does anyone know why this might be the case?
Any advice appreciated. Thanks.
The text was updated successfully, but these errors were encountered: