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
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter Shelly 10.4.x (LATEST / BETA)

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.2k
  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.9k
  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.3k

Test Adapter Shelly 10.4.x (LATEST / BETA)

Geplant Angeheftet Gesperrt Verschoben Tester
mcm1957shelly
54 Beiträge 11 Kommentatoren 5.5k Aufrufe 14 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.
  • W wg

    Hi,
    habe gestern die 10.0.0 installiert und danach gings mir wie Fabio.
    Ich habe das script v1.0 von https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/v10.0.0/docs/en/ble-devices.md kopiert - dort ist noch die Version mit der problematischen Zeile ( console.log('Received ' + JSON.stringify(unpackedData)); ).
    Sollte noch nachgeführt werden.
    Gruß

    haus-automatisierungH Online
    haus-automatisierungH Online
    haus-automatisierung
    Developer Most Active
    schrieb am zuletzt editiert von haus-automatisierung
    #25

    @wg Da ist ein Copy/Paste Fehler im Script. Nimm mal das von der neuesten Version

    https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/v10.1.0/docs/en/ble-devices.md

    🧑‍🎓 Autor des beliebten ioBroker-Master-Kurses
    🎥 Tutorials rund um das Thema DIY-Smart-Home: https://haus-automatisierung.com/
    📚 Meine inoffizielle ioBroker Dokumentation

    1 Antwort Letzte Antwort
    1
    • W wg

      Hi,
      habe gestern die 10.0.0 installiert und danach gings mir wie Fabio.
      Ich habe das script v1.0 von https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/v10.0.0/docs/en/ble-devices.md kopiert - dort ist noch die Version mit der problematischen Zeile ( console.log('Received ' + JSON.stringify(unpackedData)); ).
      Sollte noch nachgeführt werden.
      Gruß

      mcm1957M Online
      mcm1957M Online
      mcm1957
      schrieb am zuletzt editiert von
      #26

      @wg
      Sieht sobaus als hättest du das mit Release 10.0.0 getaggte Skript genommen. Das ist Stand der zum Zeitpunkt des Releasens von 10.0.0 aktuell war. Bitte benutze die jeweils aktuelle Versuon. Dort ist der Fehler korrigiert.

      Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
      Support Repositoryverwaltung.

      Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

      LESEN - gute Forenbeitrage

      haus-automatisierungH 1 Antwort Letzte Antwort
      1
      • mcm1957M mcm1957

        @wg
        Sieht sobaus als hättest du das mit Release 10.0.0 getaggte Skript genommen. Das ist Stand der zum Zeitpunkt des Releasens von 10.0.0 aktuell war. Bitte benutze die jeweils aktuelle Versuon. Dort ist der Fehler korrigiert.

        haus-automatisierungH Online
        haus-automatisierungH Online
        haus-automatisierung
        Developer Most Active
        schrieb am zuletzt editiert von
        #27

        @mcm1957 sagte in Test Adapter Shelly 10.0.0 (LATEST / BETA):

        Sieht sobaus als hättest du das mit Release 10.0.0 getaggte Skript genommen.

        Das ist ja auch erstmal der richtige Weg. Dafür gibt es ja die Tabelle in der Doku. Ich aktualisiere die mal.

        🧑‍🎓 Autor des beliebten ioBroker-Master-Kurses
        🎥 Tutorials rund um das Thema DIY-Smart-Home: https://haus-automatisierung.com/
        📚 Meine inoffizielle ioBroker Dokumentation

        Rene55R 1 Antwort Letzte Antwort
        0
        • W Offline
          W Offline
          wg
          schrieb am zuletzt editiert von
          #28

          Ja, genau - über die Tabelle der Doku kommt man dahin. Sollte nur ein Hinweis sein. Ich hab das betreffende statement auskommentiert - läuft dann problemlos.

          mcm1957M 1 Antwort Letzte Antwort
          0
          • W wg

            Ja, genau - über die Tabelle der Doku kommt man dahin. Sollte nur ein Hinweis sein. Ich hab das betreffende statement auskommentiert - läuft dann problemlos.

            mcm1957M Online
            mcm1957M Online
            mcm1957
            schrieb am zuletzt editiert von mcm1957
            #29

            @wg
            DANKE jetzt versteh ich das Problem.

            Mir war nicht bewusst dass hinter der Version in der Tabelle ein Link auf eine GH Release / Tag steht. Daher bist du auf der alten Version gelandet Im .md File war der Fehler ja schon korrigiert.

            @haus-automatisierung hat das aber schon ausgebessert. Danke.

            DANKE an alle

            Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
            Support Repositoryverwaltung.

            Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

            LESEN - gute Forenbeitrage

            mcm1957M 1 Antwort Letzte Antwort
            0
            • mcm1957M mcm1957

              @wg
              DANKE jetzt versteh ich das Problem.

              Mir war nicht bewusst dass hinter der Version in der Tabelle ein Link auf eine GH Release / Tag steht. Daher bist du auf der alten Version gelandet Im .md File war der Fehler ja schon korrigiert.

              @haus-automatisierung hat das aber schon ausgebessert. Danke.

              DANKE an alle

              mcm1957M Online
              mcm1957M Online
              mcm1957
              schrieb am zuletzt editiert von mcm1957
              #30

              Anbei eine Kopie des Postings von @haus-automatisierung im parallelen Topic mit der Bitte um Feedback zum Thema ENCRYPTED BLU Geräten:

              @haus-automatisierung said in Shelly >= 10.0.0 mit verschlüsselten BLU-Geräten:

              Nachdem ich ja bereits die Shelly-BLU Geräte mit einem Scripts in den ioBroker geholt habe, gibt es mal wieder ein größeres Update: Es werden ab Version 10.0.0 des Shelly-Adapters auch verschlüsselte Payloads unterstützt!

              Dafür muss man den EcryptionKey (welchen man in der Shelly BLE Debug App bekommen hat) in den Objekten hinterlegen.

              Doku: https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/docs/en/ble-devices.md#encryption

              Komplette Video-Erklärung: https://www.youtube.com/watch?v=FubPHOsktbU

              Neu ist auch, dass das Script deutlich kürzer geworden ist und somit nicht mehr zu Speicherplatz-Problemen auf Gen3-Geräten führt (da hat man für Scripting weniger Ressourcen dank Matter und co).

              Ich würde mich über Feedback freuen, ob das alles bei euch klappt! Auch positives Feedback, wenn alles gut läuft! Ansonsten weißt ich ja gar nicht, ob das jemals jemand ausprobiert hat...

              Wer also nur dieses Topic auf dem Radar hat - bitte bei Verwendung von BLU mit Encryption um Feedback - auch positives Feedback - an @haus-automatisierung bzw. im genannten Parallelthread.

              DANKE

              Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
              Support Repositoryverwaltung.

              Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

              LESEN - gute Forenbeitrage

              1 Antwort Letzte Antwort
              1
              • haus-automatisierungH haus-automatisierung

                @mcm1957 sagte in Test Adapter Shelly 10.0.0 (LATEST / BETA):

                Sieht sobaus als hättest du das mit Release 10.0.0 getaggte Skript genommen.

                Das ist ja auch erstmal der richtige Weg. Dafür gibt es ja die Tabelle in der Doku. Ich aktualisiere die mal.

                Rene55R Offline
                Rene55R Offline
                Rene55
                schrieb am zuletzt editiert von Rene55
                #31

                @haus-automatisierung Dann hier auch ein Feedback zu encrypteten BLU-Devices. Adapter auf 10.0.0, Script V1.0 auf ein Shelly 1PM. Encryption-Code (mit passenden Bindesrichen) eingetragen - funktioniert. :blush:
                Das schwierigste war, das Device (Blue Tough) mit der Shelly BLE Debug zu koppeln. Hier musste noch ein Update eingespielt werden. Bei der Gelegenheit ist mir dann ein Button 1 gestorben. :cry:
                EDIT: Ich hab den Blu Button 1 wieder reanimieren können (Batterie raus, nochmal OTA Update). Jetzt ist der auch encrypted und funktioniert.

                Host: Fujitsu Intel(R) Pentium(R) CPU G4560T, 32 GB RAM, Proxmox 8.x + lxc Ubuntu 22.04
                ioBroker (8 GB RAM) Node.js: 20.19.1, NPM: 10.8.2, js-Controller: 7.0.6, Admin: 7.6.3
                Wetterstation: Froggit WH3000SE V1.6.6

                haus-automatisierungH 1 Antwort Letzte Antwort
                1
                • Rene55R Rene55

                  @haus-automatisierung Dann hier auch ein Feedback zu encrypteten BLU-Devices. Adapter auf 10.0.0, Script V1.0 auf ein Shelly 1PM. Encryption-Code (mit passenden Bindesrichen) eingetragen - funktioniert. :blush:
                  Das schwierigste war, das Device (Blue Tough) mit der Shelly BLE Debug zu koppeln. Hier musste noch ein Update eingespielt werden. Bei der Gelegenheit ist mir dann ein Button 1 gestorben. :cry:
                  EDIT: Ich hab den Blu Button 1 wieder reanimieren können (Batterie raus, nochmal OTA Update). Jetzt ist der auch encrypted und funktioniert.

                  haus-automatisierungH Online
                  haus-automatisierungH Online
                  haus-automatisierung
                  Developer Most Active
                  schrieb am zuletzt editiert von
                  #32

                  @rene55 Bindestriche sind egal. Sollten in der aktuellen Version auch direkt entfernt werden, wenn man den EncryptionKey unbestätigt schreibt (was man ja eh immer bei „fremden“ Datenpunkten so macht)

                  🧑‍🎓 Autor des beliebten ioBroker-Master-Kurses
                  🎥 Tutorials rund um das Thema DIY-Smart-Home: https://haus-automatisierung.com/
                  📚 Meine inoffizielle ioBroker Dokumentation

                  Rene55R 1 Antwort Letzte Antwort
                  0
                  • haus-automatisierungH haus-automatisierung

                    @rene55 Bindestriche sind egal. Sollten in der aktuellen Version auch direkt entfernt werden, wenn man den EncryptionKey unbestätigt schreibt (was man ja eh immer bei „fremden“ Datenpunkten so macht)

                    Rene55R Offline
                    Rene55R Offline
                    Rene55
                    schrieb am zuletzt editiert von
                    #33

                    @haus-automatisierung Ok, die Bindestriche sind luxus. Heißt das auch, dass der encriptionKey immer mit ack=false stehen bleibt?

                    Host: Fujitsu Intel(R) Pentium(R) CPU G4560T, 32 GB RAM, Proxmox 8.x + lxc Ubuntu 22.04
                    ioBroker (8 GB RAM) Node.js: 20.19.1, NPM: 10.8.2, js-Controller: 7.0.6, Admin: 7.6.3
                    Wetterstation: Froggit WH3000SE V1.6.6

                    haus-automatisierungH 1 Antwort Letzte Antwort
                    0
                    • Rene55R Rene55

                      @haus-automatisierung Ok, die Bindestriche sind luxus. Heißt das auch, dass der encriptionKey immer mit ack=false stehen bleibt?

                      haus-automatisierungH Online
                      haus-automatisierungH Online
                      haus-automatisierung
                      Developer Most Active
                      schrieb am zuletzt editiert von
                      #34

                      @rene55 Version 10.1.0 sollte den Schlüssel bestätigen und entsprechend mit ack true neu schreiben.

                      🧑‍🎓 Autor des beliebten ioBroker-Master-Kurses
                      🎥 Tutorials rund um das Thema DIY-Smart-Home: https://haus-automatisierung.com/
                      📚 Meine inoffizielle ioBroker Dokumentation

                      Rene55R 1 Antwort Letzte Antwort
                      1
                      • icebearI Online
                        icebearI Online
                        icebear
                        schrieb am zuletzt editiert von icebear
                        #35

                        Ich hab jetzt auch nochmals auf die Version 10.1.0 geupdatet in der Hoffung das die Fehlermeldung vom Shelly Adapter verschwinden, aber ich bekomme immer noch die folgenden Fehlermeldungen die das Log zumüllen:

                        [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"

                        bei allen Shelly Plugs die ich einsetzte.

                        Debug Log (Auszug)

                        shelly.0
2025-07-08 09:55:30.347	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1125876

shelly.0
2025-07-08 09:55:29.111	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on

shelly.0
2025-07-08 09:55:29.111	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761

shelly.0
2025-07-08 09:55:29.110	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00

shelly.0
2025-07-08 09:55:20.774	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"

shelly.0
2025-07-08 09:55:20.763	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"

shelly.0
2025-07-08 09:55:20.723	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)

shelly.0
2025-07-08 09:55:20.723	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 09:55:20.722	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 09:55:20.695	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)

shelly.0
2025-07-08 09:55:20.695	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 09:55:20.695	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 09:55:20.694	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"

shelly.0
2025-07-08 09:55:20.605	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)

shelly.0
2025-07-08 09:55:20.605	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 09:55:20.604	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 09:55:14.535	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1125860

shelly.0
2025-07-08 09:55:14.503	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761

shelly.0
2025-07-08 09:55:10.577	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1"]

shelly.0
2025-07-08 09:55:10.349	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1"]

shelly.0
2025-07-08 09:55:10.143	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplus1#b0a7324c9984#1"]

shelly.0
2025-07-08 09:55:08.400	debug	[deviceStatusUpdate] shellyplus1#78ee4cc5972c#1: false

shelly.0
2025-07-08 09:55:07.159	debug	[MQTT Server] Close for 192.168.178.63 ((undefined / undefined / undefined))

shelly.0
2025-07-08 09:55:07.159	debug	[MQTT] Destroying

shelly.0
2025-07-08 09:55:07.159	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: false

shelly.0
2025-07-08 09:55:07.159	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1)

shelly.0
2025-07-08 09:55:07.159	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) (false)

shelly.0
2025-07-08 09:55:07.158	debug	[MQTT Server] End for 192.168.178.63 ((shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1))

shelly.0
2025-07-08 09:55:06.609	debug	[MQTT Server] Close for 192.168.178.76 ((undefined / undefined / undefined))

shelly.0
2025-07-08 09:55:06.609	debug	[MQTT] Destroying

shelly.0
2025-07-08 09:55:06.609	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: false

shelly.0
2025-07-08 09:55:06.609	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1)

shelly.0
2025-07-08 09:55:06.609	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) (false)

shelly.0
2025-07-08 09:55:06.608	debug	[MQTT Server] End for 192.168.178.76 ((shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1))

shelly.0
2025-07-08 09:55:06.372	debug	[MQTT Server] Close for 192.168.178.44 ((undefined / undefined / undefined))

shelly.0
2025-07-08 09:55:06.372	debug	[MQTT] Destroying

shelly.0
2025-07-08 09:55:06.371	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: false

shelly.0
2025-07-08 09:55:06.371	debug	[BaseClient] Destroying (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1)

shelly.0
2025-07-08 09:55:06.371	info	[MQTT] Client Close: (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) (false)

shelly.0
2025-07-08 09:55:06.362	debug	[MQTT Server] End for 192.168.178.44 ((shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1))

shelly.0
2025-07-08 09:55:06.278	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#441793ab4310#1","shellyplus1#b0a7324c9984#1"]

shelly.0
2025-07-08 09:55:05.963	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#441793ab4310#1"]

host.iobroker
2025-07-08 09:55:05.612	info	instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 26785

shelly.0
2025-07-08 09:55:05.391	debug	[onlineCheck] Checking shellyplus1#78ee4cc5972c#1 on 192.168.178.78:80

shelly.0
2025-07-08 09:55:05.000	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: true

shelly.0
2025-07-08 09:55:04.997	debug	[onlineCheck] Checking shellyplus1#b0a7324c9984#1 on 192.168.178.76:80

shelly.0
2025-07-08 09:55:04.383	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: true

shelly.0
2025-07-08 09:55:04.376	debug	[onlineCheck] Checking shellyplus1#441793ab4310#1 on 192.168.178.63:80

shelly.0
2025-07-08 09:55:03.352	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: true

shelly.0
2025-07-08 09:55:03.349	debug	[onlineCheck] Checking shellyplusplugs#e465b85e4500#1 on 192.168.178.44:80

shelly.0
2025-07-08 09:55:03.257	debug	[deviceStatusUpdate] SHPLG-1#8FF28C#1: true

shelly.0
2025-07-08 09:55:03.196	debug	[onlineCheck] Checking SHPLG-1#8FF28C#1 on 192.168.178.43:80

shelly.0
2025-07-08 09:55:00.508	warn	[mqtt controlFunction] Unable to perform request - device (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) is offline

shelly.0
2025-07-08 09:55:00.508	debug	[onStateChange] "shelly.0.shellyplus1#441793ab4310#1.Relay0.Switch" state changed: {"val":false,"ack":false,"ts":1751961300038,"q":0,"c":"script.js.Energie_Strom.TestWW","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1751885460060} - forwarding to objectHelper

                        Und noch ein weiteres Log

                        
shelly.0
2025-07-08 10:12:01.160	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"

shelly.0
2025-07-08 10:12:01.120	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"

shelly.0
2025-07-08 10:12:01.117	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)

shelly.0
2025-07-08 10:12:01.117	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:12:01.117	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:12:01.054	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)

shelly.0
2025-07-08 10:12:01.054	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:12:01.054	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:12:00.997	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"

shelly.0
2025-07-08 10:12:00.948	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)

shelly.0
2025-07-08 10:12:00.947	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:12:00.947	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:59.212	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on

shelly.0
2025-07-08 10:11:59.212	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761

shelly.0
2025-07-08 10:11:59.211	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00

shelly.0
2025-07-08 10:11:58.026	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1"]

shelly.0
2025-07-08 10:11:56.630	debug	[MQTT Server] Close for 192.168.178.76 ((undefined / undefined / undefined))

shelly.0
2025-07-08 10:11:56.630	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:56.630	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: false

shelly.0
2025-07-08 10:11:56.630	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1)

shelly.0
2025-07-08 10:11:56.630	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) (false)

shelly.0
2025-07-08 10:11:56.629	debug	[MQTT Server] End for 192.168.178.76 ((shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1))

shelly.0
2025-07-08 10:11:52.882	debug	[deviceStatusUpdate] shellyplus1#78ee4cc5972c#1: false

shelly.0
2025-07-08 10:11:52.877	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#b0a7324c9984#1"]

shelly.0
2025-07-08 10:11:52.290	debug	[MQTT Server] Close for 192.168.178.63 ((undefined / undefined / undefined))

shelly.0
2025-07-08 10:11:52.290	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:52.290	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: false

shelly.0
2025-07-08 10:11:52.290	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1)

shelly.0
2025-07-08 10:11:52.289	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) (false)

shelly.0
2025-07-08 10:11:52.289	debug	[MQTT Server] End for 192.168.178.63 ((shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1))

shelly.0
2025-07-08 10:11:50.193	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplusplugs#e465b85e4500#1","shellyplus1#b0a7324c9984#1"]

shelly.0
2025-07-08 10:11:50.040	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplusplugs#e465b85e4500#1"]

shelly.0
2025-07-08 10:11:49.919	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126856

shelly.0
2025-07-08 10:11:49.875	debug	[onlineCheck] Checking shellyplus1#78ee4cc5972c#1 on 192.168.178.78:80

shelly.0
2025-07-08 10:11:49.345	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: true

shelly.0
2025-07-08 10:11:49.336	debug	[onlineCheck] Checking shellyplus1#b0a7324c9984#1 on 192.168.178.76:80

shelly.0
2025-07-08 10:11:48.720	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: true

shelly.0
2025-07-08 10:11:48.716	debug	[onlineCheck] Checking shellyplus1#441793ab4310#1 on 192.168.178.63:80

shelly.0
2025-07-08 10:11:48.478	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: true

shelly.0
2025-07-08 10:11:48.474	debug	[onlineCheck] Checking shellyplusplugs#e465b85e4500#1 on 192.168.178.44:80

shelly.0
2025-07-08 10:11:48.456	debug	[deviceStatusUpdate] SHPLG-1#8FF28C#1: true

shelly.0
2025-07-08 10:11:48.434	debug	[onlineCheck] Checking SHPLG-1#8FF28C#1 on 192.168.178.43:80

shelly.0
2025-07-08 10:11:48.317	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) for mode: <not set>

shelly.0
2025-07-08 10:11:46.640	info	[MQTT] Device with client id "shellyplus1-b0a7324c9984" connected from 192.168.178.76!

shelly.0
2025-07-08 10:11:46.639	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:46.637	debug	[BaseClient] Destroying 192.168.178.76 (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:46.636	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":96,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-b0a7324c9984","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}

shelly.0
2025-07-08 10:11:46.632	debug	[MQTT Server] New connection from 192.168.178.76

shelly.0
2025-07-08 10:11:45.244	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1"]

shelly.0
2025-07-08 10:11:44.794	debug	[MQTT Server] Close for 192.168.178.44 ((undefined / undefined / undefined))

shelly.0
2025-07-08 10:11:44.793	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:44.793	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: false

shelly.0
2025-07-08 10:11:44.793	debug	[BaseClient] Destroying (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1)

shelly.0
2025-07-08 10:11:44.793	info	[MQTT] Client Close: (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) (false)

shelly.0
2025-07-08 10:11:44.791	debug	[MQTT Server] End for 192.168.178.44 ((shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1))

shelly.0
2025-07-08 10:11:43.188	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) for mode: <not set>

shelly.0
2025-07-08 10:11:42.296	info	[MQTT] Device with client id "shellyplus1-441793ab4310" connected from 192.168.178.63!

shelly.0
2025-07-08 10:11:42.296	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:42.296	debug	[BaseClient] Destroying 192.168.178.63 (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:42.296	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":96,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-441793ab4310","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}

shelly.0
2025-07-08 10:11:42.295	debug	[MQTT Server] New connection from 192.168.178.63

shelly.0
2025-07-08 10:11:35.819	debug	[createObjects] Starting object creation of (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) for mode: <not set>

shelly.0
2025-07-08 10:11:34.796	info	[MQTT] Device with client id "shellyplusplugs-e465b85e4500" connected from 192.168.178.44!

shelly.0
2025-07-08 10:11:34.795	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:34.795	debug	[BaseClient] Destroying 192.168.178.44 (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:34.795	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":82,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplusplugs-e465b85e4500","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}

shelly.0
2025-07-08 10:11:34.794	debug	[MQTT Server] New connection from 192.168.178.44

shelly.0
2025-07-08 10:11:33.660	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126839

shelly.0
2025-07-08 10:11:29.209	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on

shelly.0
2025-07-08 10:11:29.208	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761

shelly.0
2025-07-08 10:11:29.207	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00

host.iobroker
2025-07-08 10:11:24.910	info	instance system.adapter.dwd.0 having pid 27773 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

dwd.0
2025-07-08 10:11:23.252	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

shelly.0
2025-07-08 10:11:18.409	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.rssi, value: -63

shelly.0
2025-07-08 10:11:18.409	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126824

shelly.0
2025-07-08 10:11:12.338	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"

shelly.0
2025-07-08 10:11:12.291	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)

shelly.0
2025-07-08 10:11:12.291	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:11:12.290	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:12.258	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"

shelly.0
2025-07-08 10:11:12.149	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)

shelly.0
2025-07-08 10:11:12.148	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:11:12.147	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:12.144	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"

shelly.0
2025-07-08 10:11:12.073	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)

shelly.0
2025-07-08 10:11:12.073	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:11:12.073	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

                        was kann ich tun?

                        mcm1957M 1 Antwort Letzte Antwort
                        0
                        • icebearI icebear

                          Ich hab jetzt auch nochmals auf die Version 10.1.0 geupdatet in der Hoffung das die Fehlermeldung vom Shelly Adapter verschwinden, aber ich bekomme immer noch die folgenden Fehlermeldungen die das Log zumüllen:

                          [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"

                          bei allen Shelly Plugs die ich einsetzte.

                          Debug Log (Auszug)

                          shelly.0
2025-07-08 09:55:30.347	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1125876

shelly.0
2025-07-08 09:55:29.111	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on

shelly.0
2025-07-08 09:55:29.111	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761

shelly.0
2025-07-08 09:55:29.110	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00

shelly.0
2025-07-08 09:55:20.774	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"

shelly.0
2025-07-08 09:55:20.763	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"

shelly.0
2025-07-08 09:55:20.723	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)

shelly.0
2025-07-08 09:55:20.723	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 09:55:20.722	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 09:55:20.695	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)

shelly.0
2025-07-08 09:55:20.695	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 09:55:20.695	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 09:55:20.694	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"

shelly.0
2025-07-08 09:55:20.605	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)

shelly.0
2025-07-08 09:55:20.605	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 09:55:20.604	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 09:55:14.535	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1125860

shelly.0
2025-07-08 09:55:14.503	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761

shelly.0
2025-07-08 09:55:10.577	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1"]

shelly.0
2025-07-08 09:55:10.349	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1"]

shelly.0
2025-07-08 09:55:10.143	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplus1#b0a7324c9984#1"]

shelly.0
2025-07-08 09:55:08.400	debug	[deviceStatusUpdate] shellyplus1#78ee4cc5972c#1: false

shelly.0
2025-07-08 09:55:07.159	debug	[MQTT Server] Close for 192.168.178.63 ((undefined / undefined / undefined))

shelly.0
2025-07-08 09:55:07.159	debug	[MQTT] Destroying

shelly.0
2025-07-08 09:55:07.159	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: false

shelly.0
2025-07-08 09:55:07.159	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1)

shelly.0
2025-07-08 09:55:07.159	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) (false)

shelly.0
2025-07-08 09:55:07.158	debug	[MQTT Server] End for 192.168.178.63 ((shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1))

shelly.0
2025-07-08 09:55:06.609	debug	[MQTT Server] Close for 192.168.178.76 ((undefined / undefined / undefined))

shelly.0
2025-07-08 09:55:06.609	debug	[MQTT] Destroying

shelly.0
2025-07-08 09:55:06.609	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: false

shelly.0
2025-07-08 09:55:06.609	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1)

shelly.0
2025-07-08 09:55:06.609	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) (false)

shelly.0
2025-07-08 09:55:06.608	debug	[MQTT Server] End for 192.168.178.76 ((shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1))

shelly.0
2025-07-08 09:55:06.372	debug	[MQTT Server] Close for 192.168.178.44 ((undefined / undefined / undefined))

shelly.0
2025-07-08 09:55:06.372	debug	[MQTT] Destroying

shelly.0
2025-07-08 09:55:06.371	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: false

shelly.0
2025-07-08 09:55:06.371	debug	[BaseClient] Destroying (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1)

shelly.0
2025-07-08 09:55:06.371	info	[MQTT] Client Close: (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) (false)

shelly.0
2025-07-08 09:55:06.362	debug	[MQTT Server] End for 192.168.178.44 ((shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1))

shelly.0
2025-07-08 09:55:06.278	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#441793ab4310#1","shellyplus1#b0a7324c9984#1"]

shelly.0
2025-07-08 09:55:05.963	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#441793ab4310#1"]

host.iobroker
2025-07-08 09:55:05.612	info	instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 26785

shelly.0
2025-07-08 09:55:05.391	debug	[onlineCheck] Checking shellyplus1#78ee4cc5972c#1 on 192.168.178.78:80

shelly.0
2025-07-08 09:55:05.000	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: true

shelly.0
2025-07-08 09:55:04.997	debug	[onlineCheck] Checking shellyplus1#b0a7324c9984#1 on 192.168.178.76:80

shelly.0
2025-07-08 09:55:04.383	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: true

shelly.0
2025-07-08 09:55:04.376	debug	[onlineCheck] Checking shellyplus1#441793ab4310#1 on 192.168.178.63:80

shelly.0
2025-07-08 09:55:03.352	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: true

shelly.0
2025-07-08 09:55:03.349	debug	[onlineCheck] Checking shellyplusplugs#e465b85e4500#1 on 192.168.178.44:80

shelly.0
2025-07-08 09:55:03.257	debug	[deviceStatusUpdate] SHPLG-1#8FF28C#1: true

shelly.0
2025-07-08 09:55:03.196	debug	[onlineCheck] Checking SHPLG-1#8FF28C#1 on 192.168.178.43:80

shelly.0
2025-07-08 09:55:00.508	warn	[mqtt controlFunction] Unable to perform request - device (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) is offline

shelly.0
2025-07-08 09:55:00.508	debug	[onStateChange] "shelly.0.shellyplus1#441793ab4310#1.Relay0.Switch" state changed: {"val":false,"ack":false,"ts":1751961300038,"q":0,"c":"script.js.Energie_Strom.TestWW","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1751885460060} - forwarding to objectHelper

                          Und noch ein weiteres Log

                          
shelly.0
2025-07-08 10:12:01.160	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"

shelly.0
2025-07-08 10:12:01.120	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"

shelly.0
2025-07-08 10:12:01.117	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)

shelly.0
2025-07-08 10:12:01.117	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:12:01.117	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:12:01.054	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)

shelly.0
2025-07-08 10:12:01.054	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:12:01.054	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:12:00.997	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"

shelly.0
2025-07-08 10:12:00.948	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)

shelly.0
2025-07-08 10:12:00.947	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:12:00.947	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:59.212	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on

shelly.0
2025-07-08 10:11:59.212	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761

shelly.0
2025-07-08 10:11:59.211	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00

shelly.0
2025-07-08 10:11:58.026	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1"]

shelly.0
2025-07-08 10:11:56.630	debug	[MQTT Server] Close for 192.168.178.76 ((undefined / undefined / undefined))

shelly.0
2025-07-08 10:11:56.630	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:56.630	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: false

shelly.0
2025-07-08 10:11:56.630	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1)

shelly.0
2025-07-08 10:11:56.630	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) (false)

shelly.0
2025-07-08 10:11:56.629	debug	[MQTT Server] End for 192.168.178.76 ((shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1))

shelly.0
2025-07-08 10:11:52.882	debug	[deviceStatusUpdate] shellyplus1#78ee4cc5972c#1: false

shelly.0
2025-07-08 10:11:52.877	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#b0a7324c9984#1"]

shelly.0
2025-07-08 10:11:52.290	debug	[MQTT Server] Close for 192.168.178.63 ((undefined / undefined / undefined))

shelly.0
2025-07-08 10:11:52.290	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:52.290	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: false

shelly.0
2025-07-08 10:11:52.290	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1)

shelly.0
2025-07-08 10:11:52.289	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) (false)

shelly.0
2025-07-08 10:11:52.289	debug	[MQTT Server] End for 192.168.178.63 ((shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1))

shelly.0
2025-07-08 10:11:50.193	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplusplugs#e465b85e4500#1","shellyplus1#b0a7324c9984#1"]

shelly.0
2025-07-08 10:11:50.040	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplusplugs#e465b85e4500#1"]

shelly.0
2025-07-08 10:11:49.919	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126856

shelly.0
2025-07-08 10:11:49.875	debug	[onlineCheck] Checking shellyplus1#78ee4cc5972c#1 on 192.168.178.78:80

shelly.0
2025-07-08 10:11:49.345	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: true

shelly.0
2025-07-08 10:11:49.336	debug	[onlineCheck] Checking shellyplus1#b0a7324c9984#1 on 192.168.178.76:80

shelly.0
2025-07-08 10:11:48.720	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: true

shelly.0
2025-07-08 10:11:48.716	debug	[onlineCheck] Checking shellyplus1#441793ab4310#1 on 192.168.178.63:80

shelly.0
2025-07-08 10:11:48.478	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: true

shelly.0
2025-07-08 10:11:48.474	debug	[onlineCheck] Checking shellyplusplugs#e465b85e4500#1 on 192.168.178.44:80

shelly.0
2025-07-08 10:11:48.456	debug	[deviceStatusUpdate] SHPLG-1#8FF28C#1: true

shelly.0
2025-07-08 10:11:48.434	debug	[onlineCheck] Checking SHPLG-1#8FF28C#1 on 192.168.178.43:80

shelly.0
2025-07-08 10:11:48.317	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) for mode: <not set>

shelly.0
2025-07-08 10:11:46.640	info	[MQTT] Device with client id "shellyplus1-b0a7324c9984" connected from 192.168.178.76!

shelly.0
2025-07-08 10:11:46.639	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:46.637	debug	[BaseClient] Destroying 192.168.178.76 (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:46.636	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":96,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-b0a7324c9984","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}

shelly.0
2025-07-08 10:11:46.632	debug	[MQTT Server] New connection from 192.168.178.76

shelly.0
2025-07-08 10:11:45.244	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1"]

shelly.0
2025-07-08 10:11:44.794	debug	[MQTT Server] Close for 192.168.178.44 ((undefined / undefined / undefined))

shelly.0
2025-07-08 10:11:44.793	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:44.793	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: false

shelly.0
2025-07-08 10:11:44.793	debug	[BaseClient] Destroying (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1)

shelly.0
2025-07-08 10:11:44.793	info	[MQTT] Client Close: (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) (false)

shelly.0
2025-07-08 10:11:44.791	debug	[MQTT Server] End for 192.168.178.44 ((shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1))

shelly.0
2025-07-08 10:11:43.188	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) for mode: <not set>

shelly.0
2025-07-08 10:11:42.296	info	[MQTT] Device with client id "shellyplus1-441793ab4310" connected from 192.168.178.63!

shelly.0
2025-07-08 10:11:42.296	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:42.296	debug	[BaseClient] Destroying 192.168.178.63 (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:42.296	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":96,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-441793ab4310","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}

shelly.0
2025-07-08 10:11:42.295	debug	[MQTT Server] New connection from 192.168.178.63

shelly.0
2025-07-08 10:11:35.819	debug	[createObjects] Starting object creation of (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) for mode: <not set>

shelly.0
2025-07-08 10:11:34.796	info	[MQTT] Device with client id "shellyplusplugs-e465b85e4500" connected from 192.168.178.44!

shelly.0
2025-07-08 10:11:34.795	debug	[MQTT] Destroying

shelly.0
2025-07-08 10:11:34.795	debug	[BaseClient] Destroying 192.168.178.44 (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:34.795	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":82,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplusplugs-e465b85e4500","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}

shelly.0
2025-07-08 10:11:34.794	debug	[MQTT Server] New connection from 192.168.178.44

shelly.0
2025-07-08 10:11:33.660	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126839

shelly.0
2025-07-08 10:11:29.209	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on

shelly.0
2025-07-08 10:11:29.208	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761

shelly.0
2025-07-08 10:11:29.207	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00

host.iobroker
2025-07-08 10:11:24.910	info	instance system.adapter.dwd.0 having pid 27773 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

dwd.0
2025-07-08 10:11:23.252	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

shelly.0
2025-07-08 10:11:18.409	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.rssi, value: -63

shelly.0
2025-07-08 10:11:18.409	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126824

shelly.0
2025-07-08 10:11:12.338	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"

shelly.0
2025-07-08 10:11:12.291	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)

shelly.0
2025-07-08 10:11:12.291	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:11:12.290	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:12.258	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"

shelly.0
2025-07-08 10:11:12.149	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)

shelly.0
2025-07-08 10:11:12.148	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:11:12.147	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

shelly.0
2025-07-08 10:11:12.144	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"

shelly.0
2025-07-08 10:11:12.073	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)

shelly.0
2025-07-08 10:11:12.073	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}

shelly.0
2025-07-08 10:11:12.073	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)

                          was kann ich tun?

                          mcm1957M Online
                          mcm1957M Online
                          mcm1957
                          schrieb am zuletzt editiert von
                          #36

                          @icebear
                          Das Problem ist bekannt. Die Ursache leider nicht. @haus-automatisierung konnte bisher keine Ursache eingrenzen und daher leider auch nichts unternehmen.

                          Siehe z.B.
                          https://github.com/iobroker-community-adapters/ioBroker.shelly/issues/931

                          Danke jedenfalls für den Log.

                          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                          Support Repositoryverwaltung.

                          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                          LESEN - gute Forenbeitrage

                          1 Antwort Letzte Antwort
                          1
                          • haus-automatisierungH haus-automatisierung

                            @rene55 Version 10.1.0 sollte den Schlüssel bestätigen und entsprechend mit ack true neu schreiben.

                            Rene55R Offline
                            Rene55R Offline
                            Rene55
                            schrieb am zuletzt editiert von
                            #37

                            @haus-automatisierung Mit 10.1.0 und nochmaligem Eingeben des Encryption-Keys ist er jetzt ohne Bindestriche und bestätigt.

                            Host: Fujitsu Intel(R) Pentium(R) CPU G4560T, 32 GB RAM, Proxmox 8.x + lxc Ubuntu 22.04
                            ioBroker (8 GB RAM) Node.js: 20.19.1, NPM: 10.8.2, js-Controller: 7.0.6, Admin: 7.6.3
                            Wetterstation: Froggit WH3000SE V1.6.6

                            1 Antwort Letzte Antwort
                            1
                            • mcm1957M mcm1957
                              Aktuelle Test Version 10.4.1
                              Veröffentlichungsdatum 3.11.2025
                              Github Link https://github.com/iobroker-community-adapters/ioBroker.shelly

                              Zum Thema Shelly gibt es mehrere aktive Topics. Bitte das am besten passende Topic benutzen:

                              Shelly Topics
                              Shelly ALPHA Tests https://forum.iobroker.net/topic/80649/test-adapter-shelly-alpha-versionen
                              Shelly STABLE Fragen https://forum.iobroker.net/topic/81297/shelly-adapter-genereller-support

                              Für den Adapter ioBroker.shelly steht eine neue Release im BETA / LATEST Repository (ab dem nächsten Update) zu Testzwecken zur Verfügung.

                              Hinweis:
                              Dieses Topic behandelt die offizielle LATEST Version des Adapters. Informationen zu ALPHA Versionen findet sich hier: https://forum.iobroker.net/topic/80649/test-adapter-shelly-alpha-versionen

                              Feedback jeder Art - insbesondere auch ok - funktioniert ist gerne gesehen.

                              Changelog

                              9.3.0 (2025-04-14)

                              • (@klein0r) Adapter requires admin 7.4.10 now.
                              • (@mcm1957) Added Shelly Outdoor Plug S Gen3
                              • (@mcm1957) Missing energy values for Switches (i.e. Shelly Outdoor Plug S Gen3) have been added
                              • (@mcm1957) Missing energy values for pmminigen3 have been added

                              9.4.0 (2025-04-16)

                              • (@klein0r) Added Gen4 devices (see documentation for details)

                              9.4.1 (2025-04-17)

                              • (@mcm1957) Minimum value for min_brightness fixed for dimmer1/2 [#1166]

                              9.5.0 (2025-05-03)

                              • (@mcm1957) Added Shelly Pro Dimmer 0/1-10V PM (shellypro0110pm).
                              • (@mcm1957) Added Shelly Pro RGBWW PM (shellyprorgbwwpm) - Note: CCT component still missing.
                              • (@mcm1957) Added Shelly AZ Plug (shellyazplug).
                              • (@mcm1957) Added Shelly EM Gen 3 (shellyemg3).
                              • (@mcm1957) Added 'total returned energy' to Gen2+ EM devices.
                              • (@mcm1957) Added 'Relay' to Shelly Pro EM 50 [#1038].
                              • (@mcm1957) Added Ogemray 25A (ogemray25a).
                              • (@mcm1957) Added energy states to Shelly Plus RBGW PM (shellyrgbwpm) [#1099].
                              • (@mcm1957) Added energy states to Shelly Pro Dimmer 1 PM (shellyprodm1pm) [#1129].
                              • (@mcm1957) Added energy states to Shelly Pro Dimmer 2 PM (shellyprodm2pm) [#1067, #1056, #1037].
                              • (@mcm1957) Added energy states to Shelly Plus 0-10V Dimmer Gen 3 (shelly0110dimg3) [#1103].

                              9.5.1 (2025-05-10)

                              • (@mcm1957) ATTENTION: Reworked configuration of inputs could effect some devices.
                              • (@mcm1957) ResetPower has been added to Shelly switches supporting power measurement. [#1156]
                              • (@mcm1957) ResetPower has been added to Gen2+ PM type devices.
                              • (@mcm1957) Shelly Plus Uni (shellyplusuni) - configuration of inputs reworked.
                              • (@mcm1957) Shelly Plus Uni (shellyplusuni) - support to reset counters added.
                              • (@mcm1957) Added sensors (Temperature, Voltmeter, Humidity, analog Input) to Shelly Plus Uni (shellyplusuni).
                              • (@mcm1957) Issues reported by repositor checker have been fixed.
                              • (@mcm1957) Dependencies have been updated

                              10.0.0 (2025-05-30)

                              • (@klein0r) Moved BTHome decoding to adapter (save memory on devices)
                              • (@klein0r) Allow encrypted payloads of BTHome devices (set encryption key in state)

                              10.1.0 (2025-06-30)

                              • (@klein0r) Allow infinite event listeners
                              • (@klein0r) Added transformed voltage for voltmeter
                              • (@klein0r) Improved logging of mqtt authentication failures
                              • (@klein0r) Acknowledge new encryption keys for bthome encryption

                              10.2.0 (2025-09-09)

                              • (@mcm1957) Role definitions for anergy states has been corrected [#1195].
                              • (@mcm1957) Shelly Dali Dimmer Gen 3 (shellyddimmerg3) has been added.
                              • (@mcm1957) Shelly1L Gen 3 (shelly1lg3) has been added.
                              • (@mcm1957) Shelly2L Gen 3 (shelly2lg3) has been added.
                              • (@mcm1957) Shelly2PM Gen 4 (shelly2pmg4) has been added. (*)
                              • (@klein0r) Shelly Shutter Gen 3 (shellyshutter) has been added.
                              • (@klein0r) admin 7.6.17 and js-controller 6.0.11 (or later) are required now.
                              • (@mcm1957) Dependencies have been updated

                              10.3.0 (2025-10-06)

                              • (@klein0r) Rssi for ble has been added to script.
                              • (@mcm1957) Shelly Flood Gen 4 (shellyfloodg4) has been added.
                              • (@mcm1957) Shelly Power Strip Gen 4 (shellypstripg4) has been added with partial support. (*)

                              (*) slat functionality not yet implemented

                              10.4.0 (2025-10-13)

                              • (@mcm1957) Slat control added to Shelly ProDualCoverPM, Shelly Pro2PM, Shelly Shutter, Shelly Plus 2PM, Shelly 2PM Gen 3 and Shelly 2PM Gen 4.
                              • (@mcm1957) Log adapter version if unknown device is detected.
                              • (@mcm1957) posControl indicator has been added to devices supporting cover operation.
                              • (@mcm1957) Dependencies have been updated

                              10.4.1 (2025-11-03)

                              • (@mcm1957) Shelly pro 3em400 has been added as dedicated device to improve detectio (shellypro3em400) [#1269].
                              • (@mcm1957) Missing energy states have been added to Shelly Dimmer Gen 3 (shellydimmerg3) [#1274].
                              • (@klein0r) Added distance support to ble sensors
                              • (@mcm1957) Dependencies have been updated
                              HumidorH Offline
                              HumidorH Offline
                              Humidor
                              schrieb am zuletzt editiert von Humidor
                              #38

                              @mcm1957 Hallo! erstmal wieder Danke für eure tolle Arbeit!
                              ich habe auf die letzte Version vom Adapter und das 1.0 Script für die BLE installiert.
                              Leider bekomme ich keine Infos mehr von den BLE BT Geräten mehr?
                              Tja, wo muss ich denn da jetzt nachsehen? BG
                              in der Shelly App sind die Geräte drin und zeigen den korrekten Zustand
                              im Shelly BLE Server ist das Script 1.0 gestartet und läuft

                              -> hab grad nachgesehen, das Script ist nicht gelaufen, ich habe es gestartet, OK.. neu gestartet und JA es funktoniert natürlich wieder ! 👍

                              BG

                              mcm1957M 1 Antwort Letzte Antwort
                              1
                              • HumidorH Humidor

                                @mcm1957 Hallo! erstmal wieder Danke für eure tolle Arbeit!
                                ich habe auf die letzte Version vom Adapter und das 1.0 Script für die BLE installiert.
                                Leider bekomme ich keine Infos mehr von den BLE BT Geräten mehr?
                                Tja, wo muss ich denn da jetzt nachsehen? BG
                                in der Shelly App sind die Geräte drin und zeigen den korrekten Zustand
                                im Shelly BLE Server ist das Script 1.0 gestartet und läuft

                                -> hab grad nachgesehen, das Script ist nicht gelaufen, ich habe es gestartet, OK.. neu gestartet und JA es funktoniert natürlich wieder ! 👍

                                mcm1957M Online
                                mcm1957M Online
                                mcm1957
                                schrieb am zuletzt editiert von
                                #39

                                @humidor
                                Dankje fürs Feedback. UInd sorry, dass ich nicht früher antworten konnte.

                                Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                Support Repositoryverwaltung.

                                Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                LESEN - gute Forenbeitrage

                                mcm1957M 1 Antwort Letzte Antwort
                                1
                                • mcm1957M mcm1957

                                  @humidor
                                  Dankje fürs Feedback. UInd sorry, dass ich nicht früher antworten konnte.

                                  mcm1957M Online
                                  mcm1957M Online
                                  mcm1957
                                  schrieb am zuletzt editiert von
                                  #40

                                  @mcm1957

                                  Release 10.2.0 wurde ins Latest entlassen.
                                  Details siehe Releasenotes.

                                  Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                  Support Repositoryverwaltung.

                                  Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                  LESEN - gute Forenbeitrage

                                  mcm1957M 1 Antwort Letzte Antwort
                                  0
                                  • mcm1957M mcm1957

                                    @mcm1957

                                    Release 10.2.0 wurde ins Latest entlassen.
                                    Details siehe Releasenotes.

                                    mcm1957M Online
                                    mcm1957M Online
                                    mcm1957
                                    schrieb am zuletzt editiert von
                                    #41

                                    Release 10.2.0 wurde ins STABLE Repository entlassen.

                                    Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                    Support Repositoryverwaltung.

                                    Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                    LESEN - gute Forenbeitrage

                                    mcm1957M 1 Antwort Letzte Antwort
                                    1
                                    • mcm1957M mcm1957

                                      Release 10.2.0 wurde ins STABLE Repository entlassen.

                                      mcm1957M Online
                                      mcm1957M Online
                                      mcm1957
                                      schrieb am zuletzt editiert von
                                      #42

                                      Release 10.3.0 wurde ins Latest entlassen.
                                      Details siehe Releasenotes.

                                      Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                      Support Repositoryverwaltung.

                                      Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                      LESEN - gute Forenbeitrage

                                      1 Antwort Letzte Antwort
                                      2
                                      • mcm1957M Online
                                        mcm1957M Online
                                        mcm1957
                                        schrieb am zuletzt editiert von
                                        #43

                                        Release 10.4.0 wurde ins Latest entlassen.
                                        Details siehe Releasenotes.

                                        Die wesentliche Änderung ist der Support der slat Funktion (Lamellenneigung) bei allen Shellies die diese Funktion unterstützen.

                                        Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                        Support Repositoryverwaltung.

                                        Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                        LESEN - gute Forenbeitrage

                                        mcm1957M 1 Antwort Letzte Antwort
                                        2
                                        • mcm1957M mcm1957

                                          Release 10.4.0 wurde ins Latest entlassen.
                                          Details siehe Releasenotes.

                                          Die wesentliche Änderung ist der Support der slat Funktion (Lamellenneigung) bei allen Shellies die diese Funktion unterstützen.

                                          mcm1957M Online
                                          mcm1957M Online
                                          mcm1957
                                          schrieb am zuletzt editiert von mcm1957
                                          #44

                                          Release 10.4.0 wurde ins STABLE entlassen.

                                          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                          Support Repositoryverwaltung.

                                          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                          LESEN - gute Forenbeitrage

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

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          502

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          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