SOLVED [gelöst] Adapter lassen sich nicht Installieren!
-
nunja, etwas weiter bin ich nun aber es lässt sich nicht Insatllieren, der Key ist ungültig?
john@raspberrypi:~ $ john@raspberrypi:~ $ wget -q -O - https://apt.pivccu.de/piVCCU/public.key | sudo tee /usr/share/keyrings/pivccu.asc -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.14 (GNU/Linux) mQENBFJsL6IBCADMlaNsEi/ -- gelöscht -- -----END PGP PUBLIC KEY BLOCK----- john@raspberrypi:~ $ echo "deb [signed-by=/usr/share/keyrings/pivccu.asc] https: //apt.pivccu.de/piVCCU stable main" | sudo tee /etc/apt/sources.list.d/pivccu.li st sudo apt update deb [signed-by=/usr/share/keyrings/pivccu.asc] https://apt.pivccu.de/piVCCU stab le main Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 http://deb.debian.org/debian bookworm-updates InRelease Get:5 https://apt.pivccu.de/piVCCU stable InRelease [13.6 kB] Get:6 https://apt.debmatic.de/debmatic stable InRelease [13.6 kB] Get:7 https://apt.pivccu.de/piVCCU stable/main arm64 Packages [14.0 kB] Get:8 https://apt.pivccu.de/piVCCU stable/main armhf Packages [14.2 kB] Err:6 https://apt.debmatic.de/debmatic stable InRelease The following signatures couldn't be verified because the public key is not av ailable: NO_PUBKEY 541230BA05C38BC4 Reading package lists... Done W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following s ignatures couldn't be verified because the public key is not available: NO_PUBKE john@raspberrypi:~ $ manpage for repository creation and user configuration deta -bash: john@raspberrypi:~: command not found -bash: -----BEGIN: command not found -bash: syntax error near unexpected token `(' -bash: G E L Ö S C H T Fm: No such file or directory - 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 Get:5 https://apt.pivccu.de/piVCCU stable InRelease [13.6 kB] Get:6 https://apt.debmatic.de/debmatic stable InRelease [13.6 kB] Err:5 https://apt.pivccu.de/piVCCU stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 Err:6 https://apt.debmatic.de/debmatic stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 Reading package lists... Done N: Ignoring file 'pivccu.li' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.pivccu.de/piVCCU stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.MOD-EDIT: Code in code-tags gesetzt und Key gelöscht!
MFG Schweizer
-
@schweiz sagte in Adapter lassen sich nicht Installieren!:
wie kann ich es unkompliziert Updaten?
gar nicht!
nimm eine neue Karte, installier darauf das aktuelle OS lite,
Anschließend piVCCU nach der Schritt für Schritt Anleitung von Alex Reinert
dann iobroker per Einzeilerfertig!
für den unwahrscheinlichen Notfall hast du noch deine alte Installation
-
ich bin mal einfach weiter gegangen in der Install
john@raspberrypi:~ $ sudo apt install build-essential bison flex libssl-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done build-essential is already the newest version (12.9). bison is already the newest version (2:3.8.2+dfsg-1+b1). flex is already the newest version (2.6.4-8.2). libssl-dev is already the newest version (3.0.11-1~deb12u2+rpt1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. N: Ignoring file 'pivccu.li' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension john@raspberrypi:~ $ sudo apt install raspberrypi-kernel-headers pivccu-modules-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: dkms Suggested packages: menu The following NEW packages will be installed: dkms pivccu-modules-dkms raspberrypi-kernel-headers 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 10.3 MB of archives. After this operation, 65.0 MB of additional disk space will be used. N: Ignoring file 'pivccu.li' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension Do you want to continue? [Y/n] y Get:1 http://deb.debian.org/debian bookworm/main arm64 dkms all 3.0.10-8+deb12u1 [48.7 kB] Get:2 http://archive.raspberrypi.com/debian bookworm/main arm64 raspberrypi-kernel-headers arm64 1:1.20230405-1 [10.2 MB] Get:3 https://apt.pivccu.de/piVCCU stable/main arm64 pivccu-modules-dkms all 1.0.84 [43.1 kB] Fetched 10.3 MB in 4s (2,853 kB/s) N: Ignoring file 'pivccu.li' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension Preconfiguring packages ... Selecting previously unselected package dkms. (Reading database ... 55552 files and directories currently installed.) Preparing to unpack .../dkms_3.0.10-8+deb12u1_all.deb ... Unpacking dkms (3.0.10-8+deb12u1) ... Setting up dkms (3.0.10-8+deb12u1) ... Selecting previously unselected package pivccu-modules-dkms. (Reading database ... 55576 files and directories currently installed.) Preparing to unpack .../pivccu-modules-dkms_1.0.84_all.deb ... Unpacking pivccu-modules-dkms (1.0.84) ... Selecting previously unselected package raspberrypi-kernel-headers. Preparing to unpack .../raspberrypi-kernel-headers_1%3a1.20230405-1_arm64.deb ... Unpacking raspberrypi-kernel-headers (1:1.20230405-1) ... Setting up raspberrypi-kernel-headers (1:1.20230405-1) ... run-parts: executing /etc/kernel/header_postinst.d/dkms 6.1.21+ dkms: autoinstall for kernel 6.1.21+ was skipped since the kernel headers for this kernel do not seem to be installed. run-parts: executing /etc/kernel/header_postinst.d/dkms 6.1.21-v7+ dkms: autoinstall for kernel 6.1.21-v7+ was skipped since the kernel headers for this kernel do not seem to be installed. run-parts: executing /etc/kernel/header_postinst.d/dkms 6.1.21-v7l+ dkms: autoinstall for kernel 6.1.21-v7l+ was skipped since the kernel headers for this kernel do not seem to be installed. run-parts: executing /etc/kernel/header_postinst.d/dkms 6.1.21-v8+ dkms: running auto installation service for kernel 6.1.21-v8+. dkms: autoinstall for kernel: 6.1.21-v8+. Setting up pivccu-modules-dkms (1.0.84) ... Ensure non mixed processor architecure ... Done Create kernel modules ... Done Enable DKMS service ... Done Processing triggers for man-db (2.11.2-2) ...mal einen neustart machen...
MFG Schweizer
-
@schweiz sagte in Adapter lassen sich nicht Installieren!:
ich bin mal einfach weiter gegangen in der Install
warum?
was war da mit dem Key?
ich hatte mal keine Zeit!
@schweiz sagte in Adapter lassen sich nicht Installieren!:
mal einen neustart machen...
warum?
der ist noch nicht fertigimmer warten bis der Prompt wieder erscheint!
hast du anscheinend auch ganz oben nicht gemacht.
und zieh mal das putty Fenster größer damit die Zeilen vollständig sind
das debmatic repo spukt da auch noch rum.Mach am besten alles komplett neu.
und dann Zeile für Zeile abarbeiten bis der Prompt kommt, dann erst weitermachen.Was für ein Pi ist das denn?
-
RP4
musste noch Node installieren, IOBroker läuft nun, nur lässt sich immernoch kein Adapter installieren...
Das fenster geht auf, es steht
$ iobroker add alexa2 --host raspberrypiNPM version: 10.2.3
Installing iobroker.alexa2@3.26.3... (System call)
npm ERR! code ETIMEDOUTnpm ERR! syscall connectnpm ERR! errno ETIMEDOUTnpm ERR! network request to https://registry.npmjs.org/iobroker.alexa2 failed, reason: connect ETIMEDOUT 2606:4700::6810:1e22:443npm ERR! network This is a problem related to network connectivity.npm ERR! network In most cases you are behind a proxy or have bad network settings.npm ERR! network npm ERR! network If you are behind a proxy, please make sure that thenpm ERR! network 'proxy' config is set properly. See: 'npm help config'npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-12-26T18_25_44_393Z-debug-0.log
host.raspberrypi Cannot install iobroker.alexa2@3.26.3: 1
ERROR: Process exited with code 25
oben läuft die blaue Leiste, 10 min... so lange hat es nie gedauert dann bricht es mit dem fehler oben ab...
MFG Schweizer
-
@schweiz sagte in Adapter lassen sich nicht Installieren!:
musste noch Node installieren,
doch nicht für piVCCU!
und für iobroker passiert das mit dem Installer.bitte das aktuelle iob diag full
EDIT:
Nie nicht niemals nachträglich posts verändern ohne es zu markieren! -
@schweiz sagte in Adapter lassen sich nicht Installieren!:
This is a problem related to network connectivity
das passt auch zu deinen piVCCU Problemen
-
CCU geht, und das alte Backup ist drin, Geräte laufen...
Copy text starting here:
======================= SUMMARY ======================= v.2023-10-10 Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi7-rpi-v8 Architecture: arm64 Installation: native Kernel: aarch64 Userland: arm64 Timezone: Europe/London (GMT, +0000) User-ID: 1000 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 ^C ok, sorry mit dem Edit... iob diag das grosse log kann ich nicht kopieren, weil unten steh weiter mit einer Taste, sobald ich kopieren will geht es weiter... :( MFG Schweizer -
======== 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.1 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 18:49:52 up 39 min, 2 users, load average: 0.72, 0.48, 0.38 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Tue 2023-12-26 18:49:52 GMT Universal time: Tue 2023-12-26 18:49:52 UTC RTC time: n/a Time zone: Europe/London (GMT, +0000) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** john /home/john john adm dialout cdrom sudo audio video plugdev games users input render netdev 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 819M 2.1G 1.3M 1.1G 3.2G Swap: 104M 0B 104M Total: 4.1G 819M 2.2G 3793 M total memory 781 M used memory 840 M active memory 746 M inactive memory 2018 M free memory 64 M buffer memory 1005 M swap cache 99 M total swap 0 M used swap 99 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 3.3G 25G 12% / tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 62M 449M 13% /boot/firmware tmpfs tmpfs 380M 0 380M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Tue Dec 26 18:10:21 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:29:88:49 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=fed7638c-02 rootfstype=ext4 fsck.repair=yes rootwait [Tue Dec 26 18:10:23 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Tue Dec 26 18:10:25 2023] 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,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.2G /var/ 826M /var/lib 661M /var/lib/piVCCU3 604M /var/lib/piVCCU3/rootfs 279M /var/lib/piVCCU3/rootfs/opt Archived and active journals take up 64.0M in the file system. /opt/iobroker/backups: 4.0K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 19M /opt/iobroker/iobroker-data/ 15M /opt/iobroker/iobroker-data/files 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static 13M /opt/iobroker/iobroker-data/files/admin.admin/custom The five largest files in iobroker-data are: 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map 4.0M /opt/iobroker/iobroker-data/objects.jsonl 2.8M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js 1.6M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map 652K /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0-1nodesource1 Version table: *** 18.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 500 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 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 500 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.17 admin: 6.12.0 javascript: "javascript" not found Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.discovery.0 : discovery : 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: admin 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.12.0 , installed 6.12.0 Adapter "backitup" : 2.9.8 , installed 2.9.8 Adapter "discovery" : 4.2.0 , installed 4.2.0 Controller "js-controller": 5.0.17 , installed 5.0.17 Objects and States Please stand by - This may take a while Objects: 143 States: 106 *** OS-Repositories and Updates *** W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 14969 968/sshd: /usr/sbin tcp 0 0 10.0.3.1:53 0.0.0.0:* LISTEN 0 16511 1039/dnsmasq tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 41119 9275/iobroker.js-co tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 41112 9275/iobroker.js-co tcp6 0 0 :::22 :::* LISTEN 0 14971 968/sshd: /usr/sbin tcp6 0 0 :::8081 :::* LISTEN 1001 43792 9754/io.admin.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 14782 534/avahi-daemon: r udp 0 0 0.0.0.0:38951 0.0.0.0:* 104 14784 534/avahi-daemon: r udp 0 0 10.0.3.1:53 0.0.0.0:* 0 16510 1039/dnsmasq udp 0 0 0.0.0.0:67 0.0.0.0:* 0 16507 1039/dnsmasq udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14924 889/dhclient udp6 0 0 :::5353 :::* 104 14783 534/avahi-daemon: r udp6 0 0 :::34621 :::* 104 14785 534/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-12-26 18:20:30.854 - info: admin.0 (9754) received all objects 2023-12-26 18:20:30.937 - warn: admin.0 (9754) Repository cannot be read: Active repo - stable 2023-12-26 18:20:30.939 - warn: admin.0 (9754) Active repository "stable" cannot be read 2023-12-26 18:20:31.082 - info: admin.0 (9754) socket.io server listening on port 8081 2023-12-26 18:20:31.087 - info: admin.0 (9754) http server listening on port 8081 2023-12-26 18:20:31.087 - info: admin.0 (9754) Use link "http://127.0.0.1:8081" to configure. 2023-12-26 18:20:31.350 - info: admin.0 (9754) failed connection to socket.io from ::ffff:192.168.2.116: Passport was not initialized 2023-12-26 18:20:31.782 - info: admin.0 (9754) failed connection to socket.io from ::ffff:192.168.2.116: Passport was not initialized 2023-12-26 18:20:48.435 - info: admin.0 (9754) ==> Connected system.user.admin from ::ffff:192.168.2.116 2023-12-26 18:20:48.914 - info: host.raspberrypi Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-12-26 18:21:13.453 - info: admin.0 (9754) <== Disconnect system.user.admin from ::ffff:192.168.2.116 admin 2023-12-26 18:21:49.280 - info: admin.0 (9754) ==> Connected system.user.admin from ::ffff:192.168.2.116 2023-12-26 18:21:58.099 - info: admin.0 (9754) <== Disconnect system.user.admin from ::ffff:192.168.2.116 admin 2023-12-26 18:22:15.352 - info: admin.0 (9754) ==> Connected system.user.admin from ::ffff:192.168.2.116 2023-12-26 18:22:15.648 - info: admin.0 (9754) <== Disconnect system.user.admin from ::ffff:192.168.2.116 admin 2023-12-26 18:22:21.951 - info: admin.0 (9754) ==> Connected system.user.admin from ::ffff:192.168.2.116 2023-12-26 18:25:39.843 - info: host.raspberrypi iobroker add alexa2 --host raspberrypi 2023-12-26 18:25:43.464 - info: host.raspberrypi iobroker NPM version: 10.2.3 2023-12-26 18:25:43.466 - info: host.raspberrypi iobroker Installing iobroker.alexa2@3.26.3... (System call) 2023-12-26 18:33:27.397 - error: host.raspberrypi iobroker npm ERR! code ETIMEDOUTnpm ERR! syscall connectnpm ERR! errno ETIMEDOUTnpm ERR! network request to https://registry.npmjs.org/iobroker.alexa2 failed, reason: connect ETIMEDOUT 2606:4700::6810:1e22:443npm ERR! network This is a problem related to network connectivity.npm ERR! network In most cases you are behind a proxy or have bad network settings.npm ERR! network npm ERR! network If you are behind a proxy, please make sure that thenpm ERR! network 'proxy' config is set properly. See: 'npm help config'npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-12-26T18_25_44_393Z-debug-0.log 2023-12-26 18:33:27.402 - error: host.raspberrypi iobroker host.raspberrypi Cannot install iobroker.alexa2@3.26.3: 1 2023-12-26 18:33:28.436 - info: host.raspberrypi iobroker exit 25 2023-12-26 18:45:27.826 - info: host.raspberrypi iobroker add hm-rega --host raspberrypi 2023-12-26 18:45:31.546 - info: host.raspberrypi iobroker NPM version: 10.2.3 2023-12-26 18:45:31.549 - info: host.raspberrypi iobroker Installing iobroker.hm-rega@4.0.0... (System call)============ Mark until here for C&P =============
iob diag has finished.
-
@schweiz sagte in Adapter lassen sich nicht Installieren!:
*** OS-Repositories and Updates ***
da ist das unsignierte debmatic und kein piVCCU repo!
sonst nichts aufregendes bis auf die Probleme mit dem Zugriff auf npm
könnte ein kurzzeitiges Problem mit deren Server sein, muss aber nicht.später nochmal versuchen, ggf. über due Konsole mit
iob add alexa2 --debug -
@homoran
hmmm, ok soweit läuft ja CCU und IOBm beides über eigene IP, nur das ich im IOB nix hinzufügen kann...Ich schau mal morgen nochmal rein, hab heute auch nicht mehr die lust, sitze schon so lange an der Kiste und gefühlt geht nix...
Erst einmal Herzlichen Dank für die Geduld mit mir und die erbrachte Hilfe
iob add alexa2 --debug geht auf Console auch nicht voran...iob add alexa2 --debug NPM version: 10.2.3 Installing iobroker.alexa2@3.26.3... (System call) npm ERR! code ETIMEDOUT npm ERR! syscall connect npm ERR! errno ETIMEDOUT npm ERR! network request to https://registry.npmjs.org/iobroker.alexa2 failed, reason: connect ETIMEDOUT 2606:4700::6810:1e22:443 npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-12-26T18_58_23_191Z-debug-0.log npm ERR! code ETIMEDOUT npm ERR! syscall connect npm ERR! errno ETIMEDOUT npm ERR! network request to https://registry.npmjs.org/iobroker.alexa2 failed, reason: connect ETIMEDOUT 2606:4700::6810:1e22:443 npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-12-26T18_58_23_191Z-debug-0.log host.raspberrypi Cannot install iobroker.alexa2@3.26.3: 1MFG Schweizer
-
john@raspberrypi:/opt/iobroker $ iobroker fix library: loaded Library version=2023-10-13 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2023-10-13 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== 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://deb.nodesource.com/node_18.x nodistro InRelease Get:6 https://apt.pivccu.de/piVCCU stable InRelease [13.6 kB] Get:7 https://apt.debmatic.de/debmatic stable InRelease [13.6 kB] Err:7 https://apt.debmatic.de/debmatic stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 Reading package lists... Done N: Ignoring file 'pivccu.li' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed acl W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed libavahi-compat-libdnssd-dev W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed libudev-dev W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed libpam0g-dev W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed git W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed libcairo2-dev W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed libpango1.0-dev W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed libjpeg-dev W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed libgif-dev W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed librsvg2-dev W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed libpixman-1-dev W: GPG error: https://apt.debmatic.de/debmatic stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 541230BA05C38BC4 E: The repository 'https://apt.debmatic.de/debmatic stable InRelease' is not signed. Installed cmake ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... This system does not support setting default permissions. Do not use npm to manually install adapters unless you know what you are doing! ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! npm ERR! code ETIMEDOUT npm ERR! syscall connect npm ERR! errno ETIMEDOUT npm ERR! network request to https://registry.npmjs.org/@iobroker%2fjsonltool failed, reason: connect ETIMEDOUT 2606:4700::6810:1e22:443 npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-12-26T19_12_31_342Z-debug-0.log ========================================================================== Checking autostart (5/5) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================das ist aus IOB FIX, kann aber im npm help config nix finden bzgl. der Netzwerk Konfig...
MFG Schweizer
-
@schweiz du hast probleme mit dem Internet.
Möglicherweise mit IPv6 -
-
-
Dann ändere es auf die korrekte Zeitzone ab.
Spart dir Rückfragen, warum irgendwas zur falschen Zeit ausgeführt wird. Und Trouble im Netzwerk auch. -
super, ich DANKE EUCH BEIDEN...
die Uhrzeit hat er mir nach der konfig richtig angezeigt, und nun scheint es zu gehen...
MFG Schweizer
-
@schweiz dann musst du jetzt nur noch dein piVCCU repo anlegen und dafür das debmatic repo wieder loswerden.
Vielleicht kann dir @Thomas-Braun dabei unter die Arme greifen. ich kann so was nicht.
-
-
Erst einmal ein Frohes neues Jahre euch allen...
john@raspberrypi:~ $ ls -lAh /etc/apt/sources.list.d/
total 16K
-rw-r--r-- 1 root root 94 Dec 26 17:55 debmatic.list
-rw-r--r-- 1 root root 100 Dec 26 18:30 nodesource.list
-rw-r--r-- 1 root root 0 Dec 26 17:32 pivccu.li
-rw-r--r-- 1 root root 88 Dec 26 17:55 pivccu.list
-rw-r--r-- 1 root root 191 Dec 26 17:55 raspi.listSo nachdem PIVCCU so halbwegs läuft komme ich im IOB nicht weiter...
Die Homematic Adapter haben sich installieren lassen, nun wollte ich JS Installieren, aber leider scheint es ein problem mit der Source zu geben...Invalid request getRepository. "callback"(false) or "from"(true) is null
iobroker host.raspberrypi Cannot install iobroker.javascript@7.1.6: 1
iobroker npm ERR! code ETIMEDOUTnpm ERR! syscall connectnpm ERR! errno ETIMEDOUTnpm ERR! network request to https://registry.npmjs.org/iobroker.javascript failed, reason: connect ETIMEDOUT 2606:4700::6810:323:443npm ERR! network This is a problem related to network connectivity.npm ERR! network In most cases you are behind a proxy or have bad network settings.npm ERR! network npm ERR! network If you are behind a proxy, please make sure that thenpm ERR! network 'proxy' config is set properly. See: 'npm help config'npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-01-01T12_15_26_104Z-debug-0.logMFG
-
sudo rm /etc/apt/sources.list.d/debmatic.list sudo rm /etc/apt/sources.list.d/pivccu.li sudo apt update
