NEWS

Ciwa

das wars.....eine dämliche Kleinigkeit. Ist halt ein String........mano

Vielen Dank......

Gruß

Ciwa

Ciwa

Hallo,

das Problem wurde dank der Unterstützung von @Asgothian gelöst. Falls jemand das gleiche Gerät nutzen möchte, hier gehts zum Lösungspfad:

https://github.com/ioBroker/ioBroker.zigbee/issues/2374

Der Adapter muß manuell gepatched werden.

Noch mal vielen Dank für die Zeit.

Gruß

Ciwa

ciwa-alt created this issue in ioBroker/ioBroker.zigbee

closed Tuya Radarsensor ZG-205Z funktioniert aber permanent Fehlermeldung #2374

Ciwa

Ich hab jetzt die 15er Version Installiert. Die Fehlermeldung bleibt. Gibt es noch etwas was ich tun kann?

zigbee.0
	2025-02-10 21:24:56.552	error	Error while processing converters DEVICE_ID: 'a4c13835180427f5' cluster 'manuSpecificTuya' type 'commandDataReport'

Danke & Gruß

Ciwa

@asgothian

Wieder was gelernt...hier die Ausgabe.

2025-02-09 22:20:05.373  - warn: zigbee.0 (29407) ELEVATED I0: Zigbee Event of Type commandDataReport from device "0xa4c13835180427f5", incoming event: {"type":"commandDataReport","device":"0xa4c13835180427f5","endpoint":1,"data":{"seq":37120,"dpValues":[{"dp":1,"datatype":4,"data":{"type":"Buffer","data":[1]}}]},"linkquality":44,"groupID":0,"cluster":"manuSpecificTuya"}
2025-02-09 22:20:05.386  - warn: zigbee.0 (29407) ELEVATED I1: message received '{"linkquality":44}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:20:05.387  - warn: zigbee.0 (29407) ELEVATED I2: value generated '44' from device a4c13835180427f5 for 'Link quality'
2025-02-09 22:20:05.391  - warn: zigbee.0 (29407) ELEVATED I1: message received '{"presence":true}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:20:05.391  - warn: zigbee.0 (29407) ELEVATED I2: value generated 'true' from device a4c13835180427f5 for 'Indicates whether the device detected presence'
2025-02-09 22:20:05.466  - warn: zigbee.0 (29407) ELEVATED I0: Zigbee Event of Type commandDataReport from device "0xa4c13835180427f5", incoming event: {"type":"commandDataReport","device":"0xa4c13835180427f5","endpoint":1,"data":{"seq":37376,"dpValues":[{"dp":101,"datatype":4,"data":{"type":"Buffer","data":[1]}}]},"linkquality":47,"groupID":0,"cluster":"manuSpecificTuya"}
2025-02-09 22:20:05.496  - warn: zigbee.0 (29407) ELEVATED I1: message received '{"linkquality":47}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:20:05.502  - warn: zigbee.0 (29407) ELEVATED I2: value generated '47' from device a4c13835180427f5 for 'Link quality'
2025-02-09 22:20:05.507  - warn: zigbee.0 (29407) ELEVATED I1: message received '{"motion_state":"large"}' from device a4c13835180427f5 type 'ZG-205Z/A'

2025-02-09 22:25:39.338  - warn: zigbee.0 (29407) ELEVATED I1: message received '{"linkquality":23}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:25:39.339  - warn: zigbee.0 (29407) ELEVATED I2: value generated '23' from device a4c13835180427f5 for 'Link quality'
2025-02-09 22:25:39.342  - warn: zigbee.0 (29407) ELEVATED I1: message received '{}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:25:39.343  - error: zigbee.0 (29407) ELEVATED IE4: No value published for device a4c13835180427f5
2025-02-09 22:25:39.602  - debug: shelly.0 (28000) [onlineCheck] Checking SHEM-3#C8C9A33D6DA0#1 on 192.168.7.88:80
2025-02-09 22:25:39.616  - debug: shelly.0 (28000) [deviceStatusUpdate] SHEM-3#C8C9A33D6DA0#1: true
2025-02-09 22:25:41.427  - warn: zigbee.0 (29407) ELEVATED I0: Zigbee Event of Type commandDataReport from device "0xa4c13835180427f5", incoming event: {"type":"commandDataReport","device":"0xa4c13835180427f5","endpoint":1,"data":{"seq":44800,"dpValues":[{"dp":101,"datatype":4,"data":{"type":"Buffer","data":[4]}}]},"linkquality":34,"groupID":0,"cluster":"manuSpecificTuya"}
2025-02-09 22:25:41.441  - warn: zigbee.0 (29407) ELEVATED I1: message received '{"linkquality":34}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:25:41.441  - warn: zigbee.0 (29407) ELEVATED I2: value generated '34' from device a4c13835180427f5 for 'Link quality'
2025-02-09 22:25:41.441  - error: zigbee.0 (29407) Error while processing converters DEVICE_ID: 'a4c13835180427f5' cluster 'manuSpecificTuya' type 'commandDataReport'
2025-02-09 22:25:41.506  - warn: zigbee.0 (29407) ELEVATED I0: Zigbee Event of Type commandDataReport from device "0xa4c13835180427f5", incoming event: {"type":"commandDataReport","device":"0xa4c13835180427f5","endpoint":1,"data":{"seq":45056,"dpValues":[{"dp":122,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,220]}}]},"linkquality":31,"groupID":0,"cluster":"manuSpecificTuya"}
2025-02-09 22:25:41.520  - warn: zigbee.0 (29407) ELEVATED I1: message received '{"linkquality":31}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:25:41.521  - warn: zigbee.0 (29407) ELEVATED I2: value generated '31' from device a4c13835180427f5 for 'Link quality'
2025-02-09 22:25:41.530  - warn: zigbee.0 (29407) ELEVATED I1: message received '{}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:25:41.534  - error: zigbee.0 (29407) ELEVATED IE4: No value published for device a4c13835180427f5
2025-02-09 22:25:42.626  - warn: zigbee.0 (29407) ELEVATED I0: Zigbee Event of Type commandDataReport from device "0xa4c13835180427f5", incoming event: {"type":"commandDataReport","device":"0xa4c13835180427f5","endpoint":1,"data":{"seq":45312,"dpValues":[{"dp":122,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,140]}}]},"linkquality":26,"groupID":0,"cluster":"manuSpecificTuya"}
2025-02-09 22:25:42.637  - warn: zigbee.0 (29407) ELEVATED I1: message received '{"linkquality":26}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:25:42.637  - warn: zigbee.0 (29407) ELEVATED I2: value generated '26' from device a4c13835180427f5 for 'Link quality'
2025-02-09 22:25:42.640  - warn: zigbee.0 (29407) ELEVATED I1: message received '{}' from device a4c13835180427f5 type 'ZG-205Z/A'
2025-02-09 22:25:42.641  - error: zigbee.0 (29407) ELEVATED IE4: No value published for device a4c13835180427f5

Gruß
Ciwa

Ciwa

@thomas-braun

Nachforschungen laufen....der Werkzeugkasten ist im übrigen gut zu gebrauchen.....Hier noch mal die Ausgabe:

2025-02-09 20:51:29.066  - error: zigbee.0 (27989) Error while processing converters DEVICE_ID: 'a4c13835180427f5' cluster 'manuSpecificTuya' type 'commandDataReport'

Ciwa

@thomas-braun said in Zigbee Fehlermeldung -Error while processing converters-:

iob diag

======================= SUMMARY =======================
                        v.2025-02-02


 Static hostname: IoBroker-VM-V2
       Icon name: computer-vm
         Chassis: vm 🖴
  Virtualization: kvm
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.1.0-25-amd64
    Architecture: x86-64
 Hardware Vendor: QEMU
  Hardware Model: Standard PC _i440FX + PIIX, 1996_
Firmware Version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org

Installation:           kvm
Kernel:                 x86_64
Userland:               64 bit
Timezone:               Europe/Berlin (CET, +0100)
User-ID:                1000
Display-Server:         false
Boot Target:            multi-user.target

Pending OS-Updates:     0
Pending iob updates:    0

Nodejs-Installation:
/usr/bin/nodejs         v20.18.2
/usr/bin/node           v20.18.2
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.29.4

Recommended versions are nodejs 20.18.2 and npm 10.8.2
nodeJS installation is correct

MEMORY:
               total        used        free      shared  buff/cache   available
Mem:            6.2G        1.8G        3.1G        540K        1.6G        4.4G
Swap:           1.0G          0B        1.0G
Total:          7.2G        1.8G        4.1G

Active iob-Instances:   18
Upgrade policy: none

ioBroker Core:          js-controller           7.0.6
                        admin                   7.4.10

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : IoBroker-VM-V2                           -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.web.0                    : web                   : IoBroker-VM-V2                           - disabled, port: 8082, bind: 0.0.0.0, run as: admin

Objects:                10987
States:                 10087

Size of iob-Database:

21M     /opt/iobroker/iobroker-data/objects.jsonl
4.9M    /opt/iobroker/iobroker-data/states.jsonl


Operating System is the current Debian stable version codenamed 'bookworm'!

=================== END OF SUMMARY ====================

Bis auf die Tatsache das ich den Zigbee Stick nicht "by ID" eingebunden hab keine Auffälligkeiten...

Gruß

Ciwa

Ciwa

@thomas-braun said in Zigbee Fehlermeldung -Error while processing converters-:

iob fix

Hatter gemacht

Ciwa

@thomas-braun

Habs im Log gesehen....nachlässig. Updates laufen

Boot Target: umgestellt....

Danke

Ciwa

Ciwa

Adaptername: Zigbee
Link zu Adapterrepository: https://github.com/ioBroker/ioBroker.zigbee
Adapterversion: 1.10.14
js-controller Version: 20.17.0
Admin Version: 7.4.10
Hardwaresystem: HP Thin Client, Proxmox VM 8.3.2
Arbeitsspeicher: 6GB
Festplattenart: SSD
Betriebssystem: Linux Debian Bookworm
Nodejs-Version: 20.17.0
NPM-Version: 10.8.2
Installationsart: Manuell
Image, Docker genutzt: Nein

Hallo liebe Gemeinde,

ich habe folgenden "Schönheitsfehler" beim Betreiben eines Radarsensors ZG-205Z. Bei Bewegungserkennung kommt die Fehlermeldung:

zigbee.0
	2025-02-09 19:41:43.112	error	Error while processing converters DEVICE_ID: 'a4c13835180427f5' cluster 'manuSpecificTuya' type 'commandDataReport'

Das Gerät funktioniert soweit prima nur die Fehlermeldungen nerven halt. Könnt ihr mir den Wald zeigen bitte? Die Bäume sind im weg....vielen Dank

Ciwa

PS: Das Diag File...

======================= SUMMARY =======================
                        v.2025-02-02


 Static hostname: IoBroker-VM-V2
       Icon name: computer-vm
         Chassis: vm 🖴
  Virtualization: kvm
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.1.0-25-amd64
    Architecture: x86-64
 Hardware Vendor: QEMU
  Hardware Model: Standard PC _i440FX + PIIX, 1996_
Firmware Version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org

Installation:           kvm
Kernel:                 x86_64
Userland:               64 bit
Timezone:               Europe/Berlin (CET, +0100)
User-ID:                1000
Display-Server:         false
Boot Target:            graphical.target

Pending OS-Updates:     78
Pending iob updates:    0

Nodejs-Installation:
/usr/bin/nodejs         v20.17.0
/usr/bin/node           v20.17.0
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.29.3

Recommended versions are nodejs 20.18.2 and npm 10.8.2
nodeJS installation is correct

MEMORY:
               total        used        free      shared  buff/cache   available
Mem:            6.2G        2.4G        1.9G        540K        2.2G        3.8G
Swap:           1.0G          0B        1.0G
Total:          7.2G        2.4G        2.9G

Active iob-Instances:   18
Upgrade policy: none

ioBroker Core:          js-controller           7.0.6
                        admin                   7.4.10

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : IoBroker-VM-V2                           -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.web.0                    : web                   : IoBroker-VM-V2                           - disabled, port: 8082, bind: 0.0.0.0, run as: admin

Objects:                10991
States:                 10067

Size of iob-Database:

23M     /opt/iobroker/iobroker-data/objects.jsonl
3.7M    /opt/iobroker/iobroker-data/states.jsonl


Unknown release codenamed 'bookworm'. Please check yourself if the Operating System is actively maintained.

=================== END OF SUMMARY ====================

Ciwa

@armilar

das wars.....eine dämliche Kleinigkeit. Ist halt ein String........mano

Vielen Dank......

Gruß

Ciwa

Ciwa

Hallo,

ich habe meine beiden NS Panels auf die TypeScript v4.3.1.3 umgestellt. Funktioniert alles bestens......Nur der rechte Button lässt sich nicht überreden die Seite mit der Gäste Wlan Konfiguration anzuzeigen. Im Type Script kann ich "Page" nicht verwenden. Da kommt folgender Fehler:

19:57:42.657	error	javascript.0 (452) script.js.common.NS_Panel: TypeScript compilation failed: mode: page, ^ ERROR: Cannot find name 'page'.

 button2: {
        mode: page,     // Mögliche Werte wenn Rule2 definiert: 'page', 'toggle', 'set' - Wenn nicht definiert --> mode: null
        page: Wlan,     // Zielpage - Verwendet wenn mode = page (bisher button2Page)
        entity: null,   // Zielentity - Verwendet wenn mode = set oder toggle
        setValue: null  // Zielwert - Verwendet wenn mode = set
    }

Im NS Panel habe ich folgendes eingegeben:

Rule2 on Button2#state do Publish SmartHome/%topic%/tele/RESULT {"CustomRecv":"event,button2"} endon

Rule2 On

Wahrscheinlich nur eine dämliche Kleinigkeit.....aber ich komm nicht drauf

Danke für eure Hilfe

Gruß

Ciwa

NEWS

Ciwa

@Ciwa

Best posts made by Ciwa

Latest posts made by Ciwa

closed Tuya Radarsensor ZG-205Z funktioniert aber permanent Fehlermeldung #2374