The clicksendaudio platform uses ClickSend to deliver text-to-speech (TTS) notifications from Home Assistant.
+
Go to your ClickSend Dashboard section and create your new project. After creating your project, you should now be able to obtain your username and api_key.
+
To add ClickSend to your installation, add the following to your Home Assistant configuration.yaml file:
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is ClickSend. The notifier will bind to the service notify.NOTIFIER_NAME.
+
username (Required): Your username.
+
api_key (Required): Your API Key.
+
recipient (Required): Your phone no. This is where you want to send your notification SMS messages. eg: 09171234567
+
language (Optional): The language you want to use to convert the message to audio. Accepted values are found in the ClickSend Documentation. Default value is ‘en-us’.
+
voice (Optional): The voice that needs to be used to play the message to the recipient. Allowed values are ‘female’ or ‘male’. Default value is ‘female’.
diff --git a/components/notify.facebook/index.html b/components/notify.facebook/index.html
index 7fe80124f0..b0bd8b566d 100644
--- a/components/notify.facebook/index.html
+++ b/components/notify.facebook/index.html
@@ -204,6 +204,9 @@ The phone number used in target should be registered with Faceb
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index aa54687a37..46c10293f6 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -131,6 +131,9 @@ If you disable and re-enable the SMS API option, please be sure to update your t
diff --git a/components/notify.lametric/index.html b/components/notify.lametric/index.html
index 7a78c32a25..b9e588730d 100644
--- a/components/notify.lametric/index.html
+++ b/components/notify.lametric/index.html
@@ -130,6 +130,9 @@ Note that icons always begin with “i” while animations begin with “a”. T
diff --git a/components/notify.nfandroidtv/index.html b/components/notify.nfandroidtv/index.html
index ccdde63204..3be702c06b 100644
--- a/components/notify.nfandroidtv/index.html
+++ b/components/notify.nfandroidtv/index.html
@@ -147,6 +147,9 @@ This is a fully customized JSON you can use to test how the final notification w
diff --git a/components/notify.smtp/index.html b/components/notify.smtp/index.html
index b5f99587fc..634f78a32d 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -240,6 +240,9 @@ which need special attention. By default, the usage by external applications, es
purge_days (Optional): Delete events and states older than x days. The purge task runs every 2 days, starting from when Home Assistant is started if you restart your instance more frequently than the purge will never take place.
+
purge_interval (Optional): (days) Enable scheduled purge of older events and states. The purge task runs every x days, starting from when Home Assistant is started. If you restart your instance more frequently, than the purge will never take place. You can use service call recorder.purge when needed.
+
purge_keep_days (Required with purge_interval): Specify number of history days to keep in recorder database after purge.
exclude (Optional): Configure which components should be excluded from recordings.
entities (Optional): The list of entity ids to be excluded from recordings.
@@ -102,7 +103,8 @@
Define domains and entities to exclude (aka. blacklist). This is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains. Usually these are entities/domains which do not change (like weblink) or rarely change (updater or automation).
# Example configuration.yaml entry with excluderecorder:
- purge_days:5
+ purge_interval:2
+ purge_keep_days:5db_url:sqlite:///home/user/.homeassistant/testexclude:domains:
@@ -140,6 +142,15 @@
If you only want to hide events from e.g. your history, take a look at the history component. Same goes for logbook. But if you have privacy concerns about certain events or neither want them in history or logbook, you should use the exclude/include options of the recorder component, that they aren’t even in your database. That way you can save storage and keep the database small by excluding certain often-logged events (like sensor.last_boot).
+
Service purge
+
Call the service recorder.purge to start purge task, which deletes events and states older than x days, according to keep_days service data (Required)
+