NEWS
EMS-ESP mit ipinside funktioniert nicht mehr?
-
@felixrhoese Niemand eine Idee? Bin für jede Hilfe dankbar!
@felixrhoese said in EMS-ESP mit ipinside funktioniert nicht mehr?:
@felixrhoese Niemand eine Idee? Bin für jede Hilfe dankbar!
Na ja - ohne Informationen gibts nur wenig Hilfe. Keine Info welcher Adapter / Version im einsatz ist. Kein Log bzw. Fehlermeldungen...
Versionen?
adapter
admin
js-controller
node
O/SHäng auch an
Output von iob diag IN DER LANGFASSUNG
Log des Adapters mit Level DEBUG -
@mcm1957
Danke für den Hinweis!Adapter: EMS-ESP 4.8.0
Admin: 7.0.23
Js-controller: 8.3.1
Node: 18.17.1
O/S: Linux auf Raspberry pi3Log des Adapters mit Level DEBUG:
2024-09-14 09:31:51.979 - info: host.iobroker-pi "system.adapter.ems-esp.0" enabled 2024-09-14 09:31:52.135 - info: host.iobroker-pi instance system.adapter.ems-esp.0 started with pid 19751 2024-09-14 09:31:56.436 - info: ems-esp.0 (19751) starting. Version 4.8.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v18.17.1, js-controller: 5.0.19 2024-09-14 09:31:56.939 - info: ems-esp.0 (19751) InfluxDB 1.x - Retention: 730 days --- Adapterversion: 4.0.2 2024-09-14 09:32:00.037 - info: javascript.0 (13044) script.js.common.10_Heizung.Temperatur_Mean24h: 0 2024-09-14 09:32:06.462 - info: host.iobroker-pi stopInstance system.adapter.ems-esp.0 (force=false, process=true) 2024-09-14 09:32:06.473 - info: ems-esp.0 (19751) Got terminate signal TERMINATE_YOURSELF 2024-09-14 09:32:06.478 - info: ems-esp.0 (19751) terminating 2024-09-14 09:32:06.481 - info: ems-esp.0 (19751) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-09-14 09:32:06.517 - info: host.iobroker-pi stopInstance system.adapter.ems-esp.0 send kill signal 2024-09-14 09:32:07.120 - info: host.iobroker-pi instance system.adapter.ems-esp.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-09-14 09:32:10.138 - info: host.iobroker-pi instance system.adapter.ems-esp.0 started with pid 19766 2024-09-14 09:32:13.802 - info: ems-esp.0 (19766) starting. Version 4.8.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v18.17.1, js-controller: 5.0.19 2024-09-14 09:32:14.187 - info: ems-esp.0 (19766) InfluxDB 1.x - Retention: 730 days --- Adapterversion: 4.0.2 2024-09-14 09:32:20.329 - info: javascript.0 (13044) script.js.common.10_Heizung.Temperature_Mean3h: NaN 2024-09-14 09:32:34.908 - error: ems-esp.0 (19766) error reading KM200 gateway (wrong ip address) - stop KM200 read: http://TK-850-JH3E-NETHinweis: Die IP Adresse bzw. der Hostname sind definitiv korrekt. In der MyBuderus App kann ich die Live Daten auch alle sehen.
Output von iob diag IN DER LANGFASSUNG
Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: iobroker-pi Icon name: computer Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.10.103-v7+ Architecture: arm Model : Raspberry Pi 3 Model B Rev 1.2 Docker : false Virtualization : none Kernel : armv7l Userland : 32 bit Systemuptime and Load: 09:43:31 up 1 day, 13:28, 1 user, load average: 1.67, 0.84, 0.52 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Sat 2024-09-14 09:43:31 CEST Universal time: Sat 2024-09-14 07:43:31 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video bluetooth gpio i2c *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 972M 729M 52M 36M 190M 187M Swap: 99M 99M 0.0K Total: 1.1G 829M 52M Active iob-Instances: 11 972 M total memory 729 M used memory 326 M active memory 537 M inactive memory 52 M free memory 28 M buffer memory 162 M swap cache 99 M total swap 99 M used swap 0 M free swap *** top - Table Of Processes *** top - 09:43:31 up 1 day, 13:28, 1 user, load average: 1.67, 0.84, 0.52 Tasks: 132 total, 1 running, 131 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.4 us, 2.8 sy, 0.0 ni, 95.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 972.8 total, 51.9 free, 729.4 used, 191.4 buff/cache MiB Swap: 100.0 total, 0.2 free, 99.8 used. 187.5 avail Mem *** FAILED SERVICES *** 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 57G 5.7G 49G 11% / devtmpfs devtmpfs 454M 0 454M 0% /dev tmpfs tmpfs 487M 0 487M 0% /dev/shm tmpfs tmpfs 487M 50M 438M 11% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 487M 0 487M 0% /sys/fs/cgroup /dev/mmcblk0p1 vfat 247M 49M 198M 20% /boot tmpfs tmpfs 98M 0 98M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Thu Sep 12 20:14:39 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 console=ttyS0,115200 console=tty1 root=PARTUUID=d677b88f-02 rootfstype=ext4 fsck.repair=yes rootwait [Thu Sep 12 20:14:42 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Thu Sep 12 20:14:42 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Thu Sep 12 20:14:44 2024] EXT4-fs (mmcblk0p2): recovery complete [Thu Sep 12 20:14:44 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Thu Sep 12 20:14:44 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Thu Sep 12 20:14:47 2024] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [Fri Sep 13 20:17:02 2024] [<802b0ee8>] (filemap_fault) from [<8042d260>] (ext4_filemap_fault+0x38/0x4c) [Fri Sep 13 20:17:02 2024] [<8042d228>] (ext4_filemap_fault) from [<802e8900>] (__do_fault+0x48/0x14c) Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/dev devtmpfs devtmpfs rw,relatime,size=464768k,nr_inodes=116192,mode=755 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | `-/dev/mqueue mqueue mqueue rw,relatime |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup tmpfs tmpfs ro,nosuid,nodev,noexec,mode=755 | | |-/sys/fs/cgroup/unified cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate | | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd | | |-/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct | | |-/sys/fs/cgroup/net_cls,net_prio cgroup cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio | | |-/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,relatime,perf_event | | |-/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpuset | | |-/sys/fs/cgroup/pids cgroup cgroup rw,nosuid,nodev,noexec,relatime,pids | | |-/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,relatime,freezer | | |-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,relatime,devices | | `-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,relatime,blkio | |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/debug debugfs debugfs rw,relatime | `-/sys/kernel/config configfs configfs rw,relatime |-/proc proc proc rw,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=33,pgrp=1,timeout=0,minproto=5,maxproto=5,direct |-/run tmpfs tmpfs rw,nosuid,nodev,mode=755 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | `-/run/user/1000 tmpfs tmpfs rw,nosuid,nodev,relatime,size=99608k,mode=700,uid=1000,gid=1000 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.7G /var/ 834M /var/lib 739M /var/lib/influxdb 703M /var/lib/influxdb/data 656M /var/lib/influxdb/data/iobroker/autogen Archived and active journals take up 48.6M in the file system. /opt/iobroker/backups: 31M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 272M /opt/iobroker/iobroker-data/ 206M /opt/iobroker/iobroker-data/files 138M /opt/iobroker/iobroker-data/files/javascript.admin 118M /opt/iobroker/iobroker-data/files/javascript.admin/static 117M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map 11M /opt/iobroker/iobroker-data/objects.jsonl 8.0M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.a9c6d34a.chunk.js.map 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/61.54b23816.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' *** NodeJS-Installation *** nodejs: N/A /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 *** nodejs is NOT correctly installed *** nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u3 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf 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: 7.0.23 javascript: 8.3.1 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 : iobroker-pi - enabled, compact disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : iobroker-pi - enabled, compact disabled + system.adapter.ems-esp.0 : ems-esp : iobroker-pi - enabled, compact disabled + system.adapter.history.0 : history : iobroker-pi - enabled, compact disabled + system.adapter.influxdb.0 : influxdb : iobroker-pi - enabled, compact disabled, port: 8086 + system.adapter.javascript.0 : javascript : iobroker-pi - enabled, compact disabled + system.adapter.mqtt.0 : mqtt : iobroker-pi - enabled, compact disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker-pi - enabled, compact disabled, port: 1885, bind: 0.0.0.0 + system.adapter.nut.0 : nut : iobroker-pi - enabled, compact disabled + system.adapter.telegram.0 : telegram : iobroker-pi - enabled, compact disabled, port: 8443, bind: 0.0.0.0 system.adapter.text2command.0 : text2command : iobroker-pi - disabled, compact disabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker-pi - enabled, compact disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : iobroker-pi - enabled, compact disabled, port: 8086 + system.adapter.mqtt.0 : mqtt : iobroker-pi - enabled, compact disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker-pi - enabled, compact disabled, port: 1885, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : iobroker-pi - enabled, compact disabled, port: 8443, bind: 0.0.0.0 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: stableIch sehe selbst gerade, dass es wohl auch ein Problem mit dem NodeJS System gibt. Ich werde versuchen das zu fixen, auch wenn ich keine Ahnung habe.
Danke für jede Hilfe!
VG
Felix -
@mcm1957
Danke für den Hinweis!Adapter: EMS-ESP 4.8.0
Admin: 7.0.23
Js-controller: 8.3.1
Node: 18.17.1
O/S: Linux auf Raspberry pi3Log des Adapters mit Level DEBUG:
2024-09-14 09:31:51.979 - info: host.iobroker-pi "system.adapter.ems-esp.0" enabled 2024-09-14 09:31:52.135 - info: host.iobroker-pi instance system.adapter.ems-esp.0 started with pid 19751 2024-09-14 09:31:56.436 - info: ems-esp.0 (19751) starting. Version 4.8.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v18.17.1, js-controller: 5.0.19 2024-09-14 09:31:56.939 - info: ems-esp.0 (19751) InfluxDB 1.x - Retention: 730 days --- Adapterversion: 4.0.2 2024-09-14 09:32:00.037 - info: javascript.0 (13044) script.js.common.10_Heizung.Temperatur_Mean24h: 0 2024-09-14 09:32:06.462 - info: host.iobroker-pi stopInstance system.adapter.ems-esp.0 (force=false, process=true) 2024-09-14 09:32:06.473 - info: ems-esp.0 (19751) Got terminate signal TERMINATE_YOURSELF 2024-09-14 09:32:06.478 - info: ems-esp.0 (19751) terminating 2024-09-14 09:32:06.481 - info: ems-esp.0 (19751) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-09-14 09:32:06.517 - info: host.iobroker-pi stopInstance system.adapter.ems-esp.0 send kill signal 2024-09-14 09:32:07.120 - info: host.iobroker-pi instance system.adapter.ems-esp.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-09-14 09:32:10.138 - info: host.iobroker-pi instance system.adapter.ems-esp.0 started with pid 19766 2024-09-14 09:32:13.802 - info: ems-esp.0 (19766) starting. Version 4.8.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v18.17.1, js-controller: 5.0.19 2024-09-14 09:32:14.187 - info: ems-esp.0 (19766) InfluxDB 1.x - Retention: 730 days --- Adapterversion: 4.0.2 2024-09-14 09:32:20.329 - info: javascript.0 (13044) script.js.common.10_Heizung.Temperature_Mean3h: NaN 2024-09-14 09:32:34.908 - error: ems-esp.0 (19766) error reading KM200 gateway (wrong ip address) - stop KM200 read: http://TK-850-JH3E-NETHinweis: Die IP Adresse bzw. der Hostname sind definitiv korrekt. In der MyBuderus App kann ich die Live Daten auch alle sehen.
Output von iob diag IN DER LANGFASSUNG
Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: iobroker-pi Icon name: computer Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.10.103-v7+ Architecture: arm Model : Raspberry Pi 3 Model B Rev 1.2 Docker : false Virtualization : none Kernel : armv7l Userland : 32 bit Systemuptime and Load: 09:43:31 up 1 day, 13:28, 1 user, load average: 1.67, 0.84, 0.52 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Sat 2024-09-14 09:43:31 CEST Universal time: Sat 2024-09-14 07:43:31 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video bluetooth gpio i2c *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 972M 729M 52M 36M 190M 187M Swap: 99M 99M 0.0K Total: 1.1G 829M 52M Active iob-Instances: 11 972 M total memory 729 M used memory 326 M active memory 537 M inactive memory 52 M free memory 28 M buffer memory 162 M swap cache 99 M total swap 99 M used swap 0 M free swap *** top - Table Of Processes *** top - 09:43:31 up 1 day, 13:28, 1 user, load average: 1.67, 0.84, 0.52 Tasks: 132 total, 1 running, 131 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.4 us, 2.8 sy, 0.0 ni, 95.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 972.8 total, 51.9 free, 729.4 used, 191.4 buff/cache MiB Swap: 100.0 total, 0.2 free, 99.8 used. 187.5 avail Mem *** FAILED SERVICES *** 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 57G 5.7G 49G 11% / devtmpfs devtmpfs 454M 0 454M 0% /dev tmpfs tmpfs 487M 0 487M 0% /dev/shm tmpfs tmpfs 487M 50M 438M 11% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 487M 0 487M 0% /sys/fs/cgroup /dev/mmcblk0p1 vfat 247M 49M 198M 20% /boot tmpfs tmpfs 98M 0 98M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Thu Sep 12 20:14:39 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 console=ttyS0,115200 console=tty1 root=PARTUUID=d677b88f-02 rootfstype=ext4 fsck.repair=yes rootwait [Thu Sep 12 20:14:42 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Thu Sep 12 20:14:42 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Thu Sep 12 20:14:44 2024] EXT4-fs (mmcblk0p2): recovery complete [Thu Sep 12 20:14:44 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Thu Sep 12 20:14:44 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Thu Sep 12 20:14:47 2024] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [Fri Sep 13 20:17:02 2024] [<802b0ee8>] (filemap_fault) from [<8042d260>] (ext4_filemap_fault+0x38/0x4c) [Fri Sep 13 20:17:02 2024] [<8042d228>] (ext4_filemap_fault) from [<802e8900>] (__do_fault+0x48/0x14c) Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/dev devtmpfs devtmpfs rw,relatime,size=464768k,nr_inodes=116192,mode=755 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | `-/dev/mqueue mqueue mqueue rw,relatime |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup tmpfs tmpfs ro,nosuid,nodev,noexec,mode=755 | | |-/sys/fs/cgroup/unified cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate | | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd | | |-/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct | | |-/sys/fs/cgroup/net_cls,net_prio cgroup cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio | | |-/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,relatime,perf_event | | |-/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpuset | | |-/sys/fs/cgroup/pids cgroup cgroup rw,nosuid,nodev,noexec,relatime,pids | | |-/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,relatime,freezer | | |-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,relatime,devices | | `-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,relatime,blkio | |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/debug debugfs debugfs rw,relatime | `-/sys/kernel/config configfs configfs rw,relatime |-/proc proc proc rw,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=33,pgrp=1,timeout=0,minproto=5,maxproto=5,direct |-/run tmpfs tmpfs rw,nosuid,nodev,mode=755 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | `-/run/user/1000 tmpfs tmpfs rw,nosuid,nodev,relatime,size=99608k,mode=700,uid=1000,gid=1000 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.7G /var/ 834M /var/lib 739M /var/lib/influxdb 703M /var/lib/influxdb/data 656M /var/lib/influxdb/data/iobroker/autogen Archived and active journals take up 48.6M in the file system. /opt/iobroker/backups: 31M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 272M /opt/iobroker/iobroker-data/ 206M /opt/iobroker/iobroker-data/files 138M /opt/iobroker/iobroker-data/files/javascript.admin 118M /opt/iobroker/iobroker-data/files/javascript.admin/static 117M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map 11M /opt/iobroker/iobroker-data/objects.jsonl 8.0M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.a9c6d34a.chunk.js.map 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/61.54b23816.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' *** NodeJS-Installation *** nodejs: N/A /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 *** nodejs is NOT correctly installed *** nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u3 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf 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: 7.0.23 javascript: 8.3.1 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 : iobroker-pi - enabled, compact disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : iobroker-pi - enabled, compact disabled + system.adapter.ems-esp.0 : ems-esp : iobroker-pi - enabled, compact disabled + system.adapter.history.0 : history : iobroker-pi - enabled, compact disabled + system.adapter.influxdb.0 : influxdb : iobroker-pi - enabled, compact disabled, port: 8086 + system.adapter.javascript.0 : javascript : iobroker-pi - enabled, compact disabled + system.adapter.mqtt.0 : mqtt : iobroker-pi - enabled, compact disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker-pi - enabled, compact disabled, port: 1885, bind: 0.0.0.0 + system.adapter.nut.0 : nut : iobroker-pi - enabled, compact disabled + system.adapter.telegram.0 : telegram : iobroker-pi - enabled, compact disabled, port: 8443, bind: 0.0.0.0 system.adapter.text2command.0 : text2command : iobroker-pi - disabled, compact disabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker-pi - enabled, compact disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : iobroker-pi - enabled, compact disabled, port: 8086 + system.adapter.mqtt.0 : mqtt : iobroker-pi - enabled, compact disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker-pi - enabled, compact disabled, port: 1885, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : iobroker-pi - enabled, compact disabled, port: 8443, bind: 0.0.0.0 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: stableIch sehe selbst gerade, dass es wohl auch ein Problem mit dem NodeJS System gibt. Ich werde versuchen das zu fixen, auch wenn ich keine Ahnung habe.
Danke für jede Hilfe!
VG
Felix@felixrhoese Ich habe das mit dem NodeJS nun auf V18 gefixt. leider ohne Erfolg.
Jemand eine Idee? -
@mcm1957
Danke für den Hinweis!Adapter: EMS-ESP 4.8.0
Admin: 7.0.23
Js-controller: 8.3.1
Node: 18.17.1
O/S: Linux auf Raspberry pi3Log des Adapters mit Level DEBUG:
2024-09-14 09:31:51.979 - info: host.iobroker-pi "system.adapter.ems-esp.0" enabled 2024-09-14 09:31:52.135 - info: host.iobroker-pi instance system.adapter.ems-esp.0 started with pid 19751 2024-09-14 09:31:56.436 - info: ems-esp.0 (19751) starting. Version 4.8.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v18.17.1, js-controller: 5.0.19 2024-09-14 09:31:56.939 - info: ems-esp.0 (19751) InfluxDB 1.x - Retention: 730 days --- Adapterversion: 4.0.2 2024-09-14 09:32:00.037 - info: javascript.0 (13044) script.js.common.10_Heizung.Temperatur_Mean24h: 0 2024-09-14 09:32:06.462 - info: host.iobroker-pi stopInstance system.adapter.ems-esp.0 (force=false, process=true) 2024-09-14 09:32:06.473 - info: ems-esp.0 (19751) Got terminate signal TERMINATE_YOURSELF 2024-09-14 09:32:06.478 - info: ems-esp.0 (19751) terminating 2024-09-14 09:32:06.481 - info: ems-esp.0 (19751) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-09-14 09:32:06.517 - info: host.iobroker-pi stopInstance system.adapter.ems-esp.0 send kill signal 2024-09-14 09:32:07.120 - info: host.iobroker-pi instance system.adapter.ems-esp.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-09-14 09:32:10.138 - info: host.iobroker-pi instance system.adapter.ems-esp.0 started with pid 19766 2024-09-14 09:32:13.802 - info: ems-esp.0 (19766) starting. Version 4.8.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v18.17.1, js-controller: 5.0.19 2024-09-14 09:32:14.187 - info: ems-esp.0 (19766) InfluxDB 1.x - Retention: 730 days --- Adapterversion: 4.0.2 2024-09-14 09:32:20.329 - info: javascript.0 (13044) script.js.common.10_Heizung.Temperature_Mean3h: NaN 2024-09-14 09:32:34.908 - error: ems-esp.0 (19766) error reading KM200 gateway (wrong ip address) - stop KM200 read: http://TK-850-JH3E-NETHinweis: Die IP Adresse bzw. der Hostname sind definitiv korrekt. In der MyBuderus App kann ich die Live Daten auch alle sehen.
Output von iob diag IN DER LANGFASSUNG
Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: iobroker-pi Icon name: computer Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.10.103-v7+ Architecture: arm Model : Raspberry Pi 3 Model B Rev 1.2 Docker : false Virtualization : none Kernel : armv7l Userland : 32 bit Systemuptime and Load: 09:43:31 up 1 day, 13:28, 1 user, load average: 1.67, 0.84, 0.52 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Sat 2024-09-14 09:43:31 CEST Universal time: Sat 2024-09-14 07:43:31 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video bluetooth gpio i2c *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 972M 729M 52M 36M 190M 187M Swap: 99M 99M 0.0K Total: 1.1G 829M 52M Active iob-Instances: 11 972 M total memory 729 M used memory 326 M active memory 537 M inactive memory 52 M free memory 28 M buffer memory 162 M swap cache 99 M total swap 99 M used swap 0 M free swap *** top - Table Of Processes *** top - 09:43:31 up 1 day, 13:28, 1 user, load average: 1.67, 0.84, 0.52 Tasks: 132 total, 1 running, 131 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.4 us, 2.8 sy, 0.0 ni, 95.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 972.8 total, 51.9 free, 729.4 used, 191.4 buff/cache MiB Swap: 100.0 total, 0.2 free, 99.8 used. 187.5 avail Mem *** FAILED SERVICES *** 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 57G 5.7G 49G 11% / devtmpfs devtmpfs 454M 0 454M 0% /dev tmpfs tmpfs 487M 0 487M 0% /dev/shm tmpfs tmpfs 487M 50M 438M 11% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 487M 0 487M 0% /sys/fs/cgroup /dev/mmcblk0p1 vfat 247M 49M 198M 20% /boot tmpfs tmpfs 98M 0 98M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Thu Sep 12 20:14:39 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 console=ttyS0,115200 console=tty1 root=PARTUUID=d677b88f-02 rootfstype=ext4 fsck.repair=yes rootwait [Thu Sep 12 20:14:42 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Thu Sep 12 20:14:42 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Thu Sep 12 20:14:44 2024] EXT4-fs (mmcblk0p2): recovery complete [Thu Sep 12 20:14:44 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Thu Sep 12 20:14:44 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Thu Sep 12 20:14:47 2024] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [Fri Sep 13 20:17:02 2024] [<802b0ee8>] (filemap_fault) from [<8042d260>] (ext4_filemap_fault+0x38/0x4c) [Fri Sep 13 20:17:02 2024] [<8042d228>] (ext4_filemap_fault) from [<802e8900>] (__do_fault+0x48/0x14c) Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/dev devtmpfs devtmpfs rw,relatime,size=464768k,nr_inodes=116192,mode=755 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | `-/dev/mqueue mqueue mqueue rw,relatime |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup tmpfs tmpfs ro,nosuid,nodev,noexec,mode=755 | | |-/sys/fs/cgroup/unified cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate | | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd | | |-/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct | | |-/sys/fs/cgroup/net_cls,net_prio cgroup cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio | | |-/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,relatime,perf_event | | |-/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpuset | | |-/sys/fs/cgroup/pids cgroup cgroup rw,nosuid,nodev,noexec,relatime,pids | | |-/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,relatime,freezer | | |-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,relatime,devices | | `-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,relatime,blkio | |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/debug debugfs debugfs rw,relatime | `-/sys/kernel/config configfs configfs rw,relatime |-/proc proc proc rw,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=33,pgrp=1,timeout=0,minproto=5,maxproto=5,direct |-/run tmpfs tmpfs rw,nosuid,nodev,mode=755 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | `-/run/user/1000 tmpfs tmpfs rw,nosuid,nodev,relatime,size=99608k,mode=700,uid=1000,gid=1000 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.7G /var/ 834M /var/lib 739M /var/lib/influxdb 703M /var/lib/influxdb/data 656M /var/lib/influxdb/data/iobroker/autogen Archived and active journals take up 48.6M in the file system. /opt/iobroker/backups: 31M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 272M /opt/iobroker/iobroker-data/ 206M /opt/iobroker/iobroker-data/files 138M /opt/iobroker/iobroker-data/files/javascript.admin 118M /opt/iobroker/iobroker-data/files/javascript.admin/static 117M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map 11M /opt/iobroker/iobroker-data/objects.jsonl 8.0M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.a9c6d34a.chunk.js.map 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/61.54b23816.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' *** NodeJS-Installation *** nodejs: N/A /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 *** nodejs is NOT correctly installed *** nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u3 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf 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: 7.0.23 javascript: 8.3.1 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 : iobroker-pi - enabled, compact disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : iobroker-pi - enabled, compact disabled + system.adapter.ems-esp.0 : ems-esp : iobroker-pi - enabled, compact disabled + system.adapter.history.0 : history : iobroker-pi - enabled, compact disabled + system.adapter.influxdb.0 : influxdb : iobroker-pi - enabled, compact disabled, port: 8086 + system.adapter.javascript.0 : javascript : iobroker-pi - enabled, compact disabled + system.adapter.mqtt.0 : mqtt : iobroker-pi - enabled, compact disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker-pi - enabled, compact disabled, port: 1885, bind: 0.0.0.0 + system.adapter.nut.0 : nut : iobroker-pi - enabled, compact disabled + system.adapter.telegram.0 : telegram : iobroker-pi - enabled, compact disabled, port: 8443, bind: 0.0.0.0 system.adapter.text2command.0 : text2command : iobroker-pi - disabled, compact disabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker-pi - enabled, compact disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : iobroker-pi - enabled, compact disabled, port: 8086 + system.adapter.mqtt.0 : mqtt : iobroker-pi - enabled, compact disabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker-pi - enabled, compact disabled, port: 1885, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : iobroker-pi - enabled, compact disabled, port: 8443, bind: 0.0.0.0 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: stableIch sehe selbst gerade, dass es wohl auch ein Problem mit dem NodeJS System gibt. Ich werde versuchen das zu fixen, auch wenn ich keine Ahnung habe.
Danke für jede Hilfe!
VG
Felix@felixrhoese sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
(buster)
Muss komplett von Grund auf NEUINSTALLIERT werden.
Diesmal dann in der 64Bit-Lite-Version.Und
*** nodejs is NOT correctly installed *** -
@felixrhoese sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
(buster)
Muss komplett von Grund auf NEUINSTALLIERT werden.
Diesmal dann in der 64Bit-Lite-Version.Und
*** nodejs is NOT correctly installed ***@thomas-braun
Danke für den Hinweis!
Ich habe die Neuinstallation durchgeführt. Leider ohne Erfolg.
Hier die Diag:======================= SUMMARY ======================= v.2024-05-22 Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.47+rpt-rpi-v8 Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs 20.17.0 and npm 10.8.2 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 951M 506M 101M 12K 411M 445M Swap: 209M 124M 85M Total: 1.2G 630M 186M Active iob-Instances: 3 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.0.23 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin Objects: 203 States: 109 Size of iob-Database: 20M /opt/iobroker/iobroker-data/objects.jsonl 1.9M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Im Log sieht es so aus:
2024-09-15 17:45:20.885 - info: host.raspberrypi instance system.adapter.ems-esp.0 in version "4.8.0" started with pid 13020
2024-09-15 17:45:26.224 - info: ems-esp.0 (13020) starting. Version 4.8.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v20.17.0, js-controller: 6.0.11
2024-09-15 17:45:26.498 - info: ems-esp.0 (13020) KM200 no database instance selected for recordings
2024-09-15 17:45:26.843 - info: discovery.0 (13014) starting. Version 4.5.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.17.0, js-controller: 6.0.11
2024-09-15 17:45:27.333 - info: javascript.0 (13007) starting. Version 8.7.6 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.17.0, js-controller: 6.0.11
2024-09-15 17:45:27.866 - info: javascript.0 (13007) requesting all states
2024-09-15 17:45:27.869 - info: javascript.0 (13007) requesting all objects
2024-09-15 17:45:28.840 - warn: javascript.0 (13007) Configured latitude is not a number - check (instance/system) configuration
2024-09-15 17:45:28.843 - warn: javascript.0 (13007) Configured longitude is not a number - check (instance/system) configuration
2024-09-15 17:45:28.845 - info: javascript.0 (13007) received all objects
2024-09-15 17:45:28.858 - info: javascript.0 (13007) received all states
2024-09-15 17:45:47.131 - error: ems-esp.0 (13020) error reading KM200 gateway (wrong ip address) - stop KM200 read: http://192.168.178.84Hat jemand noch eine Idee?
Vielen Dank und viele Grüße Felix -
@thomas-braun
Danke für den Hinweis!
Ich habe die Neuinstallation durchgeführt. Leider ohne Erfolg.
Hier die Diag:======================= SUMMARY ======================= v.2024-05-22 Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.47+rpt-rpi-v8 Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs 20.17.0 and npm 10.8.2 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 951M 506M 101M 12K 411M 445M Swap: 209M 124M 85M Total: 1.2G 630M 186M Active iob-Instances: 3 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.0.23 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin Objects: 203 States: 109 Size of iob-Database: 20M /opt/iobroker/iobroker-data/objects.jsonl 1.9M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Im Log sieht es so aus:
2024-09-15 17:45:20.885 - info: host.raspberrypi instance system.adapter.ems-esp.0 in version "4.8.0" started with pid 13020
2024-09-15 17:45:26.224 - info: ems-esp.0 (13020) starting. Version 4.8.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v20.17.0, js-controller: 6.0.11
2024-09-15 17:45:26.498 - info: ems-esp.0 (13020) KM200 no database instance selected for recordings
2024-09-15 17:45:26.843 - info: discovery.0 (13014) starting. Version 4.5.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.17.0, js-controller: 6.0.11
2024-09-15 17:45:27.333 - info: javascript.0 (13007) starting. Version 8.7.6 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.17.0, js-controller: 6.0.11
2024-09-15 17:45:27.866 - info: javascript.0 (13007) requesting all states
2024-09-15 17:45:27.869 - info: javascript.0 (13007) requesting all objects
2024-09-15 17:45:28.840 - warn: javascript.0 (13007) Configured latitude is not a number - check (instance/system) configuration
2024-09-15 17:45:28.843 - warn: javascript.0 (13007) Configured longitude is not a number - check (instance/system) configuration
2024-09-15 17:45:28.845 - info: javascript.0 (13007) received all objects
2024-09-15 17:45:28.858 - info: javascript.0 (13007) received all states
2024-09-15 17:45:47.131 - error: ems-esp.0 (13020) error reading KM200 gateway (wrong ip address) - stop KM200 read: http://192.168.178.84Hat jemand noch eine Idee?
Vielen Dank und viele Grüße Felix@felixrhoese sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
Hat jemand noch eine Idee?
Langfassung von iobdiag zeigen und ein Tip: mit einem RPI3 mit 1GB Ram kommst Du nicht weit !
-
@thomas-braun
Danke für den Hinweis!
Ich habe die Neuinstallation durchgeführt. Leider ohne Erfolg.
Hier die Diag:======================= SUMMARY ======================= v.2024-05-22 Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.47+rpt-rpi-v8 Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs 20.17.0 and npm 10.8.2 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 951M 506M 101M 12K 411M 445M Swap: 209M 124M 85M Total: 1.2G 630M 186M Active iob-Instances: 3 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.0.23 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin Objects: 203 States: 109 Size of iob-Database: 20M /opt/iobroker/iobroker-data/objects.jsonl 1.9M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Im Log sieht es so aus:
2024-09-15 17:45:20.885 - info: host.raspberrypi instance system.adapter.ems-esp.0 in version "4.8.0" started with pid 13020
2024-09-15 17:45:26.224 - info: ems-esp.0 (13020) starting. Version 4.8.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v20.17.0, js-controller: 6.0.11
2024-09-15 17:45:26.498 - info: ems-esp.0 (13020) KM200 no database instance selected for recordings
2024-09-15 17:45:26.843 - info: discovery.0 (13014) starting. Version 4.5.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.17.0, js-controller: 6.0.11
2024-09-15 17:45:27.333 - info: javascript.0 (13007) starting. Version 8.7.6 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.17.0, js-controller: 6.0.11
2024-09-15 17:45:27.866 - info: javascript.0 (13007) requesting all states
2024-09-15 17:45:27.869 - info: javascript.0 (13007) requesting all objects
2024-09-15 17:45:28.840 - warn: javascript.0 (13007) Configured latitude is not a number - check (instance/system) configuration
2024-09-15 17:45:28.843 - warn: javascript.0 (13007) Configured longitude is not a number - check (instance/system) configuration
2024-09-15 17:45:28.845 - info: javascript.0 (13007) received all objects
2024-09-15 17:45:28.858 - info: javascript.0 (13007) received all states
2024-09-15 17:45:47.131 - error: ems-esp.0 (13020) error reading KM200 gateway (wrong ip address) - stop KM200 read: http://192.168.178.84Hat jemand noch eine Idee?
Vielen Dank und viele Grüße Felix@felixrhoese sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
(wrong ip address)
Welche IP Addresse ist denn die richtige?
-
@felixrhoese sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
(wrong ip address)
Welche IP Addresse ist denn die richtige?
@thomas-braun
Die IP Adresse ist die 192.168.178.84.
Ich habe zwischenzeitlich auch Testweise eine Instanz vom Home Assistanz hochgezogen. Dort gibt des die Bosch Thermostat Integration, die nutzt direkt die Cloud. Da geht alles problemlos. Nur ist der Home Assistant nicht so komfortabel wie der IO Broker. Ich fürchte, die alte Integration über das KM200 Modul direkt, ohne die Nutzung der Cloud geht einfach nicht mehr, wegen FW Update seitens Buderus.
Probiere aber gerne weiter. Ansonsten werde ich mir eine Instanz vom Home Assistant auf dem kleinen Pi laufen lassen und mir für den IO Broker einen neuen holen. Danke für eure Mühen. VG Felix -
@felixrhoese sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
(wrong ip address)
Welche IP Addresse ist denn die richtige?
@thomas-braun
Problem gelöst. Offenbar wurde das Format der Passworteingabe geändert. Es dürfen nun keine Bindestriche mehr genutzt werden. In der Adapter Ansicht ist auch noch das Ausrufezeichen zu sehen. Trotzdem ist in der Objektansicht alles aktuell. Sehr seltsam. Danke an alle, die mitgeholfen haben! VG Felix -
@felixrhoese
Welche Änderung musstest du im iobroker vornehmen, dass der Adapter wieder funktioniert?@luxusl sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
@felixrhoese
Welche Änderung musstest du im iobroker vornehmen, dass der Adapter wieder funktioniert?@felixrhoese sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
Offenbar wurde das Format der Passworteingabe geändert. Es dürfen nun keine Bindestriche mehr genutzt werden.
-
@Homoran
Das habe ich gelesen, nur welche Konsequenz hat dies schlussendlich? einfach die Bindestriche löschen geht nicht...@luxusl sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
einfach die Bindestriche löschen geht nicht...
Natürlich nicht!
Du musst das Passwort ändern -
@luxusl sagte in EMS-ESP mit ipinside funktioniert nicht mehr?:
einfach die Bindestriche löschen geht nicht...
Natürlich nicht!
Du musst das Passwort ändern -
@homoran ich habe eine Buderus, da wüsste ich nicht wie ich das Gateway-Passwort im Gerät ändern kann. Das Passwort ist mit einem Aufkleber sogar außen aufgebracht? Mit der App Buderus MyDevice finde ich keine Änderungsmöglichkeit.
@luxusl dann kann ich dir nicht mehr helfen.
Vielleicht weiss @felixrhoese wie
352
Online32.6k
Benutzer82.0k
Themen1.3m
Beiträge