Test Adapter eufy Home Robovac
-
@tombox sagte in Test Adapter eufy Home Robovac:
@stefan1984 der gtoken fehler verhindert ein korrekte Arbeitsweise ich bräuchte mal dein account um das zu beheben
tombox2020@gmail.comHabe Dir eine Email geschickt. Was brauchst Du genau für die Behebung? Eufy Account? IoBroker? Zugang oder nur den Benutzernamen?
-
@tombox Danke für die schnelle Unterstützung. Sieht gut aus. Bisher keine roten Protokolle mehr. Falls sich was ändert, dann melde ich mich dazu nochmal. Objekte in ioBroker sind jetzt auch alle benannt. Funktioniert also.
Vielen, vielen Dank.
Ist Deine Änderung etwas was Du bei jedem Account machen musst, oder war das jetzt Zufall und hilft auch anderen Nutzern?
Stefan
-
@stefan1984 War ein genereller Bug der jedem Nutzer hilft
-
@tombox Bis jetzt läuft der Adapter super. Alle Fehlermeldungen sind weg, Objektnamen werden komplett dargestellt. Ich kann den X10 über ioBroker starten und nach Hause schicken. Ausserdem läuft der Adapter bisher stabil.
Vielen Dank für Deine Arbeit und Deine Zeit.
Wie kann es weitergehen? Was ist noch geplant? Anbei ein paar Wünsche, die bestimmt auch anderen Nutzern gefallen werden:
- Zugriff auf die in der App erstellten Szenarien über ioBroker (z.B. zur Verwendung per Blockly)
- Einstellen des manuellen Modus über ioBroker (z.B. Start saugen ohne wischen, Start intensives wischen ohne saugen, etc)
- Gezieltes Arbeiten ein einzelnen Räumen (mache die Küche sauber) - wäre aber alternativ auch über Szenarien möglich
Wie kann ich als Tester dabei unterstützen? @VierlingMt ist bestimmt auch dabei.
Grüße,
Stefan -
Hallo,
ich habe kürzlich einen X10 Pro Omni gekauft und kann ihn auch über die App sehen und steuern. Der Login mit dem Adapter funktioniert auch einwandfrei. Allerdings wurden keine Objekte angelegt und im Log findet sich die Meldung "Found 0 devices".
-
@bmueller77 Bitte Beitrag #1 beachten und
benutzen -
@tombox Hab ich glatt übersehen... Danke. Funktioniert.
-
@tombox ich habe hier ein scheinbar neues Modell G50: https://www.amazon.de/dp/B0CR5N9SM3
Das Anbinden über den Adapter funktionierte (per MQTT), Steuerung scheint nicht möglich zu sein, die Fehlermeldung auf alles im Log ist immererror: euhome.0 (996356) Device not found for undefinedDas hat er beim Versuch etwas zu starten gebracht, jetzt saugt Ding gerade und bringt diese Meldung ebenfalls mehrmals pro Minute.
es gibt den Datenpunkt
15wo ich zumindest einige Befehle sehe (in der Auswahl und in den Eigenschaften), aber wie geschrieben obige Fehlermeldung.Falls du mal schauen willst kann ich dir gerne die App-Zugangsdaten zur Verfügung stellen, schreib mich einfach über den Chat an.
Edit: Bei der Installation gab es allerdings auch folgende Warnmeldungen (als Info)
2024-05-19 13:50:27.345 - info: host.iobroker iobroker npm WARN While resolving: @iobroker/adapter-core@3.1.4npm WARN Found: @iobroker/types@5.0.20-alpha.0-20240508-d36cddc8dnpm WARN node_modules/iobroker.admin/node_modules/@iobroker/typesnpm WARN @iobroker/types@"5.0.20-alpha.0-20240508-d36cddc8d" from iobroker.admin@6.17.7npm WARN node_modules/iobroker.adminnpm WARN iobroker.admin@"6.17.7" from the root projectnpm WARN npm WARN Could not resolve dependency:npm WARN peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4npm WARN node_modules/iobroker.admin/node_modules/@iobroker/adapter-corenpm WARN @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.7npm WARN node_modules/iobroker.adminnpm WARN npm WARN Conflicting peer dependency: @iobroker/types@5.0.19npm WARN node_modules/@iobroker/typesnpm WARN peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 2024-05-19 13:50:27.346 - info: host.iobroker iobroker npm WARN node_modules/iobroker.admin/node_modules/@iobroker/adapter-corenpm WARN @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.7npm WARN node_modules/iobroker.adminDie Kurzfassung von
iob diagfür die Versionen:======================= SUMMARY ======================= v.2024-04-21 Static hostname: iobroker Icon name: computer-vm Chassis: vm Virtualization: vmware Operating System: Ubuntu 22.04.4 LTS Kernel: Linux 5.15.0-102-generic Architecture: x86-64 Hardware Vendor: VMware, Inc. Hardware Model: VMware Virtual Platform Installation: vmware Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1002 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 41 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v18.20.2 /usr/bin/node v18.20.2 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.25.2 Recommended versions are nodejs 18.20.2 and npm 10.5.0 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 11G 8.0G 1.3G 8.0M 2.7G 3.6G Swap: 2.0G 1.7G 359M Total: 14G 9.7G 1.6G Active iob-Instances: 61 Active repo(s): beta ioBroker Core: js-controller 5.0.19 admin 6.17.7 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: redis Status admin and web instance: system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.admin.1 : admin : iobroker - disabled, port: 60081, bind: 0.0.0.0, run as: admin + system.adapter.admin.2 : admin : iobroker - enabled, port: 60082, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.web.1 : web : iobroker - enabled, port: 60008, bind: 0.0.0.0, run as: admin Objects: 43473 States: 40150 Size of iob-Database: 75M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/objects.json.migrated 24M /opt/iobroker/iobroker-data/objects.json.bak.migrated 1.8M /opt/iobroker/iobroker-data/states.json.bak 1.8M /opt/iobroker/iobroker-data/states.json =================== END OF SUMMARY ====================und die Langfassung:
Skript v.2024-04-21 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer-vm Chassis: vm Virtualization: vmware Operating System: Ubuntu 22.04.4 LTS Kernel: Linux 5.15.0-102-generic Architecture: x86-64 Hardware Vendor: VMware, Inc. Hardware Model: VMware Virtual Platform model name : AMD FX-9830P RADEON R7, 12 COMPUTE CORES 4C+8G Docker : false Virtualization : vmware Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 13:57:45 up 36 days, 15:13, 4 users, load average: 1.78, 1.39, 1.15 CPU threads: 4 *** Time and Time Zones *** Local time: Sun 2024-05-19 13:57:45 CEST Universal time: Sun 2024-05-19 11:57:45 UTC RTC time: Sun 2024-05-19 11:57:45 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: n/a RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': bananajoe HOME=/home/bananajoe GROUPS=bananajoe sudo User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video redis *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 11G 7.9G 1.4G 8.0M 2.7G 3.7G Swap: 2.0G 1.7G 359M Total: 14G 9.6G 1.8G Active iob-Instances: 61 11957 M total memory 7882 M used memory 4566 M active memory 4830 M inactive memory 1419 M free memory 550 M buffer memory 2104 M swap cache 2047 M total swap 1688 M used swap 359 M free swap *** top - Table Of Processes *** top - 13:57:45 up 36 days, 15:13, 4 users, load average: 1.72, 1.39, 1.15 Tasks: 404 total, 1 running, 403 sleeping, 0 stopped, 0 zombie %Cpu(s): 16.9 us, 6.2 sy, 0.0 ni, 75.4 id, 0.0 wa, 0.0 hi, 1.5 si, 0.0 st MiB Mem : 11957.5 total, 1419.0 free, 7883.7 used, 2654.8 buff/cache MiB Swap: 2048.0 total, 359.2 free, 1688.8 used. 3747.7 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * openipmi.service loaded failed failed LSB: OpenIPMI Driver init script 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 1.2G 3.0M 1.2G 1% /run /dev/sda2 ext4 63G 28G 33G 47% / tmpfs tmpfs 5.9G 0 5.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 64M 0 64M 0% /RAMdisk tmpfs tmpfs 1.2G 4.0K 1.2G 1% /run/user/0 Messages concerning ext4 filesystem in dmesg: [Fri Apr 12 22:44:39 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [Fri Apr 12 22:44:40 2024] EXT4-fs (sda2): re-mounted. Opts: (null). Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,relatime |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/fs/bpf bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime | `-/sys/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime |-/proc proc proc rw,nosuid,nodev,noexec,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=1211 | `-/proc/sys/fs/binfmt_misc binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime |-/dev udev devtmpfs rw,nosuid,relatime,size=6064224k,nr_inodes=1516056,mode=755,inode64 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev,inode64 | |-/dev/hugepages hugetlbfs hugetlbfs rw,relatime,pagesize=2M | `-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime |-/run tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=1224444k,mode=755,inode64 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k,inode64 | |-/run/user/0 tmpfs tmpfs rw,nosuid,nodev,relatime,size=1224440k,nr_inodes=306110,mode=700,inode64 | |-/run/credentials/systemd-sysusers.service none ramfs ro,nosuid,nodev,noexec,relatime,mode=700 | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | `-/run/snapd/ns tmpfs[/snapd/ns] tmpfs rw,nosuid,nodev,noexec,relatime,size=1224444k,mode=755,inode64 | `-/run/snapd/ns/lxd.mnt nsfs[mnt:[4026532603]] nsfs rw |-/RAMdisk tmpfs tmpfs rw,nosuid,nodev,relatime,size=65536k,inode64 |-/snap/lxd/28463 /dev/loop0 squashfs ro,nodev,relatime,errors=continue |-/snap/core18/2812 /dev/loop1 squashfs ro,nodev,relatime,errors=continue |-/snap/core20/2264 /dev/loop3 squashfs ro,nodev,relatime,errors=continue |-/snap/core22/1122 /dev/loop5 squashfs ro,nodev,relatime,errors=continue |-/snap/core20/2318 /dev/loop7 squashfs ro,nodev,relatime,errors=continue |-/snap/snapd/21184 /dev/loop9 squashfs ro,nodev,relatime,errors=continue |-/snap/core22/1380 /dev/loop6 squashfs ro,nodev,relatime,errors=continue |-/snap/snapd/21465 /dev/loop10 squashfs ro,nodev,relatime,errors=continue |-/snap/lxd/28322 /dev/loop8 squashfs ro,nodev,relatime,errors=continue `-/snap/core18/2823 /dev/loop4 squashfs ro,nodev,relatime,errors=continue Files in neuralgic directories: /var: 9.5G /var/ 4.7G /var/log 4.6G /var/lib 4.2G /var/log/journal/26010950dd3a4d9ab8f579561945c3da 4.2G /var/log/journal Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 8.0M in the file system. /opt/iobroker/backups: 1.1G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.4G /opt/iobroker/iobroker-data/ 1.1G /opt/iobroker/iobroker-data/files 237M /opt/iobroker/iobroker-data/files/vis.0 176M /opt/iobroker/iobroker-data/files/vis-2 172M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 75M /opt/iobroker/iobroker-data/objects.jsonl 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 24M /opt/iobroker/iobroker-data/objects.json.migrated USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2190370-if00 Your zigbee.0 COM-Port is matching 'by-id'. Very good! HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp *** NodeJS-Installation *** /usr/bin/nodejs v18.20.2 /usr/bin/node v18.20.2 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.25.2 nodejs: Installed: 18.20.2-1nodesource1 Candidate: 18.20.2-1nodesource1 Version table: *** 18.20.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.20.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 12.22.9~dfsg-1ubuntu3.5 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages 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: redis Core adapters versions js-controller: 5.0.19 admin: 6.17.7 javascript: 8.3.1 nodejs modules from github: 7 +-- iobroker.alexa2@3.26.5 (git+ssh://git@github.com/Apollon77/ioBroker.alexa2.git#37160cf729a9c70ca70679d4b1d3c16ba51c6456) +-- iobroker.energiefluss@3.6.0 (git+ssh://git@github.com/SKB-CGN/ioBroker.energiefluss.git#1b2f62380b39ac21b8a94853d76b4acf6c395111) +-- iobroker.google-sharedlocations@2.2.1 (git+ssh://git@github.com/Garfonso/ioBroker.google-sharedlocations.git#0db73d57d00aa5dff22ff22e853f1231ce141dc1) +-- iobroker.klipper-moonraker@0.0.4 (git+ssh://git@github.com/DrozmotiX/ioBroker.klipper-moonraker.git#4adef3ab69e5ff232d0d740fe3e0f560bca3c27e) +-- iobroker.life360@0.2.22 (git+ssh://git@github.com/MiGoller/ioBroker.life360.git#23166aab1b2e36d917a9b7b480d9faa7f73ca2d1) +-- iobroker.notificationforandroidtv@2.3.0 (git+ssh://git@github.com/DNAngelX/ioBroker.notificationforandroidtv.git#d9fc47833dbc17e1a499494050b2df31bf7ec23d) +-- iobroker.smartstate@0.0.4 (git+ssh://git@github.com/ChriD/ioBroker.smartstate.git#aa448478fd656fff055532b33decd1138d9222e3) Adapter State system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.admin.1 : admin : iobroker - disabled, port: 60081, bind: 0.0.0.0, run as: admin + system.adapter.admin.2 : admin : iobroker - enabled, port: 60082, bind: 0.0.0.0, run as: admin + system.adapter.alexa-shoppinglist.0 : alexa-shoppinglist : iobroker - enabled + system.adapter.alexa-timer-vis.0 : alexa-timer-vis : iobroker - enabled + system.adapter.alexa2.0 : alexa2 : iobroker - enabled system.adapter.alias-manager.0 : alias-manager : iobroker - enabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.broadlink2.0 : broadlink2 : iobroker - enabled system.adapter.daswetter.0 : daswetter : iobroker - enabled + system.adapter.device-reminder.0 : device-reminder : iobroker - enabled system.adapter.devices.0 : devices : iobroker - enabled + system.adapter.discovery.0 : discovery : iobroker - enabled system.adapter.dwd.0 : dwd : iobroker - enabled + system.adapter.echarts.0 : echarts : iobroker - enabled + system.adapter.email.0 : email : iobroker - enabled + system.adapter.energiefluss-erweitert.0 : energiefluss-erweitert: iobroker - enabled + system.adapter.energiefluss.0 : energiefluss : iobroker - enabled system.adapter.euhome.0 : euhome : iobroker - disabled system.adapter.feiertage.0 : feiertage : iobroker - enabled + system.adapter.followthesun.0 : followthesun : iobroker - enabled + system.adapter.fritzdect.0 : fritzdect : iobroker - enabled + system.adapter.fullybrowser.0 : fullybrowser : iobroker - enabled + system.adapter.google-sharedlocations.0 : google-sharedlocations: iobroker - enabled system.adapter.ical.0 : ical : iobroker - enabled + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.javascript.1 : javascript : iobroker - enabled system.adapter.klipper-moonraker.0 : klipper-moonraker : iobroker - disabled + system.adapter.life360.0 : life360 : iobroker - enabled + system.adapter.logparser.0 : logparser : iobroker - enabled + system.adapter.midea.0 : midea : iobroker - enabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.notificationforandroidtv.0: notificationforandroidtv: iobroker - enabled + system.adapter.nut.0 : nut : iobroker - enabled + system.adapter.nut.1 : nut : iobroker - enabled + system.adapter.operating-hours.0 : operating-hours : iobroker - enabled system.adapter.pi-hole.0 : pi-hole : iobroker - disabled + system.adapter.pi-hole.1 : pi-hole : iobroker - enabled + system.adapter.ping.0 : ping : iobroker - enabled + system.adapter.puppeteer.0 : puppeteer : iobroker - enabled + system.adapter.pvforecast.0 : pvforecast : iobroker - enabled + system.adapter.pvforecast.1 : pvforecast : iobroker - enabled system.adapter.pylontech.0 : pylontech : iobroker - disabled, port: 4196 + system.adapter.rest-api.0 : rest-api : iobroker - enabled, port: 8093, bind: 0.0.0.0, run as: admin + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 system.adapter.shelly.1 : shelly : iobroker - disabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin system.adapter.smartstate.0 : smartstate : iobroker - disabled + system.adapter.snmp.0 : snmp : iobroker - enabled + system.adapter.socketio.0 : socketio : iobroker - enabled, port: 60084, bind: 0.0.0.0, run as: admin + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled + system.adapter.sql.0 : sql : iobroker - enabled, port: 3306 + system.adapter.tankerkoenig.0 : tankerkoenig : iobroker - enabled + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.1 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.2 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.3 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : iobroker - enabled + system.adapter.time-switch.0 : time-switch : iobroker - enabled + system.adapter.tr-064.0 : tr-064 : iobroker - enabled + system.adapter.tr-064.1 : tr-064 : iobroker - enabled + system.adapter.traccar.0 : traccar : iobroker - enabled + system.adapter.trashschedule.0 : trashschedule : iobroker - enabled + system.adapter.tuya.0 : tuya : iobroker - enabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : iobroker - enabled system.adapter.vis-2-widgets-gauges.0 : vis-2-widgets-gauges : iobroker - enabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: iobroker - enabled + system.adapter.vis-2.0 : vis-2 : iobroker - enabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : iobroker - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : iobroker - enabled system.adapter.vis-icontwo.0 : vis-icontwo : 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-map.0 : vis-map : iobroker - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : iobroker - enabled system.adapter.vis.0 : vis : iobroker - enabled + system.adapter.vw-connect.0 : vw-connect : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.web.1 : web : iobroker - enabled, port: 60008, bind: 0.0.0.0, run as: admin + system.adapter.ws.0 : ws : iobroker - enabled, port: 60086, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : iobroker - enabled, port: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2190370-if00 + system.adapter.zigbee.1 : zigbee : iobroker - enabled, port: tcp://192.168.1.249:6638 + system.adapter.zigbee.2 : zigbee : iobroker - enabled, port: tcp://192.168.1.208:6638 + instance is alive Enabled adapters with bindings + system.adapter.admin.2 : admin : iobroker - enabled, port: 60082, bind: 0.0.0.0, run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.rest-api.0 : rest-api : iobroker - enabled, port: 8093, bind: 0.0.0.0, run as: admin + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : iobroker - enabled, port: 60084, bind: 0.0.0.0, run as: admin + system.adapter.sql.0 : sql : iobroker - enabled, port: 3306 + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.1 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.2 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.3 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.web.1 : web : iobroker - enabled, port: 60008, bind: 0.0.0.0, run as: admin + system.adapter.ws.0 : ws : iobroker - enabled, port: 60086, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : iobroker - enabled, port: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2190370-if00 + system.adapter.zigbee.1 : zigbee : iobroker - enabled, port: tcp://192.168.1.249:6638 + system.adapter.zigbee.2 : zigbee : iobroker - enabled, port: tcp://192.168.1.208:6638 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.17.7 , installed 6.17.7 Adapter "alexa-shoppinglist": 0.1.5, installed 0.1.5 Adapter "alexa-timer-vis": 0.3.0 , installed 0.3.0 Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "alias-manager": 1.2.6 , installed 1.2.6 Adapter "backitup" : 2.11.0 , installed 2.11.0 Adapter "broadlink2" : 2.2.0 , installed 2.2.0 Adapter "daswetter" : 3.1.13 , installed 3.1.13 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "devices" : 1.1.5 , installed 1.1.5 Adapter "discovery" : 4.5.0 , installed 4.5.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "echarts" : 1.7.2 , installed 1.7.2 Adapter "email" : 1.3.0 , installed 1.3.0 Adapter "energiefluss" : 3.6.0 , installed 3.6.0 Adapter "energiefluss-erweitert": 0.4.1, installed 0.4.1 Adapter "feiertage" : 1.2.0 , installed 1.2.0 Adapter "followthesun" : 0.5.0 , installed 0.5.0 Adapter "fritzdect" : 2.5.9 , installed 2.5.9 Adapter "fullybrowser" : 3.0.12 , installed 3.0.12 Adapter "ical" : 1.15.0 , installed 1.15.0 Adapter "iot" : 3.3.0 , installed 3.3.0 Adapter "javascript" : 8.3.1 , installed 8.3.1 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "logparser" : 2.2.2 , installed 2.2.2 Adapter "midea" : 0.0.7 , installed 0.0.7 Adapter "mqtt" : 5.2.0 , installed 5.2.0 Adapter "nut" : 1.6.0 , installed 1.6.0 Adapter "operating-hours": 1.0.6 , installed 1.0.6 Adapter "pi-hole" : 1.3.6 , installed 1.3.6 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "puppeteer" : 0.2.8 , installed 0.2.8 Adapter "pvforecast" : 2.9.1 , installed 2.9.1 Adapter "pylontech" : 0.0.10 , installed 0.0.10 Adapter "rest-api" : 1.1.0 , installed 1.1.0 Adapter "shelly" : 7.0.0 , installed 7.0.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "snmp" : 3.2.0 , installed 3.2.0 Adapter "socketio" : 6.7.0 , installed 6.7.0 Adapter "sourceanalytix": 0.4.14 , installed 0.4.14 Adapter "sql" : 2.2.0 , installed 2.2.0 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "telegram" : 3.2.1 , installed 3.2.1 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "time-switch" : 2.2.2 , installed 2.2.2 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "traccar" : 1.1.4 , installed 1.1.4 Adapter "trashschedule": 3.3.0 , installed 3.3.0 Adapter "tuya" : 3.15.0 , installed 3.15.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.9.63 , installed 2.9.63 Adapter "vis-2-widgets-energy": 0.3.11, installed 0.3.11 Adapter "vis-2-widgets-gauges": 1.0.3, installed 1.0.3 Adapter "vis-2-widgets-material": 1.3.32, installed 1.3.32 Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1 Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-icontwo" : 1.5.0 , installed 1.5.0 Adapter "vis-inventwo" : 3.3.4 , installed 3.3.4 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.1.1 Adapter "vis-map" : 1.1.0 , installed 1.1.0 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "vw-connect" : 0.6.0 , installed 0.6.0 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.1 , installed 2.6.1 Adapter "zigbee" : 1.10.3 , installed 1.9.7 [Updatable] Objects and States Please stand by - This may take a while Objects: 43473 States: 40158 *** OS-Repositories and Updates *** Hit:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:4 https://packages.grafana.com/oss/deb stable InRelease Hit:5 http://de.archive.ubuntu.com/ubuntu jammy-security InRelease Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:7 https://repo.zabbix.com/zabbix-agent2-plugins/1/ubuntu jammy InRelease Hit:8 https://repo.zabbix.com/zabbix/6.0/ubuntu jammy InRelease Reading package lists... Pending Updates: 41 *** 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:8093 0.0.0.0:* LISTEN 1000 41471 3203/io.rest-api.0 tcp 0 0 0.0.0.0:8082 0.0.0.0:* LISTEN 1000 70583558 1270559/io.web.0 tcp 0 0 0.0.0.0:8087 0.0.0.0:* LISTEN 1000 39871 2987/io.simple-api. tcp 0 0 0.0.0.0:6379 0.0.0.0:* LISTEN 120 25717 764/redis-server 0. tcp 0 0 0.0.0.0:5002 0.0.0.0:* LISTEN 0 22160 674/python3 tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 101 21067 637/systemd-resolve tcp 0 0 0.0.0.0:20050 0.0.0.0:* LISTEN 115 26779 809/zabbix_agent2 tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 114 25861 974/mariadbd tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN 123 25442 1131/grafana tcp 0 0 0.0.0.0:60008 0.0.0.0:* LISTEN 1000 70577104 1270566/io.web.1 tcp 0 0 0.0.0.0:60082 0.0.0.0:* LISTEN 1000 169150016 767300/io.admin.2 tcp 0 0 0.0.0.0:60084 0.0.0.0:* LISTEN 1000 70583582 1270591/io.socketio tcp 0 0 0.0.0.0:60086 0.0.0.0:* LISTEN 1000 54585016 29214/io.ws.0 tcp 0 0 0.0.0.0:1893 0.0.0.0:* LISTEN 1000 36717 2738/io.fullybrowse tcp 0 0 0.0.0.0:10051 0.0.0.0:* LISTEN 115 22425 1166/zabbix_proxy tcp 0 0 0.0.0.0:10050 0.0.0.0:* LISTEN 115 26777 809/zabbix_agent2 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 119 22164 848/mosquitto tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1000 27238 979/iobroker.js-con tcp 0 0 127.0.0.1:46311 0.0.0.0:* LISTEN 1000 46054 3703/chrome tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 0 25673 844/vsftpd tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 26691 828/sshd: /usr/sbin tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 18778 1/init tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 25616 773/apache2 udp 0 0 127.0.0.53:53 0.0.0.0:* 101 21066 637/systemd-resolve udp 0 0 0.0.0.0:111 0.0.0.0:* 0 18779 1/init udp 0 0 192.168.1.8:123 0.0.0.0:* 0 21971 739/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 0 21969 739/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 0 21964 739/ntpd udp 0 0 0.0.0.0:162 0.0.0.0:* 0 23304 1/init udp 0 0 0.0.0.0:59218 0.0.0.0:* 1000 33186 2155/io.snmp.0 udp 0 0 0.0.0.0:46158 0.0.0.0:* 1000 18364337 1409024/io.broadlin udp 0 0 0.0.0.0:5683 0.0.0.0:* 1000 84267854 2335172/io.shelly.0 udp 0 0 0.0.0.0:47519 0.0.0.0:* 1000 172359125 1409024/io.broadlin udp 0 0 0.0.0.0:6666 0.0.0.0:* 1000 61403213 564757/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1000 61403214 564757/io.tuya.0 udp 0 0 0.0.0.0:15001 0.0.0.0:* 1000 18364333 1409024/io.broadlin *** Log File - Last 25 Lines *** 2024-05-19 13:58:00.024 - info: midea.0 (1055385) Scheduled restart. 2024-05-19 13:58:00.028 - info: midea.0 (1055385) cleaned everything up... 2024-05-19 13:58:00.057 - info: midea.0 (1055385) terminating 2024-05-19 13:58:00.059 - info: midea.0 (1055385) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2024-05-19 13:58:00.071 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: Laden erlaubt: Solaranlage in Betrieb! 2024-05-19 13:58:00.071 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: Laden erlaubt: SoyoSource hat keine Einspeisung: 0W 2024-05-19 13:58:00.071 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: Laden erlaubt: Ziel SoC noch nicht erreicht 2024-05-19 13:58:00.071 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: Nur Huawei wird gesetzt 2024-05-19 13:58:00.071 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: mqtt.0.Huawei.Huawei_1cea67.MaxPower bis 90%: 2200W (unverändert) 2024-05-19 13:58:00.071 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: mqtt.0.Huawei.Huawei_1c35ac.MaxPower bis 90%: 2200W (unverändert) 2024-05-19 13:58:00.071 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: Huawei 1 Ausgangsleistung aktuell: 0W 2024-05-19 13:58:00.072 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: Huawei 2 Ausgangsleistung aktuell: 0W 2024-05-19 13:58:00.072 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: Pylontech heute geladen Total: 4.37kWh 2024-05-19 13:58:00.072 - info: javascript.1 (3183748) script.js.001_Routinen.Pylontech.LadesteuerungV2: Aktueller Stromverbrauch: 6W 2024-05-19 13:58:00.112 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 1056013 2024-05-19 13:58:00.536 - info: midea.0 (1055385) terminating 2024-05-19 13:58:00.758 - info: host.iobroker instance system.adapter.midea.0 scheduled normal terminated and will be restarted on schedule. 2024-05-19 13:58:00.760 - info: host.iobroker Restart adapter system.adapter.midea.0 because enabled 2024-05-19 13:58:02.334 - info: host.iobroker instance system.adapter.midea.0 started with pid 1056045 2024-05-19 13:58:03.016 - info: daswetter.0 (1056013) starting. Version 3.1.13 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.20.2, js-controller: 5.0.19 2024-05-19 13:58:05.193 - info: midea.0 (1056045) starting. Version 0.0.7 in /opt/iobroker/node_modules/iobroker.midea, node: v18.20.2, js-controller: 5.0.19 2024-05-19 13:58:05.705 - info: midea.0 (1056045) Login successful 2024-05-19 13:58:22.733 - info: daswetter.0 (1056013) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment 2024-05-19 13:58:23.245 - info: daswetter.0 (1056013) cleaned everything up... 2024-05-19 13:58:23.264 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) -
debug log der GitHub version an mail
tombox2020@gmail.com -
-
@tombox so, mit der aktuellen GitHub-Version ist die Log-Meldung wegen dem
Device not found for undefiniedschon mal weg.Steuern geht noch nicht.
Der Status scheint der Datenpunkt
work_statuszu seineuhome.0.APY2101E10200224.dps.15
Sollte da nicht Text statt einer 6 stehen? Laut App ist er gerade "Vollständig aufgeladen", Hier die Objektdaten:
{ "type": "state", "common": { "name": "work_status", "role": "text", "type": "string", "write": true, "read": true, "states": { "6": "6", "Running": "RUNNING", "standby": "STAND_BY", "Sleeping": "SLEEPING", "Charging": "CHARGING", "completed": "COMPLETED", "Recharge": "RECHARGE_NEEDED", "cleaning": "CLEANING", "goto_charge": "GOING_TO_CHARGE" } }, "native": {}, "from": "system.adapter.euhome.0", "user": "system.user.admin", "ts": 1716315054035, "_id": "euhome.0.APY2101E10200224.dps.15", "acl": { "object": 1636, "state": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator" } }6 war "Vollständig geladen" (controlMode 0)
2 ist "Reinigung läuft"
4 ist "Zurück zur Ladestation" (controlMode 3)
5 ist "lädt" (controlMode 0)Dito bei 5
controlMode
Objektdaten:{ "type": "state", "common": { "name": "controlMode", "role": "text", "type": "string", "write": true, "read": true, "states": { "0": "0", "auto": "AUTO", "SmallRoom": "SMALL_ROOM", "Spot": "SPOT", "Edge": "EDGE", "Nosweep": "NO_SWEEP", "single": "SINGLE", "point": "POINT", "standby": "STANDBY", "wall_follow": "WALL_FOLLOW", "smart": "SMART" } }, "native": {}, "from": "system.adapter.euhome.0", "user": "system.user.admin", "ts": 1716315054021, "_id": "euhome.0.APY2101E10200224.dps.5", "acl": { "object": 1636, "state": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator" } }Dementsprechend gibt es ein paar Warnungen wegen falscher Typen wenn ich das Gerät starte:
2024-05-21 20:26:16.640 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.5" has to be type "string" but received type "number" 2024-05-21 20:26:16.641 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.15" has to be type "string" but received type "number" 2024-05-21 20:26:16.641 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.102" has to be type "string" but received type "number" 2024-05-21 20:26:16.642 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.104" has to be type "string" but received type "number" 2024-05-21 20:26:16.643 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.106" has to be type "string" but received type "number" 2024-05-21 20:26:16.644 - warn: euhome.0 (2066696) Object of state "euhome.0.APY2101E10200224.dps.107" is missing the required property "common.type" 2024-05-21 20:26:16.644 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.108" has to be type "string" but received type "number" 2024-05-21 20:26:16.644 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.109" has to be type "string" but received type "number" 2024-05-21 20:26:16.645 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.110" has to be type "string" but received type "number" 2024-05-21 20:26:16.645 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.111" has to be type "string" but received type "number" 2024-05-21 20:26:16.645 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.118" has to be type "string" but received type "number" 2024-05-21 20:26:16.684 - warn: euhome.0 (2066696) Object of state "euhome.0.APY2101E10200224.dps.127" is missing the required property "common.type" 2024-05-21 20:26:16.685 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.135" has to be type "string" but received type "number" 2024-05-21 20:26:16.685 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.136" has to be type "string" but received type "number" 2024-05-21 20:26:16.686 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.138" has to be type "string" but received type "number" 2024-05-21 20:26:16.686 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.139" has to be type "string" but received type "number" 2024-05-21 20:26:16.687 - warn: euhome.0 (2066696) Object of state "euhome.0.APY2101E10200224.dps.150" is missing the required property "common.type" 2024-05-21 20:26:16.687 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.153" has to be type "string" but received type "number" 2024-05-21 20:26:16.687 - info: euhome.0 (2066696) State value to set for "euhome.0.APY2101E10200224.dps.154" has to be type "string" but received type "number" 2024-05-21 20:29:34.450 - warn: euhome.0 (2066696) Object of state "euhome.0.APY2101E10200224.dps.151" is missing the required property "common.type" 2024-05-21 20:29:35.164 - warn: euhome.0 (2066696) Object of state "euhome.0.APY2101E10200224.dps.151" is missing the required property "common.type" 2024-05-21 20:29:35.489 - warn: euhome.0 (2066696) Object of state "euhome.0.APY2101E10200224.dps.151" is missing the required property "common.type" 2024-05-21 20:29:35.981 - warn: euhome.0 (2066696) Object of state "euhome.0.APY2101E10200224.dps.151" is missing the required property "common.type"Steuern kann ich den auch per Alexa-TestCommand / Skill, wenn die Warnungen weg wären, wäre mir schon geholfen (ja, ich das Logging auch auf
Errorschalten) -
@bananajoe lösch mal den ganzen objektbaum 'dps' und starte den adapter neu. Da zieht sich schmodder gern aus vorversionen
-
@vierlingmt das hatte ich bereits gemacht
Bevor ich die neue Version des Adapters gestartet hatte, habe ich den ganzen Baum euhome.0.APY2101E10200224gelöscht -
Hey. I'm getting these errors for my S1 Pro.
The device populates but when I try to change status nothing happens. I see the device is shown as a T2080
Anyone provide any assistance?
-
@iorokermcgee Please post your log as text file using Code Tags </>
-
Hallo
Ist es auch irgendwie möglich, dass mir Alexa eine Nachricht sendet, wenn der Roboter hängen bleibt?
Mit freundlichen Grüßen
Semmy -
Ich habe den Adapter gerade erst entdeckt und installiert ( V0.1.5 ).
Verbindung zu Eufy Clean (Home) besteht.
Wenn ich meinen RoboVac G30 Hybrid per App steuere, werden auch jede Menge Datenpunkte unter dps aktualisiert - z.B. 5 aktualisiert sich beim Reinigungsstart auf Auto.
Setze ich aber einen dieser Datenpunkte, passiert gar nix am Roboter. Im Log sind keine Fehler zu sehen. Er sendet auch Befehle an den Robi - diese kommen dort entweder nicht an oder werden einfach ignoriert.
Hat noch jemand irgendeine Idee?
-
Gibts einen Trick wie man rausfinden kann, welcher Raum, welche ID hat?
-
@semmy Klar, auf Errorcode ragieren. Z.B. mit Blockly und als Trigger der Errorcode. Dann Sento Alexa textcommand oder was auch immer...
-
Müsst ihr den Adapter auch ständig neu starten? Ich mache das jetzt alle 15 min. Ich bekomme sonst keine neuen Werte vom Sauger.
Außerdem habe ich immernoch das Problem, das es mit den Räumen nicht klappt.im Datenpunk room_id sehe ich z.B. 2b95792b-6c65-4902-803c-2b64cd4bbf24
Schicke ich
{"method":"selectRoomsClean","data":{"roomIds":[2b95792b-6c65-4902-803c-2b64cd4bbf24],"cleanTimes":1}}
es geht auch nicht mit roomid 4 statt der langen kryptischen.
an remote.sendCommand passiert genau nichts.
