Adapter sma-speedwire
-
@bob_morane77 sagte in Adapter sma-speedwire:
die Infos zu Filesystem/größte Dateien sind irrelevant denke ich oder was wäre noch interessant?
Nix kürzen, vollständige Ausgaben posten.
-
- ja mit nvm experimentiert, nun wieder entfernt
- ich kann in meinen docker iobrokern egal welche imageversion 7.x oder 8.x
nachstellen, das wenn js_controller von 4.x auf 5.x der sma-speedwire aussteigt, mit einzig der obigen Meldung - erzwinge ich des Downgrade auf 4.x funktioniert es wieder
hier des aktuelle summary
======================= SUMMARY =======================
v.2023-04-16Operatingsystem: Raspbian GNU/Linux 12 (bookworm)
Kernel: 5.10.103-v7l+
Installation: Native
Timezone: Europe/Berlin (CEST, +0200)
User-ID: 1000
X-Server: false
Boot Target: graphical.targetPending OS-Updates: 0
Pending iob updates: 1Nodejs-Installation: /usr/bin/nodejs v18.17.1
/usr/bin/node v18.17.1
/usr/bin/npm 9.6.7
/usr/bin/npx 9.6.7Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correctMEMORY:
total used free shared buff/cache available
Mem: 4.0G 1.7G 890M 6.5M 1.2G 2.3G
Swap: 1.3G 94M 1.2G
Total: 5.3G 1.8G 2.1GActive iob-Instances: 14
Active repo(s): betaioBroker Core: js-controller 5.0.12
admin 6.9.1ioBroker Status: iobroker is running on this host.
Objects type: jsonl
States type: jsonlStatus admin and web instance:
- system.adapter.admin.0 : admin : Raspi4B - enabled, port: 8081, bind: 0.0.0.0, run as: admin
Objects: 5697
States: 4415Size of iob-Database:
20M /opt/iobroker/iobroker-data/objects.jsonl
6.1M /opt/iobroker/iobroker-data/objects.json.migrated
6.1M /opt/iobroker/iobroker-data/objects.json.bak.migrated
0 /opt/iobroker/iobroker-data/objects.json.broken
6.8M /opt/iobroker/iobroker-data/states.jsonl
652K /opt/iobroker/iobroker-data/states.json.migrated
652K /opt/iobroker/iobroker-data/states.json.bak.migrated
0 /opt/iobroker/iobroker-data/states.json.broken=================== END OF SUMMARY ====================
-
@bob_morane77 sagte in Adapter sma-speedwire:
Operatingsystem: Raspbian GNU/Linux 12 (bookworm)
Kernel: 5.10.103-v7l+Das dürfte auch nicht passen. Da sollte eigentlich ein Kernel 6.1 drin sein. Und auf 64bit würde ich das ganze auch hieven.
-
habe zwar keine Erklärung, warum der Kernel nicht geupdatet wurde
angeschubst======================= SUMMARY =======================
v.2023-04-16Operatingsystem: Raspbian GNU/Linux 12 (bookworm)
Kernel: 6.1.47-v8+
Installation: Native
Timezone: Europe/Berlin (CEST, +0200)
User-ID: 1000
X-Server: false
Boot Target: graphical.targetPending OS-Updates: 0
Pending iob updates: 1Nodejs-Installation: /usr/bin/nodejs v18.17.1
/usr/bin/node v18.17.1
/usr/bin/npm 9.6.7
/usr/bin/npx 9.6.7Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correctMEMORY:
total used free shared buff/cache available
Mem: 4.0G 1.4G 465M 6.7M 2.1G 2.5G
Swap: 1.3G 0B 1.3G
Total: 5.2G 1.4G 1.7GActive iob-Instances: 14
Active repo(s): betaioBroker Core: js-controller 5.0.12
admin 6.9.1ioBroker Status: iobroker is running on this host.
Objects type: jsonl
States type: jsonlStatus admin and web instance:
- system.adapter.admin.0 : admin : Raspi4B - enabled, port: 8081, bind: 0.0.0.0, run as: admin
Objects: 5699
States: 4420Size of iob-Database:
21M /opt/iobroker/iobroker-data/objects.jsonl
6.1M /opt/iobroker/iobroker-data/objects.json.migrated
6.1M /opt/iobroker/iobroker-data/objects.json.bak.migrated
0 /opt/iobroker/iobroker-data/objects.json.broken
8.8M /opt/iobroker/iobroker-data/states.jsonl
652K /opt/iobroker/iobroker-data/states.json.migrated
652K /opt/iobroker/iobroker-data/states.json.bak.migrated
0 /opt/iobroker/iobroker-data/states.json.broken=================== END OF SUMMARY ====================
-
Die Langfassung in CodeTags bitte.
-
======== Start marking the full check here =========
Skript v.2023-04-16 *** BASE SYSTEM *** Model : Raspberry Pi 400 Rev 1.1 Architecture : aarch64 Docker : false Virtualization : none Distributor ID: Raspbian Description: Raspbian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm PRETTY_NAME="Raspbian GNU/Linux 12 (bookworm)" NAME="Raspbian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" Systemuptime and Load: 15:03:54 up 32 min, 2 users, load average: 1.54, 1.09, 1.02 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=43.3'C volt=0.9460V *** Time and Time Zones *** Local time: Wed 2023-08-30 15:03:55 CEST Universal time: Wed 2023-08-30 13:03:55 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input netdev docker gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 4.0G 1.5G 297M 6.7M 2.1G 2.5G Swap: 1.3G 0B 1.3G Total: 5.2G 1.5G 1.6G 3792 M total memory 1420 M used memory 1669 M active memory 1073 M inactive memory 283 M free memory 440 M buffer memory 1565 M swap cache 1199 M total swap 0 M used swap 1199 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 165G 39G 121G 25% / devtmpfs devtmpfs 1.6G 0 1.6G 0% /dev tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 759M 952K 758M 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/sda1 vfat 253M 53M 200M 21% /boot tmpfs tmpfs 380M 0 380M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Aug 30 14:31:05 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=E4:5F:01:49:69:B6 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=ttyS0,115200 console=tty1 root=PARTUUID=b7dcae69-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait [Wed Aug 30 14:31:08 2023] EXT4-fs (sda2): INFO: recovery required on readonly filesystem [Wed Aug 30 14:31:08 2023] EXT4-fs (sda2): write access will be enabled during recovery [Wed Aug 30 14:31:08 2023] EXT4-fs (sda2): recovery complete [Wed Aug 30 14:31:08 2023] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none. [Wed Aug 30 14:31:08 2023] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. [Wed Aug 30 14:31:10 2023] EXT4-fs (sda2): re-mounted. Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime `-/boot /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 19G /var/ 16G /var/lib/docker 16G /var/lib 11G /var/lib/docker/overlay2 5.7G /var/lib/docker/volumes Archived and active journals take up 487.3M in the file system. /opt/iobroker/backups: 22M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 208M /opt/iobroker/iobroker-data/ 96M /opt/iobroker/iobroker-data/backup-objects 71M /opt/iobroker/iobroker-data/files 52M /opt/iobroker/iobroker-data/files/javascript.admin 34M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 21M /opt/iobroker/iobroker-data/objects.jsonl 7.1M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/610.f22de4ab.chunk.js.map 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map 6.1M /opt/iobroker/iobroker-data/states.jsonl 6.1M /opt/iobroker/iobroker-data/objects.json.migrated *** NodeJS-Installation *** /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 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 bookworm/main armhf Packages 100 /var/lib/dpkg/status 18.13.0+dfsg1-1+rpi1 500 500 http://raspbian.raspberrypi.org/raspbian bookworm/main armhf Packages Temp directories causing npm8 problem: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl MULTIHOSTSERVICE/enabled: false Core adapters versions js-controller: 5.0.12 admin: 6.9.1 javascript: 7.1.4 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : Raspi4B - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.awattar.0 : awattar : Raspi4B - enabled + system.adapter.backitup.0 : backitup : Raspi4B - enabled + system.adapter.discovery.0 : discovery : Raspi4B - enabled + system.adapter.fritzdect.0 : fritzdect : Raspi4B - enabled + system.adapter.influxdb.0 : influxdb : Raspi4B - enabled, port: 8086 + system.adapter.info.0 : info : Raspi4B - enabled + system.adapter.javascript.0 : javascript : Raspi4B - enabled system.adapter.knx.0 : knx : Raspi4B - disabled, bind: 192.168.178.15 + system.adapter.loxone.0 : loxone : Raspi4B - enabled, port: 80 system.adapter.meross.0 : meross : Raspi4B - disabled system.adapter.nibeuplink.0 : nibeuplink : Raspi4B - disabled system.adapter.openweathermap.0 : openweathermap : Raspi4B - enabled + system.adapter.pi-hole.0 : pi-hole : Raspi4B - enabled + system.adapter.rpi2.0 : rpi2 : Raspi4B - enabled + system.adapter.shelly.0 : shelly : Raspi4B - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sma-em.0 : sma-em : Raspi4B - enabled system.adapter.sma-speedwire.0 : sma-speedwire : Raspi4B - enabled, port: 9522 + system.adapter.upnp.0 : upnp : Raspi4B - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : Raspi4B - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : Raspi4B - enabled, port: 8086 + system.adapter.loxone.0 : loxone : Raspi4B - enabled, port: 80 + system.adapter.shelly.0 : shelly : Raspi4B - enabled, port: 1882, bind: 0.0.0.0 system.adapter.sma-speedwire.0 : sma-speedwire : Raspi4B - enabled, port: 9522 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): beta Installed ioBroker-Instances Used repository: beta Adapter "admin" : 6.9.1 , installed 6.9.1 Adapter "awattar" : 1.0.6 , installed 1.0.6 Adapter "backitup" : 2.7.0 , installed 2.7.0 Adapter "discovery" : 3.2.0 , installed 3.2.0 Adapter "fritzdect" : 2.3.1 , installed 2.3.1 Adapter "influxdb" : 3.2.0 , installed 3.2.0 Adapter "info" : 1.9.26 , installed 1.9.26 Adapter "javascript" : 7.1.4 , installed 7.1.4 Controller "js-controller": 5.0.12 , installed 5.0.12 Adapter "knx" : 2.0.22 , installed 1.0.45 [Updatable] Adapter "loxone" : 3.0.1 , installed 3.0.1 Adapter "meross" : 1.15.1 , installed 1.15.1 Adapter "nibeuplink" : 1.3.0 , installed 1.3.0 Adapter "openweathermap": 0.4.2 , installed 0.4.2 Adapter "pi-hole" : 1.3.6 , installed 1.3.6 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "shelly" : 6.4.1 , installed 6.4.1 Adapter "sma-em" : 1.0.0 , installed 1.0.0 Adapter "upnp" : 1.0.21 , installed 1.0.21 Objects and States Please stand by - This may take a while Objects: 5699 States: 4418 *** OS-Repositories and Updates *** Hit:1 http://archive.raspberrypi.org/debian bookworm InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian bookworm InRelease Hit:3 https://download.docker.com/linux/raspbian bookworm InRelease Hit:4 https://dl.yarnpkg.com/debian stable InRelease Get:5 https://deb.nodesource.com/node_18.x bookworm InRelease [4586 B] Fetched 4586 B in 1s (3706 B/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:443 0.0.0.0:* LISTEN 0 18440 1022/docker-proxy tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 17779 705/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 17786 705/iobroker.js-con tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 13059 716/sshd: /usr/sbin tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 0 18499 1114/docker-proxy tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 18467 1065/docker-proxy tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN 0 15795 1087/docker-proxy tcp 0 0 0.0.0.0:9005 0.0.0.0:* LISTEN 0 16667 1152/docker-proxy tcp 0 0 0.0.0.0:8089 0.0.0.0:* LISTEN 0 26865 4428/docker-proxy tcp 0 0 0.0.0.0:8086 0.0.0.0:* LISTEN 0 26945 4583/docker-proxy tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 0 13997 802/perl tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN 0 18541 1175/docker-proxy tcp6 0 0 :::443 :::* LISTEN 0 16563 1042/docker-proxy tcp6 0 0 :::22 :::* LISTEN 0 13061 716/sshd: /usr/sbin tcp6 0 0 :::53 :::* LISTEN 0 16629 1122/docker-proxy tcp6 0 0 :::80 :::* LISTEN 0 15786 1074/docker-proxy tcp6 0 0 :::3000 :::* LISTEN 0 17480 1093/docker-proxy tcp6 0 0 :::9005 :::* LISTEN 0 17501 1160/docker-proxy tcp6 0 0 :::8089 :::* LISTEN 0 25441 4437/docker-proxy tcp6 0 0 :::8086 :::* LISTEN 0 28099 4590/docker-proxy tcp6 0 0 :::8081 :::* LISTEN 1001 16263 1808/io.admin.0 tcp6 0 0 :::8001 :::* LISTEN 1001 40123 3579/io.upnp.0 tcp6 0 0 :::8000 :::* LISTEN 0 18547 1182/docker-proxy udp 0 0 0.0.0.0:48124 0.0.0.0:* 1001 24172 3579/io.upnp.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 12010 404/avahi-daemon: r udp 0 0 0.0.0.0:9522 0.0.0.0:* 1001 22997 3438/io.sma-em.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 20716 2851/io.shelly.0 udp 0 0 0.0.0.0:54884 0.0.0.0:* 108 12012 404/avahi-daemon: r udp 0 0 0.0.0.0:52893 0.0.0.0:* 1001 24173 3579/io.upnp.0 udp 0 0 0.0.0.0:10000 0.0.0.0:* 0 13998 802/perl udp 0 0 0.0.0.0:44901 0.0.0.0:* 1001 24175 3579/io.upnp.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 27903 3579/io.upnp.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 27902 3579/io.upnp.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 27901 3579/io.upnp.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 27900 3579/io.upnp.0 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 27899 3579/io.upnp.0 udp 0 0 0.0.0.0:42865 0.0.0.0:* 1001 24171 3579/io.upnp.0 udp 0 0 192.168.178.15:53 0.0.0.0:* 0 16643 1138/docker-proxy udp 0 0 0.0.0.0:68 0.0.0.0:* 0 15379 702/dhcpcd udp 0 0 0.0.0.0:49255 0.0.0.0:* 1001 24174 3579/io.upnp.0 udp6 0 0 :::5353 :::* 108 12011 404/avahi-daemon: r udp6 0 0 :::36915 :::* 108 12013 404/avahi-daemon: r udp6 0 0 :::546 :::* 0 12132 702/dhcpcd *** Log File - Last 25 Lines *** 2023-08-30 15:05:02.762 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.pregard" has to be type "state" but received type "number" 2023-08-30 15:05:02.811 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.psurplus" has to be type "state" but received type "number" 2023-08-30 15:05:03.038 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.SMASerial" has to be type "state" but received type "number" 2023-08-30 15:05:03.751 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.pregard" has to be type "state" but received type "number" 2023-08-30 15:05:03.798 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.psurplus" has to be type "state" but received type "number" 2023-08-30 15:05:04.039 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.SMASerial" has to be type "state" but received type "number" 2023-08-30 15:05:04.757 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.pregard" has to be type "state" but received type "number" 2023-08-30 15:05:04.802 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.psurplus" has to be type "state" but received type "number" 2023-08-30 15:05:05.039 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.SMASerial" has to be type "state" but received type "number" 2023-08-30 15:05:05.750 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.pregard" has to be type "state" but received type "number" 2023-08-30 15:05:05.802 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.psurplus" has to be type "state" but received type "number" 2023-08-30 15:05:06.022 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.SMASerial" has to be type "state" but received type "number" 2023-08-30 15:05:06.758 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.pregard" has to be type "state" but received type "number" 2023-08-30 15:05:06.810 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.psurplus" has to be type "state" but received type "number" 2023-08-30 15:05:07.039 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.SMASerial" has to be type "state" but received type "number" 2023-08-30 15:05:07.750 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.pregard" has to be type "state" but received type "number" 2023-08-30 15:05:07.798 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.psurplus" has to be type "state" but received type "number" 2023-08-30 15:05:08.024 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.SMASerial" has to be type "state" but received type "number" 2023-08-30 15:05:08.748 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.pregard" has to be type "state" but received type "number" 2023-08-30 15:05:08.752 - info: influxdb.0 (1892) Store 51 buffered influxDB history points 2023-08-30 15:05:08.795 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.psurplus" has to be type "state" but received type "number" 2023-08-30 15:05:09.039 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.SMASerial" has to be type "state" but received type "number" 2023-08-30 15:05:09.753 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.pregard" has to be type "state" but received type "number" 2023-08-30 15:05:09.803 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.psurplus" has to be type "state" but received type "number" 2023-08-30 15:05:10.117 - info: sma-em.0 (3438) State value to set for "sma-em.0.3006139391.SMASerial" has to be type "state" but received type "number"============ Mark until here for C&P =============
-
@bob_morane77 sagte in Adapter sma-speedwire:
EXT4-fs (sda2): INFO: recovery required on readonly filesystem
Was stellst du mit der Kiste an?
Immer ordentlich herunterfahren/neustarten.
Vom Strom reißen ist nicht ordentlich.Ich hätte an deiner Stelle auch ein reines 64bit-System installiert.
Knallst du da auch noch docker rein?
Hit:3 https://download.docker.com/linux/raspbian bookworm InRelease
Hit:4 https://dl.yarnpkg.com/debian stable InReleaseDie Quelle für yarn ist auch zu 99% entbehrlich.
Und konkret geht es um diesen Adapter?
https://github.com/Apollon77/iobroker.sma-speedwireHaste mal gesehen wann da das letzte mal am Code was getan wurde?
Kann ich noch irgendwelche Logs / Tests beisteuern?
Du kannst ein Issue beim Adapter anlegen und auf inkompatibiltät mit js-controller 5 hinweisen.
-
@thomas-braun
ja, der Adapter ist es, siehe oben
https://github.com/Apollon77/iobroker.sma-speedwireich hatte apollon77 angeschrieben wegen dem Adapter
ich kann im git bei diesem Repository kein Issue eröffnen den Button gibts nicht, er hatte das auch vorgeschlagen - Alternative war hier Forum@Strom raus
natürlich gute Idee aber nein per Fernzugriff sudo reboot@docker
ja, steht auch oben, so kann ich weitere Sachen testen und schnell hoch runter fahren@yarn - ok
@sma-speedwire Alter
ja, der Code ist 5-6 Jahre alt ich weiß, daher auch vorher die Frage an apollon77 ob die Chance besteht, das hier nochmal was passiertda git nicht geht hab ich des Topic aufgemacht
-
@bob_morane77 sagte in Adapter sma-speedwire:
natürlich gute Idee aber nein per Fernzugriff sudo reboot
Dann hast du ein Problem.
Ein reboot darf kein recovery des Dateisystems auslösen. -
@bob_morane77 sagte in Adapter sma-speedwire:
@thomas-braun
ja, der Adapter ist es, siehe oben
https://github.com/Apollon77/iobroker.sma-speedwireHmmm... ich glaube du hast da ein Missverständnis. Ich habe nur einen Fork von dem Adapter ... Der orignale ist von AttackStrawbery/ioBroker.sma-speedwire ... und da es nur ein Fork ist ist das auch der Grund das Du keine Issues anlegen kannst.
Issues sind korrekt unter https://github.com/AttackStrawbery/ioBroker.sma-speedwire/issues aufgehoben, aber da ist die letzte Aktion von 2018 ...
Ergo:Adapter nicht von mir ... aber ja lege issue beim Adapter an.
ggf kann man den Dev anschreiben ob er den Adapter in die Community schiebt ... aber ich erinnere mich dunkel das es andere sma adapter gibt inzwischen?? -
@apollon77
Danke für die Infos@andere Adapter
ist mir nur sma-em bekannt, der für das Auslesen vom sma shm2.0 da istsbfspot gäbe es noch für Wechselrichter auslesen, die wollen zwingend andere Datenbank - keine influx
Alternative wäre noch auf Modbus umzusatteln
