aboutsummaryrefslogtreecommitdiffstats
path: root/telegram-chat
AgeCommit message (Collapse)AuthorFilesLines
2023-02-26telegram-chat: ignore new messages after rebootGravatar Christian Hesse1-1/+2
This script supports multiple devices, and sending offset to discard messages is delayed to third fetch to make sure all devices get the message. This can cause trouble, though: Sending a device a reboot command can make that device reboot multiple times 🥴 or - even worse - make it enter an infinite boot loop 😳 if it is the only device. So let's ignore first messages after reboot.
2023-02-26telegram-chat: send messages in replyGravatar Christian Hesse1-3/+4
2023-02-14telegram-chat: log command with failed syntax validationGravatar Christian Hesse1-0/+1
2023-02-14telegram-chat: never decrease the local offsetGravatar Christian Hesse1-1/+1
2023-02-14telegram-chat: add debug message for handled updatesGravatar Christian Hesse1-0/+2
2023-02-14telegram-chat: add updateid in log messagesGravatar Christian Hesse1-3/+4
2023-02-07telegram-chat: use complete property nameGravatar Christian Hesse1-1/+1
2023-02-04telegram-chat: handle exceeded file read sizeGravatar Christian Hesse1-1/+2
2023-02-03telegram-chat: no need to :put ...Gravatar Christian Hesse1-2/+2
... a simple change to root dir is sufficient.
2023-02-03telegram-chat: log with severity debug only...Gravatar Christian Hesse1-1/+1
... as failed request are quite common.
2023-02-03telegram-chat: delay confirmation of updatesGravatar Christian Hesse1-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-03telegram-chat: log warning only when trying to activateGravatar Christian Hesse1-2/+5
2023-02-03telegram-chat: handle missing usernameGravatar Christian Hesse1-1/+3
2023-02-02telegram-chat: discard messages without textGravatar Christian Hesse1-1/+1
2023-02-02telegram-chat: allow to modify the time to wait for commandGravatar Christian Hesse1-1/+3
For now this is a hidden settings... Do we want this to be documented?
2023-02-02global-functions: $WaitForFile: use delay instead of iterationsGravatar Christian Hesse1-1/+1
2023-02-02telegram-chat: reply with a hint when untrusted...Gravatar Christian Hesse1-1/+6
... but only when activating via identity.
2023-02-02telegram-chat: always reply to origin chatGravatar Christian Hesse1-2/+3
2023-02-01telegram-chat: modify text if no output availableGravatar Christian Hesse1-1/+2
2023-02-01telegram-chat: also give a hint on failed syntax validationGravatar Christian Hesse1-1/+3
... and drop the warning in log instead.
2023-02-01telegram-chat: ... and give a hint on failureGravatar Christian Hesse1-1/+4
2023-02-01telegram-chat: handle error in command...Gravatar Christian Hesse1-1/+2
2023-02-01telegram-chat: give a hint if command is still runningGravatar Christian Hesse1-2/+3
2023-01-31introduce telegram-chatchange-90Gravatar Christian Hesse1-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!)