Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • 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

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Shelly Plus 1PM nach update Fehler

NEWS

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    10
    1
    319

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    24
    1
    1.5k

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

Shelly Plus 1PM nach update Fehler

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
6 Beiträge 3 Kommentatoren 1.6k Aufrufe 3 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • MichaelFM Offline
    MichaelFM Offline
    MichaelF
    schrieb am zuletzt editiert von MichaelF
    #1

    Hi,

    gestern habe ich meine 4 Shellys plus 1PM und 2PM mit der neusten Firmware upgedatet.

    Jetzt habe ich volgende Fehlermelung von allen :

    [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443g58fb374"
    

    Hat das vielleicht noch jemand oder weis wie ich den Fehler beseitigen kann, Problem ist das mein Iobroker bei der riesigen menge an Meldungen nicht mehr läuft, ich habe den Adapter jetzt ausgeschaltet.

    Oder weis jemand wie ich die Firmware wieder downgrade kann, gefunden habe ich dieses hier :

    b713dd04-0a9e-4cc1-b8f7-9171719837e5-image.png

    Allerdings finde ich das Archiv nicht

    Grüße

    1 Antwort Letzte Antwort
    0
    • MichaelFM Offline
      MichaelFM Offline
      MichaelF
      schrieb am zuletzt editiert von MichaelF
      #2
      6006	2023-09-17 09:21:28.010	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().
      shelly.1
      	6006	2023-09-17 09:21:28.009	error	Cannot find view "system" for search "channel" : Connection is closed.
      shelly.1
      	6006	2023-09-17 09:21:28.007	error	Cannot find view "system" for search "device" : Connection is closed.
      shelly.1
      	6006	2023-09-17 09:21:26.385	error	DB closed
      shelly.1
      	6006	2023-09-17 09:21:26.384	error	Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9)
      shelly.1
      	6006	2023-09-17 09:21:26.378	error	unhandled promise rejection: DB closed
      shelly.1
      	6006	2023-09-17 09:21:26.378	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().
      shelly.1
      	6006	2023-09-17 09:21:20.474	error	DB closed
      shelly.1
      	6006	2023-09-17 09:21:20.473	error	Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
      shelly.1
      	6006	2023-09-17 09:21:19.929	error	unhandled promise rejection: DB closed
      shelly.1
      	6006	2023-09-17 09:21:19.928	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().
      shelly.1
      	6006	2023-09-17 09:21:19.599	error	DB closed
      shelly.1
      	6006	2023-09-17 09:21:19.599	error	Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
      shelly.1
      	6006	2023-09-17 09:21:19.599	error	unhandled promise rejection: DB closed
      shelly.1
      	6006	2023-09-17 09:21:19.598	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().
      shelly.1
      	6006	2023-09-17 09:21:19.571	error	DB closed
      shelly.1
      	6006	2023-09-17 09:21:19.570	error	Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
      shelly.1
      	6006	2023-09-17 09:21:19.563	error	unhandled promise rejection: DB closed
      shelly.1
      	6006	2023-09-17 09:21:19.562	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().
      shelly.1
      	6006	2023-09-17 09:21:17.862	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443grewb394"
      shelly.1
      	6006	2023-09-17 09:20:47.628	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c6ff49b2d4"
      shelly.1
      	6006	2023-09-17 09:20:46.417	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab48ff28"
      shelly.1
      	6006	2023-09-17 09:20:33.289	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce658490"
      shelly.1
      	6006	2023-09-17 09:20:07.657	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23ss394"
      

      hier nochmal ein längerer Auszug

      Kurzes update, ich habe jetzt überall nochmal das MQTT Passwort eingegeben, jetzt bekomme ich von allen dieses :

      shelly.1
      	14651	2023-09-17 09:47:59.331	info	[MQTT] Client Close: (shellyplus1pm / shellyplus1pm-3c6579b2d4 / shellyplus1pm#3c6579b2d4#1) (false)
      shelly.1
      	14651	2023-09-17 09:47:49.339	info	[MQTT] Device with client id "shellyplus1pm-3c610579b2d4" connected!
      shelly.1
      	14651	2023-09-17 09:47:45.550	info	[MQTT] Client Close: (shellyplus1pm / shellyplus1pm-7cce648490 / shellyplus1pm#7cce648490#1) (false)
      shelly.1
      	14651	2023-09-17 09:47:35.765	info	[MQTT] Device with client id "shellyplus1pm-7c87ce648490" connected!
      shelly.1
      	14651	2023-09-17 09:47:33.682	info	[MQTT] Client Close: (shellyplus2pm / shellyplus2pm-53b23fb394 / shellyplus2pm#53b23fb394#1) (false)
      

      Aber auch jetzt wieder Fehlermeldungen

      66er6 1 Antwort Letzte Antwort
      0
      • MichaelFM MichaelF
        6006	2023-09-17 09:21:28.010	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().
        shelly.1
        	6006	2023-09-17 09:21:28.009	error	Cannot find view "system" for search "channel" : Connection is closed.
        shelly.1
        	6006	2023-09-17 09:21:28.007	error	Cannot find view "system" for search "device" : Connection is closed.
        shelly.1
        	6006	2023-09-17 09:21:26.385	error	DB closed
        shelly.1
        	6006	2023-09-17 09:21:26.384	error	Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9)
        shelly.1
        	6006	2023-09-17 09:21:26.378	error	unhandled promise rejection: DB closed
        shelly.1
        	6006	2023-09-17 09:21:26.378	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().
        shelly.1
        	6006	2023-09-17 09:21:20.474	error	DB closed
        shelly.1
        	6006	2023-09-17 09:21:20.473	error	Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34)
        shelly.1
        	6006	2023-09-17 09:21:19.929	error	unhandled promise rejection: DB closed
        shelly.1
        	6006	2023-09-17 09:21:19.928	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().
        shelly.1
        	6006	2023-09-17 09:21:19.599	error	DB closed
        shelly.1
        	6006	2023-09-17 09:21:19.599	error	Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
        shelly.1
        	6006	2023-09-17 09:21:19.599	error	unhandled promise rejection: DB closed
        shelly.1
        	6006	2023-09-17 09:21:19.598	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().
        shelly.1
        	6006	2023-09-17 09:21:19.571	error	DB closed
        shelly.1
        	6006	2023-09-17 09:21:19.570	error	Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:629:26) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:323:12)
        shelly.1
        	6006	2023-09-17 09:21:19.563	error	unhandled promise rejection: DB closed
        shelly.1
        	6006	2023-09-17 09:21:19.562	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().
        shelly.1
        	6006	2023-09-17 09:21:17.862	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443grewb394"
        shelly.1
        	6006	2023-09-17 09:20:47.628	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-3c6ff49b2d4"
        shelly.1
        	6006	2023-09-17 09:20:46.417	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab48ff28"
        shelly.1
        	6006	2023-09-17 09:20:33.289	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-7c87ce658490"
        shelly.1
        	6006	2023-09-17 09:20:07.657	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-5443b23ss394"
        

        hier nochmal ein längerer Auszug

        Kurzes update, ich habe jetzt überall nochmal das MQTT Passwort eingegeben, jetzt bekomme ich von allen dieses :

        shelly.1
        	14651	2023-09-17 09:47:59.331	info	[MQTT] Client Close: (shellyplus1pm / shellyplus1pm-3c6579b2d4 / shellyplus1pm#3c6579b2d4#1) (false)
        shelly.1
        	14651	2023-09-17 09:47:49.339	info	[MQTT] Device with client id "shellyplus1pm-3c610579b2d4" connected!
        shelly.1
        	14651	2023-09-17 09:47:45.550	info	[MQTT] Client Close: (shellyplus1pm / shellyplus1pm-7cce648490 / shellyplus1pm#7cce648490#1) (false)
        shelly.1
        	14651	2023-09-17 09:47:35.765	info	[MQTT] Device with client id "shellyplus1pm-7c87ce648490" connected!
        shelly.1
        	14651	2023-09-17 09:47:33.682	info	[MQTT] Client Close: (shellyplus2pm / shellyplus2pm-53b23fb394 / shellyplus2pm#53b23fb394#1) (false)
        

        Aber auch jetzt wieder Fehlermeldungen

        66er6 Offline
        66er6 Offline
        66er
        schrieb am zuletzt editiert von
        #3

        @michaelf

        Moin moin.

        • Für Generation2 Shelly wirst Du kein Archiv finden, da der Hersteller Shelly die Firmware nicht mehr generell zum Downgrade

        • Die wichtigste Angabe zu Deinem Problem fehlt leider. :-(
          Welche Firmware ist denn nun drauf? Ich vermute mal 1.0.0 ?

        LG
        Stefan

        MichaelFM 1 Antwort Letzte Antwort
        0
        • 66er6 66er

          @michaelf

          Moin moin.

          • Für Generation2 Shelly wirst Du kein Archiv finden, da der Hersteller Shelly die Firmware nicht mehr generell zum Downgrade

          • Die wichtigste Angabe zu Deinem Problem fehlt leider. :-(
            Welche Firmware ist denn nun drauf? Ich vermute mal 1.0.0 ?

          MichaelFM Offline
          MichaelFM Offline
          MichaelF
          schrieb am zuletzt editiert von
          #4

          @66er

          Hi, hatte die 1.0.3 auf den shelly's.

          Habe im Schelly forum die 0.14 bekommen seit dem läuft wieder alles wie vorher.

          Grüße

          66er6 1 Antwort Letzte Antwort
          0
          • MichaelFM MichaelF

            @66er

            Hi, hatte die 1.0.3 auf den shelly's.

            Habe im Schelly forum die 0.14 bekommen seit dem läuft wieder alles wie vorher.

            Grüße

            66er6 Offline
            66er6 Offline
            66er
            schrieb am zuletzt editiert von
            #5

            @michaelf

            ok. :+1:

            LG
            Stefan

            SoundyS 1 Antwort Letzte Antwort
            0
            • 66er6 66er

              @michaelf

              ok. :+1:

              SoundyS Offline
              SoundyS Offline
              Soundy
              schrieb am zuletzt editiert von
              #6

              Hier mein (sehr positives) Fazit zum Downgrade:
              https://forum.iobroker.net/post/1058091

              Ich wollte es hier nicht nochmal posten. ;)

              1 Antwort Letzte Antwort
              0
              Antworten
              • In einem neuen Thema antworten
              Anmelden zum Antworten
              • Älteste zuerst
              • Neuste zuerst
              • Meiste Stimmen


              Support us

              ioBroker
              Community Adapters
              Donate
              FAQ Cloud / IOT
              HowTo: Node.js-Update
              HowTo: Backup/Restore
              Downloads
              BLOG

              754

              Online

              32.5k

              Benutzer

              81.7k

              Themen

              1.3m

              Beiträge
              Community
              Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
              ioBroker Community 2014-2025
              logo
              • Anmelden

              • Du hast noch kein Konto? Registrieren

              • Anmelden oder registrieren, um zu suchen
              • Erster Beitrag
                Letzter Beitrag
              0
              • Home
              • Aktuell
              • Tags
              • Ungelesen 0
              • Kategorien
              • Unreplied
              • Beliebt
              • GitHub
              • Docu
              • Hilfe