Radar2 startet nicht
-
======== Start marking the full check here =========
Skript v.2023-04-16 *** BASE SYSTEM *** Architecture : x86_64 Docker : false Virtualization : kvm Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy Systemuptime and Load: 13:13:28 up 12 min, 4 users, load average: 0.01, 0.08, 0.08 CPU threads: 8 *** Time and Time Zones *** Local time: Mon 2023-07-17 13:13:28 UTC Universal time: Mon 2023-07-17 13:13:28 UTC RTC time: Mon 2023-07-17 13:13:28 Time zone: Etc/UTC (UTC, +0000) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 5.9G 1.5G 3.7G 0.0K 726M 4.2G Swap: 0B 0B 0B Total: 5.9G 1.5G 3.7G 5921 M total memory 1459 M used memory 188 M active memory 1710 M inactive memory 3735 M free memory 66 M buffer memory 659 M swap cache 0 M total swap 0 M used swap 0 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on tmpfs tmpfs 593M 804K 592M 1% /run /dev/mapper/ubuntu--vg-ubuntu--lv ext4 11G 4.1G 6.2G 40% / tmpfs tmpfs 2.9G 0 2.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/sda2 ext4 2.0G 130M 1.7G 8% /boot tmpfs tmpfs 593M 4.0K 593M 1% /run/user/0 tmpfs tmpfs 593M 4.0K 593M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Mon Jul 17 13:01:10 2023] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [Mon Jul 17 13:01:10 2023] EXT4-fs (dm-0): re-mounted. Opts: (null). Quota mode: none. [Mon Jul 17 13:01:11 2023] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/ubuntu--vg-ubuntu--lv ext4 rw,relatime `-/boot /dev/sda2 ext4 rw,relatime Files in neuralgic directories: /var: 436M /var/ 239M /var/cache 231M /var/cache/apt 164M /var/lib 146M /var/cache/apt/archives Archived and active journals take up 32.0M in the file system. /opt/iobroker/backups: 4.0K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 124M /opt/iobroker/iobroker-data/ 90M /opt/iobroker/iobroker-data/files 51M /opt/iobroker/iobroker-data/files/javascript.admin 33M /opt/iobroker/iobroker-data/files/javascript.admin/static 32M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 14M /opt/iobroker/iobroker-data/objects.jsonl 7.2M /opt/iobroker/iobroker-data/files/ham.admin/static/js/main.8080bc0b.js.map 6.9M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/910.e1389bdb.chunk.js.map 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 5.3M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/472.d73f9bde.chunk.js.map *** NodeJS-Installation *** /usr/bin/nodejs v18.16.1 /usr/bin/node v18.16.1 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 nodejs: Installed: 18.16.1-deb-1nodesource1 Candidate: 18.16.1-deb-1nodesource1 Version table: *** 18.16.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x jammy/main amd64 Packages 100 /var/lib/dpkg/status 12.22.9~dfsg-1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Temp directories causing npm8 problem: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl MULTIHOSTSERVICE/enabled: false Core adapters versions js-controller: 5.0.8 admin: 6.6.0 javascript: 7.1.1 Adapters from github: 4 Adapter State + system.adapter.accuweather.0 : accuweather : iob-server - enabled + system.adapter.admin.0 : admin : iob-server - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : iob-server - enabled + system.adapter.backitup.0 : backitup : iob-server - enabled + system.adapter.ble.0 : ble : iob-server - enabled + system.adapter.discovery.0 : discovery : iob-server - enabled + system.adapter.ham.0 : ham : iob-server - enabled + system.adapter.history.0 : history : iob-server - enabled + system.adapter.hue-extended.0 : hue-extended : iob-server - enabled + system.adapter.javascript.0 : javascript : iob-server - enabled + system.adapter.mihome.0 : mihome : iob-server - enabled, port: 9898, bind: 0.0.0.0 + system.adapter.nina.0 : nina : iob-server - enabled system.adapter.radar2.0 : radar2 : iob-server - enabled + system.adapter.tapo.0 : tapo : iob-server - enabled + system.adapter.tuya.0 : tuya : iob-server - enabled + system.adapter.yeelight-2.0 : yeelight-2 : iob-server - enabled + system.adapter.zigbee.0 : zigbee : iob-server - enabled, port: /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iob-server - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.mihome.0 : mihome : iob-server - enabled, port: 9898, bind: 0.0.0.0 + system.adapter.zigbee.0 : zigbee : iob-server - enabled, port: /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): beta Installed ioBroker-Instances Used repository: beta Adapter "accuweather" : 1.2.4 , installed 1.2.4 Adapter "admin" : 6.6.0 , installed 6.6.0 Adapter "alexa2" : 3.23.2 , installed 3.23.2 Adapter "backitup" : 2.6.23 , installed 2.6.23 Adapter "ble" : 0.13.4 , installed 0.13.4 Adapter "discovery" : 3.2.0 , installed 3.2.0 Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 2.2.4 , installed 2.2.4 Adapter "hue-extended" : 2.0.0 , installed 2.0.1 Adapter "javascript" : 7.1.1 , installed 7.1.1 Controller "js-controller": 5.0.8 , installed 5.0.8 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "nina" : 0.0.25 , installed 0.0.25 Adapter "radar2" : 2.0.7 , installed 2.0.7 Adapter "tapo" : 0.0.8 , installed 0.0.8 Adapter "tuya" : 3.14.2 , installed 3.14.2 Adapter "yeelight-2" : 1.2.1 , installed 1.2.1 Adapter "zigbee" : 1.8.18 , installed 1.8.18 Objects and States Please stand by - This may take a while Objects: 6251 States: 5556 *** OS-Repositories and Updates *** Hit:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 https://deb.nodesource.com/node_18.x jammy InRelease Hit:3 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease Get:4 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease [108 kB] Hit:5 http://de.archive.ubuntu.com/ubuntu jammy-security InRelease Fetched 108 kB in 1s (207 kB/s) Reading package lists... 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 127.0.0.53:53 0.0.0.0:* LISTEN 102 20274 605/systemd-resolve tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 17316 1/init tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 20371 649/sshd: /usr/sbin tcp 0 0 0.0.0.0:50157 0.0.0.0:* LISTEN 109 29379 2071/rpc.statd tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 28842 1835/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 26985 1835/iobroker.js-co tcp6 0 0 :::111 :::* LISTEN 0 17318 1/init tcp6 0 0 :::22 :::* LISTEN 0 20373 649/sshd: /usr/sbin tcp6 0 0 :::45869 :::* LISTEN 109 29383 2071/rpc.statd tcp6 0 0 :::8081 :::* LISTEN 1001 28883 1853/io.admin.0 tcp6 0 0 :::36461 :::* LISTEN 1001 28101 1939/io.ham.0 udp 0 0 127.0.0.1:975 0.0.0.0:* 0 29373 2071/rpc.statd udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 29830 1939/io.ham.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 28102 1939/io.ham.0 udp 0 0 0.0.0.0:9898 0.0.0.0:* 1001 27145 1966/io.mihome.0 udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 28143 1994/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 28144 1994/io.tuya.0 udp 0 0 127.0.0.53:53 0.0.0.0:* 102 20273 605/systemd-resolve udp 0 0 192.168.1.166:68 0.0.0.0:* 101 20254 603/systemd-network udp 0 0 0.0.0.0:111 0.0.0.0:* 0 17317 1/init udp 0 0 0.0.0.0:45259 0.0.0.0:* 109 29377 2071/rpc.statd udp6 0 0 :::52179 :::* 109 29381 2071/rpc.statd udp6 0 0 :::111 :::* 0 17319 1/init udp6 0 0 fe80::4401:1ff:fe01:546 :::* 101 20701 603/systemd-network *** Log File - Last 25 Lines *** 2023-07-17 13:07:25.755 - info: radar2.0 (2504) Will try to scan BT devices: hci0 78:8A:86:1F:0B:8B 2023-07-17 13:07:25.768 - warn: radar2.0 (2504) Uncaught Exception: spawn ping ENOENT 2023-07-17 13:07:25.769 - error: radar2.0 (2504) uncaught exception: spawn ping ENOENT 2023-07-17 13:07:25.769 - error: radar2.0 (2504) Error: spawn ping ENOENT at ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:476:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) 2023-07-17 13:07:25.769 - error: radar2.0 (2504) Exception-Code: ENOENT: spawn ping ENOENT 2023-07-17 13:07:25.774 - info: radar2.0 (2504) Unload adapter now with null 2023-07-17 13:07:25.774 - info: radar2.0 (2504) Adapter disconnected and stopped with dostop(null) and callback(true) 2023-07-17 13:07:25.774 - info: radar2.0 (2504) terminating 2023-07-17 13:07:25.775 - warn: radar2.0 (2504) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-17 13:07:25.775 - info: radar2.0 (2504) terminating 2023-07-17 13:07:25.775 - info: radar2.0 (2504) terminating 2023-07-17 13:07:25.821 - info: radar2.0 (2504) debug: created State radar2.0.info.connection 2023-07-17 13:07:26.273 - info: radar2.0 (2504) terminating 2023-07-17 13:07:26.303 - error: host.iob-server instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-17 13:07:26.304 - info: host.iob-server Restart adapter system.adapter.radar2.0 because enabled 2023-07-17 13:07:26.304 - warn: host.iob-server Do not restart adapter system.adapter.radar2.0 because restart loop detected 2023-07-17 13:10:00.022 - warn: javascript.0 (1895) getState "radar2.0.Homework._here" not found (3) 2023-07-17 13:10:00.023 - warn: javascript.0 (1895) at Object.<anonymous> (script.js.common.Wohnung.Wohnzimmer_Licht_Automatic:5:63) 2023-07-17 13:10:00.023 - warn: javascript.0 (1895) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1255:38) 2023-07-17 13:10:00.023 - warn: javascript.0 (1895) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:645:29) 2023-07-17 13:10:00.023 - warn: javascript.0 (1895) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11082:62) 2023-07-17 13:10:00.023 - warn: javascript.0 (1895) at processImmediate (node:internal/timers:476:21)============ Mark until here for C&P =============
iob diag has finished.
-
Radar 2 startet nicht.
log
host.iob-server 2023-07-17 15:06:54.411 info Restart adapter system.adapter.radar2.0 because enabled host.iob-server 2023-07-17 15:06:54.411 error instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) radar2.0 2023-07-17 15:06:54.382 info terminating radar2.0 2023-07-17 15:06:53.933 info debug: created State radar2.0.info.connection radar2.0 2023-07-17 15:06:53.884 info terminating radar2.0 2023-07-17 15:06:53.884 info terminating radar2.0 2023-07-17 15:06:53.884 warn Terminated (UNCAUGHT_EXCEPTION): Without reason radar2.0 2023-07-17 15:06:53.883 info terminating radar2.0 2023-07-17 15:06:53.883 info Adapter disconnected and stopped with dostop(null) and callback(true) radar2.0 2023-07-17 15:06:53.883 info Unload adapter now with null radar2.0 2023-07-17 15:06:53.878 error Exception-Code: ENOENT: spawn ping ENOENT radar2.0 2023-07-17 15:06:53.878 error Error: spawn ping ENOENT at ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:476:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) radar2.0 2023-07-17 15:06:53.878 error uncaught exception: spawn ping ENOENT radar2.0 2023-07-17 15:06:53.877 warn Uncaught Exception: spawn ping ENOENT radar2.0 2023-07-17 15:06:53.862 info Will try to scan BT devices: hci0 78:8A:86:1F:0B:8B radar2.0 2023-07-17 15:06:53.851 info debug: Will 'not save' unknown BT devices and will 'save' unknown IP devices! radar2.0 2023-07-17 15:06:53.850 info debug: radar2 set to scan every 30 seconds and printers every 720 minutes. radar2.0 2023-07-17 15:06:53.776 info Connected with '0.0.0.0' for DHCP Scan radar2.0 2023-07-17 15:06:53.769 info arp-scan will use the following interfaces: [ 'ens18' ] radar2.0 2023-07-17 15:06:53.769 info debug: use known IP list: [ '192.168.178.10', '192.168.178.10' ] radar2.0 2023-07-17 15:06:53.768 info debug: use known BT list: [ '01:12:23:34:45:56' ] radar2.0 2023-07-17 15:06:53.767 info debug: radar2 set to flag items away if they are not seen for 3 minutes radar2.0 2023-07-17 15:06:53.567 info debug: started #3 hciconfig hci0 up radar2.0 2023-07-17 15:06:53.448 info debug: started #2 hciconfig hci0 down radar2.0 2023-07-17 15:06:53.443 info Will run hcitool-mode and not noble on device [ [Object] ]! radar2.0 2023-07-17 15:06:53.425 info debug: started #1 hcitool dev radar2.0 2023-07-17 15:06:53.411 info Will use l2Ping for BT scans. radar2.0 2023-07-17 15:06:53.405 info radar2 initialization started... radar2.0 2023-07-17 15:06:53.404 info debug: radar2 received 2 objects and 1 states, with config devices,scandelay,arp_scan_cmd,btadapterid,printerdelay,debug,knownIPs,knownBTs,external,delayaway,delayuwz,numuwz,hcionly,l2ponly,longuwz,suBT,suIP,lang,latitude,longitude,adapterConf,loglevel radar2.0 2023-07-17 15:06:53.364 info starting. Version 2.0.7 (non-npm: frankjoke/ioBroker.radar2) in /opt/iobroker/node_modules/iobroker.radar2, node: v18.16.1, js-controller: 5.0.8 host.iob-server 2023-07-17 15:06:52.579 info instance system.adapter.radar2.0 started with pid 2469 host.iob-server 2023-07-17 13:06:22.554 info Restart adapter system.adapter.radar2.0 because enabled host.iob-server 2023-07-17 13:06:22.554 error instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION) radar2.0 2023-07-17 13:06:22.523 info terminating radar2.0 2023-07-17 13:06:22.069 info debug: created State radar2.0.info.connection radar2.0 2023-07-17 13:06:22.024 info terminating radar2.0 2023-07-17 13:06:22.023 info terminating radar2.0 2023-07-17 13:06:22.023 warn Terminated (UNCAUGHT_EXCEPTION): Without reason radar2.0 2023-07-17 13:06:22.023 info terminating radar2.0 2023-07-17 13:06:22.023 info Adapter disconnected and stopped with dostop(null) and callback(true) radar2.0 2023-07-17 13:06:22.022 info Unload adapter now with null radar2.0 2023-07-17 13:06:22.018 error Exception-Code: ENOENT: spawn ping ENOENT radar2.0 2023-07-17 13:06:22.018 error Error: spawn ping ENOENT at ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:476:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) radar2.0 2023-07-17 13:06:22.017 error uncaught exception: spawn ping ENOENT radar2.0 2023-07-17 13:06:22.017 warn Uncaught Exception: spawn ping ENOENT radar2.0 2023-07-17 13:06:22.002 info Will try to scan BT devices: hci0 78:8A:86:1F:0B:8B radar2.0 2023-07-17 13:06:21.991 info debug: Will 'not save' unknown BT devices and will 'save' unknown IP devices! radar2.0 2023-07-17 13:06:21.990 info debug: radar2 set to scan every 30 seconds and printers every 720 minutes. radar2.0 2023-07-17 13:06:21.918 info Connected with '0.0.0.0' for DHCP Scan radar2.0 2023-07-17 13:06:21.912 info arp-scan will use the following interfaces: [ 'ens18' ] radar2.0 2023-07-17 13:06:21.911 info debug: use known IP list: [ '192.168.178.10', '192.168.178.10' ] radar2.0 2023-07-17 13:06:21.911 info debug: use known BT list: [ '01:12:23:34:45:56' ] radar2.0 2023-07-17 13:06:21.910 info debug: radar2 set to flag items away if they are not seen for 3 minutes radar2.0 2023-07-17 13:06:21.723 info debug: started #3 hciconfig hci0 up radar2.0 2023-07-17 13:06:21.604 info debug: started #2 hciconfig hci0 down radar2.0 2023-07-17 13:06:21.600 info Will run hcitool-mode and not noble on device [ [Object] ]! radar2.0 2023-07-17 13:06:21.580 info debug: started #1 hcitool dev radar2.0 2023-07-17 13:06:21.566 info Will use l2Ping for BT scans. radar2.0 2023-07-17 13:06:21.560 info radar2 initialization started... radar2.0 2023-07-17 13:06:21.559 info debug: radar2 received 2 objects and 1 states, with config devices,scandelay,arp_scan_cmd,btadapterid,printerdelay,debug,knownIPs,knownBTs,external,delayaway,delayuwz,numuwz,hcionly,l2ponly,longuwz,suBT,suIP,lang,latitude,longitude,adapterConf,loglevel radar2.0 2023-07-17 13:06:21.512 info starting. Version 2.0.7 (non-npm: frankjoke/ioBroker.radar2) in /opt/iobroker/node_modules/iobroker.radar2, node: v18.16.1, js-controller: 5.0.8 radar2.0 2023-07-17 13:06:21.426 debug States connected to redis: 127.0.0.1:9000 radar2.0 2023-07-17 13:06:21.373 debug States create User PubSub Client radar2.0 2023-07-17 13:06:21.373 debug States create System PubSub Client radar2.0 2023-07-17 13:06:21.366 debug Redis States: Use Redis connection: 127.0.0.1:9000 radar2.0 2023-07-17 13:06:21.351 debug Objects connected to redis: 127.0.0.1:9001 radar2.0 2023-07-17 13:06:21.347 debug Objects client initialize lua scripts radar2.0 2023-07-17 13:06:21.329 debug Objects create User PubSub Client radar2.0 2023-07-17 13:06:21.328 debug Objects create System PubSub Client radar2.0 2023-07-17 13:06:21.327 debug Objects client ready ... initialize now radar2.0 2023-07-17 13:06:21.309 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 host.iob-server 2023-07-17 13:06:20.735 info instance system.adapter.radar2.0 started with pid 2434MOD-EDIT: Code in code-tags gesetzt!
die adapter Hilfe habe ich schon ausprobiert.
Fehler verschwindet einfach nicht -
@larryxxl Hast Du die Befehle unter https://github.com/iobroker-community-adapters/ioBroker.radar2#installation ausgeführt?
-
ja habe die Befehle schon ausgeführt. Denke das in IOBroker alles ok ist. Aber etwas unter Ubuntu fehlt oder falsch installiert ist.
Es laufen alle anderen Adapter bis auf den Radar2.
Auch Bluetooth ist ok unter Proxmox und einer VM. Habe hierfür allerdings verschiedene M2 Wifi adapter ausprobieren müssen. Intel war ein Problem AX201,210. Realtek funktioniert aber. -
Zeitzone ist nicht richtig gesetzt, du hampelst als root herum.
-
Kann es sein das man als User "Pi" mit Sudo mehr rumhampelt als als "root" ?
Und wenn eine falsche Zeitzone dem Radar2 Adapter beim Starten permanent abstürzen lässt sollte ich vielleicht doch noch Lotto spielen.
-
@larryxxl sagte in Radar2 startet nicht:
Kann es sein das man als User "Pi" mit Sudo mehr rumhampelt als als "root" ?
Nein.
-
@larryxxl sagte in Radar2 startet nicht:
Und wenn eine falsche Zeitzone dem Radar2 Adapter beim Starten permanent abstürzen lässt sollte ich vielleicht doch noch Lotto spielen.
Ist halt ein Indikator dafür daß das System nicht senkrecht eingerichtet ist. Vor allem in Kombination mit dem root.
-
wo stelle ich die Zeitzone in IOBroker ein ?
-
Die Zeitzone in deinem OS ist falsch.
-
To restore this content, you can run the 'unminimize' command. Last login: Mon Jul 17 14:26:06 2023 from 192.168.1.150 root@iob-server:~# su pi pi@iob-server:/root$ sudo timedatectl set-timezone Europe/Berlin [sudo] password for pi: pi@iob-server:/root$ sudo timedatectl Local time: Tue 2023-07-18 20:36:07 CEST Universal time: Tue 2023-07-18 18:36:07 UTC RTC time: Tue 2023-07-18 18:36:07 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no pi@iob-server:/root$MOD-EDIT: Code in code-tags gesetzt!
Das nächste Prolem war das wenn ich das aktuellen Beta Admin.adapter installiere iobroker gar nicht mehr startet. 6.6.0->6.6.1.
danach war ein Rollback nötig.
-
@larryxxl sagte in Radar2 startet nicht:
Das nächste Prolem war das wenn ich das aktuellen Beta Admin.adapter installiere iobroker gar nicht mehr startet. 6.6.0->6.6.1.
danach war ein Rollback nötig.Was soll ich sagen...
Hat es auf meinem System natürlich getan. -
Ubuntu neu installiert. kein root. iobroker neu installiert. Adapter neu installiert und eingerichtet. Zigbee Backup eingespielt.
alles gebrauchten Adapter sind nun grün und laufen.
Blockly Scripte mussten teilweise korrigiert werden weil jetzt die empfohlende node Version benutzt wird.
Alles soweit ok. -
Also 'kaum macht man es ordentlich/richtig, schon funktioniert es?'
-
@larryxxl sagte in Radar2 startet nicht:
Blockly Scripte mussten teilweise korrigiert werden weil jetzt die empfohlende node Version benutzt wird.
Verstehe ich aber nicht ganz den Zusammenhang
