[Gelöst] ESP Easy Readings "ändern" sich von allein?

Begonnen von thm12345, 14 Mai 2017, 22:48:07

Vorheriges Thema - Nächstes Thema

thm12345

Hallo,

ich möchte mit einem ESP-01 und einem PCF8574 4 Relais per FHEM schalten. Grundsätzlich funktioniert es bis auf ein (hoffentlich) kleineres Problem:

Die Logik ist beim ESP Easy "verdreht" - 0 => Ein / 1 => Aus. Das bekomme ich in FHEM (eventMap) angepasst. Was mich aber verwundert, ist, dass mein Reading irgendwann, ohne einen Schaltvorgang o.ä. von "off" auf "0"(!) und "on" auf "1"(!) schaltet. Ist das eventuell ein Bug? Indem ich alle 4 Statuswerte abfange, funktioniert es. Es ist aber sicher nicht so gedacht oder?

Hier meine Definition:

define ESPEasy_ESPEasy00_R1 ESPEasy 192.168.178.240 80 ESPBridge ESPEasy00_R1
attr ESPEasy_ESPEasy00_R1 IODev ESPBridge
attr ESPEasy_ESPEasy00_R1 Interval 60
attr ESPEasy_ESPEasy00_R1 alias Relais 1 - Wiese
attr ESPEasy_ESPEasy00_R1 devStateIcon off:ios-on-green:off 0:ios-on-green:off on:ios-off:on 1:ios-off:on .*:ios-NACK:check
attr ESPEasy_ESPEasy00_R1 event-min-interval 1800
attr ESPEasy_ESPEasy00_R1 event-on-change-reading R1
attr ESPEasy_ESPEasy00_R1 eventMap /pcfgpio 1 on:off/pcfgpio 1 off:on/
attr ESPEasy_ESPEasy00_R1 group Bewässerungskreis 1
attr ESPEasy_ESPEasy00_R1 icon sani_irrigation
attr ESPEasy_ESPEasy00_R1 room Garten
attr ESPEasy_ESPEasy00_R1 setState 0
attr ESPEasy_ESPEasy00_R1 stateFormat {ReadingsVal($name,"presence","") eq "absent" ? "absent" : ReadingsVal($name,"R1","")}
attr ESPEasy_ESPEasy00_R1 webCmd :


Gruß
Thomas

dev0

Zitat von: thm12345 am 14 Mai 2017, 22:48:07
Die Logik ist beim ESP Easy "verdreht" - 0 => Ein / 1 => Aus. Das bekomme ich in FHEM (eventMap) angepasst.
Ich gehe davon aus, dass das vom ESPEasy Plugin falsch verarbeitet wird. Um das zu prüfen benötige ich das verbose 5 Log der Bridge, von einem Schaltvorgang.

Zitat
attr ESPEasy_ESPEasy00_R1 event-min-interval 1800
Die Syntax ist falsch. Siehe https://fhem.de/commandref.html#readingFnAttributes

Zitat
attr ESPEasy_ESPEasy00_R1 event-on-change-reading R1
Damit bekommst Du nur noch Änderungden des Reading R1 als Event. Alle anderen Events (zB. für Presence etc.) werden nicht mehr verarbeitet.

Zitat
Was mich aber verwundert, ist, dass mein Reading irgendwann, ohne einen Schaltvorgang o.ä. von "off" auf "0"(!) und "on" auf "1"(!) schaltet. Ist das eventuell ein Bug?
Um das zu prüfen benötige ich:
- die Ausgabe von 'version'.
- ein 'list' der Bridge und des betroffenen Device
- die Events, die das beschriebene Verhalten auslösen (Eventmonitor oder inform)
- das passende Log zu diesem Zeitpunkt (mit 'attr global verbose 5' und 'attr global mseclog 1') incl. 5s vor- u. nachher.
- alle gezeigten Informationen bitte in Code Tags einfassen (# Button). Siehe: https://forum.fhem.de/index.php/topic,71806.0.html

Was heißt irgendwann etwas genauer? Regelmäßig nach ~60s oder auch mal am erst nächsten Tag?


thm12345

Hallo,
Zitat
Die Logik ist beim ESP Easy "verdreht" - 0 => Ein / 1 => Aus. Das bekomme ich in FHEM (eventMap) angepasst.
Zitat
Ich gehe davon aus, dass das vom ESPEasy Plugin falsch verarbeitet wird. Um das zu prüfen benötige ich das verbose 5 Log der Bridge, von einem Schaltvorgang.
Ich denke das ist soweit richtig, da ich diese "Drehung" schon im ESP Easy habe. Ich verwende hier als Device "Switch Input - PCF8574". Auch wenn ich direkt per URL schalte, ist es so - 0 schaltet das Relais ein, 1 schaltet es aus.
Zitat
attr ESPEasy_ESPEasy00_R1 event-min-interval 1800
Zitat
Die Syntax ist falsch. Siehe https://fhem.de/commandref.html#readingFnAttributes
attr ESPEasy_ESPEasy00_R1 event-on-change-reading R1
Zitat
Damit bekommst Du nur noch Änderungden des Reading R1 als Event. Alle anderen Events (zB. für Presence etc.) werden nicht mehr verarbeitet.
Ich bin gerade "Einsteiger" in FHEM. Ich entferne diese Einstellungen erst mal und belese mich ein wenig mehr. Ich hatte diese Settings zum "Erkunden" der Funktionen drin. Danke für den Hinweis. :)
Zitat
- die Ausgabe von 'version'.

Latest Revision: 14275

File                Rev   Last Change

fhem.pl             14270 2017-05-13 11:58:16Z rudolfkoenig
96_allowed.pm       13492 2017-02-23 09:11:20Z rudolfkoenig
90_at.pm            13840 2017-03-29 07:52:29Z rudolfkoenig
98_autocreate.pm    11984 2016-08-19 12:47:50Z rudolfkoenig
93_DbLog.pm         14030 2017-04-18 20:24:55Z DS_Starter
98_dummy.pm         12700 2016-12-02 16:49:42Z rudolfkoenig
34_ESPEasy.pm       14184 2017-05-04 10:21:43Z dev0
91_eventTypes.pm    11984 2016-08-19 12:47:50Z rudolfkoenig
01_FHEMWEB.pm       14253 2017-05-12 06:11:12Z rudolfkoenig
92_FileLog.pm       14206 2017-05-06 11:42:54Z rudolfkoenig
72_FRITZBOX.pm      14176 2017-05-03 16:08:54Z tupol
02_HTTPSRV.pm       13976 2017-04-12 13:35:44Z neubert
38_netatmo.pm       14247 2017-05-11 15:21:40Z moises
91_notify.pm        13630 2017-03-06 21:05:08Z rudolfkoenig
33_readingsGroup.pm 14044 2017-04-20 07:48:44Z justme1968
99_SUNRISE_EL.pm    12485 2016-11-01 15:18:51Z rudolfkoenig
98_telnet.pm        13443 2017-02-19 12:51:22Z rudolfkoenig
99_Utils.pm         13259 2017-01-28 17:39:39Z rudolfkoenig
98_version.pm       13628 2017-03-06 20:43:50Z markusbloch

Blocking.pm         12648 2016-11-24 12:15:25Z rudolfkoenig
Color.pm            11159 2016-03-30 16:08:06Z justme1968
FritzBoxUtils.pm     6574 2014-09-19 17:32:48Z rudolfkoenig
HttpUtils.pm        13998 2017-04-15 12:33:23Z rudolfkoenig
RTypes.pm           10476 2016-01-12 21:03:33Z borisneubert
SetExtensions.pm    12935 2017-01-02 19:51:46Z rudolfkoenig
TcpServerUtils.pm   13967 2017-04-11 09:32:30Z rudolfkoenig

fhemweb.js                 14057 2017-04-21 08:30:42Z rudolfkoenig
fhemweb_colorpicker.js     13580 2017-03-02 13:03:29Z justme1968
fhemweb_fbcalllist.js      13629 2017-03-06 20:50:43Z markusbloch
fhemweb_readingsGroup.js   13580 2017-03-02 13:03:29Z justme1968
fhemweb_readingsHistory.js 13580 2017-03-02 13:03:29Z justme1968
fhemweb_sortable.js        13629 2017-03-06 20:50:43Z markusbloch
fhemweb_uzsu.js            13580 2017-03-02 13:03:29Z justme1968

Zitat
- ein 'list' der Bridge und des betroffenen Device

Internals:
   CONNECTS   60
   DEF        bridge 8383
   FD         11
   HOST       bridge
   MAX_HTTP_SESSIONS 3
   MAX_QUEUE_SIZE 250
   NAME       ESPBridge
   NOTIFYDEV  global
   NR         27
   NTFY_ORDER 50-ESPBridge
   PASS       not defined yet !!!
   PORT       8383
   SESSIONS   0
   STATE      initialized
   SUBTYPE    bridge
   TYPE       ESPEasy
   USER       not defined yet !!!
   VERSION    1.07
   Readings:
     2017-05-16 21:08:32   state           initialized
   Helper:
     pmEncode   1
     Received:
       192.168.178.240:
         build      147
         espName    ESPEasy00
         sleep      0
         unit       1
         version    9
Attributes:
   authentication 0
   combineDevices 0
   devStateIcon .*:it_wifi
   room       Unsorted
   verbose    5
   webCmd     :

Internals:
   DEF        192.168.178.240 80 ESPBridge ESPEasy00_R1
   ESPBridge_MSGCNT 18
   ESPBridge_TIME 2017-05-16 21:25:42
   ESP_BUILD  147
   ESP_SLEEP  0
   ESP_UNIT   1
   ESP_VERSION 9
   HOST       192.168.178.240
   IDENT      ESPEasy00_R1
   INTERVAL   60
   IODev      ESPBridge
   LASTInputDev ESPBridge
   MSGCNT     18
   NAME       ESPEasy_ESPEasy00_R1
   NOTIFYDEV  global
   NR         42
   NTFY_ORDER 50-ESPEasy_ESPEasy00_R1
   PORT       80
   STATE      off
   SUBTYPE    device
   TYPE       ESPEasy
   VERSION    1.07
   Helper:
     Dblog:
       R1:
         Logdb:
           TIME       1494962742.21677
           VALUE      off
       State:
         Logdb:
           TIME       1494962742.01133
           VALUE      on
   Readings:
     2017-05-16 21:25:42   R1              off
     2017-05-16 21:25:16   presence        present
     2017-05-16 21:08:33   state           opened
   Helper:
     fpc        1494961721
     pmEncode   1
     Intat:
       1:
         FN         ESPEasy_statusRequest
         INTERVAL   63
         TRIGGERTIME 16.05.2017 21:26:19
     Received:
       R1         1494962742
Attributes:
   IODev      ESPBridge
   Interval   60
   alias      Relais 1 - Wiese
   devStateIcon off:ios-on-green:off 0:ios-on-green:off on:ios-off:on 1:ios-off:on .*:ios-NACK:check
   eventMap   /pcfgpio 1 on:off/pcfgpio 1 off:on/
   group      Bewässerungskreis 1
   icon       sani_irrigation
   room       Garten
   setState   0
   stateFormat {ReadingsVal($name,"presence","") eq "absent" ? "absent" : ReadingsVal($name,"R1","")}
   webCmd     :

Zitat
- die Events, die das beschriebene Verhalten auslösen (Eventmonitor oder inform)
Wenn ich das Relais per FHEM schalte und einen Moment (1-2 Minuten) warte, passiert die "Umschaltung" von off nach 0 und umgekehrt. In diesem Eventlogausschnitt habe ich gegen 22:09:21 das Relais ein- und gegen 22:10:19 ausgeschaltet.

2017-05-16 22:09:13.026 ESPEasy ESPEasy_ESPEasy00_R2 R2: 1
2017-05-16 22:09:19.035 ESPEasy ESPEasy_ESPEasy00_R3 R3: 1
2017-05-16 22:09:21.316 ESPEasy ESPEasy_ESPEasy00_R1 on
2017-05-16 22:09:21.448 ESPEasy ESPEasy_ESPEasy00_R1 R1: off
2017-05-16 22:09:26.042 ESPEasy ESPEasy_ESPEasy00_R4 R4: 1
2017-05-16 22:10:06.196 ESPEasy ESPEasy_ESPEasy00_R1 R1: 0
2017-05-16 22:10:06.804 ESPEasy ESPEasy_ESPEasy00_R1 presence: present
2017-05-16 22:10:13.091 ESPEasy ESPEasy_ESPEasy00_R2 R2: 1
2017-05-16 22:10:17.393 ESPEasy ESPEasy_ESPEasy00_R1 off
2017-05-16 22:10:19.043 ESPEasy ESPEasy_ESPEasy00_R1 R1: on
2017-05-16 22:10:20.069 ESPEasy ESPEasy_ESPEasy00_R3 R3: 1
2017-05-16 22:10:26.161 ESPEasy ESPEasy_ESPEasy00_R4 R4: 1
2017-05-16 22:11:06.150 ESPEasy ESPEasy_ESPEasy00_R1 R1: 1
2017-05-16 22:11:09.792 ESPEasy ESPEasy_ESPEasy00_R1 presence: present
2017-05-16 22:11:13.157 ESPEasy ESPEasy_ESPEasy00_R2 R2: 1
2017-05-16 22:11:19.164 ESPEasy ESPEasy_ESPEasy00_R3 R3: 1

Zitat
- das passende Log zu diesem Zeitpunkt (mit 'attr global verbose 5' und 'attr global mseclog 1') incl. 5s vor- u. nachher.

...
2017.05.16 22:09:19.209 4: Connection accepted from WEB_192.168.178.53_65178
2017.05.16 22:09:21.252 4: WEB_192.168.178.53_65156 POST /fhem?cmd.ESPEasy_ESPEasy00_R1=set%20ESPEasy_ESPEasy00_R1%20on&room=Garten&room=Garten&XHR=1&fw_id=249; BUFLEN:0
2017.05.16 22:09:21.254 5: Cmd: >set ESPEasy_ESPEasy00_R1 on<
2017.05.16 22:09:21.256 3: ESPEasy ESPEasy_ESPEasy00_R1: set ESPEasy_ESPEasy00_R1 pcfgpio 1 off
2017.05.16 22:09:21.257 5: ESPEasy ESPEasy_ESPEasy00_R1: onOff mapping off => 0
2017.05.16 22:09:21.257 5: ESPEasy ESPEasy_ESPEasy00_R1: IOWrite($defs{ESPEasy_ESPEasy00_R1}, 192.168.178.240, 80, ESPEasy00_R1, pcfgpio, 1,0)
2017.05.16 22:09:21.258 4: ESPEasy ESPBridge: Send pcfgpio,1,0 to 192.168.178.240 for ident ESPEasy00_R1
2017.05.16 22:09:21.259 5: ESPEasy ESPBridge: NonblockingGet for ident:ESPEasy00_R1 => http://192.168.178.240:80/control?cmd=pcfgpio,1,0
2017.05.16 22:09:21.259 4: HttpUtils url=http://192.168.178.240:80/control?cmd=pcfgpio,1,0
2017.05.16 22:09:21.263 5: Starting notify loop for ESPEasy_ESPEasy00_R1, 1 event(s), first is on
2017.05.16 22:09:21.264 5: createNotifyHash
2017.05.16 22:09:21.267 4: DbLog logdb -> ################################################################
2017.05.16 22:09:21.267 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:09:21.268 4: DbLog logdb -> ################################################################
2017.05.16 22:09:21.268 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R1
2017.05.16 22:09:21.269 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R1 , Event: on
2017.05.16 22:09:21.270 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:09:21, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: on, Reading: state, Value: on, Unit:
2017.05.16 22:09:21.274 4: DbLog logdb -> ################################################################
2017.05.16 22:09:21.275 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:09:21.275 4: DbLog logdb -> ################################################################
2017.05.16 22:09:21.275 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:09:21.302 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:09:21.302 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:09:21.303 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:09:21, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: on, Reading: state, Value: on, Unit:
2017.05.16 22:09:21.307 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:09:21.314 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:09:21.322 5: End notify loop for ESPEasy_ESPEasy00_R1
2017.05.16 22:09:21.324 4: WEB: /fhem?cmd.ESPEasy_ESPEasy00_R1=set%20ESPEasy_ESPEasy00_R1%20on&room=Garten&room=Garten&XHR=1&fw_id=249 / RL:20 / text/plain; charset=UTF-8 / Content-Encoding: gzip

/
2017.05.16 22:09:21.326 5: HttpUtils request header:
GET /control?cmd=pcfgpio,1,0 HTTP/1.0

Host: 192.168.178.240

User-Agent: fhem


2017.05.16 22:09:21.346 4: http://192.168.178.240:80/control?cmd=pcfgpio,1,0: HTTP response code 200
2017.05.16 22:09:21.346 4: HttpUtils http://192.168.178.240:80/control?cmd=pcfgpio,1,0: Got data, length: 83
2017.05.16 22:09:21.346 5: HttpUtils response header:
HTTP/1.1 200 OK

Content-Type: application/json

Content-Length: 83

Connection: close

Access-Control-Allow-Origin: *
2017.05.16 22:09:21.377 4: Connection accepted from ESPBridge_192.168.178.240_12120
2017.05.16 22:09:21.382 4: ESPEasy ESPBridge_192.168.178.240_12120: Peer address accepted
2017.05.16 22:09:21.383 5: ESPEasy ESPBridge_192.168.178.240_12120: Received header: {'Host' => '192.168.178.221','Authorization' => 'Basic ***** ','Connection' => 'close','Content-Length' => '213'}
2017.05.16 22:09:21.384 5: ESPEasy ESPBridge_192.168.178.240_12120: Received content: {"module":"ESPEasy","version":"1.02","data":{"ESP":{"name":"ESPEasy00","unit":1,"version":9,"build":147,"sleep":0,"ip":"192.168.178.240"},"SENSOR":{"0":{"deviceName":"R1","valueName":"R1","type":10,"value":"0"}}}}
2017.05.16 22:09:21.386 2: ESPEasy ESPBridge_192.168.178.240_12120: No basic authentication active but credentials received
2017.05.16 22:09:21.386 4: ESPEasy ESPBridge_192.168.178.240_12120: Send http close '200 OK'
2017.05.16 22:09:21.388 5: ESPEasy ESPBridge_192.168.178.240_12120: Dispatch: ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||0||10
2017.05.16 22:09:21.389 5: ESPBridge: dispatch ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||0||10
2017.05.16 22:09:21.390 5: ESPEasy ESPEasy_ESPEasy00_R1: Received: ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||0||10
2017.05.16 22:09:21.393 4: ESPEasy ESPEasy_ESPEasy00_R1: R1: off
2017.05.16 22:09:21.393 5: ESPEasy ESPEasy_ESPEasy00_R1: Internals: unit:1 sleep:0 build:147 version:9
2017.05.16 22:09:21.395 5: Starting notify loop for ESPEasy_ESPEasy00_R1, 1 event(s), first is R1: off
2017.05.16 22:09:21.396 4: DbLog logdb -> ################################################################
2017.05.16 22:09:21.397 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:09:21.397 4: DbLog logdb -> ################################################################
2017.05.16 22:09:21.397 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R1
2017.05.16 22:09:21.398 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R1 , Event: R1: off
2017.05.16 22:09:21.399 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:09:21, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: R1: off, Reading: R1, Value: off, Unit:
2017.05.16 22:09:21.404 4: DbLog logdb -> ################################################################
2017.05.16 22:09:21.404 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:09:21.404 4: DbLog logdb -> ################################################################
2017.05.16 22:09:21.405 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:09:21.432 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:09:21.433 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:09:21.433 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:09:21, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: R1: off, Reading: R1, Value: off, Unit:
2017.05.16 22:09:21.437 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:09:21.445 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:09:21.454 5: End notify loop for ESPEasy_ESPEasy00_R1
2017.05.16 22:09:21.456 4: ESPEasy ESPBridge_192.168.178.240_12120: Closing tcp session.
2017.05.16 22:09:21.474 4: WEB_192.168.178.53_65156 GET /fhem/images/default/ios-on-green.png; BUFLEN:0
2017.05.16 22:09:21.476 4: WEB_192.168.178.53_65156 => 304 Not Modified
2017.05.16 22:09:23.372 4: Connection closed for WEB_192.168.178.53_65172: EOF
2017.05.16 22:09:25.971 4: Connection accepted from ESPBridge_192.168.178.240_4843
2017.05.16 22:09:25.976 4: ESPEasy ESPBridge_192.168.178.240_4843: Peer address accepted
2017.05.16 22:09:25.978 5: ESPEasy ESPBridge_192.168.178.240_4843: Received header: {'Host' => '192.168.178.221','Authorization' => 'Basic ***** ','Content-Length' => '212','Connection' => 'close'}
2017.05.16 22:09:25.978 5: ESPEasy ESPBridge_192.168.178.240_4843: Received content: {"module":"ESPEasy","version":"1.02","data":{"ESP":{"name":"ESPEasy00","unit":1,"version":9,"build":147,"sleep":0,"ip":"192.168.178.240"},"SENSOR":{"0":{"deviceName":"R4","valueName":"R4","type":1,"value":"1"}}}}
2017.05.16 22:09:25.980 2: ESPEasy ESPBridge_192.168.178.240_4843: No basic authentication active but credentials received
2017.05.16 22:09:25.981 4: ESPEasy ESPBridge_192.168.178.240_4843: Send http close '200 OK'
2017.05.16 22:09:25.982 5: ESPEasy ESPBridge_192.168.178.240_4843: Dispatch: ESPEasy00_R4::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R4||1||1
2017.05.16 22:09:25.983 5: ESPBridge: dispatch ESPEasy00_R4::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R4||1||1
2017.05.16 22:09:25.984 5: ESPEasy ESPEasy_ESPEasy00_R4: Received: ESPEasy00_R4::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R4||1||1
2017.05.16 22:09:25.987 4: ESPEasy ESPEasy_ESPEasy00_R4: R4: 1
2017.05.16 22:09:25.988 5: ESPEasy ESPEasy_ESPEasy00_R4: Internals: unit:1 sleep:0 build:147 version:9
2017.05.16 22:09:25.990 5: Starting notify loop for ESPEasy_ESPEasy00_R4, 1 event(s), first is R4: 1
2017.05.16 22:09:25.992 4: DbLog logdb -> ################################################################
2017.05.16 22:09:25.992 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:09:25.992 4: DbLog logdb -> ################################################################
2017.05.16 22:09:25.993 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R4
2017.05.16 22:09:25.993 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R4 , Event: R4: 1
2017.05.16 22:09:25.994 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:09:25, Device: ESPEasy_ESPEasy00_R4, Type: ESPEASY, Event: R4: 1, Reading: R4, Value: 1, Unit:
2017.05.16 22:09:25.999 4: DbLog logdb -> ################################################################
2017.05.16 22:09:25.999 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:09:26.000 4: DbLog logdb -> ################################################################
2017.05.16 22:09:26.000 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:09:26.027 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:09:26.027 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:09:26.028 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:09:25, Device: ESPEasy_ESPEasy00_R4, Type: ESPEASY, Event: R4: 1, Reading: R4, Value: 1, Unit:
2017.05.16 22:09:26.032 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:09:26.039 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:09:26.048 5: End notify loop for ESPEasy_ESPEasy00_R4
2017.05.16 22:09:26.051 4: ESPEasy ESPBridge_192.168.178.240_4843: Closing tcp session.
2017.05.16 22:09:28.498 4: WEB_192.168.178.53_65156 GET /fhem?detail=ESPEasy_ESPEasy00_R1; BUFLEN:0
2017.05.16 22:09:28.543 4: WEB: /fhem?detail=ESPEasy_ESPEasy00_R1 / RL:6026 / text/html; charset=UTF-8 / Content-Encoding: gzip

/
2017.05.16 22:09:29.038 4: WEB_192.168.178.53_65156 GET /fhem?cmd=%7BReadingsVal(%22ESPEasy_ESPEasy00_R1%22%2C%22clearreadings%22%2C%22%22)%7D&XHR=1; BUFLEN:0
2017.05.16 22:09:29.040 5: Cmd: >{ReadingsVal("ESPEasy_ESPEasy00_R1","clearreadings","")}<
2017.05.16 22:09:29.043 4: WEB: /fhem?cmd=%7BReadingsVal(%22ESPEasy_ESPEasy00_R1%22%2C%22clearreadings%22%2C%22%22)%7D&XHR=1 / RL:21 / text/plain; charset=UTF-8 / Content-Encoding: gzip

/
2017.05.16 22:09:29.050 4: WEB_192.168.178.53_65164 GET /fhem?cmd=%7BAttrVal(%22ESPEasy_ESPEasy00_R1%22%2C%22room%22%2C%22%22)%7D&XHR=1; BUFLEN:0
2017.05.16 22:09:29.052 5: Cmd: >{AttrVal("ESPEasy_ESPEasy00_R1","room","")}<
2017.05.16 22:09:29.056 4: WEB: /fhem?cmd=%7BAttrVal(%22ESPEasy_ESPEasy00_R1%22%2C%22room%22%2C%22%22)%7D&XHR=1 / RL:27 / text/plain; charset=UTF-8 / Content-Encoding: gzip

/
2017.05.16 22:09:29.170 4: Connection accepted from WEB_192.168.178.53_65179
2017.05.16 22:09:36.550 4: Connection closed for WEB_192.168.178.53_65174: EOF
2017.05.16 22:09:38.577 4: Connection closed for WEB_192.168.178.53_65176: EOF
2017.05.16 22:09:48.511 4: Connection closed for WEB_192.168.178.53_65178: EOF
2017.05.16 22:10:06.125 4: Connection accepted from ESPBridge_192.168.178.240_32627
2017.05.16 22:10:06.131 4: ESPEasy ESPBridge_192.168.178.240_32627: Peer address accepted
2017.05.16 22:10:06.132 5: ESPEasy ESPBridge_192.168.178.240_32627: Received header: {'Connection' => 'close','Content-Length' => '212','Host' => '192.168.178.221','Authorization' => 'Basic ***** '}
2017.05.16 22:10:06.132 5: ESPEasy ESPBridge_192.168.178.240_32627: Received content: {"module":"ESPEasy","version":"1.02","data":{"ESP":{"name":"ESPEasy00","unit":1,"version":9,"build":147,"sleep":0,"ip":"192.168.178.240"},"SENSOR":{"0":{"deviceName":"R1","valueName":"R1","type":1,"value":"0"}}}}
2017.05.16 22:10:06.134 2: ESPEasy ESPBridge_192.168.178.240_32627: No basic authentication active but credentials received
2017.05.16 22:10:06.135 4: ESPEasy ESPBridge_192.168.178.240_32627: Send http close '200 OK'
2017.05.16 22:10:06.136 5: ESPEasy ESPBridge_192.168.178.240_32627: Dispatch: ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||0||1
2017.05.16 22:10:06.137 5: ESPBridge: dispatch ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||0||1
2017.05.16 22:10:06.138 5: ESPEasy ESPEasy_ESPEasy00_R1: Received: ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||0||1
2017.05.16 22:10:06.141 4: ESPEasy ESPEasy_ESPEasy00_R1: R1: 0
2017.05.16 22:10:06.141 5: ESPEasy ESPEasy_ESPEasy00_R1: Internals: unit:1 sleep:0 build:147 version:9
2017.05.16 22:10:06.143 5: Starting notify loop for ESPEasy_ESPEasy00_R1, 1 event(s), first is R1: 0
2017.05.16 22:10:06.143 5: createNotifyHash
2017.05.16 22:10:06.147 4: DbLog logdb -> ################################################################
2017.05.16 22:10:06.147 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:10:06.147 4: DbLog logdb -> ################################################################
2017.05.16 22:10:06.148 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R1
2017.05.16 22:10:06.149 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R1 , Event: R1: 0
2017.05.16 22:10:06.149 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:10:06, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: R1: 0, Reading: R1, Value: 0, Unit:
2017.05.16 22:10:06.154 4: DbLog logdb -> ################################################################
2017.05.16 22:10:06.154 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:10:06.155 4: DbLog logdb -> ################################################################
2017.05.16 22:10:06.155 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:10:06.181 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:10:06.182 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:10:06.182 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:10:06, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: R1: 0, Reading: R1, Value: 0, Unit:
2017.05.16 22:10:06.187 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:10:06.193 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:10:06.201 5: End notify loop for ESPEasy_ESPEasy00_R1
2017.05.16 22:10:06.204 4: ESPEasy ESPBridge_192.168.178.240_32627: Closing tcp session.
2017.05.16 22:10:06.754 4: ESPEasy ESPEasy_ESPEasy00_R1: set statusRequest
2017.05.16 22:10:06.758 5: Starting notify loop for ESPEasy_ESPEasy00_R1, 1 event(s), first is presence: present
2017.05.16 22:10:06.760 4: DbLog logdb -> ################################################################
2017.05.16 22:10:06.760 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:10:06.761 4: DbLog logdb -> ################################################################
2017.05.16 22:10:06.761 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R1
2017.05.16 22:10:06.762 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R1 , Event: presence: present
2017.05.16 22:10:06.763 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:10:06, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: presence: present, Reading: presence, Value: present, Unit:
2017.05.16 22:10:06.767 4: DbLog logdb -> ################################################################
2017.05.16 22:10:06.768 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:10:06.768 4: DbLog logdb -> ################################################################
2017.05.16 22:10:06.768 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:10:06.790 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:10:06.791 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:10:06.791 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:10:06, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: presence: present, Reading: presence, Value: present, Unit:
2017.05.16 22:10:06.795 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:10:06.801 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:10:06.810 5: End notify loop for ESPEasy_ESPEasy00_R1
2017.05.16 22:10:06.810 4: ESPEasy ESPEasy_ESPEasy00_R1: presence: present
2017.05.16 22:10:06.811 5: ESPEasy ESPEasy_ESPEasy00_R1: Start internalTimer +62 => 2017-05-16 22:11:09
2017.05.16 22:10:13.019 4: Connection accepted from ESPBridge_192.168.178.240_13073
2017.05.16 22:10:13.023 4: ESPEasy ESPBridge_192.168.178.240_13073: Peer address accepted
2017.05.16 22:10:13.025 5: ESPEasy ESPBridge_192.168.178.240_13073: Received header: {'Content-Length' => '212','Connection' => 'close','Host' => '192.168.178.221','Authorization' => 'Basic ***** '}
2017.05.16 22:10:13.025 5: ESPEasy ESPBridge_192.168.178.240_13073: Received content: {"module":"ESPEasy","version":"1.02","data":{"ESP":{"name":"ESPEasy00","unit":1,"version":9,"build":147,"sleep":0,"ip":"192.168.178.240"},"SENSOR":{"0":{"deviceName":"R2","valueName":"R2","type":1,"value":"1"}}}}
2017.05.16 22:10:13.027 2: ESPEasy ESPBridge_192.168.178.240_13073: No basic authentication active but credentials received
2017.05.16 22:10:13.028 4: ESPEasy ESPBridge_192.168.178.240_13073: Send http close '200 OK'
2017.05.16 22:10:13.029 5: ESPEasy ESPBridge_192.168.178.240_13073: Dispatch: ESPEasy00_R2::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R2||1||1
2017.05.16 22:10:13.030 5: ESPBridge: dispatch ESPEasy00_R2::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R2||1||1
2017.05.16 22:10:13.031 5: ESPEasy ESPEasy_ESPEasy00_R2: Received: ESPEasy00_R2::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R2||1||1
2017.05.16 22:10:13.034 4: ESPEasy ESPEasy_ESPEasy00_R2: R2: 1
2017.05.16 22:10:13.035 5: ESPEasy ESPEasy_ESPEasy00_R2: Internals: unit:1 sleep:0 build:147 version:9
2017.05.16 22:10:13.037 5: Starting notify loop for ESPEasy_ESPEasy00_R2, 1 event(s), first is R2: 1
2017.05.16 22:10:13.038 4: DbLog logdb -> ################################################################
2017.05.16 22:10:13.039 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:10:13.039 4: DbLog logdb -> ################################################################
2017.05.16 22:10:13.039 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R2
2017.05.16 22:10:13.040 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R2 , Event: R2: 1
2017.05.16 22:10:13.041 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:10:13, Device: ESPEasy_ESPEasy00_R2, Type: ESPEASY, Event: R2: 1, Reading: R2, Value: 1, Unit:
2017.05.16 22:10:13.045 4: DbLog logdb -> ################################################################
2017.05.16 22:10:13.046 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:10:13.046 4: DbLog logdb -> ################################################################
2017.05.16 22:10:13.046 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:10:13.076 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:10:13.076 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:10:13.077 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:10:13, Device: ESPEasy_ESPEasy00_R2, Type: ESPEASY, Event: R2: 1, Reading: R2, Value: 1, Unit:
2017.05.16 22:10:13.081 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:10:13.087 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:10:13.091 5: End notify loop for ESPEasy_ESPEasy00_R2
2017.05.16 22:10:13.093 4: ESPEasy ESPBridge_192.168.178.240_13073: Closing tcp session.
2017.05.16 22:10:17.331 4: WEB_192.168.178.53_65156 POST /fhem?cmd.ESPEasy_ESPEasy00_R1=set%20ESPEasy_ESPEasy00_R1%20off&room=Garten&XHR=1&fw_id=249; BUFLEN:0
2017.05.16 22:10:17.332 5: Cmd: >set ESPEasy_ESPEasy00_R1 off<
2017.05.16 22:10:17.335 3: ESPEasy ESPEasy_ESPEasy00_R1: set ESPEasy_ESPEasy00_R1 pcfgpio 1 on
2017.05.16 22:10:17.335 5: ESPEasy ESPEasy_ESPEasy00_R1: onOff mapping on => 1
2017.05.16 22:10:17.336 5: ESPEasy ESPEasy_ESPEasy00_R1: IOWrite($defs{ESPEasy_ESPEasy00_R1}, 192.168.178.240, 80, ESPEasy00_R1, pcfgpio, 1,1)
2017.05.16 22:10:17.337 4: ESPEasy ESPBridge: Send pcfgpio,1,1 to 192.168.178.240 for ident ESPEasy00_R1
2017.05.16 22:10:17.337 5: ESPEasy ESPBridge: NonblockingGet for ident:ESPEasy00_R1 => http://192.168.178.240:80/control?cmd=pcfgpio,1,1
2017.05.16 22:10:17.337 4: HttpUtils url=http://192.168.178.240:80/control?cmd=pcfgpio,1,1
2017.05.16 22:10:17.341 5: Starting notify loop for ESPEasy_ESPEasy00_R1, 1 event(s), first is off
2017.05.16 22:10:17.343 4: DbLog logdb -> ################################################################
2017.05.16 22:10:17.343 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:10:17.344 4: DbLog logdb -> ################################################################
2017.05.16 22:10:17.344 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R1
2017.05.16 22:10:17.344 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R1 , Event: off
2017.05.16 22:10:17.345 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:10:17, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: off, Reading: state, Value: off, Unit:
2017.05.16 22:10:17.350 4: DbLog logdb -> ################################################################
2017.05.16 22:10:17.350 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:10:17.351 4: DbLog logdb -> ################################################################
2017.05.16 22:10:17.351 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:10:17.378 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:10:17.379 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:10:17.380 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:10:17, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: off, Reading: state, Value: off, Unit:
2017.05.16 22:10:17.384 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:10:17.390 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:10:17.398 5: End notify loop for ESPEasy_ESPEasy00_R1
2017.05.16 22:10:17.400 4: WEB: /fhem?cmd.ESPEasy_ESPEasy00_R1=set%20ESPEasy_ESPEasy00_R1%20off&room=Garten&XHR=1&fw_id=249 / RL:20 / text/plain; charset=UTF-8 / Content-Encoding: gzip

/
2017.05.16 22:10:17.440 5: HttpUtils request header:
GET /control?cmd=pcfgpio,1,1 HTTP/1.0

Host: 192.168.178.240

User-Agent: fhem


2017.05.16 22:10:17.495 4: http://192.168.178.240:80/control?cmd=pcfgpio,1,1: HTTP response code 200
2017.05.16 22:10:17.496 4: HttpUtils http://192.168.178.240:80/control?cmd=pcfgpio,1,1: Got data, length: 83
2017.05.16 22:10:17.496 5: HttpUtils response header:
HTTP/1.1 200 OK

Content-Type: application/json

Content-Length: 83

Connection: close

Access-Control-Allow-Origin: *
2017.05.16 22:10:18.974 4: Connection accepted from ESPBridge_192.168.178.240_3813
2017.05.16 22:10:18.979 4: ESPEasy ESPBridge_192.168.178.240_3813: Peer address accepted
2017.05.16 22:10:18.980 5: ESPEasy ESPBridge_192.168.178.240_3813: Received header: {'Connection' => 'close','Content-Length' => '213','Authorization' => 'Basic ***** ','Host' => '192.168.178.221'}
2017.05.16 22:10:18.981 5: ESPEasy ESPBridge_192.168.178.240_3813: Received content: {"module":"ESPEasy","version":"1.02","data":{"ESP":{"name":"ESPEasy00","unit":1,"version":9,"build":147,"sleep":0,"ip":"192.168.178.240"},"SENSOR":{"0":{"deviceName":"R1","valueName":"R1","type":10,"value":"1"}}}}
2017.05.16 22:10:18.983 2: ESPEasy ESPBridge_192.168.178.240_3813: No basic authentication active but credentials received
2017.05.16 22:10:18.983 4: ESPEasy ESPBridge_192.168.178.240_3813: Send http close '200 OK'
2017.05.16 22:10:18.985 5: ESPEasy ESPBridge_192.168.178.240_3813: Dispatch: ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||1||10
2017.05.16 22:10:18.986 5: ESPBridge: dispatch ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||1||10
2017.05.16 22:10:18.987 5: ESPEasy ESPEasy_ESPEasy00_R1: Received: ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||1||10
2017.05.16 22:10:18.990 4: ESPEasy ESPEasy_ESPEasy00_R1: R1: on
2017.05.16 22:10:18.990 5: ESPEasy ESPEasy_ESPEasy00_R1: Internals: unit:1 sleep:0 build:147 version:9
2017.05.16 22:10:18.992 5: Starting notify loop for ESPEasy_ESPEasy00_R1, 1 event(s), first is R1: on
2017.05.16 22:10:18.993 4: DbLog logdb -> ################################################################
2017.05.16 22:10:18.994 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:10:18.994 4: DbLog logdb -> ################################################################
2017.05.16 22:10:18.994 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R1
2017.05.16 22:10:18.995 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R1 , Event: R1: on
2017.05.16 22:10:18.996 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:10:18, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: R1: on, Reading: R1, Value: on, Unit:
2017.05.16 22:10:19.000 4: DbLog logdb -> ################################################################
2017.05.16 22:10:19.001 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:10:19.001 4: DbLog logdb -> ################################################################
2017.05.16 22:10:19.002 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:10:19.028 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:10:19.029 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:10:19.029 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:10:18, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: R1: on, Reading: R1, Value: on, Unit:
2017.05.16 22:10:19.033 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:10:19.040 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:10:19.048 5: End notify loop for ESPEasy_ESPEasy00_R1
2017.05.16 22:10:19.050 4: ESPEasy ESPBridge_192.168.178.240_3813: Closing tcp session.
2017.05.16 22:10:20.001 4: Connection accepted from ESPBridge_192.168.178.240_29342
2017.05.16 22:10:20.007 4: ESPEasy ESPBridge_192.168.178.240_29342: Peer address accepted
2017.05.16 22:10:20.008 5: ESPEasy ESPBridge_192.168.178.240_29342: Received header: {'Connection' => 'close','Content-Length' => '212','Authorization' => 'Basic ***** ','Host' => '192.168.178.221'}
2017.05.16 22:10:20.008 5: ESPEasy ESPBridge_192.168.178.240_29342: Received content: {"module":"ESPEasy","version":"1.02","data":{"ESP":{"name":"ESPEasy00","unit":1,"version":9,"build":147,"sleep":0,"ip":"192.168.178.240"},"SENSOR":{"0":{"deviceName":"R3","valueName":"R3","type":1,"value":"1"}}}}
2017.05.16 22:10:20.010 2: ESPEasy ESPBridge_192.168.178.240_29342: No basic authentication active but credentials received
2017.05.16 22:10:20.011 4: ESPEasy ESPBridge_192.168.178.240_29342: Send http close '200 OK'
2017.05.16 22:10:20.012 5: ESPEasy ESPBridge_192.168.178.240_29342: Dispatch: ESPEasy00_R3::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R3||1||1
2017.05.16 22:10:20.013 5: ESPBridge: dispatch ESPEasy00_R3::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R3||1||1
2017.05.16 22:10:20.014 5: ESPEasy ESPEasy_ESPEasy00_R3: Received: ESPEasy00_R3::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R3||1||1
2017.05.16 22:10:20.017 4: ESPEasy ESPEasy_ESPEasy00_R3: R3: 1
2017.05.16 22:10:20.018 5: ESPEasy ESPEasy_ESPEasy00_R3: Internals: unit:1 sleep:0 build:147 version:9
2017.05.16 22:10:20.020 5: Starting notify loop for ESPEasy_ESPEasy00_R3, 1 event(s), first is R3: 1
2017.05.16 22:10:20.022 4: DbLog logdb -> ################################################################
2017.05.16 22:10:20.022 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:10:20.022 4: DbLog logdb -> ################################################################
2017.05.16 22:10:20.022 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R3
2017.05.16 22:10:20.023 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R3 , Event: R3: 1
2017.05.16 22:10:20.024 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:10:20, Device: ESPEasy_ESPEasy00_R3, Type: ESPEASY, Event: R3: 1, Reading: R3, Value: 1, Unit:
2017.05.16 22:10:20.029 4: DbLog logdb -> ################################################################
2017.05.16 22:10:20.029 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:10:20.029 4: DbLog logdb -> ################################################################
2017.05.16 22:10:20.030 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:10:20.054 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:10:20.055 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:10:20.055 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:10:20, Device: ESPEasy_ESPEasy00_R3, Type: ESPEASY, Event: R3: 1, Reading: R3, Value: 1, Unit:
2017.05.16 22:10:20.059 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:10:20.065 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:10:20.069 5: End notify loop for ESPEasy_ESPEasy00_R3
2017.05.16 22:10:20.071 4: ESPEasy ESPBridge_192.168.178.240_29342: Closing tcp session.
2017.05.16 22:10:26.094 4: Connection accepted from ESPBridge_192.168.178.240_19428
2017.05.16 22:10:26.099 4: ESPEasy ESPBridge_192.168.178.240_19428: Peer address accepted
2017.05.16 22:10:26.100 5: ESPEasy ESPBridge_192.168.178.240_19428: Received header: {'Authorization' => 'Basic ***** ','Host' => '192.168.178.221','Connection' => 'close','Content-Length' => '212'}
2017.05.16 22:10:26.101 5: ESPEasy ESPBridge_192.168.178.240_19428: Received content: {"module":"ESPEasy","version":"1.02","data":{"ESP":{"name":"ESPEasy00","unit":1,"version":9,"build":147,"sleep":0,"ip":"192.168.178.240"},"SENSOR":{"0":{"deviceName":"R4","valueName":"R4","type":1,"value":"1"}}}}
2017.05.16 22:10:26.102 2: ESPEasy ESPBridge_192.168.178.240_19428: No basic authentication active but credentials received
2017.05.16 22:10:26.103 4: ESPEasy ESPBridge_192.168.178.240_19428: Send http close '200 OK'
2017.05.16 22:10:26.104 5: ESPEasy ESPBridge_192.168.178.240_19428: Dispatch: ESPEasy00_R4::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R4||1||1
2017.05.16 22:10:26.105 5: ESPBridge: dispatch ESPEasy00_R4::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R4||1||1
2017.05.16 22:10:26.106 5: ESPEasy ESPEasy_ESPEasy00_R4: Received: ESPEasy00_R4::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R4||1||1
2017.05.16 22:10:26.110 4: ESPEasy ESPEasy_ESPEasy00_R4: R4: 1
2017.05.16 22:10:26.110 5: ESPEasy ESPEasy_ESPEasy00_R4: Internals: unit:1 sleep:0 build:147 version:9
2017.05.16 22:10:26.112 5: Starting notify loop for ESPEasy_ESPEasy00_R4, 1 event(s), first is R4: 1
2017.05.16 22:10:26.114 4: DbLog logdb -> ################################################################
2017.05.16 22:10:26.114 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:10:26.114 4: DbLog logdb -> ################################################################
2017.05.16 22:10:26.115 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R4
2017.05.16 22:10:26.115 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R4 , Event: R4: 1
2017.05.16 22:10:26.116 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:10:26, Device: ESPEasy_ESPEasy00_R4, Type: ESPEASY, Event: R4: 1, Reading: R4, Value: 1, Unit:
2017.05.16 22:10:26.121 4: DbLog logdb -> ################################################################
2017.05.16 22:10:26.121 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:10:26.122 4: DbLog logdb -> ################################################################
2017.05.16 22:10:26.122 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:10:26.147 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:10:26.147 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:10:26.148 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:10:26, Device: ESPEasy_ESPEasy00_R4, Type: ESPEASY, Event: R4: 1, Reading: R4, Value: 1, Unit:
2017.05.16 22:10:26.152 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:10:26.158 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:10:26.162 5: End notify loop for ESPEasy_ESPEasy00_R4
2017.05.16 22:10:26.164 4: ESPEasy ESPBridge_192.168.178.240_19428: Closing tcp session.
2017.05.16 22:11:06.083 4: Connection accepted from ESPBridge_192.168.178.240_15597
2017.05.16 22:11:06.089 4: ESPEasy ESPBridge_192.168.178.240_15597: Peer address accepted
2017.05.16 22:11:06.090 5: ESPEasy ESPBridge_192.168.178.240_15597: Received header: {'Content-Length' => '212','Connection' => 'close','Authorization' => 'Basic ***** ','Host' => '192.168.178.221'}
2017.05.16 22:11:06.090 5: ESPEasy ESPBridge_192.168.178.240_15597: Received content: {"module":"ESPEasy","version":"1.02","data":{"ESP":{"name":"ESPEasy00","unit":1,"version":9,"build":147,"sleep":0,"ip":"192.168.178.240"},"SENSOR":{"0":{"deviceName":"R1","valueName":"R1","type":1,"value":"1"}}}}
2017.05.16 22:11:06.092 2: ESPEasy ESPBridge_192.168.178.240_15597: No basic authentication active but credentials received
2017.05.16 22:11:06.093 4: ESPEasy ESPBridge_192.168.178.240_15597: Send http close '200 OK'
2017.05.16 22:11:06.094 5: ESPEasy ESPBridge_192.168.178.240_15597: Dispatch: ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||1||1
2017.05.16 22:11:06.095 5: ESPBridge: dispatch ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||1||1
2017.05.16 22:11:06.096 5: ESPEasy ESPEasy_ESPEasy00_R1: Received: ESPEasy00_R1::192.168.178.240::1::1::1::i||unit||1||0|||i||sleep||0||0|||i||build||147||0|||i||version||9||0|||r||R1||1||1
2017.05.16 22:11:06.099 4: ESPEasy ESPEasy_ESPEasy00_R1: R1: 1
2017.05.16 22:11:06.099 5: ESPEasy ESPEasy_ESPEasy00_R1: Internals: unit:1 sleep:0 build:147 version:9
2017.05.16 22:11:06.101 5: Starting notify loop for ESPEasy_ESPEasy00_R1, 1 event(s), first is R1: 1
2017.05.16 22:11:06.103 4: DbLog logdb -> ################################################################
2017.05.16 22:11:06.103 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:11:06.103 4: DbLog logdb -> ################################################################
2017.05.16 22:11:06.104 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R1
2017.05.16 22:11:06.104 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R1 , Event: R1: 1
2017.05.16 22:11:06.105 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:11:06, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: R1: 1, Reading: R1, Value: 1, Unit:
2017.05.16 22:11:06.110 4: DbLog logdb -> ################################################################
2017.05.16 22:11:06.110 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:11:06.111 4: DbLog logdb -> ################################################################
2017.05.16 22:11:06.111 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:11:06.135 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:11:06.136 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:11:06.137 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:11:06, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: R1: 1, Reading: R1, Value: 1, Unit:
2017.05.16 22:11:06.141 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:11:06.147 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:11:06.155 5: End notify loop for ESPEasy_ESPEasy00_R1
2017.05.16 22:11:06.157 4: ESPEasy ESPBridge_192.168.178.240_15597: Closing tcp session.
2017.05.16 22:11:09.739 4: ESPEasy ESPEasy_ESPEasy00_R1: set statusRequest
2017.05.16 22:11:09.743 5: Starting notify loop for ESPEasy_ESPEasy00_R1, 1 event(s), first is presence: present
2017.05.16 22:11:09.745 4: DbLog logdb -> ################################################################
2017.05.16 22:11:09.745 4: DbLog logdb -> ###              start of new Logcycle                       ###
2017.05.16 22:11:09.746 4: DbLog logdb -> ################################################################
2017.05.16 22:11:09.746 4: DbLog logdb -> amount of events received: 1 for device: ESPEasy_ESPEasy00_R1
2017.05.16 22:11:09.747 4: DbLog logdb -> check Device: ESPEasy_ESPEasy00_R1 , Event: presence: present
2017.05.16 22:11:09.748 4: DbLog logdb -> added event - Timestamp: 2017-05-16 22:11:09, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: presence: present, Reading: presence, Value: present, Unit:
2017.05.16 22:11:09.752 4: DbLog logdb -> ################################################################
2017.05.16 22:11:09.753 4: DbLog logdb -> ###         New database processing cycle - synchronous      ###
2017.05.16 22:11:09.753 4: DbLog logdb -> ################################################################
2017.05.16 22:11:09.753 4: DbLog logdb -> DbLogType is: History
2017.05.16 22:11:09.778 5: DbLog logdb -> Primary Key used in fhem.history: none
2017.05.16 22:11:09.779 5: DbLog logdb -> Primary Key used in fhem.current: none
2017.05.16 22:11:09.779 4: DbLog logdb -> processing event Timestamp: 2017-05-16 22:11:09, Device: ESPEasy_ESPEasy00_R1, Type: ESPEASY, Event: presence: present, Reading: presence, Value: present, Unit:
2017.05.16 22:11:09.783 4: DbLog logdb -> 1 of 1 events inserted into table history
2017.05.16 22:11:09.789 5: DbLog logdb -> DbLog_Push Returncode: 0
2017.05.16 22:11:09.797 5: End notify loop for ESPEasy_ESPEasy00_R1
2017.05.16 22:11:09.798 4: ESPEasy ESPEasy_ESPEasy00_R1: presence: present
2017.05.16 22:11:09.799 5: ESPEasy ESPEasy_ESPEasy00_R1: Start internalTimer +64 => 2017-05-16 22:12:14
...


Vielen Dank
Gruß
Thomas

dev0

#3
Zitat von: thm12345 am 16 Mai 2017, 22:21:51

2017.05.16 22:09:21.254 5: Cmd: >set ESPEasy_ESPEasy00_R1 on<
2017.05.16 22:09:21.384 5: Received content: ... "SENSOR":{"0":{"deviceName":"R1","valueName":"R1","type":10,"value":"0"}}}}
2017.05.16 22:10:06.132 5: Received content: ... "SENSOR":{"0":{"deviceName":"R1","valueName":"R1","type":1,"value":"0"}}}}


Kurz:
Das pcfgpio Plugin sendet unterschiedliche Sensor Types.

Lang:
Das ESPEasy Modul ersetzt beim Sensor Type 10 (=switch) die Werte 0/1 durch off/on, wenn das Attribut readingSwitchText nicht oder auf 1 gesetzt ist. Das ESPEasy Plugin pcfgpio sendet nach dem Schalten eines Ports den korrekten Sensor Type 10 (=switch) mit dem Zustand. Dadurch werden sie als off/on dargestellt.
Die Werte, die regelmäßig übertragen werden (festgelegt durch das Delay im ESP Device), werden vom Plugin aber mit dem Sensor Type 1 (=single) gekennzeichnet. Die Werte dieses Sensor Types werden vom Modul aber nicht durch off/on ersetzt, da sich typischerweise nicht nur 0 und 1 enthalten, sondern zB. auch Temperaturen, etc...

Lösung:
Den Plugin oder ESPEasy Maintainer bitten dieses Verhalten zu korrigieren: https://github.com/letscontrolit/ESPEasy/issues

Workaround:
Das Attribut readingSwitchText auf 0 setzen, um die Umsetzung auf off/on abzuschalten. Die Umsetzung auf off/on könntest Du dann mit dem Modul readingsChange machen, wenn Du nicht mit 0/1 hantieren möchtest.

thm12345

Danke für die schnelle Reaktion. Ich schaue mir das mal heute oder morgen an und gebe ein kurzes Feedback.

thm12345

Hallo, es funktioniert mit readingSwitchText=0 wie gewünscht. Da ich derzeit nur einen ESP-01 habe (1MB), verwende ich "nur" die ältere Version ESPEasy 147 RC8. Demnächt fliegt ein ESP mit 4MB ein, da teste ich das ganze mal mit der aktuellen Version 2. Eventuell ist da das Problem mit den Sensor Types ja gelöst. Ansonsten melde ich mich dann bei den Entwicklern...