mirror of
https://github.com/fhem/fhem-mirror.git
synced 2025-03-10 03:06:37 +00:00
49_SSCam: commandref revised
git-svn-id: https://svn.fhem.de/fhem/trunk@19996 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
nasseeder1
parent
19a18429c7
commit
9979c25f98
@ -1,5 +1,6 @@
|
||||
# Add changes at the top of the list. Keep it in ASCII, and 80-char wide.
|
||||
# Do not insert empty lines here, update check depends on it.
|
||||
- change: 49_SSCam: commandref revised
|
||||
- bugfix: 73_AutoShuttersControl: fix UTF8 Problem und Initialisierungfehler,
|
||||
fix brightness morning and evening drive, add more condition
|
||||
for roommate and shading
|
||||
|
||||
@ -48,6 +48,7 @@ eval "use FHEM::Meta;1" or my $modMetaAbsent = 1;
|
||||
|
||||
# Versions History intern
|
||||
our %SSCam_vNotesIntern = (
|
||||
"8.16.3" => "13.08.2019 commandref revised ",
|
||||
"8.16.2" => "17.07.2019 change function SSCam_ptzpanel using css stylesheet ",
|
||||
"8.16.1" => "16.07.2019 fix warnings ",
|
||||
"8.16.0" => "14.07.2019 change detail link generation from SSCamSTRM to SSCam ",
|
||||
@ -10690,14 +10691,15 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
|
||||
</li>
|
||||
|
||||
<a name="recTelegramTxt"></a>
|
||||
<li><b>snapTelegramTxt tbot => <TelegramBot device>, peers => [<peer1 peer2 ...>], subject => [<subject text>] </b><br>
|
||||
<li><b>recTelegramTxt tbot => <TelegramBot device>, peers => [<peer1 peer2 ...>], subject => [<subject text>] </b><br>
|
||||
Activates the permanent shipping of recordings by TelegramBot after their creation. <br>
|
||||
The attribute has to be definied in the form as described. With key "tbot" the TelegramBot device is specified,
|
||||
which is used for shipping the data. Of course, the <a href="http://fhem.de/commandref.html#TelegramBot">TelegramBot device</a>
|
||||
must be available and has to be running well. <br>
|
||||
The setting of "peers" and "subject" is optional, but the keys must (empty) specified.
|
||||
If "peer" is empty, teh default peer of the TelegramBot is used. <br>
|
||||
You can use the following placeholders in "subject". <br><br>
|
||||
If "peer" is empty, the default peer of the TelegramBot device is used. <br><br>
|
||||
|
||||
You can use the following placeholders within "subject". <br><br>
|
||||
|
||||
<ul>
|
||||
<table>
|
||||
@ -10711,13 +10713,13 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
|
||||
</ul>
|
||||
<br>
|
||||
|
||||
<ul>
|
||||
<b>Examples:</b><br>
|
||||
recTelegramTxt tbot => teleBot, peers => , subject => Motion alarm ($FILE) <br>
|
||||
recTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject => <br>
|
||||
recTelegramTxt tbot => teleBot, peers => , subject => <br>
|
||||
recTelegramTxt tbot => teleBot, peers => , subject => Motion alarm from $CAM. At $CTIME the recording $FILE was created. Now it is $TIME. <br>
|
||||
</ul>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => , subject => Motion alarm ($FILE) <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject => <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => #nabugroup, subject => <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => -123456, subject => <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => , subject => <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => , subject => Motion alarm from $CAM. At $CTIME the recording $FILE was created. Now it is $TIME. <br>
|
||||
<br>
|
||||
</li><br>
|
||||
|
||||
@ -10822,8 +10824,9 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
|
||||
which is used for shipping the data. Of course, the <a href="http://fhem.de/commandref.html#TelegramBot">TelegramBot device</a>
|
||||
must be available and has to be running well. <br>
|
||||
The setting of "peers" and "subject" is optional, but the keys must (empty) specified.
|
||||
If "peer" is empty, teh default peer of the TelegramBot is used. <br>
|
||||
You can use the following placeholders in "subject". <br><br>
|
||||
If "peer" is empty, the default peer of the TelegramBot device is used. <br><br>
|
||||
|
||||
You can use the following placeholders within "subject". <br><br>
|
||||
|
||||
<ul>
|
||||
<table>
|
||||
@ -10837,13 +10840,13 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
|
||||
</ul>
|
||||
<br>
|
||||
|
||||
<ul>
|
||||
<b>Examples:</b><br>
|
||||
snapTelegramTxt tbot => teleBot, peers => , subject => Motion alarm ($FILE) <br>
|
||||
snapTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject => <br>
|
||||
snapTelegramTxt tbot => teleBot, peers => , subject => <br>
|
||||
snapTelegramTxt tbot => teleBot, peers => , subject => Motion alarm from $CAM. At $CTIME the snapshot $FILE was created <br>
|
||||
</ul>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => Motion alarm ($FILE) <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject => <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => #nabugroup, subject => <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => -123456, subject => <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => Motion alarm from $CAM. At $CTIME the snapshot $FILE was created <br>
|
||||
<br>
|
||||
</li><br>
|
||||
|
||||
@ -12511,7 +12514,8 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
|
||||
anzugeben, welches für den Versand der Daten verwendet werden soll.
|
||||
Das <a href="http://fhem.de/commandref_DE.html#TelegramBot">TelegramBot-Device</a> muss natürlich vorhanden und funktionstüchtig sein. <br>
|
||||
Die Angabe von "peers" und "subject" ist optional, jedoch muß der Schlüssel (leer) angegeben werden.
|
||||
Wurde "peer" leer gelassen, wird der Default-Peer des TelegramBot verwendet. <br>
|
||||
Wurde "peer" leer gelassen, wird der Default-Peer des TelegramBot-Device verwendet. <br><br>
|
||||
|
||||
Es können die folgenden Platzhalter im subject verwendet werden. <br><br>
|
||||
|
||||
<ul>
|
||||
@ -12526,13 +12530,13 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
|
||||
</ul>
|
||||
<br>
|
||||
|
||||
<ul>
|
||||
<b>Beispiele:</b><br>
|
||||
recTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm ($FILE) <br>
|
||||
recTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject => <br>
|
||||
recTelegramTxt tbot => teleBot, peers => , subject => <br>
|
||||
recTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm bei $CAM. Es wurde $CTIME die Aufnahme $FILE erstellt. Jetzt ist es $TIME. <br>
|
||||
</ul>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm ($FILE) <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject => <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => #nabugroup, subject => <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => -123456, subject => <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => , subject => <br>
|
||||
attr <device> recTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm bei $CAM. Es wurde $CTIME die Aufnahme $FILE erstellt. Jetzt ist es $TIME. <br>
|
||||
<br>
|
||||
</li><br>
|
||||
|
||||
@ -12640,8 +12644,9 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
|
||||
anzugeben, welches für den Versand der Daten verwendet werden soll.
|
||||
Das <a href="http://fhem.de/commandref_DE.html#TelegramBot">TelegramBot-Device</a> muss natürlich vorhanden und funktionstüchtig sein. <br>
|
||||
Die Angabe von "peers" und "subject" ist optional, jedoch muß der Schlüssel (leer) angegeben werden.
|
||||
Wurde "peer" leer gelassen, wird der Default-Peer des TelegramBot verwendet. <br>
|
||||
Es können die Platzhalter im subject verwendet werden. <br><br>
|
||||
Wurde "peer" leer gelassen, wird der Default-Peer des TelegramBot-Devices verwendet. <br><br>
|
||||
|
||||
Es können folgende Platzhalter im subject verwendet werden. <br><br>
|
||||
|
||||
<ul>
|
||||
<table>
|
||||
@ -12655,13 +12660,13 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
|
||||
</ul>
|
||||
<br>
|
||||
|
||||
<ul>
|
||||
<b>Beispiele:</b><br>
|
||||
snapTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm ($FILE) <br>
|
||||
snapTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject => <br>
|
||||
snapTelegramTxt tbot => teleBot, peers => , subject => <br>
|
||||
snapTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm bei $CAM. Es wurde $CTIME der Schnappschuss $FILE erstellt <br>
|
||||
</ul>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm ($FILE) <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject => <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => #nabugroup, subject => <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => -123456, subject => <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => <br>
|
||||
attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm bei $CAM. Es wurde $CTIME der Schnappschuss $FILE erstellt <br>
|
||||
<br>
|
||||
</li><br>
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user