[gelöst]HM-RPC Error
-
Hallo,
nach ca 2 Jahren problemlosen Lauf des ioBrokers will ich mich wieder mit ihm befassen.
Wie das so ist - vieles vergessen - manches verlernt.
Aber das wird wieder. An einige Dinge kann man sich noch dunkel erinnern.Also, den Broker geöffnet und erst mal die Updateorgie durchlaufen.
Nun habe ich bei HM-RPC.1 einen Error:
Könnt ihr mir auf die Sprünge helfen was er mir damit sagen will?
Die Steuerung der HK-Ventile funktioniert.
Habe mal einen Neustart des Adapters im Modus Debug gemacht.hm-rpc.1 2024-11-13 16:46:30.731 debug start ping interval hm-rpc.1 2024-11-13 16:46:30.731 debug clear connecting interval hm-rpc.1 2024-11-13 16:46:30.731 info Connected hm-rpc.1 2024-11-13 16:46:30.730 error Cannot call listDevices: socket hang up hm-rpc.1 2024-11-13 16:46:30.717 debug start connecting interval hm-rpc.1 2024-11-13 16:46:30.712 debug xmlrpc -> 192.168.6.50:8701/ init ["http://192.168.6.50:12001","VM-ioBroker:hm-rpc.1:59c4bb6bd10d174f8e96eab85d6f91ba"] hm-rpc.1 2024-11-13 16:46:30.711 debug Connect... hm-rpc.1 2024-11-13 16:46:30.711 info xmlrpc client is trying to connect to 192.168.6.50:8701/ with ["http://192.168.6.50:12001","VM-ioBroker:hm-rpc.1:59c4bb6bd10d174f8e96eab85d6f91ba"] hm-rpc.1 2024-11-13 16:46:30.710 info xmlrpc server is trying to listen on 192.168.6.51:12001 hm-rpc.1 2024-11-13 16:46:30.347 info starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.0, js-controller: 6.0.11 hm-rpc.1 2024-11-13 16:46:29.678 debug Plugin sentry Initialize Plugin (enabled=true) hm-rpc.1 2024-11-13 16:46:29.591 debug States connected to redis: 127.0.0.1:9000 hm-rpc.1 2024-11-13 16:46:29.433 debug States create User PubSub Client hm-rpc.1 2024-11-13 16:46:29.432 debug States create System PubSub Client hm-rpc.1 2024-11-13 16:46:29.273 debug Redis States: Use Redis connection: 127.0.0.1:9000 hm-rpc.1 2024-11-13 16:46:29.145 debug Objects connected to redis: 127.0.0.1:9001 hm-rpc.1 2024-11-13 16:46:29.136 debug Objects client initialize lua scripts hm-rpc.1 2024-11-13 16:46:28.902 debug Objects create User PubSub Client hm-rpc.1 2024-11-13 16:46:28.901 debug Objects create System PubSub Client hm-rpc.1 2024-11-13 16:46:28.856 debug Objects client ready ... initialize now hm-rpc.1 2024-11-13 16:46:28.756 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 hm-rpc.1 2024-11-13 16:46:24.080 debug Plugin sentry Initialize Plugin (enabled=true) hm-rpc.1 2024-11-13 16:46:23.977 debug States connected to redis: 127.0.0.1:9000 hm-rpc.1 2024-11-13 16:46:23.838 debug States create User PubSub Client hm-rpc.1 2024-11-13 16:46:23.837 debug States create System PubSub Client hm-rpc.1 2024-11-13 16:46:23.774 debug Redis States: Use Redis connection: 127.0.0.1:9000 hm-rpc.1 2024-11-13 16:46:23.647 debug Objects connected to redis: 127.0.0.1:9001 hm-rpc.1 2024-11-13 16:46:23.573 debug Objects client initialize lua scripts hm-rpc.1 2024-11-13 16:46:23.102 debug Objects create User PubSub Client hm-rpc.1 2024-11-13 16:46:23.101 debug Objects create System PubSub Client hm-rpc.1 2024-11-13 16:46:23.095 debug Objects client ready ... initialize now hm-rpc.1 2024-11-13 16:46:23.007 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 hm-rpc.1 2024-11-13 16:46:17.701 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason hm-rpc.1 2024-11-13 16:46:17.700 info terminating hm-rpc.1 2024-11-13 16:46:17.699 info Disconnected hm-rpc.1 2024-11-13 16:46:17.692 info xmlrpc -> 192.168.6.50:8701/ init ["http://192.168.6.50:12001",""] hm-rpc.1 2024-11-13 16:46:17.691 info Got terminate signal TERMINATE_YOURSELFGruß
Bernd -
@berlon wenn der wirklich zwei Jahre vernachlässigt wurde … was kommt dann bei
iob diag -
Dein Wunsch ist mir Befehl
======================= SUMMARY ======================= v.2024-10-19 Static hostname: VM-ioBroker Icon name: computer-vm Chassis: vm Virtualization: kvm Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.10.0-33-amd64 Architecture: x86-64 Installation: kvm Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 10 Pending iob updates: 5 Nodejs-Installation: /usr/bin/nodejs v20.18.0 /usr/bin/node v20.18.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs 20.18.0 and npm 10.8.2 nodeJS installation is correct MEMORY: total used free shared buff/cache available Mem: 3.9G 2.1G 1.2G 0.0K 663M 1.6G Swap: 974M 0B 974M Total: 4.9G 2.1G 2.2G Active iob-Instances: 23 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.1.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : VM-ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : VM-ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 70116 States: 44160 Size of iob-Database: -
@berlon sagte in HM-RPC Error:
Dein Wunsch ist mir Befehl
das ist leider nur die Summary
und selbst die ist unvollständig -
@homoran
ich gehorche========== Start marking the full check here =========== ```bash Script v.2024-10-19 *** BASE SYSTEM *** Static hostname: VM-ioBroker Icon name: computer-vm Chassis: vm Virtualization: kvm Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.10.0-33-amd64 Architecture: x86-64 OS is similar to: model name : Common KVM processor Docker : false Virtualization : kvm Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 19:53:45 up 44 min, 1 user, load average: 0.79, 0.49, 0.55 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian 'bullseye' is the current oldstable version. Please upgrade to the latest stable release 'bookworm' in due time! *** TIME AND TIMEZONES *** Local time: Wed 2024-11-13 19:53:45 CET Universal time: Wed 2024-11-13 18:53:45 UTC RTC time: Wed 2024-11-13 18:53:46 Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': bernd HOME=/home/bernd GROUPS=bernd root cdrom floppy sudo audio dip video plugdev 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 *** MEMORY *** total used free shared buff/cache available Mem: 3.9G 2.0G 1.2G 0.0K 675M 1.7G Swap: 974M 0B 974M Total: 4.9G 2.0G 2.2G Active iob-Instances: 24 3919 M total memory 2002 M used memory 274 M active memory 2231 M inactive memory 1241 M free memory 69 M buffer memory 605 M swap cache 974 M total swap 0 M used swap 974 M free swap *** top - Table Of Processes *** top - 19:53:45 up 44 min, 1 user, load average: 0.79, 0.49, 0.55 Tasks: 108 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.6 us, 3.1 sy, 0.0 ni, 81.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3919.4 total, 1241.7 free, 2002.3 used, 675.4 buff/cache MiB Swap: 975.0 total, 975.0 free, 0.0 used. 1686.1 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.9G 0 1.9G 0% /dev tmpfs tmpfs 392M 460K 392M 1% /run /dev/sda1 ext4 31G 8.1G 21G 28% / tmpfs tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 392M 0 392M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Nov 13 19:09:39 2024] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [Wed Nov 13 19:09:39 2024] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda1 ext4 rw,relatime,errors=remount-ro Files in neuralgic directories: /var: 1.1G /var/ 501M /var/log 481M /var/log/journal/7dc34dc5f4aa4a12b9e06132f71ac08b 481M /var/log/journal 440M /var/cache 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 48.0M in the file system. /opt/iobroker/backups: 145M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.3G /opt/iobroker/iobroker-data/ 1.1G /opt/iobroker/iobroker-data/files 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static 558M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 52M /opt/iobroker/iobroker-data/objects.jsonl 41M /opt/iobroker/iobroker-data/states.jsonl 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map 26M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map 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' *** NodeJS-Installation *** /usr/bin/nodejs v20.18.0 /usr/bin/node v20.18.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 nodejs: Installed: 20.18.0-1nodesource1 Candidate: 20.18.0-1nodesource1 Version table: *** 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 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 12.22.12~dfsg-1~deb11u5 500 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/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: VM-ioBroker VM-ioBroker (version: 6.0.11, hostname: VM-ioBroker , alive, uptime: 2638) Core adapters versions js-controller: 6.0.11 admin: 7.1.5 javascript: 8.8.3 nodejs modules from github: 1 | +-- syno@3.0.0 (git+https://git@github.com/MeisterTR/syno.git#0104a973d33fe332aa6b1ab5be7fe8c57d3c68b0) Adapter State + system.adapter.admin.0 : admin : VM-ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : VM-ioBroker - disabled + system.adapter.backitup.0 : backitup : VM-ioBroker - enabled + system.adapter.daikin-cloud.0 : daikin-cloud : VM-ioBroker - enabled + system.adapter.daswetter.0 : daswetter : VM-ioBroker - enabled + system.adapter.discovery.0 : discovery : VM-ioBroker - enabled system.adapter.dwd.0 : dwd : VM-ioBroker - enabled + system.adapter.echarts.0 : echarts : VM-ioBroker - enabled system.adapter.feiertage.0 : feiertage : VM-ioBroker - enabled + system.adapter.fullcalendar.0 : fullcalendar : VM-ioBroker - enabled + system.adapter.heatingcontrol.0 : heatingcontrol : VM-ioBroker - enabled + system.adapter.history.0 : history : VM-ioBroker - enabled + system.adapter.hm-rega.0 : hm-rega : VM-ioBroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : VM-ioBroker - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : VM-ioBroker - enabled, port: 12001 + system.adapter.hm-rpc.2 : hm-rpc : VM-ioBroker - enabled, port: 12010 system.adapter.ical.0 : ical : VM-ioBroker - enabled system.adapter.icons-mfd-png.0 : icons-mfd-png : VM-ioBroker - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : VM-ioBroker - disabled + system.adapter.influxdb.0 : influxdb : VM-ioBroker - enabled, port: 8086 system.adapter.info.0 : info : VM-ioBroker - enabled + system.adapter.jarvis.0 : jarvis : VM-ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.javascript.0 : javascript : VM-ioBroker - enabled system.adapter.openweathermap.0 : openweathermap : VM-ioBroker - enabled + system.adapter.ping.0 : ping : VM-ioBroker - enabled + system.adapter.proxmox.0 : proxmox : VM-ioBroker - enabled, port: 8006 + system.adapter.shelly.0 : shelly : VM-ioBroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : VM-ioBroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.synology.0 : synology : VM-ioBroker - enabled, port: 5001 + system.adapter.tr-064.0 : tr-064 : VM-ioBroker - enabled system.adapter.vis-history.0 : vis-history : VM-ioBroker - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : VM-ioBroker - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : VM-ioBroker - disabled system.adapter.vis-justgage.0 : vis-justgage : VM-ioBroker - disabled system.adapter.vis-metro.0 : vis-metro : VM-ioBroker - disabled system.adapter.vis-plumb.0 : vis-plumb : VM-ioBroker - disabled system.adapter.vis-rgraph.0 : vis-rgraph : VM-ioBroker - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : VM-ioBroker - disabled system.adapter.vis.0 : vis : VM-ioBroker - enabled + system.adapter.web.0 : web : VM-ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : VM-ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : VM-ioBroker - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : VM-ioBroker - enabled, port: 12001 + system.adapter.hm-rpc.2 : hm-rpc : VM-ioBroker - enabled, port: 12010 + system.adapter.influxdb.0 : influxdb : VM-ioBroker - enabled, port: 8086 + system.adapter.jarvis.0 : jarvis : VM-ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.proxmox.0 : proxmox : VM-ioBroker - enabled, port: 8006 + system.adapter.shelly.0 : shelly : VM-ioBroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : VM-ioBroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.synology.0 : synology : VM-ioBroker - enabled, port: 5001 + system.adapter.web.0 : web : VM-ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories +---------------------------------------------------------------------------------------------- ¦ (index) ¦ name ¦ url ¦ auto upgrade ¦ +---------------------------------------------------------------------------------------------- ¦ 0 ¦ 'stable' ¦ 'http://download.iobroker.net/sources-dist.json' ¦ false ¦ ¦ 1 ¦ 'beta' ¦ 'http://download.iobroker.net/sources-dist-latest.json' ¦ false ¦ +---------------------------------------------------------------------------------------------- Active repo(s): stable Upgrade policy: none Installed ioBroker-Instances Used repository: stable Adapter "admin" : 7.1.5 , installed 7.1.5 Adapter "alias-manager": 2.0.0 , installed 1.2.6 [Updatable] Adapter "backitup" : 3.0.25 , installed 3.0.22 [Updatable] Adapter "daikin-cloud" : 0.4.11 , installed 0.4.8 [Updatable] Adapter "daswetter" : 3.1.16 , installed 3.1.16 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "echarts" : 1.9.2 , installed 1.9.2 Adapter "feiertage" : 1.2.0 , installed 1.2.0 Adapter "fullcalendar" : 2.4.5 , installed 2.4.2 [Updatable] Adapter "heatingcontrol": 2.12.10 , installed 2.12.10 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.0.0 [Updatable] Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "ical" : 1.15.0 , installed 1.15.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "jarvis" : 3.1.8 , installed 3.1.8 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 6.0.11 , installed 6.0.11 Adapter "openweathermap": 1.1.2 , installed 1.1.2 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "proxmox" : 2.3.0 , installed 2.3.0 Adapter "shelly" : 8.2.1 , installed 8.2.1 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.1.2 , installed 3.1.2 Adapter "synology" : 3.1.0 , installed 3.1.0 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.1.1 Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.2 , installed 2.6.2 Objects and States Please stand by - This may take a while Objects: 70116 States: 44130 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Pending Updates: 10 *** 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.6.51:12001 0.0.0.0:* LISTEN 1001 13162 581/io.hm-rpc.1 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 12117 373/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 12112 373/iobroker.js-con tcp 0 0 192.168.6.51:12010 0.0.0.0:* LISTEN 1001 13188 604/io.hm-rpc.2 tcp 0 0 192.168.6.51:18701 0.0.0.0:* LISTEN 1001 13435 570/io.hm-rpc.0 tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 10468 1/init tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 14325 956/io.jarvis.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 12091 435/sshd: /usr/sbin tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 13608 696/io.shelly.0 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 13274 660/io.sonoff.0 tcp6 0 0 :::111 :::* LISTEN 0 10472 1/init tcp6 0 0 :::8081 :::* LISTEN 1001 12823 451/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 13988 819/io.web.0 tcp6 0 0 :::22 :::* LISTEN 0 12093 435/sshd: /usr/sbin udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12631 367/dhclient udp 0 0 0.0.0.0:111 0.0.0.0:* 0 10469 1/init udp 0 0 192.168.6.51:5353 0.0.0.0:* 1001 13202 545/io.tr-064.0 udp6 0 0 :::111 :::* 0 10475 1/init *** Log File - Last 25 Lines *** 2024-11-13 19:53:00.761 - info: shelly.0 (696) [authEnabled] 192.168.6.82 (shellypro3em / shellypro3em-34987a45f15c / shellypro3em#34987a45f15c#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:53:05.029 - info: host.VM-ioBroker instance system.adapter.daswetter.0 in version "3.1.16" started with pid 3678 2024-11-13 19:53:06.990 - info: daswetter.0 (3678) starting. Version 3.1.16 in /opt/iobroker/node_modules/iobroker.daswetter, node: v20.18.0, js-controller: 6.0.11 2024-11-13 19:53:08.273 - info: tr-064.0 (545) forEachConfiguredDevice: in GetSpecificHostEntry 12(PC-192-168-6-52/BC:24:11:73:10:C6) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500} 2024-11-13 19:53:13.214 - info: shelly.0 (696) [authEnabled] 192.168.6.81 (shellypro3em / shellypro3em-fcb467058324 / shellypro3em#fcb467058324#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:53:16.121 - info: shelly.0 (696) [authEnabled] 192.168.6.82 (shellypro3em / shellypro3em-34987a45f15c / shellypro3em#34987a45f15c#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:53:23.222 - info: tr-064.0 (545) forEachConfiguredDevice: in GetSpecificHostEntry 12(PC-192-168-6-52/BC:24:11:73:10:C6) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500} 2024-11-13 19:53:28.369 - info: shelly.0 (696) [authEnabled] 192.168.6.81 (shellypro3em / shellypro3em-fcb467058324 / shellypro3em#fcb467058324#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:53:31.275 - info: shelly.0 (696) [authEnabled] 192.168.6.82 (shellypro3em / shellypro3em-34987a45f15c / shellypro3em#34987a45f15c#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:53:32.411 - info: daswetter.0 (3678) still wrong data structure from server received! repaired... 2024-11-13 19:53:38.400 - info: tr-064.0 (545) forEachConfiguredDevice: in GetSpecificHostEntry 12(PC-192-168-6-52/BC:24:11:73:10:C6) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500} 2024-11-13 19:53:41.906 - info: daswetter.0 (3678) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment 2024-11-13 19:53:42.416 - info: daswetter.0 (3678) cleaned everything up... 2024-11-13 19:53:42.437 - info: host.VM-ioBroker instance system.adapter.daswetter.0 having pid 3678 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-11-13 19:53:43.733 - info: shelly.0 (696) [authEnabled] 192.168.6.81 (shellypro3em / shellypro3em-fcb467058324 / shellypro3em#fcb467058324#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:53:46.430 - info: shelly.0 (696) [authEnabled] 192.168.6.82 (shellypro3em / shellypro3em-34987a45f15c / shellypro3em#34987a45f15c#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:53:53.705 - info: tr-064.0 (545) forEachConfiguredDevice: in GetSpecificHostEntry 12(PC-192-168-6-52/BC:24:11:73:10:C6) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500} 2024-11-13 19:53:53.801 - debug: hm-rpc.1 (581) [KEEPALIVE] Check if connection is alive 2024-11-13 19:53:53.802 - debug: hm-rpc.1 (581) Send PING... 2024-11-13 19:53:53.809 - debug: hm-rpc.1 (581) PING ok 2024-11-13 19:53:59.004 - info: shelly.0 (696) [authEnabled] 192.168.6.81 (shellypro3em / shellypro3em-fcb467058324 / shellypro3em#fcb467058324#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:54:01.584 - info: shelly.0 (696) [authEnabled] 192.168.6.82 (shellypro3em / shellypro3em-34987a45f15c / shellypro3em#34987a45f15c#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:54:08.810 - info: tr-064.0 (545) forEachConfiguredDevice: in GetSpecificHostEntry 12(PC-192-168-6-52/BC:24:11:73:10:C6) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500} 2024-11-13 19:54:14.188 - info: shelly.0 (696) [authEnabled] 192.168.6.81 (shellypro3em / shellypro3em-fcb467058324 / shellypro3em#fcb467058324#1): This device is not protected via restricted login (see adapter documentation for details) 2024-11-13 19:54:16.763 - info: shelly.0 (696) [authEnabled] 192.168.6.82 (shellypro3em / shellypro3em-34987a45f15c / shellypro3em#34987a45f15c#1): This device is not protected via restricted login (see adapter documentation for details) ============ Mark until here for C&P ============= iob diag has finished. Press any key for a summary ======================= SUMMARY ======================= v.2024-10-19 Static hostname: VM-ioBroker Icon name: computer-vm Chassis: vm Virtualization: kvm Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.10.0-33-amd64 Architecture: x86-64 Installation: kvm Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 10 Pending iob updates: 5 Nodejs-Installation: /usr/bin/nodejs v20.18.0 /usr/bin/node v20.18.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs 20.18.0 and npm 10.8.2 nodeJS installation is correct MEMORY: total used free shared buff/cache available Mem: 3.9G 2.0G 1.2G 0.0K 678M 1.7G Swap: 974M 0B 974M Total: 4.9G 2.0G 2.2G Active iob-Instances: 24 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.1.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : VM-ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : VM-ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 70116 States: 44130 Size of iob-Database: 52M /opt/iobroker/iobroker-data/objects.jsonl 11M /opt/iobroker/iobroker-data/objects.json.migrated 11M /opt/iobroker/iobroker-data/objects.json.bak.migrated 42M /opt/iobroker/iobroker-data/states.jsonl 2.5M /opt/iobroker/iobroker-data/states.json.migrated 2.5M /opt/iobroker/iobroker-data/states.json.bak.migrated 0 /opt/iobroker/iobroker-data/states.json.broken Debian 'bullseye' is the current oldstable version. Please upgrade to the latest stable release 'bookworm' in due time! =================== END OF SUMMARY ==================== === Mark text until here for copying === -
@berlon sagte in HM-RPC Error:
Pending OS-Updates: 10
und
@berlon sagte in HM-RPC Error:
Pending iob updates: 5
bitte noch erledigen.
und was sind das für Ports bei den hm-rpc Instanzen?
-
@homoran
Habe dem Broker Bookworm untergeschoben.Die Ports 8701 muss als Homematic Port eingegeben werden.
der Port 12001 ist der Port des Adapters
Steht mal so in der Anleitung, wobei über den Port 12001 nix drin steht -
@berlon sagte in HM-RPC Error:
Steht mal so in der Anleitung, wobei über den Port 12001 nix drin steht
hmmm
Adapter Port
Standardmäßig ist hier Port "0" für die automatische Selektion des ioBroker-Ports eingestellt und sollte nur in Ausnahmefällen verändert werden.
-
@homoran
Bei den HM-RPC´s habe ich nun überall die 0 eingetragen.
Beim HM-RPC.1 ist der Fehler nun weg, habe da ein falsch eingestelltes Protokoll gehabt.Danke für die Hilfe.
-
@berlon falsches Protokoll kann aber nicht durch ein Upgrade da rein gekommen sein.
-
@wendy2702
bestimmt damals was falsch eingestellt. Nur störte das damals den Adapter nicht. Ich hatte immer geschaut ob ein error da ist. War vor 2 Jahren nicht der Fall. Aber mit der jetzigen Version war das anders.Aber insgesamt sehr wenig Probleme beim Updaten.
Hat nun sogar Bookworm
Muss mich nun halt wieder reinfuchsen
