Site updated at 2017-08-12 20:12:45 UTC
This commit is contained in:
parent
e1336d0fd2
commit
177731b69b
614 changed files with 10280 additions and 2298 deletions
|
@ -97,6 +97,8 @@
|
|||
<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>
|
||||
<li><strong>proxy_url</strong> (<em>Optional</em>): Proxy url if working behind one (<code class="highlighter-rouge">socks5://proxy_ip:proxy_port</code>)</li>
|
||||
<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 http component for diferent configs.</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>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue