|
|
|
|
535
|
I did that using the [Universal-Arduino-Telegram-Bot library](https://github.com/witnessmenow/Universal-Arduino-Telegram-Bot).
|
535
|
I did that using the [Universal-Arduino-Telegram-Bot library](https://github.com/witnessmenow/Universal-Arduino-Telegram-Bot).
|
536
|
Unfortunately it really takes a long time to poll for new messages, between one and two seconds.
|
536
|
Unfortunately it really takes a long time to poll for new messages, between one and two seconds.
|
537
|
Because I don't really use interrupts and handle all timings of valves and pumps in a busy-loop that also polls all available input methods, this causes quite noticable delays in both the UI as well as the timing of operations.
|
537
|
Because I don't really use interrupts and handle all timings of valves and pumps in a busy-loop that also polls all available input methods, this causes quite noticable delays in both the UI as well as the timing of operations.
|
538
|
-But it works, and with long polling times the machine is still usable.
|
|
|
|
|
538
|
+
|
|
|
539
|
+My friend [Philipp](https://www.phschoen.de/) suggested I should use the [AsyncTelegram2](https://github.com/cotestatnt/AsyncTelegram2) library instead, which I did.
|
|
|
540
|
+This greatly reduces the overhead of polling for new messages, so there is no noticeable impact on the UI and functionality.
|
539
|
|
541
|
|
540
|
<!--%
|
542
|
<!--%
|
541
|
lightgallery([
|
543
|
lightgallery([
|