Zigbee startet nicht mehr

toki1973

Ohne das ich etwas geändert habe habe ich Probleme mit dem ZIgbee Adapter

Node.js
v12.22.

Admin: 5.2.3


zigbee.0
2022-03-15 17:50:46.437	error	Error herdsman start

zigbee.0
2022-03-15 17:50:46.437	error	Failed to start Zigbee

zigbee.0
2022-03-15 17:50:46.424	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"

zigbee.0
2022-03-15 17:50:45.939	info	Installed Version: iobroker.zigbee@1.6.16

zigbee.0
2022-03-15 17:50:45.890	debug	Starting zigbee-herdsman...

zigbee.0
2022-03-15 17:50:45.890	info	Starting Zigbee npm ...

zigbee.0
2022-03-15 17:50:45.888	info	Try to reconnect. 1 attempts left

zigbee.0
2022-03-15 17:50:35.887	error	Error herdsman start

zigbee.0
2022-03-15 17:50:35.887	error	Failed to start Zigbee

zigbee.0
2022-03-15 17:50:35.886	error	Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"

Thomas Braun

@toki1973 sagte in Zigbee startet nicht mehr:

"Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"

Könnte mit der Firmware des Sticks zu tun haben.

toki1973

@thomas-braun Habe das TI Board
Ich habe eine Gruppe angelegt - sonst nichts verändert

arteck

@toki1973 zieh es mal vom USB ab und steck es wieder rein..

toki1973

@arteck said in Zigbee startet nicht mehr:

@toki1973 zieh es mal vom USB ab und steck es wieder rein..

Danke das war es. Nach dem ich Proxmox komplett durchgestartet habe hat es zum Glück wieder funktioniert :)

toki1973

@arteck said in Zigbee startet nicht mehr:

@toki1973 zieh es mal vom USB ab und steck es wieder rein..

Nun startet der Adapter zwar aber die Geräte verbinden sich nicht mehr. Der Backup Adapter will auch keine Backup zurück spielen


zigbee.0
2022-03-16 09:55:27.700	error	Failed to stop zigbee (Error: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/zigbee_0/shepherd.db.tmp' at Object.openSync (fs.js:462:3) at Object.writeFileSync (fs.js:1384:35) at Database.write (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/database.js:68:22) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:239:23) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:215:14) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:431:33) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:759:17))

zigbee.0
2022-03-16 09:48:20.805	error	Failed to stop zigbee (Error: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/zigbee_0/shepherd.db.tmp' at Object.openSync (fs.js:462:3) at Object.writeFileSync (fs.js:1384:35) at Database.write (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/database.js:68:22) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:239:23) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:215:14) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:431:33) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:759:17))

zigbee.0
2022-03-16 09:39:31.992	error	Device 0x00158d0004a06826 "undefined" not described in statesMapping.

arteck

@toki1973 kein plan was du da machst ..bzw. was du alles gefummelt hast als der coordinator nicht verbunden werden konnte.

ein abziehen und wieder einstecken bewirkt diesen fehler nicht..
wenn du an den Einstellungen was geändert hast .. das kan nich aber nicht wissen

toki1973

@arteck said in Zigbee startet nicht mehr:

@toki1973 kein plan was du da machst ..bzw. was du alles gefummelt hast als der coordinator nicht verbunden werden konnte.

ein abziehen und wieder einstecken bewirkt diesen fehler nicht..
wenn du an den Einstellungen was geändert hast .. das kan nich aber nicht wissen

Naja geändert habe ich nichts ausser ein Gruppe erstellt und 2 Devices gepairt. Vlt. hilft das weoter:


zigbee.0
2022-03-16 12:02:10.359	debug	saved device names

zigbee.0
2022-03-16 12:02:10.358	debug	saved device names

zigbee.0
2022-03-16 12:02:05.356	debug	getGroups result: {}

zigbee.0
2022-03-16 12:02:05.345	info	Zigbee started

zigbee.0
2022-03-16 12:02:05.344	info	Currently no devices.

zigbee.0
2022-03-16 12:02:05.327	info	--> transmitPower : high

zigbee.0
2022-03-16 12:02:05.326	info	Unable to disable LED, unsupported function.

zigbee.0
2022-03-16 12:02:05.325	debug	Zigbee network parameters: panID=6754 channel=15 extendedPanID=dddddddddddddddd

zigbee.0
2022-03-16 12:02:05.310	info	Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20191106}}

zigbee.0
2022-03-16 12:02:05.309	debug	zigbee-herdsman started

zigbee.0
2022-03-16 12:02:04.916	debug	Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2022_03_16-12_02_04.tar.gz success

zigbee.0
2022-03-16 12:02:04.910	info	Installed Version: iobroker.zigbee@1.6.16

zigbee.0
2022-03-16 12:02:04.320	debug	Starting zigbee-herdsman...

zigbee.0
2022-03-16 12:02:04.319	info	Starting Zigbee npm ...

zigbee.0
2022-03-16 12:02:04.276	debug	Using zigbee-herdsman with settings: {"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[15],"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":"/dev/ttyACM0","adapter":"zstack"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":true}}

zigbee.0
2022-03-16 12:02:04.236	info	starting. Version 1.6.16 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.7, js-controller: 3.3.22

zigbee.0
2022-03-16 12:02:04.178	info	Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system

zigbee.0
2022-03-16 12:02:04.173	debug	Plugin sentry Initialize Plugin (enabled=true)

zigbee.0
2022-03-16 12:01:29.927	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

zigbee.0
2022-03-16 12:01:29.927	debug	Plugin sentry destroyed

zigbee.0
2022-03-16 12:01:29.926	info	terminating

zigbee.0
2022-03-16 12:01:29.434	error	Cannot read property 'mapped' of undefined

zigbee.0
2022-03-16 12:01:29.434	error	TypeError: Cannot read property 'mapped' of undefined at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:499:36) at processTicksAndRejections (internal/process/task_queues.js:97:5) at runNextTicks (internal/process/task_queues.js:66:3) at processImmediate (internal/timers.js:434:9)

zigbee.0
2022-03-16 12:01:29.434	error	unhandled promise rejection: Cannot read property 'mapped' of undefined

zigbee.0
2022-03-16 12:01:29.434	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().

zigbee.0
2022-03-16 12:01:29.433	debug	entity: undefined

zigbee.0
2022-03-16 12:01:29.430	debug	Change state 'color' at device 0x7cb03eaa0a0085ea type '4052899926110'

zigbee.0
2022-03-16 12:01:29.426	info	Zigbee: disabling joining new devices.

zigbee.0
2022-03-16 12:01:29.425	info	cleaned everything up...

zigbee.0
2022-03-16 12:01:29.413	error	Cannot read property 'mapped' of undefined

zigbee.0
2022-03-16 12:01:29.413	error	TypeError: Cannot read property 'mapped' of undefined at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:499:36) at processTicksAndRejections (internal/process/task_queues.js:97:5) at runNextTicks (internal/process/task_queues.js:66:3) at processImmediate (internal/timers.js:434:9)

zigbee.0
2022-03-16 12:01:29.412	error	unhandled promise rejection: Cannot read property 'mapped' of undefined

zigbee.0
2022-03-16 12:01:29.412	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().

zigbee.0
2022-03-16 12:01:29.411	debug	entity: undefined

zigbee.0
2022-03-16 12:01:29.408	debug	Change state 'state' at device 0x7cb03eaa0a0085ea type '4052899926110'

zigbee.0
2022-03-16 12:01:29.396	debug	User stateChange zigbee.0.7cb03eaa0a0085ea.color {"val":"F00000","ack":false,"ts":1647428489388,"q":0,"c":"script.js.common.CO2","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1647259155612}

zigbee.0
2022-03-16 12:01:29.391	debug	User stateChange zigbee.0.7cb03eaa0a0085ea.state {"val":true,"ack":false,"ts":1647428489388,"q":0,"c":"script.js.common.CO2","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1647259155612}

zigbee.0
2022-03-16 12:00:27.733	debug	sendTo "getBinding" to system.adapter.admin.0 from system.adapter.zigbee.0

zigbee.0
2022-03-16 12:00:27.729	debug	getBinding result: []

zigbee.0
2022-03-16 12:00:27.726	debug	sendTo "getExclude" to system.adapter.admin.0 from system.adapter.zigbee.0

zigbee.0
2022-03-16 12:00:27.679	debug	getExclude result: []

zigbee.0
2022-03-16 12:00:27.251	debug	sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0

zigbee.0
2022-03-16 12:00:27.223	debug	getDevices result: [{"type":"device","common":{"name":"WSDCGQ11LM","type":"WSDCGQ11LM","icon":"img/aqara_temperature_sensor.png"},"native":{"id":"0000000000000000"},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1646389576567,"_id":"zigbee.0.0000000000000000","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"},"link_quality":0,"link_quality_lc":1646389636891,"battery":37,"statesDef":[{"id":"zigbee.0.0000000000000000.humidity","name":"Humidity","type

toki1973

@arteck würde es etwas helfen aus dem io-broker backup Verzeichnis aus dem .tar die Shepard db zurück zuholen? Die Schnittstelle funktioniert ja - ich konnte ein Device neue Pairen. Nur die alten bekommen keine Verbindung mehr.

arteck

@toki1973 spiel die shepherd und die nvbackup zurück..

sicher dir aber die jetzige nvbackup

Community Forum

NEWS

Zigbee startet nicht mehr

Support us

560

32.7k

82.6k

1.3m