NEWS
Erledigt: Zigbee mit TCP
-
@thomas-braun sagte in Zigbee mit TCP:
00124b0025792115
Weil er die ID in der Konfiguration ROT Unterstrichen hat.
Anbei das LOG
Bitte in CodeTags eingebettet hier in den Thread.
-
Bitte in CodeTags eingebettet hier in den Thread.
2023-07-26 21:21:45.054 - info: zigbee.1 (5664) starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 2023-07-26 21:21:45.193 - info: zigbee.1 (5664) delete old Backup files. keep only last 10 2023-07-26 21:21:45.196 - info: zigbee.1 (5664) Starting Zigbee npm ... 2023-07-26 21:21:45.568 - info: zigbee.1 (5664) Installed Version: iobroker.zigbee@1.8.12 2023-07-26 21:21:45.054 - info: zigbee.1 (5664) starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 2023-07-26 21:21:45.193 - info: zigbee.1 (5664) delete old Backup files. keep only last 10 2023-07-26 21:21:45.196 - info: zigbee.1 (5664) Starting Zigbee npm ... 2023-07-26 21:21:45.568 - info: zigbee.1 (5664) Installed Version: iobroker.zigbee@1.8.12 2023-07-26 21:21:47.052 - error: zigbee.1 (5664) Configuration is not consistent with adapter state/backup! 2023-07-26 21:21:47.054 - error: zigbee.1 (5664) - PAN ID: configured=6754, adapter=6755 2023-07-26 21:21:47.055 - error: zigbee.1 (5664) - Extended PAN ID: configured=00124b0025792115, adapter=00124b0025792115 2023-07-26 21:21:47.056 - error: zigbee.1 (5664) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d 2023-07-26 21:21:47.057 - error: zigbee.1 (5664) - Channel List: configured=11, adapter=11 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) Please update configuration to prevent further issues. 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_1/nvbackup.json. 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Re-commissioning your network will require re-pairing of all devices! 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Running despite adapter configuration mismatch as configured. Please update the adapter to compatible firmware and recreate your network as soon as possible. 2023-07-26 21:21:47.357 - info: zigbee.1 (5664) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:21:47.368 - info: zigbee.1 (5664) Disable LED 2023-07-26 21:21:47.370 - info: zigbee.1 (5664) Unable to disable LED, unsupported function. 2023-07-26 21:21:47.390 - info: zigbee.1 (5664) --> transmitPower : high+ 2023-07-26 21:21:47.401 - info: zigbee.1 (5664) Currently no devices. 2023-07-26 21:21:47.402 - info: zigbee.1 (5664) Zigbee started 2023-07-26 21:21:47.405 - error: zigbee.1 (5664) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms 2023-07-26 21:21:47.407 - error: zigbee.1 (5664) 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-07-26 21:21:47.408 - error: zigbee.1 (5664) unhandled promise rejection: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) TypeError: Cannot read properties of undefined (reading 'Error') at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.464 - info: zigbee.1 (5664) cleaned everything up... 2023-07-26 21:21:47.467 - info: zigbee.1 (5664) Zigbee: disabling joining new devices. 2023-07-26 21:21:47.966 - info: zigbee.1 (5664) terminating 2023-07-26 21:21:47.969 - warn: zigbee.1 (5664) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-26 21:21:48.673 - error: host.CAS-pi 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-07-26 21:21:48.673 - error: host.CAS-pi Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:48.674 - error: host.CAS-pi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:48.676 - error: host.CAS-pi instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-26 21:21:48.676 - info: host.CAS-pi Restart adapter system.adapter.zigbee.1 because enabled 2023-07-26 21:21:47.052 - error: zigbee.1 (5664) Configuration is not consistent with adapter state/backup! 2023-07-26 21:21:47.054 - error: zigbee.1 (5664) - PAN ID: configured=6754, adapter=6755 2023-07-26 21:21:47.055 - error: zigbee.1 (5664) - Extended PAN ID: configured=00124b0025792115, adapter=00124b0025792115 2023-07-26 21:21:47.056 - error: zigbee.1 (5664) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d 2023-07-26 21:21:47.057 - error: zigbee.1 (5664) - Channel List: configured=11, adapter=11 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) Please update configuration to prevent further issues. 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_1/nvbackup.json. 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Re-commissioning your network will require re-pairing of all devices! 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Running despite adapter configuration mismatch as configured. Please update the adapter to compatible firmware and recreate your network as soon as possible. 2023-07-26 21:21:47.357 - info: zigbee.1 (5664) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:21:47.368 - info: zigbee.1 (5664) Disable LED 2023-07-26 21:21:47.370 - info: zigbee.1 (5664) Unable to disable LED, unsupported function. 2023-07-26 21:21:47.390 - info: zigbee.1 (5664) --> transmitPower : high+ 2023-07-26 21:21:47.401 - info: zigbee.1 (5664) Currently no devices. 2023-07-26 21:21:47.402 - info: zigbee.1 (5664) Zigbee started 2023-07-26 21:21:47.405 - error: zigbee.1 (5664) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms 2023-07-26 21:21:47.407 - error: zigbee.1 (5664) 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-07-26 21:21:47.408 - error: zigbee.1 (5664) unhandled promise rejection: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) TypeError: Cannot read properties of undefined (reading 'Error') at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.464 - info: zigbee.1 (5664) cleaned everything up... 2023-07-26 21:21:47.467 - info: zigbee.1 (5664) Zigbee: disabling joining new devices. 2023-07-26 21:21:47.966 - info: zigbee.1 (5664) terminating 2023-07-26 21:21:47.969 - warn: zigbee.1 (5664) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-26 21:21:48.673 - error: host.CAS-pi 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-07-26 21:21:48.673 - error: host.CAS-pi Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:48.674 - error: host.CAS-pi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:48.676 - error: host.CAS-pi instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-26 21:21:48.676 - info: host.CAS-pi Restart adapter system.adapter.zigbee.1 because enabled -
2023-07-26 21:21:45.054 - info: zigbee.1 (5664) starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 2023-07-26 21:21:45.193 - info: zigbee.1 (5664) delete old Backup files. keep only last 10 2023-07-26 21:21:45.196 - info: zigbee.1 (5664) Starting Zigbee npm ... 2023-07-26 21:21:45.568 - info: zigbee.1 (5664) Installed Version: iobroker.zigbee@1.8.12 2023-07-26 21:21:45.054 - info: zigbee.1 (5664) starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 2023-07-26 21:21:45.193 - info: zigbee.1 (5664) delete old Backup files. keep only last 10 2023-07-26 21:21:45.196 - info: zigbee.1 (5664) Starting Zigbee npm ... 2023-07-26 21:21:45.568 - info: zigbee.1 (5664) Installed Version: iobroker.zigbee@1.8.12 2023-07-26 21:21:47.052 - error: zigbee.1 (5664) Configuration is not consistent with adapter state/backup! 2023-07-26 21:21:47.054 - error: zigbee.1 (5664) - PAN ID: configured=6754, adapter=6755 2023-07-26 21:21:47.055 - error: zigbee.1 (5664) - Extended PAN ID: configured=00124b0025792115, adapter=00124b0025792115 2023-07-26 21:21:47.056 - error: zigbee.1 (5664) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d 2023-07-26 21:21:47.057 - error: zigbee.1 (5664) - Channel List: configured=11, adapter=11 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) Please update configuration to prevent further issues. 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_1/nvbackup.json. 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Re-commissioning your network will require re-pairing of all devices! 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Running despite adapter configuration mismatch as configured. Please update the adapter to compatible firmware and recreate your network as soon as possible. 2023-07-26 21:21:47.357 - info: zigbee.1 (5664) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:21:47.368 - info: zigbee.1 (5664) Disable LED 2023-07-26 21:21:47.370 - info: zigbee.1 (5664) Unable to disable LED, unsupported function. 2023-07-26 21:21:47.390 - info: zigbee.1 (5664) --> transmitPower : high+ 2023-07-26 21:21:47.401 - info: zigbee.1 (5664) Currently no devices. 2023-07-26 21:21:47.402 - info: zigbee.1 (5664) Zigbee started 2023-07-26 21:21:47.405 - error: zigbee.1 (5664) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms 2023-07-26 21:21:47.407 - error: zigbee.1 (5664) 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-07-26 21:21:47.408 - error: zigbee.1 (5664) unhandled promise rejection: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) TypeError: Cannot read properties of undefined (reading 'Error') at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.464 - info: zigbee.1 (5664) cleaned everything up... 2023-07-26 21:21:47.467 - info: zigbee.1 (5664) Zigbee: disabling joining new devices. 2023-07-26 21:21:47.966 - info: zigbee.1 (5664) terminating 2023-07-26 21:21:47.969 - warn: zigbee.1 (5664) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-26 21:21:48.673 - error: host.CAS-pi 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-07-26 21:21:48.673 - error: host.CAS-pi Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:48.674 - error: host.CAS-pi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:48.676 - error: host.CAS-pi instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-26 21:21:48.676 - info: host.CAS-pi Restart adapter system.adapter.zigbee.1 because enabled 2023-07-26 21:21:47.052 - error: zigbee.1 (5664) Configuration is not consistent with adapter state/backup! 2023-07-26 21:21:47.054 - error: zigbee.1 (5664) - PAN ID: configured=6754, adapter=6755 2023-07-26 21:21:47.055 - error: zigbee.1 (5664) - Extended PAN ID: configured=00124b0025792115, adapter=00124b0025792115 2023-07-26 21:21:47.056 - error: zigbee.1 (5664) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d 2023-07-26 21:21:47.057 - error: zigbee.1 (5664) - Channel List: configured=11, adapter=11 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) Please update configuration to prevent further issues. 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_1/nvbackup.json. 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Re-commissioning your network will require re-pairing of all devices! 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Running despite adapter configuration mismatch as configured. Please update the adapter to compatible firmware and recreate your network as soon as possible. 2023-07-26 21:21:47.357 - info: zigbee.1 (5664) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:21:47.368 - info: zigbee.1 (5664) Disable LED 2023-07-26 21:21:47.370 - info: zigbee.1 (5664) Unable to disable LED, unsupported function. 2023-07-26 21:21:47.390 - info: zigbee.1 (5664) --> transmitPower : high+ 2023-07-26 21:21:47.401 - info: zigbee.1 (5664) Currently no devices. 2023-07-26 21:21:47.402 - info: zigbee.1 (5664) Zigbee started 2023-07-26 21:21:47.405 - error: zigbee.1 (5664) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms 2023-07-26 21:21:47.407 - error: zigbee.1 (5664) 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-07-26 21:21:47.408 - error: zigbee.1 (5664) unhandled promise rejection: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) TypeError: Cannot read properties of undefined (reading 'Error') at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.464 - info: zigbee.1 (5664) cleaned everything up... 2023-07-26 21:21:47.467 - info: zigbee.1 (5664) Zigbee: disabling joining new devices. 2023-07-26 21:21:47.966 - info: zigbee.1 (5664) terminating 2023-07-26 21:21:47.969 - warn: zigbee.1 (5664) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-26 21:21:48.673 - error: host.CAS-pi 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-07-26 21:21:48.673 - error: host.CAS-pi Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:48.674 - error: host.CAS-pi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:48.676 - error: host.CAS-pi instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-26 21:21:48.676 - info: host.CAS-pi Restart adapter system.adapter.zigbee.1 because enabled@michihorn sagte in Zigbee mit TCP:
PAN ID: configured=6754, adapter=6755
Ich wiederhole mich glaube ich.
Die Werte MÜSSEN übereinstimmen. -
2023-07-26 21:21:45.054 - info: zigbee.1 (5664) starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 2023-07-26 21:21:45.193 - info: zigbee.1 (5664) delete old Backup files. keep only last 10 2023-07-26 21:21:45.196 - info: zigbee.1 (5664) Starting Zigbee npm ... 2023-07-26 21:21:45.568 - info: zigbee.1 (5664) Installed Version: iobroker.zigbee@1.8.12 2023-07-26 21:21:45.054 - info: zigbee.1 (5664) starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 2023-07-26 21:21:45.193 - info: zigbee.1 (5664) delete old Backup files. keep only last 10 2023-07-26 21:21:45.196 - info: zigbee.1 (5664) Starting Zigbee npm ... 2023-07-26 21:21:45.568 - info: zigbee.1 (5664) Installed Version: iobroker.zigbee@1.8.12 2023-07-26 21:21:47.052 - error: zigbee.1 (5664) Configuration is not consistent with adapter state/backup! 2023-07-26 21:21:47.054 - error: zigbee.1 (5664) - PAN ID: configured=6754, adapter=6755 2023-07-26 21:21:47.055 - error: zigbee.1 (5664) - Extended PAN ID: configured=00124b0025792115, adapter=00124b0025792115 2023-07-26 21:21:47.056 - error: zigbee.1 (5664) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d 2023-07-26 21:21:47.057 - error: zigbee.1 (5664) - Channel List: configured=11, adapter=11 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) Please update configuration to prevent further issues. 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_1/nvbackup.json. 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Re-commissioning your network will require re-pairing of all devices! 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Running despite adapter configuration mismatch as configured. Please update the adapter to compatible firmware and recreate your network as soon as possible. 2023-07-26 21:21:47.357 - info: zigbee.1 (5664) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:21:47.368 - info: zigbee.1 (5664) Disable LED 2023-07-26 21:21:47.370 - info: zigbee.1 (5664) Unable to disable LED, unsupported function. 2023-07-26 21:21:47.390 - info: zigbee.1 (5664) --> transmitPower : high+ 2023-07-26 21:21:47.401 - info: zigbee.1 (5664) Currently no devices. 2023-07-26 21:21:47.402 - info: zigbee.1 (5664) Zigbee started 2023-07-26 21:21:47.405 - error: zigbee.1 (5664) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms 2023-07-26 21:21:47.407 - error: zigbee.1 (5664) 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-07-26 21:21:47.408 - error: zigbee.1 (5664) unhandled promise rejection: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) TypeError: Cannot read properties of undefined (reading 'Error') at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.464 - info: zigbee.1 (5664) cleaned everything up... 2023-07-26 21:21:47.467 - info: zigbee.1 (5664) Zigbee: disabling joining new devices. 2023-07-26 21:21:47.966 - info: zigbee.1 (5664) terminating 2023-07-26 21:21:47.969 - warn: zigbee.1 (5664) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-26 21:21:48.673 - error: host.CAS-pi 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-07-26 21:21:48.673 - error: host.CAS-pi Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:48.674 - error: host.CAS-pi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:48.676 - error: host.CAS-pi instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-26 21:21:48.676 - info: host.CAS-pi Restart adapter system.adapter.zigbee.1 because enabled 2023-07-26 21:21:47.052 - error: zigbee.1 (5664) Configuration is not consistent with adapter state/backup! 2023-07-26 21:21:47.054 - error: zigbee.1 (5664) - PAN ID: configured=6754, adapter=6755 2023-07-26 21:21:47.055 - error: zigbee.1 (5664) - Extended PAN ID: configured=00124b0025792115, adapter=00124b0025792115 2023-07-26 21:21:47.056 - error: zigbee.1 (5664) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d 2023-07-26 21:21:47.057 - error: zigbee.1 (5664) - Channel List: configured=11, adapter=11 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) Please update configuration to prevent further issues. 2023-07-26 21:21:47.059 - error: zigbee.1 (5664) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_1/nvbackup.json. 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Re-commissioning your network will require re-pairing of all devices! 2023-07-26 21:21:47.060 - error: zigbee.1 (5664) Running despite adapter configuration mismatch as configured. Please update the adapter to compatible firmware and recreate your network as soon as possible. 2023-07-26 21:21:47.357 - info: zigbee.1 (5664) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:21:47.368 - info: zigbee.1 (5664) Disable LED 2023-07-26 21:21:47.370 - info: zigbee.1 (5664) Unable to disable LED, unsupported function. 2023-07-26 21:21:47.390 - info: zigbee.1 (5664) --> transmitPower : high+ 2023-07-26 21:21:47.401 - info: zigbee.1 (5664) Currently no devices. 2023-07-26 21:21:47.402 - info: zigbee.1 (5664) Zigbee started 2023-07-26 21:21:47.405 - error: zigbee.1 (5664) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms 2023-07-26 21:21:47.407 - error: zigbee.1 (5664) 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-07-26 21:21:47.408 - error: zigbee.1 (5664) unhandled promise rejection: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) TypeError: Cannot read properties of undefined (reading 'Error') at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:47.450 - error: zigbee.1 (5664) Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:47.464 - info: zigbee.1 (5664) cleaned everything up... 2023-07-26 21:21:47.467 - info: zigbee.1 (5664) Zigbee: disabling joining new devices. 2023-07-26 21:21:47.966 - info: zigbee.1 (5664) terminating 2023-07-26 21:21:47.969 - warn: zigbee.1 (5664) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-26 21:21:48.673 - error: host.CAS-pi 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-07-26 21:21:48.673 - error: host.CAS-pi Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'Error') 2023-07-26 21:21:48.674 - error: host.CAS-pi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:122:56 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Hub.configureScope (/opt/iobroker/node_modules/@sentry/src/hub.ts:340:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Object.configureScope (/opt/iobroker/node_modules/@sentry/src/exports.ts:76:1) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.sendError (/opt/iobroker/node_modules/iobroker.zigbee/main.js:118:32) 2023-07-26 21:21:48.675 - error: host.CAS-pi Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:415:30) 2023-07-26 21:21:48.676 - error: host.CAS-pi instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-26 21:21:48.676 - info: host.CAS-pi Restart adapter system.adapter.zigbee.1 because enabledUnd schalte Sentry für die Instanz aus.
-
@michihorn sagte in Zigbee mit TCP:
PAN ID: configured=6754, adapter=6755
Ich wiederhole mich glaube ich.
Die Werte MÜSSEN übereinstimmen.@thomas-braun Ich weiß hattest du geschrieben, habe ich auch mittels Screenshot gezeigt.
Offenbar ist irgendwo noch die 6755 gespeichert.Ich habe aus dem aktuellen Protokoll eine neue Erweiterte Pan ID angezeigt bekommen, die konnte gespeichert werden, im Moment ist der Adapter grün. Das wars leider nicht nun ist der Adapter gelb. Sentry ist ausgeschaltet. Witzigerweise ist wärend ich hier schreibe der Adapter wieder auf grün gegangen
Nun ist er wieder auf gelb, im Protokoll steht folgendes:
zigbee.1 6054 2023-07-26 21:46:28.878 error Failed to start Zigbee zigbee.1 6054 2023-07-26 21:46:28.876 error Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby" zigbee.1 6054 2023-07-26 21:45:22.035 info Installed Version: iobroker.zigbee@1.8.12 zigbee.1 6054 2023-07-26 21:45:21.572 info Starting Zigbee npm ... zigbee.1 6054 2023-07-26 21:45:21.388 info starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 zigbee.1 5949 2023-07-26 21:45:07.905 info terminating zigbee.1 5949 2023-07-26 21:45:07.730 warn setObject info.debugmessages (type=state) property common.role missing! zigbee.1 5949 2023-07-26 21:45:07.637 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.1 5949 2023-07-26 21:45:07.632 info terminating zigbee.1 5949 2023-07-26 21:45:07.630 warn Failed to stop zigbee during startup zigbee.1 5949 2023-07-26 21:45:07.615 warn setObject info.undefinedDevices (type=state) property common.role missing! zigbee.1 5949 2023-07-26 21:45:07.595 info Zigbee: disabling joining new devices. zigbee.1 5949 2023-07-26 21:45:07.403 info cleaned everything up... zigbee.1 5949 2023-07-26 21:45:07.400 info Got terminate signal TERMINATE_YOURSELF zigbee.1 5949 2023-07-26 21:44:47.814 info Installed Version: iobroker.zigbee@1.8.12 zigbee.1 5949 2023-07-26 21:44:47.430 info Starting Zigbee npm ... zigbee.1 5949 2023-07-26 21:44:47.239 info starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 zigbee.1 5933 2023-07-26 21:44:38.970 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.1 5933 2023-07-26 21:44:38.968 info terminating zigbee.1 5933 2023-07-26 21:44:38.782 warn setObject info.debugmessages (type=state) property common.role missing! zigbee.1 5933 2023-07-26 21:44:38.580 warn setObject info.undefinedDevices (type=state) property common.role missing! zigbee.1 5933 2023-07-26 21:44:38.563 info Zigbee: disabling joining new devices. zigbee.1 5933 2023-07-26 21:44:38.467 info cleaned everything up... zigbee.1 5933 2023-07-26 21:44:38.464 info Got terminate signal TERMINATE_YOURSELF zigbee.1 5933 2023-07-26 21:44:35.502 info List of port: [{"path":"/dev/ttyAMA0"}] -
@thomas-braun Ich weiß hattest du geschrieben, habe ich auch mittels Screenshot gezeigt.
Offenbar ist irgendwo noch die 6755 gespeichert.Ich habe aus dem aktuellen Protokoll eine neue Erweiterte Pan ID angezeigt bekommen, die konnte gespeichert werden, im Moment ist der Adapter grün. Das wars leider nicht nun ist der Adapter gelb. Sentry ist ausgeschaltet. Witzigerweise ist wärend ich hier schreibe der Adapter wieder auf grün gegangen
Nun ist er wieder auf gelb, im Protokoll steht folgendes:
zigbee.1 6054 2023-07-26 21:46:28.878 error Failed to start Zigbee zigbee.1 6054 2023-07-26 21:46:28.876 error Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby" zigbee.1 6054 2023-07-26 21:45:22.035 info Installed Version: iobroker.zigbee@1.8.12 zigbee.1 6054 2023-07-26 21:45:21.572 info Starting Zigbee npm ... zigbee.1 6054 2023-07-26 21:45:21.388 info starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 zigbee.1 5949 2023-07-26 21:45:07.905 info terminating zigbee.1 5949 2023-07-26 21:45:07.730 warn setObject info.debugmessages (type=state) property common.role missing! zigbee.1 5949 2023-07-26 21:45:07.637 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.1 5949 2023-07-26 21:45:07.632 info terminating zigbee.1 5949 2023-07-26 21:45:07.630 warn Failed to stop zigbee during startup zigbee.1 5949 2023-07-26 21:45:07.615 warn setObject info.undefinedDevices (type=state) property common.role missing! zigbee.1 5949 2023-07-26 21:45:07.595 info Zigbee: disabling joining new devices. zigbee.1 5949 2023-07-26 21:45:07.403 info cleaned everything up... zigbee.1 5949 2023-07-26 21:45:07.400 info Got terminate signal TERMINATE_YOURSELF zigbee.1 5949 2023-07-26 21:44:47.814 info Installed Version: iobroker.zigbee@1.8.12 zigbee.1 5949 2023-07-26 21:44:47.430 info Starting Zigbee npm ... zigbee.1 5949 2023-07-26 21:44:47.239 info starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 zigbee.1 5933 2023-07-26 21:44:38.970 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.1 5933 2023-07-26 21:44:38.968 info terminating zigbee.1 5933 2023-07-26 21:44:38.782 warn setObject info.debugmessages (type=state) property common.role missing! zigbee.1 5933 2023-07-26 21:44:38.580 warn setObject info.undefinedDevices (type=state) property common.role missing! zigbee.1 5933 2023-07-26 21:44:38.563 info Zigbee: disabling joining new devices. zigbee.1 5933 2023-07-26 21:44:38.467 info cleaned everything up... zigbee.1 5933 2023-07-26 21:44:38.464 info Got terminate signal TERMINATE_YOURSELF zigbee.1 5933 2023-07-26 21:44:35.502 info List of port: [{"path":"/dev/ttyAMA0"}]Das ist wieder der chronologisch falsche Eintrag aus dem Admin.
Ich hab keine Lust von unten nach oben zu lesen. -
Das ist wieder der chronologisch falsche Eintrag aus dem Admin.
Ich hab keine Lust von unten nach oben zu lesen.@thomas-braun Offenbar weiß ich nicht was du sehen willst, so habe ich das Protokoll kopiert
-
@thomas-braun Offenbar weiß ich nicht was du sehen willst, so habe ich das Protokoll kopiert
Du nimmst das natürlich aus dem Terminal. Dafür hast du das ja offen und das Log läuft da mit. Chronologisch richtig.
-
Du nimmst das natürlich aus dem Terminal. Dafür hast du das ja offen und das Log läuft da mit. Chronologisch richtig.
@thomas-braun Aktuell ist der Adapter wieder grün
2023-07-26 21:57:02.102 - info: zigbee.1 (6127) Try to reconnect. 2023-07-26 21:57:02.103 - info: zigbee.1 (6127) Starting Zigbee npm ... 2023-07-26 21:57:02.104 - info: zigbee.1 (6127) Try to reconnect. 2023-07-26 21:57:02.105 - info: zigbee.1 (6127) Starting Zigbee npm ... 2023-07-26 21:57:03.868 - info: zigbee.1 (6127) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:57:03.870 - info: zigbee.1 (6127) Disable LED 2023-07-26 21:57:03.871 - info: zigbee.1 (6127) Unable to disable LED, unsupported function. 2023-07-26 21:57:03.872 - info: zigbee.1 (6127) --> transmitPower : high+ 2023-07-26 21:57:03.883 - info: zigbee.1 (6127) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:57:03.883 - info: zigbee.1 (6127) Disable LED 2023-07-26 21:57:03.884 - info: zigbee.1 (6127) Unable to disable LED, unsupported function. 2023-07-26 21:57:03.885 - info: zigbee.1 (6127) --> transmitPower : high+ 2023-07-26 21:57:03.892 - info: zigbee.1 (6127) Currently no devices. 2023-07-26 21:57:03.892 - info: zigbee.1 (6127) Zigbee started 2023-07-26 21:57:03.901 - info: zigbee.1 (6127) Currently no devices. 2023-07-26 21:57:03.901 - info: zigbee.1 (6127) Zigbee started -
@thomas-braun Aktuell ist der Adapter wieder grün
2023-07-26 21:57:02.102 - info: zigbee.1 (6127) Try to reconnect. 2023-07-26 21:57:02.103 - info: zigbee.1 (6127) Starting Zigbee npm ... 2023-07-26 21:57:02.104 - info: zigbee.1 (6127) Try to reconnect. 2023-07-26 21:57:02.105 - info: zigbee.1 (6127) Starting Zigbee npm ... 2023-07-26 21:57:03.868 - info: zigbee.1 (6127) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:57:03.870 - info: zigbee.1 (6127) Disable LED 2023-07-26 21:57:03.871 - info: zigbee.1 (6127) Unable to disable LED, unsupported function. 2023-07-26 21:57:03.872 - info: zigbee.1 (6127) --> transmitPower : high+ 2023-07-26 21:57:03.883 - info: zigbee.1 (6127) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220726}} 2023-07-26 21:57:03.883 - info: zigbee.1 (6127) Disable LED 2023-07-26 21:57:03.884 - info: zigbee.1 (6127) Unable to disable LED, unsupported function. 2023-07-26 21:57:03.885 - info: zigbee.1 (6127) --> transmitPower : high+ 2023-07-26 21:57:03.892 - info: zigbee.1 (6127) Currently no devices. 2023-07-26 21:57:03.892 - info: zigbee.1 (6127) Zigbee started 2023-07-26 21:57:03.901 - info: zigbee.1 (6127) Currently no devices. 2023-07-26 21:57:03.901 - info: zigbee.1 (6127) Zigbee started -
@thomas-braun Danke für deinen Einsatz, konnte auch gerade ein Gerät pairen
-
@thomas-braun Ich weiß hattest du geschrieben, habe ich auch mittels Screenshot gezeigt.
Offenbar ist irgendwo noch die 6755 gespeichert.Ich habe aus dem aktuellen Protokoll eine neue Erweiterte Pan ID angezeigt bekommen, die konnte gespeichert werden, im Moment ist der Adapter grün. Das wars leider nicht nun ist der Adapter gelb. Sentry ist ausgeschaltet. Witzigerweise ist wärend ich hier schreibe der Adapter wieder auf grün gegangen
Nun ist er wieder auf gelb, im Protokoll steht folgendes:
zigbee.1 6054 2023-07-26 21:46:28.878 error Failed to start Zigbee zigbee.1 6054 2023-07-26 21:46:28.876 error Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby" zigbee.1 6054 2023-07-26 21:45:22.035 info Installed Version: iobroker.zigbee@1.8.12 zigbee.1 6054 2023-07-26 21:45:21.572 info Starting Zigbee npm ... zigbee.1 6054 2023-07-26 21:45:21.388 info starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 zigbee.1 5949 2023-07-26 21:45:07.905 info terminating zigbee.1 5949 2023-07-26 21:45:07.730 warn setObject info.debugmessages (type=state) property common.role missing! zigbee.1 5949 2023-07-26 21:45:07.637 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.1 5949 2023-07-26 21:45:07.632 info terminating zigbee.1 5949 2023-07-26 21:45:07.630 warn Failed to stop zigbee during startup zigbee.1 5949 2023-07-26 21:45:07.615 warn setObject info.undefinedDevices (type=state) property common.role missing! zigbee.1 5949 2023-07-26 21:45:07.595 info Zigbee: disabling joining new devices. zigbee.1 5949 2023-07-26 21:45:07.403 info cleaned everything up... zigbee.1 5949 2023-07-26 21:45:07.400 info Got terminate signal TERMINATE_YOURSELF zigbee.1 5949 2023-07-26 21:44:47.814 info Installed Version: iobroker.zigbee@1.8.12 zigbee.1 5949 2023-07-26 21:44:47.430 info Starting Zigbee npm ... zigbee.1 5949 2023-07-26 21:44:47.239 info starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8 zigbee.1 5933 2023-07-26 21:44:38.970 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.1 5933 2023-07-26 21:44:38.968 info terminating zigbee.1 5933 2023-07-26 21:44:38.782 warn setObject info.debugmessages (type=state) property common.role missing! zigbee.1 5933 2023-07-26 21:44:38.580 warn setObject info.undefinedDevices (type=state) property common.role missing! zigbee.1 5933 2023-07-26 21:44:38.563 info Zigbee: disabling joining new devices. zigbee.1 5933 2023-07-26 21:44:38.467 info cleaned everything up... zigbee.1 5933 2023-07-26 21:44:38.464 info Got terminate signal TERMINATE_YOURSELF zigbee.1 5933 2023-07-26 21:44:35.502 info List of port: [{"path":"/dev/ttyAMA0"}]@michihorn sagte in Erledigt: Zigbee mit TCP:
zigbee.1
6054 2023-07-26 21:46:28.876 error Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby"Moin,
irgendwo in Deinem Netzwerk gibt es da Überlappungen, Du musst mal schauen, ob noch andere auf dem Kanal 11 Funken, ansonsten kann es immer wieder mal zu Aussetzern im Zigbee Netzwerk kommen.
Das ist nur zur Information:
Hier mal etwas von Github, ist zwarzigbee2mqtt, ist aber egal, das derzigbee` Adapter darauf aufbaut.
https://github.com/Koenkk/zigbee2mqtt/issues/10858VG
Bernd
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden