diff --git a/CHANGED b/CHANGED
index 0bab14a8d..5a93d436d 100644
--- a/CHANGED
+++ b/CHANGED
@@ -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
diff --git a/FHEM/49_SSCam.pm b/FHEM/49_SSCam.pm
index 7bad96ead..660579d96 100644
--- a/FHEM/49_SSCam.pm
+++ b/FHEM/49_SSCam.pm
@@ -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
-
snapTelegramTxt tbot => <TelegramBot device>, peers => [<peer1 peer2 ...>], subject => [<subject text>]
+ recTelegramTxt tbot => <TelegramBot device>, peers => [<peer1 peer2 ...>], subject => [<subject text>]
Activates the permanent shipping of recordings by TelegramBot after their creation.
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 TelegramBot device
must be available and has to be running well.
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.
- You can use the following placeholders in "subject".
+ If "peer" is empty, the default peer of the TelegramBot device is used.
+
+ You can use the following placeholders within "subject".
@@ -10711,14 +10713,14 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
-
- Examples:
- recTelegramTxt tbot => teleBot, peers => , subject => Motion alarm ($FILE)
- recTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject =>
- recTelegramTxt tbot => teleBot, peers => , subject =>
- recTelegramTxt tbot => teleBot, peers => , subject => Motion alarm from $CAM. At $CTIME the recording $FILE was created. Now it is $TIME.
-
-
+ Examples:
+ attr <device> recTelegramTxt tbot => teleBot, peers => , subject => Motion alarm ($FILE)
+ attr <device> recTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject =>
+ attr <device> recTelegramTxt tbot => teleBot, peers => #nabugroup, subject =>
+ attr <device> recTelegramTxt tbot => teleBot, peers => -123456, subject =>
+ attr <device> recTelegramTxt tbot => teleBot, peers => , subject =>
+ attr <device> recTelegramTxt tbot => teleBot, peers => , subject => Motion alarm from $CAM. At $CTIME the recording $FILE was created. Now it is $TIME.
+
@@ -10822,8 +10824,9 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
which is used for shipping the data. Of course, the TelegramBot device
must be available and has to be running well.
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.
- You can use the following placeholders in "subject".
+ If "peer" is empty, the default peer of the TelegramBot device is used.
+
+ You can use the following placeholders within "subject".
@@ -10836,15 +10839,15 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
-
-
- Examples:
- snapTelegramTxt tbot => teleBot, peers => , subject => Motion alarm ($FILE)
- snapTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject =>
- snapTelegramTxt tbot => teleBot, peers => , subject =>
- snapTelegramTxt tbot => teleBot, peers => , subject => Motion alarm from $CAM. At $CTIME the snapshot $FILE was created
-
-
+
+ Examples:
+ attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => Motion alarm ($FILE)
+ attr <device> snapTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject =>
+ attr <device> snapTelegramTxt tbot => teleBot, peers => #nabugroup, subject =>
+ attr <device> snapTelegramTxt tbot => teleBot, peers => -123456, subject =>
+ attr <device> snapTelegramTxt tbot => teleBot, peers => , subject =>
+ attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => Motion alarm from $CAM. At $CTIME the snapshot $FILE was created
+
@@ -12511,7 +12514,8 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
anzugeben, welches für den Versand der Daten verwendet werden soll.
Das TelegramBot-Device muss natürlich vorhanden und funktionstüchtig sein.
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.
+ Wurde "peer" leer gelassen, wird der Default-Peer des TelegramBot-Device verwendet.
+
Es können die folgenden Platzhalter im subject verwendet werden.
@@ -12526,13 +12530,13 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
-
- Beispiele:
- recTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm ($FILE)
- recTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject =>
- recTelegramTxt tbot => teleBot, peers => , subject =>
- recTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm bei $CAM. Es wurde $CTIME die Aufnahme $FILE erstellt. Jetzt ist es $TIME.
-
+ Beispiele:
+ attr <device> recTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm ($FILE)
+ attr <device> recTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject =>
+ attr <device> recTelegramTxt tbot => teleBot, peers => #nabugroup, subject =>
+ attr <device> recTelegramTxt tbot => teleBot, peers => -123456, subject =>
+ attr <device> recTelegramTxt tbot => teleBot, peers => , subject =>
+ attr <device> recTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm bei $CAM. Es wurde $CTIME die Aufnahme $FILE erstellt. Jetzt ist es $TIME.
@@ -12640,8 +12644,9 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
anzugeben, welches für den Versand der Daten verwendet werden soll.
Das TelegramBot-Device muss natürlich vorhanden und funktionstüchtig sein.
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.
- Es können die Platzhalter im subject verwendet werden.
+ Wurde "peer" leer gelassen, wird der Default-Peer des TelegramBot-Devices verwendet.
+
+ Es können folgende Platzhalter im subject verwendet werden.
@@ -12655,14 +12660,14 @@ attr <name> genericStrmHtmlTag <img $HTMLATTR
-
- Beispiele:
- snapTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm ($FILE)
- snapTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject =>
- snapTelegramTxt tbot => teleBot, peers => , subject =>
- snapTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm bei $CAM. Es wurde $CTIME der Schnappschuss $FILE erstellt
-
-
+ Beispiele:
+ attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm ($FILE)
+ attr <device> snapTelegramTxt tbot => teleBot, peers => @nabuko @foo @bar, subject =>
+ attr <device> snapTelegramTxt tbot => teleBot, peers => #nabugroup, subject =>
+ attr <device> snapTelegramTxt tbot => teleBot, peers => -123456, subject =>
+ attr <device> snapTelegramTxt tbot => teleBot, peers => , subject =>
+ attr <device> snapTelegramTxt tbot => teleBot, peers => , subject => Bewegungsalarm bei $CAM. Es wurde $CTIME der Schnappschuss $FILE erstellt
+