[gelöst] Tasmota Sonoff Zigbee Pro Verbindung geht nicht

[A Former User]

ich kämpfe hier mit der Konfiguration des Zigbee-Pro in ioBroker

Gerät ist geflasht auf Tasmota 15.5.0.1
Konfiguration ist eingestellt auf Sonoff ZBPro TCP

als Adapter ist Zigbee installiert, es baut aber keine Verbindung auf:

zigbee.0 2023-05-05 15:48:03.188 error Error herdsman start
zigbee.0 2023-05-05 15:48:03.187 error Failed to start Zigbee
zigbee.0 2023-05-05 15:48:03.186 error Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
zigbee.0 2023-05-05 15:48:03.180 warn Failed to stop zigbee during startup

Im Adapter ist folgendes eingestellt:

kann jemand helfen?

[Glasfaser]

@papa_aus_rastatt sagte in Tasmota Sonoff Zigbee Pro Verbindung geht nicht:

kann jemand helfen?

Port

8888

richtig !?

[A Former User]

@glasfaser port 8888

19:22:35.558 TCP: Stopping TCP server
19:22:35.564 TCP: Starting TCP server on port 8888
19:22:35.575 MQT: stat/tasmota_615E34/RESULT = {"TCPStart":"Done"}
19:22:38.877 MQT: tele/tasmota_615E34/STATE = {"Time":"2023-05-05T19:22:38","Uptime":"0T00:04:20","UptimeSec":260,"Heap":161,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":49},"Wifi":{"AP":1,"SSId":"weinbrecht.machine","BSSId":"EA:63:DA:68:59:89","Channel":11,"Mode":"11n","RSSI":100,"Signal":-48,"LinkCount":1,"Downtime":"0T00:00:03"}}
19:22:48.886 MQT: tele/tasmota_615E34/STATE = {"Time":"2023-05-05T19:22:48","Uptime":"0T00:04:30","UptimeSec":270,"Heap":161,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":49},"Wifi":{"AP":1,"SSId":"weinbrecht.machine","BSSId":"EA:63:DA:68:59:89","Channel":11,"Mode":"11n","RSSI":100,"Signal":-49,"LinkCount":1,"Downtime":"0T00:00:03"}}
19:22:58.892 MQT: tele/tasmota_615E34/STATE = {"Time":"2023-05-05T19:22:58","Uptime":"0T00:04:40","UptimeSec":280,"Heap":161,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":49},"Wifi":{"AP":1,"SSId":"weinbrecht.machine","BSSId":"EA:63:DA:68:59:89","Channel":11,"Mode":"11n","RSSI":100,"Signal":-50,"LinkCount":1,"Downtime":"0T00:00:03"}}

[A Former User]

@glasfaser

im log auf dem zigbee Pro ist auch der Versuch der Verbindung protokoliert:

19:23:35.101 TCP: Got connection from 192.168.174.12

[Glasfaser]

@papa_aus_rastatt

Kannst du bitte die Ausgaben in Code-Tags </> setzen !

Kann nur entziffern das Mqtt abgefragt wird ,
dann eher mit dem Mqtt Adapter / bzw. Sonoff Adapter

Aber nicht mit dem Zigbee Adapter !

[A Former User]

@glasfaser sorry. dreams....

also iobroker Protokoll meldet:

20:38:09.896 MQT: tele/tasmota_615E34/STATE = {"Time":"2023-05-05T20:38:09","Uptime":"0T00:19:51","UptimeSec":1191,"Heap":158,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":5,"Objects":77},"Wifi":{"AP":1,"SSId":"weinbrecht.machine","BSSId":"EA:63:DA:68:59:89","Channel":11,"Mode":"11n","RSSI":100,"Signal":-49,"LinkCount":1,"Downtime":"0T00:00:03"}}
20:38:09.928 TCP: Got connection from 192.168.174.12
20:38:19.893 MQT: tele/tasmota_615E34/STATE = {"Time":"2023-05-05T20:38:19","Uptime":"0T00:20:01","UptimeSec":1201,"Heap":158,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":5,"Objects":77},"Wifi":{"AP":1,"SSId":"weinbrecht.machine","BSSId":"EA:63:DA:68:59:89","Channel":11,"Mode":"11n","RSSI":100,"Signal":-49,"LinkCount":1,"Downtime":"0T00:00:03"}}

im protokoll steht nichts verwendbares

host.app-server1.weinbrecht.lan
2023-05-05 20:39:52.306	info	instance system.adapter.zigbee.0 started with pid 43409
host.app-server1.weinbrecht.lan
2023-05-05 20:39:50.022	info	instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

zigbee.0
2023-05-05 20:39:49.436	warn	Failed to stop zigbee during startup
host.app-server1.weinbrecht.lan
2023-05-05 20:39:49.228	info	stopInstance system.adapter.zigbee.0 send kill signal```

[Glasfaser]

@papa_aus_rastatt sagte in Tasmota Sonoff Zigbee Pro Verbindung geht nicht:

also iobroker Protokoll meldet:
20:38:09.896 MQT: tele/tasmota_615E34/STATE

Das ist doch nicht ein ioBroker Log !?

Für mich ist das ein Mqtt Protokoll ...

@glasfaser sagte in Tasmota Sonoff Zigbee Pro Verbindung geht nicht:

dann eher mit dem Mqtt Adapter / bzw. Sonoff Adapter

[A Former User]

@glasfaser das soll das zigbee-Modul in ioBroker sein.

zigbee.0
2023-05-05 20:44:13.294	debug	Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2023_05_05-20_44_12.tar.gz success

zigbee.0
2023-05-05 20:44:13.267	info	Installed Version: iobroker.zigbee@1.8.10

zigbee.0
2023-05-05 20:44:12.670	debug	Starting zigbee-herdsman...

zigbee.0
2023-05-05 20:44:12.668	info	Starting Zigbee npm ...

zigbee.0
2023-05-05 20:44:12.665	info	delete old Backup files. keep only last 10

zigbee.0
2023-05-05 20:44:12.583	debug	Using zigbee-herdsman with settings: {"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"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.174.73:8888","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":true}}

zigbee.0
2023-05-05 20:44:12.529	info	starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.16.0, js-controller: 4.0.24

zigbee.0
2023-05-05 20:44:12.061	debug	Plugin sentry Initialize Plugin (enabled=true)
host.app-server1.weinbrecht.lan
2023-05-05 20:44:07.978	info	instance system.adapter.zigbee.0 started with pid 43490
host.app-server1.weinbrecht.lan
2023-05-05 20:44:05.754	info	instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

zigbee.0
2023-05-05 20:44:05.153	warn	Failed to stop zigbee during startup
host.app-server1.weinbrecht.lan
2023-05-05 20:44:04.881	info	stopInstance system.adapter.zigbee.0 send kill signal
host.app-server1.weinbrecht.lan
2023-05-05 20:44:04.810	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)

[A Former User]

@papa_aus_rastatt

[A Former User]

@papa_aus_rastatt ich glaube, ich habe es:

für den Zigbee Pro will er einen anderen Stack: