diff --git a/_addons_bindings/mqtt.homeassistant/readme.md b/_addons_bindings/mqtt.homeassistant/readme.md index 36b579a59..c666efb7f 100644 --- a/_addons_bindings/mqtt.homeassistant/readme.md +++ b/_addons_bindings/mqtt.homeassistant/readme.md @@ -28,5 +28,5 @@ The mapping is structured like this: * The HomeAssistant Fan Components only support ON/OFF. * The HomeAssistant Cover Components only support OPEN/CLOSE/STOP. -* The HomeAssistant Light Component does not support XY color changes. +* The HomeAssistant Light Component only supports RGB color changes. * The HomeAssistant Climate Components is not yet supported. diff --git a/_addons_bindings/telegram/readme.md b/_addons_bindings/telegram/readme.md index c94941d7d..e4b1c6713 100644 --- a/_addons_bindings/telegram/readme.md +++ b/_addons_bindings/telegram/readme.md @@ -30,10 +30,15 @@ As described in the Telegram Bot API, this is the manual procedure needed in ord - Open a chat with your new Bot and send any message to it. The next step will not work unless you send a message to your bot first. -3. Get the chatId +3. Get the chatID - Open a browser and invoke `https://api.telegram.org/bot/getUpdates` (where `` is the authentication token previously obtained) -- Look at the JSON result to find the value of `id`. That is 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 file. (e.g. bot1.chatId: -22334455) +- 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`). +If this does not work for you (the JSON response may be empty), or you want to send to *more* than one recipient (= another chatID), the alternative is to contact (= open a chat with) a Telegram bot to respond with the chatID. +There's a number of them such as `@myidbot` or `@chatid_echo_bot` - open a chat, eventually tap `/start` and it will return the chatID you're looking for. +Another option is `@getidsbot` which gives you much more information. +Note bots may work or not at any time so eventually you need to try another one. 4. Test the bot diff --git a/_addons_transformations/regex/readme.md b/_addons_transformations/regex/readme.md index fcdb80b39..3d72d40d1 100644 --- a/_addons_transformations/regex/readme.md +++ b/_addons_transformations/regex/readme.md @@ -117,3 +117,4 @@ Please note: This profile is a one-way transformation, i.e. only values from a d * Online validator help to check the syntax of a regex and give information how to design it. * [Regex 101](https://regex101.com/) * [Regex R](https://regexr.com/) + * [ExtendsClass](https://extendsclass.com/regex-tester.html) diff --git a/_addons_transformations/xslt/readme.md b/_addons_transformations/xslt/readme.md index af9aec735..0babea18a 100644 --- a/_addons_transformations/xslt/readme.md +++ b/_addons_transformations/xslt/readme.md @@ -137,4 +137,4 @@ Please note: This profile is a one-way transformation, i.e. only values from a d * Extended introduction and more [examples](https://en.wikipedia.org/wiki/XSLT#XSLT_examples) at Wikipedia. * A good [introduction](https://www.w3schools.com/xml/xsl_intro.asp) and [tutorial](https://www.w3schools.com/xml/xsl_transformation.asp) at W3School. * An informative [tutorial](https://www.ibm.com/developerworks/library/x-xsltmistakes/) of common mistakes. - +* Online XSL transformer tools like [this](https://www.freeformatter.com/xsl-transformer.html) to check the syntax.