Skip to content
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

Large Telegram traffic #7

Open
denis-stepanov opened this issue Jan 1, 2021 · 1 comment
Open

Large Telegram traffic #7

denis-stepanov opened this issue Jan 1, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@denis-stepanov
Copy link
Owner

From documentation:

The underlying library Universal-Telegram-Bot uses polling to receive new messages. Frequency of polling determines how quickly bot will react on your commands. The default set in the sketch is 10 seconds, meaning bot will lazily respond to your command anytime between 0 and 10 seconds. In this application it is not important to have fast response, but if you want to make it quicker, change POLL_INTERVAL constant in Telegram.cpp. Note that even with 10 seconds the application generates a lot of traffic (like tens of GB per month). The reason for this is not yet understood — it could be a bug or misuse of the library.

This bug is to investigate the traffic issue.

@denis-stepanov denis-stepanov added the enhancement New feature or request label Jan 1, 2021
@denis-stepanov
Copy link
Owner Author

This seems to be a "feature", e.g., see open bug reports witnessmenow/Universal-Arduino-Telegram-Bot#148, witnessmenow/Universal-Arduino-Telegram-Bot#143 (comment), etc. All report traffic of similar magnitude. This seem to be somewhat alleviated when long poll is used, but it will block the loop() for long - something we cannot afford.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant