Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • 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. Shellys reagieren nicht mehr

NEWS

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    1.6k

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    10
    1
    674

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    1.2k

Shellys reagieren nicht mehr

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
2 Beiträge 1 Kommentatoren 307 Aufrufe 1 Beobachtet
  • Ä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.
  • M Offline
    M Offline
    M1R0O
    schrieb am zuletzt editiert von Homoran
    #1

    Hi zusammen,
    seit wenigen Tagen lassen sich meine Shellys nicht mehr schalten.

    Alle haben den Status online. Wenn ich aber den switch in den Objekten auf true setze, passiert gar nichts.

    Über die Shelly-App klappt alles problemlos.

    Hier das debug-Log, mit fehlgeschlagenen Schaltvorgängen?!

     2023-01-14 16:46:43.049 - info: shelly.0 (19931) starting. Version 6.0.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v16.19.0, js-controller: 4.0.24
    2023-01-14 16:46:43.287 - info: shelly.0 (19931) Starting in CoAP mode.
    2023-01-14 16:46:43.289 - debug: shelly.0 (19931) [CoAP Server] Starting shelly listener with options: {"user":"...","password":".....","multicastInterface":null}
    2023-01-14 16:46:43.361 - info: shelly.0 (19931) [CoAP Server] Listening for packets in the network
    2023-01-14 16:46:43.392 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#2C7EDC#1.hostname on 192.168.178.60:80
    2023-01-14 16:46:43.399 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#5553D6#1.hostname on 192.168.178.39:80
    2023-01-14 16:46:43.401 - debug: shelly.0 (19931) [onlineCheck] Checking SHRGBW2#80E360#1.hostname on 192.168.178.66:80
    2023-01-14 16:46:43.405 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#5553D6#1: true
    2023-01-14 16:46:43.406 - debug: shelly.0 (19931) [onlineCheck] Checking SHRGBW2#A69531#1.hostname on 192.168.178.67:80
    2023-01-14 16:46:43.410 - debug: shelly.0 (19931) [deviceStatusUpdate] SHRGBW2#80E360#1: true
    2023-01-14 16:46:43.411 - debug: shelly.0 (19931) [onlineCheck] Checking SHIX3-1#10521CF2CD40#1.hostname on 192.168.178.68:80
    2023-01-14 16:46:43.415 - debug: shelly.0 (19931) [deviceStatusUpdate] SHRGBW2#A69531#1: true
    2023-01-14 16:46:43.417 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#3494546A2571#1.hostname on 192.168.178.108:80
    2023-01-14 16:46:43.421 - debug: shelly.0 (19931) [deviceStatusUpdate] SHIX3-1#10521CF2CD40#1: true
    2023-01-14 16:46:43.423 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#3494546A2571#1: true
    2023-01-14 16:46:43.494 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#3494546ACE3A#1.hostname on 192.168.178.114:80
    2023-01-14 16:46:43.500 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#3494546ACE3A#1: true
    2023-01-14 16:46:43.580 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#E89F6D85A6AF#1.hostname on 192.168.178.127:80
    2023-01-14 16:46:43.588 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#E89F6D85A6AF#1: true
    2023-01-14 16:46:43.651 - debug: shelly.0 (19931) [deviceStatusUpdate] Online devices: ["SHSW-1#5553D6#1"]
    2023-01-14 16:46:43.653 - debug: shelly.0 (19931) [deviceStatusUpdate] Online devices: ["SHSW-1#5553D6#1","SHRGBW2#80E360#1"]
    2023-01-14 16:46:43.662 - debug: shelly.0 (19931) [deviceStatusUpdate] Online devices: ["SHSW-1#5553D6#1","SHRGBW2#80E360#1","SHRGBW2#A69531#1"]
    2023-01-14 16:46:43.663 - debug: shelly.0 (19931) [deviceStatusUpdate] Online devices: ["SHSW-1#5553D6#1","SHRGBW2#80E360#1","SHRGBW2#A69531#1","SHIX3-1#10521CF2CD40#1"]
    2023-01-14 16:46:43.664 - debug: shelly.0 (19931) [deviceStatusUpdate] Online devices: ["SHSW-1#5553D6#1","SHRGBW2#80E360#1","SHRGBW2#A69531#1","SHIX3-1#10521CF2CD40#1","SHSW-1#3494546A2571#1"]
    2023-01-14 16:46:43.676 - debug: shelly.0 (19931) [deviceStatusUpdate] Online devices: ["SHSW-1#5553D6#1","SHRGBW2#80E360#1","SHRGBW2#A69531#1","SHIX3-1#10521CF2CD40#1","SHSW-1#3494546A2571#1","SHSW-1#3494546ACE3A#1"]
    2023-01-14 16:46:43.722 - debug: shelly.0 (19931) [deviceStatusUpdate] Online devices: ["SHSW-1#5553D6#1","SHRGBW2#80E360#1","SHRGBW2#A69531#1","SHIX3-1#10521CF2CD40#1","SHSW-1#3494546A2571#1","SHSW-1#3494546ACE3A#1","SHSW-1#E89F6D85A6AF#1"]
    2023-01-14 16:46:46.496 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#2C7EDC#1: false
    2023-01-14 16:46:57.830 - debug: shelly.0 (19931) [onStateChange] "shelly.0.SHSW-1#5553D6#1.Relay0.Switch" state changed: {"val":false,"ack":false,"ts":1673711217823,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1673711217823} - forwarding to objectHelper
    2023-01-14 16:47:02.453 - debug: shelly.0 (19931) [onStateChange] "shelly.0.SHSW-1#5553D6#1.Relay0.Switch" state changed: {"val":true,"ack":false,"ts":1673711222446,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1673711222446} - forwarding to objectHelper
    2023-01-14 16:47:43.636 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#2C7EDC#1.hostname on 192.168.178.60:80
    2023-01-14 16:47:43.642 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#5553D6#1.hostname on 192.168.178.39:80
    2023-01-14 16:47:43.646 - debug: shelly.0 (19931) [onlineCheck] Checking SHRGBW2#80E360#1.hostname on 192.168.178.66:80
    2023-01-14 16:47:43.652 - debug: shelly.0 (19931) [onlineCheck] Checking SHRGBW2#A69531#1.hostname on 192.168.178.67:80
    2023-01-14 16:47:43.656 - debug: shelly.0 (19931) [onlineCheck] Checking SHIX3-1#10521CF2CD40#1.hostname on 192.168.178.68:80
    2023-01-14 16:47:43.661 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#3494546A2571#1.hostname on 192.168.178.108:80
    2023-01-14 16:47:43.664 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#3494546ACE3A#1.hostname on 192.168.178.114:80
    2023-01-14 16:47:43.667 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#3494546A2571#1: true
    2023-01-14 16:47:43.671 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#E89F6D85A6AF#1.hostname on 192.168.178.127:80
    2023-01-14 16:47:43.683 - debug: shelly.0 (19931) [deviceStatusUpdate] SHIX3-1#10521CF2CD40#1: true
    2023-01-14 16:47:43.685 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#5553D6#1: true
    2023-01-14 16:47:43.687 - debug: shelly.0 (19931) [deviceStatusUpdate] SHRGBW2#80E360#1: true
    2023-01-14 16:47:43.689 - debug: shelly.0 (19931) [deviceStatusUpdate] SHRGBW2#A69531#1: true
    2023-01-14 16:47:43.691 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#3494546ACE3A#1: true
    2023-01-14 16:47:43.699 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#E89F6D85A6AF#1: true
    2023-01-14 16:47:46.731 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#2C7EDC#1: false
    2023-01-14 16:48:43.712 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#2C7EDC#1.hostname on 192.168.178.60:80
    2023-01-14 16:48:43.715 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#5553D6#1.hostname on 192.168.178.39:80
    2023-01-14 16:48:43.718 - debug: shelly.0 (19931) [onlineCheck] Checking SHRGBW2#80E360#1.hostname on 192.168.178.66:80
    2023-01-14 16:48:43.721 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#5553D6#1: true
    2023-01-14 16:48:43.723 - debug: shelly.0 (19931) [onlineCheck] Checking SHRGBW2#A69531#1.hostname on 192.168.178.67:80
    2023-01-14 16:48:43.726 - debug: shelly.0 (19931) [deviceStatusUpdate] SHRGBW2#80E360#1: true
    2023-01-14 16:48:43.728 - debug: shelly.0 (19931) [onlineCheck] Checking SHIX3-1#10521CF2CD40#1.hostname on 192.168.178.68:80
    2023-01-14 16:48:43.738 - debug: shelly.0 (19931) [deviceStatusUpdate] SHIX3-1#10521CF2CD40#1: true
    2023-01-14 16:48:43.771 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#3494546A2571#1.hostname on 192.168.178.108:80
    2023-01-14 16:48:43.775 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#3494546A2571#1: true
    2023-01-14 16:48:43.790 - debug: shelly.0 (19931) [deviceStatusUpdate] SHRGBW2#A69531#1: true
    2023-01-14 16:48:43.824 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#3494546ACE3A#1.hostname on 192.168.178.114:80
    2023-01-14 16:48:43.826 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#E89F6D85A6AF#1.hostname on 192.168.178.127:80
    2023-01-14 16:48:43.831 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#3494546ACE3A#1: true
    2023-01-14 16:48:43.833 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#E89F6D85A6AF#1: true
    2023-01-14 16:48:46.811 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#2C7EDC#1: false
    2023-01-14 16:49:00.094 - info: host.raspberrypi instance system.adapter.mobile-alerts.0 started with pid 23364
    2023-01-14 16:49:03.028 - info: mobile-alerts.0 (23364) starting. Version 0.5.1 (non-npm: bluerai/ioBroker.mobile-alerts#98c3185661866676db1a97ed5b9e14455fb63bb9) in /opt/iobroker/node_modules/iobroker.mobile-alerts, node: v16.19.0, js-controller: 4.0.24
    2023-01-14 16:49:11.638 - warn: admin.0 (13915) Read-only state "shelly.0.SHSW-1#5553D6#1.ext.switch1" has been written without ack-flag with value "true"
    2023-01-14 16:49:11.648 - debug: shelly.0 (19931) [onStateChange] "shelly.0.SHSW-1#5553D6#1.ext.switch1" state changed: {"val":true,"ack":false,"ts":1673711351645,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1673711351645} - forwarding to objectHelper
    2023-01-14 16:49:17.017 - warn: admin.0 (13915) Read-only state "shelly.0.SHSW-1#5553D6#1.ext.switch1" has been written without ack-flag with value "false"
    2023-01-14 16:49:17.022 - debug: shelly.0 (19931) [onStateChange] "shelly.0.SHSW-1#5553D6#1.ext.switch1" state changed: {"val":false,"ack":false,"ts":1673711357019,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1673711357019} - forwarding to objectHelper
    2023-01-14 16:49:29.349 - info: host.raspberrypi instance system.adapter.mobile-alerts.0 terminated with code 0 (NO_ERROR)
    2023-01-14 16:49:31.959 - debug: shelly.0 (19931) [onStateChange] "shelly.0.SHSW-1#5553D6#1.Relay0.Switch" state changed: {"val":false,"ack":false,"ts":1673711371953,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1673711371953} - forwarding to objectHelper
    2023-01-14 16:49:43.858 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#2C7EDC#1.hostname on 192.168.178.60:80
    2023-01-14 16:49:43.860 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#5553D6#1.hostname on 192.168.178.39:80
    2023-01-14 16:49:43.863 - debug: shelly.0 (19931) [onlineCheck] Checking SHRGBW2#80E360#1.hostname on 192.168.178.66:80
    2023-01-14 16:49:43.866 - debug: shelly.0 (19931) [onlineCheck] Checking SHRGBW2#A69531#1.hostname on 192.168.178.67:80
    2023-01-14 16:49:43.869 - debug: shelly.0 (19931) [onlineCheck] Checking SHIX3-1#10521CF2CD40#1.hostname on 192.168.178.68:80
    2023-01-14 16:49:43.872 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#3494546A2571#1.hostname on 192.168.178.108:80
    2023-01-14 16:49:43.875 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#3494546ACE3A#1.hostname on 192.168.178.114:80
    2023-01-14 16:49:43.877 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#3494546A2571#1: true
    2023-01-14 16:49:43.878 - debug: shelly.0 (19931) [onlineCheck] Checking SHSW-1#E89F6D85A6AF#1.hostname on 192.168.178.127:80
    2023-01-14 16:49:43.902 - debug: shelly.0 (19931) [deviceStatusUpdate] SHIX3-1#10521CF2CD40#1: true
    2023-01-14 16:49:43.904 - debug: shelly.0 (19931) [deviceStatusUpdate] SHRGBW2#80E360#1: true
    2023-01-14 16:49:43.905 - debug: shelly.0 (19931) [deviceStatusUpdate] SHRGBW2#A69531#1: true
    2023-01-14 16:49:43.908 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#3494546ACE3A#1: true
    2023-01-14 16:49:43.909 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#E89F6D85A6AF#1: true
    2023-01-14 16:49:43.911 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#5553D6#1: true
    2023-01-14 16:49:46.971 - debug: shelly.0 (19931) [deviceStatusUpdate] SHSW-1#2C7EDC#1: false
    2023-01-14 16:50:05.558 - debug: shelly.0 (19931) [onStateChange] "shelly.0.SHSW-1#5553D6#1.Relay0.Switch" state changed: {"val":false,"ack":false,"ts":1673711405554,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1673711405554} - forwarding to objectHelper
    2023-01-14 16:50:10.684 - debug: shelly.0 (19931) [onStateChange] "shelly.0.SHSW-1#5553D6#1.Relay0.Switch" state changed: {"val":true,"ack":false,"ts":1673711410680,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1673711410680} - forwarding to objectHelper
    
    


    MOD-EDIT: private Daten entfernt!

    Ich bin nicht firm genug, um selber herauszufinden, woran es liegt.
    Kannst du helfen?

    Danke!

    1 Antwort Letzte Antwort
    0
    • M Offline
      M Offline
      M1R0O
      schrieb am zuletzt editiert von
      #2

      Moin,

      ich habe es selber gelöst.
      Erst dachte ich, das Problem sei, dass sich die Shellys mit meinem Repeater im OG verbunden hatten. Also im Repeater alle via MAC-Adresse gesperrt. Keine Änderung.

      Dann habe ich den Adapter neu installiert und die COAP-Verbindung mit IP und Port 5683 eingetragen und nu klappt es wieder.

      1 Antwort Letzte Antwort
      0

      Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

      Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

      Mit deinem Input könnte dieser Beitrag noch besser werden 💗

      Registrieren Anmelden
      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

      311

      Online

      32.9k

      Benutzer

      83.0k

      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