@eisbaeeer
Ich finde das ein sehr schönes Projekt. Woher hast du das Gehäuse? Und da müsste ja dann eigentlich noch Platz für einen Voc Sensor sein, oder?
Best posts made by pseudoreal
-
RE: CO2 Ampel mit MQTT und ESP8266posted in Hardware
Latest posts made by pseudoreal
-
RE: iobroker.admin.0 lässt sich nicht aktivierenposted in ioBroker Allgemein
@Glasfaser
habe jetzt die Beta installiert und auch die Befehle aus dem Thread hier wiederholt. Leider lässt sich die Admin Instanz immer noch nicht aktivieren.
Ich habe mal iobroker via SSH komplett neu aufgesetzt, da funktionierte dann die weboberfläche. Ich vermute mal, dass irgendeine Datei zerschossen ist.sehe gerade in dem beta container eine neue Fehlermeldung
2023/12/22 12:53:53 stdout } 2023/12/22 12:53:53 stdout port: 42010 2023/12/22 12:53:53 stdout address: '192.168.178.52', 2023/12/22 12:53:53 stdout syscall: 'listen', 2023/12/22 12:53:53 stdout errno: -99, 2023/12/22 12:53:53 stdout code: 'EADDRNOTAVAIL', 2023/12/22 12:53:53 stdout at processTicksAndRejections (node:internal/process/task_queues:83:21) { 2023/12/22 12:53:53 stdout at doListen (node:net:2014:7) 2023/12/22 12:53:53 stdout at listenInCluster (node:net:1865:12) 2023/12/22 12:53:53 stdout at Server.setupListenHandle [as _listen2] (node:net:1800:21) 2023/12/22 12:53:53 stdout Error: listen EADDRNOTAVAIL: address not available 192.168.178.52:42010 2023/12/22 12:53:21 stdoutEdit: habe jetzt einen neuen Container mit latest erzeugt und einen neuen Pfad hergestellt. Backup vom Novmeber konnte ich einspielen. Interessanterweise vom Dezember nicht (hatte 3 und 12.12 getestet). Da ist der Restore-vorgang abgebrochen.
-
RE: iobroker.admin.0 lässt sich nicht aktivierenposted in ioBroker Allgemein
hmm ich frage mich eher, was dazu geführt hat, dass es zerschossen ist?!
Ich versuche morgen mal die beta...
-
RE: iobroker.admin.0 lässt sich nicht aktivierenposted in ioBroker Allgemein
das geht nicht:
The execution of this command is blocked as your ioBroker is running inside a Doc ker container! For more details see ioBroker Docker image docs (https://docs.buanet.de/iobroker- docker-image/docs/) or use the maintenance script 'maintenance --help'.
-
RE: iobroker.admin.0 lässt sich nicht aktivierenposted in ioBroker Allgemein
status
root@iobroker:/opt/iobroker# iobroker status iobroker is running on this host. Objects type: jsonl States type: jsonldiag
Skript v.2023-10-10 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : amd64 Docker : v9.0.1 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 23:32:02 up 11:12, 0 user, load average: 3.03, 4.81, 5.30 CPU threads: 2 *** Time and Time Zones *** Thu Dec 21 22:32:02 UTC 2023 Thu Dec 21 23:32:02 CET 2023 CET +0100 Etc/UTC *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 18G 3.9G 285M 646M 15G 14G Swap: 13G 70M 13G Total: 32G 3.9G 13G 17836 M total memory 3700 M used memory 7854 M active memory 8766 M inactive memory 272 M free memory 49 M buffer memory 14766 M swap cache 12749 M total swap 66 M used swap 12683 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/md2 btrfs 3.5T 1.8T 1.8T 51% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 8.8G 0 8.8G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/md2 btrfs 3.5T 1.8T 1.8T 51% /opt/iobroker /dev/md2 btrfs 3.5T 1.8T 1.8T 51% /etc/hosts tmpfs tmpfs 8.8G 0 8.8G 0% /proc/acpi tmpfs tmpfs 8.8G 0 8.8G 0% /proc/scsi tmpfs tmpfs 8.8G 0 8.8G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: sudo: unable to resolve host iobroker: Name or service not known Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/md2[/@syno/@docker/btrfs/subvolumes/769fca532000df7bd06a6 b2495878a45410548fa1233ac9d0718b1a3aabf31d4] btrfs rw,nodev,relatime,ssd,s ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli d=2143,subvol=/@syno/@docker/btrfs/subvolumes/769fca532000df7bd06a6b2495878a45410 548fa1233ac9d0718b1a3aabf31d4 |-/opt/iobroker /dev/md2[/@syno/docker/iobroker] btrfs rw,nodev,relatime,ssd,s ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli d=260,subvol=/@syno/docker |-/etc/resolv.conf /dev/md2[/@syno/@docker/containers/bff6048aa927721b34e64ac2831 6ab5dd0572f9b10fecd32a7151e936c569f30/resolv.conf] btrfs rw,nodev,relatime,ssd,s ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli d=257,subvol=/@syno |-/etc/hostname /dev/md2[/@syno/@docker/containers/bff6048aa927721b34e64ac2831 6ab5dd0572f9b10fecd32a7151e936c569f30/hostname] btrfs rw,nodev,relatime,ssd,s ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli d=257,subvol=/@syno `-/etc/hosts /dev/md2[/@syno/@docker/containers/bff6048aa927721b34e64ac2831 6ab5dd0572f9b10fecd32a7151e936c569f30/hosts] btrfs rw,nodev,relatime,ssd,s ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli d=257,subvol=/@syno Files in neuralgic directories: /var: sudo: unable to resolve host iobroker: Name or service not known 34M /var/ 32M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 13M /var/lib/dpkg /opt/iobroker/backups: 522M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 428M /opt/iobroker/iobroker-data/ 226M /opt/iobroker/iobroker-data/files 142M /opt/iobroker/iobroker-data/backup-objects 67M /opt/iobroker/iobroker-data/files/javascript.admin 48M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 33M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.ma p 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.ma p 20M /opt/iobroker/iobroker-data/objects.jsonl 16M /opt/iobroker/iobroker-data/states.jsonl 12M /opt/iobroker/iobroker-data/objects.json.migrated 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 amd64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 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: 7.1.6 Adapters from github: 0 Adapter State system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : iobroker - enabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.cloud.0 : cloud : iobroker - enabled + system.adapter.discovery.0 : discovery : iobroker - enabled system.adapter.ecovacs-deebot.0 : ecovacs-deebot : iobroker - disabled system.adapter.flot.0 : flot : iobroker - enabled + system.adapter.gruenbeck.0 : gruenbeck : iobroker - enabled + system.adapter.hm-rega.0 : hm-rega : iobroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.info.0 : info : iobroker - enabled + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled system.adapter.mqtt-client.0 : mqtt-client : iobroker - disabled, port: 1883 + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 192.168.178.52 system.adapter.openweathermap.0 : openweathermap : iobroker - enabled + system.adapter.panasonic-comfort-cloud.0: panasonic-comfort-cloud: iobroker - enabled + system.adapter.ping.0 : ping : iobroker - enabled + system.adapter.scenes.0 : scenes : iobroker - enabled + system.adapter.smartcontrol.0 : smartcontrol : iobroker - enabled + system.adapter.sony-bravia.0 : sony-bravia : iobroker - enabled + system.adapter.sql.0 : sql : iobroker - enabled, port: 3307 + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.terminal.0 : terminal : iobroker - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.vesync.0 : vesync : iobroker - enabled system.adapter.vis.0 : vis : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 192.168.178.52, run as: admin + system.adapter.whatsapp-cmb.0 : whatsapp-cmb : iobroker - enabled + system.adapter.zigbee.0 : zigbee : iobroker - enabled, port: tcp://192.168.178.5:6638 + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 192.168.178.52 + system.adapter.sql.0 : sql : iobroker - enabled, port: 3307 + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.terminal.0 : terminal : iobroker - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 192.168.178.52, run as: admin + system.adapter.zigbee.0 : zigbee : iobroker - enabled, port: tcp://192.168.178.5:6638 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json pana : https://github.com/marc2016/ioBroker.panasonic-comfort-cloud Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.12.0 , installed 6.12.0 Adapter "alexa2" : 3.26.3 , installed 3.26.3 Adapter "backitup" : 2.8.7 , installed 2.8.7 Adapter "cloud" : 4.4.1 , installed 4.4.1 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "ecovacs-deebot": 1.4.13 , installed 1.4.13 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "gruenbeck" : 0.0.42 , installed 0.0.42 Adapter "hm-rega" : 4.0.0 , installed 4.0.0 Adapter "hm-rpc" : 1.15.19 , installed 1.15.19 Adapter "info" : 2.0.0 , installed 2.0.0 Adapter "iot" : 2.0.11 , installed 2.0.11 Adapter "javascript" : 7.1.6 , installed 7.1.6 Controller "js-controller": 5.0.17 , installed 5.0.17 Adapter "mqtt" : 5.1.0 , installed 5.1.0 Adapter "mqtt-client" : 1.7.0 , installed 1.7.0 Adapter "openweathermap": 0.4.5 , installed 0.4.5 Adapter "panasonic-comfort-cloud": 2.2.4, installed 2.2.4 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "scenes" : 2.3.9 , installed 2.3.9 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "smartcontrol" : 2.0.1 , installed 2.0.1 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "sony-bravia" : 1.0.9 , installed 1.0.9 Adapter "sql" : 2.2.0 , installed 2.2.0 Adapter "telegram" : 3.0.0 , installed 3.0.0 Adapter "terminal" : 1.0.0 , installed 1.0.0 Adapter "vesync" : 0.0.3 , installed 0.0.3 Adapter "vis" : 1.5.4 , installed 1.5.4 Adapter "vis-hqwidgets": 1.4.0 , installed 1.4.0 Adapter "weatherunderground": 3.6.0, installed 3.6.0 Adapter "web" : 6.1.10 , installed 6.1.10 Adapter "whatsapp-cmb" : 0.2.3 , installed 0.2.3 Adapter "ws" : 2.5.8 , installed 2.5.8 Adapter "zigbee" : 1.8.24 , installed 1.8.24 Objects and States Please stand by - This may take a while Objects: 11169 States: 9270 *** OS-Repositories and Updates *** sudo: unable to resolve host iobroker: Name or service not known sudo: unable to resolve host iobroker: Name or service not known Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** sudo: unable to resolve host iobroker: Name or service not known 3482043 - Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State U ser Inode PID/Program name tcp 0 0 192.168.178.52:42010 0.0.0.0:* LISTEN 1 000 4662589 - tcp 0 0 192.168.178.52:1883 0.0.0.0:* LISTEN 1 000 4665719 - tcp 0 0 0.0.0.0:6011 0.0.0.0:* LISTEN 2 54178 119443 - tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 48335 - tcp 0 0 0.0.0.0:6012 0.0.0.0:* LISTEN 2 54178 120432 - tcp 0 0 0.0.0.0:892 0.0.0.0:* LISTEN 0 27010 - tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 56007 - tcp 0 0 127.0.0.1:512 0.0.0.0:* LISTEN 0 128944 - tcp 0 0 127.0.0.1:161 0.0.0.0:* LISTEN 0 67992 - tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN 0 41443 - tcp 0 0 0.0.0.0:6690 0.0.0.0:* LISTEN 0 161086 - tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1 000 4657587 - tcp 0 0 192.168.178.52:49160 0.0.0.0:* LISTEN 0 124425 - tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 0 48329 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1 000 4657541 - tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN 0 48331 - tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 0 3480800 - tcp 0 0 0.0.0.0:3307 0.0.0.0:* LISTEN 6 6 103720 - tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 0 56008 - tcp 0 0 0.0.0.0:5357 0.0.0.0:* LISTEN 0 56614 - tcp 0 0 0.0.0.0:4045 0.0.0.0:* LISTEN 0 41466 - tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 22626 - tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 48333 - tcp 0 0 192.168.178.52:50001 0.0.0.0:* LISTEN 0 121254 - tcp 0 0 192.168.178.52:8082 0.0.0.0:* LISTEN 1 000 4670898 - tcp 0 0 0.0.0.0:5010 0.0.0.0:* LISTEN 0 3482369 - tcp 0 0 0.0.0.0:50002 0.0.0.0:* LISTEN 0 121541 - tcp 0 0 192.168.178.52:49170 0.0.0.0:* LISTEN 2 54178 119223 - tcp 0 0 127.0.0.1:915 0.0.0.0:* LISTEN 0 108377 - tcp 0 0 0.0.0.0:662 0.0.0.0:* LISTEN 0 27879 - tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 24612 - tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN 0 tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 0 3479802 - tcp 0 0 127.0.0.1:33304 0.0.0.0:* LISTEN 0 183457 - tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 5 5 102861 - tcp 0 0 127.0.0.1:18617 0.0.0.0:* LISTEN 0 124469 - tcp6 0 0 :::443 :::* LISTEN 0 48336 - tcp6 0 0 :::892 :::* LISTEN 0 27016 - tcp6 0 0 :::3261 :::* LISTEN 0 70512 - tcp6 0 0 :::445 :::* LISTEN 0 56005 - tcp6 0 0 :::5566 :::* LISTEN 0 95836 - tcp6 0 0 :::3263 :::* LISTEN 0 70510 - tcp6 0 0 :::3264 :::* LISTEN 0 70514 - tcp6 0 0 :::3265 :::* LISTEN 0 71938 - tcp6 0 0 :::2049 :::* LISTEN 0 41456 - tcp6 0 0 :::6690 :::* LISTEN 0 161087 - tcp6 0 0 :::5000 :::* LISTEN 0 48330 - tcp6 0 0 :::5001 :::* LISTEN 0 48332 - tcp6 0 0 :::3306 :::* LISTEN 0 3480805 - tcp6 0 0 :::139 :::* LISTEN 0 56006 - tcp6 0 0 :::5357 :::* LISTEN 0 56615 - tcp6 0 0 :::4045 :::* LISTEN 0 41468 - tcp6 0 0 :::111 :::* LISTEN 0 22629 - tcp6 0 0 :::80 :::* LISTEN 0 48334 - tcp6 0 0 :::5010 :::* LISTEN 0 3482374 - tcp6 0 0 :::662 :::* LISTEN 0 27883 - tcp6 0 0 :::22 :::* LISTEN 0 24614 - tcp6 0 0 :::8088 :::* LISTEN 1 000 4671410 - tcp6 0 0 :::3000 :::* LISTEN 0 3482048 - tcp6 0 0 :::8888 :::* LISTEN 0 3479807 - udp 0 0 0.0.0.0:9997 0.0.0.0:* 0 23392 - udp 0 0 0.0.0.0:9998 0.0.0.0:* 0 23391 - udp 0 0 0.0.0.0:9999 0.0.0.0:* 0 23390 - udp 0 0 127.0.0.1:59233 0.0.0.0:* 0 121255 - udp 0 0 0.0.0.0:43647 0.0.0.0:* 0 182180 - udp 0 0 0.0.0.0:47990 0.0.0.0:* 0 2993018 - udp 0 0 0.0.0.0:64921 0.0.0.0:* 0 22625 - udp 0 0 127.0.0.1:48677 0.0.0.0:* 0 124426 - udp 0 0 0.0.0.0:68 0.0.0.0:* 0 23331 - udp 0 0 0.0.0.0:68 0.0.0.0:* 0 23828 - udp 0 0 0.0.0.0:111 0.0.0.0:* 0 21135 - udp 0 0 192.168.178.255:137 0.0.0.0:* 0 2993100 - udp 0 0 192.168.178.52:137 0.0.0.0:* 0 2993099 - udp 0 0 0.0.0.0:137 0.0.0.0:* 0 2993064 - udp 0 0 192.168.178.255:138 0.0.0.0:* 0 2993102 - udp 0 0 192.168.178.52:138 0.0.0.0:* 0 2993101 - udp 0 0 0.0.0.0:138 0.0.0.0:* 0 2993065 - udp 0 0 127.0.0.1:161 0.0.0.0:* 0 67991 - udp 0 0 0.0.0.0:662 0.0.0.0:* 0 27877 - udp 0 0 127.0.0.1:676 0.0.0.0:* 0 27170 - udp 0 0 0.0.0.0:892 0.0.0.0:* 0 27007 - udp 0 0 127.0.0.1:33734 0.0.0.0:* 2 54178 119224 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 0 124428 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 0 121257 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 2 54178 119226 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 0 48805 - udp 0 0 0.0.0.0:2049 0.0.0.0:* 0 41455 - udp 0 0 0.0.0.0:3702 0.0.0.0:* 9 9 55753 - udp 0 0 0.0.0.0:4045 0.0.0.0:* 0 41465 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 0 2993016 - udp 0 0 192.168.178.52:55900 0.0.0.0:* 2 54178 119225 - udp 0 0 192.168.178.52:55901 0.0.0.0:* 0 121256 - udp 0 0 192.168.178.52:55902 0.0.0.0:* 0 124427 - udp6 0 0 :::111 :::* 0 22627 - udp6 0 0 :::662 :::* 0 27881 - udp6 0 0 :::892 :::* 0 27013 - udp6 0 0 :::2049 :::* 0 41457 - udp6 0 0 :::36027 :::* 0 2993019 - udp6 0 0 :::3702 :::* 9 9 55755 - udp6 0 0 :::4045 :::* 0 41467 - udp6 0 0 :::5353 :::* 0 2993017 - udp6 0 0 :::56733 :::* 0 22628 - *** Log File - Last 25 Lines *** 2023-12-21 23:28:57.304 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish KeepAlive event 2023-12-21 23:28:59.755 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:28:59.937 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event SIPRegisterResult to MQTT 2023-12-21 23:29:00.960 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event SIPRegisterResult to MQTT 2023-12-21 23:29:04.186 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:29:04.667 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:29:11.185 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:29:52.303 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish KeepAlive event 2023-12-21 23:29:57.935 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event SIPRegisterResult to MQTT 2023-12-21 23:29:58.957 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event SIPRegisterResult to MQTT 2023-12-21 23:30:24.172 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:30:31.183 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:30:47.302 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish KeepAlive event 2023-12-21 23:30:55.933 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event SIPRegisterResult to MQTT 2023-12-21 23:30:56.954 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event SIPRegisterResult to MQTT 2023-12-21 23:31:11.304 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:31:16.183 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:31:37.254 - info: panasonic-comfort-cloud.0 (917) state panasonic- comfort-cloud.0.info.connection changed: true (ack = true) 2023-12-21 23:31:42.320 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish KeepAlive event 2023-12-21 23:31:43.280 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:31:53.932 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event SIPRegisterResult to MQTT 2023-12-21 23:31:54.954 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event SIPRegisterResult to MQTT 2023-12-21 23:31:56.301 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event NTPAdjustTime to MQTT 2023-12-21 23:31:59.182 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish event VideoMotion to MQTT 2023-12-21 23:32:37.301 - info: javascript.0 (292) script.js.common.Dahua.DahuaE vent: Publish KeepAlive event ============ Mark until here for C&P =============Summary
======================= SUMMARY ======================= v.2023-10-10 model name : Intel(R) Celeron(R) J4025 CPU @ 2.00GHz Kernel : x86_64 Userland : amd64 Docker : v9.0.1 Installation: Docker Kernel: x86_64 Userland: amd64 Timezone: Etc/UTC User-ID: 0 X-Server: false 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 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 18G 4.0G 308M 646M 15G 14G Swap: 13G 70M 13G Total: 32G 4.0G 13G Active iob-Instances: 24 Active repo(s): stable ioBroker Core: js-controller 5.0.17 admin 6.12.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 192.168.178.52, run as: admin Objects: 11169 States: 9270 Size of iob-Database: 20M /opt/iobroker/iobroker-data/objects.jsonl 12M /opt/iobroker/iobroker-data/objects.json.migrated 12M /opt/iobroker/iobroker-data/objects.json.bak.migrated 17M /opt/iobroker/iobroker-data/states.jsonl 1.4M /opt/iobroker/iobroker-data/states.json.migrated 1.4M /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ====================
-
RE: iobroker.admin.0 lässt sich nicht aktivierenposted in ioBroker Allgemein
naja ich habe natürlich nicht wild rumgeschossen, sondern schon geschaut was sinn macht. Die sudo Befehle haben im bash bei mir aber noch nie funktioniert:
oot@iobroker:/opt/iobroker# sudo -H -u iobroker npm install iobroker.js-controll er sudo: unable to resolve host iobroker: Name or service not known (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil removed 97 packages in 29s 143 packages are looking for funding run `npm fund` for details
-
RE: iobroker.admin.0 lässt sich nicht aktivierenposted in ioBroker Allgemein
Danke für die Unterstützung, aber wo gebe ich den sudo Befehl ein? Wenn ich im Docker das Terminal öffne , dann bekomme ich folgende Meldung:
sudo: unable to resolve host iobroker: Name or service not known removed 97 packages in 29s 143 packages are looking for funding run `npm fund` for detailsWenn ich dann den Container neustarte, kommt dieselbe Fehlermeldung.
-
iobroker.admin.0 lässt sich nicht aktivierenposted in ioBroker Allgemein
Hallo zusammen,
ich nutze schon seit einiger Zeit ioBroker im Container Manager auf eine Synology mit DSM v.7. Bis vor einiger Zeit hat auch alles sehr gut funktioniert. Von Zeit zu Zeit habe ich mich in die Admin Oberfläche eingewählt und geschaut, welche Updates es gibt, etc. Das letzte Mal habe ich das wohl Anfang Oktober gemacht. Heute wollte ich mich wieder einloggen, um nach einem spezifischen Adapter zu suchen (Tesla), aber die Oberfläche öffnete sich nicht "ERR_CONNECTION_REFUSED"
Dann bin ich den Container gegangen und habe im Terminal mit list instances nach geschaut und gesehen, dass alle meine Instanzen laufen - deshalb ist mir das nicht aufgefallen - außer die admin.0 Instanz. Die ist auf enabled und mit bind 0.0.0.0
Habe dann das image im Container Manager aktualisiert, sämtliche iob Befehle, die hier im Forum zu finden waren, aber leider läuft die Instanz Admin immer noch nicht.
Wenn ich den Container starte, dann bekomme ich auch eine Fehlermeldung mit der ich aber bislang noch nichts anfangen konnte:2023/12/21 22:39:26,stdout,================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging] 2023/12/21 22:39:26,stdout,================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] 2023/12/21 22:39:26,stdout, 2023/12/21 22:39:26,stdout,Node.js v18.19.0 2023/12/21 22:39:26,stdout, 2023/12/21 22:39:26,stdout,} 2023/12/21 22:39:26,stdout, ] 2023/12/21 22:39:26,stdout, '/opt/iobroker/node_modules/iobroker.admin/main.js' 2023/12/21 22:39:26,stdout," '/opt/iobroker/node_modules/iobroker.admin/lib/web.js', " 2023/12/21 22:39:26,stdout," '/opt/iobroker/node_modules/mime/index.js', " 2023/12/21 22:39:26,stdout, requireStack: [ 2023/12/21 22:39:26,stdout," code: 'MODULE_NOT_FOUND', " 2023/12/21 22:39:26,stdout, at Module.require (node:internal/modules/cjs/loader:1225:19) { 2023/12/21 22:39:26,stdout, at Module._load (node:internal/modules/cjs/loader:1013:12) 2023/12/21 22:39:26,stdout, at Module.load (node:internal/modules/cjs/loader:1197:32) 2023/12/21 22:39:26,stdout, at Module._extensions..js (node:internal/modules/cjs/loader:1414:10) 2023/12/21 22:39:26,stdout, at Module._compile (node:internal/modules/cjs/loader:1356:14) 2023/12/21 22:39:26,stdout, at Object.<anonymous> (/opt/iobroker/node_modules/mime/index.js:3:12) 2023/12/21 22:39:26,stdout, at require (node:internal/modules/helpers:177:18) 2023/12/21 22:39:26,stdout, at Module.require (node:internal/modules/cjs/loader:1225:19) 2023/12/21 22:39:26,stdout, at Module._load (node:internal/modules/cjs/loader:975:27) 2023/12/21 22:39:26,stdout, at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15) 2023/12/21 22:39:26,stdout,- /opt/iobroker/node_modules/iobroker.admin/main.js 2023/12/21 22:39:26,stdout,- /opt/iobroker/node_modules/iobroker.admin/lib/web.js 2023/12/21 22:39:26,stdout,- /opt/iobroker/node_modules/mime/index.js 2023/12/21 22:39:26,stdout,Require stack: 2023/12/21 22:39:26,stdout,Error: Cannot find module './Mime' 2023/12/21 22:39:26,stdout, 2023/12/21 22:39:26,stdout, ^ 2023/12/21 22:39:26,stdout, throw err; 2023/12/21 22:39:26,stdout,node:internal/modules/cjs/loader:1137 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.panasonic-comfort-cloud.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.vesync.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.gruenbeck.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.smartcontrol.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.ecovacs-deebot.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.vis.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.terminal.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.web.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.iot.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.cloud.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.backitup.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.info.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.discovery.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.ping.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.zigbee.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.openweathermap.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.sony-bravia.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.mqtt-client.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.mqtt.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.alexa2.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.hm-rega.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.hm-rpc.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.sql.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.telegram.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.javascript.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.scenes.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.whatsapp-cmb.0" for host "iobroker" 2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.admin.0" for host "iobroker" 2023/12/21 22:39:22,stdout,##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### 2023/12/21 22:39:22,stdout, 2023/12/21 22:39:22,stdout,Starting ioBroker... 2023/12/21 22:39:22,stdout, 2023/12/21 22:39:22,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:39:22,stdout,----- Step 5 of 5: ioBroker startup ----- 2023/12/21 22:39:22,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:39:22,stdout, 2023/12/21 22:39:22,stdout, 2023/12/21 22:39:22,stdout,For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). 2023/12/21 22:39:22,stdout,Some adapters have special requirements/ settings which can be activated by the use of environment variables. 2023/12/21 22:39:22,stdout, 2023/12/21 22:39:22,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:39:22,stdout,----- Step 4 of 5: Applying special settings ----- 2023/12/21 22:39:22,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:39:22,stdout, 2023/12/21 22:39:22,stdout,No action required. 2023/12/21 22:39:22,stdout,Hostname in ioBroker matches the hostname of this container. 2023/12/21 22:38:56,stdout, 2023/12/21 22:38:56,stdout,Checking Database connection... Done. 2023/12/21 22:38:44,stdout, 2023/12/21 22:38:43,stdout,(Re)setting permissions (This might take a while! Please be patient!)... Done. 2023/12/21 22:38:41,stdout, 2023/12/21 22:38:41,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:41,stdout,----- Step 3 of 5: Checking ioBroker installation ----- 2023/12/21 22:38:41,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:41,stdout, 2023/12/21 22:38:41,stdout,Existing installation of ioBroker detected in "/opt/iobroker". 2023/12/21 22:38:40,stdout, 2023/12/21 22:38:40,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:40,stdout,----- Step 2 of 5: Detecting ioBroker installation ----- 2023/12/21 22:38:40,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:40,stdout, 2023/12/21 22:38:40,stdout,This is not the first run of this container. Skipping first run preparation. 2023/12/21 22:38:40,stdout, 2023/12/21 22:38:40,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:40,stdout,----- Step 1 of 5: Preparing container ----- 2023/12/21 22:38:40,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:40,stdout, 2023/12/21 22:38:40,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:40,stdout,----- SETUID: 1000 ----- 2023/12/21 22:38:40,stdout,----- SETGID: 1000 ----- 2023/12/21 22:38:40,stdout,----- Environment Variables ----- 2023/12/21 22:38:40,stdout,----- ----- 2023/12/21 22:38:40,stdout,----- npm: 10.2.3 ----- 2023/12/21 22:38:39,stdout,----- node: v18.19.0 ----- 2023/12/21 22:38:39,stdout,----- build: 2023-12-19T23:44:44+00:00 ----- 2023/12/21 22:38:39,stdout,----- image: v9.0.1 ----- 2023/12/21 22:38:39,stdout,----- Version Information ----- 2023/12/21 22:38:39,stdout,----- ----- 2023/12/21 22:38:39,stdout,----- hostname: iobroker ----- 2023/12/21 22:38:39,stdout,----- arch: x86_64 ----- 2023/12/21 22:38:39,stdout,----- System Information ----- 2023/12/21 22:38:39,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:39,stdout, 2023/12/21 22:38:39,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:39,stdout,----- Please be patient! ----- 2023/12/21 22:38:39,stdout,----- Startupscript is now running! ----- 2023/12/21 22:38:39,stdout,----- Welcome to your ioBroker Docker container! ----- 2023/12/21 22:38:39,stdout,----- ----- 2023/12/21 22:38:39,stdout,----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- 2023/12/21 22:38:39,stdout,----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- 2023/12/21 22:38:39,stdout,----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- 2023/12/21 22:38:39,stdout,----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- 2023/12/21 22:38:39,stdout,----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- 2023/12/21 22:38:39,stdout,----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- 2023/12/21 22:38:39,stdout,----- ----- 2023/12/21 22:38:39,stdout,-------------------------------------------------------------------------------- 2023/12/21 22:38:39,stdout,------------------------- 2023-12-21 22:38:39 ------------------------- 2023/12/21 22:38:39,stdout,--------------------------------------------------------------------------------Jemand eine Idee, was ich noch versuchen könnte?
-
RE: [Verkaufe] Zigbee Kohlendioxid ( CO2 ) Sensorposted in Marktplatz
@dimaiv
funktioniert dieser nur über USB? Was ist da alles dabei bzw. welche weitere Hardware benötigt man, um diesen zu betreiben?
-
RE: [Verkaufe] Zigbee LAN/USB/WLAN Gateway CC2652Pposted in Marktplatz
Hallo zusammen,
ich habe das Problem, dass der ikea tradfri LED Treiber (ICPSHC24-10EU-IL-1) immer wieder die Verbindung zum Gateway verliert. Ich muss ihn dann immer wieder neu anlernen. Wenn die Geräte an ihrem Ort sind, dann hat der tradfri eine Verbindungsstärke von rund 50. Ich habe dazu jetzt nichts spezifisches im Netz gefunden (Tradfri und CC2652P).
Ideen?
-
Tradfri FB und direkte Verknüpfung Lampe als auch CC2652posted in Off Topic
Hallo zusammen,
ich habe folgende Frage bzw. Anmerkung / Beobachtung: In einem Zimmer habe ich eine ikea tradfri Lampe sowie die tradfri Fernbedienung.
Wenn ich die Fernbedienung direkt mit der Lampe koppele, dann kann ich mit den Pfeiltasten auch die Farbwahl steuern.
Da ich die Fernbedienung allerdings auch in iobroker haben will, um weitere Elemente zu steuern, habe ich die Fernbedienung erst mit dem CC2652 gekoppelt und dann im Anschluss direkt mit der Lampe. An/aus sowie dimmen funktioniert mit der Fernbedienung und der direktverknüpften Lampe perfekt. Allerdings funktioniert das Ändern der Farbwahl nicht mehr, wenn der Stick auch mit dem CC2652 gekoppelt ist.
Irgendeine Idee, wieso?
Danke
