beim Auslösen erhalte ich mehrfache Benachrichtigung

Begonnen von achim60, 02 Dezember 2017, 07:55:52

Vorheriges Thema - Nächstes Thema

achim60

Morgen,
sobald etwas ausgelöst wir erhalte ich eine Mail mit dem Betreff des Auslösers. In diesem Fall Bewegung-Garage bzw.Tor und Bewegung-Hausflur, was auch immer klappte.
Seit neuestem erhalte ich diese 3-5 fach  nach dem Auslösen ???

Das mit der -m option störte mich nie, da die Mail ja immer ankommt. Oder ist das der Verursacher ?

Log:

2017.12.01 17:17:06 1: sendEmail RCP: <xyz@xyz.de>
2017.12.01 17:17:06 1: sendEmail Subject: Bewegung-Garage bzw.Tor
2017.12.01 17:17:06 1: sendEmail Text:
2017.12.01 17:17:06 1: sendEmail Anhang:
2017.12.01 17:17:08 1: sendEmail returned: Reading message body from STDIN because the '-m' option was not used.If you are manually typing in a message:  - First line must be received within 60 seconds.  - End manual input with a CTRL-D on its own line.Dec 01 17:17:07 raspberrypi sendEmail[17656]: Message input complete.Dec 01 17:17:08 raspberrypi sendEmail[17656]: Email was sent successfully!
2017.12.01 17:19:47 3: CUL_HM set Schalter_Funksteckdose_A off
2017.12.01 17:19:47 3: CUL_HM set Schalter_Funksteckdose_C off
2017.12.01 17:22:49 1: sendEmail RCP: <xyz@xyz.de>
2017.12.01 17:22:49 1: sendEmail Subject: Bewegung-Garage bzw.Tor
2017.12.01 17:22:49 1: sendEmail Text:
2017.12.01 17:22:49 1: sendEmail Anhang:
2017.12.01 17:22:50 1: sendEmail returned: Reading message body from STDIN because the '-m' option was not used.If you are manually typing in a message:  - First line must be received within 60 seconds.  - End manual input with a CTRL-D on its own line.Dec 01 17:22:49 raspberrypi sendEmail[18011]: Message input complete.Dec 01 17:22:50 raspberrypi sendEmail[18011]: Email was sent successfully!
2017.12.01 17:24:47 3: CUL_HM set Schalter_Funksteckdose_A off
2017.12.01 17:24:47 3: CUL_HM set Schalter_Funksteckdose_C off
2017.12.01 17:26:10 3: CUL_HM set Sprachausgabe playTone 012
2017.12.01 17:27:12 3: CUL_HM set Sprachausgabe playTone 012
2017.12.01 17:28:31 1: sendEmail RCP: <alarm@keil-datenklick.de>
2017.12.01 17:28:31 1: sendEmail Subject: Bewegung-Hausflur
2017.12.01 17:28:31 1: sendEmail Text:
2017.12.01 17:28:31 1: sendEmail Anhang:
2017.12.01 17:28:32 1: sendEmail returned: Reading message body from STDIN because the '-m' option was not used.If you are manually typing in a message:  - First line must be received within 60 seconds.  - End manual input with a CTRL-D on its own line.Dec 01 17:28:31 raspberrypi sendEmail[18361]: Message input complete.Dec 01 17:28:32 raspberrypi sendEmail[18361]: Email was sent successfully!
2017.12.01 17:29:47 3: CUL_HM set Schalter_Funksteckdose_A off
2017.12.01 17:29:47 3: CUL_HM set Schalter_Funksteckdose_C off
2017.12.01 17:29:50 3: CUL_HM set HM_4140E2_Dim off
2017.12.01 17:29:50 3: CUL_HM set Schalter_Funksteckdose_A off
2017.12.01 17:30:01 1: sendEmail RCP: <xyz@xyz.de>
2017.12.01 17:30:01 1: sendEmail Subject: Bewegung-Garage bzw.Tor
2017.12.01 17:30:01 1: sendEmail Text:
2017.12.01 17:30:01 1: sendEmail Anhang:
2017.12.01 17:30:02 1: sendEmail returned: Reading message body from STDIN because the '-m' option was not used.If you are manually typing in a message:  - First line must be received within 60 seconds.  - End manual input with a CTRL-D on its own line.Dec 01 17:30:01 raspberrypi sendEmail[18562]: Message input complete.Dec 01 17:30:02 raspberrypi sendEmail[18562]: Email was sent successfully!
2017.12.01 17:30:30 3: CUL_HM set HM_4140E2_Dim on
2017.12.01 17:30:30 3: CUL_HM set Schalter_Funksteckdose_A on-for-timer 3600
2017.12.01 17:30:37 3: CUL_HM set HM_4140E2_Dim off
2017.12.01 17:30:37 3: CUL_HM set Schalter_Funksteckdose_A off
2017.12.01 17:30:38 3: CUL_HM set HM_4140E2_Dim off
2017.12.01 17:30:38 3: CUL_HM set Schalter_Funksteckdose_A off
2017.12.01 17:32:13 1: sendEmail RCP: <alarm@keil-datenklick.de>
2017.12.01 17:32:13 1: sendEmail Subject: Bewegung-Hausflur
2017.12.01 17:32:13 1: sendEmail Text:
2017.12.01 17:32:13 1: sendEmail Anhang:
2017.12.01 17:32:16 1: sendEmail returned: Reading message body from STDIN because the '-m' option was not used.If you are manually typing in a message:  - First line must be received within 60 seconds.  - End manual input with a CTRL-D on its own line.Dec 01 17:32:14 raspberrypi sendEmail[18716]: Message input complete.Dec 01 17:32:16 raspberrypi sendEmail[18716]: Email was sent successfully!
2017.12.01 17:33:06 3: CUL_HM set HM_4140E2_Dim on
2017.12.01 17:33:06 3: CUL_HM set Schalter_Funksteckdose_A on-for-timer 3600
2017.12.01 17:33:06 3: CUL_HM set HM_4140E2_Dim on
2017.12.01 17:33:07 3: CUL_HM set Schalter_Funksteckdose_A on-for-timer 3600
2017.12.01 17:33:07 3: CUL_HM set HM_4140E2_Dim on
2017.12.01 17:33:07 3: CUL_HM set Schalter_Funksteckdose_A on-for-timer 3600
2017.12.01 17:33:43 1: sendEmail RCP: <xyz@xyz.de>
2017.12.01 17:33:43 1: sendEmail Subject: Bewegung-Garage bzw.Tor
2017.12.01 17:33:43 1: sendEmail Text:
2017.12.01 17:33:43 1: sendEmail Anhang:
2017.12.01 17:33:46 1: sendEmail returned: Reading message body from STDIN because the '-m' option was not used.If you are manually typing in a message:  - First line must be received within 60 seconds.  - End manual input with a CTRL-D on its own line.Dec 01 17:33:43 raspberrypi sendEmail[18754]: Message input complete.Dec 01 17:33:46 raspberrypi sendEmail[18754]: Email was sent successfully!



Internals:
   DEF        ([XYZ_Anwesend_Anwesend] eq "off" and [Bewegung_Hausflur] eq "on")  ({ DebianMail('<xyz@xyz.de>','Bewegung-Hausflur','');;})
   NAME       di_meldung_Handy_flur
   NR         174
   NTFY_ORDER 50-di_meldung_Handy_flur
   STATE      cmd_1
   TYPE       DOIF
   READINGS:
     2017-12-02 06:46:42   Device          XYZ_Anwesend
     2017-12-01 17:32:16   cmd             1
     2017-12-01 17:32:16   cmd_event       XYZ_Anwesend
     2017-12-01 17:32:16   cmd_nr          1
     2017-12-02 06:46:42   e_XYZ_Anwesend_Anwesend_STATE on
     2017-12-01 18:23:28   e_Bewegung_Hausflur_STATE off
     2017-12-01 17:32:16   state           cmd_1
     2017-11-30 19:14:41   wait_timer      no timer
   condition:
     0          InternalDoIf($hash,'XYZ_Anwesend_Anwesend','STATE') eq "off" and InternalDoIf($hash,'Bewegung_Hausflur','STATE') eq "on"
   devices:
     0           XYZ_AnwesendBewegung_Hausflur
     all         XYZ_AnwesendBewegung_Hausflur
   do:
     0:
       0          { DebianMail('<xyz@xyz.de>','Bewegung-Hausflur','');;}
     1:
   helper:
     event      on
     globalinit 1
     last_timer 0
     sleepdevice Bewegung_Hausflur
     sleepsubtimer -1
     sleeptimer -1
     timerdev   XYZ_Anwesend
     timerevent off
     triggerDev XYZ_Anwesend
     timerevents:
       off
     timereventsState:
       state: off
     triggerEvents:
       on
     triggerEventsState:
       state: on
   internals:
     0           XYZ_Anwesend_Anwesend:STATE Bewegung_Hausflur:STATE
     all         XYZ_Anwesend_Anwesend:STATE Bewegung_Hausflur:STATE
   itimer:
   readings:
   regexp:
     0:
     all:
   state:
     STATE:
   trigger:
Attributes:
   do         always
   room       Handys




Internals:
   DEF        ([XYZ_Anwesend_Anwesend] eq "off" and [alarm_sprach_aus] eq "off"  and [Bewegung_Garage] eq "on") ({ DebianMail('<xyz@xyz.de>','Bewegung-Garage bzw.Tor','');;})

   NAME       alarm_bewegung_garage_handy
   NR         155
   NTFY_ORDER 50-alarm_bewegung_garage_handy
   STATE      cmd_1
   TYPE       DOIF
   READINGS:
     2017-12-02 06:46:42   Device          XYZ_Anwesend
     2017-12-01 17:33:46   cmd             1
     2017-12-01 17:33:46   cmd_event       XYZ_Anwesend
     2017-12-01 17:33:46   cmd_nr          1
     2017-12-02 06:46:42   e_XYZ_Anwesend_Anwesend_STATE on
     2017-12-01 18:23:28   e_Bewegung_Garage_STATE off
     2017-11-18 19:47:56   e_alarm_sprach_aus_STATE off
     2017-12-01 17:33:46   state           cmd_1
     2017-12-01 17:33:43   wait_timer      no timer
   condition:
     0          InternalDoIf($hash,'XYZ_Anwesend_Anwesend','STATE') eq "off" and InternalDoIf($hash,'alarm_sprach_aus','STATE') eq "off"  and InternalDoIf($hash,'Bewegung_Garage','STATE') eq "on"
   devices:
     0           XYZ_Anwesendalarm_sprach_aus Bewegung_Garage
     all         XYZ_Anwesendalarm_sprach_aus Bewegung_Garage
   do:
     0:
       0          { DebianMail('<xyz@xyz.de>','Bewegung-Garage bzw.Tor','');;}
     1:
   helper:
     event      on
     globalinit 1
     last_timer 0
     sleepdevice XYZ_Anwesend
     sleepsubtimer -1
     sleeptimer -1
     timerdev   XYZ_Anwesend
     timerevent off
     triggerDev XYZ_Anwesend
     timerevents:
       off
     timereventsState:
       state: off
     triggerEvents:
       on
     triggerEventsState:
       state: on
   internals:
     0           XYZ_Anwesend_Anwesend:STATE alarm_sprach_aus:STATE Bewegung_Garage:STATE
     all         XYZ_Anwesend_Anwesend:STATE alarm_sprach_aus:STATE Bewegung_Garage:STATE
   itimer:
   readings:
   regexp:
     0:
     all:
   state:
     STATE:
   trigger:
Attributes:
   disable    0
   do         always
   room       Handys,test
   wait       90



##############################################
# $Id: myUtilsTemplate.pm 7570 2015-01-14 18:31:44Z rudolfkoenig $
#
# Save this file as 99_myUtils.pm, and create your own functions in the new
# file. They are then available in every Perl expression.

package main;

use strict;
use warnings;
use POSIX;

sub
myUtils_Initialize($$)
{
  my ($hash) = @_;
}

# Enter you functions below _this_ line.



## DebianMail Mail auf dem RPi versenden ############
sub
DebianMail
{
my $rcpt = shift;
my $subject = shift;
my $text = shift;
my $attach = shift;
my $ret = "";
my $sender = "xyz.de";
my $konto = "test\@d.de";
my $passwrd = "yyyyyyy";
my $provider = "smtp.xyz.:25";
Log 1, "sendEmail RCP: $rcpt";
Log 1, "sendEmail Subject: $subject";
Log 1, "sendEmail Text: $text";
Log 1, "sendEmail Anhang: $attach";;

$ret .= qx(sendEmail -f '$sender' -t '$rcpt' -u '$subject' -m  '$provider' -xu '$konto' -xp '$passwrd' -o tls=no  -o ;
$ret =~ s,[\r\n]*,,g; # remove CR from return-string
Log 1, "sendEmail returned: $ret";
}

1;

Ellert

Mit do always wird jedesmal, wenn die Bedingung wahr wird gesendet. Wie sehen die Events de beteiligten Geräte aus?

achim60

#2
Das System lief vorher echt stabil so wie es konfiguriert ist auch mit der do always bedingung. Erst nach eine Update macht es hier und da Probleme.


Internals:
   CUL_0_MSGCNT 8
   CUL_0_RAWMSG A0D28A6414CCFA6F1103401282E80::-66.5:CUL_0
   CUL_0_RSSI -66.5
   CUL_0_TIME 2017-12-01 17:11:42
   DEF        4CCFA6
   IODev      CUL_0
   LASTInputDev CUL_0
   MSGCNT     8
   NAME       Bewegungsmelder_Garage
   NOTIFYDEV  global
   NR         111
   STATE      noMotion
   TYPE       CUL_HM
   lastMsg    No:28 - t:41 s:4CCFA6 d:F11034 01282E80
   protLastRcv 2017-12-01 17:11:42
   protSnd    8 last_at:2017-12-01 17:11:42
   protState  CMDs_done
   rssi_at_CUL_0 avg:-68.81 lst:-66.5 max:-66.5 cnt:8 min:-72.5
   READINGS:
     2017-01-17 13:39:41   CommandAccepted yes
     2017-01-17 13:39:40   D-firmware      1.6
     2017-01-17 13:39:40   D-serialNr      NEQ0417044
     2017-01-17 13:39:40   R-pairCentral   set_0xF11034
     2017-06-12 20:49:07   RegL_00.
     2017-04-03 12:42:33   STATE           motion
     2017-12-01 17:11:42   battery         ok
     2017-12-01 17:11:42   brightness      46
     2017-11-04 15:33:16   cover           closed
     2017-12-01 17:15:44   motion          off
     2017-12-01 17:11:42   motionCount     40_next:240s
     2017-12-01 17:15:44   motionDuration  242
     2017-11-04 15:33:16   powerOn         2017-11-04 15:33:16
     2017-11-04 15:33:16   recentStateType info
     2017-12-01 17:15:44   state           noMotion
     2017-12-01 17:11:42   trigDst_F11034  noConfig
     2017-12-01 17:11:42   trigger_cnt     40
   helper:
     HM_CMDNR   40
     mId        004F
     rxType     28
     supp_Pair_Rep 0
     expert:
       def        1
       det        0
       raw        1
       tpl        0
     io:
       newChn     +4CCFA6,00,00,00
       nextSend   1512144702.71289
       prefIO
       rxt        2
       vccu
       p:
         4CCFA6
         00
         00
         00
     mRssi:
       mNo        28
       io:
         CUL_0      -64.5
     prt:
       bErr       0
       sProc      0
       sleeping   1
       rspWait:
     q:
       qReqConf   00
       qReqStat
     role:
       chn        1
       dev        1
     rpt:
       IO         CUL_0
       flg        A
       ts         1512144702.75336
       ack:
         HASH(0x350f678)
         288002F110344CCFA601012E00
     rssi:
       at_CUL_0:
         avg        -68.8125
         cnt        8
         lst        -66.5
         max        -66.5
         min        -72.5
Attributes:
   IODev      CUL_0
   actStatus  1
   autoReadReg 4_reqStatus
   expert     2_full
   firmware   1.6
   model      HM-SEN-MDIR-SM
   room       Garage
   serialNr   NEQ0417044
   showtime   1
   subType    motionDetector



Internals:
   ADDRESS    192.168.178.26
   CHANGED
   DEF        lan-ping 192.168.178.26
   MODE       lan-ping
   NAME       Handy_xyz
   NOTIFYDEV  global
   NR         110
   NTFY_ORDER 50-Handy_xyz
   STATE      present
   TIMEOUT_NORMAL 30
   TIMEOUT_PRESENT 30
   TYPE       PRESENCE
   READINGS:
     2017-11-28 10:04:47   model           lan-ping
     2017-12-02 10:50:34   presence        present
     2017-12-02 10:50:34   state           present
   helper:
     CURRENT_STATE present
Attributes:
   event-on-change-reading state,presence
   ping_count 1
   presence   Anwesenheit
   room       Handys
   userattr   presence presence_map structexclude



Internals:
   CUL_0_MSGCNT 1024
   CUL_0_RAWMSG A0D5384104F9301F1103406014C00::-48:CUL_0
   CUL_0_RSSI -48
   CUL_0_TIME 2017-12-02 10:47:56
   DEF        4F9301
   IODev      CUL_0
   LASTInputDev CUL_0
   MSGCNT     1024
   NAME       Bewegungsmelder_Hausflur
   NOTIFYDEV  global
   NR         94
   STATE      noMotion
   TYPE       CUL_HM
   lastMsg    No:53 - t:10 s:4F9301 d:F11034 06014C00
   protLastRcv 2017-12-02 10:47:56
   protSnd    16 last_at:2017-12-02 08:10:50
   protState  CMDs_done
   rssi_at_CUL_0 avg:-47.56 max:-44 lst:-48 min:-51.5 cnt:1024
   READINGS:
     2017-11-28 10:04:53   Activity        alive
     2017-01-13 20:16:46   D-firmware      1.6
     2017-01-13 20:16:46   D-serialNr      NEQ1295704
     2017-01-13 20:06:51   PairedTo        0xF11034
     2017-01-13 20:16:37   R-brightFilter  set_7
     2017-01-13 20:16:37   R-captInInterval set_off
     2017-01-13 20:16:37   R-evtFltrNum    set_1
     2017-01-13 20:16:37   R-evtFltrPeriod set_1 s
     2017-01-13 20:16:37   R-minInterval   set_60
     2017-01-13 20:06:51   R-pairCentral   0xF11034
     2017-04-03 10:12:21   STATE           motion
     2017-12-02 10:47:56   battery         ok
     2017-12-02 10:47:56   brightness      76
     2017-12-02 10:47:56   cover           closed
     2017-12-02 08:11:52   motion          off
     2017-12-02 08:10:50   motionCount     134_next:60s
     2017-12-02 08:11:52   motionDuration  62
     2017-02-21 13:34:13   powerOn         2017-02-21 13:34:13
     2017-12-02 10:47:56   recentStateType info
     2017-12-02 08:11:52   state           noMotion
     2017-12-02 08:10:50   trigDst_F11034  noConfig
     2017-12-02 08:10:50   trigger_cnt     134
   helper:
     HM_CMDNR   83
     mId        005D
     rxType     28
     supp_Pair_Rep 0
     expert:
       def        1
       det        0
       raw        1
       tpl        0
     io:
       newChn     +4F9301,00,00,00
       nextSend   1512208076.54331
       prefIO
       rxt        2
       vccu
       p:
         4F9301
         00
         00
         00
     mRssi:
       mNo        53
       io:
         CUL_0      -46
     prt:
       bErr       0
       sProc      0
       sleeping   1
       rspWait:
     q:
       qReqConf   00
       qReqStat
     role:
       chn        1
       dev        1
     rssi:
       at_CUL_0:
         avg        -47.560546875
         cnt        1024
         lst        -48
         max        -44
         min        -51.5
Attributes:
   IODev      CUL_0
   actCycle   000:10
   actStatus  alive
   autoReadReg 4_reqStatus
   expert     2_full
   firmware   1.6
   model      HM-Sen-MDIR-O
   peerIDs    00000000,
   room       Haus-Flur
   serialNr   NEQ1295704
   showtime   1
   subType    motionDetector


Die XYZ_Anwesend_Anwesend, alarm_sprach_aus und Bewegung_Garage sind nur Dummys die entweder ein oder ausgeschaltet werden

Ellert


achim60

mhhhh im Eventmonitors kommt nicht viel. Habe gerade einmal alles Simuliert und es ging. Also es kam nur ein Mail, wie gewollt.
Warum ist das mal so und mal so ?

Ich poste Dir auch noch einmal das jetzige Log


Eventmonitors

2017-12-02 11:14:11 DOIF di_meldung_Handy_flur cmd_nr: 1
2017-12-02 11:14:11 DOIF di_meldung_Handy_flur cmd: 1
2017-12-02 11:14:11 DOIF di_meldung_Handy_flur cmd_event: Bewegung_Hausflur
2017-12-02 11:14:11 DOIF di_meldung_Handy_flur cmd_1
2017-12-02 11:14:11 dummy Bewegung_Hausflur on
###############
2017-12-02 11:27:50 DOIF alarm_bewegung_garage_handy wait_timer: no timer
2017-12-02 11:27:51 DOIF alarm_bewegung_garage_handy cmd_nr: 1
2017-12-02 11:27:51 DOIF alarm_bewegung_garage_handy cmd: 1
2017-12-02 11:27:51 DOIF alarm_bewegung_garage_handy cmd_event: Bewegung_Garage
2017-12-02 11:27:51 DOIF alarm_bewegung_garage_handy cmd_1


Log:


2017.12.02 11:14:10 5: Cmd: >set Bewegung_Hausflur on<
2017.12.02 11:14:10 4: dummy set Bewegung_Hausflur on
2017.12.02 11:14:10 5: Starting notify loop for Bewegung_Hausflur, 1 event(s), first is on
2017.12.02 11:14:10 1: sendEmail RCP: <alarm@keil-datenklick.de>
2017.12.02 11:14:10 1: sendEmail Subject: Bewegung-Hausflur
2017.12.02 11:14:10 1: sendEmail Text:
2017.12.02 11:14:10 1: sendEmail Anhang:
2017.12.02 11:14:11 1: sendEmail returned: Reading message body from STDIN because the '-m' option was not used.If you are manually typing in a message:  - First line must be received within 60 seconds.  - End manual input with a CTRL-D on its own line.Dec 02 11:14:11 raspberrypi sendEmail[22569]: Message input complete.Dec 02 11:14:11 raspberrypi sendEmail[22569]: Email was sent successfully!
2017.12.02 11:14:11 5: Starting notify loop for di_meldung_Handy_flur, 4 event(s), first is cmd_nr: 1
2017.12.02 11:14:11 5: End notify loop for di_meldung_Handy_flur
2017.12.02 11:14:11 5: End notify loop for Bewegung_Hausflur
2017.12.02 11:14:11 4: WEB: /fhem?cmd.Bewegung_Hausflur=set%20Bewegung_Hausflur%20on&room=Haus-Flur&XHR=1&fw_id=31561 / RL:20 / text/plain; charset=UTF-8 / Content-Encoding: gzip
###############################
2017.12.02 11:27:50 5: Starting notify loop for alarm_bewegung_garage_handy, 1 event(s), first is wait_timer: no timer
2017.12.02 11:27:50 5: End notify loop for alarm_bewegung_garage_handy
2017.12.02 11:27:50 1: sendEmail RCP: <a.k@keil-datenklick.de>
2017.12.02 11:27:50 1: sendEmail Subject: Bewegung-Garage bzw.Tor
2017.12.02 11:27:50 1: sendEmail Text:
2017.12.02 11:27:50 1: sendEmail Anhang:
2017.12.02 11:27:51 1: sendEmail returned: Reading message body from STDIN because the '-m' option was not used.If you are manually typing in a message:  - First line must be received within 60 seconds.  - End manual input with a CTRL-D on its own line.Dec 02 11:27:51 raspberrypi sendEmail[23078]: Message input complete.Dec 02 11:27:51 raspberrypi sendEmail[23078]: Email was sent successfully!
2017.12.02 11:27:51 5: Starting notify loop for alarm_bewegung_garage_handy, 4 event(s), first is cmd_nr: 1
2017.12.02 11:27:51 5: End notify loop for alarm_bewegung_garage_handy



Ellert

Ja, den Events nach hat DOIF den Befehl nur einmal gesendet, es wäre zur Fehlereingrenzung hilfreich, die Events zu kennen, die zum wiederholten Auslösen führen.

achim60

ja das möchte ich auch gerne wissen, nur finde ich keine Logs mehr.
Logt Fhem noch irgendwo mit ?

Ellert

Du müsstest den Eventmonitor geöffnet lassen, ggf. die Events filtern und ins Log schreiben lassen.