jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2017-09-26 07:14:23 UTC

Browse source
This commit is contained in:
Travis CI 2017-09-26 07:14:23 +00:00
parent 80847eb95a
commit b723b0750d
415 changed files with 2329 additions and 1581 deletions
Download patch file Download diff file Expand all files Collapse all files

4
components/telegram_bot.webhooks/index.html
View file

@ -93,7 +93,7 @@
</div>
<p>Configuration variables:</p>
<ul>
<li><strong>allowed_chat_ids</strong> (<em>Required</em>): A list of ids representing the users and group chats that are authorised to interact with the webhook.</li>
<li><strong>allowed_chat_ids</strong> (<em>Required</em>): A list of ids representing the users and group chats that are authorized to interact with the webhook.</li>
<li><strong>api_key</strong> (<em>Required</em>): The API token of your bot.</li>
<li><strong>trusted_networks</strong> (<em>Optional</em>): Telegram server access ACL as list. Defaults to <code class="highlighter-rouge">149.154.167.197-233</code>.</li>
<li><strong>parse_mode</strong> (<em>Optional</em>): Default parser for messages if not explicit in message data: ‘html’ or ‘markdown’. Default is ‘markdown’.</li>
@ -101,7 +101,7 @@
<li><strong>proxy_params</strong> (<em>Optional</em>): Proxy configuration parameters, as dict, if working behind a proxy (<code class="highlighter-rouge">username</code>, <code class="highlighter-rouge">password</code>, etc.)</li>
<li><strong>url</strong> (<em>Optional</em>): Allow to overwrite the <code class="highlighter-rouge">base_url</code> from the <a href="/components/http/"><code class="highlighter-rouge">http</code></a> component for different configurations (<code class="highlighter-rouge">https://&lt;public_url&gt;:&lt;port&gt;</code>).</li>
</ul>
<p>To get your <code class="highlighter-rouge">chat_id</code> and <code class="highlighter-rouge">api_key</code> follow the instructions <a href="/components/notify.telegram">here</a>. As well as authorising the chat, if you have added your bot to a group you will also need to authorise any user that will be interacting with the webhook. When an unauthorised user tries to interact with the webhook Home Assistant will raise an error (“Incoming message is not allowed”), you can easily obtain the the users id by looking in the “from” section of this error message.</p>
<p>To get your <code class="highlighter-rouge">chat_id</code> and <code class="highlighter-rouge">api_key</code> follow the instructions <a href="/components/notify.telegram">here</a>. As well as authorizing the chat, if you have added your bot to a group you will also need to authorize any user that will be interacting with the webhook. When an unauthorized user tries to interact with the webhook Home Assistant will raise an error (“Incoming message is not allowed”), you can easily obtain the the users id by looking in the “from” section of this error message.</p>
<p>Full configuration sample:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
<span class="s">http</span><span class="pi">:</span>