Hallo,
ist es normal, dass keine Updates vom Adapter im ioBroker angezeigt werden?
Ich musste die github Adresse als manuelle Installation vor längerer Zeit hinzufügen, aber darüber werden keine Updates angezeigt.
Hat dafür jemand einen Tipp, sonst müsste man alle 4-6 Wochen den Adapter im git prüfen, Version abgleichen und dann manuell drüber installieren.
Falls es dafür einen schöneren Workaround gibt, wäre das schöner 
Danke für den Adapter, ich habe zwei EV Charger.
Alle 3-4 Monate kommt es mal vor, dass beide EV Charger die Kommunikation zum SHM verlieren und dann nicht laden können. Ich bekomme es nur per Mail mit, dass es einen Kommunkationsfehler gab.
Ich habe von SMA bereits schon jeweils einen neuen EVcharger erhalten. Abhilfe schafft nur ein Reboot der Wallbox. Die Kommunkation wurde auch von Broadcast auf Uni umgestellt, bei den Switchen den LAG auch so.
Über die Web UI gibt es bei den Parametern den Schalter "Geräteneustarte auslösen" (Parameter.Sys.DevRstr).
Kannst du das mit deinem Adapter aufnehmen? Dann könnte ich alle 4 Wochen beide WB per Script neustarten lassen.
Besten Dank für die schnellen Antworten.
Es hat geklappt
@dp20eic - ja den reboot, nachdem erfolglosen nodjs update habe ich auch gesehen als ich es gepostet habe. Reboot vor dem Fixer ausgeführt
Dann den NodeJS Fixer von @Thomas-Braun durchlaufen lassen und es ist jetzt die korrekte Version drauf, anschließend noch den iob fix ausgeführt.
Anbei der iob diag nachdem Fixer, der iobroker Dienst war noch gestoppt. Vielen Dank :
======================= SUMMARY =======================
v.2023-10-10
Static hostname: iobroker
Icon name: computer-vm
Chassis: vm
Virtualization: vmware
Operating System: Ubuntu 22.04.3 LTS
Kernel: Linux 5.15.0-86-generic
Architecture: x86-64
Hardware Vendor: VMware, Inc.
Hardware Model: VMware Virtual Platform
Installation: vmware
Kernel: x86_64
Userland: amd64
Timezone: Europe/Berlin (CEST, +0200)
User-ID: 1000
X-Server: false
Boot Target: graphical.target
Pending OS-Updates: 0
Pending iob updates: 0
Nodejs-Installation: /usr/bin/nodejs v18.18.1
/usr/bin/node v18.18.1
/usr/bin/npm 9.8.1
/usr/bin/npx 9.8.1
/usr/bin/corepack 0.19.0
Recommended versions are nodejs 18.18.1 and npm 9.8.1
Your nodejs installation is correct
MEMORY:
total used free shared buff/cache available
Mem: 3.9G 390M 2.0G 1.0M 1.5G 3.2G
Swap: 2.0G 0B 2.0G
Total: 6.0G 390M 4.1G
Active iob-Instances: 1
Active repo(s): stable
ioBroker Core: js-controller 5.0.12
admin 6.10.1
ioBroker Status: iobroker is not running on this host.
Objects type: jsonl
States type: jsonl
Status admin and web instance:
system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 192.168.1.13, run as: admin
Objects: 25498
States: 22364
Size of iob-Database:
15M /opt/iobroker/iobroker-data/objects.jsonl
9.7M /opt/iobroker/iobroker-data/objects.json.migrated
9.7M /opt/iobroker/iobroker-data/objects.json.bak.migrated
0 /opt/iobroker/iobroker-data/objects.json.broken
7.7M /opt/iobroker/iobroker-data/states.jsonl
4.3M /opt/iobroker/iobroker-data/states.json.migrated
4.3M /opt/iobroker/iobroker-data/states.json.bak.migrated
0 /opt/iobroker/iobroker-data/states.json.broken
=================== END OF SUMMARY ====================
=== Mark text until here for copying ===
Hallo,
ich aktualisiere nodejs 2-3 im Jahr. Die aktuelle Version die ich einsetze ist die 18.17.1.
Jetzt wird mir im Intro angezeigt, dass die 18.18.1 verfügbar ist.
Folgenermaßen habe ich das Update versucht auszuführen, es bleibt aber bei 18.17.1:
iobroker stop
cd /opt/iobroker
sudo npm cache verify
sudo chown -R iobroker /opt/iobroker
sudo apt update -y && sudo apt upgrade -y
sudo apt-get purge nodejs -y && sudo apt-get autoremove -y && sudo apt-get autoclean -y
sudo curl -sL https://deb.nodesource.com/setup_18.x | sudo bash -
sudo apt-get install -y nodejs
sudo chown -R iobroker /opt/iobroker
curl -sL https://iobroker.net/fix.sh | bash -
npm install -y iobroker.js-controller --unsafe-perm --production --save --prefix
npm rebuild
iobroker update
iobroker upgrade self
iobroker upgrade
iobroker start
iob diag hat folgende Ausgabe ergeben:
======== Start marking the full check here =========
Skript v.2023-10-10
*** BASE SYSTEM ***
Static hostname: iobroker
Icon name: computer-vm
Chassis: vm
Virtualization: vmware
Operating System: Ubuntu 22.04.3 LTS
Kernel: Linux 5.15.0-84-generic
Architecture: x86-64
Hardware Vendor: VMware, Inc.
Hardware Model: VMware Virtual Platform
model name : Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Docker : false
Virtualization : vmware
Kernel : x86_64
Userland : amd64
Systemuptime and Load:
14:01:11 up 14 days, 2:53, 2 users, load average: 1.77, 1.01, 0.66
CPU threads: 1
This system needs to be REBOOTED!
*** Time and Time Zones ***
Local time: Thu 2023-10-12 14:01:11 CEST
Universal time: Thu 2023-10-12 12:01:11 UTC
RTC time: Thu 2023-10-12 12:01:11
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
*** User and Groups ***
matze
/home/matze
matze adm cdrom sudo dip plugdev lxd iobroker
*** X-Server-Setup ***
X-Server: false
Desktop:
Terminal: tty
Boot Target: graphical.target
*** MEMORY ***
total used free shared buff/cache available
Mem: 3.9G 2.0G 111M 0.0K 1.8G 1.6G
Swap: 2.0G 44M 2.0G
Total: 6.0G 2.0G 2.1G
3912 M total memory
1983 M used memory
833 M active memory
2486 M inactive memory
111 M free memory
233 M buffer memory
1584 M swap cache
2047 M total swap
44 M used swap
2003 M free swap
*** FAILED SERVICES ***
UNIT LOAD ACTIVE SUB DESCRIPTION
* motioneye.service loaded failed failed motionEye Server
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
*** FILESYSTEM ***
Filesystem Type Size Used Avail Use% Mounted on
tmpfs tmpfs 392M 1.4M 390M 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv ext4 24G 17G 6.2G 73% /
tmpfs tmpfs 2.0G 16K 2.0G 1% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda2 ext4 974M 291M 617M 33% /boot
tmpfs tmpfs 392M 4.0K 392M 1% /run/user/1000
Messages concerning ext4 filesystem in dmesg:
[Thu Sep 28 11:07:25 2023] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[Thu Sep 28 11:07:29 2023] EXT4-fs (dm-0): re-mounted. Opts: (null). Quota mode: none.
[Thu Sep 28 11:07:36 2023] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[Thu Sep 28 11:12:32 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Thu Sep 28 11:12:32 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Thu Sep 28 11:12:32 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Fri Sep 29 12:50:11 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Fri Sep 29 12:50:11 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Fri Sep 29 12:50:11 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Sat Sep 30 14:28:07 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Sat Sep 30 14:28:07 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Sat Sep 30 14:28:07 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Sun Oct 1 16:06:02 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Sun Oct 1 16:06:02 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Sun Oct 1 16:06:02 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Mon Oct 2 17:43:58 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Mon Oct 2 17:43:58 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Mon Oct 2 17:43:58 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Tue Oct 3 19:21:53 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Tue Oct 3 19:21:53 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Tue Oct 3 19:21:53 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Wed Oct 4 20:59:49 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Wed Oct 4 20:59:49 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Wed Oct 4 20:59:49 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Thu Oct 5 22:37:44 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Thu Oct 5 22:37:44 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Thu Oct 5 22:37:44 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Sat Oct 7 00:15:40 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Sat Oct 7 00:15:40 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Sat Oct 7 00:15:40 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Sun Oct 8 01:53:35 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Sun Oct 8 01:53:35 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Sun Oct 8 01:53:35 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Mon Oct 9 03:31:31 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Mon Oct 9 03:31:31 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Mon Oct 9 03:31:31 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Tue Oct 10 05:09:26 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Tue Oct 10 05:09:26 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Tue Oct 10 05:09:26 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Wed Oct 11 06:47:22 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Wed Oct 11 06:47:22 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Wed Oct 11 06:47:22 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
[Thu Oct 12 08:25:17 2023] EXT4-fs (dm-0): error count since last fsck: 13
[Thu Oct 12 08:25:17 2023] EXT4-fs (dm-0): initial error at time 1629469500: ext4_journal_check_start:61
[Thu Oct 12 08:25:17 2023] EXT4-fs (dm-0): last error at time 1629475362: ext4_reserve_inode_write:5875
Show mounted filesystems \(real ones only\):
TARGET SOURCE FSTYPE OPTIONS
/ /dev/mapper/ubuntu--vg-ubuntu--lv ext4 rw,relatime
|-/snap/motioneye/373 /dev/loop0 squashfs ro,nodev,relatime,errors=continue
|-/snap/core/16091 /dev/loop1 squashfs ro,nodev,relatime,errors=continue
|-/snap/core18/2785 /dev/loop2 squashfs ro,nodev,relatime,errors=continue
|-/snap/core18/2790 /dev/loop3 squashfs ro,nodev,relatime,errors=continue
|-/snap/core20/2015 /dev/loop5 squashfs ro,nodev,relatime,errors=continue
|-/snap/core20/1974 /dev/loop4 squashfs ro,nodev,relatime,errors=continue
|-/snap/core22/858 /dev/loop6 squashfs ro,nodev,relatime,errors=continue
|-/snap/core22/864 /dev/loop7 squashfs ro,nodev,relatime,errors=continue
|-/snap/docker/2856 /dev/loop8 squashfs ro,nodev,relatime,errors=continue
|-/snap/docker/2893 /dev/loop9 squashfs ro,nodev,relatime,errors=continue
|-/snap/gh/502 /dev/loop10 squashfs ro,nodev,relatime,errors=continue
|-/snap/lxd/24061 /dev/loop12 squashfs ro,nodev,relatime,errors=continue
|-/snap/lxd/23991 /dev/loop11 squashfs ro,nodev,relatime,errors=continue
|-/boot /dev/sda2 ext4 rw,relatime
|-/snap/motioneye/371 /dev/loop14 squashfs ro,nodev,relatime,errors=continue
`-/snap/core/16202 /dev/loop15 squashfs ro,nodev,relatime,errors=continue
Files in neuralgic directories:
/var:
4.8G /var/
2.6G /var/log
2.5G /var/log/journal/8d218b88b25d4f278859f3d025addb15
2.5G /var/log/journal
2.1G /var/lib
Archived and active journals take up 2.4G in the file system.
/opt/iobroker/backups:
150M /opt/iobroker/backups/
/opt/iobroker/iobroker-data:
537M /opt/iobroker/iobroker-data/
354M /opt/iobroker/iobroker-data/files
123M /opt/iobroker/iobroker-data/backup-objects
57M /opt/iobroker/iobroker-data/files/echarts
53M /opt/iobroker/iobroker-data/files/javascript.admin
The five largest files in iobroker-data are:
35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map
23M /opt/iobroker/iobroker-data/files/echarts/static/js/main.eb0afecd.js.map
21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js.map
17M /opt/iobroker/iobroker-data/files/echarts/preview/static/js/main.1b04901d.js.map
15M /opt/iobroker/iobroker-data/objects.jsonl
USB-Devices by-id:
USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id':
find: '/dev/serial/by-id/': No such file or directory
*** NodeJS-Installation ***
/home/iobroker/.diag.sh: line 277: nodejs: command not found
/usr/bin/node v18.17.1
/usr/bin/npm 9.6.7
/usr/bin/npx 9.6.7
/usr/bin/corepack 0.18.0
/home/iobroker/.diag.sh: line 288: nodejs: command not found
*** nodejs is NOT correctly installed ***
nodejs:
Installed: 18.17.1-deb-1nodesource1
Candidate: 18.17.1-deb-1nodesource1
Version table:
*** 18.17.1-deb-1nodesource1 500
500 https://deb.nodesource.com/node_18.x jammy/main amd64 Packages
100 /var/lib/dpkg/status
12.22.9~dfsg-1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
Temp directories causing npm8 problem: 0
No problems detected
Errors in npm tree:
*** ioBroker-Installation ***
ioBroker Status
iobroker is running on this host.
Objects type: jsonl
States type: jsonl
Core adapters versions
js-controller: 5.0.12
admin: 6.10.1
javascript: 7.1.4
Adapters from github: 5
Adapter State
+ system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.alexa2.0 : alexa2 : iobroker - enabled
system.adapter.apple-find-me.0 : apple-find-me : iobroker - disabled
+ system.adapter.backitup.0 : backitup : iobroker - enabled
system.adapter.coronavirus-statistics.0 : coronavirus-statistics: iobroker - disabled
system.adapter.daswetter.0 : daswetter : iobroker - enabled
system.adapter.devices.0 : devices : iobroker - enabled
system.adapter.discovery.0 : discovery : iobroker - disabled
system.adapter.dwd.0 : dwd : iobroker - enabled
system.adapter.echarts.0 : echarts : iobroker - enabled
system.adapter.fb-checkpresence.0 : fb-checkpresence : iobroker - disabled
system.adapter.flot.0 : flot : iobroker - enabled
+ system.adapter.followthesun.0 : followthesun : iobroker - enabled
system.adapter.fritzbox.0 : fritzbox : iobroker - disabled
+ system.adapter.fritzdect.1 : fritzdect : iobroker - enabled
system.adapter.fullybrowser.0 : fullybrowser : iobroker - disabled
+ system.adapter.geofency.0 : geofency : iobroker - enabled, port: 7999, bind: 0.0.0.0
+ system.adapter.history.0 : history : iobroker - enabled
+ system.adapter.hm-rega.0 : hm-rega : iobroker - enabled
+ system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0
system.adapter.ical.0 : ical : iobroker - enabled
system.adapter.icons-mfd-png.0 : icons-mfd-png : iobroker - enabled
system.adapter.icons-mfd-svg.0 : icons-mfd-svg : iobroker - enabled
+ system.adapter.info.0 : info : iobroker - enabled
+ system.adapter.javascript.0 : javascript : iobroker - enabled
system.adapter.kodi.0 : kodi : iobroker - disabled, port: 9090
+ system.adapter.nina.0 : nina : iobroker - enabled
+ system.adapter.parcel.0 : parcel : iobroker - enabled
+ system.adapter.ping.0 : ping : iobroker - enabled
+ system.adapter.pvforecast.0 : pvforecast : iobroker - enabled
+ system.adapter.samsung.0 : samsung : iobroker - enabled
+ system.adapter.sayit.0 : sayit : iobroker - enabled
system.adapter.sbfspot.0 : sbfspot : iobroker - disabled
system.adapter.semp.0 : semp : iobroker - enabled
+ system.adapter.shuttercontrol.0 : shuttercontrol : iobroker - enabled
system.adapter.sma-ev-charger.0 : sma-ev-charger : iobroker - enabled
system.adapter.sma-ev-charger.1 : sma-ev-charger : iobroker - enabled
+ system.adapter.spotify-premium.0 : spotify-premium : iobroker - enabled
+ system.adapter.tankerkoenig.0 : tankerkoenig : iobroker - enabled
system.adapter.tronity.0 : tronity : iobroker - enabled
system.adapter.tvspielfilm.0 : tvspielfilm : iobroker - enabled
+ system.adapter.viessmannapi.0 : viessmannapi : iobroker - enabled
system.adapter.vis-bars.0 : vis-bars : iobroker - enabled
system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : iobroker - enabled
+ system.adapter.vis-inventwo.0 : vis-inventwo : iobroker - enabled
system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : iobroker - enabled
system.adapter.vis-keyboard.0 : vis-keyboard : iobroker - enabled
system.adapter.vis-knob.0 : vis-knob : iobroker - enabled
system.adapter.vis-map.0 : vis-map : iobroker - enabled
system.adapter.vis-material-advanced.0 : vis-material-advanced : iobroker - enabled
system.adapter.vis-players.0 : vis-players : iobroker - enabled
system.adapter.vis-plumb.0 : vis-plumb : iobroker - enabled
system.adapter.vis-timeandweather.0 : vis-timeandweather : iobroker - enabled
system.adapter.vis-weather.0 : vis-weather : iobroker - enabled
system.adapter.vis.0 : vis : iobroker - enabled
+ system.adapter.vw-connect.0 : vw-connect : iobroker - enabled
system.adapter.wallpanel.0 : wallpanel : iobroker - enabled
+ system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 192.168.1.13, run as: admin
+ system.adapter.yahka.0 : yahka : iobroker - enabled
+ instance is alive
Enabled adapters with bindings
+ system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.geofency.0 : geofency : iobroker - enabled, port: 7999, bind: 0.0.0.0
+ system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0
+ system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 192.168.1.13, run as: admin
ioBroker-Repositories
stable : http://download.iobroker.net/sources-dist.json
beta : http://download.iobroker.net/sources-dist-latest.json
Active repo(s): stable
Installed ioBroker-Instances
Used repository: stable
Adapter "admin" : 6.10.1 , installed 6.10.1
Adapter "alexa2" : 3.25.2 , installed 3.25.2
Adapter "apcups" : 1.0.15 , installed 1.0.15
Adapter "apple-find-me": 0.0.14 , installed 0.0.14
Adapter "backitup" : 2.8.1 , installed 2.8.1
Adapter "coronavirus-statistics": 0.8.7, installed 0.8.7
Adapter "daswetter" : 3.1.10 , installed 3.1.10
Adapter "devices" : 1.1.5 , installed 1.1.5
Adapter "discovery" : 3.1.0 , installed 3.1.0
Adapter "dwd" : 2.8.5 , installed 2.8.5
Adapter "echarts" : 1.5.1 , installed 1.5.1
Adapter "fb-checkpresence": 1.2.2 , installed 1.2.2
Adapter "flot" : 1.12.0 , installed 1.12.0
Adapter "followthesun" : 0.4.2 , installed 0.4.2
Adapter "fritzbox" : 0.5.0 , installed 0.5.0
Adapter "fritzdect" : 2.3.1 , installed 2.3.1
Adapter "fullybrowser" : 2.1.2 , installed 2.1.2
Adapter "geofency" : 1.2.4 , installed 1.2.4
Adapter "history" : 2.2.6 , installed 2.2.6
Adapter "hm-rega" : 3.0.47 , installed 3.0.47
Adapter "hm-rpc" : 1.15.19 , installed 1.15.19
Adapter "ical" : 1.13.3 , installed 1.13.3
Adapter "icons-mfd-png": 1.1.0 , installed 1.1.0
Adapter "icons-mfd-svg": 1.1.0 , installed 1.1.0
Adapter "info" : 2.0.0 , installed 2.0.0
Adapter "javascript" : 7.1.4 , installed 7.1.4
Controller "js-controller": 5.0.12 , installed 5.0.12
Adapter "kodi" : 3.0.0 , installed 3.0.0
Adapter "nina" : 0.0.25 , installed 0.0.25
Adapter "parcel" : 0.0.27 , installed 0.0.27
Adapter "ping" : 1.6.2 , installed 1.6.2
Adapter "pvforecast" : 2.8.1 , installed 2.8.1
Adapter "samsung" : 0.5.11 , installed 0.5.11
Adapter "sayit" : 3.0.5 , installed 3.0.5
Adapter "sbfspot" : 4.1.6 , installed 4.1.6
Adapter "semp" : 1.3.4 , installed 1.3.4
Adapter "shuttercontrol": 1.6.2 , installed 1.6.2
Adapter "simple-api" : 2.7.2 , installed 2.7.2
Adapter "sma-em" : 1.0.0 , installed 1.0.0
Adapter "socketio" : 6.5.5 , installed 6.5.5
Adapter "spotify-premium": 1.2.2 , installed 1.2.2
Adapter "tankerkoenig" : 3.3.7 , installed 3.3.7
Adapter "tronity" : 1.1.1 , installed 1.1.1
Adapter "tvspielfilm" : 2.0.4 , installed 2.0.4
Adapter "viessmannapi" : 2.0.9 , installed 2.0.9
Adapter "vis" : 1.4.16 , installed 1.4.16
Adapter "vis-bars" : 0.1.4 , installed 0.1.4
Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1
Adapter "vis-inventwo" : 3.3.3 , installed 3.3.3
Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12
Adapter "vis-keyboard" : 0.0.2 , installed 0.0.2
Adapter "vis-map" : 1.0.4 , installed 1.0.4
Adapter "vis-material-advanced": 1.7.4, installed 1.7.4
Adapter "vis-players" : 0.1.6 , installed 0.1.6
Adapter "vis-plumb" : 1.0.2 , installed 1.0.2
Adapter "vis-timeandweather": 1.2.2, installed 1.2.2
Adapter "vis-weather" : 2.5.6 , installed 2.5.6
Adapter "vw-connect" : 0.0.67 , installed 0.1.5
Adapter "wallpanel" : 0.3.11 , installed 0.3.11
Adapter "web" : 6.1.2 , installed 6.1.2
Adapter "ws" : 2.5.5 , installed 2.5.5
Adapter "yahka" : 1.0.3 , installed 1.0.3
Objects and States
Please stand by - This may take a while
Objects: 24770
States: 22029
*** OS-Repositories and Updates ***
Hit:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 https://dl.yarnpkg.com/debian stable InRelease
Hit:3 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease
Get:4 https://dl.cloudsmith.io/public/evcc/stable/deb/ubuntu focal InRelease [5121 B]
Hit:5 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:6 https://deb.nodesource.com/node_18.x jammy InRelease [4563 B]
Hit:7 http://de.archive.ubuntu.com/ubuntu jammy-security InRelease
Fetched 9684 B in 1s (10.7 kB/s)
Reading package lists...
Pending Updates: 0
*** Listening Ports ***
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:8085 0.0.0.0:* LISTEN 0 9540529 728685/motion
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 101 13372507 1042450/systemd-res
tcp 0 0 127.0.0.1:7999 0.0.0.0:* LISTEN 0 9540525 728685/motion
tcp 0 0 192.168.1.13:8082 0.0.0.0:* LISTEN 1001 13395313 1047882/io.web.0
tcp 0 0 192.168.1.13:2001 0.0.0.0:* LISTEN 1001 13392908 1047109/io.hm-rpc.0
tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 0 9540538 728607/python2
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 13372069 1042408/sshd: /usr/
tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 13392490 1047017/iobroker.js
tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 13392497 1047017/iobroker.js
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 18600 1/systemd
tcp6 0 0 :::8081 :::* LISTEN 1001 13392638 1047035/io.admin.0
tcp6 0 0 :::9765 :::* LISTEN 1001 13398558 1048438/io.semp.0
tcp6 0 0 :::36245 :::* LISTEN 1001 13394747 1047460/io.yahka.0
tcp6 0 0 :::7070 :::* LISTEN 119 1708371 129496/evcc
tcp6 0 0 :::4712 :::* LISTEN 119 1706696 129496/evcc
tcp6 0 0 :::22 :::* LISTEN 0 13372071 1042408/sshd: /usr/
tcp6 0 0 :::111 :::* LISTEN 0 18606 1/systemd
udp 0 0 0.0.0.0:56035 0.0.0.0:* 111 13372002 1042399/avahi-daemo
udp 0 0 0.0.0.0:5353 0.0.0.0:* 111 13372000 1042399/avahi-daemo
udp 0 0 0.0.0.0:5353 0.0.0.0:* 119 1708346 129496/evcc
udp 0 0 0.0.0.0:9522 0.0.0.0:* 119 1706690 129496/evcc
udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 13398560 1048438/io.semp.0
udp 0 0 127.0.0.53:53 0.0.0.0:* 101 13372506 1042450/systemd-res
udp 0 0 0.0.0.0:111 0.0.0.0:* 0 18603 1/systemd
udp6 0 0 :::5353 :::* 119 1708347 129496/evcc
udp6 0 0 :::5353 :::* 111 13372001 1042399/avahi-daemo
udp6 0 0 :::49060 :::* 111 13372003 1042399/avahi-daemo
udp6 0 0 :::111 :::* 0 18609 1/systemd
*** Log File - Last 25 Lines ***
2023-10-12 14:01:41.387 - info: host.iobroker instance system.adapter.semp.0 started with pid 1048438
2023-10-12 14:01:43.454 - info: semp.0 (1048438) starting. Version 1.3.4 in /opt/iobroker/node_modules/iobroker.semp, node: v18.17.1, js-controller: 5.0.12
2023-10-12 14:01:43.484 - info: semp.0 (1048438) device created F-34248195-000000000001-00 Waschmaschine
2023-10-12 14:01:43.485 - info: semp.0 (1048438) device created F-34248195-000000000002-00 Trockner
2023-10-12 14:01:43.485 - info: semp.0 (1048438) device created F-34248195-000000000003-00 TV-Wohnzimmer
2023-10-12 14:01:43.486 - info: semp.0 (1048438) device created F-34248195-000000000004-00 Rasenmäher
2023-10-12 14:01:43.486 - info: semp.0 (1048438) device created F-34248195-000000000005-00 Dunstabzugshaube
2023-10-12 14:01:43.486 - info: semp.0 (1048438) device created F-34248195-000000000006-00 Geschirrspüler
2023-10-12 14:01:43.487 - info: semp.0 (1048438) device created F-34248195-000000000007-00 Backofen
2023-10-12 14:01:45.435 - info: host.iobroker instance system.adapter.tronity.0 started with pid 1048483
2023-10-12 14:01:46.588 - info: semp.0 (1048438) adapter discovered by SHM
2023-10-12 14:01:46.743 - info: tronity.0 (1048483) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.tronity, node: v18.17.1, js-controller: 5.0.12
2023-10-12 14:01:47.217 - error: tronity.0 (1048483) HTTPError: Response code 405 (Method Not Allowed)
2023-10-12 14:01:49.357 - info: host.iobroker instance system.adapter.echarts.0 started with pid 1048511
2023-10-12 14:01:50.627 - info: echarts.0 (1048511) starting. Version 1.5.1 in /opt/iobroker/node_modules/iobroker.echarts, node: v18.17.1, js-controller: 5.0.12
2023-10-12 14:01:53.494 - info: host.iobroker instance system.adapter.sma-ev-charger.0 started with pid 1048556
2023-10-12 14:01:55.801 - info: sma-ev-charger.0 (1048556) starting. Version 0.1.6 (non-npm: zapccu/ioBroker.sma-ev-charger#dd59086615a4de52a174134675152390833f47b4) in /opt/iobroker/node_modules/iobroker.sma-ev-charger, node: v18.17.1, js-controller: 5.0.12
2023-10-12 14:01:55.820 - info: sma-ev-charger.0 (1048556) Initial login
2023-10-12 14:01:57.390 - info: host.iobroker instance system.adapter.sma-ev-charger.1 started with pid 1049001
2023-10-12 14:01:58.359 - info: sma-ev-charger.0 (1048556) Connected to 192.168.1.110
2023-10-12 14:01:58.359 - info: sma-ev-charger.0 (1048556) Token refresh interval = 3540 seconds
2023-10-12 14:01:58.359 - info: sma-ev-charger.0 (1048556) Initial update of charger information
2023-10-12 14:01:58.889 - info: sma-ev-charger.1 (1049001) starting. Version 0.1.6 (non-npm: zapccu/ioBroker.sma-ev-charger#dd59086615a4de52a174134675152390833f47b4) in /opt/iobroker/node_modules/iobroker.sma-ev-charger, node: v18.17.1, js-controller: 5.0.12
2023-10-12 14:01:58.969 - info: sma-ev-charger.0 (1048556) Initial update of charger parameters
2023-10-12 14:01:59.291 - info: sma-ev-charger.1 (1049001) Initial login
============ Mark until here for C&P =============
iob diag has finished.
Habt Ihr eine Idee?
Viele Grüße
Matthias
Hallo zusammen,
ich habe vier Geräte in die PING Überwachung gegeben, da die Wallbox ab und zu Probleme macht wollte ich die Leitungen mal prüfen.
Was sagt der Wert RPS aus?
1000 hz und 632 hz? Oder sind das Prozentsätze von dem PING Ergebnis?
Viele Grüße
Matthias
gelöst, es gab vor einigen Monaten mal Probleme mit der Zeitzone.
Da habe ich unseren beiden Kalender auf UTC-0 gestellt, dann waren Anfang des Jahres die Einträge in der richtigen Zeit drin.
Habe sie jetzt wieder auf "Berlin" gesetzt und neugestartet und zack waren beiden Kalender wieder da.
Jetzt kann geschlossen werden, danke an alle
Es ist leider nicht gelöst, ich habe zwei Exchange Kalender. Den von meiner Frau und meinen.
Es wird nur einer abgerufen (der von meiner Frau), in dem großen Debug Log finde ich keinen Fehler.
Wenn jemand interesse an meiner ICS Datei hat (die nicht verarbeitet wird), dann kann ich die gerne per PN zur Verfügung stellen.
@glasfaser said in iCal - Events aus dem Exchange werden nicht mehr abgerufen:
Empfohlen ist Node 14 / NPM 6
Danke für den Tipp. Ich habe nodejs deinstalliert und mit Version 14.19. neu installiert, NPM ist 6.14.17.
Wird nur ein Kalender abgerufen.
Wenn jemand Interesse an meiner ICS Datei vom Exchange 2019 hat, kann er sich gerne bei mir melden dann stelle ich sie per PN bereit.
ical.0 2022-05-23 10:17:57.324 info Terminated (NO_ERROR): Without reason
ical.0 2022-05-23 10:17:52.081 info processing URL: Caro https://mail.xxxxxx.de/owa/calendar/c0e6cc2e31414bdbb97884913f16fcc1@xxxxxx.de/0372ae6441fc4accac5f951210ec990d7499262095505457187/calendar.ics
ical.0 2022-05-23 10:17:51.524 info starting. Version 1.12.1 in /opt/iobroker/node_modules/iobroker.ical, node: v14.19.3, js-controller: 4.0.23
Guten Morgen,
seit einigen Tagen liest er zumindest den Kalender meiner Frau wieder ein, habe mir gerade mal das Debug Log angesehen. Ich bin davon ausgegangen, wenn ich auswähle "21 Tage" die Cal Daten abrufen, dass er auch nur die verarbeitet.
Im Log sind jetzt alle enthalten, meine Kalender Daten werden am anfang auch eingelesen, aber nicht verarbeitet. Mein Kalender ist noch größer, als der von meiner Frau.
Ich habe das Log mal hochgeladen, da es als Text zu Lang war:
log_kalender.txt
edit: Unter Log "Info" steht, es wird nur der Kalender meiner Frau verarbeitet:
Wenn ich die URL aus meinem Kalender nehme, wird sie heruntergeladen (87KB)
ical.0 2022-05-23 06:47:59.220 info Terminated (NO_ERROR): Without reason
ical.0 2022-05-23 06:47:54.074 info processing URL: Caro https://mail........../calendar.ics
ical.0 2022-05-23 06:47:53.599 info starting. Version 1.12.1 in /opt/iobroker/node_modules/iobroker.ical, node: v16.14.2, js-controller: 4.0.23
MOD-EDIT: private Daten entfernt
Die beiden Cache Dateien werden auch heruntergeladen in der Verzeichnis /opt/iobroker/node_modules/iobroker.ical/
Ich habe die Cache Files mal bei https://icalendar.org/validator.html hochgeladen, da werden mir 230x Errors ausgegeben (alle den gleichen Inhalt, nur andere Zeilen):
Invalid TZID value or missing VTIMEZONE component ("(UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien") near line # 79Reference: 3.2.19. Time Zone Identifier
Invalid TZID value or missing VTIMEZONE component ("(UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien") near line # 79Reference: 3.2.19. Time Zone Identifier
Invalid TZID value or missing VTIMEZONE component ("(UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien") near line # 103Reference: 3.2.19. Time Zone Identifier
Aber das ist ja eine Zeitzone die vom Exchange oder vom Outlook kommmt.
Einen Ausschnitt aus der ICS Datei hatte ich 3 Post darüber mal angehangen. https://forum.iobroker.net/post/801427
Kann damit der ICAL Adapter Probleme haben?
Ich kann meine ICS Datei gerne per PN zur Verfügung stellen.
