Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. IOBroker hängt sich nach Crash und Neuinstallation oft auf

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    IOBroker hängt sich nach Crash und Neuinstallation oft auf

    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      Greenhorn last edited by

      Hier ein neues iob diag

      Skript v.2023-10-10
      
      *** BASE SYSTEM ***
       Static hostname: iobroker
             Icon name: computer
      Operating System: Debian GNU/Linux 12 (bookworm)
                Kernel: Linux 6.1.0-rpi8-rpi-v8
          Architecture: arm64
      
      Model		: Raspberry Pi 4 Model B Rev 1.5
      Docker          : false
      Virtualization  : none
      Kernel          : aarch64
      Userland        : arm64
      
      Systemuptime and Load:
       20:04:44 up 33 min,  4 users,  load average: 3.18, 1.98, 1.30
      CPU threads: 4
      
      
      *** RASPBERRY THROTTLING ***
      Current issues:
      No throttling issues detected.
      
      Previously detected issues:
      No throttling issues detected.
      
      *** Time and Time Zones ***
                     Local time: Sun 2024-03-10 20:04:44 CET
                 Universal time: Sun 2024-03-10 19:04:44 UTC
                       RTC time: n/a
                      Time zone: Europe/Berlin (CET, +0100)
      System clock synchronized: yes
                    NTP service: active
                RTC in local TZ: no
      
      *** User and Groups ***
      simon
      /home/simon
      simon adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker
      
      *** X-Server-Setup ***
      X-Server: 	false
      Desktop: 	
      Terminal: 	tty
      Boot Target: 	graphical.target
      
      *** MEMORY ***
                     total        used        free      shared  buff/cache   available
      Mem:            4.0G        3.4G        489M         14M        265M        603M
      Swap:           104M        104M        249K
      Total:          4.1G        3.5G        489M
      
               3793 M total memory
               3217 M used memory
               2880 M active memory
                210 M inactive memory
                466 M free memory
                  1 M buffer memory
                252 M swap cache
                 99 M total swap
                 99 M used swap
                  0 M free swap
      
      Raspberry only:
      oom events: 0
      lifetime oom required: 0 Mbytes
      total time in oom handler: 0 ms
      max time spent in oom handler: 0 ms
      
      
      *** FAILED SERVICES ***
      
        UNIT LOAD ACTIVE SUB DESCRIPTION
      0 loaded units listed.
      
      *** FILESYSTEM ***
      Filesystem     Type      Size  Used Avail Use% Mounted on
      udev           devtmpfs  1.6G     0  1.6G   0% /dev
      tmpfs          tmpfs     380M  1.3M  379M   1% /run
      /dev/mmcblk0p2 ext4      117G  6.6G  105G   6% /
      tmpfs          tmpfs     1.9G  148K  1.9G   1% /dev/shm
      tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
      /dev/mmcblk0p1 vfat      510M   74M  437M  15% /boot/firmware
      tmpfs          tmpfs     380M   36K  380M   1% /run/user/1000
      
      Messages concerning ext4 filesystem in dmesg:
      [Sun Mar 10 19:31:39 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=D8:3A:DD:0F:E4:E2 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=ccc359c3-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=DE
      [Sun Mar 10 19:31:42 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
      [Sun Mar 10 19:31:44 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.
      
      Show mounted filesystems \(real ones only\):
      TARGET               SOURCE         FSTYPE      OPTIONS
      /                    /dev/mmcblk0p2 ext4        rw,noatime,commit=600
      |-/run/user/1000/doc portal         fuse.portal rw,nosuid,nodev,relatime,user_id=1000,group_id=1000
      `-/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:
      774M	/var/
      285M	/var/log
      284M	/var/log/journal/8ec53d3bc1c549d5b36274323c1b8255
      284M	/var/log/journal
      195M	/var/lib
      
      Archived and active journals take up 283.8M in the file system.
      
      /opt/iobroker/backups:
      12M	/opt/iobroker/backups/
      60K	/opt/iobroker/backups/tmpJavis0
      4.0K	/opt/iobroker/backups/tmpJavis0/states
      
      /opt/iobroker/iobroker-data:
      333M	/opt/iobroker/iobroker-data/
      163M	/opt/iobroker/iobroker-data/files
      57M	/opt/iobroker/iobroker-data/files/javascript.admin
      46M	/opt/iobroker/iobroker-data/backup-objects
      38M	/opt/iobroker/iobroker-data/files/javascript.admin/static
      
      The five largest files in iobroker-data are:
      124M	/opt/iobroker/iobroker-data/objects.jsonl
      22M	/opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js.map
      8.3M	/opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js
      7.0M	/opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.d0c8b930.chunk.js.map
      6.3M	/opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map
      
      USB-Devices by-id:
      USB-Sticks -  Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id':
      
      /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4d856ba1ab6ed1196ded60ea8669f5d-if00-port0
      
      *** NodeJS-Installation ***
      
      /usr/bin/nodejs 	v18.19.1
      /usr/bin/node 		v18.19.1
      /usr/bin/npm 		10.2.4
      /usr/bin/npx 		10.2.4
      /usr/bin/corepack 	0.22.0
      
      
      nodejs:
        Installed: 18.19.1-1nodesource1
        Candidate: 18.19.1-1nodesource1
        Version table:
       *** 18.19.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
              100 /var/lib/dpkg/status
           18.19.0+dfsg-6~deb12u1 500
              500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages
           18.19.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.18.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.18.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.18.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.17.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.17.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.16.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.16.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.15.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.14.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.14.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.14.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.13.0+dfsg1-1 500
              500 http://deb.debian.org/debian bookworm/main arm64 Packages
           18.13.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.12.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.11.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.10.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.9.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.9.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.8.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.7.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.6.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.5.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.4.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.3.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.2.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.1.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
           18.0.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
      
      Temp directories causing npm8 problem: 0
      No problems detected
      
      Errors in npm tree:
      
      *** ioBroker-Installation ***
      
      ioBroker Status
      iobroker is running on this host.
      
      
      Objects type: jsonl
      States  type: jsonl
      
      Core adapters versions
      js-controller: 	5.0.19
      admin: 		6.13.16
      javascript: 	7.8.0
      
      Adapters from github: 	0
      
      Adapter State
      + system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.backitup.0               : backitup              : iobroker                                 -  enabled
      + system.adapter.discovery.0              : discovery             : iobroker                                 -  enabled
      + system.adapter.hmip.0                   : hmip                  : iobroker                                 -  enabled
      + system.adapter.iqontrol.0               : iqontrol              : iobroker                                 -  enabled
        system.adapter.jarvis.0                 : jarvis                : iobroker                                 - disabled
        system.adapter.javascript.0             : javascript            : iobroker                                 - disabled
        system.adapter.link.0                   : link                  : iobroker                                 - disabled
      + system.adapter.midea.0                  : midea                 : iobroker                                 -  enabled
      + system.adapter.mqtt.0                   : mqtt                  : iobroker                                 -  enabled, port: 1883, bind: 192.168.178.96
      + system.adapter.shelly.0                 : shelly                : iobroker                                 -  enabled, port: 1882, bind: 0.0.0.0
      + system.adapter.sonoff.0                 : sonoff                : iobroker                                 -  enabled, port: 1883, bind: 192.168.178.96
        system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : iobroker                                 - disabled
        system.adapter.vis.0                    : vis                   : iobroker                                 - disabled
      + system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      + system.adapter.zigbee.0                 : zigbee                : iobroker                                 -  enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4d856ba1ab6ed1196ded60ea8669f5d-if00-port0
        system.adapter.zigbee2mqtt.0            : zigbee2mqtt           : iobroker                                 - disabled
      
      + instance is alive
      
      Enabled adapters with bindings
      + system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.mqtt.0                   : mqtt                  : iobroker                                 -  enabled, port: 1883, bind: 192.168.178.96
      + system.adapter.shelly.0                 : shelly                : iobroker                                 -  enabled, port: 1882, bind: 0.0.0.0
      + system.adapter.sonoff.0                 : sonoff                : iobroker                                 -  enabled, port: 1883, bind: 192.168.178.96
      + system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      + system.adapter.zigbee.0                 : zigbee                : iobroker                                 -  enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4d856ba1ab6ed1196ded60ea8669f5d-if00-port0
      
      ioBroker-Repositories
      stable        : http://download.iobroker.net/sources-dist.json
      beta          : http://download.iobroker.net/sources-dist-latest.json
      
      Active repo(s): stable
      
      Installed ioBroker-Instances
      Used repository: stable
      Adapter    "admin"        : 6.13.16  , installed 6.13.16
      Adapter    "backitup"     : 2.10.11  , installed 2.10.11
      Adapter    "discovery"    : 4.2.0    , installed 4.2.0
      Adapter    "hmip"         : 1.22.0   , installed 1.22.0
      Adapter    "influxdb"     : 4.0.2    , installed 4.0.2
      Adapter    "iqontrol"     : 2.3.0    , installed 2.3.0
      Adapter    "jarvis"       : 3.1.8    , installed 3.1.8
      Adapter    "javascript"   : 7.8.0    , installed 7.8.0
      Controller "js-controller": 5.0.19   , installed 5.0.19
      Adapter    "link"         : 0.5.12   , installed 0.5.12
      Adapter    "midea"        : 0.0.7    , installed 0.0.7
      Adapter    "mqtt"         : 5.2.0    , installed 5.2.0
      Adapter    "shelly"       : 6.6.1    , installed 6.6.1
      Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
      Adapter    "socketio"     : 6.6.0    , installed 6.6.0
      Adapter    "sonoff"       : 3.0.3    , installed 3.0.3
      Adapter    "vis"          : 1.5.4    , installed 1.5.4
      Adapter    "vis-hqwidgets": 1.4.0    , installed 1.4.0
      Adapter    "web"          : 6.2.3    , installed 6.2.3
      Adapter    "ws"           : 2.5.10   , installed 2.5.10
      Adapter    "zigbee"       : 1.10.1   , installed 1.10.1
      Adapter    "zigbee2mqtt"  : 2.13.4   , installed 2.13.4
      
      Objects and States
      Please stand by - This may take a while
      Objects: 	3979
      States: 	3262
      
      *** 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://archive.raspberrypi.com/debian bookworm InRelease
      Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
      Hit:5 https://deb.nodesource.com/node_18.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:1882            0.0.0.0:*               LISTEN      1001       51776      21179/io.shelly.0   
      tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          16115      800/sshd: /usr/sbin 
      tcp        0      0 192.168.178.96:1883     0.0.0.0:*               LISTEN      1001       53265      21197/io.sonoff.0   
      tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       48757      21090/iobroker.js-c 
      tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       52284      21090/iobroker.js-c 
      tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      0          17488      772/cupsd           
      tcp6       0      0 ::1:631                 :::*                    LISTEN      0          17487      772/cupsd           
      tcp6       0      0 :::8081                 :::*                    LISTEN      1001       48847      21108/io.admin.0    
      tcp6       0      0 :::8082                 :::*                    LISTEN      1001       48907      21273/io.web.0      
      tcp6       0      0 :::22                   :::*                    LISTEN      0          16117      800/sshd: /usr/sbin 
      udp        0      0 0.0.0.0:631             0.0.0.0:*                           0          16359      1078/cups-browsed   
      udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        13011      553/avahi-daemon: r 
      udp        0      0 0.0.0.0:44590           0.0.0.0:*                           104        13013      553/avahi-daemon: r 
      udp6       0      0 :::58315                :::*                                104        13014      553/avahi-daemon: r 
      udp6       0      0 :::5353                 :::*                                104        13012      553/avahi-daemon: r 
      
      *** Log File - Last 25 Lines ***
      
      2024-03-10 20:04:12.912  - warn: zigbee.0 (21212) DeviceAvailability:Failed to ping 0xf0d1b8be2408284c B40 DIM T
      2024-03-10 20:04:12.899  - info: shelly.0 (21179) [MQTT] Device with client id "shellypro1-30c6f781f3c8" connected!
      2024-03-10 20:04:13.017  - warn: zigbee.0 (21212) DeviceAvailability:Failed to ping 0x001788010d3ec68f LWA024
      2024-03-10 20:04:13.199  - warn: zigbee.0 (21212) DeviceAvailability:Failed to ping 0x001788010db790af LWU002
      2024-03-10 20:04:13.326  - warn: zigbee.0 (21212) DeviceAvailability:Failed to ping 0x001788010d3fd6b1 LWA024
      2024-03-10 20:04:19.152  - info: shelly.0 (21179) [MQTT] Client Close:  (shellyplus1pm / shellyplus1pm-4855199d7590 / shellyplus1pm#4855199d7590#1) (false)
      2024-03-10 20:04:20.066  - info: shelly.0 (21179) [MQTT] Device with client id "shellyplus1pm-b0b21c1b1e9c" connected!
      2024-03-10 20:04:20.311  - info: shelly.0 (21179) [MQTT] Client Close:  (shellyplus1pm / shellyplus1pm-b48a0a218644 / shellyplus1pm#b48a0a218644#1) (false)
      2024-03-10 20:04:22.281  - info: shelly.0 (21179) [MQTT] Client Close:  (shellyplus1pm / shellyplus1pm-b48a0a21c40c / shellyplus1pm#b48a0a21c40c#1) (false)
      2024-03-10 20:04:22.339  - info: shelly.0 (21179) [MQTT] Client Close:  (shellypro1 / shellypro1-30c6f781f3c8 / shellypro1#30c6f781f3c8#1) (false)
      2024-03-10 20:04:24.067  - info: hmip.0 (21131) hmip adapter connected and ready
      2024-03-10 20:04:24.889  - error: shelly.0 (21179) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-b48a0a21c40c"
      2024-03-10 20:04:24.937  - error: shelly.0 (21179) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199d7590"
      2024-03-10 20:04:24.939  - error: shelly.0 (21179) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-b48a0a218644"
      2024-03-10 20:04:24.941  - error: shelly.0 (21179) [MQTT] Unable to get mqttprefix of client with id "shellypro1-30c6f781f3c8"
      2024-03-10 20:05:16.854  - info: shelly.0 (21179) [MQTT] Device with client id "shellypro1-30c6f781f3c8" connected!
      2024-03-10 20:05:17.119  - info: shelly.0 (21179) [MQTT] Device with client id "shellyplus1pm-4855199d7590" connected!
      2024-03-10 20:05:19.052  - info: shelly.0 (21179) [MQTT] Device with client id "shellyplus1pm-b48a0a218644" connected!
      2024-03-10 20:05:22.762  - info: shelly.0 (21179) [MQTT] Device with client id "shellyplus1pm-b48a0a21c40c" connected!
      2024-03-10 20:05:26.887  - info: shelly.0 (21179) [MQTT] Client Close: 192.168.178.28 (shellypro1 / shellypro1-30c6f781f3c8 / shellypro1#30c6f781f3c8#1) (false)
      2024-03-10 20:05:26.929  - error: shelly.0 (21179) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for  (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace')
      2024-03-10 20:05:26.929  - error: shelly.0 (21179) [MQTT] Unable to get mqttprefix of client with id "shellypro1-30c6f781f3c8"
      2024-03-10 20:05:27.133  - info: shelly.0 (21179) [MQTT] Client Close: 192.168.178.150 (shellyplus1pm / shellyplus1pm-4855199d7590 / shellyplus1pm#4855199d7590#1) (false)
      2024-03-10 20:05:27.216  - error: shelly.0 (21179) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for  (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace')
      2024-03-10 20:05:27.216  - error: shelly.0 (21179) [MQTT] Unable to get mqttprefix of client with id "shellyplus1pm-4855199d7590"
      
      
      ======================= SUMMARY =======================
      			v.2023-10-10
      
      
       Static hostname: iobroker
             Icon name: computer
      Operating System: Debian GNU/Linux 12 (bookworm)
                Kernel: Linux 6.1.0-rpi8-rpi-v8
          Architecture: arm64
      
      Installation: 		native
      Kernel: 		aarch64
      Userland: 		arm64
      Timezone: 		Europe/Berlin (CET, +0100)
      User-ID: 		1000
      X-Server: 		false
      Boot Target: 		graphical.target
      
      Pending OS-Updates: 	0
      Pending iob updates: 	0
      
      Nodejs-Installation: 	/usr/bin/nodejs 	v18.19.1
      			/usr/bin/node 		v18.19.1
      			/usr/bin/npm 		10.2.4
      			/usr/bin/npx 		10.2.4
      			/usr/bin/corepack 	0.22.0
      
      Recommended versions are nodejs 18.19.1 and npm 10.2.4
      Your nodejs installation is correct
      
      MEMORY: 
                     total        used        free      shared  buff/cache   available
      Mem:            4.0G        2.9G        596M         14M        621M        1.1G
      Swap:           104M        104M        356K
      Total:          4.1G        3.0G        596M
      
      Active iob-Instances: 	12
      Active repo(s): stable
      
      ioBroker Core: 		js-controller 		5.0.19
      			admin 			6.13.16
      
      ioBroker Status: 	iobroker is running on this host.
      
      
      Objects type: jsonl
      States  type: jsonl
      
      Status admin and web instance:
      + system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      
      Objects: 		3979
      States: 		3262
      
      Size of iob-Database:
      
      124M	/opt/iobroker/iobroker-data/objects.jsonl
      1.4M	/opt/iobroker/iobroker-data/states.jsonl
      
      
      
      =================== END OF SUMMARY ====================
      
      1 Reply Last reply Reply Quote 0
      • G
        Greenhorn @crunchip last edited by Greenhorn

        @crunchip
        OK🤔 Welche?

        crunchip 1 Reply Last reply Reply Quote 0
        • crunchip
          crunchip Forum Testing Most Active @Greenhorn last edited by

          @greenhorn dein mqtt und sonoff ist falsch

          G 1 Reply Last reply Reply Quote 1
          • G
            Greenhorn @crunchip last edited by

            @crunchip Ja, beide nutzen den gleichen Port...

            crunchip 1 Reply Last reply Reply Quote 0
            • crunchip
              crunchip Forum Testing Most Active @Greenhorn last edited by crunchip

              @greenhorn das darf nicht, die müssen unterschiedlich sein

              @Homoran kannst du mir sagen warum man aus dem diag nicht einzelne Zeilen markieren/ zitieren kann? da passt doch das Format nicht?

              G Homoran 2 Replies Last reply Reply Quote 0
              • G
                Greenhorn @crunchip last edited by

                @crunchip Klar, kann ich den Port in der Sonoff Instanz einfach ändern auf z.B. 1884 ?

                crunchip 1 Reply Last reply Reply Quote 0
                • crunchip
                  crunchip Forum Testing Most Active @Greenhorn last edited by crunchip

                  @greenhorn ja und du hast beide instanzen fest an die IP gebunden

                  du musst aber bedenken, deine sonoff Geräte musst du entsprechend anpassen, zwecks port

                  1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Greenhorn last edited by

                    @greenhorn sagte in IOBroker hängt sich nach Crash und Neuinstallation oft auf:

                    anschließenden Neuinstallation

                    Warum nimmt man da nicht gleich die 'Lite'-Version, ohne z. B. einem laufenden Drucker-Server wie cupsd?

                    sudo systemctl set-default multi-user.target
                    

                    Sonoff und mqtt hast du auf den gleichen Port auf der gleichen IP laufen.

                    G 1 Reply Last reply Reply Quote 0
                    • G
                      Greenhorn @Thomas Braun last edited by

                      @thomas-braun Wie ändere ich das jetzt?

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators @crunchip last edited by

                        @crunchip muss sich @jey-Cee nochmal ansehen.
                        er hatte was mit dem "alles markieren" optiiert, seitdem gibt es auf Android dieses Problem.
                        Ich fürchte fast, dass genau deswegen vor Jahren das "alles markieren" verändert worden war

                        crunchip 1 Reply Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @Homoran last edited by

                          @homoran sagte in IOBroker hängt sich nach Crash und Neuinstallation oft auf:

                          seitdem gibt es auf Android dieses Problem

                          ich sitz allerdings am PC, aber ja, alles markieren geht, aber einzelne Zeilen beginnt es zu flackern

                          1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @Greenhorn last edited by

                            @greenhorn sagte in IOBroker hängt sich nach Crash und Neuinstallation oft auf:

                            Wie ändere ich das jetzt?

                            Man kann die Ports der mqtt-Broker ändern. Konkret beim sonoff? Keine Ahnung, hab den nicht im Einsatz.

                            G 1 Reply Last reply Reply Quote 0
                            • G
                              Greenhorn @Thomas Braun last edited by Greenhorn

                              @thomas-braun
                              Also einfach im Adapter den Port ändern. Dann muss er aber in allen Geräten geändert werden. Das bedeutet vermutlich mehr Arbeit als beim Sonoff.
                              Die IP-Adresse ist ja die des Raspis, die kann doch nicht einfach im Adapter geändert werden ?

                              Thomas Braun crunchip 2 Replies Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Greenhorn last edited by Thomas Braun

                                @greenhorn

                                Wobei ich auch nicht verstehe, warum man den sonoff ebenfalls als Broker konfiguriert, wenn da schon anderweitig ein mqtt-Broker läuft.

                                crunchip 1 Reply Last reply Reply Quote 0
                                • crunchip
                                  crunchip Forum Testing Most Active @Greenhorn last edited by

                                  @greenhorn hab ich doch oben schon geschrieben
                                  shelly ein Port sowie Geräte gleich
                                  sonoff ein port sowie Geräte gleich
                                  oder
                                  mqtt ein Port und an allen Geräten diesen Port und damit alles empfangen, steuerungs Datenpunkte müssen dann allerdings manuell angelegt werden

                                  1 Reply Last reply Reply Quote 0
                                  • crunchip
                                    crunchip Forum Testing Most Active @Thomas Braun last edited by

                                    @thomas-braun weil der Adapter einiges an Arbeit abnimmt

                                    Thomas Braun 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @crunchip last edited by

                                      @crunchip sagte in IOBroker hängt sich nach Crash und Neuinstallation oft auf:

                                      @thomas-braun weil der Adapter einiges an Arbeit abnimmt

                                      Aber nicht, wenn die beiden dann auf der gleichen Frequenz funken...

                                      crunchip 1 Reply Last reply Reply Quote 0
                                      • crunchip
                                        crunchip Forum Testing Most Active @Thomas Braun last edited by

                                        @thomas-braun dürfen/sollen sie ja nicht, hab ich ihm oben ja schon geschrieben

                                        genau genommen, sollte sogar ein Port Abstand sein

                                        WebSockets – wenn parallel zum TCP-Server, sollte der WebSocket-MQTT-Server laufen.
                                        Port – Port, auf dem der Server ausgeführt wird (Standard 1883). WebSockets werden immer auf Port+1 ausgeführt (Standard 1884)
                                        
                                        1 Reply Last reply Reply Quote 0
                                        • crunchip
                                          crunchip Forum Testing Most Active @Homoran last edited by

                                          @homoran das meinte ich
                                          589ce1eb-3965-4f08-9e44-fb6d29f32f06-image.png aber hat sich mit dem fix ja erledigt

                                          Homoran 1 Reply Last reply Reply Quote 0
                                          • Homoran
                                            Homoran Global Moderator Administrators @crunchip last edited by

                                            @crunchip sagte in IOBroker hängt sich nach Crash und Neuinstallation oft auf:

                                            aber hat sich mit dem fix ja erledigt

                                            oder mit dem Neustart.
                                            Aber was hing da via 127.0.0.1 dran?

                                            crunchip 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

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

                                            806
                                            Online

                                            31.9k
                                            Users

                                            80.3k
                                            Topics

                                            1.3m
                                            Posts

                                            8
                                            118
                                            6539
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo