NEWS
Homebridge Fehler Code 243
ioBroker Allgemein
41
Posts
4
Posters
4.7k
Views
3
Watching
-
@marcelinho sagte in Homebridge Fehler Code 243:
Influxdb läuft bisher problemlos - was kann ich da tun?
Ich würde sagen, unter normalen Bedingungen bekommt man eine InfluxDB kaum in solche Größenordnungen wie bei dir. Der Klassiker ist, dass man versehentlich das Logging von Performancedaten aktiviert hat. Du kannst mal diesen Thread anschauen, ob das bei dir der Fall ist:
https://forum.iobroker.net/topic/73784/speicherplatzbelegung-influxdb2-nach-containerisierung
@marc-berg ja das ist bei mir in der Tat so, ich schreibe viele Datenpunkte in die influxdb (siehe screenshot) die Scrapers habe ich nun gelöscht - wie kann ich nun die Daten bereinigen ? Danke auch Dir für deine Mühe/Hilfe.
-
Bei den Updates war ein Kernel-Update dabei:
Neustart der Kiste erforderlich!iob stop sudo reboot@thomas-braun danke habe ich gemacht - Fehler bleibt bestehen
-
@marc-berg ja das ist bei mir in der Tat so, ich schreibe viele Datenpunkte in die influxdb (siehe screenshot) die Scrapers habe ich nun gelöscht - wie kann ich nun die Daten bereinigen ? Danke auch Dir für deine Mühe/Hilfe.
@marcelinho sagte in Homebridge Fehler Code 243:
wie kann ich nun die Daten bereinigen ?
Ja da hast du jetzt ein kleines Problem. Dadurch, dass die zu löschenden Daten mit in deinem ioBroker Bucket gelandet sind (so habe ich es verstanden), musst du diese einzeln auf der Kommandozeile löschen (Bucketname, Organisation und Measurement anpassen)
influx delete --bucket "iobroker" --predicate '_measurement="storage_cache_inuse_bytes"' --start '1970-01-01T00:00:00Z' --stop '2030-12-31T23:59:00Z' -o homebzw.:
influx delete --bucket "iobroker" --predicate '_measurement="storage_cache_inuse_bytes"' --start '1970-01-01T00:00:00Z' --stop '2030-12-31T23:59:00Z' -o home -t <token>Ich würde aber dringend empfehlen, die Daten dort rauszulöschen, da man ja in deinen Logs schon sieht, dass die Datenbank Probleme und Timeouts hat.
EDIT: hier ein kleines Script zum Löschen der Daten:
delete_scraper_data.sh -
@marcelinho sagte in Homebridge Fehler Code 243:
wie kann ich nun die Daten bereinigen ?
Ja da hast du jetzt ein kleines Problem. Dadurch, dass die zu löschenden Daten mit in deinem ioBroker Bucket gelandet sind (so habe ich es verstanden), musst du diese einzeln auf der Kommandozeile löschen (Bucketname, Organisation und Measurement anpassen)
influx delete --bucket "iobroker" --predicate '_measurement="storage_cache_inuse_bytes"' --start '1970-01-01T00:00:00Z' --stop '2030-12-31T23:59:00Z' -o homebzw.:
influx delete --bucket "iobroker" --predicate '_measurement="storage_cache_inuse_bytes"' --start '1970-01-01T00:00:00Z' --stop '2030-12-31T23:59:00Z' -o home -t <token>Ich würde aber dringend empfehlen, die Daten dort rauszulöschen, da man ja in deinen Logs schon sieht, dass die Datenbank Probleme und Timeouts hat.
EDIT: hier ein kleines Script zum Löschen der Daten:
delete_scraper_data.sh@marc-berg Danke nochmal, Nodered funktioniert jetzt auch - hat nur etwas Zeit gebraucht.
Bist der beste - Schönen Abend noch Marc
-
Bei den Updates war ein Kernel-Update dabei:
Neustart der Kiste erforderlich!iob stop sudo reboot@thomas-braun wie besprochen die neue Auslesung / Fehler Homebridge bleibt bestehen:
======== Start marking the full check here =========Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi7-rpi-v8 Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 15:54:39 up 22:08, 3 users, load average: 0.21, 0.31, 0.27 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Wed 2024-04-24 15:54:39 CEST Universal time: Wed 2024-04-24 13:54:39 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input render netdev lp admin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 4.0G 2.9G 288M 86K 858M 1.1G Swap: 104M 15M 89M Total: 4.1G 2.9G 378M 3793 M total memory 2774 M used memory 2927 M active memory 374 M inactive memory 274 M free memory 93 M buffer memory 726 M swap cache 99 M total swap 14 M used swap 85 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.6G 0 1.6G 0% /dev tmpfs tmpfs 380M 1.2M 379M 1% /run /dev/mmcblk0p2 ext4 29G 20G 8.0G 71% / tmpfs tmpfs 1.9G 8.0K 1.9G 1% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 73M 438M 15% /boot/firmware tmpfs tmpfs 380M 32K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Tue Apr 23 17:46:09 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.ena ble_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=D8:3A:DD:1A:71:9B vc_mem. mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty 1 root=PARTUUID=1e048ecb-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splas h plymouth.ignore-serial-consoles [Tue Apr 23 17:46:12 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Tue Apr 23 17:46:14 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepag e=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 11G /var/ 8.9G /var/lib 8.3G /var/lib/influxdb/engine/data/86690b2dbdd230c8/autogen 8.3G /var/lib/influxdb/engine/data/86690b2dbdd230c8 8.3G /var/lib/influxdb/engine/data Archived and active journals take up 739.9M in the file system. /opt/iobroker/backups: 215M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 320M /opt/iobroker/iobroker-data/ 191M /opt/iobroker/iobroker-data/files 57M /opt/iobroker/iobroker-data/files/javascript.admin 52M /opt/iobroker/iobroker-data/backup-objects 38M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 32M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.m ap 22M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.578d79d9.j s.map 9.8M /opt/iobroker/iobroker-data/states.jsonl 8.8M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.578d79d9.j s USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4452914ae9ded11bf 33d1a5a7669f5d-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.20.2 /usr/bin/node v18.20.2 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.25.2 nodejs: Installed: 18.20.2-1nodesource1 Candidate: 18.20.2-1nodesource1 Version table: *** 18.20.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.20.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main arm64 P ackages 18.19.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 3 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admi n + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.cloud.0 : cloud : raspberrypi - enabled + system.adapter.daikin-cloud.0 : daikin-cloud : raspberrypi - enabled + system.adapter.daikin.0 : daikin : raspberrypi - enabled + system.adapter.daikin.1 : daikin : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled + system.adapter.ecovacs-deebot.0 : ecovacs-deebot : raspberrypi - enabled + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.iqontrol.0 : iqontrol : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.lg-thinq.0 : lg-thinq : raspberrypi - enabled + system.adapter.meross.0 : meross : raspberrypi - enabled + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.myenergi.0 : myenergi : raspberrypi - enabled + system.adapter.node-red.0 : node-red : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.smart-eq.0 : smart-eq : raspberrypi - enabled + system.adapter.tesla-motors.0 : tesla-motors : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admi n + system.adapter.zigbee2mqtt.0 : zigbee2mqtt : raspberrypi - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admi n + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admi n ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "backitup" : 2.11.0 , installed 2.11.0 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "daikin" : 1.4.2 , installed 1.4.2 Adapter "daikin-cloud" : 0.3.0 , installed 0.3.0 Adapter "discovery" : 4.4.0 , installed 4.4.0 Adapter "ecovacs-deebot": 1.4.15 , installed 1.4.15 Adapter "homekit-controller": 0.5.10, installed 0.5.10 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "iqontrol" : 2.3.0 , installed 2.3.0 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "lg-thinq" : 0.3.3 , installed 0.3.3 Adapter "meross" : 1.17.0 , installed 1.17.0 Adapter "modbus" : 6.1.0 , installed 6.1.0 Adapter "mqtt" : 5.2.0 , installed 5.2.0 Adapter "mqtt-client" : 1.7.0 , installed 1.7.0 Adapter "myenergi" : 0.0.3 , installed 0.0.3 Adapter "node-red" : 5.2.0 , installed 5.2.0 Adapter "openhab" : 1.1.0 , installed 1.1.0 Adapter "shelly" : 6.8.0 , installed 6.8.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "smart-eq" : 0.0.4 , installed 0.0.6 Adapter "socketio" : 6.6.1 , installed 6.6.1 Adapter "tesla-motors" : 1.3.2 , installed 1.3.2 Adapter "tuya" : 3.15.0 , installed 3.15.0 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.5.11 , installed 2.5.11 Adapter "zigbee" : 1.10.3 , installed 1.10.3 Adapter "zigbee2mqtt" : 2.13.6 , installed 2.13.6 Objects and States Please stand by - This may take a while Objects: 14989 States: 13387 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Hit:5 https://repos.influxdata.com/debian stable InRelease Hit:6 https://apt.grafana.com stable InRelease Hit:7 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:8 https://repo.homebridge.io stable 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 127.0.0.1:38691 0.0.0.0:* LISTEN 112 17194 1300/homebridge: @0 tcp 0 0 127.0.0.1:38543 0.0.0.0:* LISTEN 112 17159 1317/homebridge: ho tcp 0 0 127.0.0.1:40315 0.0.0.0:* LISTEN 112 17110 1290/homebridge: ho tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 1001 26211 1952/node-red tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 114 16746 786/mosquitto tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 19125 1561/io.shelly.0 tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 20031 1576/io.mqtt.0 tcp 0 0 127.0.0.1:46551 0.0.0.0:* LISTEN 112 21533 1634/homebridge: ho tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1000 21580 1617/node tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 16938 1082/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 17920 1082/iobroker.js-co tcp 0 0 127.0.0.1:37849 0.0.0.0:* LISTEN 112 19798 1298/homebridge: ho tcp 0 0 127.0.0.1:35727 0.0.0.0:* LISTEN 112 17154 1291/homebridge: ho tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 17543 792/sshd: /usr/sbin tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 343770 9169/cupsd tcp 0 0 127.0.0.1:45139 0.0.0.0:* LISTEN 112 18280 1293/homebridge: ho tcp 0 0 127.0.0.1:39007 0.0.0.0:* LISTEN 112 19738 1319/homebridge: ho tcp6 0 0 :::52403 :::* LISTEN 112 19754 1298/homebridge: ho tcp6 0 0 :::44253 :::* LISTEN 112 19726 1317/homebridge: ho tcp6 0 0 :::1883 :::* LISTEN 114 16747 786/mosquitto tcp6 0 0 :::8081 :::* LISTEN 1001 19538 1140/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 21629 1690/io.web.0 tcp6 0 0 :::8086 :::* LISTEN 999 16913 892/influxd tcp6 0 0 ::1:631 :::* LISTEN 0 343769 9169/cupsd tcp6 0 0 :::37166 :::* LISTEN 112 18883 1291/homebridge: ho tcp6 0 0 :::45391 :::* LISTEN 112 18903 1300/homebridge: @0 tcp6 0 0 :::8581 :::* LISTEN 112 17952 1058/hb-service tcp6 0 0 :::53299 :::* LISTEN 112 19213 1634/homebridge: ho tcp6 0 0 :::22 :::* LISTEN 0 17545 792/sshd: /usr/sbin tcp6 0 0 :::47961 :::* LISTEN 112 18841 1290/homebridge: ho tcp6 0 0 :::3000 :::* LISTEN 113 15360 1081/grafana tcp6 0 0 :::52120 :::* LISTEN 112 17120 1319/homebridge: ho tcp6 0 0 :::51798 :::* LISTEN 112 18821 1147/homebridge tcp6 0 0 :::39667 :::* LISTEN 112 18857 1293/homebridge: ho udp 0 0 0.0.0.0:5353 0.0.0.0:* 112 18887 1293/homebridge: ho udp 0 0 0.0.0.0:5353 0.0.0.0:* 112 17949 1058/hb-service udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 14012 549/avahi-daemon: r udp 0 0 0.0.0.0:38879 0.0.0.0:* 104 14014 549/avahi-daemon: r udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 20514 1467/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 20515 1467/io.tuya.0 udp 0 0 0.0.0.0:631 0.0.0.0:* 0 343790 9192/cups-browsed udp6 0 0 :::5353 :::* 104 14013 549/avahi-daemon: r udp6 0 0 :::49377 :::* 104 14015 549/avahi-daemon: r udp6 0 0 fe80::81a3:20c2:583:546 :::* 0 17593 652/NetworkManager *** Log File - Last 25 Lines *** 2024-04-24 15:56:16.028 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=1 2024-04-24 15:56:16.031 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.032 - warn: influxdb.0 (1208) Error on writePoint("{"value":-2,"time":"2024-04-24T13:55:54.255Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.032 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=2 2024-04-24 15:56:16.037 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.037 - warn: influxdb.0 (1208) Error on writePoint("{"value":0,"time":"2024-04-24T13:55:54.255Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.037 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Einspeisung_W to buffer again, error-count=1 2024-04-24 15:56:16.132 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.133 - warn: influxdb.0 (1208) Error on writePoint("{"value":-8,"time":"2024-04-24T13:56:05.088Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.134 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Huawei.Meter.Active_Power to buffer again, error-count=2 2024-04-24 15:56:16.154 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.155 - warn: influxdb.0 (1208) Error on writePoint("{"value":96,"time":"2024-04-24T13:55:59.437Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.155 - info: influxdb.0 (1208) Add point that had error for BatterieProzent to buffer again, error-count=1 2024-04-24 15:56:16.165 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.165 - warn: influxdb.0 (1208) Error on writePoint("{"value":-8,"time":"2024-04-24T13:56:05.091Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.165 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=3 2024-04-24 15:56:16.173 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.173 - warn: influxdb.0 (1208) Error on writePoint("{"value":24.5,"time":"2024-04-24T13:55:02.852Z","from":"system.adapter.tuya.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.174 - info: influxdb.0 (1208) Add point that had error for EsszimmerThermostat to buffer again, error-count=1 2024-04-24 15:56:16.180 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.181 - warn: influxdb.0 (1208) Error on writePoint("{"value":98,"time":"2024-04-24T13:50:00.207Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.181 - info: influxdb.0 (1208) Add point that had error for BatterieProzent to buffer again, error-count=2 2024-04-24 15:56:16.202 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.202 - warn: influxdb.0 (1208) Error on writePoint("{"value":24,"time":"2024-04-24T13:56:01.967Z","from":"system.adapter.tuya.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.203 - info: influxdb.0 (1208) Add point that had error for EsszimmerThermostat to buffer again, error-count=2============ Mark until here for C&P =============
-
@thomas-braun wie besprochen die neue Auslesung / Fehler Homebridge bleibt bestehen:
======== Start marking the full check here =========Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi7-rpi-v8 Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 15:54:39 up 22:08, 3 users, load average: 0.21, 0.31, 0.27 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Wed 2024-04-24 15:54:39 CEST Universal time: Wed 2024-04-24 13:54:39 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input render netdev lp admin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 4.0G 2.9G 288M 86K 858M 1.1G Swap: 104M 15M 89M Total: 4.1G 2.9G 378M 3793 M total memory 2774 M used memory 2927 M active memory 374 M inactive memory 274 M free memory 93 M buffer memory 726 M swap cache 99 M total swap 14 M used swap 85 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.6G 0 1.6G 0% /dev tmpfs tmpfs 380M 1.2M 379M 1% /run /dev/mmcblk0p2 ext4 29G 20G 8.0G 71% / tmpfs tmpfs 1.9G 8.0K 1.9G 1% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 73M 438M 15% /boot/firmware tmpfs tmpfs 380M 32K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Tue Apr 23 17:46:09 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.ena ble_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=D8:3A:DD:1A:71:9B vc_mem. mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty 1 root=PARTUUID=1e048ecb-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splas h plymouth.ignore-serial-consoles [Tue Apr 23 17:46:12 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Tue Apr 23 17:46:14 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepag e=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 11G /var/ 8.9G /var/lib 8.3G /var/lib/influxdb/engine/data/86690b2dbdd230c8/autogen 8.3G /var/lib/influxdb/engine/data/86690b2dbdd230c8 8.3G /var/lib/influxdb/engine/data Archived and active journals take up 739.9M in the file system. /opt/iobroker/backups: 215M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 320M /opt/iobroker/iobroker-data/ 191M /opt/iobroker/iobroker-data/files 57M /opt/iobroker/iobroker-data/files/javascript.admin 52M /opt/iobroker/iobroker-data/backup-objects 38M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 32M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.m ap 22M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.578d79d9.j s.map 9.8M /opt/iobroker/iobroker-data/states.jsonl 8.8M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.578d79d9.j s USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4452914ae9ded11bf 33d1a5a7669f5d-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.20.2 /usr/bin/node v18.20.2 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.25.2 nodejs: Installed: 18.20.2-1nodesource1 Candidate: 18.20.2-1nodesource1 Version table: *** 18.20.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.20.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main arm64 P ackages 18.19.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 3 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admi n + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.cloud.0 : cloud : raspberrypi - enabled + system.adapter.daikin-cloud.0 : daikin-cloud : raspberrypi - enabled + system.adapter.daikin.0 : daikin : raspberrypi - enabled + system.adapter.daikin.1 : daikin : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled + system.adapter.ecovacs-deebot.0 : ecovacs-deebot : raspberrypi - enabled + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.iqontrol.0 : iqontrol : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.lg-thinq.0 : lg-thinq : raspberrypi - enabled + system.adapter.meross.0 : meross : raspberrypi - enabled + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.myenergi.0 : myenergi : raspberrypi - enabled + system.adapter.node-red.0 : node-red : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.smart-eq.0 : smart-eq : raspberrypi - enabled + system.adapter.tesla-motors.0 : tesla-motors : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admi n + system.adapter.zigbee2mqtt.0 : zigbee2mqtt : raspberrypi - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admi n + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admi n ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "backitup" : 2.11.0 , installed 2.11.0 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "daikin" : 1.4.2 , installed 1.4.2 Adapter "daikin-cloud" : 0.3.0 , installed 0.3.0 Adapter "discovery" : 4.4.0 , installed 4.4.0 Adapter "ecovacs-deebot": 1.4.15 , installed 1.4.15 Adapter "homekit-controller": 0.5.10, installed 0.5.10 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "iqontrol" : 2.3.0 , installed 2.3.0 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "lg-thinq" : 0.3.3 , installed 0.3.3 Adapter "meross" : 1.17.0 , installed 1.17.0 Adapter "modbus" : 6.1.0 , installed 6.1.0 Adapter "mqtt" : 5.2.0 , installed 5.2.0 Adapter "mqtt-client" : 1.7.0 , installed 1.7.0 Adapter "myenergi" : 0.0.3 , installed 0.0.3 Adapter "node-red" : 5.2.0 , installed 5.2.0 Adapter "openhab" : 1.1.0 , installed 1.1.0 Adapter "shelly" : 6.8.0 , installed 6.8.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "smart-eq" : 0.0.4 , installed 0.0.6 Adapter "socketio" : 6.6.1 , installed 6.6.1 Adapter "tesla-motors" : 1.3.2 , installed 1.3.2 Adapter "tuya" : 3.15.0 , installed 3.15.0 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.5.11 , installed 2.5.11 Adapter "zigbee" : 1.10.3 , installed 1.10.3 Adapter "zigbee2mqtt" : 2.13.6 , installed 2.13.6 Objects and States Please stand by - This may take a while Objects: 14989 States: 13387 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Hit:5 https://repos.influxdata.com/debian stable InRelease Hit:6 https://apt.grafana.com stable InRelease Hit:7 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:8 https://repo.homebridge.io stable 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 127.0.0.1:38691 0.0.0.0:* LISTEN 112 17194 1300/homebridge: @0 tcp 0 0 127.0.0.1:38543 0.0.0.0:* LISTEN 112 17159 1317/homebridge: ho tcp 0 0 127.0.0.1:40315 0.0.0.0:* LISTEN 112 17110 1290/homebridge: ho tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 1001 26211 1952/node-red tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 114 16746 786/mosquitto tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 19125 1561/io.shelly.0 tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 20031 1576/io.mqtt.0 tcp 0 0 127.0.0.1:46551 0.0.0.0:* LISTEN 112 21533 1634/homebridge: ho tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1000 21580 1617/node tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 16938 1082/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 17920 1082/iobroker.js-co tcp 0 0 127.0.0.1:37849 0.0.0.0:* LISTEN 112 19798 1298/homebridge: ho tcp 0 0 127.0.0.1:35727 0.0.0.0:* LISTEN 112 17154 1291/homebridge: ho tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 17543 792/sshd: /usr/sbin tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 343770 9169/cupsd tcp 0 0 127.0.0.1:45139 0.0.0.0:* LISTEN 112 18280 1293/homebridge: ho tcp 0 0 127.0.0.1:39007 0.0.0.0:* LISTEN 112 19738 1319/homebridge: ho tcp6 0 0 :::52403 :::* LISTEN 112 19754 1298/homebridge: ho tcp6 0 0 :::44253 :::* LISTEN 112 19726 1317/homebridge: ho tcp6 0 0 :::1883 :::* LISTEN 114 16747 786/mosquitto tcp6 0 0 :::8081 :::* LISTEN 1001 19538 1140/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 21629 1690/io.web.0 tcp6 0 0 :::8086 :::* LISTEN 999 16913 892/influxd tcp6 0 0 ::1:631 :::* LISTEN 0 343769 9169/cupsd tcp6 0 0 :::37166 :::* LISTEN 112 18883 1291/homebridge: ho tcp6 0 0 :::45391 :::* LISTEN 112 18903 1300/homebridge: @0 tcp6 0 0 :::8581 :::* LISTEN 112 17952 1058/hb-service tcp6 0 0 :::53299 :::* LISTEN 112 19213 1634/homebridge: ho tcp6 0 0 :::22 :::* LISTEN 0 17545 792/sshd: /usr/sbin tcp6 0 0 :::47961 :::* LISTEN 112 18841 1290/homebridge: ho tcp6 0 0 :::3000 :::* LISTEN 113 15360 1081/grafana tcp6 0 0 :::52120 :::* LISTEN 112 17120 1319/homebridge: ho tcp6 0 0 :::51798 :::* LISTEN 112 18821 1147/homebridge tcp6 0 0 :::39667 :::* LISTEN 112 18857 1293/homebridge: ho udp 0 0 0.0.0.0:5353 0.0.0.0:* 112 18887 1293/homebridge: ho udp 0 0 0.0.0.0:5353 0.0.0.0:* 112 17949 1058/hb-service udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 14012 549/avahi-daemon: r udp 0 0 0.0.0.0:38879 0.0.0.0:* 104 14014 549/avahi-daemon: r udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 20514 1467/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 20515 1467/io.tuya.0 udp 0 0 0.0.0.0:631 0.0.0.0:* 0 343790 9192/cups-browsed udp6 0 0 :::5353 :::* 104 14013 549/avahi-daemon: r udp6 0 0 :::49377 :::* 104 14015 549/avahi-daemon: r udp6 0 0 fe80::81a3:20c2:583:546 :::* 0 17593 652/NetworkManager *** Log File - Last 25 Lines *** 2024-04-24 15:56:16.028 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=1 2024-04-24 15:56:16.031 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.032 - warn: influxdb.0 (1208) Error on writePoint("{"value":-2,"time":"2024-04-24T13:55:54.255Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.032 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=2 2024-04-24 15:56:16.037 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.037 - warn: influxdb.0 (1208) Error on writePoint("{"value":0,"time":"2024-04-24T13:55:54.255Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.037 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Einspeisung_W to buffer again, error-count=1 2024-04-24 15:56:16.132 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.133 - warn: influxdb.0 (1208) Error on writePoint("{"value":-8,"time":"2024-04-24T13:56:05.088Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.134 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Huawei.Meter.Active_Power to buffer again, error-count=2 2024-04-24 15:56:16.154 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.155 - warn: influxdb.0 (1208) Error on writePoint("{"value":96,"time":"2024-04-24T13:55:59.437Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.155 - info: influxdb.0 (1208) Add point that had error for BatterieProzent to buffer again, error-count=1 2024-04-24 15:56:16.165 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.165 - warn: influxdb.0 (1208) Error on writePoint("{"value":-8,"time":"2024-04-24T13:56:05.091Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.165 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=3 2024-04-24 15:56:16.173 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.173 - warn: influxdb.0 (1208) Error on writePoint("{"value":24.5,"time":"2024-04-24T13:55:02.852Z","from":"system.adapter.tuya.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.174 - info: influxdb.0 (1208) Add point that had error for EsszimmerThermostat to buffer again, error-count=1 2024-04-24 15:56:16.180 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.181 - warn: influxdb.0 (1208) Error on writePoint("{"value":98,"time":"2024-04-24T13:50:00.207Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.181 - info: influxdb.0 (1208) Add point that had error for BatterieProzent to buffer again, error-count=2 2024-04-24 15:56:16.202 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.202 - warn: influxdb.0 (1208) Error on writePoint("{"value":24,"time":"2024-04-24T13:56:01.967Z","from":"system.adapter.tuya.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.203 - info: influxdb.0 (1208) Add point that had error for EsszimmerThermostat to buffer again, error-count=2============ Mark until here for C&P =============
@marcelinho sagte in Homebridge Fehler Code 243:
Pending Updates: 3
Hau die noch rein.
Und deiner influxdb geht es immer noch nicht so richtig gut, würde ich sagen.
Wenn die da im Millisekundenbereich auf Fehler läuft kann das nicht gesund sein.Zu Homebridge: Mit ist immer noch nicht klar was genau du da machen willst.
-
@marcelinho sagte in Homebridge Fehler Code 243:
Pending Updates: 3
Hau die noch rein.
Und deiner influxdb geht es immer noch nicht so richtig gut, würde ich sagen.
Wenn die da im Millisekundenbereich auf Fehler läuft kann das nicht gesund sein.Zu Homebridge: Mit ist immer noch nicht klar was genau du da machen willst.
@thomas-braun mit sudo apt update & upgrade sollte das gehen oder?
Ich möchte Homebridge aktualisieren bzw alte plugins die nicht mehr benötigt werden löschen.
Influxdb habe ich gestern mit @Marc-Berg bereinigt. Wüsste nicht was da falsch gehen sollte in grafana wird alles korrekt angezeigt. -
@thomas-braun mit sudo apt update & upgrade sollte das gehen oder?
Ich möchte Homebridge aktualisieren bzw alte plugins die nicht mehr benötigt werden löschen.
Influxdb habe ich gestern mit @Marc-Berg bereinigt. Wüsste nicht was da falsch gehen sollte in grafana wird alles korrekt angezeigt.@marcelinho sagte in Homebridge Fehler Code 243:
Wüsste nicht was da falsch gehen sollte
Dann schau in das Log:
2024-04-24 15:56:16.028 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=1 2024-04-24 15:56:16.031 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.032 - warn: influxdb.0 (1208) Error on writePoint("{"value":-2,"time":"2024-04-24T13:55:54.255Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.032 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=2 2024-04-24 15:56:16.037 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.037 - warn: influxdb.0 (1208) Error on writePoint("{"value":0,"time":"2024-04-24T13:55:54.255Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.037 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Einspeisung_W to buffer again, error-count=1 2024-04-24 15:56:16.132 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.133 - warn: influxdb.0 (1208) Error on writePoint("{"value":-8,"time":"2024-04-24T13:56:05.088Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.134 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Huawei.Meter.Active_Power to buffer again, error-count=2 2024-04-24 15:56:16.154 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.155 - warn: influxdb.0 (1208) Error on writePoint("{"value":96,"time":"2024-04-24T13:55:59.437Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.155 - info: influxdb.0 (1208) Add point that had error for BatterieProzent to buffer again, error-count=1 2024-04-24 15:56:16.165 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.165 - warn: influxdb.0 (1208) Error on writePoint("{"value":-8,"time":"2024-04-24T13:56:05.091Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.165 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=3 2024-04-24 15:56:16.173 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.173 - warn: influxdb.0 (1208) Error on writePoint("{"value":24.5,"time":"2024-04-24T13:55:02.852Z","from":"system.adapter.tuya.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.174 - info: influxdb.0 (1208) Add point that had error for EsszimmerThermostat to buffer again, error-count=1 2024-04-24 15:56:16.180 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.181 - warn: influxdb.0 (1208) Error on writePoint("{"value":98,"time":"2024-04-24T13:50:00.207Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.181 - info: influxdb.0 (1208) Add point that had error for BatterieProzent to buffer again, error-count=2 2024-04-24 15:56:16.202 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.202 - warn: influxdb.0 (1208) Error on writePoint("{"value":24,"time":"2024-04-24T13:56:01.967Z","from":"system.adapter.tuya.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.203 - info: influxdb.0 (1208) Add point that had error for EsszimmerThermostat to buffer again, error-count=2Sieht für mich nicht gesund aus. Insbesondere nicht in der Frequenz mit der da Zeug geloggt wird. Das bläst dir alleine das Logfile in kürzester Zeit auf unnötige Größen auf.
Homebridge über den ham-Adapter? Der ist aber gar nicht installiert bei dir.
-
@thomas-braun mit sudo apt update & upgrade sollte das gehen oder?
Ich möchte Homebridge aktualisieren bzw alte plugins die nicht mehr benötigt werden löschen.
Influxdb habe ich gestern mit @Marc-Berg bereinigt. Wüsste nicht was da falsch gehen sollte in grafana wird alles korrekt angezeigt.@marcelinho sagte in Homebridge Fehler Code 243:
Influxdb habe ich gestern mit @Marc-Berg bereinigt
Jain. Du hattest den Speicherzeitraum der InfluxDB auf 90 Tage gesetzt und wir haben gesagt, dass die ungewollt geloggten Daten nach 90 Tagen endgültig raus sind.
Du könntest des Speicherzeitraum jetzt auch noch weiter verkürzen, um den Effekt zu beschleunigen.
Weiterhin kannst du in den Datenpunkteinstellungen des InfluxDB Adapters prüfen, ob du weniger Daten wegschreibst, indem du z.B. die Blockierzeit auf 30 Sekunden setzt.
-
@marcelinho sagte in Homebridge Fehler Code 243:
Wüsste nicht was da falsch gehen sollte
Dann schau in das Log:
2024-04-24 15:56:16.028 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=1 2024-04-24 15:56:16.031 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.032 - warn: influxdb.0 (1208) Error on writePoint("{"value":-2,"time":"2024-04-24T13:55:54.255Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.032 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=2 2024-04-24 15:56:16.037 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.037 - warn: influxdb.0 (1208) Error on writePoint("{"value":0,"time":"2024-04-24T13:55:54.255Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.037 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Einspeisung_W to buffer again, error-count=1 2024-04-24 15:56:16.132 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.133 - warn: influxdb.0 (1208) Error on writePoint("{"value":-8,"time":"2024-04-24T13:56:05.088Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.134 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Huawei.Meter.Active_Power to buffer again, error-count=2 2024-04-24 15:56:16.154 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.155 - warn: influxdb.0 (1208) Error on writePoint("{"value":96,"time":"2024-04-24T13:55:59.437Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.155 - info: influxdb.0 (1208) Add point that had error for BatterieProzent to buffer again, error-count=1 2024-04-24 15:56:16.165 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.165 - warn: influxdb.0 (1208) Error on writePoint("{"value":-8,"time":"2024-04-24T13:56:05.091Z","from":"system.adapter.javascript.0","q":0,"ack":false}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.165 - info: influxdb.0 (1208) Add point that had error for 0_userdata.0.Stromverbrauch.Netzbezug_W to buffer again, error-count=3 2024-04-24 15:56:16.173 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.173 - warn: influxdb.0 (1208) Error on writePoint("{"value":24.5,"time":"2024-04-24T13:55:02.852Z","from":"system.adapter.tuya.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.174 - info: influxdb.0 (1208) Add point that had error for EsszimmerThermostat to buffer again, error-count=1 2024-04-24 15:56:16.180 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.181 - warn: influxdb.0 (1208) Error on writePoint("{"value":98,"time":"2024-04-24T13:50:00.207Z","from":"system.adapter.node-red.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.181 - info: influxdb.0 (1208) Add point that had error for BatterieProzent to buffer again, error-count=2 2024-04-24 15:56:16.202 - warn: influxdb.0 (1208) Point could not be written to database: admin 2024-04-24 15:56:16.202 - warn: influxdb.0 (1208) Error on writePoint("{"value":24,"time":"2024-04-24T13:56:01.967Z","from":"system.adapter.tuya.0","q":0,"ack":true}): HttpError: unexpected error writing points to database: timeout / "unexpected error writing points to database: timeout"" 2024-04-24 15:56:16.203 - info: influxdb.0 (1208) Add point that had error for EsszimmerThermostat to buffer again, error-count=2Sieht für mich nicht gesund aus. Insbesondere nicht in der Frequenz mit der da Zeug geloggt wird. Das bläst dir alleine das Logfile in kürzester Zeit auf unnötige Größen auf.
Homebridge über den ham-Adapter? Der ist aber gar nicht installiert bei dir.
@thomas-braun said in Homebridge Fehler Code 243:
ham-Adapter
Homebridge habe ich über die SD-Karte über ein Image installiert gehabt
https://smartapfel.de/homebridge/installieren/ -
@marcelinho sagte in Homebridge Fehler Code 243:
Influxdb habe ich gestern mit @Marc-Berg bereinigt
Jain. Du hattest den Speicherzeitraum der InfluxDB auf 90 Tage gesetzt und wir haben gesagt, dass die ungewollt geloggten Daten nach 90 Tagen endgültig raus sind.
Du könntest des Speicherzeitraum jetzt auch noch weiter verkürzen, um den Effekt zu beschleunigen.
Weiterhin kannst du in den Datenpunkteinstellungen des InfluxDB Adapters prüfen, ob du weniger Daten wegschreibst, indem du z.B. die Blockierzeit auf 30 Sekunden setzt.
@marc-berg ich habe im influx.db Adapter nun auch 90 Tage geändert und die Blockzeit auf 30 gesetzt - ist dies so korrekt?
-
@thomas-braun said in Homebridge Fehler Code 243:
ham-Adapter
Homebridge habe ich über die SD-Karte über ein Image installiert gehabt
https://smartapfel.de/homebridge/installieren/Und wo ist da jetzt die Verbindung zum ioBroker?
-
@marc-berg ich habe im influx.db Adapter nun auch 90 Tage geändert und die Blockzeit auf 30 gesetzt - ist dies so korrekt?
@marcelinho sagte in Homebridge Fehler Code 243:
ich habe im influx.db Adapter nun auch 90 Tage geändert und die Blockzeit auf 30 gesetzt - ist dies so korrekt?
Ob du die Einstellung für die Vorhaltezeit in der Instanz des Adapters änderst oder direkt in der Datenbank-Oberfläche ist völlig egal, das funktioniert beides.
Zur Blockzeit: Du hast jetzt lediglich die "Standardeinstellung" geändert, die angezogen wird, wenn du neue Datenpunkte mit der InfluxDB verbindest. Dies hat keine Auswirkungen auf schon bestehende Datenpunkte.
Du solltest also Datenpunkt für Datenpunkt durchgehen und jeweils schauen, ob du nur geänderte Werte aufzeichnen willst, ob du eine Blockzeit verwendest oder nur Änderungen protokollierst, wenn sich der Wert um x ändert.
Das kann man nicht pauschal empfehlen, es hängt einfach davon ab, welche Daten jeweils in welchen Intervallen reinfliegen. Ziel sollte jedenfalls sein, die Menge an Daten, die (vielleicht unnötigerweise) in die Datenbank geschrieben wird, auf ein sinnvolles Maß zu reduzieren.EDIT: Außerdem wird die Blockzeit in Millisekunden angegeben
-
Und wo ist da jetzt die Verbindung zum ioBroker?
@thomas-braun sagte in Homebridge Fehler Code 243:
Und wo ist da jetzt die Verbindung zum ioBroker?
Im Tab "DB Settings"!?
-
@marcelinho sagte in Homebridge Fehler Code 243:
ich habe im influx.db Adapter nun auch 90 Tage geändert und die Blockzeit auf 30 gesetzt - ist dies so korrekt?
Ob du die Einstellung für die Vorhaltezeit in der Instanz des Adapters änderst oder direkt in der Datenbank-Oberfläche ist völlig egal, das funktioniert beides.
Zur Blockzeit: Du hast jetzt lediglich die "Standardeinstellung" geändert, die angezogen wird, wenn du neue Datenpunkte mit der InfluxDB verbindest. Dies hat keine Auswirkungen auf schon bestehende Datenpunkte.
Du solltest also Datenpunkt für Datenpunkt durchgehen und jeweils schauen, ob du nur geänderte Werte aufzeichnen willst, ob du eine Blockzeit verwendest oder nur Änderungen protokollierst, wenn sich der Wert um x ändert.
Das kann man nicht pauschal empfehlen, es hängt einfach davon ab, welche Daten jeweils in welchen Intervallen reinfliegen. Ziel sollte jedenfalls sein, die Menge an Daten, die (vielleicht unnötigerweise) in die Datenbank geschrieben wird, auf ein sinnvolles Maß zu reduzieren.EDIT: Außerdem wird die Blockzeit in Millisekunden angegeben
@marc-berg jetzt sieht es wohl besser aus, habe alle Influxdb Datenpunkte mit Millisekunden angepasst:
======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi7-rpi-v8 Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 09:23:33 up 1 day, 15:37, 3 users, load average: 0.27, 0.37, 0.33 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Thu 2024-04-25 09:23:33 CEST Universal time: Thu 2024-04-25 07:23:33 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input render netdev lp admin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 4.0G 2.9G 827M 28K 296M 1.0G Swap: 104M 104M 278K Total: 4.1G 3.0G 827M 3793 M total memory 2796 M used memory 2004 M active memory 808 M inactive memory 788 M free memory 16 M buffer memory 266 M swap cache 99 M total swap 99 M used swap 0 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.6G 0 1.6G 0% /dev tmpfs tmpfs 380M 1.2M 379M 1% /run /dev/mmcblk0p2 ext4 29G 20G 8.0G 71% / tmpfs tmpfs 1.9G 8.0K 1.9G 1% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 73M 438M 15% /boot/firmware tmpfs tmpfs 380M 32K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Tue Apr 23 17:46:09 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.ena ble_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=D8:3A:DD:1A:71:9B vc_mem. mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty 1 root=PARTUUID=1e048ecb-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splas h plymouth.ignore-serial-consoles [Tue Apr 23 17:46:12 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Tue Apr 23 17:46:14 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepag e=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 11G /var/ 8.9G /var/lib 8.3G /var/lib/influxdb/engine/data/86690b2dbdd230c8/autogen 8.3G /var/lib/influxdb/engine/data/86690b2dbdd230c8 8.3G /var/lib/influxdb/engine/data Archived and active journals take up 739.9M in the file system. /opt/iobroker/backups: 217M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 303M /opt/iobroker/iobroker-data/ 191M /opt/iobroker/iobroker-data/files 57M /opt/iobroker/iobroker-data/files/javascript.admin 52M /opt/iobroker/iobroker-data/backup-objects 38M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.m ap 22M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.578d79d9.j s.map 18M /opt/iobroker/iobroker-data/objects.jsonl 8.8M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.578d79d9.j s 8.5M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4452914ae9ded11bf 33d1a5a7669f5d-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.20.2 /usr/bin/node v18.20.2 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.25.2 nodejs: Installed: 18.20.2-1nodesource1 Candidate: 18.20.2-1nodesource1 Version table: *** 18.20.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.20.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main arm64 P ackages 18.19.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 3 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admi n + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.cloud.0 : cloud : raspberrypi - enabled + system.adapter.daikin-cloud.0 : daikin-cloud : raspberrypi - enabled + system.adapter.daikin.0 : daikin : raspberrypi - enabled + system.adapter.daikin.1 : daikin : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled + system.adapter.ecovacs-deebot.0 : ecovacs-deebot : raspberrypi - enabled + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.iqontrol.0 : iqontrol : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.lg-thinq.0 : lg-thinq : raspberrypi - enabled + system.adapter.meross.0 : meross : raspberrypi - enabled + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.myenergi.0 : myenergi : raspberrypi - enabled + system.adapter.node-red.0 : node-red : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.smart-eq.0 : smart-eq : raspberrypi - enabled + system.adapter.tesla-motors.0 : tesla-motors : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admi n + system.adapter.zigbee2mqtt.0 : zigbee2mqtt : raspberrypi - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admi n + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admi n ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "backitup" : 2.11.0 , installed 2.11.0 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "daikin" : 1.4.2 , installed 1.4.2 Adapter "daikin-cloud" : 0.3.0 , installed 0.3.0 Adapter "discovery" : 4.4.0 , installed 4.4.0 Adapter "ecovacs-deebot": 1.4.15 , installed 1.4.15 Adapter "homekit-controller": 0.5.10, installed 0.5.10 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "iqontrol" : 2.3.0 , installed 2.3.0 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "lg-thinq" : 0.3.3 , installed 0.3.3 Adapter "meross" : 1.17.0 , installed 1.17.0 Adapter "modbus" : 6.1.0 , installed 6.1.0 Adapter "mqtt" : 5.2.0 , installed 5.2.0 Adapter "mqtt-client" : 1.7.0 , installed 1.7.0 Adapter "myenergi" : 0.0.3 , installed 0.0.3 Adapter "node-red" : 5.2.0 , installed 5.2.0 Adapter "openhab" : 1.1.0 , installed 1.1.0 Adapter "shelly" : 6.8.0 , installed 6.8.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "smart-eq" : 0.0.4 , installed 0.0.6 Adapter "socketio" : 6.6.1 , installed 6.6.1 Adapter "tesla-motors" : 1.3.2 , installed 1.3.2 Adapter "tuya" : 3.15.0 , installed 3.15.0 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.5.11 , installed 2.5.11 Adapter "zigbee" : 1.10.3 , installed 1.10.3 Adapter "zigbee2mqtt" : 2.13.6 , installed 2.13.6 Objects and States Please stand by - This may take a while Objects: 14991 States: 13387 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://archive.raspberrypi.com/debian bookworm InRelease Hit:4 http://deb.debian.org/debian bookworm-updates InRelease Hit:5 https://repos.influxdata.com/debian stable InRelease Hit:6 https://apt.grafana.com stable InRelease Hit:7 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:8 https://repo.homebridge.io stable 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 127.0.0.1:38691 0.0.0.0:* LISTEN 112 17194 1300/homebridge: @0 tcp 0 0 127.0.0.1:38543 0.0.0.0:* LISTEN 112 17159 1317/homebridge: ho tcp 0 0 127.0.0.1:40315 0.0.0.0:* LISTEN 112 17110 1290/homebridge: ho tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 1001 26211 1952/node-red tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 114 16746 786/mosquitto tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 19125 1561/io.shelly.0 tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 20031 1576/io.mqtt.0 tcp 0 0 127.0.0.1:46551 0.0.0.0:* LISTEN 112 21533 1634/homebridge: ho tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1000 21580 1617/node tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 16938 1082/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 17920 1082/iobroker.js-co tcp 0 0 127.0.0.1:37849 0.0.0.0:* LISTEN 112 19798 1298/homebridge: ho tcp 0 0 127.0.0.1:35727 0.0.0.0:* LISTEN 112 17154 1291/homebridge: ho tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 17543 792/sshd: /usr/sbin tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 1585299 38874/cupsd tcp 0 0 127.0.0.1:45139 0.0.0.0:* LISTEN 112 18280 1293/homebridge: ho tcp 0 0 127.0.0.1:39007 0.0.0.0:* LISTEN 112 19738 1319/homebridge: ho tcp6 0 0 :::52403 :::* LISTEN 112 19754 1298/homebridge: ho tcp6 0 0 :::44253 :::* LISTEN 112 19726 1317/homebridge: ho tcp6 0 0 :::1883 :::* LISTEN 114 16747 786/mosquitto tcp6 0 0 :::8081 :::* LISTEN 1001 19538 1140/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 21629 1690/io.web.0 tcp6 0 0 :::8086 :::* LISTEN 999 16913 892/influxd tcp6 0 0 ::1:631 :::* LISTEN 0 1585298 38874/cupsd tcp6 0 0 :::37166 :::* LISTEN 112 18883 1291/homebridge: ho tcp6 0 0 :::45391 :::* LISTEN 112 18903 1300/homebridge: @0 tcp6 0 0 :::8581 :::* LISTEN 112 17952 1058/hb-service tcp6 0 0 :::53299 :::* LISTEN 112 19213 1634/homebridge: ho tcp6 0 0 :::22 :::* LISTEN 0 17545 792/sshd: /usr/sbin tcp6 0 0 :::47961 :::* LISTEN 112 18841 1290/homebridge: ho tcp6 0 0 :::3000 :::* LISTEN 113 15360 1081/grafana tcp6 0 0 :::52120 :::* LISTEN 112 17120 1319/homebridge: ho tcp6 0 0 :::51798 :::* LISTEN 112 18821 1147/homebridge tcp6 0 0 :::39667 :::* LISTEN 112 18857 1293/homebridge: ho udp 0 0 0.0.0.0:5353 0.0.0.0:* 112 18887 1293/homebridge: ho udp 0 0 0.0.0.0:5353 0.0.0.0:* 112 17949 1058/hb-service udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 14012 549/avahi-daemon: r udp 0 0 0.0.0.0:38879 0.0.0.0:* 104 14014 549/avahi-daemon: r udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 20514 1467/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 20515 1467/io.tuya.0 udp 0 0 0.0.0.0:631 0.0.0.0:* 0 1586228 38876/cups-browsed udp6 0 0 :::5353 :::* 104 14013 549/avahi-daemon: r udp6 0 0 :::49377 :::* 104 14015 549/avahi-daemon: r udp6 0 0 fe80::81a3:20c2:583:546 :::* 0 17593 652/NetworkManager *** Log File - Last 25 Lines *** 2024-04-25 09:10:38.129 - info: tesla-motors.0 (1742) State value to set for "tesla-motors.0.XP7YGCEK0RB294491.charge_history.gas_savings.total_spent.raw_value" has to be type "number" but received type "string" 2024-04-25 09:10:38.133 - info: tesla-motors.0 (1742) State value to set for "tesla-motors.0.XP7YGCEK0RB294491.charge_history.total_spent.raw_value" has to be type "number" but received type "string" 2024-04-25 09:11:45.291 - info: influxdb.0 (47993) enabled logging of PV Tagesertrag, Alias=true 2024-04-25 09:12:30.314 - info: influxdb.0 (47993) enabled logging of BatterieGeladenTag, Alias=true 2024-04-25 09:12:50.951 - info: influxdb.0 (47993) enabled logging of BatterieEntladenTag, Alias=true 2024-04-25 09:13:25.909 - warn: influxdb.0 (47993) Error in query "from(bucket: "admin") |> range(start: 1999-12-31T23:00:00.000Z, stop: 2024-04-25T07:12:55.411Z) |> filter(fn: (r) => r["_measurement"] == "BatterieEntladung") |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value") |> group() |> sort(columns:["_time"], desc: false) |> limit(n: 500)": RequestTimedOutError: Request timed out 2024-04-25 09:14:14.696 - info: influxdb.0 (47993) enabled logging of BatterieEntladung, Alias=true 2024-04-25 09:14:23.823 - info: influxdb.0 (47993) enabled logging of BatterieProzent, Alias=true 2024-04-25 09:14:32.228 - info: influxdb.0 (47993) enabled logging of BatterieGeladenTotal, Alias=true 2024-04-25 09:14:38.869 - info: influxdb.0 (47993) enabled logging of BatterieEntladenTotal, Alias=true 2024-04-25 09:14:42.461 - info: shelly.0 (1561) [MQTT] Device with client id "shellyplus1-fcb467bf172c" connected! 2024-04-25 09:14:57.799 - info: influxdb.0 (47993) enabled logging of 0_userdata.0.Huawei.Inverter.Accumulated_Energy_Yield, Alias=false 2024-04-25 09:15:10.195 - info: influxdb.0 (47993) enabled logging of 0_userdata.0.Huawei.Inverter.Active_Power, Alias=false 2024-04-25 09:15:16.964 - info: influxdb.0 (47993) enabled logging of 0_userdata.0.Huawei.Inverter.Daily_Energy_Yield, Alias=false 2024-04-25 09:15:31.414 - info: influxdb.0 (47993) enabled logging of 0_userdata.0.Huawei.Inverter.Input_Power, Alias=false 2024-04-25 09:15:42.478 - info: influxdb.0 (47993) enabled logging of 0_userdata.0.Huawei.Inverter.Internal_Temperature, Alias=false 2024-04-25 09:18:36.103 - info: influxdb.0 (47993) enabled logging of Eigenverbrauch_Tag_Euro, Alias=true 2024-04-25 09:18:42.306 - info: influxdb.0 (47993) enabled logging of Hausspeicher_gespart, Alias=true 2024-04-25 09:18:48.544 - info: influxdb.0 (47993) enabled logging of Netzbezug_Tag_Euro, Alias=true 2024-04-25 09:19:00.758 - info: influxdb.0 (47993) enabled logging of Netzeinspeisung_Tag_Euro, Alias=true 2024-04-25 09:19:13.266 - info: influxdb.0 (47993) enabled logging of Eigenverbrauch_Tag_kWh, Alias=true 2024-04-25 09:19:20.297 - info: influxdb.0 (47993) enabled logging of 0_userdata.0.Stromverbrauch.Einspeisung_Tag_kWh, Alias=false 2024-04-25 09:19:26.029 - info: influxdb.0 (47993) enabled logging of 0_userdata.0.Stromverbrauch.Einspeisung_W, Alias=false 2024-04-25 09:19:34.118 - info: influxdb.0 (47993) enabled logging of 0_userdata.0.Stromverbrauch.Netzbezug_Tag_kWh, Alias=false 2024-04-25 09:19:43.416 - info: influxdb.0 (47993) enabled logging of 0_userdata.0.Stromverbrauch.Netzbezug_W, Alias=false============ Mark until here for C&P =============
-
Und wo ist da jetzt die Verbindung zum ioBroker?
@thomas-braun hast du zufällig noch einen Vorschlag was ich gegen den Fehler machen könnte?
-
@thomas-braun hast du zufällig noch einen Vorschlag was ich gegen den Fehler machen könnte?
@marcelinho
Nein. Mit GUIs hab ich aber auch wenig am Hut. Und mit Homebridge auch nicht. -
Hallo zusammen,
ich kann keine Plugins mehr löschen bzw. Homebridge updaten von v1.7.0 --> v1.8.0
Kann mir jemand bitte behilflich sein? Danke vorab.
Folgender Fehler:USER: homebridge
DIR: /var/lib/homebridge
CMD: npm install --save homebridge@1.8.0npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /nonexistent
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, mkdir '/nonexistent'
npm ERR! [Error: EACCES: permission denied, mkdir '/nonexistent'] {
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'mkdir',
npm ERR! path: '/nonexistent'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.npm ERR! Log files were not written due to an error writing to the directory: /nonexistent/.npm/_logs
npm ERR! You can rerun the command with--loglevel=verboseto see the logs in your terminalOperation failed with code 243.
You can download this log file for future reference.
See https://github.com/homebridge/homebridge-config-ui-x/wiki/Troubleshooting for help.habe nun folgenden Fehler:
npm ERR! code EACCES
npm ERR! syscall rename
npm ERR! path /usr/local/bin/homebridge
npm ERR! dest /usr/local/bin/.homebridge-kaN4ImAr
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, rename '/usr/local/bin/homebridge' -> '/usr/local/bin/.homebridge-kaN4ImAr'
npm ERR! [Error: EACCES: permission denied, rename '/usr/local/bin/homebridge' -> '/usr/local/bin/.homebridge-kaN4ImAr'] {
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'rename',
npm ERR! path: '/usr/local/bin/homebridge',
npm ERR! dest: '/usr/local/bin/.homebridge-kaN4ImAr'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2024-05-06T15_54_11_806Z-debug-0.log
jemand eine Idee?
-
habe nun folgenden Fehler:
npm ERR! code EACCES
npm ERR! syscall rename
npm ERR! path /usr/local/bin/homebridge
npm ERR! dest /usr/local/bin/.homebridge-kaN4ImAr
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, rename '/usr/local/bin/homebridge' -> '/usr/local/bin/.homebridge-kaN4ImAr'
npm ERR! [Error: EACCES: permission denied, rename '/usr/local/bin/homebridge' -> '/usr/local/bin/.homebridge-kaN4ImAr'] {
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'rename',
npm ERR! path: '/usr/local/bin/homebridge',
npm ERR! dest: '/usr/local/bin/.homebridge-kaN4ImAr'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2024-05-06T15_54_11_806Z-debug-0.log
jemand eine Idee?
@marcelinho sagte in Homebridge Fehler Code 243:
jemand eine Idee?
Du könntest dazu schreiben welche Aktion mit welchem User zu diesen Meldungen führt.
Und welche Berechtigungen für homebridge erforderlich sind.ls -lah /usr/local/bin/homebridge -
@marcelinho sagte in Homebridge Fehler Code 243:
jemand eine Idee?
Du könntest dazu schreiben welche Aktion mit welchem User zu diesen Meldungen führt.
Und welche Berechtigungen für homebridge erforderlich sind.ls -lah /usr/local/bin/homebridge@thomas-braun wenn ich den Befehl in der Konsole eingebe kommt folgendes:
pi@raspberrypi:~ $ ls -lah /usr/local/bin/homebridge
lrwxrwxrwx 1 root root 45 May 6 17:51 /usr/local/bin/homebridge -> ../lib/node_ modules/homebridge/bin/homebridgeich bin etwas überfragt, weis nicht genau was du meinst.
699
Online32.4k
Users81.4k
Topics1.3m
Posts