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 - ALPHA Versionen

NEWS

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

  • 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 - ALPHA Versionen

Geplant Angeheftet Gesperrt Verschoben Tester
mcm1957shelly
168 Beiträge 20 Kommentatoren 20.1k Aufrufe 24 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.
  • haus-automatisierungH haus-automatisierung

    @stenmic RPC Events nicht aktiviert in der Shelly MQTT Konfiguration?

    S Offline
    S Offline
    stenmic
    schrieb am zuletzt editiert von stenmic
    #65

    @haus-automatisierung
    das sollte eigentlich passen, oder?
    2025-05-29 06 39 02.jpg

    1 Antwort Letzte Antwort
    0
    • mcm1957M mcm1957

      @stenmic

      So wie ich es sehe bekommt der Adapter die Meldung via mqtt. Damit stellt sich die Frage:

      Kommt die Änderung verzögert, sprich du änderst den Wert in der shelly app / im Webinterface und der State im ioBroker wird erst nach x Sekunden angepasst?

      Oder wird im ioBroker IMMER das Gegenteil von dem angezeigt was tatsächlich eingestellt ist?

      Was passiert wenn du den State direkt in ioBroker admin umstellst?

      Ev. hol mag die json mit Output von http://ogemray-ip/rpc/Shelly.GetStatus ab und zwar sowohl im eingeschalteten als auch im ausgeschalteten Zustand und poste die (bitte dazu schreiben welches json zu ein / aus gehört). Alternativ zum posten auch gern im Issue gesehen.

      Und - wenn es das Relay kann - stell mal nen Timer ein der das Relais nach x Sekunden ein bzw. ausschaltet und beobachte ob / was sich im ioBroker State tut.

      Arbeitshypothese:
      Das Ding schickt den Status zeitlich verzögert ODER das Ding schickt den Status invertiert ...
      Da der switch Modul nicht spezifisch für dieses Relay ist sollte dort eigentlich kein Fehler drinnen sein... Aber wer weiß.

      fuzzy1955F Online
      fuzzy1955F Online
      fuzzy1955
      schrieb am zuletzt editiert von fuzzy1955
      #66

      @mcm1957 sagte in Test Adapter shelly - ALPHA Versionen:

      Da der switch Modul nicht spezifisch für dieses Relay ist sollte dort eigentlich kein Fehler drinnen sein

      Hallo @mcm1957,

      seit ich die Shelly-Version v9.5.1-alpha.8 installiert habe, funktioniert das Steuern aus dem IOB nicht mehr. Sowohl das manuelle Schalten über die Web-Adresse des Shelly oder über die Objekte im IOB, als auch das Steuern via JavaScript im IOB laufen nicht mehr. Auch die Temperaturen des ShellyPlus1Addon werden im IOB nicht korrekt angezeigt.

      Clipboard01.jpg

      Clipboard02.jpg

      Clipboard03.jpg

      Clipboard05.jpg

      Protokoll silly


      shelly.0
      2025-05-29 07:46:49.662 debug [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748497609654,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper

      shelly.0
      2025-05-29 07:46:49.661 silly States user redis pmessage shelly.0.*/shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent:{"val":0,"ack":false,"ts":1748497609654,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244}

      shelly.0
      2025-05-29 07:46:44.041 debug [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness" state changed: {"val":0,"ack":false,"ts":1748497604035,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668} - forwarding to objectHelper

      shelly.0
      2025-05-29 07:46:44.040 silly States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness:{"val":0,"ack":false,"ts":1748497604035,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668}

      shelly.0
      2025-05-29 07:46:44.038 debug [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch" state changed: {"val":false,"ack":false,"ts":1748497604035,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543} - forwarding to objectHelper

      shelly.0
      2025-05-29 07:46:44.038 silly States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch:{"val":false,"ack":false,"ts":1748497604035,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543}

      shelly.0
      2025-05-29 07:46:42.005 debug [deviceStatusUpdate] shellyplus1#78ee4ccff568#1: true

      shelly.0
      2025-05-29 07:46:42.001 debug [onlineCheck] Checking shellyplus1#78ee4ccff568#1 on 192.168.0.101:80

      shelly.0
      2025-05-29 07:46:42.001 debug [deviceStatusUpdate] shellyplusplugs#e465b8b35bdc#1: true

      shelly.0
      2025-05-29 07:46:41.997 debug [deviceStatusUpdate] shellypro0110pm#8813bfe0db54#1: true

      shelly.0
      2025-05-29 07:46:41.997 debug [onlineCheck] Checking shellyplusplugs#e465b8b35bdc#1 on 192.168.0.105:80

      shelly.0
      2025-05-29 07:46:41.995 debug [onlineCheck] Checking shellypro0110pm#8813bfe0db54#1 on 192.168.0.102:80

      iob diag


      ========== Start marking the full check here ===========

      Script v.2025-03-08
      
      *** BASE SYSTEM ***
       Static hostname: raspberrypi
             Icon name: computer
      Operating System: Debian GNU/Linux 12 (bookworm)
                Kernel: Linux 6.12.25+rpt-rpi-2712
          Architecture: arm64
      OS is similar to:
      
      Model           : Raspberry Pi 5 Model B Rev 1.1
      Docker          : false
      Virtualization  : none
      Kernel          : aarch64
      Userland        : 64 bit
      
      Systemuptime and Load:
       07:57:26 up 1 day, 18:23,  2 users,  load average: 0.07, 0.02, 0.00
      CPU threads: 4
      
      
      *** LIFE CYCLE STATUS ***
      Operating System is the current Debian stable version codenamed 'bookworm'!
      
      *** RASPBERRY THROTTLING ***
      Current issues:
      No throttling issues detected.
      
      Previously detected issues:
      No throttling issues detected.
      
      *** TIME AND TIMEZONES ***
                     Local time: Thu 2025-05-29 07:57:26 CEST
                 Universal time: Thu 2025-05-29 05:57:26 UTC
                       RTC time: Thu 2025-05-29 05:57:26
                      Time zone: Europe/Vienna (CEST, +0200)
      System clock synchronized: yes
                    NTP service: active
                RTC in local TZ: no
      
      *** Users and Groups ***
      User that called 'iob diag':
      pi
      HOME=/home/pi
      GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
      
      User that is running 'js-controller':
      iobroker
      HOME=/home/iobroker
      GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c
      
      *** DISPLAY-SERVER SETUP ***
      Display-Server: false
      Desktop:
      Terminal:       tty
      
      *** MEMORY ***
                     total        used        free      shared  buff/cache   available
      Mem:             17G        2.0G         13G        7.6M        1.4G         14G
      Swap:           536M          0B        536M
      Total:           17G        2.0G         14G
      
      Active iob-Instances:   14
      
              16219 M total memory
               1941 M used memory
               1769 M active memory
               1048 M inactive memory
              13054 M free memory
                132 M buffer memory
               1213 M swap cache
                511 M total swap
                  0 M used swap
                511 M free swap
      
      *** top - Table Of Processes  ***
      top - 07:57:27 up 1 day, 18:23,  2 users,  load average: 0.07, 0.02, 0.00
      Tasks: 202 total,   1 running, 201 sleeping,   0 stopped,   0 zombie
      %Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
      MiB Mem :  16219.7 total,  13054.7 free,   1941.5 used,   1345.5 buff/cache
      MiB Swap:    512.0 total,    512.0 free,      0.0 used.  14278.1 avail Mem
      
      *** FAILED SERVICES ***
      
        UNIT LOAD ACTIVE SUB DESCRIPTION
      0 loaded units listed.
      
      
      *** DMESG CRITICAL ERRORS ***
      No critical errors detected
      
      *** FILESYSTEM ***
      Filesystem     Type      Size  Used Avail Use% Mounted on
      udev           devtmpfs  7.9G     0  7.9G   0% /dev
      tmpfs          tmpfs     1.6G  7.3M  1.6G   1% /run
      /dev/mmcblk0p2 ext4       15G   12G  2.0G  86% /
      tmpfs          tmpfs     8.0G     0  8.0G   0% /dev/shm
      tmpfs          tmpfs     5.0M   48K  5.0M   1% /run/lock
      /dev/mmcblk0p1 vfat      510M   56M  455M  11% /boot/firmware
      tmpfs          tmpfs     1.6G     0  1.6G   0% /run/user/1000
      
      Messages concerning ext4 filesystem in dmesg:
      
      Show mounted filesystems:
      TARGET           SOURCE         FSTYPE OPTIONS
      /                /dev/mmcblk0p2 ext4   rw,noatime
      `-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
      
      Files in neuralgic directories:
      
      /var:
      2.3G    /var/
      756M    /var/log
      755M    /var/log/journal/ce49b5c207f74de48fc362bf23ca73ba
      755M    /var/log/journal
      551M    /var/lib
      
      Archived and active journals take up 754.7M in the file system.
      
      /opt/iobroker/backups:
      167M    /opt/iobroker/backups/
      
      /opt/iobroker/iobroker-data:
      1.2G    /opt/iobroker/iobroker-data/
      1.1G    /opt/iobroker/iobroker-data/files
      617M    /opt/iobroker/iobroker-data/files/javascript.admin
      560M    /opt/iobroker/iobroker-data/files/javascript.admin/static
      558M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js
      
      The five largest files in iobroker-data are:
      26M     /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map
      26M     /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map
      24M     /opt/iobroker/iobroker-data/files/vis-2/static/js/main.f305bc29.js.map
      24M     /opt/iobroker/iobroker-data/files/vis-2/static/js/main.8e80ccb0.js.map
      24M     /opt/iobroker/iobroker-data/files/vis-2/customWidgets.js.map
      
      USB-Devices by-id:
      USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':
      
      No Devices found 'by-id'
      
      Zigbee Network Settings on your coordinator/in nvbackup are:
      
      zigbee.X
      Extended Pan ID:
      *** MASKED ***
      Pan ID:
      *** MASKED ***
      Channel:
      *** MASKED ***
      Network Key:
      *** MASKED ***
      
      To unmask the settings run 'iob diag --unmask'
      
      
      *** NodeJS-Installation ***
      
      /usr/bin/nodejs         v20.19.2
      /usr/bin/node           v20.19.2
      /usr/bin/npm            10.8.2
      /usr/bin/npx            10.8.2
      /usr/bin/corepack       0.31.0
      
      nodejs:
        Installed: 20.19.2-1nodesource1
        Candidate: 20.19.2-1nodesource1
        Version table:
       *** 20.19.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
              100 /var/lib/dpkg/status
           20.19.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.19.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.18.3-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.18.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.18.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.18.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.17.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.16.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.15.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.15.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.14.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.13.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.13.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.12.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.12.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.12.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.11.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.11.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.10.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.9.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.8.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.8.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.7.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.6.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.6.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.5.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.5.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.4.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.3.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.3.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.2.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.1.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.0.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           18.19.0+dfsg-6~deb12u2 500
              500 http://deb.debian.org/debian bookworm/main arm64 Packages
           18.19.0+dfsg-6~deb12u1 500
              500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages
      
      Temp directories causing deletion problem: 0
      No problems detected
      
      Errors in npm tree: 0
      No problems detected
      
      *** ioBroker-Installation ***
      
      ioBroker Status
      iobroker is running on this host.
      
      
      Objects type: jsonl
      States  type: jsonl
      
      Hosts:
      raspberrypi         raspberrypi (version: 7.0.6, hostname: raspberrypi   , alive, uptime: 152603)
      
      Core adapters versions
      js-controller:  7.0.6
      admin:          7.6.17
      javascript:     8.8.3
      
      nodejs modules from github:     0
      
      Adapter State
      + system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.backitup.0               : backitup              : raspberrypi                              -  enabled
      + system.adapter.echarts.0                : echarts               : raspberrypi                              -  enabled
      + system.adapter.email.0                  : email                 : raspberrypi                              -  enabled
        system.adapter.emporia.0                : emporia               : raspberrypi                              - disabled
      + system.adapter.javascript.0             : javascript            : raspberrypi                              -  enabled
      + system.adapter.javascript.1             : javascript            : raspberrypi                              -  enabled
      + system.adapter.kecontact.0              : kecontact             : raspberrypi                              -  enabled
      + system.adapter.modbus.0                 : modbus                : raspberrypi                              -  enabled
        system.adapter.modbus.1                 : modbus                : raspberrypi                              - disabled
      + system.adapter.modbus.2                 : modbus                : raspberrypi                              -  enabled
      + system.adapter.shelly.0                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 192.168.0.100
      + system.adapter.sql.0                    : sql                   : raspberrypi                              -  enabled, port: 3306
        system.adapter.vis-2-widgets-energy.0   : vis-2-widgets-energy  : raspberrypi                              - disabled
        system.adapter.vis-2-widgets-gauges.0   : vis-2-widgets-gauges  : raspberrypi                              -  enabled
        system.adapter.vis-2-widgets-inventwo.0 : vis-2-widgets-inventwo: raspberrypi                              -  enabled
        system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: raspberrypi                              - disabled
        system.adapter.vis-2-widgets-weather-and-heating.0: vis-2-widgets-weather-and-heating: raspberrypi                              - disabled
      + system.adapter.vis-2.0                  : vis-2                 : raspberrypi                              -  enabled
      + system.adapter.web.0                    : web                   : raspberrypi                              -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      
      + instance is alive
      
      Enabled adapters with bindings
      + system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.shelly.0                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 192.168.0.100
      + system.adapter.sql.0                    : sql                   : raspberrypi                              -  enabled, port: 3306
      + system.adapter.web.0                    : web                   : raspberrypi                              -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      
      ioBroker-Repositories
      ┌─────────┬──────────┬──────────────────────────────────────────────────┬──────────────┐
      │ (index) │ name     │ url                                              │ auto upgrade │
      ├─────────┼──────────┼──────────────────────────────────────────────────┼──────────────┤
      │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ true         │
      └─────────┴──────────┴──────────────────────────────────────────────────┴──────────────┘
      
      Active repo(s): stable
      Upgrade policy: minor
      
      Installed ioBroker-Adapters
      Used repository: stable
      Adapter    "admin"        : 7.6.17   , installed 7.6.17
      Adapter    "backitup"     : 3.2.2    , installed 3.2.2
      Adapter    "echarts"      : 1.9.2    , installed 1.9.2
      Adapter    "email"        : 2.0.4    , installed 2.0.4
      Adapter    "emporia"      : 0.0.12   , installed 0.1.0
      Adapter    "javascript"   : 8.8.3    , installed 8.8.3
      Controller "js-controller": 7.0.6    , installed 7.0.6
      Adapter    "kecontact"    : 3.1.0    , installed 3.1.0
      Adapter    "modbus"       : 6.3.2    , installed 6.3.2
      Adapter    "shelly"       : 9.5.1    , installed 9.5.1-alpha.8 [Updatable]
      Adapter    "socketio"     : 6.7.1    , installed 6.7.1
      Adapter    "sql"          : 3.0.1    , installed 3.0.1
      Adapter    "vis-2"        : 2.9.64   , installed 2.9.64
      Adapter    "vis-2-widgets-energy": 1.0.2, installed 1.0.2
      Adapter    "vis-2-widgets-gauges": 1.1.0, installed 1.1.0
      Adapter    "vis-2-widgets-inventwo": 0.1.11, installed 0.1.11
      Adapter    "vis-2-widgets-material": 1.4.10, installed 1.4.10
      Adapter    "vis-2-widgets-weather-and-heating": 0.10.4, installed 0.10.4
      Adapter    "web"          : 7.0.8    , installed 7.0.8
      Adapter    "ws"           : 2.6.2    , installed 2.6.2
      
      Objects and States
      Please stand by - This may take a while
      Objects:        1930
      States:         1589
      
      *** OS-Repositories and Updates ***
      Hit:1 http://deb.debian.org/debian bookworm InRelease
      Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
      Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
      Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
      Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
      Reading package lists...
      Pending Updates: 0
      
      *** Listening Ports ***
      Active Internet connections (only servers)
      Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
      tcp        0      0 0.0.0.0:3306            0.0.0.0:*               LISTEN      106        6526       825/mariadbd
      tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      0          6699       933/smbd
      tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          821        765/sshd: /usr/sbin
      tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      0          6698       933/smbd
      tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       6712       745/iobroker.js-con
      tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       3003       745/iobroker.js-con
      tcp        0      0 192.168.0.100:1882      0.0.0.0:*               LISTEN      1001       624470     11471/io.shelly.0
      tcp6       0      0 :::139                  :::*                    LISTEN      0          6697       933/smbd
      tcp6       0      0 :::22                   :::*                    LISTEN      0          823        765/sshd: /usr/sbin
      tcp6       0      0 :::445                  :::*                    LISTEN      0          6696       933/smbd
      tcp6       0      0 :::8081                 :::*                    LISTEN      1001       6802       1076/io.admin.0
      tcp6       0      0 :::8082                 :::*                    LISTEN      1001       7661       1345/io.web.0
      udp        0      0 192.168.0.255:137       0.0.0.0:*                           0          6587       921/nmbd
      udp        0      0 192.168.0.100:137       0.0.0.0:*                           0          6586       921/nmbd
      udp        0      0 0.0.0.0:137             0.0.0.0:*                           0          6574       921/nmbd
      udp        0      0 192.168.0.255:138       0.0.0.0:*                           0          6589       921/nmbd
      udp        0      0 192.168.0.100:138       0.0.0.0:*                           0          6588       921/nmbd
      udp        0      0 0.0.0.0:138             0.0.0.0:*                           0          6575       921/nmbd
      udp        0      0 0.0.0.0:42923           0.0.0.0:*                           104        5683       598/avahi-daemon: r
      udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        5681       598/avahi-daemon: r
      udp        0      0 0.0.0.0:46915           0.0.0.0:*                           1001       7045       1267/io.kecontact.0
      udp        0      0 0.0.0.0:7090            0.0.0.0:*                           1001       7043       1267/io.kecontact.0
      udp        0      0 0.0.0.0:7092            0.0.0.0:*                           1001       7044       1267/io.kecontact.0
      udp6       0      0 fe80::7de6:a76b:229:546 :::*                                0          964        717/NetworkManager
      udp6       0      0 :::53247                :::*                                104        5684       598/avahi-daemon: r
      udp6       0      0 :::5353                 :::*                                104        5682       598/avahi-daemon: r
      
      *** Log File - Last 25 Lines ***
      
      2025-05-29 07:57:19.710  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748498239661,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper
      2025-05-29 07:57:24.056  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch:{"val":false,"ack":false,"ts":1748498244053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543}
      2025-05-29 07:57:24.056  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch" state changed: {"val":false,"ack":false,"ts":1748498244053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543} - forwarding to objectHelper
      2025-05-29 07:57:24.058  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness:{"val":0,"ack":false,"ts":1748498244053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668}
      2025-05-29 07:57:24.058  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness" state changed: {"val":0,"ack":false,"ts":1748498244053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668} - forwarding to objectHelper
      2025-05-29 07:57:29.666  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent:{"val":0,"ack":false,"ts":1748498249662,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244}
      2025-05-29 07:57:29.667  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748498249662,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper
      2025-05-29 07:57:34.055  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch:{"val":false,"ack":false,"ts":1748498254053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543}
      2025-05-29 07:57:34.056  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch" state changed: {"val":false,"ack":false,"ts":1748498254053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543} - forwarding to objectHelper
      2025-05-29 07:57:34.056  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness:{"val":0,"ack":false,"ts":1748498254053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668}
      2025-05-29 07:57:34.057  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness" state changed: {"val":0,"ack":false,"ts":1748498254053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668} - forwarding to objectHelper
      2025-05-29 07:57:39.666  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent:{"val":0,"ack":false,"ts":1748498259661,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244}
      2025-05-29 07:57:39.666  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748498259661,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper
      2025-05-29 07:57:42.151  - debug: shelly.0 (11471) [onlineCheck] Checking shellypro0110pm#8813bfe0db54#1 on 192.168.0.102:80
      2025-05-29 07:57:42.153  - debug: shelly.0 (11471) [onlineCheck] Checking shellyplusplugs#e465b8b35bdc#1 on 192.168.0.105:80
      2025-05-29 07:57:42.153  - debug: shelly.0 (11471) [deviceStatusUpdate] shellypro0110pm#8813bfe0db54#1: true
      2025-05-29 07:57:42.157  - debug: shelly.0 (11471) [deviceStatusUpdate] shellyplusplugs#e465b8b35bdc#1: true
      2025-05-29 07:57:42.157  - debug: shelly.0 (11471) [onlineCheck] Checking shellyplus1#78ee4ccff568#1 on 192.168.0.101:80
      2025-05-29 07:57:42.170  - debug: shelly.0 (11471) [deviceStatusUpdate] shellyplus1#78ee4ccff568#1: true
      2025-05-29 07:57:44.057  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch:{"val":false,"ack":false,"ts":1748498264054,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543}
      2025-05-29 07:57:44.058  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch" state changed: {"val":false,"ack":false,"ts":1748498264054,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543} - forwarding to objectHelper
      2025-05-29 07:57:44.065  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness:{"val":0,"ack":false,"ts":1748498264054,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668}
      2025-05-29 07:57:44.066  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness" state changed: {"val":0,"ack":false,"ts":1748498264054,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668} - forwarding to objectHelper
      2025-05-29 07:57:49.674  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent:{"val":0,"ack":false,"ts":1748498269662,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244}
      2025-05-29 07:57:49.674  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748498269662,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper
      
      

      ============ Mark until here for C&P =============

      iob diag has finished.

      Was kann da die Ursache sein? Vorweg danke für dein Schaffen! Gruß, fuzzy

      Raspberry PI5 mit Linux Debian 13 (Trixie), IoBroker v7.7.2, VIS-2, MariaDB (MySQL)
      mehrere Shellies Plus xx, Modbus: Waveshare Relay 8 Channels, Waveshare RS485-TO-ETH , Smartmeter ET340.
      PV: 10 kWp Module, 2 x Deye WR SUN-10K, 2 x 10 kWh MeritSun LiFe Speicher, KEBA P30 Wallbox, Fronius Wattpilot home 11

      mcm1957M 1 Antwort Letzte Antwort
      0
      • fuzzy1955F fuzzy1955

        @mcm1957 sagte in Test Adapter shelly - ALPHA Versionen:

        Da der switch Modul nicht spezifisch für dieses Relay ist sollte dort eigentlich kein Fehler drinnen sein

        Hallo @mcm1957,

        seit ich die Shelly-Version v9.5.1-alpha.8 installiert habe, funktioniert das Steuern aus dem IOB nicht mehr. Sowohl das manuelle Schalten über die Web-Adresse des Shelly oder über die Objekte im IOB, als auch das Steuern via JavaScript im IOB laufen nicht mehr. Auch die Temperaturen des ShellyPlus1Addon werden im IOB nicht korrekt angezeigt.

        Clipboard01.jpg

        Clipboard02.jpg

        Clipboard03.jpg

        Clipboard05.jpg

        Protokoll silly


        shelly.0
        2025-05-29 07:46:49.662 debug [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748497609654,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper

        shelly.0
        2025-05-29 07:46:49.661 silly States user redis pmessage shelly.0.*/shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent:{"val":0,"ack":false,"ts":1748497609654,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244}

        shelly.0
        2025-05-29 07:46:44.041 debug [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness" state changed: {"val":0,"ack":false,"ts":1748497604035,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668} - forwarding to objectHelper

        shelly.0
        2025-05-29 07:46:44.040 silly States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness:{"val":0,"ack":false,"ts":1748497604035,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668}

        shelly.0
        2025-05-29 07:46:44.038 debug [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch" state changed: {"val":false,"ack":false,"ts":1748497604035,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543} - forwarding to objectHelper

        shelly.0
        2025-05-29 07:46:44.038 silly States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch:{"val":false,"ack":false,"ts":1748497604035,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543}

        shelly.0
        2025-05-29 07:46:42.005 debug [deviceStatusUpdate] shellyplus1#78ee4ccff568#1: true

        shelly.0
        2025-05-29 07:46:42.001 debug [onlineCheck] Checking shellyplus1#78ee4ccff568#1 on 192.168.0.101:80

        shelly.0
        2025-05-29 07:46:42.001 debug [deviceStatusUpdate] shellyplusplugs#e465b8b35bdc#1: true

        shelly.0
        2025-05-29 07:46:41.997 debug [deviceStatusUpdate] shellypro0110pm#8813bfe0db54#1: true

        shelly.0
        2025-05-29 07:46:41.997 debug [onlineCheck] Checking shellyplusplugs#e465b8b35bdc#1 on 192.168.0.105:80

        shelly.0
        2025-05-29 07:46:41.995 debug [onlineCheck] Checking shellypro0110pm#8813bfe0db54#1 on 192.168.0.102:80

        iob diag


        ========== Start marking the full check here ===========

        Script v.2025-03-08
        
        *** BASE SYSTEM ***
         Static hostname: raspberrypi
               Icon name: computer
        Operating System: Debian GNU/Linux 12 (bookworm)
                  Kernel: Linux 6.12.25+rpt-rpi-2712
            Architecture: arm64
        OS is similar to:
        
        Model           : Raspberry Pi 5 Model B Rev 1.1
        Docker          : false
        Virtualization  : none
        Kernel          : aarch64
        Userland        : 64 bit
        
        Systemuptime and Load:
         07:57:26 up 1 day, 18:23,  2 users,  load average: 0.07, 0.02, 0.00
        CPU threads: 4
        
        
        *** LIFE CYCLE STATUS ***
        Operating System is the current Debian stable version codenamed 'bookworm'!
        
        *** RASPBERRY THROTTLING ***
        Current issues:
        No throttling issues detected.
        
        Previously detected issues:
        No throttling issues detected.
        
        *** TIME AND TIMEZONES ***
                       Local time: Thu 2025-05-29 07:57:26 CEST
                   Universal time: Thu 2025-05-29 05:57:26 UTC
                         RTC time: Thu 2025-05-29 05:57:26
                        Time zone: Europe/Vienna (CEST, +0200)
        System clock synchronized: yes
                      NTP service: active
                  RTC in local TZ: no
        
        *** Users and Groups ***
        User that called 'iob diag':
        pi
        HOME=/home/pi
        GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
        
        User that is running 'js-controller':
        iobroker
        HOME=/home/iobroker
        GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c
        
        *** DISPLAY-SERVER SETUP ***
        Display-Server: false
        Desktop:
        Terminal:       tty
        
        *** MEMORY ***
                       total        used        free      shared  buff/cache   available
        Mem:             17G        2.0G         13G        7.6M        1.4G         14G
        Swap:           536M          0B        536M
        Total:           17G        2.0G         14G
        
        Active iob-Instances:   14
        
                16219 M total memory
                 1941 M used memory
                 1769 M active memory
                 1048 M inactive memory
                13054 M free memory
                  132 M buffer memory
                 1213 M swap cache
                  511 M total swap
                    0 M used swap
                  511 M free swap
        
        *** top - Table Of Processes  ***
        top - 07:57:27 up 1 day, 18:23,  2 users,  load average: 0.07, 0.02, 0.00
        Tasks: 202 total,   1 running, 201 sleeping,   0 stopped,   0 zombie
        %Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
        MiB Mem :  16219.7 total,  13054.7 free,   1941.5 used,   1345.5 buff/cache
        MiB Swap:    512.0 total,    512.0 free,      0.0 used.  14278.1 avail Mem
        
        *** FAILED SERVICES ***
        
          UNIT LOAD ACTIVE SUB DESCRIPTION
        0 loaded units listed.
        
        
        *** DMESG CRITICAL ERRORS ***
        No critical errors detected
        
        *** FILESYSTEM ***
        Filesystem     Type      Size  Used Avail Use% Mounted on
        udev           devtmpfs  7.9G     0  7.9G   0% /dev
        tmpfs          tmpfs     1.6G  7.3M  1.6G   1% /run
        /dev/mmcblk0p2 ext4       15G   12G  2.0G  86% /
        tmpfs          tmpfs     8.0G     0  8.0G   0% /dev/shm
        tmpfs          tmpfs     5.0M   48K  5.0M   1% /run/lock
        /dev/mmcblk0p1 vfat      510M   56M  455M  11% /boot/firmware
        tmpfs          tmpfs     1.6G     0  1.6G   0% /run/user/1000
        
        Messages concerning ext4 filesystem in dmesg:
        
        Show mounted filesystems:
        TARGET           SOURCE         FSTYPE OPTIONS
        /                /dev/mmcblk0p2 ext4   rw,noatime
        `-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
        
        Files in neuralgic directories:
        
        /var:
        2.3G    /var/
        756M    /var/log
        755M    /var/log/journal/ce49b5c207f74de48fc362bf23ca73ba
        755M    /var/log/journal
        551M    /var/lib
        
        Archived and active journals take up 754.7M in the file system.
        
        /opt/iobroker/backups:
        167M    /opt/iobroker/backups/
        
        /opt/iobroker/iobroker-data:
        1.2G    /opt/iobroker/iobroker-data/
        1.1G    /opt/iobroker/iobroker-data/files
        617M    /opt/iobroker/iobroker-data/files/javascript.admin
        560M    /opt/iobroker/iobroker-data/files/javascript.admin/static
        558M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js
        
        The five largest files in iobroker-data are:
        26M     /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map
        26M     /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map
        24M     /opt/iobroker/iobroker-data/files/vis-2/static/js/main.f305bc29.js.map
        24M     /opt/iobroker/iobroker-data/files/vis-2/static/js/main.8e80ccb0.js.map
        24M     /opt/iobroker/iobroker-data/files/vis-2/customWidgets.js.map
        
        USB-Devices by-id:
        USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':
        
        No Devices found 'by-id'
        
        Zigbee Network Settings on your coordinator/in nvbackup are:
        
        zigbee.X
        Extended Pan ID:
        *** MASKED ***
        Pan ID:
        *** MASKED ***
        Channel:
        *** MASKED ***
        Network Key:
        *** MASKED ***
        
        To unmask the settings run 'iob diag --unmask'
        
        
        *** NodeJS-Installation ***
        
        /usr/bin/nodejs         v20.19.2
        /usr/bin/node           v20.19.2
        /usr/bin/npm            10.8.2
        /usr/bin/npx            10.8.2
        /usr/bin/corepack       0.31.0
        
        nodejs:
          Installed: 20.19.2-1nodesource1
          Candidate: 20.19.2-1nodesource1
          Version table:
         *** 20.19.2-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                100 /var/lib/dpkg/status
             20.19.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.19.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.18.3-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.18.2-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.18.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.18.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.17.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.16.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.15.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.15.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.14.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.13.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.13.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.12.2-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.12.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.12.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.11.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.11.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.10.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.9.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.8.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.8.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.7.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.6.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.6.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.5.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.5.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.4.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.3.1-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.3.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.2.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.1.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             20.0.0-1nodesource1 1001
                500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
             18.19.0+dfsg-6~deb12u2 500
                500 http://deb.debian.org/debian bookworm/main arm64 Packages
             18.19.0+dfsg-6~deb12u1 500
                500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages
        
        Temp directories causing deletion problem: 0
        No problems detected
        
        Errors in npm tree: 0
        No problems detected
        
        *** ioBroker-Installation ***
        
        ioBroker Status
        iobroker is running on this host.
        
        
        Objects type: jsonl
        States  type: jsonl
        
        Hosts:
        raspberrypi         raspberrypi (version: 7.0.6, hostname: raspberrypi   , alive, uptime: 152603)
        
        Core adapters versions
        js-controller:  7.0.6
        admin:          7.6.17
        javascript:     8.8.3
        
        nodejs modules from github:     0
        
        Adapter State
        + system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        + system.adapter.backitup.0               : backitup              : raspberrypi                              -  enabled
        + system.adapter.echarts.0                : echarts               : raspberrypi                              -  enabled
        + system.adapter.email.0                  : email                 : raspberrypi                              -  enabled
          system.adapter.emporia.0                : emporia               : raspberrypi                              - disabled
        + system.adapter.javascript.0             : javascript            : raspberrypi                              -  enabled
        + system.adapter.javascript.1             : javascript            : raspberrypi                              -  enabled
        + system.adapter.kecontact.0              : kecontact             : raspberrypi                              -  enabled
        + system.adapter.modbus.0                 : modbus                : raspberrypi                              -  enabled
          system.adapter.modbus.1                 : modbus                : raspberrypi                              - disabled
        + system.adapter.modbus.2                 : modbus                : raspberrypi                              -  enabled
        + system.adapter.shelly.0                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 192.168.0.100
        + system.adapter.sql.0                    : sql                   : raspberrypi                              -  enabled, port: 3306
          system.adapter.vis-2-widgets-energy.0   : vis-2-widgets-energy  : raspberrypi                              - disabled
          system.adapter.vis-2-widgets-gauges.0   : vis-2-widgets-gauges  : raspberrypi                              -  enabled
          system.adapter.vis-2-widgets-inventwo.0 : vis-2-widgets-inventwo: raspberrypi                              -  enabled
          system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: raspberrypi                              - disabled
          system.adapter.vis-2-widgets-weather-and-heating.0: vis-2-widgets-weather-and-heating: raspberrypi                              - disabled
        + system.adapter.vis-2.0                  : vis-2                 : raspberrypi                              -  enabled
        + system.adapter.web.0                    : web                   : raspberrypi                              -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
        
        + instance is alive
        
        Enabled adapters with bindings
        + system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        + system.adapter.shelly.0                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 192.168.0.100
        + system.adapter.sql.0                    : sql                   : raspberrypi                              -  enabled, port: 3306
        + system.adapter.web.0                    : web                   : raspberrypi                              -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
        
        ioBroker-Repositories
        ┌─────────┬──────────┬──────────────────────────────────────────────────┬──────────────┐
        │ (index) │ name     │ url                                              │ auto upgrade │
        ├─────────┼──────────┼──────────────────────────────────────────────────┼──────────────┤
        │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ true         │
        └─────────┴──────────┴──────────────────────────────────────────────────┴──────────────┘
        
        Active repo(s): stable
        Upgrade policy: minor
        
        Installed ioBroker-Adapters
        Used repository: stable
        Adapter    "admin"        : 7.6.17   , installed 7.6.17
        Adapter    "backitup"     : 3.2.2    , installed 3.2.2
        Adapter    "echarts"      : 1.9.2    , installed 1.9.2
        Adapter    "email"        : 2.0.4    , installed 2.0.4
        Adapter    "emporia"      : 0.0.12   , installed 0.1.0
        Adapter    "javascript"   : 8.8.3    , installed 8.8.3
        Controller "js-controller": 7.0.6    , installed 7.0.6
        Adapter    "kecontact"    : 3.1.0    , installed 3.1.0
        Adapter    "modbus"       : 6.3.2    , installed 6.3.2
        Adapter    "shelly"       : 9.5.1    , installed 9.5.1-alpha.8 [Updatable]
        Adapter    "socketio"     : 6.7.1    , installed 6.7.1
        Adapter    "sql"          : 3.0.1    , installed 3.0.1
        Adapter    "vis-2"        : 2.9.64   , installed 2.9.64
        Adapter    "vis-2-widgets-energy": 1.0.2, installed 1.0.2
        Adapter    "vis-2-widgets-gauges": 1.1.0, installed 1.1.0
        Adapter    "vis-2-widgets-inventwo": 0.1.11, installed 0.1.11
        Adapter    "vis-2-widgets-material": 1.4.10, installed 1.4.10
        Adapter    "vis-2-widgets-weather-and-heating": 0.10.4, installed 0.10.4
        Adapter    "web"          : 7.0.8    , installed 7.0.8
        Adapter    "ws"           : 2.6.2    , installed 2.6.2
        
        Objects and States
        Please stand by - This may take a while
        Objects:        1930
        States:         1589
        
        *** OS-Repositories and Updates ***
        Hit:1 http://deb.debian.org/debian bookworm InRelease
        Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
        Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
        Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
        Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
        Reading package lists...
        Pending Updates: 0
        
        *** Listening Ports ***
        Active Internet connections (only servers)
        Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
        tcp        0      0 0.0.0.0:3306            0.0.0.0:*               LISTEN      106        6526       825/mariadbd
        tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      0          6699       933/smbd
        tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          821        765/sshd: /usr/sbin
        tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      0          6698       933/smbd
        tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       6712       745/iobroker.js-con
        tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       3003       745/iobroker.js-con
        tcp        0      0 192.168.0.100:1882      0.0.0.0:*               LISTEN      1001       624470     11471/io.shelly.0
        tcp6       0      0 :::139                  :::*                    LISTEN      0          6697       933/smbd
        tcp6       0      0 :::22                   :::*                    LISTEN      0          823        765/sshd: /usr/sbin
        tcp6       0      0 :::445                  :::*                    LISTEN      0          6696       933/smbd
        tcp6       0      0 :::8081                 :::*                    LISTEN      1001       6802       1076/io.admin.0
        tcp6       0      0 :::8082                 :::*                    LISTEN      1001       7661       1345/io.web.0
        udp        0      0 192.168.0.255:137       0.0.0.0:*                           0          6587       921/nmbd
        udp        0      0 192.168.0.100:137       0.0.0.0:*                           0          6586       921/nmbd
        udp        0      0 0.0.0.0:137             0.0.0.0:*                           0          6574       921/nmbd
        udp        0      0 192.168.0.255:138       0.0.0.0:*                           0          6589       921/nmbd
        udp        0      0 192.168.0.100:138       0.0.0.0:*                           0          6588       921/nmbd
        udp        0      0 0.0.0.0:138             0.0.0.0:*                           0          6575       921/nmbd
        udp        0      0 0.0.0.0:42923           0.0.0.0:*                           104        5683       598/avahi-daemon: r
        udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        5681       598/avahi-daemon: r
        udp        0      0 0.0.0.0:46915           0.0.0.0:*                           1001       7045       1267/io.kecontact.0
        udp        0      0 0.0.0.0:7090            0.0.0.0:*                           1001       7043       1267/io.kecontact.0
        udp        0      0 0.0.0.0:7092            0.0.0.0:*                           1001       7044       1267/io.kecontact.0
        udp6       0      0 fe80::7de6:a76b:229:546 :::*                                0          964        717/NetworkManager
        udp6       0      0 :::53247                :::*                                104        5684       598/avahi-daemon: r
        udp6       0      0 :::5353                 :::*                                104        5682       598/avahi-daemon: r
        
        *** Log File - Last 25 Lines ***
        
        2025-05-29 07:57:19.710  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748498239661,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper
        2025-05-29 07:57:24.056  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch:{"val":false,"ack":false,"ts":1748498244053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543}
        2025-05-29 07:57:24.056  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch" state changed: {"val":false,"ack":false,"ts":1748498244053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543} - forwarding to objectHelper
        2025-05-29 07:57:24.058  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness:{"val":0,"ack":false,"ts":1748498244053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668}
        2025-05-29 07:57:24.058  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness" state changed: {"val":0,"ack":false,"ts":1748498244053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668} - forwarding to objectHelper
        2025-05-29 07:57:29.666  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent:{"val":0,"ack":false,"ts":1748498249662,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244}
        2025-05-29 07:57:29.667  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748498249662,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper
        2025-05-29 07:57:34.055  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch:{"val":false,"ack":false,"ts":1748498254053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543}
        2025-05-29 07:57:34.056  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch" state changed: {"val":false,"ack":false,"ts":1748498254053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543} - forwarding to objectHelper
        2025-05-29 07:57:34.056  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness:{"val":0,"ack":false,"ts":1748498254053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668}
        2025-05-29 07:57:34.057  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness" state changed: {"val":0,"ack":false,"ts":1748498254053,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668} - forwarding to objectHelper
        2025-05-29 07:57:39.666  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent:{"val":0,"ack":false,"ts":1748498259661,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244}
        2025-05-29 07:57:39.666  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748498259661,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper
        2025-05-29 07:57:42.151  - debug: shelly.0 (11471) [onlineCheck] Checking shellypro0110pm#8813bfe0db54#1 on 192.168.0.102:80
        2025-05-29 07:57:42.153  - debug: shelly.0 (11471) [onlineCheck] Checking shellyplusplugs#e465b8b35bdc#1 on 192.168.0.105:80
        2025-05-29 07:57:42.153  - debug: shelly.0 (11471) [deviceStatusUpdate] shellypro0110pm#8813bfe0db54#1: true
        2025-05-29 07:57:42.157  - debug: shelly.0 (11471) [deviceStatusUpdate] shellyplusplugs#e465b8b35bdc#1: true
        2025-05-29 07:57:42.157  - debug: shelly.0 (11471) [onlineCheck] Checking shellyplus1#78ee4ccff568#1 on 192.168.0.101:80
        2025-05-29 07:57:42.170  - debug: shelly.0 (11471) [deviceStatusUpdate] shellyplus1#78ee4ccff568#1: true
        2025-05-29 07:57:44.057  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch:{"val":false,"ack":false,"ts":1748498264054,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543}
        2025-05-29 07:57:44.058  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Switch" state changed: {"val":false,"ack":false,"ts":1748498264054,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232543} - forwarding to objectHelper
        2025-05-29 07:57:44.065  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness:{"val":0,"ack":false,"ts":1748498264054,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668}
        2025-05-29 07:57:44.066  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellypro0110pm#8813bfe0db54#1.Light0.Brightness" state changed: {"val":0,"ack":false,"ts":1748498264054,"q":0,"c":"script.js.common.Photovoltaik.PvAblaufsteuerung","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748462232668} - forwarding to objectHelper
        2025-05-29 07:57:49.674  - silly: shelly.0 (11471) States user redis pmessage shelly.0.*/shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent:{"val":0,"ack":false,"ts":1748498269662,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244}
        2025-05-29 07:57:49.674  - debug: shelly.0 (11471) [onStateChange] "shelly.0.shellyplusplugs#e465b8b35bdc#1.Relay0.LimitCurrent" state changed: {"val":0,"ack":false,"ts":1748498269662,"q":0,"c":"script.js.common.DpRefresh","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1748366076244} - forwarding to objectHelper
        
        

        ============ Mark until here for C&P =============

        iob diag has finished.

        Was kann da die Ursache sein? Vorweg danke für dein Schaffen! Gruß, fuzzy

        mcm1957M Offline
        mcm1957M Offline
        mcm1957
        schrieb am zuletzt editiert von
        #67

        @fuzzy1955 said in Test Adapter shelly - ALPHA Versionen:

        An sich ist die 9.5.1 seit kurzem bereits im Stabel, alle alphas sind damit outdated. Aber das tut mal nichts zur Sache.

        Was ich nicht verstehe ist - du schreibst:

        Sowohl das manuelle Schalten über die Web-Adresse des Shelly oder über die Objekte im IOB, als auch das Steuern via JavaScript im IOB laufen nicht mehr.

        Lese ich das richtig? Auch ein steuern des Shelly direkt über die Web-Addresse des Shellys funktioniert nicht? Bei dieser Aktion ist ja der ioBroker Adapter ger nicht involviert. Was bedeutet außerdem "laufen nicht mehr."? Fehlermeldung? Welches Fehlverhalten? etc.

        Triott das Problem bei einem Shelly auf (Modell?) oder bei mehreren? Alle gleicher Typ?

        Im Moment klingt das für mich eher nach einen Hardwareproblem eines Shellies, ev. noch nach einem Netzwerkproblem (mit viel geringerer Wahrscheinlichkeit). Da Shelly derzeit eine neue Firmware ausrollt könnte bei einem Update auch was schief gegangen sein.

        In jedem Fall macht es erst Sinn nach etwas im Adapter zu suchen wenn der Shelly via eigenem Webinterface und App normal funktioniert.

        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

        fuzzy1955F 1 Antwort Letzte Antwort
        0
        • mcm1957M mcm1957

          @fuzzy1955 said in Test Adapter shelly - ALPHA Versionen:

          An sich ist die 9.5.1 seit kurzem bereits im Stabel, alle alphas sind damit outdated. Aber das tut mal nichts zur Sache.

          Was ich nicht verstehe ist - du schreibst:

          Sowohl das manuelle Schalten über die Web-Adresse des Shelly oder über die Objekte im IOB, als auch das Steuern via JavaScript im IOB laufen nicht mehr.

          Lese ich das richtig? Auch ein steuern des Shelly direkt über die Web-Addresse des Shellys funktioniert nicht? Bei dieser Aktion ist ja der ioBroker Adapter ger nicht involviert. Was bedeutet außerdem "laufen nicht mehr."? Fehlermeldung? Welches Fehlverhalten? etc.

          Triott das Problem bei einem Shelly auf (Modell?) oder bei mehreren? Alle gleicher Typ?

          Im Moment klingt das für mich eher nach einen Hardwareproblem eines Shellies, ev. noch nach einem Netzwerkproblem (mit viel geringerer Wahrscheinlichkeit). Da Shelly derzeit eine neue Firmware ausrollt könnte bei einem Update auch was schief gegangen sein.

          In jedem Fall macht es erst Sinn nach etwas im Adapter zu suchen wenn der Shelly via eigenem Webinterface und App normal funktioniert.

          fuzzy1955F Online
          fuzzy1955F Online
          fuzzy1955
          schrieb am zuletzt editiert von
          #68

          @mcm1957 sagte in Test Adapter shelly - ALPHA Versionen:

          Sowohl das manuelle Schalten über die Web-Adresse des Shelly

          Pardon, das manuelle Schalten über die Web-Adresse hat schon funktioniert.

          Inzwischen habe ich die Ursache gefunden. Es lag daran, dass der Raspi nicht auf die IP-Adresse der Shellies zugreifen konnte. Der Port 1882 war in der Firewall nicht auf die Raspi-IP eingetragen.

          Ich muss wohl noch reichlich dazulernen. Danke jedenfalls!

          Raspberry PI5 mit Linux Debian 13 (Trixie), IoBroker v7.7.2, VIS-2, MariaDB (MySQL)
          mehrere Shellies Plus xx, Modbus: Waveshare Relay 8 Channels, Waveshare RS485-TO-ETH , Smartmeter ET340.
          PV: 10 kWp Module, 2 x Deye WR SUN-10K, 2 x 10 kWh MeritSun LiFe Speicher, KEBA P30 Wallbox, Fronius Wattpilot home 11

          mcm1957M haus-automatisierungH 2 Antworten Letzte Antwort
          1
          • fuzzy1955F fuzzy1955

            @mcm1957 sagte in Test Adapter shelly - ALPHA Versionen:

            Sowohl das manuelle Schalten über die Web-Adresse des Shelly

            Pardon, das manuelle Schalten über die Web-Adresse hat schon funktioniert.

            Inzwischen habe ich die Ursache gefunden. Es lag daran, dass der Raspi nicht auf die IP-Adresse der Shellies zugreifen konnte. Der Port 1882 war in der Firewall nicht auf die Raspi-IP eingetragen.

            Ich muss wohl noch reichlich dazulernen. Danke jedenfalls!

            mcm1957M Offline
            mcm1957M Offline
            mcm1957
            schrieb am zuletzt editiert von
            #69

            @fuzzy1955
            Danke fürs Feedback.

            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
            0
            • fuzzy1955F fuzzy1955

              @mcm1957 sagte in Test Adapter shelly - ALPHA Versionen:

              Sowohl das manuelle Schalten über die Web-Adresse des Shelly

              Pardon, das manuelle Schalten über die Web-Adresse hat schon funktioniert.

              Inzwischen habe ich die Ursache gefunden. Es lag daran, dass der Raspi nicht auf die IP-Adresse der Shellies zugreifen konnte. Der Port 1882 war in der Firewall nicht auf die Raspi-IP eingetragen.

              Ich muss wohl noch reichlich dazulernen. Danke jedenfalls!

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

              @fuzzy1955 sagte in Test Adapter shelly - ALPHA Versionen:

              Es lag daran, dass der Raspi nicht auf die IP-Adresse der Shellies zugreifen konnte.

              Mh? Der Raspi öffnet den Port 1882 und der Shelly greift darauf zu. Nicht andersrum.

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

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

                @fuzzy1955 sagte in Test Adapter shelly - ALPHA Versionen:

                Es lag daran, dass der Raspi nicht auf die IP-Adresse der Shellies zugreifen konnte.

                Mh? Der Raspi öffnet den Port 1882 und der Shelly greift darauf zu. Nicht andersrum.

                fuzzy1955F Online
                fuzzy1955F Online
                fuzzy1955
                schrieb am zuletzt editiert von
                #71

                @haus-automatisierung sagte in Test Adapter shelly - ALPHA Versionen:

                Der Raspi öffnet den Port 1882 und der Shelly greift darauf zu.

                Ja, klar. Die IP des Raspi mit dem Port 1882 war nicht in dessen Linux-Firewall eingetragen.

                Raspberry PI5 mit Linux Debian 13 (Trixie), IoBroker v7.7.2, VIS-2, MariaDB (MySQL)
                mehrere Shellies Plus xx, Modbus: Waveshare Relay 8 Channels, Waveshare RS485-TO-ETH , Smartmeter ET340.
                PV: 10 kWp Module, 2 x Deye WR SUN-10K, 2 x 10 kWh MeritSun LiFe Speicher, KEBA P30 Wallbox, Fronius Wattpilot home 11

                1 Antwort Letzte Antwort
                0
                • mcm1957M mcm1957
                  Aktuelle Test Version 10.4.2-alpha.1
                  Veröffentlichungsdatum 12.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 BETA/LATEST Test https://forum.iobroker.net/topic/80722/test-adapter-shelly-10-1-0-latest-beta
                  Shelly STABLE Fragen https://forum.iobroker.net/topic/81297/shelly-adapter-genereller-support

                  ==============================================================================

                  Der Adapter ioBroker.shelly wird seit langer Zeit von @haus-automatisierung sehr gut betruet und weiter entwickelt. Um ihn ein wenig zu entlasten (und für anspruchsvollere Dinge freizuschaufeln) werde ich versuchen bei der Konfiguration neuer Geräte mitzuwirken.

                  Leider kann (und will) ich mir nicht alle verfügbaren Shellies kaufen wenn ich sie nicht selbst verwenden kann. Da es aus Erfahrung unrealistisch ist, dass es genug Spenden zur Finanzierung der Geräte gibt - und ich auch nicht garantieren kann und will dass ich kurzfristig auf geschenkte Geräte reagiere - werde ich hier um eure Mithilfe ersuchen.

                  Ich werde daher in diesem Topic primär um Informationen zu neuen Geräten bitten und um Feedback zu Alpha-Implementierungen bitten. Konkret in Arbeit befindliche Geräte werde ich im nächsten Kommentar nennen. Ansonsten gilt natürlich unverändert bitte bei Problemen und dem Wunsch nach Einbindung eines bestimmten Geräts ein Issue im Adapter-Repository eröffnen.

                  Changelog

                  siehe https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/README.md#changelog

                  gelberlemmyG Offline
                  gelberlemmyG Offline
                  gelberlemmy
                  schrieb am zuletzt editiert von
                  #72

                  @mcm1957 Hallo, ich habe aktuell ein Problem mit meinem Shelly Adapter über MQTT. Ich würde jetzt tippen, dass es etwas mit der aktuellen Firmware zu tun hat. Egal welche Version vom Adapter ich nehme, bekomme ich folgende Nachrichten

                  shelly.1
                  2025-06-03 21:43:04.010	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                  
                  shelly.1
                  2025-06-03 21:42:54.016	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                  
                  shelly.1
                  2025-06-03 21:42:45.727	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) (false)
                  
                  shelly.1
                  2025-06-03 21:42:44.328	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                  
                  shelly.1
                  2025-06-03 21:42:44.311	error	[MQTT] Wrong MQTT authentification of client "shellypro3-2cbcbba79f0c"
                  
                  shelly.1
                  2025-06-03 21:42:35.735	info	[MQTT] Device with client id "shellyplus1-441793a712a8" connected from 192.168.171.106!
                  
                  shelly.1
                  2025-06-03 21:41:56.079	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                  
                  shelly.1
                  2025-06-03 21:41:48.497	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                  
                  shelly.1
                  2025-06-03 21:41:48.473	error	[MQTT] Wrong MQTT authentification of client "shellypro3-2cbcbba79f0c"
                  
                  shelly.1
                  2025-06-03 21:41:46.083	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                  
                  shelly.1
                  2025-06-03 21:41:42.097	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                  
                  shelly.1
                  2025-06-03 21:41:42.057	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                  
                  shelly.1
                  2025-06-03 21:41:41.717	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                  
                  shelly.1
                  2025-06-03 21:41:41.333	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                  
                  shelly.1
                  2025-06-03 21:41:41.333	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                  
                  shelly.1
                  2025-06-03 21:41:41.085	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                  
                  shelly.1
                  2025-06-03 21:41:41.048	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                  
                  shelly.1
                  2025-06-03 21:41:40.871	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                  
                  shelly.1
                  2025-06-03 21:41:40.870	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                  
                  shelly.1
                  2025-06-03 21:41:40.870	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                  

                  Es lief alles reibunsglos. Auch frage ich mich, warum hinter den IP Adressen im Text ein "!" steht.

                  Anbei einmal ein Screenshot von einem Teilnehmer auf der Adapter Instanz.

                  Screenshot 2025-06-03 214556.png
                  Screenshot 2025-06-03 214715.png
                  Hat da jemand einen Tipp ?

                  Gruß André

                  haus-automatisierungH 1 Antwort Letzte Antwort
                  0
                  • gelberlemmyG gelberlemmy

                    @mcm1957 Hallo, ich habe aktuell ein Problem mit meinem Shelly Adapter über MQTT. Ich würde jetzt tippen, dass es etwas mit der aktuellen Firmware zu tun hat. Egal welche Version vom Adapter ich nehme, bekomme ich folgende Nachrichten

                    shelly.1
                    2025-06-03 21:43:04.010	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                    
                    shelly.1
                    2025-06-03 21:42:54.016	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                    
                    shelly.1
                    2025-06-03 21:42:45.727	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) (false)
                    
                    shelly.1
                    2025-06-03 21:42:44.328	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                    
                    shelly.1
                    2025-06-03 21:42:44.311	error	[MQTT] Wrong MQTT authentification of client "shellypro3-2cbcbba79f0c"
                    
                    shelly.1
                    2025-06-03 21:42:35.735	info	[MQTT] Device with client id "shellyplus1-441793a712a8" connected from 192.168.171.106!
                    
                    shelly.1
                    2025-06-03 21:41:56.079	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                    
                    shelly.1
                    2025-06-03 21:41:48.497	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                    
                    shelly.1
                    2025-06-03 21:41:48.473	error	[MQTT] Wrong MQTT authentification of client "shellypro3-2cbcbba79f0c"
                    
                    shelly.1
                    2025-06-03 21:41:46.083	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                    
                    shelly.1
                    2025-06-03 21:41:42.097	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                    
                    shelly.1
                    2025-06-03 21:41:42.057	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                    
                    shelly.1
                    2025-06-03 21:41:41.717	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                    
                    shelly.1
                    2025-06-03 21:41:41.333	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                    
                    shelly.1
                    2025-06-03 21:41:41.333	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                    
                    shelly.1
                    2025-06-03 21:41:41.085	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                    
                    shelly.1
                    2025-06-03 21:41:41.048	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                    
                    shelly.1
                    2025-06-03 21:41:40.871	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                    
                    shelly.1
                    2025-06-03 21:41:40.870	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                    
                    shelly.1
                    2025-06-03 21:41:40.870	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                    

                    Es lief alles reibunsglos. Auch frage ich mich, warum hinter den IP Adressen im Text ein "!" steht.

                    Anbei einmal ein Screenshot von einem Teilnehmer auf der Adapter Instanz.

                    Screenshot 2025-06-03 214556.png
                    Screenshot 2025-06-03 214715.png
                    Hat da jemand einen Tipp ?

                    Gruß André

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

                    @gelberlemmy sagte in Test Adapter shelly - ALPHA Versionen:

                    Auch frage ich mich, warum hinter den IP Adressen im Text ein "!" steht.

                    Aus dem gleichen Grund, warum connected from davor steht. Ist halt Teil der Meldung:

                    https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/309081556b241388e979e0ecee132de41a5c7c60/lib/protocol/mqtt.js#L453

                    🧑‍🎓 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
                    0
                    • mcm1957M Offline
                      mcm1957M Offline
                      mcm1957
                      schrieb am zuletzt editiert von
                      #74

                      @gelberlemmy said in Test Adapter shelly - ALPHA Versionen:

                      @mcm1957 Hallo, ich habe aktuell ein Problem mit meinem Shelly Adapter über MQTT. Ich würde jetzt tippen, dass es etwas mit der aktuellen Firmware zu tun hat. Egal welche Version vom Adapter ich nehme, bekomme ich folgende Nachrichten

                      shelly.1
                      2025-06-03 21:43:04.010	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                      
                      shelly.1
                      2025-06-03 21:42:54.016	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                      
                      shelly.1
                      2025-06-03 21:42:45.727	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) (false)
                      
                      shelly.1
                      2025-06-03 21:42:44.328	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                      
                      shelly.1
                      2025-06-03 21:42:44.311	error	[MQTT] Wrong MQTT authentification of client "shellypro3-2cbcbba79f0c"
                      
                      shelly.1
                      2025-06-03 21:42:35.735	info	[MQTT] Device with client id "shellyplus1-441793a712a8" connected from 192.168.171.106!
                      
                      shelly.1
                      2025-06-03 21:41:56.079	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                      
                      shelly.1
                      2025-06-03 21:41:48.497	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                      
                      shelly.1
                      2025-06-03 21:41:48.473	error	[MQTT] Wrong MQTT authentification of client "shellypro3-2cbcbba79f0c"
                      
                      shelly.1
                      2025-06-03 21:41:46.083	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                      
                      shelly.1
                      2025-06-03 21:41:42.097	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                      
                      shelly.1
                      2025-06-03 21:41:42.057	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                      
                      shelly.1
                      2025-06-03 21:41:41.717	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                      
                      shelly.1
                      2025-06-03 21:41:41.333	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                      
                      shelly.1
                      2025-06-03 21:41:41.333	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                      
                      shelly.1
                      2025-06-03 21:41:41.085	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                      
                      shelly.1
                      2025-06-03 21:41:41.048	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                      
                      shelly.1
                      2025-06-03 21:41:40.871	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                      
                      shelly.1
                      2025-06-03 21:41:40.870	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                      
                      shelly.1
                      2025-06-03 21:41:40.870	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                      

                      Es lief alles reibunsglos. Auch frage ich mich, warum hinter den IP Adressen im Text ein "!" steht.

                      Anbei einmal ein Screenshot von einem Teilnehmer auf der Adapter Instanz.

                      Screenshot 2025-06-03 214556.png
                      Screenshot 2025-06-03 214715.png
                      Hat da jemand einen Tipp ?

                      Gruß André

                      Das hat zwar nichts mit ALPHA Tests zu tun - derzeit läuft nicht mal einer - ABER:

                      Kontrollier mal dein MQTT Passwort (und auch gleich den Username für MQTT).

                      Bitte beachte, dass das Passwort am Shelly bei JEDER (!) Änderung der MQTT Einstellungen neu eingegeben werden muss. Und dass der Shelly nachher restartet werden muss.

                      Falls du auch ein HTTP Passwort gesetzt hast, verwende für HTTP und MQTT unterschiedliche Usernames und Passwörter. (Hab keine Erklärung und auch noch icht expolizit getestet aber es gab eine diesbezügliche Meldung vin ein oder 2 User die meinten dass es bei identem Username / Passwortkombinationen für HTTP und MQTT Probleme gäbe).

                      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

                      gelberlemmyG 1 Antwort Letzte Antwort
                      0
                      • mcm1957M mcm1957

                        @gelberlemmy said in Test Adapter shelly - ALPHA Versionen:

                        @mcm1957 Hallo, ich habe aktuell ein Problem mit meinem Shelly Adapter über MQTT. Ich würde jetzt tippen, dass es etwas mit der aktuellen Firmware zu tun hat. Egal welche Version vom Adapter ich nehme, bekomme ich folgende Nachrichten

                        shelly.1
                        2025-06-03 21:43:04.010	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                        
                        shelly.1
                        2025-06-03 21:42:54.016	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                        
                        shelly.1
                        2025-06-03 21:42:45.727	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) (false)
                        
                        shelly.1
                        2025-06-03 21:42:44.328	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                        
                        shelly.1
                        2025-06-03 21:42:44.311	error	[MQTT] Wrong MQTT authentification of client "shellypro3-2cbcbba79f0c"
                        
                        shelly.1
                        2025-06-03 21:42:35.735	info	[MQTT] Device with client id "shellyplus1-441793a712a8" connected from 192.168.171.106!
                        
                        shelly.1
                        2025-06-03 21:41:56.079	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                        
                        shelly.1
                        2025-06-03 21:41:48.497	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                        
                        shelly.1
                        2025-06-03 21:41:48.473	error	[MQTT] Wrong MQTT authentification of client "shellypro3-2cbcbba79f0c"
                        
                        shelly.1
                        2025-06-03 21:41:46.083	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                        
                        shelly.1
                        2025-06-03 21:41:42.097	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                        
                        shelly.1
                        2025-06-03 21:41:42.057	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                        
                        shelly.1
                        2025-06-03 21:41:41.717	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                        
                        shelly.1
                        2025-06-03 21:41:41.333	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                        
                        shelly.1
                        2025-06-03 21:41:41.333	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                        
                        shelly.1
                        2025-06-03 21:41:41.085	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                        
                        shelly.1
                        2025-06-03 21:41:41.048	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                        
                        shelly.1
                        2025-06-03 21:41:40.871	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                        
                        shelly.1
                        2025-06-03 21:41:40.870	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                        
                        shelly.1
                        2025-06-03 21:41:40.870	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                        

                        Es lief alles reibunsglos. Auch frage ich mich, warum hinter den IP Adressen im Text ein "!" steht.

                        Anbei einmal ein Screenshot von einem Teilnehmer auf der Adapter Instanz.

                        Screenshot 2025-06-03 214556.png
                        Screenshot 2025-06-03 214715.png
                        Hat da jemand einen Tipp ?

                        Gruß André

                        Das hat zwar nichts mit ALPHA Tests zu tun - derzeit läuft nicht mal einer - ABER:

                        Kontrollier mal dein MQTT Passwort (und auch gleich den Username für MQTT).

                        Bitte beachte, dass das Passwort am Shelly bei JEDER (!) Änderung der MQTT Einstellungen neu eingegeben werden muss. Und dass der Shelly nachher restartet werden muss.

                        Falls du auch ein HTTP Passwort gesetzt hast, verwende für HTTP und MQTT unterschiedliche Usernames und Passwörter. (Hab keine Erklärung und auch noch icht expolizit getestet aber es gab eine diesbezügliche Meldung vin ein oder 2 User die meinten dass es bei identem Username / Passwortkombinationen für HTTP und MQTT Probleme gäbe).

                        gelberlemmyG Offline
                        gelberlemmyG Offline
                        gelberlemmy
                        schrieb am zuletzt editiert von
                        #75

                        @mcm1957 Danke, aber das habe ich alles bereits getan. Lese aber gerade im Shelly Forum, dass es bei Firmware Probleme gibt. Da haben einige, dass Sie sich nicht mal mehr an der CLoud anmelden kann. Suche gerade das Firmwarefile zum downgraden zum testen.

                        mcm1957M 1 Antwort Letzte Antwort
                        0
                        • gelberlemmyG gelberlemmy

                          @mcm1957 Danke, aber das habe ich alles bereits getan. Lese aber gerade im Shelly Forum, dass es bei Firmware Probleme gibt. Da haben einige, dass Sie sich nicht mal mehr an der CLoud anmelden kann. Suche gerade das Firmwarefile zum downgraden zum testen.

                          mcm1957M Offline
                          mcm1957M Offline
                          mcm1957
                          schrieb am zuletzt editiert von
                          #76

                          @gelberlemmy

                          • Welche Firmware hast du die die Probleme macht?
                          • Wenn du einen Links ins Shelly Forum hast, dann post den gerne auch hier.

                          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

                          gelberlemmyG 1 Antwort Letzte Antwort
                          0
                          • mcm1957M mcm1957

                            @gelberlemmy

                            • Welche Firmware hast du die die Probleme macht?
                            • Wenn du einen Links ins Shelly Forum hast, dann post den gerne auch hier.
                            gelberlemmyG Offline
                            gelberlemmyG Offline
                            gelberlemmy
                            schrieb am zuletzt editiert von gelberlemmy
                            #77

                            @mcm1957 Das ist die 1.6.2
                            Auf allen Geräte unter dem Adapter sind auf 1.6.2 . Da scheint es wirklich ein Problem mit der Version zu geben.

                            Der Post im Shelly Forum war leider für 1.5.0 und nicht für1.6.2.

                            Leider finde aktuell ich keine Firmware zum Downgrade.Beim Linkgenerator habe ich irgendwie nicht den korrekten Typen gefunden. Oder ich bin ein wenig Blind...:face_with_head_bandage:

                            mcm1957M 1 Antwort Letzte Antwort
                            0
                            • gelberlemmyG gelberlemmy

                              @mcm1957 Das ist die 1.6.2
                              Auf allen Geräte unter dem Adapter sind auf 1.6.2 . Da scheint es wirklich ein Problem mit der Version zu geben.

                              Der Post im Shelly Forum war leider für 1.5.0 und nicht für1.6.2.

                              Leider finde aktuell ich keine Firmware zum Downgrade.Beim Linkgenerator habe ich irgendwie nicht den korrekten Typen gefunden. Oder ich bin ein wenig Blind...:face_with_head_bandage:

                              mcm1957M Offline
                              mcm1957M Offline
                              mcm1957
                              schrieb am zuletzt editiert von
                              #78

                              @gelberlemmy
                              Wenn möglich teste mal gegen den MQTT Adapter. Wenns dort auch nicht geht dann brauchen wir auf ioBroker Seite gra nicht suchen,

                              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

                              gelberlemmyG 1 Antwort Letzte Antwort
                              0
                              • mcm1957M mcm1957

                                @gelberlemmy
                                Wenn möglich teste mal gegen den MQTT Adapter. Wenns dort auch nicht geht dann brauchen wir auf ioBroker Seite gra nicht suchen,

                                gelberlemmyG Offline
                                gelberlemmyG Offline
                                gelberlemmy
                                schrieb am zuletzt editiert von
                                #79

                                @mcm1957 ich probiere das aus. Aber dann würde es ja zumindest hier her gehören, wenn die Version 1.6.2 nicht mit dem Shelly Adapter funktioniert.

                                mcm1957M 2 Antworten Letzte Antwort
                                0
                                • gelberlemmyG gelberlemmy

                                  @mcm1957 ich probiere das aus. Aber dann würde es ja zumindest hier her gehören, wenn die Version 1.6.2 nicht mit dem Shelly Adapter funktioniert.

                                  mcm1957M Offline
                                  mcm1957M Offline
                                  mcm1957
                                  schrieb am zuletzt editiert von
                                  #80

                                  @gelberlemmy
                                  Ja ja passt schon. Leg gerne alle Infos zum Problem da mal ab.

                                  Und wenn sonst wer was dazu sagen kann - insbesondere dass bei ihm die Shelly FW 1.6.2 normal funktioniert BITTE MITTEILEN.

                                  P.S.: Welche(r) Shelly Typ(en) ist/sind eigentlich bei dir betroffen?

                                  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

                                  B Peter V.P 2 Antworten Letzte Antwort
                                  0
                                  • mcm1957M mcm1957

                                    @gelberlemmy
                                    Ja ja passt schon. Leg gerne alle Infos zum Problem da mal ab.

                                    Und wenn sonst wer was dazu sagen kann - insbesondere dass bei ihm die Shelly FW 1.6.2 normal funktioniert BITTE MITTEILEN.

                                    P.S.: Welche(r) Shelly Typ(en) ist/sind eigentlich bei dir betroffen?

                                    B Offline
                                    B Offline
                                    bommel_030
                                    schrieb am zuletzt editiert von
                                    #81

                                    @mcm1957
                                    Ich hab u.a. nen Shelly Uni Plus 1.6.2 mit dem Shelly Adapter 10.0.0 am laufen und habe keine Probleme.

                                    1 Antwort Letzte Antwort
                                    2
                                    • mcm1957M mcm1957

                                      @gelberlemmy
                                      Ja ja passt schon. Leg gerne alle Infos zum Problem da mal ab.

                                      Und wenn sonst wer was dazu sagen kann - insbesondere dass bei ihm die Shelly FW 1.6.2 normal funktioniert BITTE MITTEILEN.

                                      P.S.: Welche(r) Shelly Typ(en) ist/sind eigentlich bei dir betroffen?

                                      Peter V.P Online
                                      Peter V.P Online
                                      Peter V.
                                      schrieb am zuletzt editiert von
                                      #82

                                      @mcm1957
                                      Mit der (alpha) Version 10 läuft ohne Probleme:
                                      Shelly PlusPlugS : 1.6.2
                                      Shelly PlusPlugS Gen3 : matter.123
                                      Shelly PM Mini Gen2 : 1.6.2
                                      Shelly PM Mini Gen3: 1.6.2
                                      Shelly 1PM Mini Gen2 : 1.6.2
                                      Shelly 1PM Mini Gen3 : 1.6.2
                                      Shelly DoorWindow/Button : BLE (via PlusPlugS Gen2)
                                      Shelly Plus2PM : 1.6.2
                                      Shelly Pro 3 EM-CT63 : 1.6.2
                                      Shelly 3EM63 Gen3 : 1.6.2
                                      und diverse Shelly Plus HT / Shelly Buttons / Shelly Flood
                                      demnächst:
                                      Shelly 1 Mini Gen4 & Shelly 1PM Mini Gen4

                                      AndreiosA 1 Antwort Letzte Antwort
                                      1
                                      • gelberlemmyG gelberlemmy

                                        @mcm1957 ich probiere das aus. Aber dann würde es ja zumindest hier her gehören, wenn die Version 1.6.2 nicht mit dem Shelly Adapter funktioniert.

                                        mcm1957M Offline
                                        mcm1957M Offline
                                        mcm1957
                                        schrieb am zuletzt editiert von
                                        #83

                                        @gelberlemmy
                                        Nach dem letzten Comment dürfte da doch ein Problem bei deiner INstallation (oder beim Adapter) vorliegen.

                                        Bitte verifiziere nochmals explizit die MQTT (nicht die HTTP) Username / Passwortkombinatio n und gib sie zumindest bei einem Shelly explizit neu ein uns reboote diesen zum Test.

                                        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

                                        gelberlemmyG 1 Antwort Letzte Antwort
                                        0
                                        • mcm1957M mcm1957

                                          @gelberlemmy
                                          Nach dem letzten Comment dürfte da doch ein Problem bei deiner INstallation (oder beim Adapter) vorliegen.

                                          Bitte verifiziere nochmals explizit die MQTT (nicht die HTTP) Username / Passwortkombinatio n und gib sie zumindest bei einem Shelly explizit neu ein uns reboote diesen zum Test.

                                          gelberlemmyG Offline
                                          gelberlemmyG Offline
                                          gelberlemmy
                                          schrieb am zuletzt editiert von
                                          #84

                                          @mcm1957 Okay habe ich gemacht. Ich bekomme es nicht hin. Port geändert, anderen Shelly adapter abgeschaltet. MQTT Adapter deaktiviert.... Wenn ich ein Gerät in MQTT Adapter hänge, da wird dieser Datenpunkt auch angelegt. So habe jetzt wirklich rumgespielt. Ports geändert usw. Habe einmal einige Einstellungen gescreenshotet. Auch die Protokolle auf Debug gestellt. Das kam aus heiteren Himmel. Vorher hatte ich wirklich keine Probleme.
                                          Folgende Geräte habe ich :

                                          1xShelly 3 Pro
                                          2x Shelly 1 plus
                                          1x Shelly 1 plus pm

                                          Screenshot 2025-06-04 180643.png Screenshot 2025-06-04 180654.png Screenshot 2025-06-04 180715.png

                                          shelly.1
                                          2025-06-04 18:08:35.931	debug	[MQTT Server] Close for 192.168.171.80 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.931	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.931	debug	[deviceStatusUpdate] shellyplus1#64b7080b3d78#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.931	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1)
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.931	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.929	debug	[MQTT Server] End for 192.168.171.80 ((shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1))
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.928	debug	[deviceStatusUpdate] shellypro3#2cbcbba79f0c#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.926	debug	[onlineCheck] Checking shellypro3#2cbcbba79f0c#1 on 192.168.171.158:80
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.551	debug	[deviceStatusUpdate] shellyplus1pm#a8032ab96a08#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.548	debug	[onlineCheck] Checking shellyplus1pm#a8032ab96a08#1 on 192.168.171.51:80
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.289	debug	[deviceStatusUpdate] shellyplus1#64b7080b3d78#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:08:35.285	debug	[onlineCheck] Checking shellyplus1#64b7080b3d78#1 on 192.168.171.80:80
                                          
                                          shelly.1
                                          2025-06-04 18:08:27.684	debug	[MQTT Server] Close for 192.168.171.106 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:08:27.684	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:08:27.684	debug	[deviceStatusUpdate] shellyplus1#441793a712a8#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:08:27.684	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1)
                                          
                                          shelly.1
                                          2025-06-04 18:08:27.683	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:08:27.683	debug	[MQTT Server] End for 192.168.171.106 ((shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1))
                                          
                                          shelly.1
                                          2025-06-04 18:08:27.531	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:08:25.936	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                                          
                                          shelly.1
                                          2025-06-04 18:08:25.936	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:08:25.936	debug	[BaseClient] Destroying (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:08:25.935	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":98,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-64b7080b3d78/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-64b7080b3d78","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:08:25.934	debug	[MQTT Server] New connection from 192.168.171.80
                                          
                                          shelly.1
                                          2025-06-04 18:08:19.926	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:08:17.685	info	[MQTT] Device with client id "shellyplus1-441793a712a8" connected from 192.168.171.106!
                                          
                                          shelly.1
                                          2025-06-04 18:08:17.685	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:08:17.684	debug	[BaseClient] Destroying (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:08:17.684	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":88,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"Deckenlampe WZ/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-441793a712a8","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:08:17.683	debug	[MQTT Server] New connection from 192.168.171.106
                                          
                                          shelly.1
                                          2025-06-04 18:08:17.499	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:08:15.545	debug	[MQTT Server] Close for 192.168.171.158 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:08:15.545	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:08:15.545	debug	[deviceStatusUpdate] shellypro3#2cbcbba79f0c#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:08:15.545	debug	[BaseClient] Destroying (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1)
                                          
                                          shelly.1
                                          2025-06-04 18:08:15.545	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:08:15.544	debug	[MQTT Server] End for 192.168.171.158 ((shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1))
                                          
                                          shelly.1
                                          2025-06-04 18:08:07.558	debug	[createObjects] Starting object creation of (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:08:05.547	info	[MQTT] Device with client id "shellypro3-2cbcbba79f0c" connected from 192.168.171.158!
                                          
                                          shelly.1
                                          2025-06-04 18:08:05.547	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:08:05.547	debug	[BaseClient] Destroying (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:08:05.547	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":"shellypro3-2cbcbba79f0c/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellypro3-2cbcbba79f0c","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:08:05.546	debug	[MQTT Server] New connection from 192.168.171.158
                                          
                                          shelly.1
                                          2025-06-04 18:07:40.291	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1","shellypro3#2cbcbba79f0c#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:07:38.514	debug	[MQTT Server] Close for 192.168.171.51 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:07:38.514	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:07:38.514	debug	[deviceStatusUpdate] shellyplus1pm#a8032ab96a08#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:07:38.514	debug	[BaseClient] Destroying (shellyplus1pm / shellyplus1pm-a8032ab96a08 / shellyplus1pm#a8032ab96a08#1)
                                          
                                          shelly.1
                                          2025-06-04 18:07:38.514	info	[MQTT] Client Close: (shellyplus1pm / shellyplus1pm-a8032ab96a08 / shellyplus1pm#a8032ab96a08#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:07:38.513	debug	[MQTT Server] End for 192.168.171.51 ((shellyplus1pm / shellyplus1pm-a8032ab96a08 / shellyplus1pm#a8032ab96a08#1))
                                          
                                          shelly.1
                                          2025-06-04 18:07:35.598	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1","shellyplus1pm#a8032ab96a08#1","shellypro3#2cbcbba79f0c#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:07:35.311	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1","shellyplus1pm#a8032ab96a08#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:07:35.211	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:07:34.156	debug	[deviceStatusUpdate] shellypro3#2cbcbba79f0c#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:07:34.155	debug	[onlineCheck] Checking shellypro3#2cbcbba79f0c#1 on 192.168.171.158:80
                                          
                                          shelly.1
                                          2025-06-04 18:07:33.762	debug	[deviceStatusUpdate] shellyplus1pm#a8032ab96a08#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:07:33.755	debug	[onlineCheck] Checking shellyplus1pm#a8032ab96a08#1 on 192.168.171.51:80
                                          
                                          shelly.1
                                          2025-06-04 18:07:33.500	debug	[deviceStatusUpdate] shellyplus1#64b7080b3d78#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:07:33.497	debug	[onlineCheck] Checking shellyplus1#64b7080b3d78#1 on 192.168.171.80:80
                                          
                                          shelly.1
                                          2025-06-04 18:07:30.743	debug	[deviceStatusUpdate] Online devices: []
                                          
                                          shelly.1
                                          2025-06-04 18:07:30.648	debug	[createObjects] Starting object creation of (shellyplus1pm / shellyplus1pm-a8032ab96a08 / shellyplus1pm#a8032ab96a08#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.783	debug	[MQTT Server] Close for 192.168.171.80 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.783	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.783	debug	[deviceStatusUpdate] shellyplus1#64b7080b3d78#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.783	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1)
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.783	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.782	debug	[MQTT Server] End for 192.168.171.80 ((shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1))
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.519	info	[MQTT] Device with client id "shellyplus1pm-a8032ab96a08" connected from 192.168.171.51!
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.519	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.519	debug	[BaseClient] Destroying 192.168.171.51 (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.519	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":102,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-a8032ab96a08/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-a8032ab96a08","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:07:28.518	debug	[MQTT Server] New connection from 192.168.171.51
                                          
                                          shelly.1
                                          2025-06-04 18:07:21.253	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.785	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.785	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.785	debug	[BaseClient] Destroying 192.168.171.80 (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.785	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":98,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-64b7080b3d78/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-64b7080b3d78","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.783	debug	[MQTT Server] New connection from 192.168.171.80
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.214	debug	[MQTT Server] Close for 192.168.171.106 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.214	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.214	debug	[deviceStatusUpdate] shellyplus1#441793a712a8#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.213	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1)
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.213	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:07:18.213	debug	[MQTT Server] End for 192.168.171.106 ((shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1))
                                          
                                          shelly.1
                                          2025-06-04 18:07:11.051	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:07:10.242	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:07:09.297	debug	[MQTT Server] Close for 192.168.171.158 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:07:09.297	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:07:09.297	debug	[deviceStatusUpdate] shellypro3#2cbcbba79f0c#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:07:09.297	debug	[BaseClient] Destroying (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1)
                                          
                                          shelly.1
                                          2025-06-04 18:07:09.297	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:07:09.296	debug	[MQTT Server] End for 192.168.171.158 ((shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1))
                                          
                                          shelly.1
                                          2025-06-04 18:07:08.224	info	[MQTT] Device with client id "shellyplus1-441793a712a8" connected from 192.168.171.106!
                                          
                                          shelly.1
                                          2025-06-04 18:07:08.224	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:07:08.223	debug	[BaseClient] Destroying 192.168.171.106 (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:07:08.223	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":88,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"Deckenlampe WZ/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-441793a712a8","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:07:08.222	debug	[MQTT Server] New connection from 192.168.171.106
                                          
                                          shelly.1
                                          2025-06-04 18:07:00.592	debug	[createObjects] Starting object creation of (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:06:59.307	info	[MQTT] Device with client id "shellypro3-2cbcbba79f0c" connected from 192.168.171.158!
                                          
                                          shelly.1
                                          2025-06-04 18:06:59.307	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:06:59.307	debug	[BaseClient] Destroying 192.168.171.158 (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:59.307	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":"shellypro3-2cbcbba79f0c/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellypro3-2cbcbba79f0c","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:59.306	debug	[MQTT Server] New connection from 192.168.171.158
                                          
                                          shelly.1
                                          2025-06-04 18:06:40.257	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96a08"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.868	debug	[setIP] New IP for device undefined: 192.168.171.51 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.868	debug	[MQTT] Last will for client id "shellyplus1pm-a8032ab96a08" saved: {"retain":true,"qos":0,"topic":"shellyplus1pm-a8032ab96a08/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.868	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.828	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.535	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.535	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96a08"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.535	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.534	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.531	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-64b7080b3d78"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.531	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.530	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-a8032ab96a08"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.530	debug	[setIP] New IP for device undefined: 192.168.171.158 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.529	debug	[MQTT] Last will for client id "shellypro3-2cbcbba79f0c" saved: {"retain":true,"qos":0,"topic":"shellypro3-2cbcbba79f0c/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.529	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.418	debug	[setIP] New IP for device undefined: 192.168.171.80 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.418	debug	[MQTT] Last will for client id "shellyplus1-64b7080b3d78" saved: {"retain":true,"qos":0,"topic":"shellyplus1-64b7080b3d78/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.418	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.418	debug	[setIP] New IP for device undefined: 192.168.171.51 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.418	debug	[MQTT] Last will for client id "shellyplus1pm-a8032ab96a08" saved: {"retain":true,"qos":0,"topic":"shellyplus1pm-a8032ab96a08/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.418	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.418	debug	[setIP] New IP for device undefined: 192.168.171.80 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.418	debug	[MQTT] Last will for client id "shellyplus1-64b7080b3d78" saved: {"retain":true,"qos":0,"topic":"shellyplus1-64b7080b3d78/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.417	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.417	debug	[setIP] New IP for device undefined: 192.168.171.106 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.417	debug	[MQTT] Last will for client id "shellyplus1-441793a712a8" saved: {"retain":true,"qos":0,"topic":"Deckenlampe WZ/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.416	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.416	debug	[setIP] New IP for device undefined: 192.168.171.80 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.416	debug	[MQTT] Last will for client id "shellyplus1-64b7080b3d78" saved: {"retain":true,"qos":0,"topic":"shellyplus1-64b7080b3d78/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.416	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.416	debug	[setIP] New IP for device undefined: 192.168.171.106 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.415	debug	[MQTT] Last will for client id "shellyplus1-441793a712a8" saved: {"retain":true,"qos":0,"topic":"Deckenlampe WZ/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.415	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.414	debug	[setIP] New IP for device undefined: 192.168.171.51 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.414	debug	[MQTT] Last will for client id "shellyplus1pm-a8032ab96a08" saved: {"retain":true,"qos":0,"topic":"shellyplus1pm-a8032ab96a08/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.414	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.414	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.413	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3-2cbcbba79f0c"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.372	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793a712a8"
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.026	debug	[setIP] New IP for device undefined: 192.168.171.158 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.025	debug	[MQTT] Last will for client id "shellypro3-2cbcbba79f0c" saved: {"retain":true,"qos":0,"topic":"shellypro3-2cbcbba79f0c/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.025	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.025	debug	[setIP] New IP for device undefined: 192.168.171.158 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.025	debug	[MQTT] Last will for client id "shellypro3-2cbcbba79f0c" saved: {"retain":true,"qos":0,"topic":"shellypro3-2cbcbba79f0c/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.025	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.024	debug	[setIP] New IP for device undefined: 192.168.171.106 (source: MQTT connect)
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.023	debug	[MQTT] Last will for client id "shellyplus1-441793a712a8" saved: {"retain":true,"qos":0,"topic":"Deckenlampe WZ/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:39.023	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:34.092	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1","shellypro3#2cbcbba79f0c#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:06:34.085	debug	[deviceStatusUpdate] Online devices: ["shellyplus1pm#a8032ab96a08#1","shellyplus1#64b7080b3d78#1","shellypro3#2cbcbba79f0c#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:06:33.382	debug	[deviceStatusUpdate] Online devices: ["shellyplus1pm#a8032ab96a08#1","shellyplus1#64b7080b3d78#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.808	debug	[MQTT Server] Close for 192.168.171.51 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.805	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.805	debug	[deviceStatusUpdate] shellyplus1pm#a8032ab96a08#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.804	debug	[BaseClient] Destroying (shellyplus1pm / shellyplus1pm-a8032ab96a08 / shellyplus1pm#a8032ab96a08#1)
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.804	info	[MQTT] Client Close: (shellyplus1pm / shellyplus1pm-a8032ab96a08 / shellyplus1pm#a8032ab96a08#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.803	debug	[MQTT Server] End for 192.168.171.51 ((shellyplus1pm / shellyplus1pm-a8032ab96a08 / shellyplus1pm#a8032ab96a08#1))
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.487	debug	[deviceStatusUpdate] shellypro3#2cbcbba79f0c#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.485	debug	[onlineCheck] Checking shellypro3#2cbcbba79f0c#1 on 192.168.171.158:80
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.311	debug	[deviceStatusUpdate] shellyplus1pm#a8032ab96a08#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:06:32.308	debug	[onlineCheck] Checking shellyplus1pm#a8032ab96a08#1 on 192.168.171.51:80
                                          
                                          shelly.1
                                          2025-06-04 18:06:31.887	debug	[deviceStatusUpdate] shellyplus1#64b7080b3d78#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:06:31.879	debug	[onlineCheck] Checking shellyplus1#64b7080b3d78#1 on 192.168.171.80:80
                                          
                                          shelly.1
                                          2025-06-04 18:06:26.140	debug	[deviceStatusUpdate] Online devices: ["shellyplus1pm#a8032ab96a08#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:06:24.853	debug	[createObjects] Starting object creation of (shellyplus1pm / shellyplus1pm-a8032ab96a08 / shellyplus1pm#a8032ab96a08#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:06:24.314	debug	[MQTT Server] Close for 192.168.171.80 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:06:24.314	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:06:24.314	debug	[deviceStatusUpdate] shellyplus1#64b7080b3d78#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:06:24.314	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1)
                                          
                                          shelly.1
                                          2025-06-04 18:06:24.314	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:06:24.313	debug	[MQTT Server] End for 192.168.171.80 ((shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1))
                                          
                                          shelly.1
                                          2025-06-04 18:06:22.807	info	[MQTT] Device with client id "shellyplus1pm-a8032ab96a08" connected from 192.168.171.51!
                                          
                                          shelly.1
                                          2025-06-04 18:06:22.807	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:06:22.807	debug	[BaseClient] Destroying (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:22.807	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":102,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-a8032ab96a08/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-a8032ab96a08","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:22.806	debug	[MQTT Server] New connection from 192.168.171.51
                                          
                                          shelly.1
                                          2025-06-04 18:06:15.767	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-64b7080b3d78 / shellyplus1#64b7080b3d78#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:06:14.321	info	[MQTT] Device with client id "shellyplus1-64b7080b3d78" connected from 192.168.171.80!
                                          
                                          shelly.1
                                          2025-06-04 18:06:14.321	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:06:14.321	debug	[BaseClient] Destroying (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:06:14.321	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":98,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-64b7080b3d78/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-64b7080b3d78","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:06:14.320	debug	[MQTT Server] New connection from 192.168.171.80
                                          
                                          shelly.1
                                          2025-06-04 18:06:08.615	debug	[MQTT Server] Close for 192.168.171.106 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:06:08.615	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:06:08.615	debug	[deviceStatusUpdate] shellyplus1#441793a712a8#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:06:08.615	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1)
                                          
                                          shelly.1
                                          2025-06-04 18:06:08.615	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:06:08.614	debug	[MQTT Server] End for 192.168.171.106 ((shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1))
                                          
                                          shelly.1
                                          2025-06-04 18:06:02.704	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1","shellyplus1pm#a8032ab96a08#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:06:01.409	debug	[MQTT Server] Close for 192.168.171.158 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:06:01.409	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:06:01.408	debug	[deviceStatusUpdate] shellypro3#2cbcbba79f0c#1: false
                                          
                                          shelly.1
                                          2025-06-04 18:06:01.408	debug	[BaseClient] Destroying (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1)
                                          
                                          shelly.1
                                          2025-06-04 18:06:01.408	info	[MQTT] Client Close: (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) (false)
                                          
                                          shelly.1
                                          2025-06-04 18:06:01.407	debug	[MQTT Server] End for 192.168.171.158 ((shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1))
                                          
                                          shelly.1
                                          2025-06-04 18:06:00.522	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-441793a712a8 / shellyplus1#441793a712a8#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:05:58.624	info	[MQTT] Device with client id "shellyplus1-441793a712a8" connected from 192.168.171.106!
                                          
                                          shelly.1
                                          2025-06-04 18:05:58.624	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:05:58.624	debug	[BaseClient] Destroying (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:05:58.623	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":88,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"Deckenlampe WZ/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-441793a712a8","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:05:58.622	debug	[MQTT Server] New connection from 192.168.171.106
                                          
                                          shelly.1
                                          2025-06-04 18:05:53.005	debug	[createObjects] Starting object creation of (shellypro3 / shellypro3-2cbcbba79f0c / shellypro3#2cbcbba79f0c#1) for mode: <not set>
                                          
                                          shelly.1
                                          2025-06-04 18:05:51.418	info	[MQTT] Device with client id "shellypro3-2cbcbba79f0c" connected from 192.168.171.158!
                                          
                                          shelly.1
                                          2025-06-04 18:05:51.418	debug	[MQTT] Destroying
                                          
                                          shelly.1
                                          2025-06-04 18:05:51.418	debug	[BaseClient] Destroying (undefined / undefined / undefined)
                                          
                                          shelly.1
                                          2025-06-04 18:05:51.418	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":"shellypro3-2cbcbba79f0c/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellypro3-2cbcbba79f0c","username":"Clients","password":{"type":"Buffer","data":[76,97,108,101,108,105,115,115,121,49,52]}}
                                          
                                          shelly.1
                                          2025-06-04 18:05:51.416	debug	[MQTT Server] New connection from 192.168.171.158
                                          
                                          shelly.1
                                          2025-06-04 18:05:32.222	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1","shellyplus1pm#a8032ab96a08#1","shellypro3#2cbcbba79f0c#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:05:31.859	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1","shellyplus1pm#a8032ab96a08#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:05:31.555	debug	[deviceStatusUpdate] Online devices: ["shellyplus1#64b7080b3d78#1"]
                                          
                                          shelly.1
                                          2025-06-04 18:05:30.854	debug	[deviceStatusUpdate] shellypro3#2cbcbba79f0c#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:05:30.853	debug	[onlineCheck] Checking shellypro3#2cbcbba79f0c#1 on 192.168.171.158:80
                                          
                                          shelly.1
                                          2025-06-04 18:05:30.298	debug	[deviceStatusUpdate] shellyplus1pm#a8032ab96a08#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:05:30.295	debug	[onlineCheck] Checking shellyplus1pm#a8032ab96a08#1 on 192.168.171.51:80
                                          
                                          shelly.1
                                          2025-06-04 18:05:30.212	debug	[deviceStatusUpdate] shellyplus1#64b7080b3d78#1: true
                                          
                                          shelly.1
                                          2025-06-04 18:05:30.208	debug	[onlineCheck] Checking shellyplus1#64b7080b3d78#1 on 192.168.171.80:80
                                          
                                          shelly.1
                                          2025-06-04 18:05:24.448	debug	[deviceStatusUpdate] Online devices: []
                                          
                                          shelly.1
                                          2025-06-04 18:05:23.155	debug	[MQTT Server] Close for 192.168.171.51 ((undefined / undefined / undefined))
                                          
                                          shelly.1
                                          2025-06-04 18:05:23.155	debug	[MQTT] Destroying
                                          
                                          Peter V.P mcm1957M 2 Antworten Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          348

                                          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