| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2023-02-14 | telegram-chat: never decrease the local offset |  Christian Hesse | 1 | -1/+1 | |
| 2023-02-14 | telegram-chat: add debug message for handled updates | Christian Hesse | 1 | -0/+2 | |
| 2023-02-14 | telegram-chat: add updateid in log messages | Christian Hesse | 1 | -3/+4 | |
| 2023-02-07 | telegram-chat: use complete property name | Christian Hesse | 1 | -1/+1 | |
| 2023-02-04 | telegram-chat: handle exceeded file read size | Christian Hesse | 1 | -1/+2 | |
| 2023-02-03 | telegram-chat: no need to :put ... | Christian Hesse | 1 | -2/+2 | |
| ... a simple change to root dir is sufficient. | |||||
| 2023-02-03 | telegram-chat: log with severity debug only... | Christian Hesse | 1 | -1/+1 | |
| ... as failed request are quite common. | |||||
| 2023-02-03 | telegram-chat: delay confirmation of updates | Christian Hesse | 1 | -6/+8 | |
| Several devices can communicate with the same bot, and we want all of them to receive their updates. However this can be tricky, as... * ... sometimes internet connection can be unreliable or saturated. * ... device can be busy with long running command. * ... the Telegram bot api servers seem to implement what ever kind of rate limiting. Anybody can give details? So let's confirm the update id after third request only. 😁 This gives delayed devices some extra chances to catch up. | |||||
| 2023-02-03 | telegram-chat: log warning only when trying to activate | Christian Hesse | 1 | -2/+5 | |
| 2023-02-03 | telegram-chat: handle missing username | Christian Hesse | 1 | -1/+3 | |
| 2023-02-02 | telegram-chat: discard messages without text | Christian Hesse | 1 | -1/+1 | |
| 2023-02-02 | telegram-chat: allow to modify the time to wait for command | Christian Hesse | 1 | -1/+3 | |
| For now this is a hidden settings... Do we want this to be documented? | |||||
| 2023-02-02 | global-functions: $WaitForFile: use delay instead of iterations | Christian Hesse | 1 | -1/+1 | |
| 2023-02-02 | telegram-chat: reply with a hint when untrusted... | Christian Hesse | 1 | -1/+6 | |
| ... but only when activating via identity. | |||||
| 2023-02-02 | telegram-chat: always reply to origin chat | Christian Hesse | 1 | -2/+3 | |
| 2023-02-01 | telegram-chat: modify text if no output available | Christian Hesse | 1 | -1/+2 | |
| 2023-02-01 | telegram-chat: also give a hint on failed syntax validation | Christian Hesse | 1 | -1/+3 | |
| ... and drop the warning in log instead. | |||||
| 2023-02-01 | telegram-chat: ... and give a hint on failure | Christian Hesse | 1 | -1/+4 | |
| 2023-02-01 | telegram-chat: handle error in command... | Christian Hesse | 1 | -1/+2 | |
| 2023-02-01 | telegram-chat: give a hint if command is still running | Christian Hesse | 1 | -2/+3 | |
| 2023-01-31 | introduce telegram-chatchange-90 | Christian Hesse | 1 | -0/+120 | |
| Druvis from Mikrotik produced a video "MikroTik Telegram bot - Chat with your Router?". He shows his script to chat with a Router via Telegram bot to send it commands: https://youtu.be/KLX6j3sLRIE This script is kind of limited and has several issues... 🥴 Let's make it robust, usable, multi-device capable and just fun! 😁 (Sadly Mikrotik has a policy to not allow links in Youtube comments. Thus my comment with several hints was removed immediately. If anybody is in contact with Druvis... Please tell him about this script!) | |||||
| index : routeros-scripts | ||
| RouterOS Scripts | git daemon user |
| aboutsummaryrefslogtreecommitdiffstats |
path: root/telegram-chat