Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. Einsteigerfragen
  4. Einbindung von Geräten
  5. MQTT Topics ignorieren

NEWS

  • Wartung am 15.11. – Forum ab 22:00 Uhr nicht erreichbar
    BluefoxB
    Bluefox
    12
    2
    229

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.0k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.7k

MQTT Topics ignorieren

MQTT Topics ignorieren

Scheduled Pinned Locked Moved Einbindung von Geräten
mqtttopicignorieren
7 Posts 2 Posters 572 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Rushmed
    Most Active
    wrote on last edited by
    #1

    Hallo,

    ich habe hier drei MQTT Clients die extrem viele Topics senden.
    Davon würde ich gerne welche über diese Funktion abbestellen:
    f626cecc-b3df-4a42-82be-6c5f68b793e7-grafik.png
    Ich hoffe das ist so gedacht!?
    Die MQTT Instanz ist der Server.

    Ignorieren möchte ich alles unter:
    mqtt.0.instar.all.alarm.*
    mqtt.0.instar.cam_10.alarm.*
    und
    mqtt.0.instar.cam_11.alarm.*

    Lösche ich nun alle Objekte und gebe ich im Feld ".alarm.*" ein werden diese trotzdem wieder erstellt.

    Was mache ich falsch?

    Marc BergM 1 Reply Last reply
    0
    • R Rushmed

      Hallo,

      ich habe hier drei MQTT Clients die extrem viele Topics senden.
      Davon würde ich gerne welche über diese Funktion abbestellen:
      f626cecc-b3df-4a42-82be-6c5f68b793e7-grafik.png
      Ich hoffe das ist so gedacht!?
      Die MQTT Instanz ist der Server.

      Ignorieren möchte ich alles unter:
      mqtt.0.instar.all.alarm.*
      mqtt.0.instar.cam_10.alarm.*
      und
      mqtt.0.instar.cam_11.alarm.*

      Lösche ich nun alle Objekte und gebe ich im Feld ".alarm.*" ein werden diese trotzdem wieder erstellt.

      Was mache ich falsch?

      Marc BergM Offline
      Marc BergM Offline
      Marc Berg
      Most Active
      wrote on last edited by
      #2

      @rushmed sagte in MQTT Topics ignorieren:

      ".alarm.*"

      hast du mal

      *.alarm.*
      

      probiert?

      NUC10I3+Ubuntu+Docker+ioBroker+influxDB2+Node Red+RabbitMQ+Grafana

      Pi-hole, Traefik, Checkmk, Conbee II+Zigbee2MQTT, ESPSomfy-RTS, LoRaWAN, Arduino, KiCad

      Benutzt das Voting im Beitrag, wenn er euch geholfen hat.

      R 1 Reply Last reply
      0
      • Marc BergM Marc Berg

        @rushmed sagte in MQTT Topics ignorieren:

        ".alarm.*"

        hast du mal

        *.alarm.*
        

        probiert?

        R Offline
        R Offline
        Rushmed
        Most Active
        wrote on last edited by
        #3

        @marc-berg sagte in MQTT Topics ignorieren:

        .alarm.

        Ja, das bringt den Adapter in einen Bootloop.

        host.Smartazamba
        2024-02-14 20:13:51.443	info	Restart adapter system.adapter.mqtt.0 because enabled
        host.Smartazamba
        2024-02-14 20:13:51.443	error	instance system.adapter.mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        host.Smartazamba
        2024-02-14 20:13:51.442	error	Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11905:26
        host.Smartazamba
        2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT._callReadyHandler (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11928:18)
        host.Smartazamba
        2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT.emit (node:domain:489:12)
        host.Smartazamba
        2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT.emit (node:events:517:28)
        host.Smartazamba
        2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT.onReady (/opt/iobroker/node_modules/iobroker.mqtt/main.js:38:24)
        host.Smartazamba
        2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT.main (/opt/iobroker/node_modules/iobroker.mqtt/main.js:99:54)
        host.Smartazamba
        2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTTServer (/opt/iobroker/node_modules/iobroker.mqtt/lib/server.js:17:16)
        host.Smartazamba
        2024-02-14 20:13:51.442	error	Caught by controller[0]: at new MQTTServer (/opt/iobroker/node_modules/iobroker.mqtt/lib/server.js:49:35)
        host.Smartazamba
        2024-02-14 20:13:51.442	error	Caught by controller[0]: at new RegExp (<anonymous>)
        host.Smartazamba
        2024-02-14 20:13:51.441	error	Caught by controller[0]: SyntaxError: Invalid regular expression: /*\.alarm\..*/: Nothing to repeat
        host.Smartazamba
        2024-02-14 20:13:51.441	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
        
        mqtt.0
        2024-02-14 20:13:51.240	info	terminating
        
        mqtt.0
        2024-02-14 20:13:50.737	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
        
        mqtt.0
        2024-02-14 20:13:50.734	info	terminating
        
        mqtt.0
        2024-02-14 20:13:50.674	error	Invalid regular expression: /*\.alarm\..*/: Nothing to repeat
        
        mqtt.0
        2024-02-14 20:13:50.673	error	SyntaxError: Invalid regular expression: /*\.alarm\..*/: Nothing to repeat at new RegExp (<anonymous>) at new MQTTServer (/opt/iobroker/node_modules/iobroker.mqtt/lib/server.js:49:35) at MQTTServer (/opt/iobroker/node_modules/iobroker.mqtt/lib/server.js:17:16) at MQTT.main (/opt/iobroker/node_modules/iobroker.mqtt/main.js:99:54) at MQTT.onReady (/opt/iobroker/node_modules/iobroker.mqtt/main.js:38:24) at MQTT.emit (node:events:517:28) at MQTT.emit (node:domain:489:12) at MQTT._callReadyHandler (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11928:18) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11905:26
        
        mqtt.0
        2024-02-14 20:13:50.358	error	unhandled promise rejection: Invalid regular expression: /*\.alarm\..*/: Nothing to repeat
        
        mqtt.0
        2024-02-14 20:13:50.356	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
        
        mqtt.0
        2024-02-14 20:13:50.353	info	Ignoring topic with pattern: *.alarm.* (RegExp: *\.alarm\..* und ^mqtt\.0\..*\.alarm\..*)
        
        mqtt.0
        2024-02-14 20:13:50.173	warn	No ioBroker changes will be published to the clients. Set the "publish" option in the adapter settings to subscribe for relevant changes.
        
        mqtt.0
        2024-02-14 20:13:50.131	info	starting. Version 5.2.0 in /opt/iobroker/node_modules/iobroker.mqtt, node: v18.19.0, js-controller: 5.0.17
        
        Marc BergM 1 Reply Last reply
        0
        • R Rushmed

          @marc-berg sagte in MQTT Topics ignorieren:

          .alarm.

          Ja, das bringt den Adapter in einen Bootloop.

          host.Smartazamba
          2024-02-14 20:13:51.443	info	Restart adapter system.adapter.mqtt.0 because enabled
          host.Smartazamba
          2024-02-14 20:13:51.443	error	instance system.adapter.mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          host.Smartazamba
          2024-02-14 20:13:51.442	error	Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11905:26
          host.Smartazamba
          2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT._callReadyHandler (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11928:18)
          host.Smartazamba
          2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT.emit (node:domain:489:12)
          host.Smartazamba
          2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT.emit (node:events:517:28)
          host.Smartazamba
          2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT.onReady (/opt/iobroker/node_modules/iobroker.mqtt/main.js:38:24)
          host.Smartazamba
          2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTT.main (/opt/iobroker/node_modules/iobroker.mqtt/main.js:99:54)
          host.Smartazamba
          2024-02-14 20:13:51.442	error	Caught by controller[0]: at MQTTServer (/opt/iobroker/node_modules/iobroker.mqtt/lib/server.js:17:16)
          host.Smartazamba
          2024-02-14 20:13:51.442	error	Caught by controller[0]: at new MQTTServer (/opt/iobroker/node_modules/iobroker.mqtt/lib/server.js:49:35)
          host.Smartazamba
          2024-02-14 20:13:51.442	error	Caught by controller[0]: at new RegExp (<anonymous>)
          host.Smartazamba
          2024-02-14 20:13:51.441	error	Caught by controller[0]: SyntaxError: Invalid regular expression: /*\.alarm\..*/: Nothing to repeat
          host.Smartazamba
          2024-02-14 20:13:51.441	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
          
          mqtt.0
          2024-02-14 20:13:51.240	info	terminating
          
          mqtt.0
          2024-02-14 20:13:50.737	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
          
          mqtt.0
          2024-02-14 20:13:50.734	info	terminating
          
          mqtt.0
          2024-02-14 20:13:50.674	error	Invalid regular expression: /*\.alarm\..*/: Nothing to repeat
          
          mqtt.0
          2024-02-14 20:13:50.673	error	SyntaxError: Invalid regular expression: /*\.alarm\..*/: Nothing to repeat at new RegExp (<anonymous>) at new MQTTServer (/opt/iobroker/node_modules/iobroker.mqtt/lib/server.js:49:35) at MQTTServer (/opt/iobroker/node_modules/iobroker.mqtt/lib/server.js:17:16) at MQTT.main (/opt/iobroker/node_modules/iobroker.mqtt/main.js:99:54) at MQTT.onReady (/opt/iobroker/node_modules/iobroker.mqtt/main.js:38:24) at MQTT.emit (node:events:517:28) at MQTT.emit (node:domain:489:12) at MQTT._callReadyHandler (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11928:18) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11905:26
          
          mqtt.0
          2024-02-14 20:13:50.358	error	unhandled promise rejection: Invalid regular expression: /*\.alarm\..*/: Nothing to repeat
          
          mqtt.0
          2024-02-14 20:13:50.356	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          
          mqtt.0
          2024-02-14 20:13:50.353	info	Ignoring topic with pattern: *.alarm.* (RegExp: *\.alarm\..* und ^mqtt\.0\..*\.alarm\..*)
          
          mqtt.0
          2024-02-14 20:13:50.173	warn	No ioBroker changes will be published to the clients. Set the "publish" option in the adapter settings to subscribe for relevant changes.
          
          mqtt.0
          2024-02-14 20:13:50.131	info	starting. Version 5.2.0 in /opt/iobroker/node_modules/iobroker.mqtt, node: v18.19.0, js-controller: 5.0.17
          
          Marc BergM Offline
          Marc BergM Offline
          Marc Berg
          Most Active
          wrote on last edited by
          #4

          @rushmed

          Du könntest doch auch einzeln

          mqtt.0.instar.all.alarm.*
          mqtt.0.instar.cam_10.alarm.*
          mqtt.0.instar.cam_11.alarm.*

          (jeweils duch <Enter> getrennt) angeben.

          NUC10I3+Ubuntu+Docker+ioBroker+influxDB2+Node Red+RabbitMQ+Grafana

          Pi-hole, Traefik, Checkmk, Conbee II+Zigbee2MQTT, ESPSomfy-RTS, LoRaWAN, Arduino, KiCad

          Benutzt das Voting im Beitrag, wenn er euch geholfen hat.

          R 1 Reply Last reply
          0
          • Marc BergM Marc Berg

            @rushmed

            Du könntest doch auch einzeln

            mqtt.0.instar.all.alarm.*
            mqtt.0.instar.cam_10.alarm.*
            mqtt.0.instar.cam_11.alarm.*

            (jeweils duch <Enter> getrennt) angeben.

            R Offline
            R Offline
            Rushmed
            Most Active
            wrote on last edited by
            #5

            @marc-berg sagte in MQTT Topics ignorieren:

            mqtt.0.instar.all.alarm.*

            Da werden die Ojekte ebenfalls wieder angelegt.

            Marc BergM 1 Reply Last reply
            0
            • R Rushmed

              @marc-berg sagte in MQTT Topics ignorieren:

              mqtt.0.instar.all.alarm.*

              Da werden die Ojekte ebenfalls wieder angelegt.

              Marc BergM Offline
              Marc BergM Offline
              Marc Berg
              Most Active
              wrote on last edited by
              #6

              @rushmed sagte in MQTT Topics ignorieren:

              Da werden die Ojekte ebenfalls wieder angelegt.

              und die Topics sind in einzelnen "Bubbles"?

              6945d36e-e2d9-498d-914b-56794e2ace7c-grafik.png

              Wenn ja, scheint es wohl ein Bug zu sein.

              NUC10I3+Ubuntu+Docker+ioBroker+influxDB2+Node Red+RabbitMQ+Grafana

              Pi-hole, Traefik, Checkmk, Conbee II+Zigbee2MQTT, ESPSomfy-RTS, LoRaWAN, Arduino, KiCad

              Benutzt das Voting im Beitrag, wenn er euch geholfen hat.

              R 1 Reply Last reply
              1
              • Marc BergM Marc Berg

                @rushmed sagte in MQTT Topics ignorieren:

                Da werden die Ojekte ebenfalls wieder angelegt.

                und die Topics sind in einzelnen "Bubbles"?

                6945d36e-e2d9-498d-914b-56794e2ace7c-grafik.png

                Wenn ja, scheint es wohl ein Bug zu sein.

                R Offline
                R Offline
                Rushmed
                Most Active
                wrote on last edited by
                #7

                @marc-berg Danke, das hatte ich befürchtet.
                Habe ein Issue aufgemacht.

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                Support us

                ioBroker
                Community Adapters
                Donate

                58

                Online

                32.4k

                Users

                81.3k

                Topics

                1.3m

                Posts
                Community
                Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                ioBroker Community 2014-2025
                logo
                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Recent
                • Tags
                • Unread 0
                • Categories
                • Unreplied
                • Popular
                • GitHub
                • Docu
                • Hilfe