To enable Telegram notifications in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry for the Telegram Bot
telegram_bot:
- platform: webhooks
+ platform: polling
api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
allowed_chat_ids:
- CHAT_ID_1
diff --git a/components/telegram_bot/index.html b/components/telegram_bot/index.html
index 4b42c06d3b..cbb915ce54 100644
--- a/components/telegram_bot/index.html
+++ b/components/telegram_bot/index.html
@@ -67,7 +67,7 @@
Use Telegram on your mobile or desktop device to send and receive messages or commands to/from your Home Assistant.
-This component creates notification services to send, or edit previously sent, messages from a Telegram Bot account configured either with the polling method or with the webhooks one, and trigger events when receiving messages.
+This component creates notification services to send, or edit previously sent, messages from a Telegram Bot account configured either with the polling method or with the webhooks one, and trigger events when receiving messages.
Notification services
Available services: send_message, send_photo, send_document, send_location, edit_message, edit_replymarkup, edit_caption, answer_callback_query.
Service telegram_bot/send_message
@@ -430,7 +430,7 @@
Telegram notification platform
-The Telegram notification platform requires the telegram_bot component to work with, and it’s designed to generate a customised shortcut (notify.USERNAME) to send notifications (messages, photos, documents and locations) to a particular chat_id with the old syntax, allowing backward compatibility.
+The Telegram notification platform requires the telegram_bot component to work with, and it’s designed to generate a customised shortcut (notify.USERNAME) to send notifications (messages, photos, documents and locations) to a particular chat_id with the old syntax, allowing backward compatibility.
The required yaml configuration now reduces to:
notify:
- name: NOTIFIER_NAME
@@ -446,6 +446,7 @@
from_first: "<first name of the sender>"
from_last: "<last name of the sender>"
user_id: "<id of the sender>"
+chat_id: "<origin chat id>"
Any other message not starting with / will be processed as simple text, firing a telegram_text event on the event bus with the following event_data:
@@ -453,6 +454,7 @@
from_first: "<first name of the sender>"
from_last: "<last name of the sender>"
user_id: "<id of the sender>"
+chat_id: "<origin chat id>"
if the message is sent from a press from an inline button, for example, a callback query is received, and Home Assistant will fire a telegram_callback event with:
For a more complex usage of the telegram_bot capabilities, using AppDaemon is advised.
For a more complex usage of the telegram_bot capabilities, using AppDaemon is advised.
This is how the previous 4 automations would be through a simple AppDaemon app:
import appdaemon.appapi as appapi
diff --git a/index.html b/index.html
index 08ab0dacac..c56606f51e 100644
--- a/index.html
+++ b/index.html
@@ -86,8 +86,8 @@ Home Assistant is an open-source home automation platform running on Python 3. T
- Current Version: 0.45.0
- Released: May 20, 2017
+ Current Version: 0.45.1
+ Released: May 22, 2017
diff --git a/sitemap.xml b/sitemap.xml
index 85a7ff1dff..1f19402592 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -3457,62 +3457,62 @@
https://home-assistant.io/demo/frontend.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/index.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
https://home-assistant.io/static/mdi-demo.html
-2017-05-23T15:37:18+00:00
+2017-05-23T16:26:03+00:00
diff --git a/version.json b/version.json
index 016b9da870..cc7d6349ec 100644
--- a/version.json
+++ b/version.json
@@ -1,6 +1,6 @@
{
- "current_version": "0.45.0",
- "release_date": "2017-05-20T00:00:00+00:00",
+ "current_version": "0.45.1",
+ "release_date": "2017-05-22T00:00:00+00:00",
"release_notes": "https://home-assistant.io/blog/2017/05/20/automation-editor-zwave-panel-ocr/",
"release_notes_path": "/blog/2017/05/20/automation-editor-zwave-panel-ocr/",
"release_title": "Home Assistant 0.45: Automation editor, Z-Wave panel, OCR",
@@ -10,6 +10,6 @@
"semantic_version": {
"major": 0,
"minor": 45,
- "patch": 0
+ "patch": 1
}
}