Zigbee-Adapter zickt. Flashen lassen oder tauschen?

[dexic]

@arteck

Du meinst also, dass ich alle Geräte neu anlernen muss. Muss ich sie dazu im ioBroker löschen oder werden sie einfach wieder "an ihren Platz" gebracht?

[arteck]

@dexic nur anlernen .. reicht.. löschen brauchst nicht

[dexic]

@arteck
Die nächste Hürde nach dem Klick auf "Kopplung jetzt starten!"

Error: Failed to open the network: Error: SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')
    at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:320:27
    at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
    at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:206:13
    at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
    at ZStackAdapter.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:203:9)
    at Controller.permitJoinInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:246:13)
    at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:234:9)
    at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:521:17). undefined
Pairing started 

[arteck]

@dexic sagte in Zigbee-Adapter zickt. Flashen lassen oder tauschen?:

zigbeecontroller

zeigmal die adapter Einstellungen

und die 50 Zeilen nach adapter start

[dexic]

@arteck

Oben habe ich eine LOG gepostet nach einem kompletten Neustart des Raspi. Soll ich das wiederholen?

[arteck]

@dexic sagte in Zigbee-Adapter zickt. Flashen lassen oder tauschen?:

Oben habe ich eine LOG gepostet nach einem kompletten Neustart des Raspi. Soll ich das wiederholen?

ich will jetzt sehen..

adapter stop..adapter starten.. dann posten..

[dexic]

@arteck

iobroker.2024-02-24.log

Danke für deine Unterstützung!

[arteck]

@dexic von debug Einstellung war nicht die rede...

also noch mal... und nochmal 50 Zeilen pi mal auge NACH ADAPTER START.. nicht das komplette LOG

[dexic]

@arteck
Ich hoffe, das passt jetzt. Sorry für das Missverständnis.

zigbee.0
	2024-02-24 09:38:53.568	warn	DeviceAvailability:Failed to ping 0xa4c13872a43d86fd TS011F
zigbee.0
	2024-02-24 09:38:53.553	warn	DeviceAvailability:Failed to ping 0xa4c1381cbfd11d66 TS011F
zigbee.0
	2024-02-24 09:38:53.537	warn	DeviceAvailability:Failed to ping 0xa4c138867bdf42a2 TS011F
zigbee.0
	2024-02-24 09:38:53.520	warn	DeviceAvailability:Failed to ping 0xa4c138de74061d48 TS011F
zigbee.0
	2024-02-24 09:38:53.504	warn	DeviceAvailability:Failed to ping 0xa4c1386363b09d42 TS011F
zigbee.0
	2024-02-24 09:38:53.488	warn	DeviceAvailability:Failed to ping 0xa4c1389f9914931e TS011F
zigbee.0
	2024-02-24 09:38:53.472	warn	DeviceAvailability:Failed to ping 0xa4c138e7c52b7d7f TS011F
zigbee.0
	2024-02-24 09:38:53.429	warn	DeviceAvailability:Failed to ping 0xa4c138d046d9d5ae TS011F
zigbee.0
	2024-02-24 09:38:47.367	info	debug devices set to []
zigbee.0
	2024-02-24 09:38:47.031	info	Zigbee started
zigbee.0
	2024-02-24 09:38:47.030	info	0xa4c13872a43d86fd (addr 47187): A1Z - Nous Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 09:38:47.027	info	0xa4c1381cbfd11d66 (addr 50830): A1Z - Nous Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 09:38:47.024	info	0xa4c138867bdf42a2 (addr 22255): A1Z - Nous Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 09:38:47.021	info	0xa4c138de74061d48 (addr 32429): A1Z - Nous Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 09:38:47.018	info	0x00158d000949a629 (addr 29713): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0
	2024-02-24 09:38:47.016	info	0x00158d0009451e5b (addr 13394): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
zigbee.0
	2024-02-24 09:38:47.013	info	0x00158d0008746aee (addr 58357): DJT11LM - Xiaomi Aqara vibration sensor (EndDevice)
zigbee.0
	2024-02-24 09:38:47.009	info	0x00158d0008dffe7e (addr 56436): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
zigbee.0
	2024-02-24 09:38:47.006	info	0x00158d0008d02230 (addr 31821): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
zigbee.0
	2024-02-24 09:38:47.002	info	0x00158d00094651c7 (addr 29657): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0
	2024-02-24 09:38:46.999	info	0x00158d00091b229a (addr 43507): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0
	2024-02-24 09:38:46.997	info	0xa4c1386363b09d42 (addr 37503): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 09:38:46.994	info	0xa4c1389f9914931e (addr 51274): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 09:38:46.991	info	0x00158d00094651a4 (addr 60844): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
zigbee.0
	2024-02-24 09:38:46.989	info	0x003c84fffed660a9 (addr 62062): BRT-100-TRV - Moes Thermostatic radiator valve (EndDevice)
zigbee.0
	2024-02-24 09:38:46.975	info	0xa4c138e7c52b7d7f (addr 38827): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 09:38:46.967	info	0xa4c138d046d9d5ae (addr 102): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 09:38:46.888	info	Currently 17 devices are joined:
zigbee.0
	2024-02-24 09:38:46.869	info	--> transmitPower : high+
zigbee.0
	2024-02-24 09:38:46.848	info	Unable to disable LED, unsupported function.
zigbee.0
	2024-02-24 09:38:46.831	info	Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20221226}}
zigbee.0
	2024-02-24 09:38:42.086	info	Installed Version: iobroker.zigbee@1.10.1
zigbee.0
	2024-02-24 09:38:41.795	info	Starting Zigbee npm ...
zigbee.0
	2024-02-24 09:38:41.793	info	delete old Backup files. keep only last 10
zigbee.0
	2024-02-24 09:38:41.693	info	starting. Version 1.10.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.19.0, js-controller: 5.0.19
host.raspberrypi
	2024-02-24 09:38:37.278	info	instance system.adapter.zigbee.0 started with pid 5548
host.raspberrypi
	2024-02-24 09:38:37.234	info	"system.adapter.zigbee.0" enabled
host.raspberrypi
	2024-02-24 09:38:34.825	info	instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
zigbee.0
	2024-02-24 09:38:34.250	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
zigbee.0
	2024-02-24 09:38:34.248	info	terminating
host.raspberrypi
	2024-02-24 09:38:33.830	info	stopInstance system.adapter.zigbee.0 send kill signal
zigbee.0
	2024-02-24 09:38:33.751	info	Zigbee: disabling joining new devices.
zigbee.0
	2024-02-24 09:38:33.747	info	cleaned everything up...
zigbee.0
	2024-02-24 09:38:33.744	info	Got terminate signal TERMINATE_YOURSELF
host.raspberrypi
	2024-02-24 09:38:33.732	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)

[arteck]

@dexic sagte in Zigbee-Adapter zickt. Flashen lassen oder tauschen?:

TS011F

sieht doch gut aus...

musst nur die

0xa4c138867bdf42a2 TS011F
0xa4c138de74061d48 TS011F
0xa4c1386363b09d42 TS011F
0xa4c1389f9914931e TS011F
0xa4c138e7c52b7d7f TS011F
0xa4c138d046d9d5ae TS011F

neu anlernen

[dexic]

@arteck

Das sieht bei mir auf dem Schirm anders aus ...

Und wenn ich es dann versuche:

[arteck]

@dexic mach erstmal.. wenn die Router im netz sind kann sein dass der rest dann von sich aus rein kommt.

machmal bitte

https://github.com/ioBroker/ioBroker.zigbee/wiki/GIT-install

und schau nochmal.. kein plan warum der pairing modus nicht startet

[dexic]

@arteck said in Zigbee-Adapter zickt. Flashen lassen oder tauschen?:

mach erstmal.. wenn die Router im netz sind kann sein dass der rest dann von sich aus rein kommt.

Den USB-Adapter habe ich am RPi schon getauscht. Jetzt kommt beim Einschalten des Kopplungsmodus dieser komische Fehler im Schirm.

GIT-Install habe ich durchgeführt mit exit code = 0, also problemlos. Das ist das Ergebnis:

Leider bleiben die Geräte alle weiterhin unverbunden. Das Protokoll sagt jetzt:

zigbee.0
	2024-02-24 11:03:40.839	warn	DeviceAvailability:Failed to ping 0xa4c13872a43d86fd TS011F
zigbee.0
	2024-02-24 11:03:40.820	warn	DeviceAvailability:Failed to ping 0xa4c1381cbfd11d66 TS011F
zigbee.0
	2024-02-24 11:03:40.805	warn	DeviceAvailability:Failed to ping 0xa4c138867bdf42a2 TS011F
zigbee.0
	2024-02-24 11:03:40.789	warn	DeviceAvailability:Failed to ping 0xa4c138de74061d48 TS011F
zigbee.0
	2024-02-24 11:03:40.753	warn	DeviceAvailability:Failed to ping 0xa4c1386363b09d42 TS011F
zigbee.0
	2024-02-24 11:03:40.734	warn	DeviceAvailability:Failed to ping 0xa4c1389f9914931e TS011F
zigbee.0
	2024-02-24 11:03:40.718	warn	DeviceAvailability:Failed to ping 0xa4c138e7c52b7d7f TS011F
zigbee.0
	2024-02-24 11:03:40.702	warn	DeviceAvailability:Failed to ping 0xa4c138d046d9d5ae TS011F
zigbee.0
	2024-02-24 11:03:34.022	info	debug devices set to []
zigbee.0
	2024-02-24 11:03:33.886	info	Zigbee started
zigbee.0
	2024-02-24 11:03:33.885	info	0xa4c13872a43d86fd (addr 47187): A1Z - Nous Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 11:03:33.883	info	0xa4c1381cbfd11d66 (addr 50830): A1Z - Nous Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 11:03:33.880	info	0xa4c138867bdf42a2 (addr 22255): A1Z - Nous Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 11:03:33.877	info	0xa4c138de74061d48 (addr 32429): A1Z - Nous Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 11:03:33.873	info	0x00158d000949a629 (addr 29713): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
zigbee.0
	2024-02-24 11:03:33.871	info	0x00158d0009451e5b (addr 13394): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice)
zigbee.0
	2024-02-24 11:03:33.868	info	0x00158d0008746aee (addr 58357): DJT11LM - Aqara Vibration sensor (EndDevice)
zigbee.0
	2024-02-24 11:03:33.865	info	0x00158d0008dffe7e (addr 56436): SJCGQ11LM - Aqara Water leak sensor (EndDevice)
zigbee.0
	2024-02-24 11:03:33.861	info	0x00158d0008d02230 (addr 31821): WXKG11LM - Aqara Wireless mini switch (EndDevice)
zigbee.0
	2024-02-24 11:03:33.857	info	0x00158d00094651c7 (addr 29657): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
zigbee.0
	2024-02-24 11:03:33.855	info	0x00158d00091b229a (addr 43507): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
zigbee.0
	2024-02-24 11:03:33.852	info	0xa4c1386363b09d42 (addr 37503): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 11:03:33.850	info	0xa4c1389f9914931e (addr 51274): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 11:03:33.847	info	0x00158d00094651a4 (addr 60844): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
zigbee.0
	2024-02-24 11:03:33.844	info	0x003c84fffed660a9 (addr 62062): BRT-100-TRV - Moes Thermostatic radiator valve (EndDevice)
zigbee.0
	2024-02-24 11:03:33.830	info	0xa4c138e7c52b7d7f (addr 38827): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 11:03:33.822	info	0xa4c138d046d9d5ae (addr 102): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
zigbee.0
	2024-02-24 11:03:33.742	info	Currently 17 devices are joined:
zigbee.0
	2024-02-24 11:03:33.718	info	--> transmitPower : high+
zigbee.0
	2024-02-24 11:03:33.693	info	Unable to disable LED, unsupported function.
zigbee.0
	2024-02-24 11:03:33.669	info	Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20221226}}
zigbee.0
	2024-02-24 11:03:29.107	info	Installed Version: ioBroker/ioBroker.zigbee#789c70c588651e4a06ba495ddf572adb8d9a1b7c
zigbee.0
	2024-02-24 11:03:28.741	info	Starting Zigbee npm ...
zigbee.0
	2024-02-24 11:03:28.739	info	delete old Backup files. keep only last 10
zigbee.0
	2024-02-24 11:03:28.637	info	starting. Version 1.10.2 (non-npm: ioBroker/ioBroker.zigbee#789c70c588651e4a06ba495ddf572adb8d9a1b7c) in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.19.0, js-controller: 5.0.19
host.raspberrypi
	2024-02-24 11:03:23.952	info	instance system.adapter.zigbee.0 started with pid 5990
host.raspberrypi
	2024-02-24 11:03:23.876	info	"system.adapter.zigbee.0" enabled
host.raspberrypi
	2024-02-24 11:03:22.208	info	instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

[arteck]

@dexic kannst du jetzt das pairing starten ?

[dexic]

@arteck
Nein, noch immer nicht. Ich bin ratlos...

[dexic]

@dexic

Soll ich mal einen Sonoff testen?

[Gargano]

@thomas-braun
Was ist denn ein brauchbarer Zigbee Stick ? (CC2652P, Sonoff...?)

[arteck]

@dexic poste mal den fehler ..nachdem du auf pairing gedrückt hast

[dexic]

@arteck

Das passiert mit dem CC2652P, den ich als Ersatz für den 2531 genommen habe. Den Sonoff habe ich noch nicht ausprobiert.

Error: Failed to open the network: Error: SREQ '--> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0}' failed with status '(0xc2: NWK_INVALID_REQUEST)' (expected '(0x00: SUCCESS)')
    at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:320:27
    at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
    at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:206:13
    at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
    at ZStackAdapter.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:203:9)
    at Controller.permitJoinInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:246:13)
    at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:234:9)
    at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:521:17). undefined
Pairing started

[arteck]

@dexic installier nochmal von GIT