Site updated at 2017-07-02 00:58:35 UTC
This commit is contained in:
parent
af9e56ffa0
commit
00a0f63427
651 changed files with 11395 additions and 2155 deletions
|
@ -76,6 +76,7 @@
|
|||
<hr class="divider">
|
||||
<p>Use Telegram on your mobile or desktop device to send and receive messages or commands to/from your Home Assistant.</p>
|
||||
<p>This component creates notification services to send, or edit previously sent, messages from a <a href="https://core.telegram.org/bots">Telegram Bot account</a> configured either with the <a href="/components/telegram_bot.polling/">polling</a> method or with the <a href="/components/telegram_bot.webhooks/">webhooks</a> one, and trigger events when receiving messages.</p>
|
||||
<p>If you don’t need to receive messages, you can use the <a href="/components/telegram_bot.broadcast/">broadcast</a> platform instead.</p>
|
||||
<h3><a class="title-link" name="notification-services" href="#notification-services"></a> Notification services</h3>
|
||||
<p>Available services: <code class="highlighter-rouge">send_message</code>, <code class="highlighter-rouge">send_photo</code>, <code class="highlighter-rouge">send_document</code>, <code class="highlighter-rouge">send_location</code>, <code class="highlighter-rouge">edit_message</code>, <code class="highlighter-rouge">edit_replymarkup</code>, <code class="highlighter-rouge">edit_caption</code>, <code class="highlighter-rouge">answer_callback_query</code>.</p>
|
||||
<h4><a class="title-link" name="service-telegram_botsend_message" href="#service-telegram_botsend_message"></a> Service <code class="highlighter-rouge">telegram_bot/send_message</code></h4>
|
||||
|
@ -314,7 +315,7 @@
|
|||
<tr>
|
||||
<td><code class="highlighter-rouge">message_id</code></td>
|
||||
<td>no</td>
|
||||
<td>Id of the message to edit. When answering a callback from a pressed button, the id of the origin message is in: ``.</td>
|
||||
<td>Id of the message to edit. When answering a callback from a pressed button, the id of the origin message is in: ``. You can use <code class="highlighter-rouge">"last"</code> to refer to the last message sent to <code class="highlighter-rouge">chat_id</code>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code class="highlighter-rouge">chat_id</code></td>
|
||||
|
@ -362,7 +363,7 @@
|
|||
<tr>
|
||||
<td><code class="highlighter-rouge">message_id</code></td>
|
||||
<td>no</td>
|
||||
<td>Id of the message to edit. When answering a callback from a pressed button, the id of the origin message is in: ``.</td>
|
||||
<td>Id of the message to edit. When answering a callback from a pressed button, the id of the origin message is in: ``. You can use <code class="highlighter-rouge">"last"</code> to refer to the last message sent to <code class="highlighter-rouge">chat_id</code>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code class="highlighter-rouge">chat_id</code></td>
|
||||
|
@ -400,7 +401,7 @@
|
|||
<tr>
|
||||
<td><code class="highlighter-rouge">message_id</code></td>
|
||||
<td>no</td>
|
||||
<td>Id of the message to edit. When answering a callback from a pressed button, the id of the origin message is in: ``.</td>
|
||||
<td>Id of the message to edit. When answering a callback from a pressed button, the id of the origin message is in: ``. You can use <code class="highlighter-rouge">"last"</code> to refer to the last message sent to <code class="highlighter-rouge">chat_id</code>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code class="highlighter-rouge">chat_id</code></td>
|
||||
|
@ -447,6 +448,29 @@
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h4><a class="title-link" name="service-telegram_botdelete_message" href="#service-telegram_botdelete_message"></a> Service <code class="highlighter-rouge">telegram_bot/delete_message</code></h4>
|
||||
<p>Delete a previusly sent message in a conversation.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Service data attribute</th>
|
||||
<th>Optional</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code class="highlighter-rouge">message_id</code></td>
|
||||
<td>no</td>
|
||||
<td>Id of the message to delete. When answering a callback from a pressed button, the id of the origin message is in: ``. You can use <code class="highlighter-rouge">"last"</code> to refer to the last message sent to <code class="highlighter-rouge">chat_id</code>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code class="highlighter-rouge">chat_id</code></td>
|
||||
<td>no</td>
|
||||
<td>The chat_id where to delete the message.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3><a class="title-link" name="telegram-notification-platform" href="#telegram-notification-platform"></a> <code class="highlighter-rouge">Telegram</code> notification platform</h3>
|
||||
<p>The <a href="/components/notify.telegram/">Telegram notification platform</a> requires the <code class="highlighter-rouge">telegram_bot</code> component to work with, and it’s designed to generate a customised shortcut (<code class="highlighter-rouge">notify.USERNAME</code>) to send notifications (messages, photos, documents and locations) to a particular <code class="highlighter-rouge">chat_id</code> with the old syntax, allowing backward compatibility.</p>
|
||||
<p>The required yaml configuration now reduces to:</p>
|
||||
|
@ -732,6 +756,9 @@
|
|||
</div>
|
||||
<h1 class='title delta'>Platforms</h1>
|
||||
<ul class='divided'>
|
||||
<li><a href='/components/telegram_bot.broadcast/'>
|
||||
Telegram broadcast
|
||||
</a></li>
|
||||
<li><a href='/components/telegram_bot.polling/'>
|
||||
Telegram polling
|
||||
</a></li>
|
||||
|
@ -904,6 +931,9 @@
|
|||
<li>
|
||||
<a href='/components/zwave/'>Z-Wave</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/comfoconnect/'>Zehnder ComfoAir Q Ventilation</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/zha/'>Zigbee Home Automation</a>
|
||||
</li>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue