NEWS
Failed to lock DB file nach Festplatte voll.
ioBroker Allgemein
82
Beiträge
6
Kommentatoren
8.3k
Aufrufe
5
Watching
-
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Bei Windows klappt das absolut zuverlässig
wenn gerade in die Registry geschrieben wird, während der Strom weg geht, überrascht die dein Bildschirm unter Umständen auch mit einem leuchtenden blauen Bildschirm.
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Das sagt einem halt wirklich niemand
das steht doch geschrieben, bei Ubuntu ist das erst gar nicht anders möglich
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Warum gibt es da kein System, welches solche kritischen Informationen per Mail oder Telegram verschickt?
das musst du konfigurieren
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Aber alle Adapter sind gestoppt und starten auch nicht mehr
wenn das backup zurückgespielt wurde, dauert es anschließend eine ganze Weile bis alles neu "gebaut" und geladen wurde
@crunchip OK es ist jetzt bald zwei Stunden her und die meisten Adapter sind noch immer rot und im Log tut sich nichts.
Bei der Vis kommt z.B. nur
File edit.html not found: {}wenn ich sie im Browser aufrufe.
Ein paar wenige sind grün, aber es scheint jetzt seit längerer Zeit zu hängen.
Für influxdb finde ich keine Anleitungen mehr, die aktuell sind. Gibt es da irgendeine, die für influxdb2 passt?
Bei dieser ist der Client nicht mehr gleich und das Config-File ist leer und ich kann keinen Admin-User anlegen, es kommt immer, dass ich keine Rechte hätte. https://www.smarthome-tricks.de/software-iobroker/1-2-grafana-installation-von-influxdb-und-integration-in-iobroker/
-
@crunchip OK es ist jetzt bald zwei Stunden her und die meisten Adapter sind noch immer rot und im Log tut sich nichts.
Bei der Vis kommt z.B. nur
File edit.html not found: {}wenn ich sie im Browser aufrufe.
Ein paar wenige sind grün, aber es scheint jetzt seit längerer Zeit zu hängen.
Für influxdb finde ich keine Anleitungen mehr, die aktuell sind. Gibt es da irgendeine, die für influxdb2 passt?
Bei dieser ist der Client nicht mehr gleich und das Config-File ist leer und ich kann keinen Admin-User anlegen, es kommt immer, dass ich keine Rechte hätte. https://www.smarthome-tricks.de/software-iobroker/1-2-grafana-installation-von-influxdb-und-integration-in-iobroker/
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Bei der Vis kommt z.B. nur
weil, aus aktuellem Bug vis/web vor dem Backup zurück spielen installiert sein muss, nachträglich geht auch, dann musst du manuell eine ältere Version 1.4.0 installieren, dann geht es wieder und kannst anschliessen wieder auf die aktuelle
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
die meisten Adapter sind noch immer rot
sind die IP bezogenen Adapter (shelly, mqtt, sonoff...) auf die IP angepasst, denn ich denke dein neuer Host hat jetzt einen andere IP als der alte, oder?
umgestiegen von Proxmox auf Unraid
-
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Bei der Vis kommt z.B. nur
weil, aus aktuellem Bug vis/web vor dem Backup zurück spielen installiert sein muss, nachträglich geht auch, dann musst du manuell eine ältere Version 1.4.0 installieren, dann geht es wieder und kannst anschliessen wieder auf die aktuelle
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
die meisten Adapter sind noch immer rot
sind die IP bezogenen Adapter (shelly, mqtt, sonoff...) auf die IP angepasst, denn ich denke dein neuer Host hat jetzt einen andere IP als der alte, oder?
@crunchip oh, ähm, wie?
Also jetzt ist 1.4.16 installiert. Ich kann aber die Vis-Daten nicht separat wiederherstellen?
Was muss ich also machen? Das ist alles so wahnsinnig aufwendig :confounded:
Wobei die Vis gar nicht installiert ist? Oder wie ist das zu verstehen? Starten lässt sie sich auch nicht.
-
@crunchip oh, ähm, wie?
Also jetzt ist 1.4.16 installiert. Ich kann aber die Vis-Daten nicht separat wiederherstellen?
Was muss ich also machen? Das ist alles so wahnsinnig aufwendig :confounded:
Wobei die Vis gar nicht installiert ist? Oder wie ist das zu verstehen? Starten lässt sie sich auch nicht.
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Wobei die Vis gar nicht installiert ist? Oder wie ist das zu verstehen?
Die ist noch nicht wieder gebaut worden.
-
@crunchip oh, ähm, wie?
Also jetzt ist 1.4.16 installiert. Ich kann aber die Vis-Daten nicht separat wiederherstellen?
Was muss ich also machen? Das ist alles so wahnsinnig aufwendig :confounded:
Wobei die Vis gar nicht installiert ist? Oder wie ist das zu verstehen? Starten lässt sie sich auch nicht.
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Was muss ich also machen?
warten bis alles fertig ist, und dann so wie ich geschrieben habe, der bug mit vis behebst du mit
iobroker install vis@1.4.0 -
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Wobei die Vis gar nicht installiert ist? Oder wie ist das zu verstehen?
Die ist noch nicht wieder gebaut worden.
@thomas-braun Kann das wirklich drei Stunden dauern die paar Adapter zu installieren? Auf einem 24 Kern Intel Xeon mit NVMe SSD?
-
Nach dem die Festplatte vollgelaufen ist, kann ich den ioBroker nicht mehr starten:
pi@ioBrokerVM:/opt/iobroker$ node node_modules/iobroker.js-controller/controller.js --logs 2023-03-04 09:57:15.583 - info: host.ioBrokerVM iobroker.js-controller version 4.0.24 js-controller starting 2023-03-04 09:57:15.589 - info: host.ioBrokerVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-03-04 09:57:15.590 - info: host.ioBrokerVM hostname: ioBrokerVM, node: v14.19.3 2023-03-04 09:57:15.590 - info: host.ioBrokerVM ip addresses: 192.168.20.20 fe80::a00:27ff:fe73:7859 2023-03-04 09:57:17.691 - error: host.ioBrokerVM-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!Ich habe bereits die Backup-States und -Objects wiederhergestellt, das hat aber nichts geholfen:
-rw-rwxrw-+ 1 iobroker iobroker 351377 Mär 2 20:54 2023-03-02_20-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3093058 Mär 2 22:54 2023-03-02_22-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350637 Mär 2 22:54 2023-03-02_22-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3092490 Mär 3 00:54 2023-03-03_00-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350688 Mär 3 00:54 2023-03-03_00-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3092984 Mär 3 02:54 2023-03-03_02-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350673 Mär 3 02:54 2023-03-03_02-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3092818 Mär 3 04:54 2023-03-03_04-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350887 Mär 3 04:54 2023-03-03_04-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3092699 Mär 3 06:54 2023-03-03_06-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350714 Mär 3 06:54 2023-03-03_06-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3092787 Mär 3 08:54 2023-03-03_08-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 351063 Mär 3 08:54 2023-03-03_08-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3092986 Mär 3 10:54 2023-03-03_10-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350923 Mär 3 10:54 2023-03-03_10-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3093271 Mär 3 12:54 2023-03-03_12-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350752 Mär 3 12:54 2023-03-03_12-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3093112 Mär 3 14:54 2023-03-03_14-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 351187 Mär 3 14:54 2023-03-03_14-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3093104 Mär 3 16:54 2023-03-03_16-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350992 Mär 3 16:54 2023-03-03_16-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3093138 Mär 3 18:54 2023-03-03_18-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350598 Mär 3 18:54 2023-03-03_18-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3092969 Mär 3 20:54 2023-03-03_20-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350794 Mär 3 20:54 2023-03-03_20-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3092968 Mär 3 22:54 2023-03-03_22-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350486 Mär 3 22:54 2023-03-03_22-54_states.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 3093542 Mär 4 00:54 2023-03-04_00-54_objects.jsonl.gz -rw-rwxrw-+ 1 iobroker iobroker 350223 Mär 4 00:54 2023-03-04_00-54_states.jsonl.gz pi@ioBrokerVM:/opt/iobroker/iobroker-data/backup-objects$ gunzip -ck /opt/iobroker/iobroker-data/backup-objects/2023-03-03_00-54_objects.jsonl.gz > /opt/iobroker/iobroker-data/objects.json pi@ioBrokerVM:/opt/iobroker/iobroker-data/backup-objects$ gunzip -ck /opt/iobroker/iobroker-data/backup-objects/2023-03-03_00-54_states.jsonl.gz > /opt/iobroker/iobroker-data/states.jsonDas Fix.sh-Skript habe ich bereits laufen lassen.
Danke für die Hilfe!
iob diag:
Skript v.2023-01-02 *** BASE SYSTEM *** Architecture: x86_64 Docker: false Virtualization: oracle Distributor ID: Debian Description: Debian GNU/Linux 9.13 (stretch) Release: 9.13 Codename: stretch PRETTY_NAME="Debian GNU/Linux 9 (stretch)" NAME="Debian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" VERSION_CODENAME=stretch ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Systemuptime and Load: 10:00:14 up 17 min, 1 user, load average: 0.29, 0.16, 0.11 CPU threads: 12 *** Time and Time Zones *** Sat Mar 4 09:00:14 UTC 2023 Sat Mar 4 10:00:14 CET 2023 CET +0100 Europe/Zurich *** User and Groups *** pi /home/pi pi cdrom floppy sudo audio dip video plugdev netdev iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 9.9G 575M 8.1G 8.7M 1.2G 9.0G Swap: 4.2G 0B 4.2G Total: 14G 575M 12G 9633 M total memory 562 M used memory 558 M active memory 691 M inactive memory 7907 M free memory 303 M buffer memory 860 M swap cache 4092 M total swap 0 M used swap 4092 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 4.7G 0 4.7G 0% /dev tmpfs tmpfs 964M 8.5M 955M 1% /run /dev/sda1 ext4 94G 22G 68G 25% / tmpfs tmpfs 4.8G 0 4.8G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 4.8G 0 4.8G 0% /sys/fs/cgroup tmpfs tmpfs 964M 0 964M 0% /run/user/1000 Messages in dmesg: [Sat Mar 4 09:42:54 2023] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [Sat Mar 4 09:42:54 2023] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro Show mounted filesystems (real ones only): findmnt: unrecognized option '--real' Usage: findmnt [options] findmnt [options] <device> | <mountpoint> findmnt [options] <device> <mountpoint> findmnt [options] [--source <device>] [--target <path> | --mountpoint <dir>] Find a (mounted) filesystem. Options: -s, --fstab search in static table of filesystems -m, --mtab search in table of mounted filesystems -k, --kernel search in kernel table of mounted filesystems (default) -p, --poll[=<list>] monitor changes in table of mounted filesystems -w, --timeout <num> upper limit in milliseconds that --poll will block -A, --all disable all built-in filters, print all filesystems -a, --ascii use ASCII chars for tree formatting -b, --bytes print sizes in bytes rather than in human readable format -C, --nocanonicalize don't canonicalize when comparing paths -c, --canonicalize canonicalize printed paths -D, --df imitate the output of df(1) -d, --direction <word> direction of search, 'forward' or 'backward' -e, --evaluate convert tags (LABEL,UUID,PARTUUID,PARTLABEL) to device names -F, --tab-file <path> alternative file for -s, -m or -k options -f, --first-only print the first found filesystem only -i, --invert invert the sense of matching -J, --json use JSON output format -l, --list use list format output -N, --task <tid> use alternative namespace (/proc/<tid>/mountinfo file) -n, --noheadings don't print column headings -O, --options <list> limit the set of filesystems by mount options -o, --output <list> the output columns to be shown -P, --pairs use key="value" output format -R, --submounts print all submounts for the matching filesystems -r, --raw use raw output format -S, --source <string> the device to mount (by name, maj:min, LABEL=, UUID=, PARTUUID=, PARTLABEL=) -T, --target <path> the path to the filesystem to use -M, --mountpoint <dir> the mountpoint directory -t, --types <list> limit the set of filesystems by FS types -U, --uniq ignore filesystems with duplicate target -u, --notruncate don't truncate text in columns -v, --nofsroot don't print [/dir] for bind or btrfs mounts -x, --verify verify mount table content (default is fstab) --verbose print more details -h, --help display this help and exit -V, --version output version information and exit Available columns: SOURCE source device TARGET mountpoint FSTYPE filesystem type OPTIONS all mount options VFS-OPTIONS VFS specific mount options FS-OPTIONS FS specific mount options LABEL filesystem label UUID filesystem UUID PARTLABEL partition label PARTUUID partition UUID MAJ:MIN major:minor device number ACTION action detected by --poll OLD-TARGET old mountpoint saved by --poll OLD-OPTIONS old mount options saved by --poll SIZE filesystem size AVAIL filesystem size available USED filesystem size used USE% filesystem use percentage FSROOT filesystem root TID task ID ID mount ID OPT-FIELDS optional mount fields PROPAGATION VFS propagation flags FREQ dump(8) period in days [fstab only] PASSNO pass number on parallel fsck(8) [fstab only] For more details see findmnt(8). Files in neuralgic directories: /var: 3.1G /var/ 1.5G /var/lib 1.3G /var/lib/influxdb/data 1.3G /var/lib/influxdb 1.2G /var/lib/influxdb/data/iobroker/autogen /opt/iobroker/backups: 2.1G /opt/iobroker/backups/ 16K /opt/iobroker/backups/grafana_tmp 4.0K /opt/iobroker/backups/grafana_tmp/datasource 4.0K /opt/iobroker/backups/grafana_tmp/dashboards_manually_restore 4.0K /opt/iobroker/backups/grafana_tmp/dashboards /opt/iobroker/iobroker-data: 4.0G /opt/iobroker/iobroker-data/ 3.0G /opt/iobroker/iobroker-data/history 797M /opt/iobroker/iobroker-data/files 168M /opt/iobroker/iobroker-data/files/scenes.admin/static/js 168M /opt/iobroker/iobroker-data/files/scenes.admin/static The five largest files in iobroker-data are: 41M /opt/iobroker/iobroker-data/files/material/static/js/main.c5478f66.js.map 24M /opt/iobroker/iobroker-data/objects.json 23M /opt/iobroker/iobroker-data/files/echarts/static/js/main.a5779c98.js.map 23M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.a5779c98.js.map 22M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.073332eb.js.map *** NodeJS-Installation *** /usr/bin/nodejs v14.19.3 /usr/bin/node v14.19.3 /usr/bin/npm 6.14.17 /usr/bin/npx 6.14.17 nodejs: Installed: 14.19.3-1nodesource1 Candidate: 14.21.3-1nodesource1 Version table: 14.21.3-1nodesource1 500 500 https://deb.nodesource.com/node_14.x stretch/main amd64 Packages *** 14.19.3-1nodesource1 100 100 /var/lib/dpkg/status 4.8.2~dfsg-1 500 500 http://ftp.ch.debian.org/debian stretch/main amd64 Packages Temp directories causing npm8 problem: 0 *** ioBroker-Installation *** ioBroker Status Cannot read system.config: null (OK when migrating or restoring) iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 4.0.24 admin: 6.3.6 javascript: 7.0.1 npm ERR! extraneous: @node-red/editor-api@0.20.5 /opt/iobroker/node_modules/@node-red/editor-api npm ERR! extraneous: @node-red/nodes@0.20.5 /opt/iobroker/node_modules/@node-red/nodes npm ERR! extraneous: @node-red/runtime@0.20.5 /opt/iobroker/node_modules/@node-red/runtime npm ERR! extraneous: alexa-remote2@2.3.3 /opt/iobroker/node_modules/alexa-remote2 npm ERR! extraneous: async-mutex@0.2.6 /opt/iobroker/node_modules/async-mutex npm ERR! extraneous: cron@1.7.1 /opt/iobroker/node_modules/cron npm ERR! extraneous: dropbox-v2-api@2.1.22 /opt/iobroker/node_modules/dropbox-v2-api npm ERR! extraneous: express-fileupload@0.4.1 /opt/iobroker/node_modules/express-fileupload npm ERR! extraneous: googleapis@40.0.1 /opt/iobroker/node_modules/googleapis npm ERR! extraneous: hap-nodejs@0.4.48 /opt/iobroker/node_modules/hap-nodejs npm ERR! extraneous: hap-nodejs-community-types@0.2.1 /opt/iobroker/node_modules/hap-nodejs-community-types npm ERR! extraneous: http-proxy-middleware@0.18.0 /opt/iobroker/node_modules/http-proxy-middleware npm ERR! extraneous: iobroker.type-detector@0.1.0 /opt/iobroker/node_modules/iobroker.type-detector npm ERR! extraneous: js2xmlparser@3.0.0 /opt/iobroker/node_modules/js2xmlparser npm ERR! extraneous: linkify-it@2.1.0 /opt/iobroker/node_modules/linkify-it npm ERR! extraneous: mailparser-mit@1.0.0 /opt/iobroker/node_modules/mailparser-mit npm ERR! extraneous: mailsplit@4.4.1 /opt/iobroker/node_modules/mailsplit npm ERR! extraneous: mongodb@3.1.13 /opt/iobroker/node_modules/mongodb npm ERR! extraneous: node-hikvision-api@0.0.1 /opt/iobroker/node_modules/node-hikvision-api npm ERR! extraneous: node-red@0.19.6 /opt/iobroker/node_modules/node-red npm ERR! extraneous: node-red-contrib-polymer@0.0.21 /opt/iobroker/node_modules/node-red-contrib-polymer npm ERR! extraneous: node-red-dashboard@2.14.0 /opt/iobroker/node_modules/node-red-dashboard npm ERR! extraneous: node-red-node-sentiment@0.1.3 /opt/iobroker/node_modules/node-red-node-sentiment npm ERR! extraneous: node-red-node-tail@0.0.2 /opt/iobroker/node_modules/node-red-node-tail npm ERR! extraneous: node-telegram-bot-api@0.30.0 /opt/iobroker/node_modules/node-telegram-bot-api npm ERR! extraneous: node-tradfri-client@1.5.0 /opt/iobroker/node_modules/node-tradfri-client npm ERR! extraneous: nodemailer@6.3.0 /opt/iobroker/node_modules/nodemailer npm ERR! extraneous: shelly-iot@1.0.2 /opt/iobroker/node_modules/shelly-iot npm ERR! extraneous: util@0.10.4 /opt/iobroker/node_modules/util npm ERR! extraneous: virtual-device-sdk@1.5.16 /opt/iobroker/node_modules/virtual-device-sdk npm ERR! extraneous: zigbee-herdsman@0.1.17 /opt/iobroker/node_modules/zigbee-herdsman npm ERR! extraneous: zigbee-shepherd-converters@7.0.25 /opt/iobroker/node_modules/zigbee-shepherd-converters npm ERR! peer dep missing: buffer@>=6.0.3, required by crc@4.1.1 npm ERR! extraneous: libmime@5.0.0 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red-node-email/node_modules/libmime npm ERR! peer dep missing: tough-cookie@^4.0.0, required by http-cookie-agent@4.0.2 Adapters from github: 13 Adapter State Cannot read system.config: null (OK when migrating or restoring) + instance is alive Enabled adapters with bindings ioBroker-Repositories Cannot read system.config: null (OK when migrating or restoring) List is empty Installed ioBroker-Instances Cannot read system.config: null (OK when migrating or restoring) Error: Object "system.config" not found Objects and States Please stand by - This may take a while Objects: 33 States: 20079 *** OS-Repositories and Updates *** W: GPG error: https://packages.grafana.com/oss/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9E439B102CF3C0C6 W: The repository 'https://packages.grafana.com/oss/deb stable InRelease' is not signed. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E W: GPG error: https://archive.raspbian.org/raspbian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9165938D90FDDD2E W: The repository 'https://archive.raspbian.org/raspbian buster InRelease' is not signed. W: Failed to fetch https://repos.influxdata.com/debian/dists/stretch/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E W: Some index files failed to download. They have been ignored, or old ones used instead. Ign:1 http://ftp.ch.debian.org/debian stretch InRelease Hit:2 http://ftp.ch.debian.org/debian stretch-updates InRelease Hit:3 http://security.debian.org/debian-security stretch/updates InRelease Hit:4 http://ftp.ch.debian.org/debian stretch Release Get:5 https://repos.influxdata.com/debian stretch InRelease [7021 B] Hit:6 https://deb.nodesource.com/node_14.x stretch InRelease Get:7 https://packages.grafana.com/oss/deb stable InRelease [5983 B] Get:8 https://archive.raspbian.org/raspbian buster InRelease [15.0 kB] Err:5 https://repos.influxdata.com/debian stretch InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E Ign:7 https://packages.grafana.com/oss/deb stable InRelease Ign:8 https://archive.raspbian.org/raspbian buster InRelease Fetched 28.0 kB in 1s (23.6 kB/s) Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E W: GPG error: https://packages.grafana.com/oss/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9E439B102CF3C0C6 W: The repository 'https://packages.grafana.com/oss/deb stable InRelease' is not signed. W: GPG error: https://archive.raspbian.org/raspbian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9165938D90FDDD2E W: The repository 'https://archive.raspbian.org/raspbian buster InRelease' is not signed. W: Failed to fetch https://repos.influxdata.com/debian/dists/stretch/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E W: Some index files failed to download. They have been ignored, or old ones used instead. Pending Updates: 2 *** 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:9000 0.0.0.0:* LISTEN 1001 9986 1691/iobroker.js-co tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1001 9979 1691/iobroker.js-co tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 108 1381 569/redis-server 12 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 1375 516/sshd tcp 0 0 127.0.0.1:8088 0.0.0.0:* LISTEN 998 18753 489/influxd tcp6 0 0 :::8086 :::* LISTEN 998 11394 489/influxd tcp6 0 0 :::22 :::* LISTEN 0 1377 516/sshd tcp6 0 0 :::3000 :::* LISTEN 109 18084 469/grafana-server udp 0 0 0.0.0.0:68 0.0.0.0:* 0 16728 451/dhclient udp 0 0 0.0.0.0:53600 0.0.0.0:* 107 11360 468/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 107 11358 468/avahi-daemon: r udp6 0 0 :::5353 :::* 107 11359 468/avahi-daemon: r udp6 0 0 :::46863 :::* 107 11361 468/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-03-04 09:56:54.309 - info: host.ioBrokerVM ip addresses: 192.168.20.20 fe80::a00:27ff:fe73:7859 2023-03-04 09:56:54.468 - error: host.ioBrokerVM Cannot read system.config: null (OK when migrating or restoring) 2023-03-04 09:56:54.532 - error: host.ioBrokerVM Cannot find view "system" for search "host" 2023-03-04 09:56:55.029 - info: host.ioBrokerVM connected to Objects and States 2023-03-04 09:56:55.132 - info: host.ioBrokerVM added notifications configuration of host 2023-03-04 09:56:55.139 - error: host.ioBrokerVM Cannot find view "system" for search "instance" 2023-03-04 09:56:55.140 - error: host.ioBrokerVM Could not add notifications config of this host: Could not get notifications setup from instances: Cannot find view "system" 2023-03-04 09:56:55.157 - info: host.ioBrokerVM Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2023-03-04 09:56:55.408 - warn: host.ioBrokerVM logger system.adapter.admin.0.logging was deleted 2023-03-04 09:56:55.408 - warn: host.ioBrokerVM logger system.adapter.javascript.0.logging was deleted 2023-03-04 09:56:55.409 - warn: host.ioBrokerVM logger system.adapter.jarvis.0.logging was deleted 2023-03-04 09:56:55.409 - warn: host.ioBrokerVM logger system.adapter.iot.0.logging was deleted 2023-03-04 09:56:55.419 - error: host.ioBrokerVM Cannot find view "system" for search "host" 2023-03-04 09:56:55.427 - error: host.ioBrokerVM Cannot find view "system" for search "state" 2023-03-04 09:56:55.427 - error: host.ioBrokerVM Cannot find view "system" for search "instance" 2023-03-04 09:56:55.428 - error: host.ioBrokerVM Could not collect system.host.ioBrokerVM states to check for obsolete states: Error: Cannot find view "system" 2023-03-04 09:56:55.429 - error: host.ioBrokerVM _design/system missing - call node iobroker.js setup 2023-03-04 09:56:55.429 - info: host.ioBrokerVM no instances found 2023-03-04 09:56:55.429 - info: host.ioBrokerVM no instances found 2023-03-04 09:56:55.658 - info: host.ioBrokerVM Created UUID: 5e587ae6-2d2c-c2ff-0f87-5bd33a35a917 2023-03-04 09:57:15.583 - info: host.ioBrokerVM iobroker.js-controller version 4.0.24 js-controller starting 2023-03-04 09:57:15.589 - info: host.ioBrokerVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-03-04 09:57:15.590 - info: host.ioBrokerVM hostname: ioBrokerVM, node: v14.19.3 2023-03-04 09:57:15.590 - info: host.ioBrokerVM ip addresses: 192.168.20.20 fe80::a00:27ff:fe73:7859 2023-03-04 09:57:17.691 - error: host.ioBrokerVM-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!Ich kann deinen Frust teilweise nachvollziehen.
(Manchmal) geht es mir ähnlich.Das liegt (zumindest bei mir) daran, dass ich in der Linuxwelt nicht zu Hause bin.
Habe mir durch den ioBroker nach und nach einiges angeeignet.
Hier und da, MUSS man einfach ein ordentliches Tutorial lesen, wenn man selber nicht in der Materie ist.
Das meiste bekommt man auch hier im Forum mit. Lange war zb ein Thread sehr aktuell, wie man auf Bullseye updatet.
Klar, bei Windows bin ich seit Win7 durch Windows Update bis auf Win11.
Bei Windows bekomme ich auch mit, wenn es eine neue Version gibt. Überall hat man Windows 11 gelesen.
Bin auch viel zu spät auf Bullseye. Liegt aber daran, dass ich eben nicht in der Linuxwelt zu Hause bin und nicht auf einschlägigen Websites zu Linux unterwegs bin.Linux lässt einem einfach mehr Freiheiten. Mit diesen muss man lernen umzugehen.
P. S.
Bei Windows hatte ich schon oft genug Probleme nach einem Hardreset. Oder andere Dinge die ich auf meinem Rpi noch nie hatte. -
@thomas-braun Kann das wirklich drei Stunden dauern die paar Adapter zu installieren? Auf einem 24 Kern Intel Xeon mit NVMe SSD?
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Kann das wirklich drei Stunden dauern die paar Adapter zu installieren?
Möglich.
Kann man dem LogFile aber entnehmen. -
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Kann das wirklich drei Stunden dauern die paar Adapter zu installieren?
Möglich.
Kann man dem LogFile aber entnehmen.Siehst du da was? Oder soll ich mal neustarten?
2023-03-04 16:28:12.321 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:12.329 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:28:22.334 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:28:22.335 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:22.338 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:28:32.468 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:28:32.469 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:32.472 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:28:42.481 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:28:42.481 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:42.486 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:28:52.489 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:28:52.489 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:52.497 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:02.502 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:02.503 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:02.512 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:12.516 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:12.516 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:12.524 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:22.526 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:22.527 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:22.533 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:32.544 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:32.544 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:32.549 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:42.557 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:42.557 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:42.563 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:52.575 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:52.575 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:52.578 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:00.134 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 5476 2023-03-04 16:30:01.933 - info: weatherunderground.0 (5476) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:30:02.580 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:02.580 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:02.584 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:12.594 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:12.595 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:12.599 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:22.611 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:22.611 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:22.615 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:30.144 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.234 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.332 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.423 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.510 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.592 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.716 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.810 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.898 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.001 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.120 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.210 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.313 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.406 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.494 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.589 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.676 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.770 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.855 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.054 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.152 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.242 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.330 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.419 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.522 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.607 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.616 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:32.616 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:32.620 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:32.706 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.806 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.901 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.989 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.081 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.175 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.263 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.350 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.440 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.525 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:35.599 - info: weatherunderground.0 (5476) Terminated (NO_ERROR): Without reason 2023-03-04 16:30:36.118 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR) 2023-03-04 16:30:42.622 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:42.622 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:42.627 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:52.639 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:52.641 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:52.648 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:02.658 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:02.659 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:02.668 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:12.669 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:12.669 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:12.676 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:22.677 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:22.677 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:22.681 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:32.683 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:32.684 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:32.689 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:42.706 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:42.706 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:42.713 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:52.720 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:52.720 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:52.725 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:02.725 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:02.726 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:02.742 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:12.749 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:12.749 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:12.755 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:22.756 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:22.756 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:22.764 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:32.773 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:32.773 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:32.777 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:42.779 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:42.779 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:42.783 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:52.788 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:52.788 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:52.792 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:02.793 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:02.793 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:02.800 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:12.806 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:12.807 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:12.812 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:22.819 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:22.820 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:22.827 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:32.830 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:32.831 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:32.834 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:42.848 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:42.848 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:42.853 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:52.863 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:52.864 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:52.871 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:02.882 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:02.882 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:02.886 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:12.887 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:12.888 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:12.897 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:22.899 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:22.900 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:22.904 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:32.982 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:32.983 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:32.987 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:42.991 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:42.992 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:42.997 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:53.007 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:53.008 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:53.014 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:03.041 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:03.042 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:03.048 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:13.049 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:13.050 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:13.055 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:23.056 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:23.057 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:23.061 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:33.063 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:33.064 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:33.070 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:43.087 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:43.087 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:43.090 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:53.097 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:53.098 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:53.101 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:03.102 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:03.102 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:03.109 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:13.127 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:13.127 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:13.130 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:23.143 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:23.144 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:23.149 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:33.151 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:33.151 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:33.155 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:43.157 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:43.157 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:43.163 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:53.168 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:53.169 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:53.174 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:03.178 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:03.178 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:03.184 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:13.194 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:13.195 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:13.202 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:23.207 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:23.208 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:23.212 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:33.222 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:33.222 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:33.228 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:43.242 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:43.243 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:43.253 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:53.270 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:53.270 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:53.274 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:03.296 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:03.297 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:03.300 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:13.301 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:13.301 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:13.304 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:23.326 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:23.327 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:23.330 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:33.335 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:33.335 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:33.343 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:43.352 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:43.352 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:43.356 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:53.360 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:53.360 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:53.365 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:03.365 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:03.366 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:03.374 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:13.376 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:13.377 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:13.380 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:23.390 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:23.390 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:23.394 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:33.406 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:33.407 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:33.413 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:43.423 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:43.424 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:43.427 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:53.434 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:53.434 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:53.438 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:54.986 - info: influxdb.0 (1617) Adapter is disabled => stop 2023-03-04 16:39:55.010 - info: host.iobroker "system.adapter.influxdb.0" disabled 2023-03-04 16:39:55.012 - info: host.iobroker stopInstance system.adapter.influxdb.0 (force=false, process=true) 2023-03-04 16:39:55.211 - info: influxdb.0 (1617) terminating 2023-03-04 16:39:55.212 - info: influxdb.0 (1617) Terminated (NO_ERROR): Without reason 2023-03-04 16:39:55.845 - info: host.iobroker instance system.adapter.influxdb.0 terminated with code 0 (NO_ERROR) 2023-03-04 16:39:55.845 - info: host.iobroker Do not restart adapter system.adapter.influxdb.0 because disabled or deleted 2023-03-04 16:40:00.044 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 5495 2023-03-04 16:40:01.749 - info: weatherunderground.0 (5495) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:40:14.793 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:14.882 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:14.967 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.069 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.116 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.203 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.295 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.396 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.482 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.583 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.681 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.775 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.883 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.977 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.084 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.172 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.254 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.336 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.419 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.519 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.600 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.684 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.885 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.967 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.078 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.163 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.245 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.323 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.411 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.495 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.584 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.713 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.805 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.901 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:18.004 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:18.088 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:20.153 - info: weatherunderground.0 (5495) Terminated (NO_ERROR): Without reason 2023-03-04 16:40:20.689 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR) 2023-03-04 16:50:00.044 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 6242 2023-03-04 16:50:01.851 - info: weatherunderground.0 (6242) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:50:04.521 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.614 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.704 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.791 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.846 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.950 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.058 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.147 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.228 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.314 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.420 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.526 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.646 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.734 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.819 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.919 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.010 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.095 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.193 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.272 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.362 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.459 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.544 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.633 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.733 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.816 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.910 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.993 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.091 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.175 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.273 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.358 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.445 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.524 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.616 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.701 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:09.806 - info: weatherunderground.0 (6242) Terminated (NO_ERROR): Without reason 2023-03-04 16:50:10.326 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR) 2023-03-04 16:53:23.860 - info: admin.0 (913) <== Disconnect system.user.admin from ::ffff:192.168.20.224 admin 2023-03-04 16:53:24.423 - info: admin.0 (913) ==> Connected system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:55:50.169 - info: admin.0 (913) ==> Connected system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:56:02.481 - info: admin.0 (913) <== Disconnect system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:56:02.641 - info: admin.0 (913) ==> Connected system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:56:42.391 - info: admin.0 (913) <== Disconnect system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:56:52.057 - info: host.iobroker "system.adapter.vis.0" enabled 2023-03-04 16:56:52.350 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 1 attempt 2023-03-04 16:56:52.350 - info: host.iobroker iobroker install vis@1.4.16 using installedFrom 2023-03-04 16:56:53.862 - info: host.iobroker iobroker npm-install: host.iobroker Adapter "system.adapter.vis.0" is stopped. 2023-03-04 16:56:53.883 - info: host.iobroker "system.adapter.vis.0" disabled 2023-03-04 16:56:54.387 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:56:54.388 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:57:03.858 - info: vis.0 (6294) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:57:03.991 - info: vis.0 (6294) vis license is OK. 2023-03-04 16:57:04.350 - error: vis.0 (6294) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:57:04.351 - error: vis.0 (6294) unhandled promise rejection: Not exists 2023-03-04 16:57:04.352 - error: vis.0 (6294) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:57:04.352 - error: vis.0 (6294) Not exists 2023-03-04 16:57:04.868 - info: vis.0 (6294) terminating 2023-03-04 16:57:04.868 - warn: vis.0 (6294) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:57:06.030 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:57:07.046 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:57:08.048 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 2 attempt 2023-03-04 16:57:08.049 - info: host.iobroker iobroker install vis@1.4.16 using installedFrom 2023-03-04 16:57:10.144 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:57:10.145 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:57:18.792 - info: vis.0 (6340) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:57:18.920 - info: vis.0 (6340) vis license is OK. 2023-03-04 16:57:19.262 - error: vis.0 (6340) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:57:19.263 - error: vis.0 (6340) unhandled promise rejection: Not exists 2023-03-04 16:57:19.264 - error: vis.0 (6340) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:57:19.265 - error: vis.0 (6340) Not exists 2023-03-04 16:57:19.777 - info: vis.0 (6340) terminating 2023-03-04 16:57:19.778 - warn: vis.0 (6340) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:57:21.003 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:57:22.033 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:57:23.034 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 3 attempt 2023-03-04 16:57:23.035 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-03-04 16:57:25.145 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:57:25.146 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:57:34.116 - info: vis.0 (6386) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:57:34.248 - info: vis.0 (6386) vis license is OK. 2023-03-04 16:57:34.597 - error: vis.0 (6386) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:57:34.598 - error: vis.0 (6386) unhandled promise rejection: Not exists 2023-03-04 16:57:34.600 - error: vis.0 (6386) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:57:34.600 - error: vis.0 (6386) Not exists 2023-03-04 16:57:35.106 - info: vis.0 (6386) terminating 2023-03-04 16:57:35.109 - warn: vis.0 (6386) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:57:36.300 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:57:37.337 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:57:38.342 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 4 attempt 2023-03-04 16:57:38.343 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-03-04 16:57:40.519 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:57:40.520 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:57:49.458 - info: vis.0 (6432) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:57:49.596 - info: vis.0 (6432) vis license is OK. 2023-03-04 16:57:49.928 - error: vis.0 (6432) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:57:49.929 - error: vis.0 (6432) unhandled promise rejection: Not exists 2023-03-04 16:57:49.930 - error: vis.0 (6432) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:57:49.931 - error: vis.0 (6432) Not exists 2023-03-04 16:57:50.442 - info: vis.0 (6432) terminating 2023-03-04 16:57:50.443 - warn: vis.0 (6432) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:57:51.590 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:57:52.628 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:57:53.636 - error: host.iobroker Cannot download and install adapter "vis@1.4.16". To retry it disable/enable the adapter or restart host. Also check the error messages in the log! 2023-03-04 16:57:55.127 - info: host.iobroker "system.adapter.vis.0" enabled 2023-03-04 16:57:55.245 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 1 attempt 2023-03-04 16:57:55.245 - info: host.iobroker iobroker install vis@1.4.16 using installedFrom 2023-03-04 16:57:56.740 - info: host.iobroker iobroker npm-install: host.iobroker Adapter "system.adapter.vis.0" is stopped. 2023-03-04 16:57:56.758 - info: host.iobroker "system.adapter.vis.0" disabled 2023-03-04 16:57:57.326 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:57:57.327 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:58:06.797 - info: vis.0 (6478) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:58:06.917 - info: vis.0 (6478) vis license is OK. 2023-03-04 16:58:07.246 - error: vis.0 (6478) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:58:07.247 - error: vis.0 (6478) unhandled promise rejection: Not exists 2023-03-04 16:58:07.248 - error: vis.0 (6478) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:58:07.249 - error: vis.0 (6478) Not exists 2023-03-04 16:58:07.763 - info: vis.0 (6478) terminating 2023-03-04 16:58:07.764 - warn: vis.0 (6478) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:58:08.938 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:58:09.960 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:58:10.966 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 2 attempt 2023-03-04 16:58:10.967 - info: host.iobroker iobroker install vis@1.4.16 using installedFrom 2023-03-04 16:58:12.943 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:58:12.944 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:58:22.092 - info: vis.0 (6524) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:58:22.211 - info: vis.0 (6524) vis license is OK. 2023-03-04 16:58:22.564 - error: vis.0 (6524) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:58:22.565 - error: vis.0 (6524) unhandled promise rejection: Not exists 2023-03-04 16:58:22.566 - error: vis.0 (6524) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:58:22.567 - error: vis.0 (6524) Not exists 2023-03-04 16:58:23.071 - info: vis.0 (6524) terminating 2023-03-04 16:58:23.072 - warn: vis.0 (6524) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:58:24.245 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:58:25.265 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:58:26.265 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 3 attempt 2023-03-04 16:58:26.265 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-03-04 16:58:28.392 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:58:28.393 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:58:37.480 - info: vis.0 (6572) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:58:37.612 - info: vis.0 (6572) vis license is OK. 2023-03-04 16:58:37.942 - error: vis.0 (6572) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:58:37.943 - error: vis.0 (6572) unhandled promise rejection: Not exists 2023-03-04 16:58:37.944 - error: vis.0 (6572) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:58:37.945 - error: vis.0 (6572) Not exists 2023-03-04 16:58:38.454 - info: vis.0 (6572) terminating 2023-03-04 16:58:38.456 - warn: vis.0 (6572) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:58:39.667 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:58:40.689 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:58:41.701 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 4 attempt 2023-03-04 16:58:41.701 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-03-04 16:58:43.732 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:58:43.733 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:58:52.870 - info: vis.0 (6619) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:58:52.999 - info: vis.0 (6619) vis license is OK. 2023-03-04 16:58:53.369 - error: vis.0 (6619) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:58:53.369 - error: vis.0 (6619) unhandled promise rejection: Not exists 2023-03-04 16:58:53.371 - error: vis.0 (6619) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:58:53.372 - error: vis.0 (6619) Not exists 2023-03-04 16:58:53.884 - info: vis.0 (6619) terminating 2023-03-04 16:58:53.884 - warn: vis.0 (6619) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:58:55.051 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:58:56.089 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:58:57.122 - error: host.iobroker Cannot download and install adapter "vis@1.4.16". To retry it disable/enable the adapter or restart host. Also check the error messages in the log! 2023-03-04 17:00:00.042 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 6630 2023-03-04 17:00:01.866 - info: weatherunderground.0 (6630) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 17:00:07.534 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:07.631 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:07.722 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:07.822 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:07.926 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.032 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.124 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.210 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.299 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.386 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.495 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.582 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.699 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.783 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.889 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.977 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.072 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.168 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.261 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.353 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.476 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.567 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.676 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.759 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.866 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.948 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.033 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.124 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.248 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.348 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.448 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.541 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.627 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.717 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.823 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.910 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:12.985 - info: weatherunderground.0 (6630) Terminated (NO_ERROR): Without reason 2023-03-04 17:00:13.505 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR) 2023-03-04 17:10:00.041 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 6647 2023-03-04 17:10:01.883 - info: weatherunderground.0 (6647) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 17:10:32.042 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.130 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.219 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.314 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.422 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.509 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.611 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.706 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.789 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.888 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.978 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.077 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.181 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.278 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.367 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.460 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.546 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.636 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.721 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.809 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.906 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.992 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.078 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.164 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.262 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.348 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.448 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.539 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.638 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.739 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.830 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.917 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:35.001 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:35.081 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:35.165 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:35.248 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:37.319 - info: weatherunderground.0 (6647) Terminated (NO_ERROR): Without reason 2023-03-04 17:10:37.837 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR) -
Ich kann deinen Frust teilweise nachvollziehen.
(Manchmal) geht es mir ähnlich.Das liegt (zumindest bei mir) daran, dass ich in der Linuxwelt nicht zu Hause bin.
Habe mir durch den ioBroker nach und nach einiges angeeignet.
Hier und da, MUSS man einfach ein ordentliches Tutorial lesen, wenn man selber nicht in der Materie ist.
Das meiste bekommt man auch hier im Forum mit. Lange war zb ein Thread sehr aktuell, wie man auf Bullseye updatet.
Klar, bei Windows bin ich seit Win7 durch Windows Update bis auf Win11.
Bei Windows bekomme ich auch mit, wenn es eine neue Version gibt. Überall hat man Windows 11 gelesen.
Bin auch viel zu spät auf Bullseye. Liegt aber daran, dass ich eben nicht in der Linuxwelt zu Hause bin und nicht auf einschlägigen Websites zu Linux unterwegs bin.Linux lässt einem einfach mehr Freiheiten. Mit diesen muss man lernen umzugehen.
P. S.
Bei Windows hatte ich schon oft genug Probleme nach einem Hardreset. Oder andere Dinge die ich auf meinem Rpi noch nie hatte.@david-g
Danke! :blush:
Genau, ich bin bei Linux leider auch nicht zu Hause und komme trotz 20 Jahren herumbasteln damit noch immer nicht richtig rein. Nur schon das Chaos mit Root, su, su -, sudoers, sudo usw. ist jedes Mal ein riesen Stolperstein. Und warum es jetzt einen Unterschied machen soll ob man ein root-Passwort setzt oder nicht erschliesst sich mir wirklich nicht. Bis nach der Installation nur mal wieder SSH funktioniert, damit ich Befehle reinkopieren kann, statt sie ins Fenster der VM abtippen zu müssen, dauert ewig.
Ja, ich google jedes Problem und jede Fehlermeldung und finde dutzende verschiedene Anleitungen, die dann aber alle irgendwie nicht funktionieren. Ich wollte z.B. nur mal Bash wieder auf Englisch einstellen statt auf Deutsch und habe nach der vierten Anleitung, die nur Fehlermeldungen produziert hatte, aufgegeben.
Eine aktuelle Influxdb2-Anleitung habe ich nicht gefunden. Die offizielle Anleitung für Debian von influxdb selbst stimmt nicht, weil die Quellen fürs Installieren per apt bei Debian fehlen. Aktuell kann ich keinen User anlegen.
ioBroker ist ja eine geniale Software und ich bin jedem dankbar, der daran weiterentwickelt. Aber für mich als User ist es ein Graus, wenn das System alle paar Monate nicht mehr funktioniert, weil irgendein Update was gebrochen hat (oft sogar absichtlich!) oder weil nach einem Neustart wieder irgendwelche Files korrupt sind. Alle zwei Jahre das OS neu installieren, weil es veraltet ist, sollte auch nicht sein müssen. Das ist eine Appliance. Die muss einfach laufen, egal auf welcher Version sie ist. Die Mikrowelle funktioniert auch mit der ursprünglich installierten Firmware zuverlässig.
Gibt es für sowas keinen bezahlten Support? Kann ich nicht jemandem 100€ bezahlen, dafür dass er mir ioBroker auf einer VM installiert und das Backup sauber zurückspielt? Das würde mir viel Aufwand ersparen. Weil ich aktuell durch LongCovid einen starken Brainfog habe und jede Konzentration extrem anstrengend ist, wäre sowas auch für meine Gesundheit besser.
-
Siehst du da was? Oder soll ich mal neustarten?
2023-03-04 16:28:12.321 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:12.329 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:28:22.334 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:28:22.335 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:22.338 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:28:32.468 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:28:32.469 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:32.472 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:28:42.481 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:28:42.481 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:42.486 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:28:52.489 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:28:52.489 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:28:52.497 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:02.502 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:02.503 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:02.512 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:12.516 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:12.516 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:12.524 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:22.526 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:22.527 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:22.533 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:32.544 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:32.544 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:32.549 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:42.557 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:42.557 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:42.563 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:29:52.575 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:29:52.575 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:29:52.578 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:00.134 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 5476 2023-03-04 16:30:01.933 - info: weatherunderground.0 (5476) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:30:02.580 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:02.580 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:02.584 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:12.594 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:12.595 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:12.599 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:22.611 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:22.611 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:22.615 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:30.144 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.234 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.332 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.423 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.510 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.592 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.716 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.810 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:30.898 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.001 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.120 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.210 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.313 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.406 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.494 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.589 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.676 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.770 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:31.855 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.054 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.152 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.242 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.330 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.419 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.522 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.607 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.616 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:32.616 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:32.620 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:32.706 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.806 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.901 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:32.989 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.081 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.175 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.263 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.350 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.440 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:33.525 - info: weatherunderground.0 (5476) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:30:35.599 - info: weatherunderground.0 (5476) Terminated (NO_ERROR): Without reason 2023-03-04 16:30:36.118 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR) 2023-03-04 16:30:42.622 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:42.622 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:42.627 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:30:52.639 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:30:52.641 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:30:52.648 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:02.658 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:02.659 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:02.668 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:12.669 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:12.669 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:12.676 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:22.677 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:22.677 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:22.681 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:32.683 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:32.684 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:32.689 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:42.706 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:42.706 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:42.713 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:31:52.720 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:31:52.720 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:31:52.725 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:02.725 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:02.726 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:02.742 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:12.749 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:12.749 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:12.755 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:22.756 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:22.756 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:22.764 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:32.773 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:32.773 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:32.777 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:42.779 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:42.779 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:42.783 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:32:52.788 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:32:52.788 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:32:52.792 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:02.793 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:02.793 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:02.800 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:12.806 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:12.807 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:12.812 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:22.819 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:22.820 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:22.827 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:32.830 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:32.831 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:32.834 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:42.848 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:42.848 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:42.853 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:33:52.863 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:33:52.864 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:33:52.871 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:02.882 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:02.882 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:02.886 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:12.887 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:12.888 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:12.897 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:22.899 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:22.900 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:22.904 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:32.982 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:32.983 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:32.987 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:42.991 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:42.992 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:42.997 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:34:53.007 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:34:53.008 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:34:53.014 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:03.041 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:03.042 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:03.048 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:13.049 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:13.050 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:13.055 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:23.056 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:23.057 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:23.061 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:33.063 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:33.064 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:33.070 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:43.087 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:43.087 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:43.090 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:35:53.097 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:35:53.098 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:35:53.101 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:03.102 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:03.102 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:03.109 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:13.127 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:13.127 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:13.130 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:23.143 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:23.144 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:23.149 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:33.151 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:33.151 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:33.155 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:43.157 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:43.157 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:43.163 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:36:53.168 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:36:53.169 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:36:53.174 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:03.178 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:03.178 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:03.184 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:13.194 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:13.195 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:13.202 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:23.207 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:23.208 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:23.212 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:33.222 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:33.222 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:33.228 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:43.242 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:43.243 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:43.253 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:37:53.270 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:37:53.270 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:37:53.274 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:03.296 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:03.297 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:03.300 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:13.301 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:13.301 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:13.304 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:23.326 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:23.327 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:23.330 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:33.335 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:33.335 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:33.343 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:43.352 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:43.352 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:43.356 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:38:53.360 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:38:53.360 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:38:53.365 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:03.365 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:03.366 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:03.374 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:13.376 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:13.377 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:13.380 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:23.390 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:23.390 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:23.394 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:33.406 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:33.407 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:33.413 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:43.423 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:43.424 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:43.427 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:53.434 - info: influxdb.0 (1617) Connecting http://localhost:8086/ ... 2023-03-04 16:39:53.434 - info: influxdb.0 (1617) Influx DB Version used: 1.x 2023-03-04 16:39:53.438 - error: influxdb.0 (1617) Error: {"code":"unauthorized","message":"Unauthorized"} 2023-03-04 16:39:54.986 - info: influxdb.0 (1617) Adapter is disabled => stop 2023-03-04 16:39:55.010 - info: host.iobroker "system.adapter.influxdb.0" disabled 2023-03-04 16:39:55.012 - info: host.iobroker stopInstance system.adapter.influxdb.0 (force=false, process=true) 2023-03-04 16:39:55.211 - info: influxdb.0 (1617) terminating 2023-03-04 16:39:55.212 - info: influxdb.0 (1617) Terminated (NO_ERROR): Without reason 2023-03-04 16:39:55.845 - info: host.iobroker instance system.adapter.influxdb.0 terminated with code 0 (NO_ERROR) 2023-03-04 16:39:55.845 - info: host.iobroker Do not restart adapter system.adapter.influxdb.0 because disabled or deleted 2023-03-04 16:40:00.044 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 5495 2023-03-04 16:40:01.749 - info: weatherunderground.0 (5495) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:40:14.793 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:14.882 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:14.967 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.069 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.116 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.203 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.295 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.396 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.482 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.583 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.681 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.775 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.883 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:15.977 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.084 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.172 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.254 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.336 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.419 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.519 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.600 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.684 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.885 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:16.967 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.078 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.163 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.245 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.323 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.411 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.495 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.584 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.713 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.805 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:17.901 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:18.004 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:18.088 - info: weatherunderground.0 (5495) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:40:20.153 - info: weatherunderground.0 (5495) Terminated (NO_ERROR): Without reason 2023-03-04 16:40:20.689 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR) 2023-03-04 16:50:00.044 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 6242 2023-03-04 16:50:01.851 - info: weatherunderground.0 (6242) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:50:04.521 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.614 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.704 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.791 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.846 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:04.950 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.058 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.147 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.228 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.314 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.420 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.526 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.646 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.734 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.819 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:05.919 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.010 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.095 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.193 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.272 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.362 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.459 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.544 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.633 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.733 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.816 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.910 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:06.993 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.091 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.175 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.273 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.358 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.445 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.524 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.616 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:07.701 - info: weatherunderground.0 (6242) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 16:50:09.806 - info: weatherunderground.0 (6242) Terminated (NO_ERROR): Without reason 2023-03-04 16:50:10.326 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR) 2023-03-04 16:53:23.860 - info: admin.0 (913) <== Disconnect system.user.admin from ::ffff:192.168.20.224 admin 2023-03-04 16:53:24.423 - info: admin.0 (913) ==> Connected system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:55:50.169 - info: admin.0 (913) ==> Connected system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:56:02.481 - info: admin.0 (913) <== Disconnect system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:56:02.641 - info: admin.0 (913) ==> Connected system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:56:42.391 - info: admin.0 (913) <== Disconnect system.user.admin from ::ffff:192.168.20.224 2023-03-04 16:56:52.057 - info: host.iobroker "system.adapter.vis.0" enabled 2023-03-04 16:56:52.350 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 1 attempt 2023-03-04 16:56:52.350 - info: host.iobroker iobroker install vis@1.4.16 using installedFrom 2023-03-04 16:56:53.862 - info: host.iobroker iobroker npm-install: host.iobroker Adapter "system.adapter.vis.0" is stopped. 2023-03-04 16:56:53.883 - info: host.iobroker "system.adapter.vis.0" disabled 2023-03-04 16:56:54.387 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:56:54.388 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:57:03.858 - info: vis.0 (6294) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:57:03.991 - info: vis.0 (6294) vis license is OK. 2023-03-04 16:57:04.350 - error: vis.0 (6294) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:57:04.351 - error: vis.0 (6294) unhandled promise rejection: Not exists 2023-03-04 16:57:04.352 - error: vis.0 (6294) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:57:04.352 - error: vis.0 (6294) Not exists 2023-03-04 16:57:04.868 - info: vis.0 (6294) terminating 2023-03-04 16:57:04.868 - warn: vis.0 (6294) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:57:06.030 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:57:07.046 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:57:08.048 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 2 attempt 2023-03-04 16:57:08.049 - info: host.iobroker iobroker install vis@1.4.16 using installedFrom 2023-03-04 16:57:10.144 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:57:10.145 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:57:18.792 - info: vis.0 (6340) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:57:18.920 - info: vis.0 (6340) vis license is OK. 2023-03-04 16:57:19.262 - error: vis.0 (6340) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:57:19.263 - error: vis.0 (6340) unhandled promise rejection: Not exists 2023-03-04 16:57:19.264 - error: vis.0 (6340) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:57:19.265 - error: vis.0 (6340) Not exists 2023-03-04 16:57:19.777 - info: vis.0 (6340) terminating 2023-03-04 16:57:19.778 - warn: vis.0 (6340) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:57:21.003 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:57:22.033 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:57:23.034 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 3 attempt 2023-03-04 16:57:23.035 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-03-04 16:57:25.145 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:57:25.146 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:57:34.116 - info: vis.0 (6386) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:57:34.248 - info: vis.0 (6386) vis license is OK. 2023-03-04 16:57:34.597 - error: vis.0 (6386) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:57:34.598 - error: vis.0 (6386) unhandled promise rejection: Not exists 2023-03-04 16:57:34.600 - error: vis.0 (6386) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:57:34.600 - error: vis.0 (6386) Not exists 2023-03-04 16:57:35.106 - info: vis.0 (6386) terminating 2023-03-04 16:57:35.109 - warn: vis.0 (6386) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:57:36.300 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:57:37.337 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:57:38.342 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 4 attempt 2023-03-04 16:57:38.343 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-03-04 16:57:40.519 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:57:40.520 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:57:49.458 - info: vis.0 (6432) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:57:49.596 - info: vis.0 (6432) vis license is OK. 2023-03-04 16:57:49.928 - error: vis.0 (6432) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:57:49.929 - error: vis.0 (6432) unhandled promise rejection: Not exists 2023-03-04 16:57:49.930 - error: vis.0 (6432) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:57:49.931 - error: vis.0 (6432) Not exists 2023-03-04 16:57:50.442 - info: vis.0 (6432) terminating 2023-03-04 16:57:50.443 - warn: vis.0 (6432) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:57:51.590 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:57:52.628 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:57:53.636 - error: host.iobroker Cannot download and install adapter "vis@1.4.16". To retry it disable/enable the adapter or restart host. Also check the error messages in the log! 2023-03-04 16:57:55.127 - info: host.iobroker "system.adapter.vis.0" enabled 2023-03-04 16:57:55.245 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 1 attempt 2023-03-04 16:57:55.245 - info: host.iobroker iobroker install vis@1.4.16 using installedFrom 2023-03-04 16:57:56.740 - info: host.iobroker iobroker npm-install: host.iobroker Adapter "system.adapter.vis.0" is stopped. 2023-03-04 16:57:56.758 - info: host.iobroker "system.adapter.vis.0" disabled 2023-03-04 16:57:57.326 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:57:57.327 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:58:06.797 - info: vis.0 (6478) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:58:06.917 - info: vis.0 (6478) vis license is OK. 2023-03-04 16:58:07.246 - error: vis.0 (6478) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:58:07.247 - error: vis.0 (6478) unhandled promise rejection: Not exists 2023-03-04 16:58:07.248 - error: vis.0 (6478) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:58:07.249 - error: vis.0 (6478) Not exists 2023-03-04 16:58:07.763 - info: vis.0 (6478) terminating 2023-03-04 16:58:07.764 - warn: vis.0 (6478) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:58:08.938 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:58:09.960 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:58:10.966 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 2 attempt 2023-03-04 16:58:10.967 - info: host.iobroker iobroker install vis@1.4.16 using installedFrom 2023-03-04 16:58:12.943 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:58:12.944 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:58:22.092 - info: vis.0 (6524) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:58:22.211 - info: vis.0 (6524) vis license is OK. 2023-03-04 16:58:22.564 - error: vis.0 (6524) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:58:22.565 - error: vis.0 (6524) unhandled promise rejection: Not exists 2023-03-04 16:58:22.566 - error: vis.0 (6524) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:58:22.567 - error: vis.0 (6524) Not exists 2023-03-04 16:58:23.071 - info: vis.0 (6524) terminating 2023-03-04 16:58:23.072 - warn: vis.0 (6524) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:58:24.245 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:58:25.265 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:58:26.265 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 3 attempt 2023-03-04 16:58:26.265 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-03-04 16:58:28.392 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:58:28.393 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:58:37.480 - info: vis.0 (6572) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:58:37.612 - info: vis.0 (6572) vis license is OK. 2023-03-04 16:58:37.942 - error: vis.0 (6572) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:58:37.943 - error: vis.0 (6572) unhandled promise rejection: Not exists 2023-03-04 16:58:37.944 - error: vis.0 (6572) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:58:37.945 - error: vis.0 (6572) Not exists 2023-03-04 16:58:38.454 - info: vis.0 (6572) terminating 2023-03-04 16:58:38.456 - warn: vis.0 (6572) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:58:39.667 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:58:40.689 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:58:41.701 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 4 attempt 2023-03-04 16:58:41.701 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-03-04 16:58:43.732 - info: host.iobroker iobroker npm-install: NPM version: 8.19.3 2023-03-04 16:58:43.733 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-03-04 16:58:52.870 - info: vis.0 (6619) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v16.19.1, js-controller: 4.0.24 2023-03-04 16:58:52.999 - info: vis.0 (6619) vis license is OK. 2023-03-04 16:58:53.369 - error: vis.0 (6619) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-03-04 16:58:53.369 - error: vis.0 (6619) unhandled promise rejection: Not exists 2023-03-04 16:58:53.371 - error: vis.0 (6619) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at processImmediate (node:internal/timers:468:21) 2023-03-04 16:58:53.372 - error: vis.0 (6619) Not exists 2023-03-04 16:58:53.884 - info: vis.0 (6619) terminating 2023-03-04 16:58:53.884 - warn: vis.0 (6619) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-03-04 16:58:55.051 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-03-04 16:58:56.089 - info: host.iobroker iobroker npm-install: exit 25 2023-03-04 16:58:57.122 - error: host.iobroker Cannot download and install adapter "vis@1.4.16". To retry it disable/enable the adapter or restart host. Also check the error messages in the log! 2023-03-04 17:00:00.042 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 6630 2023-03-04 17:00:01.866 - info: weatherunderground.0 (6630) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 17:00:07.534 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:07.631 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:07.722 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:07.822 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:07.926 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.032 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.124 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.210 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.299 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.386 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.495 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.582 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.699 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.783 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.889 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:08.977 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.072 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.168 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.261 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.353 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.476 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.567 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.676 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.759 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.866 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:09.948 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.033 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.124 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.248 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.348 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.448 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.541 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.627 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.717 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.823 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:10.910 - info: weatherunderground.0 (6630) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:00:12.985 - info: weatherunderground.0 (6630) Terminated (NO_ERROR): Without reason 2023-03-04 17:00:13.505 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR) 2023-03-04 17:10:00.041 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 6647 2023-03-04 17:10:01.883 - info: weatherunderground.0 (6647) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.19.1, js-controller: 4.0.24 2023-03-04 17:10:32.042 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.0h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.130 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.1h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.219 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.2h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.314 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.3h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.422 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.4h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.509 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.5h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.611 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.6h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.706 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.7h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.789 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.8h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.888 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.9h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:32.978 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.10h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.077 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.11h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.181 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.12h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.278 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.13h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.367 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.14h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.460 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.15h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.546 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.16h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.636 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.17h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.721 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.18h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.809 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.19h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.906 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.20h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:33.992 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.21h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.078 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.22h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.164 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.23h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.262 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.24h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.348 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.25h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.448 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.26h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.539 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.27h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.638 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.28h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.739 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.29h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.830 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.30h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:34.917 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.31h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:35.001 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.32h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:35.081 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.33h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:35.165 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.34h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:35.248 - info: weatherunderground.0 (6647) State value to set for "weatherunderground.0.forecastHourly.35h.precipitation" has to be type "value.precipitation" but received type "number" 2023-03-04 17:10:37.319 - info: weatherunderground.0 (6647) Terminated (NO_ERROR): Without reason 2023-03-04 17:10:37.837 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR)Ich sehe da, dass es mit der Autorisierung an einer influxdb v1 Probleme gibt.
Hättest du nicht oben geschrieben du seist auf V2 unterwegs?
-
@david-g
Danke! :blush:
Genau, ich bin bei Linux leider auch nicht zu Hause und komme trotz 20 Jahren herumbasteln damit noch immer nicht richtig rein. Nur schon das Chaos mit Root, su, su -, sudoers, sudo usw. ist jedes Mal ein riesen Stolperstein. Und warum es jetzt einen Unterschied machen soll ob man ein root-Passwort setzt oder nicht erschliesst sich mir wirklich nicht. Bis nach der Installation nur mal wieder SSH funktioniert, damit ich Befehle reinkopieren kann, statt sie ins Fenster der VM abtippen zu müssen, dauert ewig.
Ja, ich google jedes Problem und jede Fehlermeldung und finde dutzende verschiedene Anleitungen, die dann aber alle irgendwie nicht funktionieren. Ich wollte z.B. nur mal Bash wieder auf Englisch einstellen statt auf Deutsch und habe nach der vierten Anleitung, die nur Fehlermeldungen produziert hatte, aufgegeben.
Eine aktuelle Influxdb2-Anleitung habe ich nicht gefunden. Die offizielle Anleitung für Debian von influxdb selbst stimmt nicht, weil die Quellen fürs Installieren per apt bei Debian fehlen. Aktuell kann ich keinen User anlegen.
ioBroker ist ja eine geniale Software und ich bin jedem dankbar, der daran weiterentwickelt. Aber für mich als User ist es ein Graus, wenn das System alle paar Monate nicht mehr funktioniert, weil irgendein Update was gebrochen hat (oft sogar absichtlich!) oder weil nach einem Neustart wieder irgendwelche Files korrupt sind. Alle zwei Jahre das OS neu installieren, weil es veraltet ist, sollte auch nicht sein müssen. Das ist eine Appliance. Die muss einfach laufen, egal auf welcher Version sie ist. Die Mikrowelle funktioniert auch mit der ursprünglich installierten Firmware zuverlässig.
Gibt es für sowas keinen bezahlten Support? Kann ich nicht jemandem 100€ bezahlen, dafür dass er mir ioBroker auf einer VM installiert und das Backup sauber zurückspielt? Das würde mir viel Aufwand ersparen. Weil ich aktuell durch LongCovid einen starken Brainfog habe und jede Konzentration extrem anstrengend ist, wäre sowas auch für meine Gesundheit besser.
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Die Mikrowelle funktioniert auch mit der ursprünglich installierten Firmware zuverlässig.
Äpfel - Birnen...
-
@david-g
Danke! :blush:
Genau, ich bin bei Linux leider auch nicht zu Hause und komme trotz 20 Jahren herumbasteln damit noch immer nicht richtig rein. Nur schon das Chaos mit Root, su, su -, sudoers, sudo usw. ist jedes Mal ein riesen Stolperstein. Und warum es jetzt einen Unterschied machen soll ob man ein root-Passwort setzt oder nicht erschliesst sich mir wirklich nicht. Bis nach der Installation nur mal wieder SSH funktioniert, damit ich Befehle reinkopieren kann, statt sie ins Fenster der VM abtippen zu müssen, dauert ewig.
Ja, ich google jedes Problem und jede Fehlermeldung und finde dutzende verschiedene Anleitungen, die dann aber alle irgendwie nicht funktionieren. Ich wollte z.B. nur mal Bash wieder auf Englisch einstellen statt auf Deutsch und habe nach der vierten Anleitung, die nur Fehlermeldungen produziert hatte, aufgegeben.
Eine aktuelle Influxdb2-Anleitung habe ich nicht gefunden. Die offizielle Anleitung für Debian von influxdb selbst stimmt nicht, weil die Quellen fürs Installieren per apt bei Debian fehlen. Aktuell kann ich keinen User anlegen.
ioBroker ist ja eine geniale Software und ich bin jedem dankbar, der daran weiterentwickelt. Aber für mich als User ist es ein Graus, wenn das System alle paar Monate nicht mehr funktioniert, weil irgendein Update was gebrochen hat (oft sogar absichtlich!) oder weil nach einem Neustart wieder irgendwelche Files korrupt sind. Alle zwei Jahre das OS neu installieren, weil es veraltet ist, sollte auch nicht sein müssen. Das ist eine Appliance. Die muss einfach laufen, egal auf welcher Version sie ist. Die Mikrowelle funktioniert auch mit der ursprünglich installierten Firmware zuverlässig.
Gibt es für sowas keinen bezahlten Support? Kann ich nicht jemandem 100€ bezahlen, dafür dass er mir ioBroker auf einer VM installiert und das Backup sauber zurückspielt? Das würde mir viel Aufwand ersparen. Weil ich aktuell durch LongCovid einen starken Brainfog habe und jede Konzentration extrem anstrengend ist, wäre sowas auch für meine Gesundheit besser.
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Alle zwei Jahre das OS neu installieren, weil es veraltet ist, sollte auch nicht sein müssen.
Muss es auch nicht. Mit entsprechend Ahnung geht das auch so. Und es gibt ja auch Linux-Geschmacksrichtungen als 'rolling release'. Die empfehle ich aber nicht als Basis für einen Server.
-
@david-g
Danke! :blush:
Genau, ich bin bei Linux leider auch nicht zu Hause und komme trotz 20 Jahren herumbasteln damit noch immer nicht richtig rein. Nur schon das Chaos mit Root, su, su -, sudoers, sudo usw. ist jedes Mal ein riesen Stolperstein. Und warum es jetzt einen Unterschied machen soll ob man ein root-Passwort setzt oder nicht erschliesst sich mir wirklich nicht. Bis nach der Installation nur mal wieder SSH funktioniert, damit ich Befehle reinkopieren kann, statt sie ins Fenster der VM abtippen zu müssen, dauert ewig.
Ja, ich google jedes Problem und jede Fehlermeldung und finde dutzende verschiedene Anleitungen, die dann aber alle irgendwie nicht funktionieren. Ich wollte z.B. nur mal Bash wieder auf Englisch einstellen statt auf Deutsch und habe nach der vierten Anleitung, die nur Fehlermeldungen produziert hatte, aufgegeben.
Eine aktuelle Influxdb2-Anleitung habe ich nicht gefunden. Die offizielle Anleitung für Debian von influxdb selbst stimmt nicht, weil die Quellen fürs Installieren per apt bei Debian fehlen. Aktuell kann ich keinen User anlegen.
ioBroker ist ja eine geniale Software und ich bin jedem dankbar, der daran weiterentwickelt. Aber für mich als User ist es ein Graus, wenn das System alle paar Monate nicht mehr funktioniert, weil irgendein Update was gebrochen hat (oft sogar absichtlich!) oder weil nach einem Neustart wieder irgendwelche Files korrupt sind. Alle zwei Jahre das OS neu installieren, weil es veraltet ist, sollte auch nicht sein müssen. Das ist eine Appliance. Die muss einfach laufen, egal auf welcher Version sie ist. Die Mikrowelle funktioniert auch mit der ursprünglich installierten Firmware zuverlässig.
Gibt es für sowas keinen bezahlten Support? Kann ich nicht jemandem 100€ bezahlen, dafür dass er mir ioBroker auf einer VM installiert und das Backup sauber zurückspielt? Das würde mir viel Aufwand ersparen. Weil ich aktuell durch LongCovid einen starken Brainfog habe und jede Konzentration extrem anstrengend ist, wäre sowas auch für meine Gesundheit besser.
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Alle zwei Jahre das OS neu installieren, weil es veraltet ist, sollte auch nicht sein müssen.
Sind es bei Debian lts nicht sogar 5 Jahre?
-
@david-g
Danke! :blush:
Genau, ich bin bei Linux leider auch nicht zu Hause und komme trotz 20 Jahren herumbasteln damit noch immer nicht richtig rein. Nur schon das Chaos mit Root, su, su -, sudoers, sudo usw. ist jedes Mal ein riesen Stolperstein. Und warum es jetzt einen Unterschied machen soll ob man ein root-Passwort setzt oder nicht erschliesst sich mir wirklich nicht. Bis nach der Installation nur mal wieder SSH funktioniert, damit ich Befehle reinkopieren kann, statt sie ins Fenster der VM abtippen zu müssen, dauert ewig.
Ja, ich google jedes Problem und jede Fehlermeldung und finde dutzende verschiedene Anleitungen, die dann aber alle irgendwie nicht funktionieren. Ich wollte z.B. nur mal Bash wieder auf Englisch einstellen statt auf Deutsch und habe nach der vierten Anleitung, die nur Fehlermeldungen produziert hatte, aufgegeben.
Eine aktuelle Influxdb2-Anleitung habe ich nicht gefunden. Die offizielle Anleitung für Debian von influxdb selbst stimmt nicht, weil die Quellen fürs Installieren per apt bei Debian fehlen. Aktuell kann ich keinen User anlegen.
ioBroker ist ja eine geniale Software und ich bin jedem dankbar, der daran weiterentwickelt. Aber für mich als User ist es ein Graus, wenn das System alle paar Monate nicht mehr funktioniert, weil irgendein Update was gebrochen hat (oft sogar absichtlich!) oder weil nach einem Neustart wieder irgendwelche Files korrupt sind. Alle zwei Jahre das OS neu installieren, weil es veraltet ist, sollte auch nicht sein müssen. Das ist eine Appliance. Die muss einfach laufen, egal auf welcher Version sie ist. Die Mikrowelle funktioniert auch mit der ursprünglich installierten Firmware zuverlässig.
Gibt es für sowas keinen bezahlten Support? Kann ich nicht jemandem 100€ bezahlen, dafür dass er mir ioBroker auf einer VM installiert und das Backup sauber zurückspielt? Das würde mir viel Aufwand ersparen. Weil ich aktuell durch LongCovid einen starken Brainfog habe und jede Konzentration extrem anstrengend ist, wäre sowas auch für meine Gesundheit besser.
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Nur schon das Chaos mit Root, su, su -, sudoers, sudo usw. ist jedes Mal ein riesen Stolperstein.
Was für ein Chaos? Das ist ganz einfach: Als root direkt wird sich nicht angemeldet und alle Befehle die tiefer ins System reingehen werden mit sudo eingeleitet. So einfach ist das.
-
@thomas-braun Kann das wirklich drei Stunden dauern die paar Adapter zu installieren? Auf einem 24 Kern Intel Xeon mit NVMe SSD?
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Intel Xeon
oooh, da scheint es schon öfter Probleme mit gegeben zu haben.
-
Ich sehe da, dass es mit der Autorisierung an einer influxdb v1 Probleme gibt.
Hättest du nicht oben geschrieben du seist auf V2 unterwegs?
@thomas-braun sagte in Failed to lock DB file nach Festplatte voll.:
Ich sehe da, dass es mit der Autorisierung an einer influxdb v1 Probleme gibt.
Hättest du nicht oben geschrieben du seist auf V2 unterwegs?
Als ob ich das wüsste :-D Ich habe danach mit apt install influxdb2 installiert. Was muss ich nun tun? Wie kann ich einen User einrichten und die HTTP-Verbindung aktivieren? Ich finde dazu keine Anleitungen.
-
@thomas-braun sagte in Failed to lock DB file nach Festplatte voll.:
Ich sehe da, dass es mit der Autorisierung an einer influxdb v1 Probleme gibt.
Hättest du nicht oben geschrieben du seist auf V2 unterwegs?
Als ob ich das wüsste :-D Ich habe danach mit apt install influxdb2 installiert. Was muss ich nun tun? Wie kann ich einen User einrichten und die HTTP-Verbindung aktivieren? Ich finde dazu keine Anleitungen.
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Als ob ich das wüsste
Und woher sollen potentielle Helfer das dann wissen?
So kann das nix werden. Du musst schon wissen was da auf deinem System los ist.apt policy influxdb*sagt?
-
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Nur schon das Chaos mit Root, su, su -, sudoers, sudo usw. ist jedes Mal ein riesen Stolperstein.
Was für ein Chaos? Das ist ganz einfach: Als root direkt wird sich nicht angemeldet und alle Befehle die tiefer ins System reingehen werden mit sudo eingeleitet. So einfach ist das.
@thomas-braun sagte in Failed to lock DB file nach Festplatte voll.:
Was für ein Chaos? Das ist ganz einfach: Als root direkt wird sich nicht angemeldet und alle Befehle die tiefer ins System reingehen werden mit sudo eingeleitet. So einfach ist das.
Haha nein das stimmt eben leider ganz und gar nicht, sonst hätte ich ja keine Probleme gehabt! :blush:
Sudo ging nicht. auch nicht, als ich als root den user in die sudoers-Liste eingetragen hatte.
Ich musste manuel in der sudoers Textdatei den Root-Eintrag kopieren und auf den User abändern, erst dann ging Sudo.
Su ging auch nicht, da wurden keine Befehle gefunden, weil anschienend da absichtlich die Pfadvariable nicht gesetzt wird? Erst "su -" mit Bindestrich dahinter ging. Aber sowas findet man ja auch erst nach vielem Googeln. Intiutiv und konsistent ist das sicher nicht.
Und wenn Linux so flexibel ist, warum darf ich dann nicht so arbeiten wie ich will? Ich will immer als root arbeiten. Ich will keine extra Sicherheitsschicht. Warum bevormundet mich das System? Warum ist das system nicht so robust und transparent, dass beide Arbeitsweisen funktionieren? Das ist für mich ein grober Designfehler, der das Arbeiten unnötig umständlich und fehleranfällig macht. Das allein hat mich heute wieder eine Stunde gekostet.
-
@thomas-braun sagte in Failed to lock DB file nach Festplatte voll.:
Ich sehe da, dass es mit der Autorisierung an einer influxdb v1 Probleme gibt.
Hättest du nicht oben geschrieben du seist auf V2 unterwegs?
Als ob ich das wüsste :-D Ich habe danach mit apt install influxdb2 installiert. Was muss ich nun tun? Wie kann ich einen User einrichten und die HTTP-Verbindung aktivieren? Ich finde dazu keine Anleitungen.
@chrisprefect sagte in Failed to lock DB file nach Festplatte voll.:
Ich finde dazu keine Anleitungen.
Dürfte bei influxdb zu finden sein. Die haben da soweit ich es sehe eine umfangreiche Dokumentation.
652
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge