NEWS
Viessmann Adapter keine Verbindung mehr
Error/Bug
23
Beiträge
6
Kommentatoren
1.2k
Aufrufe
5
Watching
-
@thomas-braun ich habe das selbe Problem, leider hat da deine Lösung nichts gebracht und ich habe immer noch keine Verbindung. Hast du noch weitere tips?
@hugi sagte in Viessmann Adapter keine Verbindung mehr:
leider hat da deine Lösung nichts gebracht
Das war keine 'Lösung' für das Problem, das war nur die Hilfestellung um das System auf einem aktuellen Stand zu haben.
(Was aber wiederum die Ausgangsbasis für eine Problemsuche oder -lösung ist) -
@hugi sagte in Viessmann Adapter keine Verbindung mehr:
leider hat da deine Lösung nichts gebracht
Das war keine 'Lösung' für das Problem, das war nur die Hilfestellung um das System auf einem aktuellen Stand zu haben.
(Was aber wiederum die Ausgangsbasis für eine Problemsuche oder -lösung ist)@thomas-braun @Samson71
Ich habe den iob diag ausgeführt und die Fehlermeldung aus dem Log rauskopiert. Ich hoffe das hilft beim Blick in die Glaskugel. ;-){"error":"invalid_request","error_description":"Invalid request: Missing or empty code parameter"} AxiosError: Request failed with status code 400========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 12 (bookworm) Static hostname: raspberrypi Icon name: computer Kernel: Linux 6.6.51+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.0 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 10:45:47 up 18:27, 3 users, load average: 0.29, 0.16, 0.11 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Mon 2025-10-06 10:45:47 CEST Universal time: Mon 2025-10-06 08:45:47 UTC RTC time: Mon 2025-10-06 08:45:47 Time zone: Europe/Zurich (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Display-Manager: x lightdm.service - Light Display Manager Desktop: Session: tty System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix' *** MEMORY *** total used free shared buff/cache available Mem: 8.4G 2.5G 4.3G 5.9M 1.7G 5.9G Swap: 209M 0B 209M Total: 8.7G 2.5G 4.5G Active iob-Instances: 19 8052 M total memory 2424 M used memory 2254 M active memory 1252 M inactive memory 4101 M free memory 283 M buffer memory 1344 M swap cache 199 M total swap 0 M used swap 199 M free swap *** top - Table Of Processes *** top - 10:45:47 up 18:27, 3 users, load average: 0.29, 0.16, 0.11 Tasks: 207 total, 2 running, 205 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 8052.3 total, 4101.2 free, 2424.8 used, 1628.8 buff/cache MiB Swap: 200.0 total, 200.0 free, 0.0 used. 5627.6 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * lightdm.service loaded failed failed Light Display Manager 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. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.8G 0 3.8G 0% /dev tmpfs tmpfs 1.6G 5.4M 1.6G 1% /run /dev/mmcblk0p2 ext4 29G 11G 17G 39% / tmpfs tmpfs 4.0G 0 4.0G 0% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 78M 433M 16% /boot/firmware tmpfs tmpfs 806M 144K 806M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sun Oct 5 16:18:35 2025] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe smsc95xx.macaddr=2C:CF:67:1F:04:A3 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=3f5521b5-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Sun Oct 5 16:18:35 2025] EXT4-fs (mmcblk0p2): mounted filesystem cb6f0e18-5add-4177-ab98-e9f0235e06b3 ro with ordered data mode. Quota mode: none. [Sun Oct 5 16:18:36 2025] EXT4-fs (mmcblk0p2): re-mounted cb6f0e18-5add-4177-ab98-e9f0235e06b3 r/w. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 3.2G /var/ 2.1G /var/cache/apt 2.1G /var/cache 2.0G /var/cache/apt/archives 648M /var/log Archived and active journals take up 646.7M in the file system. /opt/iobroker/backups: 37M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 339M /opt/iobroker/iobroker-data/ 131M /opt/iobroker/iobroker-data/files 94M /opt/iobroker/iobroker-data/backup-objects 47M /opt/iobroker/iobroker-data/files/admin.admin 46M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets The five largest files in iobroker-data are: 58M /opt/iobroker/iobroker-data/objects.jsonl 56M /opt/iobroker/iobroker-data/states.jsonl 8.6M /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BBu8-Y_o.js 4.6M /opt/iobroker/iobroker-data/files/javascript.admin/vs/language/typescript/tsWorker.js 4.4M /opt/iobroker/iobroker-data/files/yahka.admin/yahka.admin.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.20.0 /usr/bin/node v22.20.0 /usr/bin/npm 10.9.3 /usr/bin/npx 10.9.3 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.20.0-1nodesource1 Candidate: 22.20.0-1nodesource1 Version table: *** 22.20.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.19.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: raspberrypi raspberrypi (version: 7.0.7, hostname: raspberrypi , alive, uptime: 62226) Core adapters versions js-controller: 7.0.7 admin: 7.7.2 javascript: 8.9.2 nodejs modules from github: 1 +-- iobroker.renault@0.0.21 (git+ssh://git@github.com/TA2k/ioBroker.renault.git#88555e6024eac2d1f016a9a1ef25f7c1bf965aea) Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.digitalstrom.0 : digitalstrom : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled + system.adapter.fronius.0 : fronius : raspberrypi - enabled system.adapter.go-e.0 : go-e : raspberrypi - disabled + system.adapter.harmony.0 : harmony : raspberrypi - enabled + system.adapter.hue.0 : hue : raspberrypi - enabled, port: 443 + system.adapter.javascript.0 : javascript : raspberrypi - enabled system.adapter.mihome.0 : mihome : raspberrypi - disabled, port: 9898, bind: 0.0.0.0 + system.adapter.mystrom.0 : mystrom : raspberrypi - enabled + system.adapter.netatmo.0 : netatmo : raspberrypi - enabled system.adapter.nuki-extended.0 : nuki-extended : raspberrypi - disabled + system.adapter.renault.0 : renault : raspberrypi - enabled system.adapter.roborock.0 : roborock : raspberrypi - disabled + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 system.adapter.sonos.0 : sonos : raspberrypi - disabled + system.adapter.swiss-weather-api.0 : swiss-weather-api : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.viessmannapi.0 : viessmannapi : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.yahka.0 : yahka : raspberrypi - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hue.0 : hue : raspberrypi - enabled, port: 443 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories ┌─────────┬────────────────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼────────────────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'Stable (default)' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): Stable (default) Upgrade policy: none Installed ioBroker-Adapters Used repository: Stable (default) Adapter "admin" : 7.7.2 , installed 7.7.2 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "digitalstrom" : 2.3.0 , installed 2.3.0 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "fronius" : 2.1.1 , installed 2.1.1 Adapter "go-e" : 1.0.41 , installed 1.0.41 Adapter "harmony" : 1.5.0 , installed 1.5.0 Adapter "hue" : 3.16.2 , installed 3.16.2 Adapter "javascript" : 8.9.2 , installed 8.9.2 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "netatmo" : 3.1.0 , installed 3.1.0 Adapter "nuki-extended": 2.7.0 , installed 2.7.0 Adapter "roborock" : 0.6.18 , installed 0.6.18 Adapter "rpi2" : 2.4.0 , installed 2.4.0 Adapter "shelly" : 10.2.0 , installed 10.2.0 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonos" : 3.0.0 , installed 3.0.0 Adapter "swiss-weather-api": 2.2.2, installed 2.2.2 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "viessmannapi" : 2.3.0 , installed 2.3.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yahka" : 1.1.5 , installed 1.1.5 Objects and States Please stand by - This may take a while Objects: 44134 States: 37103 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 http://deb.debian.org/debian bookworm-updates InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease 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:22 0.0.0.0:* LISTEN 0 5097 866/sshd: /usr/sbin tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 72003 17125/iobroker.js-c tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 74838 17125/iobroker.js-c tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 294632 28542/cupsd tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 75320 17372/io.shelly.0 tcp 0 0 127.0.0.1:43769 0.0.0.0:* LISTEN 1001 77117 17387/io.yahka.0 tcp6 0 0 :::61991 :::* LISTEN 1001 74736 17291/io.harmony.0 tcp6 0 0 :::33667 :::* LISTEN 1001 72254 17387/io.yahka.0 tcp6 0 0 :::22 :::* LISTEN 0 5099 866/sshd: /usr/sbin tcp6 0 0 ::1:631 :::* LISTEN 0 294631 28542/cupsd tcp6 0 0 :::8082 :::* LISTEN 1001 77077 17556/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 74908 17143/io.admin.0 udp 0 0 0.0.0.0:61991 0.0.0.0:* 1001 74737 17291/io.harmony.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 4978 679/avahi-daemon: r udp 0 0 0.0.0.0:46945 0.0.0.0:* 104 4980 679/avahi-daemon: r udp6 0 0 :::46250 :::* 104 4981 679/avahi-daemon: r udp6 0 0 :::5353 :::* 104 4979 679/avahi-daemon: r *** Log File - Last 25 Lines *** 2025-10-06 10:33:22.580 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:34:22.504 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:34:22.570 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:35:22.593 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:35:22.637 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:36:22.041 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:36:22.140 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:37:22.065 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:37:22.180 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:38:22.104 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:38:22.205 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:39:22.497 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:39:22.680 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:40:22.524 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:40:22.628 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:41:22.070 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:41:22.176 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:42:22.115 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:42:22.220 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:43:22.109 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:43:22.210 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:44:22.126 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:44:22.224 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 2025-10-06 10:45:22.134 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 2025-10-06 10:45:22.237 - info: digitalstrom.0 (17246) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string"============ Mark until here for C&P =============
iob diag has finished.
pi@raspberrypi:~ $ ========== Start marking the full check here ===========
Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 12 (bookworm) Static hostname: raspberrypi Icon name: computer Kernel: Linux 6.6.51+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.0 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 10:45:47 up 18:27, 3 users, load average: 0.29, 0.16, 0.11 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Mon 2025-10-06 10:45:47 CEST Universal time: Mon 2025-10-06 08:45:47 UTC RTC time: Mon 2025-10-06 08:45:47 Time zone: Europe/Zurich (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Display-Manager: x lightdm.service - Light Display Manager Desktop: Session: tty ============ Mark until here for C&P ============= -
@hugi sagte in Viessmann Adapter keine Verbindung mehr:
leider hat da deine Lösung nichts gebracht
Das war keine 'Lösung' für das Problem, das war nur die Hilfestellung um das System auf einem aktuellen Stand zu haben.
(Was aber wiederum die Ausgangsbasis für eine Problemsuche oder -lösung ist)@thomas-braun ich habe das gleiche Problem nach eine Neustart meine ioBroker server. Die oberen Schritte habe ich schon durchgefuhrt und kann die Ergebnisse bereitstellen wenn nötig, aber ich gehe davon aus, dass eine Analyse mit die Informationen von @hugi schon angefangen hat.
-
@thomas-braun ich habe das gleiche Problem nach eine Neustart meine ioBroker server. Die oberen Schritte habe ich schon durchgefuhrt und kann die Ergebnisse bereitstellen wenn nötig, aber ich gehe davon aus, dass eine Analyse mit die Informationen von @hugi schon angefangen hat.
@smalltower1 sagte in Viessmann Adapter keine Verbindung mehr:
die Ergebnisse bereitstellen
Mach doch. Dann kann man zumindest mal sehen, ob die sonstige Umgebung senkrecht steht.
-
@smalltower1 sagte in Viessmann Adapter keine Verbindung mehr:
die Ergebnisse bereitstellen
Mach doch. Dann kann man zumindest mal sehen, ob die sonstige Umgebung senkrecht steht.
Ich habe die Info. Gelöscht
-
Ich habe die Info. Gelöscht
-
Mit der Beta Version 2.4.3 funktioniert der Zugriff wieder. Danke für das Beheben, wer auch immer das war :)
@hugi Danke für die Info. Ich habe die Beta Version 2.4.0 probiert und es funktioniert auch :)
-
Mit der Beta Version 2.4.3 funktioniert der Zugriff wieder. Danke für das Beheben, wer auch immer das war :)
@hugi sorry, zu schnell gesprochen. Version 2.3.0 macht bei mir die Instanz Grün, aber die Werte werden nur ein mal aktualisiert, nicht jede Minute wie vorher. Wo hast du die 2.4.3 bekommen, Github?
-
@hugi sorry, zu schnell gesprochen. Version 2.3.0 macht bei mir die Instanz Grün, aber die Werte werden nur ein mal aktualisiert, nicht jede Minute wie vorher. Wo hast du die 2.4.3 bekommen, Github?
@smalltower1 ich habe in den Einstellungen vom iobroker das repository von stable auf beta gewechselt. Dann sie dir angeboten.
-
@hugi sorry, zu schnell gesprochen. Version 2.3.0 macht bei mir die Instanz Grün, aber die Werte werden nur ein mal aktualisiert, nicht jede Minute wie vorher. Wo hast du die 2.4.3 bekommen, Github?
NEIN - von direkten Installationen von Github wird EXPLIZIT ABGERATEN
Die Version 2.4.3 ist im LATEST Repository verfügbar - aber leider nicht fürs Stable vom Dev freigegeben.
Also entweder auf LATEST Repository umstellen oder im Expertenmodus "von npm" auswählen.
Alternativ auf der commandline 'iob upgrade iobroker.viessmanapi@2.4.3' verwenden.Aber Achtung: Nicht einfach alle neueren Adapter aus dem Stable in einer produktiven Umgebung installieren. Das kann auch unerwünschte Änderungen auslösen.
Support us
601
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge