[QUESTION]

[Night-Box]

Greetings !

I'm using yours API to create my own local terminal. I encountered a problem where I can't get historical data on OTC. This Api This doesn't allow you to do this? You can only get a few candles, and a new candle is built in a completely different place.

[sixtysixx]

Hello, which function are you using to complete this?

[Night-Box]

Hello, which function are you using to complete this?

Hello!

Thank you for your response.
From the documentation, I understand that the HistoricalDataApiModule module and the get_candles() function are responsible for this.

Could you please clarify:
Is get_candles() currently functional? If so, how should it be called?
If it's still under development, could you suggest the best approach for retrieving history in BinaryOptionsToolsV2? Perhaps there are other working functions for this purpose?

I also have an issue where I encountered a limit of 4 simultaneous subscriptions via subscribe_symbol().
As far as I understand from the documentation, this limit is set by the constant MAX_SUBSCRIPTIONS = 4 in the SubscriptionsApiModule.

Could you please clarify:
Is this a limitation on the PocketOption broker or a technical limitation of the library itself?
Is there a plan to increase or bypass this limitation in future versions? Or is there already a workaround so I can get more subscriptions at once and have constantly up-to-date data?

[theshadow76]

Hello, which function are you using to complete this?

Hello!

Thank you for your response.
From the documentation, I understand that the HistoricalDataApiModule module and the get_candles() function are responsible for this.

Could you please clarify:
Is get_candles() currently functional? If so, how should it be called?
If it's still under development, could you suggest the best approach for retrieving history in BinaryOptionsToolsV2? Perhaps there are other working functions for this purpose?

I also have an issue where I encountered a limit of 4 simultaneous subscriptions via subscribe_symbol().
As far as I understand from the documentation, this limit is set by the constant MAX_SUBSCRIPTIONS = 4 in the SubscriptionsApiModule.

Could you please clarify:
Is this a limitation on the PocketOption broker or a technical limitation of the library itself?
Is there a plan to increase or bypass this limitation in future versions? Or is there already a workaround so I can get more subscriptions at once and have constantly up-to-date data?

Hello for the subscribe_symbol_timed function the limit is set because pocketoption it self does not allow more, for the get_candles function I believe there is an known issue that returns inaccurate data, I belive the history function has the same problem.

[Night-Box]

Здравствуйте, для функции установлен лимит, потому что pocketoption сам не позволяет большего, и для этой функции, насколько я знаю, есть известная проблема, которая возвращает неточные данные, и, насколько я понимаю, у этой функции такая же проблема.subscribe_symbol_timed ``get_candles``history

I've come across bots and terminals that display the entire history. Perhaps they're partners with Pocket Option and have provided them with their API. I don't know =(

[theshadow76]

Or maybe they've been aggregating data for all of this time using there version of there subscribe_symbol or maybe they know something we don't 😅

[sixtysixx]

I believe compile_candles should work- if not please let us know

[sixtysixx]

I can send a code snippet in a few- that is if I don't happen to get distracted lol

[sixtysixx]

I also have an issue where I encountered a limit of 4 simultaneous subscriptions via subscribe_symbol(). As far as I understand from the documentation, this limit is set by the constant MAX_SUBSCRIPTIONS = 4 in the SubscriptionsApiModule.

Could you please clarify: Is this a limitation on the PocketOption broker or a technical limitation of the library itself? Is there a plan to increase or bypass this limitation in future versions? Or is there already a workaround so I can get more subscriptions at once and have constantly up-to-date data?

Pocketoption usually limits to 4 subscriptions per SSID however it isn't very strict and can be bypassed using the UI and switching quickly between assets. I'm unsure if the same applies to websockets or how to replicate the same thing

[sixtysixx]

I can send a code snippet in a few- that is if I don't happen to get distracted lol

Just got back to this- seems I mightve lost it or it doesnt work as expected. Ill see If I can work on this

[Night-Box]

Я могу отправить фрагмент кода через пару — если только не отвлекусь, ха-ха

Только что вернулся к этому — похоже, я его потерял или он работает не так, как ожидалось. Посмотрю, смогу ли я поработать над этим

Hi!
I tried to bypass the 4-subscription limit using a multi-worker architecture. This solves the problem, but unfortunately only partially =(
Yes, I can get more data, but everything is very slow, as if there's a heavy load. One problem I noticed with this setup is that when I switch between currency pairs, the charts for the other pair slip. I suspect this is because I'm constantly trying to get data, including updating the price for currency pairs and the payout percentage, meaning synchronization isn't working properly.

I tried setting up a single process and multiple clients.
To do this, I launched several independent PocketOptionAsync processes within a single Python process. Each client can hold up to four subscriptions. But unfortunately, I still couldn't convert this into a human-readable format. There were constant losses, or the chart was unstable and synced poorly.

I also tried using dynamic subscriptions (subscribing only to the required assets).
We subscribe only to the currently open asset plus the three most popular ones. When switching, we unsubscribe from the old one and subscribe to the new one. Then the candlestick data is lost, and when switching to another one The asset is being built from scratch, so it's a twisted story.

So, unfortunately, all my attempts have been unsuccessful so far. If you succeed, please let me know.

[Night-Box]

Pocketoption обычно ограничивает 4 подписки на SSID, однако это не очень строго, и его можно обойти с помощью интерфейса и быстрого переключения между ассетами

In that case, will the chart update in the background if I unsubscribe from a currency pair and switch to another? It seems, unfortunately, that's not the case.

[sixtysixx]

Pocketoption обычно ограничивает 4 подписки на SSID, однако это не очень строго, и его можно обойти с помощью интерфейса и быстрого переключения между ассетами

In that case, will the chart update in the background if I unsubscribe from a currency pair and switch to another? It seems, unfortunately, that's not the case.

I don't believe so

[Night-Box]

Я так не думаю

What should we do then? How do other developers or bots get around the 4-subscription limit? Does the platform itself provide its own API?

[sixtysixx]

The platform doesnt provide its own API- hence this project exists. You can quickly subscribe and unsubscribe whilst getting historical ticks as an alternative