Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄

[Snert]

Hallo,

ich habe eine Sonoff zbbridge pro, welche in den ioBroker eingebunden werden soll.
Folgendes habe ich bisher gamacht:

• die Bridge nach dieser Anleitung mit Tasmota und der coordinator firmware geflashed. https://notenoughtech.com/home-automation/tasmota-on-sonoff-zb-bridge-pro/#flash

• Danach konnte ich über Tasmota die verschiedenen Geräte per Zigbee einbinden. Allerdings hat der ioBroker Adapter (ZigBee) keine Verbindung aufbauen können und ist immer wieder abgestüzt. (Vermutlich konnte die Verbindung wegen des falschen Templates nicht aufgebaut werden? GPIO 19 und 23 auf Zigbee Tx / Rx und nicht auf TCP Tx / Rx)

• Daraufhin habe ich nochmals Tasmota per web Installer installiert. Hinweis kam von hier: https://github.com/arendst/Tasmota/discussions/14419#discussioncomment-2929774

Unter "Configure Other" habe ich folgende Einstellungen vorgenommen:

{"NAME":"Sonoff Zigbee Pro","GPIO":[0,0,576,0,480,0,0,0,0,1,1,5792,0,0,0,5472,0,320,5793,5504,0,640,608,32,0,0,0,0,0,1,0,0,0,0,0,0],"FLAG":0,"BASE":1}

Des Weiteren habe ich als Rule1 folgendes eingetragen:

rule1 on system#boot do TCPStart 8888 endon

Nach einem Neustart kann ich folgendes in der Console lesen:

00:00:00.003 HDW: ESP32-D0WD-V3 v3.0 
00:00:00.100 UFS: FlashFS mounted with 908 kB free
00:00:00.121 CFG: Loaded from File, Count 50
00:00:00.131 QPC: Count 1
00:00:00.137 I2C: Bus1 using GPIO26(SCL) and GPIO25(SDA)
00:00:00.226 BRY: Berry initialized, RAM used=3902 bytes
00:00:00.240 TFS: File '.drvset003' not found
00:00:00.249 Project tasmota - Tasmota Version 13.2.0(zbbrdgpro)-2_0_14(2023-10-19T09:04:58)
00:00:00.937 WIF: Connecting to AP1 FRITZ!Box 7590 2.4 Channel 1 BSSId 2C:3A:FD:FB:F0:6E in mode 11n as tasmota-6063A4-0932...
00:00:02.633 WIF: Connected
00:00:02.889 HTP: Web server active on tasmota-6063A4-0932 with IP address 192.168.178.86
18:10:23.874 RSL: INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"13.2.0(zbbrdgpro)","FallbackTopic":"cmnd/DVES_6063A4_fb/","GroupTopic":"cmnd/tasmotas/"}}
18:10:23.890 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6063A4-0932","IPAddress":"192.168.178.86","IP6Global":"","IP6Local":"fe80::4222:d8ff:fe60:63a4"}}
18:10:23.904 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":25}}
18:10:23.926 RUL: SYSTEM#BOOT performs "TCPStart 8888"
18:10:23.929 TCP: Starting TCP server on port 8888
18:10:23.932 RSL: RESULT = {"TCPStart":"Done"}
18:10:26.868 QPC: Reset
18:10:27.865 RSL: STATE = {"Time":"2023-10-26T18:10:27","Uptime":"0T00:00:08","UptimeSec":8,"Heap":165,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-30,"LinkCount":1,"Downtime":"0T00:00:03"}}

Nun zum ZigBee Adapter, welchen ich wie folgt konfiguriert habe:

Nach ein paar Minuten stürzt der Adapter komplett ab und muss unter Host quitiert werden.
Parallel erhalte ich in der Concole in Tasmota diese eine Zeile (die IP.36 ist der ioBroker):

18:13:17.360 TCP: Got connection from 192.168.178.36

In den Logs vom ioBroker kommen folgende Einträge zum ZigBee Adapter:

	2023-10-26 19:14:56.266	error	Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:14:56.266	error	Error: Reset error: Error: {"sequence":-1} after 10000ms at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23 at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
	2023-10-26 19:14:56.214	error	unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:14:56.214	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
	2023-10-26 19:14:12.075	error	Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:14:12.075	error	Error: Reset error: Error: {"sequence":-1} after 10000ms at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23 at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
	2023-10-26 19:14:12.010	error	unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:14:12.009	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
	2023-10-26 19:13:28.444	error	Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:13:28.443	error	Error: Reset error: Error: {"sequence":-1} after 10000ms at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23 at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
	2023-10-26 19:13:28.377	error	unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:13:28.376	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
	2023-10-26 19:09:47.246	error	Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:09:47.246	error	Error: Reset error: Error: {"sequence":-1} after 10000ms at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23 at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
	2023-10-26 19:09:47.195	error	unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:09:47.194	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
	2023-10-26 19:09:02.719	error	Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:09:02.718	error	Error: Reset error: Error: {"sequence":-1} after 10000ms at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23 at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
	2023-10-26 19:09:02.644	error	unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
	2023-10-26 19:09:02.643	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
	2023-10-26 19:09:00.682	error	getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')

Und genau da stehe ich jetzt etwas wie der Ochs vorm Berg und komme nicht mehr weiter.
Wäre super wenn jemand eine Idee oder noch besser die Lösung hätte :grin:

Vielen Dank

[arteck]

@snert sagte in Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter:

Wäre super wenn jemand eine Idee oder noch besser die Lösung hätte

währe super wenn du nicht so ein LOG schnipsel posten würdest ..sondern alles nach adapter start

[Snert]

@arteck Alles klar, da hast du vermutlich Recht.
Hier der eben durchgeführte Start bis Ende und Abbruch.

2023-10-26 19:58:29.888 - info: host.smarthome-VM "system.adapter.zigbee.0" enabled
2023-10-26 19:58:30.063 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 873684
2023-10-26 19:58:31.504 - debug: zigbee.0 (873684) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-10-26 19:58:31.572 - debug: zigbee.0 (873684) Objects client ready ... initialize now
2023-10-26 19:58:31.579 - debug: zigbee.0 (873684) Objects create System PubSub Client
2023-10-26 19:58:31.585 - debug: zigbee.0 (873684) Objects create User PubSub Client
2023-10-26 19:58:31.632 - debug: zigbee.0 (873684) Objects client initialize lua scripts
2023-10-26 19:58:31.637 - debug: zigbee.0 (873684) Objects connected to redis: 127.0.0.1:9001
2023-10-26 19:58:31.652 - debug: zigbee.0 (873684) Redis States: Use Redis connection: 127.0.0.1:9000
2023-10-26 19:58:31.702 - debug: zigbee.0 (873684) States create System PubSub Client
2023-10-26 19:58:31.704 - debug: zigbee.0 (873684) States create User PubSub Client
2023-10-26 19:58:31.773 - debug: zigbee.0 (873684) States connected to redis: 127.0.0.1:9000
2023-10-26 19:58:31.926 - debug: zigbee.0 (873684) Plugin sentry Initialize Plugin (enabled=true)
2023-10-26 19:58:32.343 - info: zigbee.0 (873684) starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-10-26 19:58:32.401 - debug: zigbee.0 (873684) Using zigbee-herdsman with settings: {"network":{"panID":6754,"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"extenedPanID":[141,220,221,218,253,61,210,189]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"tcp://192.168.178.86:8888","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}}
2023-10-26 19:58:32.469 - info: zigbee.0 (873684) delete old Backup files. keep only last 10
2023-10-26 19:58:32.470 - info: zigbee.0 (873684) Starting Zigbee npm ...
2023-10-26 19:58:32.470 - debug: zigbee.0 (873684) Starting zigbee-herdsman...
2023-10-26 19:58:32.855 - debug: zigbee.0 (873684) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2023_10_26-19_58_32.tar.gz success
2023-10-26 19:58:32.864 - info: zigbee.0 (873684) Installed Version: iobroker.zigbee@1.8.23
2023-10-26 19:58:42.864 - error: zigbee.0 (873684) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-26 19:58:42.865 - error: zigbee.0 (873684) unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 19:58:42.969 - error: zigbee.0 (873684) Error: Reset error: Error: {"sequence":-1} after 10000ms
at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 19:58:42.970 - error: zigbee.0 (873684) Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 19:58:43.068 - info: zigbee.0 (873684) cleaned everything up...
2023-10-26 19:58:43.071 - info: zigbee.0 (873684) Zigbee: disabling joining new devices.
2023-10-26 19:58:43.189 - warn: zigbee.0 (873684) Failed to stop zigbee during startup
2023-10-26 19:58:43.190 - info: zigbee.0 (873684) terminating
2023-10-26 19:58:43.190 - debug: zigbee.0 (873684) Plugin sentry destroyed
2023-10-26 19:58:43.191 - warn: zigbee.0 (873684) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-26 19:58:43.741 - error: host.smarthome-VM Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-26 19:58:43.741 - error: host.smarthome-VM Caught by controller[1]: Error: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 19:58:43.741 - error: host.smarthome-VM Caught by controller[1]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
2023-10-26 19:58:43.741 - error: host.smarthome-VM Caught by controller[1]: at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 19:58:43.741 - error: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-26 19:58:43.741 - info: host.smarthome-VM Restart adapter system.adapter.zigbee.0 because enabled
2023-10-26 19:59:13.810 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 873701
2023-10-26 19:59:16.266 - debug: zigbee.0 (873701) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-10-26 19:59:16.300 - debug: zigbee.0 (873701) Objects client ready ... initialize now
2023-10-26 19:59:16.344 - debug: zigbee.0 (873701) Objects create System PubSub Client
2023-10-26 19:59:16.347 - debug: zigbee.0 (873701) Objects create User PubSub Client
2023-10-26 19:59:16.441 - debug: zigbee.0 (873701) Objects client initialize lua scripts
2023-10-26 19:59:16.450 - debug: zigbee.0 (873701) Objects connected to redis: 127.0.0.1:9001
2023-10-26 19:59:16.491 - debug: zigbee.0 (873701) Redis States: Use Redis connection: 127.0.0.1:9000
2023-10-26 19:59:16.558 - debug: zigbee.0 (873701) States create System PubSub Client
2023-10-26 19:59:16.560 - debug: zigbee.0 (873701) States create User PubSub Client
2023-10-26 19:59:16.637 - debug: zigbee.0 (873701) States connected to redis: 127.0.0.1:9000
2023-10-26 19:59:16.804 - debug: zigbee.0 (873701) Plugin sentry Initialize Plugin (enabled=true)
2023-10-26 19:59:17.561 - info: zigbee.0 (873701) starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-10-26 19:59:17.648 - debug: zigbee.0 (873701) Using zigbee-herdsman with settings: {"network":{"panID":6754,"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"extenedPanID":[141,220,221,218,253,61,210,189]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"tcp://192.168.178.86:8888","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}}
2023-10-26 19:59:17.685 - info: zigbee.0 (873701) delete old Backup files. keep only last 10
2023-10-26 19:59:17.687 - info: zigbee.0 (873701) Starting Zigbee npm ...
2023-10-26 19:59:17.687 - debug: zigbee.0 (873701) Starting zigbee-herdsman...
2023-10-26 19:59:18.003 - debug: zigbee.0 (873701) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2023_10_26-19_59_17.tar.gz success
2023-10-26 19:59:18.074 - info: zigbee.0 (873701) Installed Version: iobroker.zigbee@1.8.23
2023-10-26 19:59:28.055 - error: zigbee.0 (873701) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-26 19:59:28.057 - error: zigbee.0 (873701) unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 19:59:28.124 - error: zigbee.0 (873701) Error: Reset error: Error: {"sequence":-1} after 10000ms
at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 19:59:28.127 - error: zigbee.0 (873701) Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 19:59:28.170 - info: zigbee.0 (873701) cleaned everything up...
2023-10-26 19:59:28.175 - info: zigbee.0 (873701) Zigbee: disabling joining new devices.
2023-10-26 19:59:28.336 - warn: zigbee.0 (873701) Failed to stop zigbee during startup
2023-10-26 19:59:28.337 - info: zigbee.0 (873701) terminating
2023-10-26 19:59:28.338 - debug: zigbee.0 (873701) Plugin sentry destroyed
2023-10-26 19:59:28.338 - warn: zigbee.0 (873701) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-26 19:59:28.945 - error: host.smarthome-VM Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-26 19:59:28.945 - error: host.smarthome-VM Caught by controller[1]: Error: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 19:59:28.945 - error: host.smarthome-VM Caught by controller[1]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
2023-10-26 19:59:28.945 - error: host.smarthome-VM Caught by controller[1]: at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 19:59:28.946 - error: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-26 19:59:28.946 - info: host.smarthome-VM Restart adapter system.adapter.zigbee.0 because enabled
2023-10-26 19:59:59.020 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 873716
2023-10-26 20:00:00.068 - info: host.smarthome-VM instance system.adapter.netatmo-crawler.0 started with pid 873723
2023-10-26 20:00:02.562 - info: netatmo-crawler.0 (873723) starting. Version 0.8.1 in /opt/iobroker/node_modules/iobroker.netatmo-crawler, node: v16.19.0, js-controller: 4.0.24
2023-10-26 20:00:02.662 - info: netatmo-crawler.0 (873723) Getting data for stationid:70:ee:50:12:fb:5c
2023-10-26 20:00:02.801 - debug: zigbee.0 (873716) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-10-26 20:00:02.825 - debug: zigbee.0 (873716) Objects client ready ... initialize now
2023-10-26 20:00:02.826 - debug: zigbee.0 (873716) Objects create System PubSub Client
2023-10-26 20:00:02.827 - debug: zigbee.0 (873716) Objects create User PubSub Client
2023-10-26 20:00:02.873 - debug: zigbee.0 (873716) Objects client initialize lua scripts
2023-10-26 20:00:02.882 - debug: zigbee.0 (873716) Objects connected to redis: 127.0.0.1:9001
2023-10-26 20:00:02.904 - debug: zigbee.0 (873716) Redis States: Use Redis connection: 127.0.0.1:9000
2023-10-26 20:00:02.962 - debug: zigbee.0 (873716) States create System PubSub Client
2023-10-26 20:00:02.963 - debug: zigbee.0 (873716) States create User PubSub Client
2023-10-26 20:00:02.992 - info: netatmo-crawler.0 (873723) Getting data for stationid:70:ee:50:17:78:3c
2023-10-26 20:00:03.028 - debug: zigbee.0 (873716) States connected to redis: 127.0.0.1:9000
2023-10-26 20:00:03.165 - debug: zigbee.0 (873716) Plugin sentry Initialize Plugin (enabled=true)
2023-10-26 20:00:03.642 - info: zigbee.0 (873716) starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-10-26 20:00:03.677 - debug: zigbee.0 (873716) Using zigbee-herdsman with settings: {"network":{"panID":6754,"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"extenedPanID":[141,220,221,218,253,61,210,189]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"tcp://192.168.178.86:8888","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}}
2023-10-26 20:00:03.710 - info: zigbee.0 (873716) delete old Backup files. keep only last 10
2023-10-26 20:00:03.711 - info: zigbee.0 (873716) Starting Zigbee npm ...
2023-10-26 20:00:03.711 - debug: zigbee.0 (873716) Starting zigbee-herdsman...
2023-10-26 20:00:04.082 - debug: zigbee.0 (873716) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2023_10_26-20_00_03.tar.gz success
2023-10-26 20:00:04.090 - info: zigbee.0 (873716) Installed Version: iobroker.zigbee@1.8.23
2023-10-26 20:00:04.110 - info: host.smarthome-VM instance system.adapter.solarmanpv.0 started with pid 873746
2023-10-26 20:00:04.634 - info: netatmo-crawler.0 (873723) Getting data for stationid:70:ee:50:7a:e3:82
2023-10-26 20:00:06.001 - info: netatmo-crawler.0 (873723) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule
2023-10-26 20:00:06.026 - info: solarmanpv.0 (873746) starting. Version 0.5.0 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v16.19.0, js-controller: 4.0.24
2023-10-26 20:00:06.541 - info: host.smarthome-VM instance system.adapter.netatmo-crawler.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-10-26 20:00:14.087 - error: zigbee.0 (873716) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-26 20:00:14.088 - error: zigbee.0 (873716) unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 20:00:14.144 - error: zigbee.0 (873716) Error: Reset error: Error: {"sequence":-1} after 10000ms
at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 20:00:14.145 - error: zigbee.0 (873716) Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 20:00:14.213 - info: zigbee.0 (873716) cleaned everything up...
2023-10-26 20:00:14.217 - info: zigbee.0 (873716) Zigbee: disabling joining new devices.
2023-10-26 20:00:14.442 - warn: zigbee.0 (873716) Failed to stop zigbee during startup
2023-10-26 20:00:14.442 - info: zigbee.0 (873716) terminating
2023-10-26 20:00:14.443 - debug: zigbee.0 (873716) Plugin sentry destroyed
2023-10-26 20:00:14.443 - warn: zigbee.0 (873716) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-26 20:00:15.051 - error: host.smarthome-VM Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-26 20:00:15.052 - error: host.smarthome-VM Caught by controller[1]: Error: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 20:00:15.052 - error: host.smarthome-VM Caught by controller[1]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
2023-10-26 20:00:15.052 - error: host.smarthome-VM Caught by controller[1]: at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 20:00:15.053 - error: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-26 20:00:15.053 - info: host.smarthome-VM Restart adapter system.adapter.zigbee.0 because enabled
2023-10-26 20:00:15.053 - warn: host.smarthome-VM Do not restart adapter system.adapter.zigbee.0 because restart loop detected

[arteck]

@snert sagte in Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter:

at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23

da ist ein Fehler im converter... installier mal den adapter von GIT
und mach Debug AUS.. brauch ich nicht

[Ralla66]

@snert

diese Seite wäre aus meiner Sicht richtig :
demnach fehlt:
rule1 1 TCPStart 8888
also die Ausführung der Rule beim booten aktivieren

sollte dann für Pro ESP32 sein:
Download
Ota:

	http://ota.tasmota.com/tasmota32/release/tasmota32-zbbrdgpro.bin

Pro als Bridge betreiben, Template

{"NAME":"TCP ZBBridge Pro","GPIO":[0,0,576,0,480,0,0,0,0,1,1,5792,0,0,0,5472,0,320,5793,5504,0,640,608,32,0,0,0,0,0,1,0,0,0,0,0,0],"FLAG":0,"BASE":1

Zigbee Commands

TCP Commands

[Snert]

@arteck Habe die Version 1.8.24 über GIT geladen. Ergebnis ist erstmal das selbe, aber vll. hilft es trozdem weiter.

2023-10-26 22:17:19.749 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 874855
2023-10-26 22:17:20.240 - info: admin.0 (649296) ==> Connected system.user.admin from ::ffff:192.168.178.89
2023-10-26 22:17:22.388 - info: zigbee.0 (874855) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-10-26 22:17:22.477 - error: zigbee.0 (874855) Serial port not selected! Go to settings page.
2023-10-26 22:17:22.595 - info: zigbee.0 (874855) delete old Backup files. keep only last 10
2023-10-26 22:17:22.596 - info: zigbee.0 (874855) Starting Zigbee npm ...
2023-10-26 22:17:23.319 - error: zigbee.0 (874855) Starting zigbee-herdsman problem : "No path provided and failed to auto detect path"
2023-10-26 22:17:23.320 - error: zigbee.0 (874855) Failed to start Zigbee
2023-10-26 22:17:23.320 - error: zigbee.0 (874855) Error herdsman start
2023-10-26 22:17:23.344 - info: zigbee.0 (874855) Installed Version: ioBroker/ioBroker.zigbee
2023-10-26 22:17:33.322 - info: zigbee.0 (874855) Try to reconnect. 1 attempts left
2023-10-26 22:17:33.324 - info: zigbee.0 (874855) Starting Zigbee npm ...
2023-10-26 22:17:33.368 - info: zigbee.0 (874855) Installed Version: ioBroker/ioBroker.zigbee
2023-10-26 22:17:33.733 - error: zigbee.0 (874855) Starting zigbee-herdsman problem : "No path provided and failed to auto detect path"
2023-10-26 22:17:33.734 - error: zigbee.0 (874855) Failed to start Zigbee
2023-10-26 22:17:33.735 - error: zigbee.0 (874855) Error herdsman start
2023-10-26 22:18:19.826 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 (force=false, process=true)
2023-10-26 22:18:19.893 - info: zigbee.0 (874855) Got terminate signal TERMINATE_YOURSELF
2023-10-26 22:18:19.904 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 send kill signal
2023-10-26 22:18:19.894 - info: zigbee.0 (874855) cleaned everything up...
2023-10-26 22:18:19.897 - info: zigbee.0 (874855) Zigbee: disabling joining new devices.
2023-10-26 22:18:19.925 - warn: zigbee.0 (874855) Failed to stop zigbee during startup
2023-10-26 22:18:19.932 - info: zigbee.0 (874855) terminating
2023-10-26 22:18:19.933 - info: zigbee.0 (874855) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-10-26 22:18:20.094 - info: admin.0 (649296) <== Disconnect system.user.admin from ::ffff:192.168.178.89
2023-10-26 22:18:20.540 - info: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-10-26 22:18:22.995 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 874887
2023-10-26 22:18:26.421 - info: zigbee.0 (874887) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-10-26 22:18:26.504 - info: zigbee.0 (874887) delete old Backup files. keep only last 10
2023-10-26 22:18:26.506 - info: zigbee.0 (874887) Starting Zigbee npm ...
2023-10-26 22:18:26.914 - info: zigbee.0 (874887) Installed Version: ioBroker/ioBroker.zigbee
2023-10-26 22:18:36.915 - error: zigbee.0 (874887) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-26 22:18:36.916 - error: zigbee.0 (874887) unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 22:18:37.058 - error: zigbee.0 (874887) Error: Reset error: Error: {"sequence":-1} after 10000ms
at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 22:18:37.059 - error: zigbee.0 (874887) Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 22:18:37.164 - info: zigbee.0 (874887) cleaned everything up...
2023-10-26 22:18:37.172 - info: zigbee.0 (874887) Zigbee: disabling joining new devices.
2023-10-26 22:18:37.443 - warn: zigbee.0 (874887) Failed to stop zigbee during startup
2023-10-26 22:18:37.444 - info: zigbee.0 (874887) terminating
2023-10-26 22:18:37.445 - warn: zigbee.0 (874887) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-26 22:18:38.095 - error: host.smarthome-VM Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-26 22:18:38.095 - error: host.smarthome-VM Caught by controller[0]: Error: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 22:18:38.096 - error: host.smarthome-VM Caught by controller[0]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
2023-10-26 22:18:38.096 - error: host.smarthome-VM Caught by controller[0]: at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 22:18:38.096 - error: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-26 22:18:38.096 - info: host.smarthome-VM Restart adapter system.adapter.zigbee.0 because enabled
2023-10-26 22:19:08.160 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 874904
2023-10-26 22:19:11.250 - info: zigbee.0 (874904) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-10-26 22:19:11.312 - info: zigbee.0 (874904) delete old Backup files. keep only last 10
2023-10-26 22:19:11.313 - info: zigbee.0 (874904) Starting Zigbee npm ...
2023-10-26 22:19:11.675 - info: zigbee.0 (874904) Installed Version: ioBroker/ioBroker.zigbee
2023-10-26 22:19:21.672 - error: zigbee.0 (874904) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-26 22:19:21.674 - error: zigbee.0 (874904) unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 22:19:21.746 - error: zigbee.0 (874904) Error: Reset error: Error: {"sequence":-1} after 10000ms
at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 22:19:21.747 - error: zigbee.0 (874904) Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 22:19:21.772 - info: zigbee.0 (874904) cleaned everything up...
2023-10-26 22:19:21.775 - info: zigbee.0 (874904) Zigbee: disabling joining new devices.
2023-10-26 22:19:21.980 - warn: zigbee.0 (874904) Failed to stop zigbee during startup
2023-10-26 22:19:21.981 - info: zigbee.0 (874904) terminating
2023-10-26 22:19:21.982 - warn: zigbee.0 (874904) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-26 22:19:22.603 - error: host.smarthome-VM Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-26 22:19:22.603 - error: host.smarthome-VM Caught by controller[1]: Error: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 22:19:22.603 - error: host.smarthome-VM Caught by controller[1]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
2023-10-26 22:19:22.603 - error: host.smarthome-VM Caught by controller[1]: at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 22:19:22.604 - error: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-26 22:19:22.604 - info: host.smarthome-VM Restart adapter system.adapter.zigbee.0 because enabled
2023-10-26 22:19:52.688 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 874919
2023-10-26 22:19:55.225 - info: zigbee.0 (874919) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-10-26 22:19:55.282 - info: zigbee.0 (874919) delete old Backup files. keep only last 10
2023-10-26 22:19:55.283 - info: zigbee.0 (874919) Starting Zigbee npm ...
2023-10-26 22:19:55.596 - info: zigbee.0 (874919) Installed Version: ioBroker/ioBroker.zigbee
2023-10-26 22:20:00.074 - info: host.smarthome-VM instance system.adapter.netatmo-crawler.0 started with pid 874934
2023-10-26 22:20:05.596 - error: zigbee.0 (874919) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-26 22:20:05.655 - info: host.smarthome-VM instance system.adapter.netatmo-crawler.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-10-26 22:20:05.598 - error: zigbee.0 (874919) unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 22:20:05.736 - error: zigbee.0 (874919) Error: Reset error: Error: {"sequence":-1} after 10000ms
at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 22:20:05.736 - error: zigbee.0 (874919) Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 22:20:05.795 - info: zigbee.0 (874919) cleaned everything up...
2023-10-26 22:20:05.809 - info: zigbee.0 (874919) Zigbee: disabling joining new devices.
2023-10-26 22:20:05.939 - warn: zigbee.0 (874919) Failed to stop zigbee during startup
2023-10-26 22:20:05.940 - info: zigbee.0 (874919) terminating
2023-10-26 22:20:05.941 - warn: zigbee.0 (874919) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-26 22:20:06.603 - error: host.smarthome-VM Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-26 22:20:06.604 - error: host.smarthome-VM Caught by controller[0]: Error: Reset error: Error: {"sequence":-1} after 10000ms
2023-10-26 22:20:06.604 - error: host.smarthome-VM Caught by controller[0]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
2023-10-26 22:20:06.604 - error: host.smarthome-VM Caught by controller[0]: at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
2023-10-26 22:20:06.604 - error: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-26 22:20:06.605 - info: host.smarthome-VM Restart adapter system.adapter.zigbee.0 because enabled
2023-10-26 22:20:06.605 - warn: host.smarthome-VM Do not restart adapter system.adapter.zigbee.0 because restart loop detected

@Ralla66 auch mit angepastem Template und der Rule, selbes Ergebnis. Morgen kann ich gerne nochmal mich an die andere Anleitung halten.

[Ralla66]

@snert

auf welcher Maschine betreibst du den ZigBee-Adapter ?

[Snert]

@ralla66 In einer Windows Server HyperV VM mit Ubuntu. Die VM hat 16GB Ram und die Host CPU ist ein Intel Core i5-4590 CPU @ 3.30GHz.

[arteck]

@snert alder was ein konstrukt

suchmal nach udev... und check das erstmal..scheint als ob der ezsp Treiber nicht geladen wird

[Snert]

@arteck Da noch einiges mehr auf dem Server an VMs läuft, hatte ich mich dafür entschieden den ioBroker hier zu installieren.

Bezüglich udev, ist das nicht nur erforderlich wenn ich einen USB Stick verwenden würde?

@Ralla66 ich habe jetzt auch per OTA geupdated, ohne weitere Verbesserungen.

[arteck]

@snert sagte in Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter:

Bezüglich udev, ist das nicht nur erforderlich wenn ich einen USB Stick verwenden würde?

ja hast ja recht.. du machst es per ip..

hmm..kein Plan.. irgendwas ist nicht so konfiguriert wie es soll.. auf der bridge

[Ralla66]

@snert

du hast diese rule in der Tasmota Console ausgeführt und neu gebootet ?

backlog rule1 on system#boot do TCPStart 8888 endon ; rule1 1 ; TCPStart 8888

In der Console kann mit

TCPBaudRate

die eingestellte Baudrate geprüft werden. Passt diese ?

Zeige mal den Consolentext, dort steht ja ob die Bridge verbunden ist.

[Snert]

@ralla66 Ja, alles so durchgeführt.
Baudrate sollte so auch passen.

RESULT = {"TCPBaudrate":115200}

Könnt ihr mir sagen was in der Tasmota Console bei korrekter Verbindung angezeigt wird?

Wenn das Kind heute Abend im Bett ist, werde ich alles nochmal in Ruhe neu anfangen. Gibts ne Möglichkeit alles auf 0 zu setzen (auch den CC2652) oder geschieht das automatisch mit dem neuen flashen von Tasmota?

Edit:

00:00:00.002 HDW: ESP32-D0WD-V3 v3.0 
00:00:00.067 UFS: FlashFS mounted with 908 kB free
00:00:00.081 CFG: Loaded from File, Count 59
00:00:00.091 QPC: Count 1
00:00:00.097 I2C: Bus1 using GPIO26(SCL) and GPIO25(SDA)
00:00:00.162 BRY: Berry initialized, RAM used=3902 bytes
00:00:00.174 TFS: File '.drvset003' not found
00:00:00.183 Project tasmota - Tasmota Version 13.2.0(zbbrdgpro)-2_0_14(2023-10-19T09:04:58)
00:00:00.667 WIF: Connecting to AP1 FRITZ!Box 7590 2.4 Channel 1 BSSId 2C:3A:FD:FB:F0:6E in mode 11n as tasmota-6063A4-0932...
00:00:02.398 WIF: Connected
00:00:02.656 HTP: Web server active on tasmota-6063A4-0932 with IP address 192.168.178.86
10:03:13.662 RSL: INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"13.2.0(zbbrdgpro)","FallbackTopic":"cmnd/DVES_6063A4_fb/","GroupTopic":"cmnd/tasmotas/"}}
10:03:13.677 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6063A4-0932","IPAddress":"192.168.178.86","IP6Global":"","IP6Local":"fe80::4222:d8ff:fe60:63a4"}}
10:03:13.691 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":31}}
10:03:13.716 RUL: SYSTEM#BOOT performs "TCPStart 8888"
10:03:13.718 TCP: Starting TCP server on port 8888
10:03:13.722 RSL: RESULT = {"TCPStart":"Done"}
10:03:16.964 QPC: Reset
10:03:17.891 RSL: STATE = {"Time":"2023-10-27T10:03:17","Uptime":"0T00:00:08","UptimeSec":8,"Heap":164,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}00:00:02.398 WIF: Connected
00:00:02.656 HTP: Web server active on tasmota-6063A4-0932 with IP address 192.168.178.86
10:03:13.662 RSL: INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"13.2.0(zbbrdgpro)","FallbackTopic":"cmnd/DVES_6063A4_fb/","GroupTopic":"cmnd/tasmotas/"}}
10:03:13.677 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6063A4-0932","IPAddress":"192.168.178.86","IP6Global":"","IP6Local":"fe80::4222:d8ff:fe60:63a4"}}
10:03:13.691 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":31}}
10:03:13.716 RUL: SYSTEM#BOOT performs "TCPStart 8888"
10:03:13.718 TCP: Starting TCP server on port 8888
10:03:13.722 RSL: RESULT = {"TCPStart":"Done"}
10:03:16.964 QPC: Reset
10:03:17.891 RSL: STATE = {"Time":"2023-10-27T10:03:17","Uptime":"0T00:00:08","UptimeSec":8,"Heap":164,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:03:28.123 TCP: Got connection from 192.168.178.36
10:04:12.032 TCP: Got connection from 192.168.178.36
10:08:17.901 RSL: STATE = {"Time":"2023-10-27T10:08:17","Uptime":"0T00:05:08","UptimeSec":308,"Heap":160,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-38,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:13:08.930 APP: Serial logging disabled
10:13:17.936 RSL: STATE = {"Time":"2023-10-27T10:13:17","Uptime":"0T00:10:08","UptimeSec":608,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:18:17.912 RSL: STATE = {"Time":"2023-10-27T10:18:17","Uptime":"0T00:15:08","UptimeSec":908,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-35,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:23:17.896 RSL: STATE = {"Time":"2023-10-27T10:23:17","Uptime":"0T00:20:08","UptimeSec":1208,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:28:17.912 RSL: STATE = {"Time":"2023-10-27T10:28:17","Uptime":"0T00:25:08","UptimeSec":1508,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:33:17.889 RSL: STATE = {"Time":"2023-10-27T10:33:17","Uptime":"0T00:30:08","UptimeSec":1808,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:38:17.927 RSL: STATE = {"Time":"2023-10-27T10:38:17","Uptime":"0T00:35:08","UptimeSec":2108,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-34,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:43:17.922 RSL: STATE = {"Time":"2023-10-27T10:43:17","Uptime":"0T00:40:08","UptimeSec":2408,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:48:17.893 RSL: STATE = {"Time":"2023-10-27T10:48:17","Uptime":"0T00:45:08","UptimeSec":2708,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:53:17.889 RSL: STATE = {"Time":"2023-10-27T10:53:17","Uptime":"0T00:50:08","UptimeSec":3008,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}
10:58:17.916 RSL: STATE = {"Time":"2023-10-27T10:58:17","Uptime":"0T00:55:08","UptimeSec":3308,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}
11:03:17.910 RSL: STATE = {"Time":"2023-10-27T11:03:17","Uptime":"0T01:00:08","UptimeSec":3608,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-35,"LinkCount":1,"Downtime":"0T00:00:03"}}
11:08:17.903 RSL: STATE = {"Time":"2023-10-27T11:08:17","Uptime":"0T01:05:08","UptimeSec":3908,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
11:11:45.034 CMD: TCPBaudRate
11:11:45.039 RSL: RESULT = {"TCPBaudrate":115200}
11:13:17.921 RSL: STATE = {"Time":"2023-10-27T11:13:17","Uptime":"0T01:10:08","UptimeSec":4208,"Heap":160,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-35,"LinkCount":1,"Downtime":"0T00:00:03"}}
11:18:17.925 RSL: STATE = {"Time":"2023-10-27T11:18:17","Uptime":"0T01:15:08","UptimeSec":4508,"Heap":160,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
11:21:46.024 CMD: TCPBaudRate
11:21:46.029 RSL: RESULT = {"TCPBaudrate":115200}

[Ralla66]

@snert

10:03:13.716 RUL: SYSTEM#BOOT performs "TCPStart 8888"
10:03:13.718 TCP: Starting TCP server on port 8888
10:03:13.722 RSL: RESULT = {"TCPStart":"Done"}

TCPStart":"Done zeigt an das der TCP Server aktiv ist.

Wenn eine Verbindung besteht wird die IP des Client in der Console angezeigt.
Sollte dies sein :

10:03:28.123 TCP: Got connection from 192.168.178.36

soweit in Ordnung

was hängt denn an GPIO 26 und 25 ?

default ESP32 ist ja
GPIO 21 (SDA)
GPIO 22 (SCL)

[Snert]

@ralla66

Die eine LED blinkt blau bei WLAN und die andere blinkt grün bei Zigbee Verbindung.

[Snert]

@ralla66 Ich habe jetzt alles nochmal von Grund auf neu gemacht.
Alles beim alten :-(

Was mir aufgefallen ist, ich erhalte beim flashen vom cc2652 NICHT diese Meldung:

22:01:25.294 RSL: RESULT = {"ZbState":{"Status":3,"Message":"Configured, starting coordinator"}}
22:01:31.293 RSL: RESULT = {"ZbState":{"Status":40,"NewState":9,"Message":"Started as coordinator"}}
22:01:31.944 RSL: RESULT = {"ZbState":{"Status":0,"Message":"Started"}}

Wie in der Anleitung von notenoughtech beschrieben.
Kann ich irgendwie prüfen welche Version auf dem Chip ist, oder was sein Status ist?
Das flashen ansonsten wurde jeweils mit ok quitiert.

[Ralla66]

@snert

habe das System nicht mit dem CC2652, kann nur noch theoretisch helfen.

hast du nach dem Ausführen dies in der Console gesehen ?

FLH: Starting verification of HEX file und
FLH: Flashing completed: OK

[Snert]

@ralla66 Ja, beide Meldungen sind gekommen.
Ich habe auch schon vor lauter Verzweiflung mit den "Typen" im ioBroker Adapter gespielt.
Ebenso auch per Webinstaller den Develop Status verwendet und auch das aktuellste hex file "SonoffZBPro_coord_20230507.hex" genutzt.
Alles lief immer ohne Probleme durch. Einzig die oben erwähnte Meldung erhalte ich nicht.
Jetzt kann ich noch mit den Templates spielen, aber ob das was ändert?

[Ralla66]

@snert

die 3 Status Meldungen scheinen nur nach dem Neustart einmalig in der Console zu erscheinen.
Boote mal neu und schau was im Log steht.

[Ralla66]

@ralla66

Moin, habe das mal auf einen ESP geflasht.

Was geschieht denn wenn du bei Berry -> cc.flash() ausführst ?
Console zeigt was ?