Test Adapter zigbee2mqtt

biker1602

biker1602@iobroker:~$ /opt/zigbee2mqtt.io
-bash: /opt/zigbee2mqtt.io: No such file or directory
biker1602@iobroker:~$ npm audit
# npm audit report

axios  1.0.0 - 1.5.1
Severity: moderate
Axios Cross-Site Request Forgery Vulnerability - https://github.com/advisories/GHSA-wf5p-g6vw-rhxx
fix available via `npm audit fix`
node_modules/axios

braces  <3.0.3
Severity: high
Uncontrolled resource consumption in braces - https://github.com/advisories/GHSA-grv7-fg5c-xmjg
fix available via `npm audit fix`
node_modules/braces

follow-redirects  <=1.15.5
Severity: moderate
Follow Redirects improperly handles URLs in the url.parse() function - https://github.com/advisories/GHSA-jchw-25xp-jwwc
follow-redirects' Proxy-Authorization header kept across hosts - https://github.com/advisories/GHSA-cxjh-pqwp-8mfp
fix available via `npm audit fix`
node_modules/follow-redirects

ip  *
Severity: high
ip SSRF improper categorization in isPublic - https://github.com/advisories/GHSA-2p57-rm9w-gvfp
NPM IP package incorrectly identifies some private IP addresses as public - https://github.com/advisories/GHSA-78xj-cgh5-2h22
fix available via `npm audit fix --force`
Will install iobroker.ring@1.2.8, which is a breaking change
node_modules/ip
  werift  *
  Depends on vulnerable versions of ip
  node_modules/werift
    ring-client-api  >=11.0.1
    Depends on vulnerable versions of werift
    node_modules/ring-client-api
      iobroker.ring  >=2.0.0-beta.0
      Depends on vulnerable versions of ring-client-api
      node_modules/iobroker.ring

semver  6.0.0 - 6.3.0
Severity: moderate
semver vulnerable to Regular Expression Denial of Service - https://github.com/advisories/GHSA-c2qf-rxjj-qqgw
fix available via `npm audit fix`
node_modules/semver

tar  <6.2.1
Severity: moderate
Denial of service while parsing a tar file due to lack of folders count validation - https://github.com/advisories/GHSA-f5x3-32g6-xq36
fix available via `npm audit fix`
node_modules/tar

ws  7.0.0 - 7.5.9 || 8.0.0 - 8.17.0
Severity: high
ws affected by a DoS when handling a request with many HTTP headers - https://github.com/advisories/GHSA-3h5v-q93c-6h6q
ws affected by a DoS when handling a request with many HTTP headers - https://github.com/advisories/GHSA-3h5v-q93c-6h6q
fix available via `npm audit fix`
node_modules/engine.io-client/node_modules/ws
node_modules/ws
  engine.io-client  0.7.0 || 0.7.8 - 0.7.9 || 3.5.0 - 3.5.3 || 4.0.0-alpha.0 - 5.2.0
  Depends on vulnerable versions of ws
  node_modules/engine.io-client

11 vulnerabilities (4 moderate, 7 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force
biker1602@iobroker:~$ /opt/zigbee2mqtt
-bash: /opt/zigbee2mqtt: Is a directory
biker1602@iobroker:~$ npm audit
# npm audit report

axios  1.0.0 - 1.5.1
Severity: moderate
Axios Cross-Site Request Forgery Vulnerability - https://github.com/advisories/GHSA-wf5p-g6vw-rhxx
fix available via `npm audit fix`
node_modules/axios

braces  <3.0.3
Severity: high
Uncontrolled resource consumption in braces - https://github.com/advisories/GHSA-grv7-fg5c-xmjg
fix available via `npm audit fix`
node_modules/braces

follow-redirects  <=1.15.5
Severity: moderate
Follow Redirects improperly handles URLs in the url.parse() function - https://github.com/advisories/GHSA-jchw-25xp-jwwc
follow-redirects' Proxy-Authorization header kept across hosts - https://github.com/advisories/GHSA-cxjh-pqwp-8mfp
fix available via `npm audit fix`
node_modules/follow-redirects

ip  *
Severity: high
ip SSRF improper categorization in isPublic - https://github.com/advisories/GHSA-2p57-rm9w-gvfp
NPM IP package incorrectly identifies some private IP addresses as public - https://github.com/advisories/GHSA-78xj-cgh5-2h22
fix available via `npm audit fix --force`
Will install iobroker.ring@1.2.8, which is a breaking change
node_modules/ip
  werift  *
  Depends on vulnerable versions of ip
  node_modules/werift
    ring-client-api  >=11.0.1
    Depends on vulnerable versions of werift
    node_modules/ring-client-api
      iobroker.ring  >=2.0.0-beta.0
      Depends on vulnerable versions of ring-client-api
      node_modules/iobroker.ring

semver  6.0.0 - 6.3.0
Severity: moderate
semver vulnerable to Regular Expression Denial of Service - https://github.com/advisories/GHSA-c2qf-rxjj-qqgw
fix available via `npm audit fix`
node_modules/semver

tar  <6.2.1
Severity: moderate
Denial of service while parsing a tar file due to lack of folders count validation - https://github.com/advisories/GHSA-f5x3-32g6-xq36
fix available via `npm audit fix`
node_modules/tar

ws  7.0.0 - 7.5.9 || 8.0.0 - 8.17.0
Severity: high
ws affected by a DoS when handling a request with many HTTP headers - https://github.com/advisories/GHSA-3h5v-q93c-6h6q
ws affected by a DoS when handling a request with many HTTP headers - https://github.com/advisories/GHSA-3h5v-q93c-6h6q
fix available via `npm audit fix`
node_modules/engine.io-client/node_modules/ws
node_modules/ws
  engine.io-client  0.7.0 || 0.7.8 - 0.7.9 || 3.5.0 - 3.5.3 || 4.0.0-alpha.0 - 5.2.0
  Depends on vulnerable versions of ws
  node_modules/engine.io-client

11 vulnerabilities (4 moderate, 7 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force
biker1602@iobroker:~$

iker1602@iobroker:~$ cd /opt/zigbee2mqtt
biker1602@iobroker:/opt/zigbee2mqtt$ npm audit
found 0 vulnerabilities
biker1602@iobroker:/opt/zigbee2mqtt$ npm audit
found 0 vulnerabilities
biker1602@iobroker:/opt/zigbee2mqtt$

Irgendwie findet er da nichts oder?

MartinP

@biker1602 Okay, also arbeitest Du mit einer dem zigbee2mqtt Adapter vorgeschalteten zigbee2MQTT Server - Instanz...

biker1602

@martinp said in Test Adapter zigbee2mqtt:

@biker1602 Du solltest erstmal genauer beschreiben, wie Du den bisherigen USB-Koordinator mit ioBroker verbunden hast.

Der Einsatz des zigbee2mqtt Adapters legt ja nahe, dass der USB-Koordinator über einen zigbee2MQTT Server eingebunden ist...

Jedenfalls ist DAS der Verwendungszweck des zigbee2mqtt Adapters.

Der USB Koordinator wird durgeschliffen bei Proxmox und wird nur für den normalen Zigbee Adapter genutzt.

biker1602

@martinp said in Test Adapter zigbee2mqtt:

@biker1602 Okay, also arbeitest Du mit einer dem zigbee2mqtt Adapter vorgeschalteten zigbee2MQTT Server - Instanz...

Ich weiß schon garnichts mehr. Den SLZB-06 habe ich erst kurz. Mein Plan war Zigbee2mqtt zu nutzen und den anderen (sonoff) und den Zigbee Adapter zu deaktivieren.
Ich bekommen zigbee2mqtt aber nicht deinstalliert um alles nochmal neu zu machen.

Wenn ich den Status abfrage kommt folgende Meldung

biker1602@iobroker:~$ systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
     Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2024-07-11 11:00:35 CEST; 2s ago
    Process: 72010 ExecStart=/usr/bin/node index.js (code=exited, status=1/FAILURE)
   Main PID: 72010 (code=exited, status=1/FAILURE)
        CPU: 562ms

Asgothian

@biker1602 Ich denke damit kommt das hier zum Tragen:

@asgothian sagte in Test Adapter zigbee2mqtt:

Beim Zigbee2mqtt.io Projekt nachschauen - die haben eigentlich gute Doku zu solchen Fällen.

Nachtrag: wenn Du dir den Text der Fehlermeldung genau anschaust, dann beschwert er sich darüber das im YAML das Schlüsselwort "serial:" doppelt vorkommt. Das kommt von Deiner Anpassung als du den TCP Port eingetragen hast. berichtige das mal, dann sollte der laufen.

A.

biker1602

@asgothian
Ich habe probiert und versucht. Jetzt habe ich ihn im ioBroker drin kann ihn auch aufrufen.

Im Protokoll sind aber Fehlermeldungen

2024-07-11 16:16:04.346 - warn: zigbee2mqtt.0 (89552) Start try again in 1 seconds...
2024-07-11 16:16:09.744 - error: zigbee2mqtt.0 (89588) ===================================================
2024-07-11 16:16:09.747 - error: zigbee2mqtt.0 (89588) ===================================================
2024-07-11 16:16:09.747 - error: zigbee2mqtt.0 (89588) Legacy api is activated, so the adapter can not work correctly!!!
2024-07-11 16:16:09.747 - error: zigbee2mqtt.0 (89588) Please add the following lines to your Zigbee2MQTT configuration.yaml:
2024-07-11 16:16:09.747 - error: zigbee2mqtt.0 (89588) advanced:
2024-07-11 16:16:09.747 - error: zigbee2mqtt.0 (89588) legacy_api: false
2024-07-11 16:16:09.748 - error: zigbee2mqtt.0 (89588)
2024-07-11 16:16:09.748 - error: zigbee2mqtt.0 (89588) Legacy Availability Payload is activated, thus the adapter cannot represent the availability of the devices!!!
2024-07-11 16:16:09.748 - error: zigbee2mqtt.0 (89588) Please add the following lines to your Zigbee2MQTT configuration.yaml:
2024-07-11 16:16:09.748 - error: zigbee2mqtt.0 (89588) advanced:
2024-07-11 16:16:09.748 - error: zigbee2mqtt.0 (89588) legacy_availability_payload: false
2024-07-11 16:16:09.748 - error: zigbee2mqtt.0 (89588)
2024-07-11 16:16:09.749 - error: zigbee2mqtt.0 (89588) Device Legacy Payload is activated, therefore the adapter may process the states of the devices correctly!!!
2024-07-11 16:16:09.749 - error: zigbee2mqtt.0 (89588) Please add the following lines to your Zigbee2MQTT configuration.yaml:
2024-07-11 16:16:09.749 - error: zigbee2mqtt.0 (89588) device_options:
2024-07-11 16:16:09.749 - error: zigbee2mqtt.0 (89588) legacy: false
2024-07-11 16:16:09.749 - error: zigbee2mqtt.0 (89588) ===================================================
2024-07-11 16:16:09.749 - error: zigbee2mqtt.0 (89588) ===================================================

und der Adapter wird nicht grün

Asgothian

@biker1602 Hast du den getan wozu dich das Log auffordert ?

crunchip

@biker1602 sagte in Test Adapter zigbee2mqtt:

configuration.yaml

Wie sieht die denn im Ganzen aus?

biker1602

@asgothian said in Test Adapter zigbee2mqtt:

@biker1602 Hast du den getan wozu dich das Log auffordert ?

Soll ich das in der Configuration eintragen?
legacy_api: false
legacy_availability_payload: false

biker1602

@crunchip said in Test Adapter zigbee2mqtt:

@biker1602 sagte in Test Adapter zigbee2mqtt:

configuration.yaml

Wie sieht die denn im Ganzen aus?

Das ist Protokoll im iobroker da ist nicht mehr.

biker1602

@crunchip said in Test Adapter zigbee2mqtt:

@biker1602 sagte in Test Adapter zigbee2mqtt:

configuration.yaml

Wie sieht die denn im Ganzen aus?

Das ist die Config

# Home Assistant integration (MQTT discovery)
homeassistant: false

# Enable the frontend, runs on port 8080 by default
frontend: true

# allow new device to join
# permit_join: true

# MQTT settings
mqtt:
  # MQTT base topic for zigbee2mqtt MQTT messages
  base_topic: zigbee2mqtt
  # MQTT server URL
  server: 'mqtt://localhost'
  # MQTT server authentication, uncomment if required:
   user: biker1602
   password: Ulli1602

# Serial settings
  # Achtung: Wenn Sie das Z2M-Add-on für HA verwenden, ist es besser, die Yaml-Konfigurationsdatei direkt zu bearbeiten
serial:
# Location of SLZB-06
  port: tcp://192.168.57.90:6638
  baudrate: 115200
  adapter: zstack
# Grüne LED deaktivieren?
  disable_led: false
# Ausgangsleistung auf max. 20 einstellen
advanced:
  transmit_power: 20
# Advanced settings
  network_key: GENERATE
  pan_id: GENERATE
  ext_pan_id: GENERATE

crunchip

@biker1602 da fehlt bisserl was, im ersten Beitrag steht was zwingend eingetragen werden muss und in der Adapterbeschreibung steht es etwas ausführlicher

biker1602

@crunchip said in Test Adapter zigbee2mqtt:

@biker1602 da fehlt bisserl was, im ersten Beitrag steht was zwingend eingetragen werden muss und in der Adapterbeschreibung steht es etwas ausführlicher

Ich mache einen anderen Tag weiter oder lasse es ganz. Ich sehe den Wald vor lauter Bäumen nicht mehr.
Kann mir jemand sagen wie ich das ganze in putty deinstallieren kann das auch alles verschwindet und nicht irgendwo noch versteckte Dateien sind dich nicht gelöscht werden?

arteck

@biker1602 es gibt keine versteckten Datei .. bist ja nicht unter Windows

und wenn du die config richtig machst dann geht das auch..man muss sich halt einlesen.. es ist nicht reinstöpseln ..fettisch

es ist alles gut Dokumentiert (wozu schreiben wir den quatsch)

biker1602

@arteck said in Test Adapter zigbee2mqtt:

@biker1602 es gibt keine versteckten Datei .. bist ja nicht unter Windows

und wenn du die config richtig machst dann geht das auch..man muss sich halt einlesen.. es ist nicht reinstöpseln ..fettisch

es ist alles gut Dokumentiert (wozu schreiben wir den quatsch)

Entschuldigung Vielleicht war ich ja gestern auch genervt weil es nicht funktioniert hat. Ich hatte es dann gestern doch noch hinbekommen und war auch glücklich das ich Geräte anlernen konnte. Heute Morgen denke ich mal sehen was bei HA passiert und da war der Adapter auch zu sehen. Ich in meinem Übermut wollte ihne konfigurieren und habe plötzlich Panik bekommen und abgebrochen. seitdem kann ich keine Geräte mehr anlernen und es kommt ein Roter Warnhinweis unter Protokolle.

zh:zstack:znp: Error while parsing to ZpiObject 'TypeError: Cannot read properties of undefined (reading 'name') at Function.readParameters (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/zpiObject.ts:88:63) at Function.fromUnpiFrame (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/zpiObject.ts:73:30) at Znp.onUnpiParsed (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:93:38) at Parser.emit (node:events:519:28) at Parser.parseNext (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:45:26) at Parser._transform (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:19:14) at Parser.Transform._write (node:internal/streams/transform:171:8) at writeOrBuffer (node:internal/streams/writable:564:12) at _write (node:internal/streams/writable:493:10) at Parser.Writable.write (node:internal/streams/writable:502:10)'

Das kann doch nur mit dem HA zusamenhängen oder? Ich hatte in der Configurationstatei nachgesehen da war eine Zeile mit HA dazu gekommen. Die habe ich gelöscht aber das hat das Problem nicht behoben. Hast du eine Ahnung was ich da noch machen kann?
Danke

2024-07-12 00:00:00.009 - info: hekr.0 (65528) Scheduled restart.
2024-07-12 00:00:00.032 - info: hekr.0 (65528) terminating
2024-07-12 00:00:00.032 - info: hekr.0 (65528) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2024-07-12 00:00:00.523 - info: hekr.0 (65528) terminating
2024-07-12 00:00:01.000 - debug: javascript.0 (64883) [sunTimeSchedules] Times: {"solarNoon":"2024-07-12T11:24:45.080Z","nadir":"2024-07-12T23:24:45.080Z","sunrise":"2024-07-12T03:12:14.591Z","sunset":"2024-07-12T19:37:15.569Z","sunriseEnd":"2024-07-12T03:16:42.195Z","sunsetStart":"2024-07-12T19:32:47.965Z","dawn":"2024-07-12T02:25:23.002Z","dusk":"2024-07-12T20:24:07.158Z","nauticalDawn":"2024-07-12T01:14:32.792Z","nauticalDusk":"2024-07-12T21:34:57.368Z","nightEnd":null,"night":null,"goldenHourEnd":"2024-07-12T04:06:04.637Z","goldenHour":"2024-07-12T18:43:25.523Z"}
2024-07-12 00:00:01.023 - debug: javascript.0 (64883) [sunTimeSchedules] Next: 2024-07-12T22:00:01.000Z
2024-07-12 00:00:02.476 - info: hekr.0 (98780) starting. Version 0.0.6 in /opt/iobroker/node_modules/iobroker.hekr, node: v20.15.1, js-controller: 5.0.19
2024-07-12 00:00:03.511 - info: hekr.0 (98780) Login successful
2024-07-12 00:00:04.163 - info: hekr.0 (98780) 1 devices found.
2024-07-12 00:00:04.479 - info: hekr.0 (98780) 1 template found.
2024-07-12 00:00:08.690 - info: feiertage.0 (98901) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.feiertage, node: v20.15.1, js-controller: 5.0.19
2024-07-12 00:00:08.824 - info: feiertage.0 (98901) Next holiday: Tag der deutschen Einheit is in 83 days on 03.10.2024
2024-07-12 00:00:08.831 - info: feiertage.0 (98901) all objects written
2024-07-12 00:00:08.875 - info: feiertage.0 (98901) Terminated (NO_ERROR): Without reason
2024-07-12 02:01:17.300 - warn: fb-checkpresence.0 (66044) checkDevices: getDeviceList: AxiosError maxContentLength size of -1 exceeded
2024-07-12 03:00:11.924 - warn: broadlink2.0 (99046) device RM:RMMINI-1a-02-40 not found, please rescan later again or delete it! It was: 192.168.57.109,80,10039,Broadlink Mini,0,[object Object],78:0f:77:1a:02:40,RM,RM:RMMINI-1a-02-40,0x2737,RM Mini,RMMINI-1a-02-40,RM:RMMINI-1a-02-40,50
2024-07-12 04:46:32.180 - warn: fb-checkpresence.0 (66044) checkDevices: getDeviceList: AxiosError maxContentLength size of -1 exceeded
2024-07-12 05:04:03.167 - info: javascript.0 (64883) script.js.Meine_Schalter.Büro.Test_Telegram_Menü:
2024-07-12 06:00:00.009 - info: hekr.0 (98780) Scheduled restart.
2024-07-12 06:00:00.015 - info: hekr.0 (98780) terminating
2024-07-12 06:00:00.015 - info: hekr.0 (98780) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2024-07-12 06:00:00.515 - info: hekr.0 (98780) terminating
2024-07-12 06:00:02.482 - info: hekr.0 (99264) starting. Version 0.0.6 in /opt/iobroker/node_modules/iobroker.hekr, node: v20.15.1, js-controller: 5.0.19
2024-07-12 06:00:03.257 - info: hekr.0 (99264) Login successful
2024-07-12 06:00:03.876 - info: hekr.0 (99264) 1 devices found.
2024-07-12 06:00:04.723 - info: hekr.0 (99264) 1 template found.
2024-07-12 06:31:34.430 - info: javascript.0 (64883) script.js.Meine_Schalter.Küche.Kaffemaschine: Bitteschön, Dein Kaffeeautomat einschalten und spülen ist fertig
2024-07-12 06:39:06.821 - info: javascript.0 (64883) script.js.Meine_Schalter.Küche.Kaffemaschine: Bitteschön, Dein Caffè Crema ist fertig
2024-07-12 06:44:13.448 - info: javascript.0 (64883) script.js.Meine_Schalter.Küche.Kaffemaschine: Bitteschön, Dein Caffè Crema ist fertig
2024-07-12 06:45:48.277 - warn: zigbee2mqtt.0 (98069) z2m: Device '0x00158d000487408c' left the network
2024-07-12 06:58:14.862 - info: javascript.0 (64883) Stopping script script.js.Meine_Schalter.Schlafzimmer.Ventilator
2024-07-12 06:58:14.907 - info: javascript.0 (64883) Start JavaScript script.js.Meine_Schalter.Schlafzimmer.Ventilator (Blockly)
2024-07-12 06:58:14.925 - info: javascript.0 (64883) script.js.Meine_Schalter.Schlafzimmer.Ventilator: registered 0 subscriptions, 1 schedule, 0 messages, 0 logs and 0 file subscriptions
2024-07-12 07:25:00.649 - info: javascript.0 (64883) Stopping script script.js.Meine_Schalter.Küche.Musik_Küche_Bewegungsmelder
2024-07-12 07:25:00.696 - info: javascript.0 (64883) Start JavaScript script.js.Meine_Schalter.Küche.Musik_Küche_Bewegungsmelder (Blockly)
2024-07-12 07:25:00.711 - info: javascript.0 (64883) script.js.Meine_Schalter.Küche.Musik_Küche_Bewegungsmelder: registered 2 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
2024-07-12 07:38:11.826 - error: zigbee2mqtt.0 (98069) zh:zstack:znp: Error while parsing to ZpiObject 'TypeError: Cannot read properties of undefined (reading 'name')
at Function.readParameters (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/zpiObject.ts:88:63)
at Function.fromUnpiFrame (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/zpiObject.ts:73:30)
at Znp.onUnpiParsed (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:93:38)
at Parser.emit (node:events:519:28)
at Parser.parseNext (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:45:26)
at Parser._transform (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:19:14)
at Parser.Transform._write (node:internal/streams/transform:171:8)
at writeOrBuffer (node:internal/streams/writable:564:12)
at _write (node:internal/streams/writable:493:10)
at Parser.Writable.write (node:internal/streams/writable:502:10)'
2024-07-12 07:44:33.170 - warn: zigbee2mqtt.0 (98069) z2m: Failed to ping 'Osram Steckdose Küche' (attempt 1/2, ZCL command 0x7cb03eaa0a094194/3 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":33593,"destendpoint":3,"srcendpoint":1,"clusterid":0,"transid":211,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,87,0,0,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')))
2024-07-12 07:44:36.178 - warn: zigbee2mqtt.0 (98069) z2m: Failed to ping 'Osram Steckdose Küche' (attempt 2/2, ZCL command 0x7cb03eaa0a094194/3 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":33593,"destendpoint":3,"srcendpoint":1,"clusterid":0,"transid":212,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,88,0,0,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')))
2024-07-12 07:54:37.189 - warn: zigbee2mqtt.0 (98069) z2m: Failed to ping 'Osram Steckdose Küche' (attempt 1/1, ZCL command 0x7cb03eaa0a094194/3 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":33593,"destendpoint":3,"srcendpoint":1,"clusterid":0,"transid":213,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,89,0,0,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')))
2024-07-12 07:56:06.936 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 07:56:16.769 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 07:56:23.430 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 07:56:30.058 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 07:56:41.258 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 07:57:31.211 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 07:58:51.162 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:00:12.992 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:00:19.085 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:00:45.364 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:02:50.022 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:04:38.197 - warn: zigbee2mqtt.0 (98069) z2m: Failed to ping 'Osram Steckdose Küche' (attempt 1/1, ZCL command 0x7cb03eaa0a094194/3 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":33593,"destendpoint":3,"srcendpoint":1,"clusterid":0,"transid":214,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,90,0,0,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')))
2024-07-12 08:07:40.767 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:11:40.196 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:11:50.666 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:14:39.206 - warn: zigbee2mqtt.0 (98069) z2m: Failed to ping 'Osram Steckdose Küche' (attempt 1/1, ZCL command 0x7cb03eaa0a094194/3 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":33593,"destendpoint":3,"srcendpoint":1,"clusterid":0,"transid":215,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,91,0,0,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')))
2024-07-12 08:18:41.767 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:18:50.614 - error: zigbee2mqtt.0 (98069) z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')'
2024-07-12 08:24:40.215 - warn: zigbee2mqtt.0 (98069) z2m: Failed to ping 'Osram Steckdose Küche' (attempt 1/1, ZCL command 0x7cb03eaa0a094194/3 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":33593,"destendpoint":3,"srcendpoint":1,"clusterid":0,"transid":216,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,92,0,0,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')))

1Topf

@biker1602 sagte in Test Adapter zigbee2mqtt:

Ich bekommen zigbee2mqtt aber nicht deinstalliert um alles nochmal neu zu machen.

Nur falls es dich noch interessiert, wie man es löscht:

sudo rm -rf /opt/zigbee2mqtt

arteck

@1topf sagte in Test Adapter zigbee2mqtt:

/opt/zigbee2mqtt

wenns da installiert wurde....

@biker1602 sagte in Test Adapter zigbee2mqtt:

und habe plötzlich Panik bekommen und abgebrochen

das ist jetzt nicht dein erst oder.. währe da dein Haus explodiert oder hättest du das Internet damit gelöscht oder wie...
kein plan was du da anstellst .. vor allem im HA bareich..

prüfe nochmal alles angefangen von zigbee2mqtt (läuft es ohne fehler) dann den adapter verbindet sich dieser mit zigbee2mqtt ohne fehler..

biker1602

@arteck said in Test Adapter zigbee2mqtt:

prüfe nochmal alles angefangen von zigbee2mqtt (läuft es ohne fehler) dann den adapter verbindet sich dieser mit zigbee2mqtt ohne fehler..

Ich habe jetzt erst bei HA ein Backup eingespielt den den SLZB neu gestartet und ich kann jetzt wieder Geräte anlernen und obwohl ich availability: true hinterlegt habe, zeigt er mir unter Objekte die Geräte mit Gelb und als nicht verbunden an.

Die Geräte reagieren aber so z.B Bewegungsmelder oder so. Das macht mich stutzig.

arteck

@biker1602 hast du alle gesetzt

advanced:
     legacy_api: false
     legacy_availability_payload: false
     output: json
device_options:
     legacy: false
availability: true

biker1602

@arteck
device options: stand nicht drin alles andere ja und jetzt sind sie auch Grün.

Eine Frage habe ich noch. Wieso werden auf dem Dashbord nicht alle Geräte angezeigt?
Unter Geräte sind sie alle da.

NEWS

Test Adapter zigbee2mqtt

Support us

793
Online

31.7k
Users

79.8k
Topics

1.3m
Posts

NEWS

Test Adapter zigbee2mqtt

Support us

793Online

31.7kUsers

79.8kTopics

1.3mPosts

793
Online

31.7k
Users

79.8k
Topics

1.3m
Posts