Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. CCU (RasperryMatic) high cpu usage

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    CCU (RasperryMatic) high cpu usage

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

      • Adaptername: hm.rpc
      • Link zu Adapterrepository: https://github.com/ioBroker/ioBroker.hm-rpc
      • Adapterversion: 2.0.2
      • js-controller Version: ...
      • Admin Version: 7.4.10
      • Hardwaresystem: Hyper-V Intel Xeon
      • Arbeitsspeicher: 4 GB
      • Festplattenart: SSD (RAID1)
      • Betriebssystem: Debian 12
      • Nodejs-Version: v20.18.3
      • NPM-Version: 10.8.2
      • Installationsart: Script
      • Image, Docker genutzt: Nein
      • Ort, Name der Imagedatei: ...
      Script v.2025-02-23
      
      *** BASE SYSTEM ***
       Static hostname: io01
             Icon name: computer-vm
               Chassis: vm 
        Virtualization: microsoft
      Operating System: Debian GNU/Linux 12 (bookworm)
                Kernel: Linux 6.1.0-31-amd64
          Architecture: x86-64
       Hardware Vendor: Microsoft Corporation
      Firmware Version: 090007
      OS is similar to: 
      
      model name: Intel(R) Xeon(R) Silver 4109T CPU @ 2.00GHz
      Docker          : false
      Virtualization  : microsoft
      Kernel          : x86_64
      Userland        : 64 bit
      
      Systemuptime and Load:
       09:09:32 up 20 days, 23:38,  2 users,  load average: 0.14, 0.08, 0.02
      CPU threads: 2
      
      
      *** LIFE CYCLE STATUS ***
      Operating System is the current Debian stable version codenamed 'bookworm'!
      
      *** TIME AND TIMEZONES ***
                     Local time: Tue 2025-03-11 09:09:32 CET
                 Universal time: Tue 2025-03-11 08:09:32 UTC
                       RTC time: Tue 2025-03-11 09:09:33
                      Time zone: Europe/Berlin (CET, +0100)
      System clock synchronized: no
                    NTP service: active
                RTC in local TZ: no
      
      *** Users and Groups ***
      User that called 'iob diag':
      debian-user
      HOME=/home/debian-user
      GROUPS=debian-user cdrom floppy audio dip video plugdev users netdev iobroker
      
      User that is running 'js-controller':
      iobroker
      HOME=/home/iobroker
      GROUPS=iobroker tty dialout audio video plugdev
      
      *** DISPLAY-SERVER SETUP ***
      Display-Server: false
      Desktop: 
      Terminal: tty
      
      System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix'
      
      *** MEMORY ***
                     total        used        free      shared  buff/cache   available
      Mem:            4.1G        1.6G        519M        4.1M        2.2G        2.5G
      Swap:           1.0G        2.6M        1.0G
      Total:          5.1G        1.6G        1.5G
      
      Active iob-Instances: 14
      
               3880 M total memory
               1523 M used memory
                707 M active memory
               2311 M inactive memory
                495 M free memory
                311 M buffer memory
               1832 M swap cache
                974 M total swap
                  2 M used swap
                972 M free swap
      
      *** top - Table Of Processes  ***
      top - 09:09:33 up 20 days, 23:38,  2 users,  load average: 0.14, 0.08, 0.02
      Tasks: 115 total,   1 running, 114 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 :   3880.7 total,    494.0 free,   1525.0 used,   2144.3 buff/cache     
      MiB Swap:    975.0 total,    972.5 free,      2.5 used.   2355.7 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  1.9G     0  1.9G   0% /dev
      tmpfs          tmpfs     389M  580K  388M   1% /run
      /dev/sda1      ext4       58G  5.0G   50G   9% /
      tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
      tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
      tmpfs          tmpfs     389M     0  389M   0% /run/user/1000
      
      Messages concerning ext4 filesystem in dmesg:
      [Tue Feb 18 09:30:39 2025] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none.
      [Tue Feb 18 09:30:40 2025] EXT4-fs (sda1): re-mounted. Quota mode: none.
      
      Show mounted filesystems:
      TARGET SOURCE    FSTYPE OPTIONS
      /      /dev/sda1 ext4   rw,relatime,errors=remount-ro
      
      Files in neuralgic directories:
      
      /var:
      460M/var/
      249M/var/cache
      242M/var/cache/apt
      165M/var/cache/apt/archives
      164M/var/lib
      
      Hint: You are currently not seeing messages from other users and the system.
            Users in groups 'adm', 'systemd-journal' can see all messages.
            Pass -q to turn off this notice.
      Archived and active journals take up 8.0M in the file system.
      
      /opt/iobroker/backups:
      18M/opt/iobroker/backups/
      
      /opt/iobroker/iobroker-data:
      860M/opt/iobroker/iobroker-data/
      803M/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:
      8.7M/opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.js.map
      8.6M/opt/iobroker/iobroker-data/files/javascript.admin/static/js/310.89a60ae1.chunk.js.map
      7.5M/opt/iobroker/iobroker-data/states.jsonl
      7.4M/opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_node_modules_mui_icons-material_esm_index_js.d7ed606b.chunk.js.map
      7.0M/opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.a9c6d34a.chunk.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.18.3
      /usr/bin/node v20.18.3
      /usr/bin/npm 10.8.2
      /usr/bin/npx 10.8.2
      /usr/bin/corepack 0.30.0
      
      nodejs:
        Installed: 20.18.3-1nodesource1
        Candidate: 20.18.3-1nodesource1
        Version table:
       *** 20.18.3-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
              100 /var/lib/dpkg/status
           20.18.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.18.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.18.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.17.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.16.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.15.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.15.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.14.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.13.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.13.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.12.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.12.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.12.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.11.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.11.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.10.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.9.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.8.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.8.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.7.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.6.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.6.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.5.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.5.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.4.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.3.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.3.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.2.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.1.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           20.0.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
           18.19.0+dfsg-6~deb12u2 500
              500 http://deb.debian.org/debian bookworm/main amd64 Packages
           18.19.0+dfsg-6~deb12u1 500
              500 http://security.debian.org/debian-security bookworm-security/main amd64 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:
      io01                io01 (version: 7.0.6, hostname: io01          , alive, uptime: 1812478)
      
      Core adapters versions
      js-controller: 7.0.6
      admin: 7.4.10
      javascript: 8.8.3
      
      nodejs modules from github: 0
      
      Adapter State
      + system.adapter.admin.0                  : admin                 : io01                                     -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.backitup.0               : backitup              : io01                                     -  enabled
      + system.adapter.discovery.0              : discovery             : io01                                     -  enabled
      + system.adapter.email.0                  : email                 : io01                                     -  enabled
      + system.adapter.hm-rega.0                : hm-rega               : io01                                     -  enabled
      + system.adapter.hm-rpc.0                 : hm-rpc                : io01                                     -  enabled, port: 2010
      + system.adapter.hm-rpc.1                 : hm-rpc                : io01                                     -  enabled, port: 8701
      + system.adapter.hm-rpc.2                 : hm-rpc                : io01                                     -  enabled, port: 9292
      + system.adapter.hm-rpc.3                 : hm-rpc                : io01                                     -  enabled
      + system.adapter.javascript.0             : javascript            : io01                                     -  enabled
      + system.adapter.netatmo.0                : netatmo               : io01                                     -  enabled
      + system.adapter.notification-manager.0   : notification-manager  : io01                                     -  enabled
      + system.adapter.pushover.0               : pushover              : io01                                     -  enabled
      
      + instance is alive
      
      Enabled adapters with bindings
      + system.adapter.admin.0                  : admin                 : io01                                     -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.hm-rpc.0                 : hm-rpc                : io01                                     -  enabled, port: 2010
      + system.adapter.hm-rpc.1                 : hm-rpc                : io01                                     -  enabled, port: 8701
      + system.adapter.hm-rpc.2                 : hm-rpc                : io01                                     -  enabled, port: 9292
      
      ioBroker-Repositories
      
       (index)  name      url                                                      auto upgrade 
      
       0        'stable'  'http://download.iobroker.net/sources-dist.json'         false        
       1        'beta'    'http://download.iobroker.net/sources-dist-latest.json'  false        
      
      
      Active repo(s): stable
      Upgrade policy: none
      
      Installed ioBroker-Adapters
      Used repository: stable
      Adapter    "admin"        : 7.4.10   , installed 7.4.10
      Adapter    "backitup"     : 3.0.31   , installed 3.0.31
      Adapter    "discovery"    : 5.0.0    , installed 5.0.0
      Adapter    "email"        : 1.3.1    , installed 1.3.1
      Adapter    "hm-rega"      : 5.1.0    , installed 5.1.0
      Adapter    "hm-rpc"       : 2.0.2    , installed 2.0.2
      Adapter    "javascript"   : 8.8.3    , installed 8.8.3
      Controller "js-controller": 7.0.6    , installed 7.0.6
      Adapter    "netatmo"      : 3.1.0    , installed 3.1.0
      Adapter    "notification-manager": 1.2.1, installed 1.2.1
      Adapter    "pushover"     : 4.1.0    , installed 4.1.0
      
      Objects and States
      Please stand by - This may take a while
      Objects: 2579
      States: 1801
      
      *** OS-Repositories and Updates ***
      Hit:1 http://deb.debian.org/debian bookworm InRelease
      Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
      Hit:3 http://security.debian.org/debian-security bookworm-security InRelease
      Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease
      Reading package lists...
      Pending Updates: 3
      
      *** 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 192.168.179.18:2001     0.0.0.0:*               LISTEN      1001       601365     37298/io.hm-rpc.3   
      tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0          56726      1/init              
      tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          21918      496/sshd: /usr/sbin 
      tcp        0      0 0.0.0.0:8701            0.0.0.0:*               LISTEN      1001       491014     32028/io.hm-rpc.1   
      tcp        0      0 0.0.0.0:2010            0.0.0.0:*               LISTEN      1001       602413     37328/io.hm-rpc.0   
      tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       60427      10863/iobroker.js-c 
      tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       60422      10863/iobroker.js-c 
      tcp        0      0 0.0.0.0:9292            0.0.0.0:*               LISTEN      1001       602265     37283/io.hm-rpc.2   
      tcp6       0      0 :::111                  :::*                    LISTEN      0          56730      1/init              
      tcp6       0      0 :::80                   :::*                    LISTEN      0          21240      508/apache2         
      tcp6       0      0 :::22                   :::*                    LISTEN      0          21929      496/sshd: /usr/sbin 
      tcp6       0      0 :::8081                 :::*                    LISTEN      1001       63175      11526/io.admin.0    
      udp        0      0 0.0.0.0:111             0.0.0.0:*                           0          56728      1/init              
      udp6       0      0 :::111                  :::*                                0          56732      1/init              
      
      *** Log File - Last 25 Lines ***
      
      2025-03-11 08:54:28.040  - info: hm-rega.0 (18280) update favorites to enum.favorites
      2025-03-11 08:54:32.065  - info: hm-rpc.2 (37283) Connected
      2025-03-11 08:54:40.240  - info: host.io01 instance system.adapter.hm-rpc.3 in version "2.0.2" started with pid 37298
      2025-03-11 08:54:41.277  - info: hm-rpc.3 (37298) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:54:41.431  - info: hm-rpc.3 (37298) xmlrpc server is trying to listen on 192.168.179.18:2001
      2025-03-11 08:54:41.431  - info: hm-rpc.3 (37298) xmlrpc client is trying to connect to 192.168.179.25:2001/ with ["http://192.168.179.18:2001","io01:hm-rpc.3:f7f5141fce086a970aa44c1dae75dce3"]
      2025-03-11 08:54:41.447  - info: hm-rpc.3 (37298) xmlrpc <- system.listMethods ["io01:hm-rpc.3:f7f5141fce086a970aa44c1dae75dce3"]
      2025-03-11 08:54:41.453  - info: hm-rpc.3 (37298) xmlrpc <- listDevices ["io01:hm-rpc.3:f7f5141fce086a970aa44c1dae75dce3"]
      2025-03-11 08:54:41.468  - info: hm-rpc.3 (37298) xmlrpc -> 71 devices
      2025-03-11 08:54:41.494  - info: hm-rpc.3 (37298) Connected
      2025-03-11 08:54:49.222  - info: host.io01 instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 37328
      2025-03-11 08:54:50.220  - info: hm-rpc.0 (37328) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:54:50.368  - info: hm-rpc.0 (37328) xmlrpc server is trying to listen on 0.0.0.0:2010
      2025-03-11 08:54:50.369  - info: hm-rpc.0 (37328) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010","io01:hm-rpc.0:2820f225f076966c3b2a6ba47db415be"]
      2025-03-11 08:54:52.782  - info: hm-rpc.0 (37328) Connected
      2025-03-11 08:56:05.161  - info: javascript.0 (11525) script.js.netatmo.Push2CCU: netatmoPush started
      2025-03-11 08:57:00.976  - info: hm-rpc.1 (32028) binrpc -> listDevices 45
      2025-03-11 08:57:00.998  - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 09:00:31.058  - info: hm-rpc.1 (32028) binrpc -> listDevices 45
      2025-03-11 09:00:31.083  - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 09:04:01.140  - info: hm-rpc.1 (32028) binrpc -> listDevices 45
      2025-03-11 09:04:01.161  - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 09:07:31.215  - info: hm-rpc.1 (32028) binrpc -> listDevices 45
      2025-03-11 09:07:31.242  - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 09:08:05.082  - info: javascript.0 (11525) script.js.netatmo.Push2CCU: netatmoPush started
      
      
      ======================= SUMMARY =======================
      v.2025-02-23
      
      
       Static hostname: io01
             Icon name: computer-vm
               Chassis: vm 
        Virtualization: microsoft
      Operating System: Debian GNU/Linux 12 (bookworm)
                Kernel: Linux 6.1.0-31-amd64
          Architecture: x86-64
       Hardware Vendor: Microsoft Corporation
      Firmware Version: 090007
      
      Installation: microsoft
      Kernel: x86_64
      Userland: 64 bit
      Timezone: Europe/Berlin (CET, +0100)
      User-ID: 1000
      Display-Server: false
      Boot Target: graphical.target
      
      Pending OS-Updates: 3
      
      Pending iob updates: 0
      
      Nodejs-Installation:
      /usr/bin/nodejs v20.18.3
      /usr/bin/node v20.18.3
      /usr/bin/npm 10.8.2
      /usr/bin/npx 10.8.2
      /usr/bin/corepack 0.30.0
      
      Recommended versions are nodejs 20.18.3 and npm 10.8.2
      nodeJS installation is correct
      
      MEMORY: 
                     total        used        free      shared  buff/cache   available
      Mem:            4.1G        1.7G        383M        4.1M        2.3G        2.3G
      Swap:           1.0G        2.6M        1.0G
      Total:          5.1G        1.7G        1.4G
      
      Active iob-Instances: 14
      Upgrade policy: none
      
      ioBroker Core: js-controller 7.0.6
      admin 7.4.10
      
      ioBroker Status: iobroker is running on this host.
      
      
      Objects type: jsonl
      States  type: jsonl
      
      Status admin and web instance:
      + system.adapter.admin.0                  : admin                 : io01                                     -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      
      Objects: 2579
      States: 1801
      
      Size of iob-Database:
      
      6.5M/opt/iobroker/iobroker-data/objects.jsonl
      7.5M/opt/iobroker/iobroker-data/states.jsonl
      
      
      Operating System is the current Debian stable version codenamed 'bookworm'!
      
      =================== END OF SUMMARY ====================
      

      Hallo zusammen,

      ich hoffe, ich mache jetzt nicht allzu viel falsch bei meinem ersten Post 😉

      Ich habe vor drei Wochen iobroker installiert, damit ich netatmo weiterhin verwenden kann. Die alte Script-Lösung auf der RaspMatic hat irgendwie nicht mehr funktioniert.

      Ich habe nun das Problem, dass regelmäßig (alle 6 Tage) die CCU praktisch die Arbeit einstellt. Ab dem Moment ist die CPU-Last für einen io-Prozess immer >=25%. Es hilft nur ein Neustart.

      Ein Update der RM-Firmware auf das aktuelle Build hat leider keinen Erfolg gebracht.

      Hat jemand von euch einen Tipp, was ich machen kann? Nach einen reboot der CCU läuft es dann erst einmal wieder bis nächste Woche...

      LG,
      Marcel

      CCU:

      Mem: 853928K used, 116156K free, 12164K shrd, 16012K buff, 228260K cached
      CPU:  25% usr   4% sys   0% nic  69% idle   0% io   0% irq   0% sirq
      Load average: 1.09 0.93 0.62 3/265 5204
        PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
       1583     1 root     S    3731m 394%  26% java -Dos.arch=aarch64 -Dgnu.io.rxtx.S
       5204  5130 root     R     3532   0%   2% top
       1709     1 root     S    2340m 247%   0% /bin/ReGaHss -f /etc/rega.conf -l 0
       5021     1 root     S    1024m 108%   0% node /usr/local/addons/hap-homematic/n
       5038  5021 root     S     714m  75%   0% hap-homematic-config
       1059     1 root     S    78560   8%   0% /usr/sbin/irqbalance --foreground
       1270     1 chrony   S    76748   8%   0% /usr/sbin/chronyd
       1539     1 root     S    26208   3%   0% /bin/rfd -f /var/etc/rfd.conf -l 1
       1005     1 root     S    19848   2%   0% /sbin/udevd -d
       1848     1 root     S    19716   2%   0% /usr/bin/monit -Ic /etc/monitrc
       1478     1 snmp     S    12868   1%   0% /usr/sbin/snmpd -Lsd -Lf /dev/null -c
       1500     1 root     S<   12320   1%   0% /bin/multimacd -f /var/etc/multimacd.c
       1378  1377 root     S    11436   1%   0% /usr/sbin/lighttpd -f /etc/lighttpd/li
       3445     1 root     S    10864   1%   0% /usr/sbin/openvpn --daemon --config /v
       5129  5113 root     S    10160   1%   0% sshd-session: root@pts/0
       5113  1401 root     S     9900   1%   0% sshd-session: root [priv]
       1401     1 root     S     9388   1%   0% sshd: /usr/sbin/sshd [listener] 0 of 1
       4918  1378 root     S     8692   1%   0% /bin/tclsh /www/api/homematic.cgi
        249     1 hssled   S     5524   1%   0% /bin/hss_led -l 6
       1370     1 eq3cfg   S     5320   1%   0% /bin/eq3configd
      
      

      Log iobroker:

      2025-03-11 08:35:30.519 - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 08:36:05.099 - info: javascript.0 (11525) script.js.netatmo.Push2CCU: netatmoPush started
      2025-03-11 08:39:00.576 - info: hm-rpc.1 (32028) binrpc -> listDevices 45
      2025-03-11 08:39:00.605 - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 08:42:30.673 - info: hm-rpc.1 (32028) binrpc -> listDevices 45
      2025-03-11 08:42:30.693 - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 08:44:13.713 - error: hm-rpc.0 (31608) Ping error [io01:hm-rpc.0:01e6220305abd2032df376fcad7ca502]: Unexpected end
      Line: 0
      Column: 0
      Char:
      2025-03-11 08:44:13.721 - info: hm-rpc.0 (31608) Disconnected
      2025-03-11 08:46:00.743 - info: hm-rpc.1 (32028) binrpc -> listDevices 45
      2025-03-11 08:46:00.770 - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 08:48:05.051 - info: javascript.0 (11525) script.js.netatmo.Push2CCU: netatmoPush started
      2025-03-11 08:48:36.258 - error: hm-rpc.0 (31608) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:48:36.267 - error: hm-rpc.0 (31608) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:48:36.273 - error: hm-rpc.0 (31608) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:48:36.276 - error: hm-rpc.0 (31608) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:48:36.281 - error: hm-rpc.0 (31608) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:48:36.285 - error: hm-rpc.0 (31608) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:48:43.731 - error: hm-rpc.0 (31608) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:49:06.261 - info: hm-rpc.0 (31608) xmlrpc -> 192.168.179.25:2010/ init ["http://0.0.0.0:2010",""]
      2025-03-11 08:49:06.267 - error: hm-rpc.0 (31608) Cannot call init: [http://0.0.0.0:2010, ""] Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:49:06.318 - info: hm-rpc.0 (31608) terminating
      2025-03-11 08:49:06.320 - info: hm-rpc.0 (31608) Terminated (NO_ERROR): Without reason
      2025-03-11 08:49:06.861 - info: host.io01 instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
      2025-03-11 08:49:06.865 - info: host.io01 Restart adapter system.adapter.hm-rpc.0 because enabled
      2025-03-11 08:49:30.814 - info: hm-rpc.1 (32028) binrpc -> listDevices 45
      2025-03-11 08:49:30.834 - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 08:49:37.131 - info: host.io01 instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 37178
      2025-03-11 08:49:38.101 - info: hm-rpc.0 (37178) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:49:38.242 - info: hm-rpc.0 (37178) xmlrpc server is trying to listen on 0.0.0.0:2010
      2025-03-11 08:49:38.243 - info: hm-rpc.0 (37178) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010","io01:hm-rpc.0:caa4076c9e6a1de6b37c5ab85e3d75a3"]
      2025-03-11 08:49:38.259 - error: hm-rpc.0 (37178) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:50:08.260 - error: hm-rpc.0 (37178) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:50:08.264 - info: hm-rpc.0 (37178) xmlrpc -> 192.168.179.25:2010/ init ["http://0.0.0.0:2010",""]
      2025-03-11 08:50:08.275 - error: hm-rpc.0 (37178) Cannot call init: [http://0.0.0.0:2010, ""] Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:50:08.321 - info: hm-rpc.0 (37178) terminating
      2025-03-11 08:50:08.323 - info: hm-rpc.0 (37178) Terminated (NO_ERROR): Without reason
      2025-03-11 08:50:08.860 - info: host.io01 instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
      2025-03-11 08:50:08.861 - info: host.io01 Restart adapter system.adapter.hm-rpc.0 because enabled
      2025-03-11 08:50:39.115 - info: host.io01 instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 37193
      2025-03-11 08:50:40.141 - info: hm-rpc.0 (37193) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:50:40.247 - info: hm-rpc.0 (37193) xmlrpc server is trying to listen on 0.0.0.0:2010
      2025-03-11 08:50:40.247 - info: hm-rpc.0 (37193) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010","io01:hm-rpc.0:96b2331a012d188e69fca7ecc089c707"]
      2025-03-11 08:50:40.261 - error: hm-rpc.0 (37193) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:51:10.267 - error: hm-rpc.0 (37193) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:51:10.270 - info: hm-rpc.0 (37193) xmlrpc -> 192.168.179.25:2010/ init ["http://0.0.0.0:2010",""]
      2025-03-11 08:51:10.280 - error: hm-rpc.0 (37193) Cannot call init: [http://0.0.0.0:2010, ""] Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:51:10.325 - info: hm-rpc.0 (37193) terminating
      2025-03-11 08:51:10.327 - info: hm-rpc.0 (37193) Terminated (NO_ERROR): Without reason
      2025-03-11 08:51:10.880 - info: host.io01 instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
      2025-03-11 08:51:10.880 - info: host.io01 Restart adapter system.adapter.hm-rpc.0 because enabled
      2025-03-11 08:51:41.165 - info: host.io01 instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 37208
      2025-03-11 08:51:42.132 - info: hm-rpc.0 (37208) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:51:42.280 - info: hm-rpc.0 (37208) xmlrpc server is trying to listen on 0.0.0.0:2010
      2025-03-11 08:51:42.280 - info: hm-rpc.0 (37208) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010","io01:hm-rpc.0:93c3293cc6cdf616f9eb001f39dc0451"]
      2025-03-11 08:51:42.316 - error: hm-rpc.0 (37208) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      2025-03-11 08:52:05.083 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.101 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.102 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.103 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.104 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.104 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.105 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.106 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.106 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.107 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.108 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.109 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.110 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.110 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.111 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.112 - error: hm-rpc.2 (31577) Init not possible, going to stop: socket hang up
      2025-03-11 08:52:05.113 - error: hm-rpc.2 (31577) Ping error [io01:hm-rpc.2:c8a70847f379697b438faff33c40b25e]: socket hang up
      2025-03-11 08:52:05.113 - info: hm-rpc.2 (31577) Disconnected
      2025-03-11 08:52:12.315 - error: hm-rpc.0 (37208) Init not possible, going to stop: Invalid XML-RPC message
      2025-03-11 08:52:12.319 - info: hm-rpc.0 (37208) xmlrpc -> 192.168.179.25:2010/ init ["http://0.0.0.0:2010",""]
      2025-03-11 08:52:12.339 - error: hm-rpc.0 (37208) Cannot call init: [http://0.0.0.0:2010, ""] Invalid XML-RPC message
      2025-03-11 08:52:12.384 - info: hm-rpc.0 (37208) terminating
      2025-03-11 08:52:12.385 - info: hm-rpc.0 (37208) Terminated (NO_ERROR): Without reason
      2025-03-11 08:52:12.917 - info: host.io01 instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
      2025-03-11 08:52:12.917 - info: host.io01 Restart adapter system.adapter.hm-rpc.0 because enabled
      2025-03-11 08:52:14.851 - error: hm-rpc.2 (31577) Init not possible, going to stop: Invalid XML-RPC message
      2025-03-11 08:52:33.386 - info: admin.0 (11526) failed connection to socket.io from ::ffff:10.0.0.1: Passport was not initialized
      2025-03-11 08:52:35.098 - info: hm-rpc.2 (31577) xmlrpc -> 192.168.179.25:9292/groups/ init ["http://0.0.0.0:9292",""]
      2025-03-11 08:52:36.100 - info: hm-rpc.2 (31577) terminating
      2025-03-11 08:52:36.101 - info: hm-rpc.2 (31577) Terminated (NO_ERROR): Without reason
      2025-03-11 08:52:36.635 - info: host.io01 instance system.adapter.hm-rpc.2 terminated with code 0 (NO_ERROR)
      2025-03-11 08:52:36.636 - info: host.io01 Restart adapter system.adapter.hm-rpc.2 because enabled
      2025-03-11 08:52:43.208 - info: host.io01 instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 37223
      2025-03-11 08:52:44.199 - info: hm-rpc.0 (37223) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:52:44.366 - info: hm-rpc.0 (37223) xmlrpc server is trying to listen on 0.0.0.0:2010
      2025-03-11 08:52:44.366 - info: hm-rpc.0 (37223) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010","io01:hm-rpc.0:dbe6d80860508f8a5cc17beae5081691"]
      2025-03-11 08:52:45.394 - error: hm-rpc.0 (37223) Init not possible, going to stop: connect ECONNREFUSED 192.168.179.25:2010
      2025-03-11 08:52:48.584 - info: admin.0 (11526) ==> Connected system.user.admin from ::ffff:10.0.0.1
      2025-03-11 08:52:55.287 - warn: hm-rega.0 (18280) Script "!# pollingInv.fn 0.2 !# !# Dieses Script gibt die Systemvariablen (inklusive uns" ignored, because still pending.
      2025-03-11 08:52:55.328 - warn: hm-rega.0 (18280) Script "!# programs.fn 1.3 !# Dieses Script gibt eine Liste der Programme als JSON Strin" ignored, because still pending.
      2025-03-11 08:52:56.784 - error: hm-rega.0 (18280) post request error: connect ECONNREFUSED 192.168.179.25:8181
      2025-03-11 08:52:56.785 - error: hm-rega.0 (18280) CCU 192.168.179.25 unreachable
      2025-03-11 08:53:06.946 - info: host.io01 instance system.adapter.hm-rpc.2 in version "2.0.2" started with pid 37252
      2025-03-11 08:53:07.949 - info: hm-rpc.2 (37252) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:53:08.069 - info: hm-rpc.2 (37252) xmlrpc server is trying to listen on 0.0.0.0:9292
      2025-03-11 08:53:08.069 - info: hm-rpc.2 (37252) xmlrpc client is trying to connect to 192.168.179.25:9292/groups/ with ["http://0.0.0.0:9292","io01:hm-rpc.2:14337105c4d16a6789bc9598ee994826"]
      2025-03-11 08:53:08.114 - error: hm-rpc.2 (37252) Init not possible, going to stop: Invalid XML-RPC message
      2025-03-11 08:53:08.941 - error: hm-rpc.3 (31592) Ping error [io01:hm-rpc.3:397a71e1d3583479f03b9a9b9aa696e5]: Invalid XML-RPC message
      2025-03-11 08:53:08.953 - info: hm-rpc.3 (31592) Disconnected
      2025-03-11 08:53:14.414 - error: hm-rpc.0 (37223) Init not possible, going to stop: Invalid XML-RPC message
      2025-03-11 08:53:15.397 - info: hm-rpc.0 (37223) xmlrpc -> 192.168.179.25:2010/ init ["http://0.0.0.0:2010",""]
      2025-03-11 08:53:15.422 - error: hm-rpc.0 (37223) Cannot call init: [http://0.0.0.0:2010, ""] Invalid XML-RPC message
      2025-03-11 08:53:15.469 - info: hm-rpc.0 (37223) terminating
      2025-03-11 08:53:15.469 - info: hm-rpc.0 (37223) Terminated (NO_ERROR): Without reason
      2025-03-11 08:53:16.013 - info: host.io01 instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
      2025-03-11 08:53:16.014 - info: host.io01 Restart adapter system.adapter.hm-rpc.0 because enabled
      2025-03-11 08:53:26.832 - error: hm-rega.0 (18280) ReGaHSS 192.168.179.25 down
      2025-03-11 08:53:30.899 - info: hm-rpc.1 (32028) binrpc -> listDevices 45
      2025-03-11 08:53:30.931 - info: hm-rpc.1 (32028) new CUxD devices/channels after filter: 0
      2025-03-11 08:53:38.106 - error: hm-rpc.2 (37252) Init not possible, going to stop: Invalid XML-RPC message
      2025-03-11 08:53:38.116 - info: hm-rpc.2 (37252) xmlrpc -> 192.168.179.25:9292/groups/ init ["http://0.0.0.0:9292",""]
      2025-03-11 08:53:38.145 - error: hm-rpc.2 (37252) Cannot call init: [http://0.0.0.0:9292, ""] Invalid XML-RPC message
      2025-03-11 08:53:38.193 - info: hm-rpc.2 (37252) terminating
      2025-03-11 08:53:38.195 - info: hm-rpc.2 (37252) Terminated (NO_ERROR): Without reason
      2025-03-11 08:53:38.745 - info: host.io01 instance system.adapter.hm-rpc.2 terminated with code 0 (NO_ERROR)
      2025-03-11 08:53:38.746 - info: host.io01 Restart adapter system.adapter.hm-rpc.2 because enabled
      2025-03-11 08:53:38.985 - error: hm-rpc.3 (31592) Init not possible, going to stop: Invalid XML-RPC message
      2025-03-11 08:53:46.341 - info: host.io01 instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 37267
      2025-03-11 08:53:47.324 - info: hm-rpc.0 (37267) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:53:47.440 - info: hm-rpc.0 (37267) xmlrpc server is trying to listen on 0.0.0.0:2010
      2025-03-11 08:53:47.440 - info: hm-rpc.0 (37267) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010","io01:hm-rpc.0:79230725caf245c9f18583e1a7986d62"]
      2025-03-11 08:53:47.481 - error: hm-rpc.0 (37267) Init not possible, going to stop: Invalid XML-RPC message
      2025-03-11 08:53:56.866 - error: hm-rega.0 (18280) ReGaHSS 192.168.179.25 down
      2025-03-11 08:54:08.988 - info: hm-rpc.3 (31592) xmlrpc -> 192.168.179.25:2001/ init ["http://192.168.179.18:2001",""]
      2025-03-11 08:54:09.029 - info: host.io01 instance system.adapter.hm-rpc.2 in version "2.0.2" started with pid 37283
      2025-03-11 08:54:09.348 - info: hm-rpc.3 (31592) xmlrpc <- system.listMethods ["io01:hm-rpc.3:397a71e1d3583479f03b9a9b9aa696e5"]
      2025-03-11 08:54:09.356 - info: hm-rpc.3 (31592) xmlrpc <- listDevices ["io01:hm-rpc.3:397a71e1d3583479f03b9a9b9aa696e5"]
      2025-03-11 08:54:09.381 - info: hm-rpc.3 (31592) xmlrpc -> 71 devices
      2025-03-11 08:54:09.420 - info: hm-rpc.3 (31592) Connected
      2025-03-11 08:54:09.420 - warn: hm-rpc.3 (31592) setInterval called, but adapter is shutting down
      2025-03-11 08:54:09.427 - info: hm-rpc.3 (31592) Disconnected
      2025-03-11 08:54:09.432 - info: hm-rpc.3 (31592) terminating
      2025-03-11 08:54:09.433 - info: hm-rpc.3 (31592) Terminated (NO_ERROR): Without reason
      2025-03-11 08:54:09.972 - info: host.io01 instance system.adapter.hm-rpc.3 terminated with code 0 (NO_ERROR)
      2025-03-11 08:54:09.972 - info: host.io01 Restart adapter system.adapter.hm-rpc.3 because enabled
      2025-03-11 08:54:10.040 - info: hm-rpc.2 (37283) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:54:10.139 - info: hm-rpc.2 (37283) xmlrpc server is trying to listen on 0.0.0.0:9292
      2025-03-11 08:54:10.139 - info: hm-rpc.2 (37283) xmlrpc client is trying to connect to 192.168.179.25:9292/groups/ with ["http://0.0.0.0:9292","io01:hm-rpc.2:2884011caa62e7c1a61b4aca14b8a1b3"]
      2025-03-11 08:54:17.483 - info: hm-rpc.0 (37267) xmlrpc -> 192.168.179.25:2010/ init ["http://0.0.0.0:2010",""]
      2025-03-11 08:54:18.488 - info: hm-rpc.0 (37267) terminating
      2025-03-11 08:54:18.490 - info: hm-rpc.0 (37267) Terminated (NO_ERROR): Without reason
      2025-03-11 08:54:19.031 - info: host.io01 instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
      2025-03-11 08:54:19.031 - info: host.io01 Restart adapter system.adapter.hm-rpc.0 because enabled
      2025-03-11 08:54:26.899 - info: hm-rega.0 (18280) ReGaHSS 192.168.179.25 up
      2025-03-11 08:54:26.915 - info: hm-rega.0 (18280) time difference local-ccu 0s
      2025-03-11 08:54:27.431 - info: hm-rega.0 (18280) request state values
      2025-03-11 08:54:27.542 - info: hm-rega.0 (18280) Updated all datapoints
      2025-03-11 08:54:27.642 - info: hm-rega.0 (18280) added/updated 1 objects
      2025-03-11 08:54:27.657 - info: hm-rega.0 (18280) got 134 variables
      2025-03-11 08:54:27.885 - info: hm-rega.0 (18280) added/updated 134 variables
      2025-03-11 08:54:27.886 - info: hm-rega.0 (18280) deleted 0 variables
      2025-03-11 08:54:27.892 - info: hm-rega.0 (18280) got 96 programs
      2025-03-11 08:54:27.912 - info: hm-rega.0 (18280) added/updated 95 programs
      2025-03-11 08:54:27.974 - info: hm-rega.0 (18280) deleted 1 programs
      2025-03-11 08:54:27.995 - info: hm-rega.0 (18280) update rooms to enum.rooms
      2025-03-11 08:54:28.027 - info: hm-rega.0 (18280) update functions to enum.functions
      2025-03-11 08:54:28.040 - info: hm-rega.0 (18280) update favorites to enum.favorites
      2025-03-11 08:54:32.065 - info: hm-rpc.2 (37283) Connected
      2025-03-11 08:54:40.240 - info: host.io01 instance system.adapter.hm-rpc.3 in version "2.0.2" started with pid 37298
      2025-03-11 08:54:41.277 - info: hm-rpc.3 (37298) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:54:41.431 - info: hm-rpc.3 (37298) xmlrpc server is trying to listen on 192.168.179.18:2001
      2025-03-11 08:54:41.431 - info: hm-rpc.3 (37298) xmlrpc client is trying to connect to 192.168.179.25:2001/ with ["http://192.168.179.18:2001","io01:hm-rpc.3:f7f5141fce086a970aa44c1dae75dce3"]
      2025-03-11 08:54:41.447 - info: hm-rpc.3 (37298) xmlrpc <- system.listMethods ["io01:hm-rpc.3:f7f5141fce086a970aa44c1dae75dce3"]
      2025-03-11 08:54:41.453 - info: hm-rpc.3 (37298) xmlrpc <- listDevices ["io01:hm-rpc.3:f7f5141fce086a970aa44c1dae75dce3"]
      2025-03-11 08:54:41.468 - info: hm-rpc.3 (37298) xmlrpc -> 71 devices
      2025-03-11 08:54:41.494 - info: hm-rpc.3 (37298) Connected
      2025-03-11 08:54:49.222 - info: host.io01 instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 37328
      2025-03-11 08:54:50.220 - info: hm-rpc.0 (37328) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.3, js-controller: 7.0.6
      2025-03-11 08:54:50.368 - info: hm-rpc.0 (37328) xmlrpc server is trying to listen on 0.0.0.0:2010
      2025-03-11 08:54:50.369 - info: hm-rpc.0 (37328) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010","io01:hm-rpc.0:2820f225f076966c3b2a6ba47db415be"]
      2025-03-11 08:54:52.782 - info: hm-rpc.0 (37328) Connected
      2025-03-11 08:56:05.161 - info: javascript.0 (11525) script.js.netatmo.Push2CCU: netatmoPush started
      
      Homoran Codierknecht 3 Replies Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators @blackbasket last edited by Homoran

        @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

        ich hoffe, ich mache jetzt nicht allzu viel falsch bei meinem ersten Post

        erst mal Willkommen!
        Dann sehn wir mal, ob wir noch Haare in der Suppe finden können 😉

        @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

        die CCU praktisch die Arbeit einstellt.

        was lässt dich glauben, dass das ein Bug von ioBroker ist?
        irgendwelche Hinweise?

        @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                                2025-03-11 08:49:06.267 - error: hm-rpc.0 (31608) Cannot call init: [http://0.0.0.0:2010, ""] Unknown XML-RPC tag 'TITLE'                                                                    
        

        das sieht eher nach Problemen der Firewalleinstellungen auf der RM aus, müsste dann aber immer kommen.

        wobei 0.0.0.0 nicht die Adresse von iob oder hm sein kann

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

          @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                                  2025-03-11 08:51:42.280 - info: hm-rpc.0 (37208) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010","io01:hm-rpc.0:93c3293cc6cdf616f9eb001f39dc0451"]                                                                    
          

          bitte Einstellungen der hm-rpc Adapter zeigen

          1 Reply Last reply Reply Quote 0
          • Codierknecht
            Codierknecht Developer Most Active @blackbasket last edited by Codierknecht

            @blackbasket
            Insbesondere bei einer Machine mit nur 4GB RAM solltest Du Dir überlegen, ob da tatsächlich ein Desktop laufen muss.

            System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix'
            
            1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active last edited by

              @homoran

              War da nicht mal irgendwas mit der CPU?

              model name: Intel(R) Xeon(R) Silver 4109T CPU @ 2.00GHz

              Ich meine mich dunkel erinnern zu können, das mit den Xeon-Prozessoren es irgendwelche Probleme gab.

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

                @thomas-braun sagte in CCU (RasperryMatic) high cpu usage:

                das mit den Xeon-Prozessoren es irgendwelche Probleme gab.

                ja, da war was!
                muss ich mal suchen, hab da aber was mit Proxmox im Hinterkopf

                EDIT:
                Hab das hier gefunden
                https://forum.iobroker.net/post/430965

                B 1 Reply Last reply Reply Quote 0
                • B
                  blackbasket @Homoran last edited by

                  erst einmal danke für eure ganzen Antworten...

                  @Homoran : da ich die Probleme vor iobroker jahrelang nicht hatte, schließe ich darauf, dass es vom iobroker kommt

                  @Codierknecht : danke für den Hinweis... eigentlich war ich der Meinung, ich hätte Debian ohne Desktop installiert... ich sehe auch keine GUI...

                  @Thomas-Braun / @Homoran : danke, also kommt das Problem daher und wenn ich die VM von Hyper-V auf irgendwas anderes migriere, ist es weg? dann müsste ja auch ein regelmäßiger reboot der iobrokers helfen, oder? (da ich das bisher nur für netatmo verwende, täte der nächtliche reboot davon nicht weh - im Gegensatz zur CCU)

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

                    @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                    also kommt das Problem daher und wenn ich die VM von Hyper-V auf irgendwas anderes migriere, ist es weg?

                    Das kann und will ich nicht bestätigen.

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      blackbasket @Thomas Braun last edited by

                      @thomas-braun said in CCU (RasperryMatic) high cpu usage:

                      Das kann und will ich nicht bestätigen.

                      ok 😉

                      danke auf jeden Fall erst einmal... ich teste das mal mit dem reboot... ist zwar nicht schön, aber wenn's hilft, tut es erst einmal nicht weh... wenn ich mir iobroker nutze, kann ich immer noch andere HW dafür beschaffen... der Server ist halt ohnehin da...

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

                        @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                        schließe ich darauf, dass es vom iobroker kommt

                        und was ist mit den angefragten Informationen?

                        B 1 Reply Last reply Reply Quote 0
                        • B
                          blackbasket @Homoran last edited by

                          @homoran said in CCU (RasperryMatic) high cpu usage:

                          @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                          schließe ich darauf, dass es vom iobroker kommt

                          und was ist mit den angefragten Informationen?

                          Entschuldige bitte! es klang für mich so, als wenn das Problem isoliert wäre...

                          die Adapter-Adresse habe ich erst nach meinem initialen Post verändert... da stand vorher 0.0.0.0 drin...

                          285aac0c-cd34-4d9c-a3b4-d0c84309a8c8-image.png
                          b6a2f25f-420b-454e-b99e-28d70a474d26-image.png

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

                            @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                            da stand vorher 0.0.0.0 drin...

                            das hab ich befürchtet
                            dann kann das ja auch nicht klappen!
                            wie soll die RM die Daten an 0.0.0.0 schicken?

                            EDIT:
                            Was ist

                                     Chassis: vm 
                            
                              Virtualization: microsoft
                            
                            Operating System: Debian GNU/Linux 12 (bookworm)
                            
                            

                            bei einer VM sollten die Einstellungen jetzt passen, wenn dein System allerdings routet müsst noch die Adresse des Hosts als Callback Adresse rein

                            B 2 Replies Last reply Reply Quote 0
                            • B
                              blackbasket @Homoran last edited by

                              @homoran said in CCU (RasperryMatic) high cpu usage:

                              @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                              da stand vorher 0.0.0.0 drin...

                              das hab ich befürchtet
                              dann kann das ja auch nicht klappen!
                              wie soll die RM die Daten an 0.0.0.0 schicken?

                              nun ja, 6 Tage am Stück funktioniert es ja... daher war das erst ein nachträglicher Test mit der Änderung...

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

                                @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                                , 6 Tage am Stück funktioniert es ja..

                                kann es eigentlich nicht

                                hier
                                @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                                                        2025-03-11 08:49:38.243 - info: hm-rpc.0 (37178) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010","io01:hm-rpc.0:caa4076c9e6a1de6b37c5ab85e3d75a3"]                                                                    
                                

                                teilt iobroker der CCU mit an welche IP Adresse die abbonierten Werte geschickt werden sollen.
                                0.0.0.0 ist da nicht hilfreich

                                Adapter Addresse

                                Im Pulldown-Menü wird die IP des Hosts ausgewählt, auf dem der Adapter installiert ist. Die Auswahl von "0.0.0.0. auf alle IPs hören" und "127.0.0.1" ist Spezialfällen vorbehalten.

                                https://www.iobroker.net/#de/adapters/adapterref/iobroker.hm-rpc/README.md?
                                Konfiguratio -> Adapteradresse

                                das müsste auch im syslog der CCU zu finden sein

                                B 1 Reply Last reply Reply Quote 0
                                • B
                                  blackbasket @Homoran last edited by

                                  @homoran ich verstehe, was du meinst... in der Realität sind die Werte jedoch angekommen... ist aber auch egal, die Diskussion ist müßig 😉

                                  ich habe heute Vormittag geändert und in 6 Tagen werden wir wohl wissen, ob es abgeholfen hat...

                                  oder, ob sich PRTG mit CPU-High-Meldungen meldet...
                                  5ab684ea-b5ad-4ac2-b20f-68c33785253c-image.png
                                  (ich rede von 6 Tagen, weil der kleine Peak (Mittwoch) von den Neustarts aufgrund der Updates auf der CCU kommt)

                                  1 Reply Last reply Reply Quote 0
                                  • B
                                    blackbasket @Homoran last edited by

                                    @homoran said in CCU (RasperryMatic) high cpu usage:

                                    EDIT:
                                    Was ist
                                    Chassis: vm

                                    Virtualization: microsoft

                                    Operating System: Debian GNU/Linux 12 (bookworm)

                                    bei einer VM sollten die Einstellungen jetzt passen, wenn dein System allerdings routet müsst noch die Adresse des Hosts als Callback Adresse rein

                                    Was genau meinst du?

                                    Es handelt sich um eine Hyper-V-VM, auf der Debian und dann iobroker mittels Script installiert wurde...

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

                                      @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                                      Was genau meinst du?

                                      ich weiß nicht was

                                      @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                                      eine Hyper-V-VM

                                      ist und wie sie funktioniert

                                      was im syslog der CCU stand, sagst du mir nicht?

                                      B 1 Reply Last reply Reply Quote 0
                                      • B
                                        blackbasket @Homoran last edited by blackbasket

                                        eine Hyper-V VM ist eine virtuelle Maschine auf Basis der Microsoft-Virtualisierungsplattform Hyper-V... also das MS-Produkt, welches VMware, Proxmox etc entspricht...

                                        @homoran said in CCU (RasperryMatic) high cpu usage:

                                        was im syslog der CCU stand, sagst du mir nicht?

                                        falls ich die Frage überlesen habe, tut es mir leid... bis gerade bin ich gar nicht auf die Idee gekommen, ins CCU-Log zu schauen... jetzt geht's natürlich nur noch 3h zurück...

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

                                          @blackbasket sagte in CCU (RasperryMatic) high cpu usage:

                                          jetzt geht's natürlich nur noch 3h zurück...

                                          interessant wäre das log nach restart der hm-rpc Instanz(en)
                                          hauptsächlich mit den alten Einstellungen.

                                          jetzt warten wir es erst mal ab.

                                          B 1 Reply Last reply Reply Quote 0
                                          • B
                                            blackbasket @Homoran last edited by

                                            Hallo zusammen,

                                            die RM und iobroker laufen nun seit über 7 Tagen stabil. Der Fehler

                                            info: hm-rpc.0 (37178) xmlrpc client is trying to connect to 192.168.179.25:2010/ with ["http://0.0.0.0:2010",

                                            ist im Log weiterhin nicht sichtbar. Aber er ist ja auch nur erschienen, wenn die CPU hoch war 😉

                                            Ich danke euch bis hier hin 🙂

                                            LG

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            906
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            4
                                            20
                                            651
                                            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