MQTT_GENERIC_BRIDGE generiert massenhaft incoming-count Events. Rekursion?

nuccleon · 02 März 2019, 20:46:53

Hallo zusammen,

ich verwende mosquitto zusammen mit MQTT2_CLIENT und MQTT_GENERIC_BRIDE.

MQTT2_CLIENT habe ich so konfiguriert, dass er sich nur auf für fhem interesannte topics subscribed:

Code Auswählen

attr mqtt2 subscriptions ebusd/# espeasy/# fhem/#

MQTT_GENERIC_BRIDE verwendet als base topic eines dieser subscriptions

Code Auswählen

attr MQTT2_bridge globalDefaults base={"fhem/$device"} retain=0

Nun habe ich mit HM_Sirene_Sen_01 (HM-Sec-Sir-WM) ein Device welches sowohl subscribed ist, als auch published:

Code Auswählen


attr HM_Sirene_Sen_01 mqttPublish state:topic={"$base/$name"} state:retain=1
attr HM_Sirene_Sen_01 mqttSubscribe state:stopic={"$base/$name/set"} state:expression={$value="off"}

Jetzt habe ich das Problem, dass beim publishen von z.B. fhem/HM_Sirene_Sen_01/state massenhaft von incoming-count Events auftreten.
Ich werde den Verdacht nicht los, dass hier irgend eine Art von Rekursion vorliegt (die aber seltsamerweise dann irgendwand endet).
Aus dem Log mit verbose 5 werde ich auch nicht so richtig schlaut.

Jemand ne Idee?

Hier die vollständigen Lists und das Log:

List MQTT_GENERIC_BRIDGE

Code Auswählen


Internals:
   DEF        mqtt ftk.*,HM_Sirene.*
   FUUID      5c67db5d-f33f-3b45-ce09-6326130e358992d0
   IODev      mqtt2
   NAME       MQTT2_bridge
   NR         206
   NTFY_ORDER 50-MQTT2_bridge
   STATE      dev: 14 in: 217611 out: 687
   TYPE       MQTT_GENERIC_BRIDGE
   devspec    ftk.*,HM_Sirene.*
   prefix     mqtt
   CHANGED:
     incoming-count: 217494
     incoming-count: 217495
     incoming-count: 217496
     incoming-count: 217497
     incoming-count: 217498
     incoming-count: 217499
     incoming-count: 217500
     incoming-count: 217501
     incoming-count: 217502
     incoming-count: 217503
     incoming-count: 217504
     incoming-count: 217505
     incoming-count: 217506
     incoming-count: 217507
     incoming-count: 217508
     incoming-count: 217509
     incoming-count: 217510
     incoming-count: 217511
     incoming-count: 217512
     incoming-count: 217513
     incoming-count: 217514
     incoming-count: 217515
     incoming-count: 217516
     incoming-count: 217517
     incoming-count: 217518
     incoming-count: 217519
     incoming-count: 217520
     incoming-count: 217521
     incoming-count: 217522
     incoming-count: 217523
     incoming-count: 217524
     incoming-count: 217525
     incoming-count: 217526
     incoming-count: 217527
     incoming-count: 217528
     incoming-count: 217529
     incoming-count: 217530
     incoming-count: 217531
     incoming-count: 217532
     incoming-count: 217533
     incoming-count: 217534
     incoming-count: 217535
     incoming-count: 217536
     incoming-count: 217537
     incoming-count: 217538
     incoming-count: 217539
     incoming-count: 217540
     incoming-count: 217541
     incoming-count: 217542
     incoming-count: 217543
     incoming-count: 217544
     incoming-count: 217545
     incoming-count: 217546
     incoming-count: 217547
     incoming-count: 217548
     incoming-count: 217549
     incoming-count: 217550
     incoming-count: 217551
     incoming-count: 217552
     incoming-count: 217553
     incoming-count: 217554
     incoming-count: 217555
     incoming-count: 217556
     incoming-count: 217557
     incoming-count: 217558
     incoming-count: 217559
     incoming-count: 217560
     incoming-count: 217561
     incoming-count: 217562
     incoming-count: 217563
     incoming-count: 217564
     incoming-count: 217565
     incoming-count: 217566
     incoming-count: 217567
     incoming-count: 217568
     incoming-count: 217569
     incoming-count: 217570
     incoming-count: 217571
     incoming-count: 217572
     incoming-count: 217573
     incoming-count: 217574
     incoming-count: 217575
     incoming-count: 217576
     incoming-count: 217577
     incoming-count: 217578
     incoming-count: 217579
     incoming-count: 217580
     incoming-count: 217581
     incoming-count: 217582
     incoming-count: 217583
     incoming-count: 217584
     incoming-count: 217585
     incoming-count: 217586
     incoming-count: 217587
     incoming-count: 217588
     incoming-count: 217589
     incoming-count: 217590
     incoming-count: 217591
     incoming-count: 217592
     incoming-count: 217593
     incoming-count: 217594
     incoming-count: 217595
     incoming-count: 217596
     incoming-count: 217597
     incoming-count: 217598
     incoming-count: 217599
     incoming-count: 217600
     incoming-count: 217601
     incoming-count: 217602
     incoming-count: 217603
     incoming-count: 217604
     incoming-count: 217605
     incoming-count: 217606
     incoming-count: 217607
     incoming-count: 217608
     incoming-count: 217609
     incoming-count: 217610
     incoming-count: 217611
   READINGS:
     2019-03-01 22:13:28   device-count    14
     2019-03-02 20:23:46   incoming-count  217611
     2019-03-02 20:21:37   outgoing-count  687
     2019-03-02 20:21:37   transmission-state outgoing publish sent
     2019-02-27 19:30:58   updated-reading-count 0
     2019-03-02 17:53:17   updated-set-count 43
   devices:
     :global:
       :defaults:
         pub:base   {"fhem/$device"}
         pub:retain 0
         sub:base   {"fhem/$device"}
         sub:retain 0
     HM_Sirene_Arm:
       :publish:
         state:
           expression {if($value eq "100"){$value="on"}elsif($value eq "127.5"){$value="blocked"}elsif($value eq "0"){$value="off"}else{$value=$value}}
           last       1551545594.83692
           mode       R
           retain     1
           topic      {"$base/$name"}
       :subscribe:
         HASH(0x316c090)
     HM_Sirene_Panic:
       :publish:
         state:
           last       1551545598.14899
           mode       R
           retain     1
           topic      {"$base/$name"}
       :subscribe:
         HASH(0x316c0c0)
     HM_Sirene_Sen_01:
       :publish:
         state:
           last       1551554497.91241
           mode       R
           retain     1
           topic      {"$base/$name"}
       :subscribe:
         HASH(0x3169350)
     HM_Sirene_Sen_02:
       :publish:
         state:
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_eg0_wohnzimmer:
       :publish:
         state:
           last       1551510933.72269
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_eg1_wohnzimmer:
       :publish:
         state:
           last       1551510252.51497
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_eg2_haustuere:
       :publish:
         state:
           last       1551549808.70324
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_eg3_wc:
       :publish:
         state:
           last       1551458216.75904
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_eg4_kueche:
       :publish:
         state:
           last       1551472182.17761
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_eg5_kueche:
       :publish:
         state:
           last       1551522501.60573
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_garden_gate:
       :publish:
         state:
           last       1551544288.87237
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_kg0_hobbyraum:
       :publish:
         state:
           last       1551459258.81798
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_kg1_technikraum:
       :publish:
         state:
           last       1551470239.41909
           mode       R
           retain     1
           topic      {"$base/$name"}
     ftk_og0_bad:
       :publish:
         state:
           last       1551516411.23228
           mode       R
           retain     1
           topic      {"$base/$name"}
   globalDeviceExcludes:
   globalReadingExcludes:
   globalTypeExcludes:
     pub:
       FHEMWEB    *
       Global     *
       MQTT       transmission-state
       MQTT2_CLIENT *
       MQTT2_DEVICE *
       MQTT_BRIDGE transmission-state
       MQTT_DEVICE transmission-state
       MQTT_GENERIC_BRIDGE *
       telnet     *
     sub:
       FHEMWEB    *
       Global     *
       MQTT       transmission-state
       MQTT2_CLIENT *
       MQTT2_DEVICE *
       MQTT_BRIDGE transmission-state
       MQTT_DEVICE transmission-state
       MQTT_GENERIC_BRIDGE *
       telnet     *
   subscribe:
Attributes:
   IODev      mqtt2
   globalDefaults base={"fhem/$device"} retain=0
   globalTypeExclude MQTT2_CLIENT MQTT2_DEVICE:*
   group      MQTT
   stateFormat dev: device-count in: incoming-count out: outgoing-count
   verbose    5

List MQTT2_CLIENT

Code Auswählen


Internals:
   BUF        
   DEF        raspberrypi:1883
   DeviceName raspberrypi:1883
   FD         4
   FUUID      5c58b6a1-f33f-3b45-a08f-45731ca8af081f59
   NAME       mqtt2
   NR         75
   PARTIAL    
   STATE      opened
   TYPE       MQTT2_CLIENT
   WBCallback 
   clientId   mqtt2
   lastMsgTime 1551554584.01785
   nextOpenDelay 5
   READINGS:
     2019-03-01 22:13:28   state           opened
Attributes:
   autocreate 0
   group      MQTT
   subscriptions ebusd/# espeasy/# fhem/#
   verbose    5

List HM_Sirene_Sen_01

Code Auswählen


Internals:
   DEF        54A69301
   FUUID      5c5f055c-f33f-3b45-be0f-e9fb240c5a7ac58b
   LASTInputDev mqtt2
   MSGCNT     14
   NAME       HM_Sirene_Sen_01
   NOTIFYDEV  global
   NR         187
   NTFY_ORDER 50-HM_Sirene_Sen_01
   STATE      off
   TYPE       CUL_HM
   chanNo     01
   device     HM_Sirene
   mqtt2_MSGCNT 14
   mqtt2_TIME 2019-03-02 17:52:19
   peerList   ftk_eg0_wohnzimmer,ftk_eg5_kueche,ftk_eg4_kueche,ftk_eg2_haustuere,ftk_eg1_wohnzimmer,ftk_kg0_hobbyraum,ftk_kg1_technikraum,ftk_eg3_wc,
   READINGS:
     2019-03-02 20:21:37   CommandAccepted yes
     2019-03-01 18:22:47   R-ftk_eg0_wohnzimmer_chn-01-lgActionType jmpToTarget
     2019-03-01 18:22:47   R-ftk_eg0_wohnzimmer_chn-01-shActionType jmpToTarget
     2019-03-01 18:22:53   R-ftk_eg1_wohnzimmer_chn-01-lgActionType jmpToTarget
     2019-03-01 18:22:53   R-ftk_eg1_wohnzimmer_chn-01-shActionType jmpToTarget
     2019-03-01 18:22:51   R-ftk_eg2_haustuere_chn-01-lgActionType jmpToTarget
     2019-03-01 18:22:51   R-ftk_eg2_haustuere_chn-01-shActionType jmpToTarget
     2019-03-01 18:22:57   R-ftk_eg3_wc_chn-01-lgActionType jmpToTarget
     2019-03-01 18:22:57   R-ftk_eg3_wc_chn-01-shActionType jmpToTarget
     2019-03-01 18:22:50   R-ftk_eg4_kueche_chn-01-lgActionType jmpToTarget
     2019-03-01 18:22:50   R-ftk_eg4_kueche_chn-01-shActionType jmpToTarget
     2019-03-01 18:22:48   R-ftk_eg5_kueche_chn-01-lgActionType jmpToTarget
     2019-03-01 18:22:48   R-ftk_eg5_kueche_chn-01-shActionType jmpToTarget
     2019-03-01 18:22:54   R-ftk_kg0_hobbyraum_chn-01-lgActionType jmpToTarget
     2019-03-01 18:22:54   R-ftk_kg0_hobbyraum_chn-01-shActionType jmpToTarget
     2019-03-01 18:22:56   R-ftk_kg1_technikraum_chn-01-lgActionType jmpToTarget
     2019-03-01 18:22:56   R-ftk_kg1_technikraum_chn-01-shActionType jmpToTarget
     2019-02-16 12:13:55   R-sign          off
     2019-03-01 18:22:39   RegL_01.         00:00 08:00 30:06 57:24 AB:40
     2019-03-01 18:22:47   RegL_03.ftk_eg0_wohnzimmer_chn-01  00:00 02:00 03:00 04:01 05:B4 06:00 07:6C 08:00 09:FF 0A:01 0B:13 0C:33 82:00 83:00 84:01 85:B4 86:00 87:6C 88:00 89:FF 8A:21 8B:13 8C:33
     2019-03-01 18:22:53   RegL_03.ftk_eg1_wohnzimmer_chn-01  00:00 02:00 03:00 04:01 05:B4 06:00 07:6C 08:00 09:FF 0A:01 0B:13 0C:33 82:00 83:00 84:01 85:B4 86:00 87:6C 88:00 89:FF 8A:21 8B:13 8C:33
     2019-03-01 18:22:51   RegL_03.ftk_eg2_haustuere_chn-01  00:00 02:00 03:00 04:01 05:B4 06:00 07:6C 08:00 09:FF 0A:01 0B:13 0C:33 82:00 83:00 84:01 85:B4 86:00 87:6C 88:00 89:FF 8A:21 8B:13 8C:33
     2019-03-01 18:22:57   RegL_03.ftk_eg3_wc_chn-01  00:00 02:00 03:00 04:01 05:B4 06:00 07:6C 08:00 09:FF 0A:01 0B:13 0C:33 82:00 83:00 84:01 85:B4 86:00 87:6C 88:00 89:FF 8A:21 8B:13 8C:33
     2019-03-01 18:22:50   RegL_03.ftk_eg4_kueche_chn-01  00:00 02:00 03:00 04:01 05:B4 06:00 07:6C 08:00 09:FF 0A:01 0B:13 0C:33 82:00 83:00 84:01 85:B4 86:00 87:6C 88:00 89:FF 8A:21 8B:13 8C:33
     2019-03-01 18:22:48   RegL_03.ftk_eg5_kueche_chn-01  00:00 02:00 03:00 04:01 05:B4 06:00 07:6C 08:00 09:FF 0A:01 0B:13 0C:33 82:00 83:00 84:01 85:B4 86:00 87:6C 88:00 89:FF 8A:21 8B:13 8C:33
     2019-03-01 18:22:54   RegL_03.ftk_kg0_hobbyraum_chn-01  00:00 02:00 03:00 04:01 05:B4 06:00 07:6C 08:00 09:FF 0A:01 0B:13 0C:33 82:00 83:00 84:01 85:B4 86:00 87:6C 88:00 89:FF 8A:21 8B:13 8C:33
     2019-03-01 18:22:56   RegL_03.ftk_kg1_technikraum_chn-01  00:00 02:00 03:00 04:01 05:B4 06:00 07:6C 08:00 09:FF 0A:01 0B:13 0C:33 82:00 83:00 84:01 85:B4 86:00 87:6C 88:00 89:FF 8A:21 8B:13 8C:33
     2019-03-02 20:21:37   deviceMsg       off (to hm_vccu)
     2019-03-02 20:21:37   level           0
     2019-03-02 20:21:37   pct             0
     2019-03-01 18:22:41   peerList        ftk_eg0_wohnzimmer,ftk_eg5_kueche,ftk_eg4_kueche,ftk_eg2_haustuere,ftk_eg1_wohnzimmer,ftk_kg0_hobbyraum,ftk_kg1_technikraum,ftk_eg3_wc,
     2019-03-02 20:21:37   recentStateType ack
     2019-03-02 20:21:37   state           off
     2019-03-02 20:21:37   timedOn         off
     2019-03-02 20:21:37   trigLast        fhem:02
     2019-03-02 08:15:33   trig_ftk_eg0_wohnzimmer Closed_35
     2019-03-02 08:04:12   trig_ftk_eg1_wohnzimmer Closed_15
     2019-03-02 19:03:28   trig_ftk_eg2_haustuere Closed_107
     2019-03-01 17:36:57   trig_ftk_eg3_wc Closed_34
     2019-03-01 21:29:42   trig_ftk_eg4_kueche Closed_75
     2019-03-02 11:28:21   trig_ftk_eg5_kueche Closed_217
     2019-03-01 17:54:20   trig_ftk_kg0_hobbyraum Closed_8
     2019-03-01 20:57:27   trig_ftk_kg1_technikraum Closed_16
   helper:
     dlvl       C8
     dlvlCmd    ++A011AFFE0054A6930201C80000
     peerIDsRaw ,59B32401,59B32E01,59ADCC01,59B34201,59B33401,68DEF701,68DED001,68CDB701,00000000
     regLst     ,1,3p
     expert:
       def        1
       det        0
       raw        1
       tpl        0
     regCollect:
     role:
       chn        1
     shadowReg:
     tmpl:
Attributes:
   model      HM-Sec-Sir-WM
   mqttPublish state:topic={"$base/$name"} state:retain=1
   mqttSubscribe state:stopic={"$base/$name/set"} state:expression={$value="off"}
   peerIDs    00000000,59ADCC01,59B32401,59B32E01,59B33401,59B34201,68CDB701,68DED001,68DEF701,
   room       Alarmanlage
   userattr   mqttAlias:textField-long mqttDefaults:textField-long mqttDisable:both,incoming,outgoing mqttForward:all,none mqttPublish:textField-long mqttSubscribe:textField-long

Log mit verbose 5

Code Auswählen


2019.03.02 20:21:37 5 : MQTT_GENERIC_BRIDGE:DEBUG:> [MQTT2_bridge] publish: fhem/HM_Sirene_Sen_01/state => set_on (qos: 0, retain: 1)
2019.03.02 20:21:37 5 : mqtt2: sending PUBLISH 1#(0)(27)fhem/HM_Sirene_Sen_01/stateset_on
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217354
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217355
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217356
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217357
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217358
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217359
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217360
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217361
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217362
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217363
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217364
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217365
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217366
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217367
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217368
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217369
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217370
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217371
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217372
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217373
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217374
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217375
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217376
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217377
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217378
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217379
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217380
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217381
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217382
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217383
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217384
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217385
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217386
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217387
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217388
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217389
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217390
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217391
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217392
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217393
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217394
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217395
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217396
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217397
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217398
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217399
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217400
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217401
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217402
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217403
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217404
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217405
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217406
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217407
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217408
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217409
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217410
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217411
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217412
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217413
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217414
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217415
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217416
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217417
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217418
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217419
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217420
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217421
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217422
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217423
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217424
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217425
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217426
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217427
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217428
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217429
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217430
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217431
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217432
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217433
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217434
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217435
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217436
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217437
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217438
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217439
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217440
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217441
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217442
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217443
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217444
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217445
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217446
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217447
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217448
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217449
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217450
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217451
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217452
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217453
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217454
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217455
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217456
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217457
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217458
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217459
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217460
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217461
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217462
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217463
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217464
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217465
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217466
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217467
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217468
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217469
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217470
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217471
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217472
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217473
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217474
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217475
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217476
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217477
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217478
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217479
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217480
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217481
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217482
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217483
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217484
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217485
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217486
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217487
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217488
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217489
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217490
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217491
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217492
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge transmission-state: outgoing publish sent
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge outgoing-count: 686
2019.03.02 20:21:37 3 : CUL_HM set HM_Sirene_Sen_01 on
2019.03.02 20:21:37 5 : mqtt2: received PUBLISH (0)(27)fhem/HM_Sirene_Sen_01/stateset_on
2019.03.02 20:21:37 5 : mqtt2: dispatch mqtt2\000fhem/HM_Sirene_Sen_01/state\000set_on
2019.03.02 20:21:37 5 : MQTT_GENERIC_BRIDGE: [MQTT2_bridge] Parse (MQTT2_CLIENT : 'mqtt2'): Msg: fhem/HM_Sirene_Sen_01/state => set_on
2019.03.02 20:21:37 5 : MQTT_GENERIC_BRIDGE:DEBUG:> [MQTT2_bridge] publish: fhem/HM_Sirene_Sen_01/state => off (qos: 0, retain: 1)
2019.03.02 20:21:37 5 : mqtt2: sending PUBLISH 1 (0)(27)fhem/HM_Sirene_Sen_01/stateoff
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 217493
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge transmission-state: outgoing publish sent
2019-03-02 20:21:37 MQTT_GENERIC_BRIDGE MQTT2_bridge outgoing-count: 687
2019.03.02 20:21:37 5 : mqtt2: received PUBLISH (0)(27)fhem/HM_Sirene_Sen_01/stateoff
2019.03.02 20:21:37 5 : mqtt2: dispatch mqtt2\000fhem/HM_Sirene_Sen_01/state\000off
2019.03.02 20:21:37 5 : MQTT_GENERIC_BRIDGE: [MQTT2_bridge] Parse (MQTT2_CLIENT : 'mqtt2'): Msg: fhem/HM_Sirene_Sen_01/state => off
2019.03.02 20:21:38 5 : mqtt2: received PUBLISH (0)(19)ebusd/global/uptime2148199
2019.03.02 20:21:38 5 : mqtt2: dispatch mqtt2\000ebusd/global/uptime\0002148199
2019.03.02 20:21:38 5 : MQTT_GENERIC_BRIDGE: [MQTT2_bridge] Parse (MQTT2_CLIENT : 'mqtt2'): Msg: ebusd/global/uptime => 2148199

hexenmeister · 03 März 2019, 00:03:00

Du hast vermutlich eine Nachrichtenschleife erzeugt. Schau dir mit einem MQTT-Client (z.B. MQTTSpy), was da durch die Leitung geht.
Probiere an dem Device ggf. mqttForward auf none zu setzen.

nuccleon · 03 März 2019, 10:04:01

Danke schon mal für die Antwort und den Support!

Also ich hab mich jetzt mal mit MQTTfx auf # subscribed. Außer

Code Auswählen

fhem/HM_Sirene_Sen_01/state kommt nichts. Also wirklich rein gar nichts! Das bestätigt ja aber in Prinzip auch schon der Log aus dem ersten Post mit verbose 5. Am MQTT2_CLIENT kommt mehr oder weniger nichts an, die Bridge bekommt aber "1 Mio" Events...
Ich vermute die Nachrichtenschleife daher eher innerhalb von FHEM :-/

mqttForward none in HM_Sirene_Sen_01 macht keinen Unterschied.

Ich bin jetzt kein Perl Held. Aber ich kann noch ein paar Versuche und Ergebnisse beisteuern, wenns hilft!

hexenmeister · 03 März 2019, 22:42:49

Noch verstehe ich gar nichts. Man sieht, dass der Counter hoch gezählt wird, aber nicht die dazu gehörenden Meldung über die Messages.
Kannst Du mal im Generic-Bridge-Modul die Zeile 2647 aktivieren, also das '#' Zeichen davor entfernen:

Code Auswählen

Log3($hash->{NAME},1,"MQTT_GENERIC_BRIDGE:DEBUG:> [$hash->{NAME}] onmessage: $topic => $message");

nuccleon · 04 März 2019, 19:05:26

Bitteschön, aber ich befürchte, daraus wird man nicht schlauer :-/

Code Auswählen


2019.03.04 19:00:19 5 : MQTT_GENERIC_BRIDGE:DEBUG:> [MQTT2_bridge] publish: fhem/HM_Sirene_Sen_01/state => set_off (qos: 0, retain: 1)
2019.03.04 19:00:19 5 : mqtt2: sending PUBLISH 1$(0)(27)fhem/HM_Sirene_Sen_01/stateset_off
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 423
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 424
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 425
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 426
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 427
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 428
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 429
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 430
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 431
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 432
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 433
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 434
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 435
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 436
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 437
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 438
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 439
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 440
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 441
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 442
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 443
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 444
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 445
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 446
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 447
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 448
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 449
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 450
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 451
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 452
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 453
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 454
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 455
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 456
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 457
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 458
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 459
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 460
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 461
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 462
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 463
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 464
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 465
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 466
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 467
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 468
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 469
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 470
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 471
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 472
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 473
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 474
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 475
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 476
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 477
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 478
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 479
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 480
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 481
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 482
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 483
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 484
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 485
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 486
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 487
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 488
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 489
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 490
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 491
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 492
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 493
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 494
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 495
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 496
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 497
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 498
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 499
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 500
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 501
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 502
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 503
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 504
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 505
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 506
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 507
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 508
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 509
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 510
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 511
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 512
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 513
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 514
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 515
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 516
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 517
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 518
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 519
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 520
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 521
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 522
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 523
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 524
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 525
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge transmission-state: outgoing publish sent
2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge outgoing-count: 27
2019-03-04 19:00:20 CUL_HM HM_Sirene_Sen_01 set_off
2019.03.04 19:00:20 3 : CUL_HM set HM_Sirene_Sen_01 off
2019-03-04 19:00:20 CUL_HM HM_Sirene_Sen_01 trigLast: fhem:02
2019.03.04 19:00:20 5 : mqtt2: received PUBLISH (0)(27)fhem/HM_Sirene_Sen_01/stateset_off
2019.03.04 19:00:20 5 : mqtt2: dispatch mqtt2\000fhem/HM_Sirene_Sen_01/state\000set_off
2019.03.04 19:00:20 5 : MQTT_GENERIC_BRIDGE: [MQTT2_bridge] Parse (MQTT2_CLIENT : 'mqtt2'): Msg: fhem/HM_Sirene_Sen_01/state => set_off
2019.03.04 19:00:20 1 : MQTT_GENERIC_BRIDGE:DEBUG:> [MQTT2_bridge] onmessage: fhem/HM_Sirene_Sen_01/state => set_off
2019-03-04 19:00:20 CUL_HM HM_Sirene CMDs_done
2019.03.04 19:00:20 5 : MQTT_GENERIC_BRIDGE:DEBUG:> [MQTT2_bridge] publish: fhem/HM_Sirene_Sen_01/state => off (qos: 0, retain: 1)
2019.03.04 19:00:20 5 : mqtt2: sending PUBLISH 1 (0)(27)fhem/HM_Sirene_Sen_01/stateoff
2019-03-04 19:00:20 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 526
2019-03-04 19:00:20 MQTT_GENERIC_BRIDGE MQTT2_bridge transmission-state: outgoing publish sent
2019-03-04 19:00:20 MQTT_GENERIC_BRIDGE MQTT2_bridge outgoing-count: 28
2019-03-04 19:00:20 CUL_HM HM_Sirene_Sen_01 deviceMsg: off (to hm_vccu)
2019-03-04 19:00:20 CUL_HM HM_Sirene_Sen_01 level: 0
2019-03-04 19:00:20 CUL_HM HM_Sirene_Sen_01 pct: 0
2019-03-04 19:00:20 CUL_HM HM_Sirene_Sen_01 off
2019-03-04 19:00:20 CUL_HM HM_Sirene_Sen_01 timedOn: off
2019-03-04 19:00:20 CUL_HM HM_Sirene_Sen_01 active: off
2019.03.04 19:00:20 5 : mqtt2: received PUBLISH (0)(27)fhem/HM_Sirene_Sen_01/stateoff
2019.03.04 19:00:20 5 : mqtt2: dispatch mqtt2\000fhem/HM_Sirene_Sen_01/state\000off
2019.03.04 19:00:20 5 : MQTT_GENERIC_BRIDGE: [MQTT2_bridge] Parse (MQTT2_CLIENT : 'mqtt2'): Msg: fhem/HM_Sirene_Sen_01/state => off
2019.03.04 19:00:20 1 : MQTT_GENERIC_BRIDGE:DEBUG:> [MQTT2_bridge] onmessage: fhem/HM_Sirene_Sen_01/state => off

Es sieht nicht danach aus, also ob die Meldung beim Empfang getriggert wird sondern beim senden. Ziemlich verrückt das Ganze. Was mir nicht klar ist, bzw da verstehe ich einfach zu wenig von Perl, wo im Code wird denn die Meldung

Code Auswählen


2019-03-04 19:00:19 MQTT_GENERIC_BRIDGE MQTT2_bridge incoming-count: 493

überhaupt generiert??? Wenn man dem aktuellen Log glaubt, kann es onMessage ja eigentlich nicht sein.

Ich hab mal einen vollständigen Log mit global verbose 5 und der einkommentierten Zeile angehängt. Vielleicht kannst du aus dem Kontext mehr lesen.

Ich sehe, dass sich das Phänomen hier zwischen abspielt:

Code Auswählen


2019.03.04 20:11:45 5: Starting notify loop for MQTT2_bridge, 151 event(s), first is incoming-count: 549
....
2019.03.04 20:11:45 5: End notify loop for MQTT2_bridge

Der onmessage kommt erst hinterher. Das Schöne ist, ich kann es zu 100% reproduzieren

hexenmeister · 04 März 2019, 22:30:47

Ich verstehe das auch gerade nicht. Eigentlich wird das nur in 'onmessage' hochgezählt und aktualisiert. Aber danach sieht das ja uch nicht aus. Es ist schon irgendein event-loop, aber wie???
Hast Du eine Möglichkeit, mit dem akten MQTT-Modul auszuprobieren? Kann man parallel zu MQTT2_CLIENT betreiben.
Passiert das auch, wenn man irgendein anderes Device anstatt der Sirene nimmt?

nuccleon · 05 März 2019, 07:27:21

Ja, es passiert auch mit anderen Devices, z.B. mit wenn man bei einem Dummy 'state' published. Das dummy hat nicht mal subscriptions hat.

Code Auswählen


Internals:
   FUUID      5c602260-f33f-3b45-20f4-91994379859906f8
   NAME       ftk_garden_gate
   NR         191
   STATE      closed
   TYPE       dummy
   READINGS:
     2019-03-05 07:19:02   contact         closed
     2019-03-05 07:19:02   state           closed
     2019-03-05 07:19:02   trigger_cnt     4
     2019-03-05 07:19:02   trigger_cnt_close 2
     2019-03-05 07:19:02   trigger_cnt_open 2
   helper:
     bm:
       dummy_Set:
         cnt        132
         dmx        -1000
         dtot       0
         dtotcnt    0
         mTS        04.03. 21:53:07
         max        1.50410294532776
         tot        1.73534250259399
         mAr:
           HASH(0x31fb5a0)
           ftk_garden_gate
           open
Attributes:
   event-on-change-reading .*
   group      PLC
   mqttPublish state:topic={"$base/$name"} state:retain=1
   room       Ftk,Hauseingang
   userattr   mqttAlias:textField-long mqttDefaults:textField-long mqttDisable:both,incoming,outgoing mqttForward:all,none mqttPublish:textField-long mqttSubscribe:textField-long

Du meinst bei der MQTT_GENERIC_BRIDGE als IODev statt dem MQTT2_CLIENT, MQTT ausprobieren?
Kann ich heute Abend mal testen.

Ich hab in meinem Setup noch ein MQTT2_DEVICE, welches ein bridgeRegexp Attribut konfiguriert hat. Auch autocreate ist bei diesem Device auf 1 (nicht aber beim MQTT2_CLIENT)

Code Auswählen


Internals:
   CID        mqtt2
   DEF        mqtt2
   DEVICETOPIC MQTT2_mqtt2
   FUUID      5c45e113-f33f-3b45-f26e-6590407c65dc31f2
   IODev      mqtt2
   NAME       MQTT2_mqtt2
   NR         39
   STATE      ???
   TYPE       MQTT2_DEVICE
   helper:
     bm:
       MQTT2_DEVICE_Get:
         cnt        1
         dmx        -1000
         dtot       0
         dtotcnt    0
         mTS        05.03. 07:27:47
         max        8.29696655273438e-05
         tot        8.29696655273438e-05
         mAr:
           HASH(0x1b94b20)
           MQTT2_mqtt2
           ?
       MQTT2_DEVICE_Set:
         cnt        7
         dmx        -1000
         dtot       0
         dtotcnt    0
         mTS        05.03. 07:27:47
         max        0.000158071517944336
         tot        0.000836372375488281
         mAr:
           HASH(0x1b94b20)
           MQTT2_mqtt2
           ?
Attributes:
   IODev      mqtt2
   autocreate 1
   bridgeRegexp [^:]+:([^/]+)/([^/]+)[/]?.*:.* "$1_$2"
[^:]+:ebusd/[^/]+[/]?.*:.* "ebusd"
   group      MQTT
   model      A_00_MQTT2_CLIENT_general_bridge
   setStateList on off

Beta-User · 05 März 2019, 10:42:23

Kannst du bitte mal die bridgeRegexp anpassen?
(beachte dazu auch meinen Post zu der GeneralBridge)

Folgendes müßte reichen:

Code Auswählen

bridgeRegexp ebusd/[^/]+[/]?.*:.* "ebusd"
Ansonsten kann es nämlich wirklich dazu kommen, dass das mehrfach durchgereicht wird, wenn die CID-Expression davor steht. Das DARF m.E. nicht sein.

nuccleon · 05 März 2019, 20:24:16

Hallo zusammen,

hier die neuesten - hoch interessanten - Erkenntnisse.
Bevor ich ins Detail gehe gleich vorab. Das Problem mit der Event Flut besteht NICHT, wenn ich als IODev der MQTT_GENERIC_BRIDGE MQTT statt MQTT2_CLIENT verwende. Es liegt wohl an der Kombination aus MQTT2_CLIENT und MQTT_GENERIC_BRIDGE :-/

Zitat von: Beta-User am 05 März 2019, 10:42:23
Folgendes müßte reichen:
Code Auswählen Erweitern
bridgeRegexp ebusd/[^/]+[/]?.*:.* "ebusd"
Ansonsten kann es nämlich wirklich dazu kommen, dass das mehrfach durchgereicht wird, wenn die CID-Expression davor steht. Das DARF m.E. nicht sein.

Bringt gar nichts. Ich habe die GeneralBridge sogar komplett gelöscht. Trotzdem Event Sturm.

Ich bin nun her gegangen und hab auf einer komplett jungfräulichen FHEM instanz ein minimal setup aufgesetzt, bestehend aus:

MQTT2_CLIENT

Code Auswählen


Internals:
   BUF        
   DEF        raspberrypi:1883
   DeviceName raspberrypi:1883
   FD         4
   FUUID      5c7ebfd2-f33f-88d3-3595-6f35017b695721d3
   NAME       mqtt2
   NR         31
   PARTIAL    
   STATE      opened
   TYPE       MQTT2_CLIENT
   WBCallback 
   clientId   sandboxpiMQTT2client
   lastMsgTime 1551813198.23705
   nextOpenDelay 5
   READINGS:
     2019-03-05 19:57:50   state           opened
Attributes:
   autocreate 0
   clientId   sandboxpi_MQTT2_client
   group      MQTT
   room       MQTT2_DEVICE
   subscriptions ebusd/# espeasy/# fhem/#

MQTT

Code Auswählen


Internals:
   CFGFN      
   DEF        raspberrypi:1883
   DeviceName raspberrypi:1883
   FD         19
   FUUID      5c7ecd81-f33f-88d3-2378-599ab70a572a9e8d
   NAME       mqtt
   NOTIFYDEV  global
   NR         177
   NTFY_ORDER 50-mqtt
   PARTIAL    
   STATE      opened
   TYPE       MQTT
   buf        
   msgid      1
   ping_received 1
   timeout    60
   READINGS:
     2019-03-05 20:27:58   connection      active
     2019-03-05 20:26:57   state           opened
   messages:
Attributes:
   room       MQTT2_DEVICE

MQTT_GENERIC_BRIDGE

Code Auswählen


Internals:
   DEF        mqtt ftk.*,HM_Sirene.*
   FUUID      5c7ec206-f33f-88d3-f5c0-a17eb58864159c90
   IODev      mqtt2
   NAME       MQTT2_bridge
   NR         56
   NTFY_ORDER 50-MQTT2_bridge
   STATE      dev: 1 in: 1018 out: 24
   TYPE       MQTT_GENERIC_BRIDGE
   devspec    ftk.*,HM_Sirene.*
   prefix     mqtt
   CHANGED:
     incoming-count: 1001
     incoming-count: 1002
     incoming-count: 1003
     incoming-count: 1004
     incoming-count: 1005
     incoming-count: 1006
     incoming-count: 1007
     incoming-count: 1008
     incoming-count: 1009
     incoming-count: 1010
     incoming-count: 1011
     incoming-count: 1012
     incoming-count: 1013
     incoming-count: 1014
     incoming-count: 1015
     incoming-count: 1016
     incoming-count: 1017
     incoming-count: 1018
   READINGS:
     2019-03-05 19:57:50   device-count    1
     2019-03-05 20:14:37   incoming-count  1018
     2019-03-05 20:14:34   outgoing-count  24
     2019-03-05 20:14:34   transmission-state outgoing publish sent
     2019-03-05 19:57:49   updated-reading-count 0
     2019-03-05 19:57:49   updated-set-count 0
   devices:
     :global:
       :defaults:
         pub:base   {"fhem/$device"}
         pub:retain 0
         sub:base   {"fhem/$device"}
         sub:retain 0
     ftk_dummy:
       :publish:
         state:
           last       1551813274.51345
           mode       R
           retain     0
           topic      {"$base/$name"}
   globalDeviceExcludes:
   globalReadingExcludes:
   globalTypeExcludes:
     pub:
       FHEMWEB    *
       Global     *
       MQTT       transmission-state
       MQTT2_CLIENT *
       MQTT2_DEVICE *
       MQTT_BRIDGE transmission-state
       MQTT_DEVICE transmission-state
       MQTT_GENERIC_BRIDGE *
       telnet     *
     sub:
       FHEMWEB    *
       Global     *
       MQTT       transmission-state
       MQTT2_CLIENT *
       MQTT2_DEVICE *
       MQTT_BRIDGE transmission-state
       MQTT_DEVICE transmission-state
       MQTT_GENERIC_BRIDGE *
       telnet     *
Attributes:
   IODev      mqtt2
   disable    0
   globalDefaults base={"fhem/$device"} retain=0
   globalTypeExclude MQTT2_CLIENT MQTT2_DEVICE:*
   group      MQTT
   room       MQTT2_DEVICE
   stateFormat dev: device-count in: incoming-count out: outgoing-count

DUMMY

Code Auswählen


Internals:
   FUUID      5c7ec610-f33f-88d3-2750-0e2e92492160b941
   NAME       ftk_dummy
   NR         57
   STATE      open
   TYPE       dummy
   READINGS:
     2019-03-05 20:14:34   state           open
Attributes:
   group      MQTT
   mqttPublish state:topic={"$base/$name"} state:retain=0
   room       MQTT2_DEVICE
   userattr   mqttAlias:textField-long mqttDefaults:textField-long mqttDisable:both,incoming,outgoing mqttForward:all,none mqttPublish:textField-long mqttSubscribe:textField-long

Indem Moment wo ich über die FHEM commandline

Code Auswählen

set ftk_dummy open eingebe - also das publishen von state triggere, geht der EVENT Sturm los.
Mach ich das Ganze zwei mal direkt hintereinander, habe ich beim Ersten set die vielen EVENTS und beim Zweiten set (ACHTUNG) keine Auffälligkeiten.
Lasse ich mir für das zweite set mehr Zeit, bekomme ich auch beim zweiten set eine Vielzahl von Events. Je mehr Zeit ich mir zwischen erstem um zweiten set lasse, desto größer die Anzahl der incomingEvents.
Es sieht für mich so aus, als ob ALLE topics, die über die Zeit beim MQTT2_CLIENT eintreffen erst mit dem publishen bei der MQTT_GENERIC_BRIDGE zu der Logausgabe, führen. Hm, kann es sein, dass der MQTT2_CLIENT, alle Topics für die es keinen Abnehmer innerhalb von FHEM gibt (also keinen MQTT2_CLIENT mit passender readingList) puffert und dann in einem Rutsch an MQTT_GENERIC_BRIDGE rausbläst, sobald was gepublished wird???

hexenmeister · 06 März 2019, 21:02:54

Gute Untersuchung! Damit wissen wir zumindest, dass das an dem Zusammenspiel liegt. Leider verstehe ich immer noch nicht, wie das geht. Ich muss versuchen, dein Minimalaufbau nachzubauen. Leider kann das etwas dauern, stecke mitten drin im Umzugsstress

nuccleon · 06 März 2019, 23:29:14

Alles klar, melde dich einfach, wenn ich dich noch irgendwie supporten kann.
Danke schonmal für deine Mühe!

nuccleon · 22 April 2019, 20:56:58

Ich wollte mal ganz vorsichtig anfragen ob es schon Neuigkeiten gibt

hexenmeister · 23 April 2019, 15:12:31

Bin vor kurzem umgezogen, habe noch weder Test- noch Produktiv-System.
Bin daher kein Schritt weiter gekommen.

Daniel123 · 11 Januar 2021, 21:44:20

Wie es aussieht habe ich das selbe Problem. Konnte es schon jemand lösen?

Daniel123 · 11 Januar 2021, 22:15:49

Also ich habe das
attr mqttGeneric IODev von "MQTT2_FHEM_Server" auf "Mosquitto" geändert.

Bei der Vorstellung des Moduls "MQTT_GENERIC_BRIDGE" ist ja auch beschrieben, dass es nicht kompatibel mit neuen Modulen MQTT2_SERVER / MQTT2_DEVICE ist.