From 930431d92e17ba9ae340b146bbf1acad192f8177 Mon Sep 17 00:00:00 2001 From: Wikibear Date: Tue, 6 Jul 2021 19:45:36 +0200 Subject: [PATCH] [telegram] Update README.md (#10948) Add design of token for better understanding --- bundles/org.openhab.binding.telegram/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/bundles/org.openhab.binding.telegram/README.md b/bundles/org.openhab.binding.telegram/README.md index 44b573881cee..51f7c87d2d7e 100644 --- a/bundles/org.openhab.binding.telegram/README.md +++ b/bundles/org.openhab.binding.telegram/README.md @@ -10,6 +10,7 @@ As described in the Telegram Bot API (https://core.telegram.org/bots#6-botfather - On a Telegram client open a chat with BotFather. - Send `/newbot` to BotFather and fill in all the needed information. The authentication token that is given will be needed in the next steps. +- The token is a combination with double point separated parts of numbers and letters e.g.: 158642643:ABCHL_O-MUovQ1NzrDF5R_nqLbFhPPrg9Jps 2. Create the destination chat @@ -17,7 +18,7 @@ As described in the Telegram Bot API (https://core.telegram.org/bots#6-botfather 3. Get the chatID -- Open a browser and invoke `https://api.telegram.org/bot/getUpdates` (where `` is the authentication token previously obtained) +- Open a browser and invoke `https://api.telegram.org/bot/getUpdates` (where `` is the authentication token previously obtained e.g.: `https://api.telegram.org/bot158642643:ABCHL_O-MUovQ1NzrDF5R_nqLbFhPPrg9Jps/getUpdates`) - Look at the JSON result to find the value of `id`: that's the chatID. Note that if using a Telegram group chat, the group chatIDs are prefixed with a dash that must be included in the config (e.g. `-22334455`).