ZigBee neue Version 1.4.4
-
@kueppert sagte in ZigBee neue Version 1.4.4:
@klassisch habs geschafft...hab einfach nach meinen Versuchen die Teile am Strom gelassen und 1h später nochmal versucht...NACHEINANDER. Gleichzeitig 2 Repeater wollte der Stick nicht.
Vorgehen:
Im Adapter den Suchvorgang/Anlernprozess gestartet
am Repeater das Knöpchen 5 Sekunden gehalten => blinkt
WARTEN und nicht ungeduldig sein (hab 120 Sekunden eingestellt)Moin, wie bist du mit den Zigbee Verstärkern zufrieden? Bin auch gerade auf der Suche und noch etwas unschlüssig
-
Moin, Hilfe!
habe jetzt auf Kanal 15 gewechselt und angefangen die Teilnehmer neu zu verbinden. Lief für die ersten 10 auch gut. Dann ging der Adapter auf rot und läßt sich nicht mehr starten.zigbee.0 2021-03-24 11:15:20.050 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:20.050 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:20.050 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:20.050 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:20.049 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:20.048 error (23087) 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 2021-03-24 11:15:19.988 warn (23087) Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee.0 2021-03-24 11:15:19.986 info (23087) terminating zigbee.0 2021-03-24 11:15:19.985 warn (23087) Failed to stop zigbee during startup zigbee.0 2021-03-24 11:15:19.982 info (23087) Zigbee: disabling joining new devices. zigbee.0 2021-03-24 11:15:19.978 info (23087) cleaned everything up... zigbee.0 2021-03-24 11:15:19.973 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.973 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:15:19.973 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:15:19.973 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.973 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:19.973 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.972 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.971 error (23087) 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 2021-03-24 11:15:19.947 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.947 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.947 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:19.947 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.946 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.945 error (23087) 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 2021-03-24 11:15:19.939 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.938 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:15:19.938 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:15:19.938 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.938 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:19.938 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.937 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.937 error (23087) 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 2021-03-24 11:15:19.932 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.931 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:15:19.931 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:15:19.931 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.931 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:19.931 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.930 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.929 error (23087) 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 2021-03-24 11:15:19.924 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.923 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:15:19.923 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:15:19.923 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.923 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:19.923 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.922 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.921 error (23087) 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 2021-03-24 11:15:19.910 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.908 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:15:19.908 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:15:19.908 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.908 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:19.908 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.907 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.906 error (23087) 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 2021-03-24 11:15:19.883 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.882 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.882 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:19.882 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.881 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.881 error (23087) 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 2021-03-24 11:15:19.874 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.874 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:15:19.874 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:15:19.874 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.874 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:19.874 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.873 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.871 error (23087) 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 2021-03-24 11:15:19.867 error (23087) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.866 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:15:19.866 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:15:19.866 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.866 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:15:19.866 error (23087) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.866 error (23087) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:15:19.865 error (23087) 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 2021-03-24 11:15:19.858 error (23087) Cannot read property 'getEntries' of null zigbee.0 2021-03-24 11:15:19.857 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:15:19.857 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:15:19.857 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:15:19.857 error at StatesController.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:213:14) zigbee.0 2021-03-24 11:15:19.857 error at StatesController.emit (events.js:314:20) zigbee.0 2021-03-24 11:15:19.857 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:443:48) zigbee.0 2021-03-24 11:15:19.857 error at ZigbeeController.resolveEntity (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:239:52) zigbee.0 2021-03-24 11:15:19.857 error at Controller.getDeviceByIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:301:31) zigbee.0 2021-03-24 11:15:19.857 error at Function.byIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:228:16) zigbee.0 2021-03-24 11:15:19.857 error at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55) zigbee.0 2021-03-24 11:15:19.857 error (23087) TypeError: Cannot read property 'getEntries' of null zigbee.0 2021-03-24 11:15:19.855 error (23087) unhandled promise rejection: Cannot read property 'getEntries' of null zigbee.0 2021-03-24 11:15:19.854 error (23087) 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 2021-03-24 11:15:16.746 info (23087) Installed Version: ioBroker/ioBroker.zigbee#master zigbee.0 2021-03-24 11:15:16.372 info (23087) Starting Zigbee npm ... zigbee.0 2021-03-24 11:15:16.201 info (23087) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.20.1, js-controller: 3.2.16Hoffe das das Log euch auf die richtige Spur bringt, ich kann das leider nicht interpretieren.
-
Bitte folgendes Tun:
- Adapter anhalten
- 60 sekunden warten
- log löschen
- adapter starten
- vollständiges Log posten.
Der Log-Eintrag vom eigentlichen Fehler ist in deiner Liste nicht zu sehen. Alle sichtbaren Meldungen sind Folgefehler eines initialen Fehlers.
A.
-
@asgothian okay
tr-064.0 2021-03-24 11:40:32.786 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReque tr-064.0 2021-03-24 11:40:31.523 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 11:40:31.463 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 11:40:31.406 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action= host.raspberrypi 2021-03-24 11:40:30.680 info Restart adapter system.adapter.zigbee.0 because enabled host.raspberrypi 2021-03-24 11:40:30.679 error instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) zigbee.0 2021-03-24 11:40:30.155 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.154 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:30.154 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:30.154 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.153 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.152 error (5544) 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 2021-03-24 11:40:30.147 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.147 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:40:30.147 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:40:30.147 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:30.147 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:30.147 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.146 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.145 error (5544) 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 2021-03-24 11:40:30.085 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.081 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:30.081 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:30.081 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.081 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.080 error (5544) 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 2021-03-24 11:40:30.070 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.070 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:40:30.070 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:40:30.070 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:30.070 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:30.070 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.069 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.068 error (5544) 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 2021-03-24 11:40:30.026 warn (5544) Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee.0 2021-03-24 11:40:30.025 info (5544) terminating zigbee.0 2021-03-24 11:40:30.024 warn (5544) Failed to stop zigbee during startup zigbee.0 2021-03-24 11:40:30.022 info (5544) Zigbee: disabling joining new devices. zigbee.0 2021-03-24 11:40:30.019 info (5544) cleaned everything up... zigbee.0 2021-03-24 11:40:30.016 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.015 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:40:30.015 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:40:30.015 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:30.015 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:30.015 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.014 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.014 error (5544) 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 2021-03-24 11:40:30.010 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.009 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:40:30.009 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:40:30.009 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:30.009 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:30.009 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.008 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.007 error (5544) 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 2021-03-24 11:40:30.002 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.001 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:40:30.001 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:40:30.001 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:30.001 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:30.001 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.000 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:30.000 error (5544) 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 2021-03-24 11:40:29.975 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:29.974 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:40:29.974 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:40:29.974 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:29.974 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:29.974 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:29.974 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:29.972 error (5544) 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 2021-03-24 11:40:29.968 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:29.968 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:40:29.968 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:40:29.968 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:29.968 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:29.968 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:29.967 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:29.966 error (5544) 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 2021-03-24 11:40:29.961 error (5544) Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:29.960 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:40:29.960 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:40:29.960 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:29.960 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:445:36) zigbee.0 2021-03-24 11:40:29.960 error (5544) TypeError: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:29.960 error (5544) unhandled promise rejection: Cannot read property 'mapped' of undefined zigbee.0 2021-03-24 11:40:29.959 error (5544) 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 2021-03-24 11:40:29.953 error (5544) Cannot read property 'getEntries' of null zigbee.0 2021-03-24 11:40:29.953 error at processImmediate (internal/timers.js:434:9) zigbee.0 2021-03-24 11:40:29.953 error at runNextTicks (internal/process/task_queues.js:66:3) zigbee.0 2021-03-24 11:40:29.953 error at processTicksAndRejections (internal/process/task_queues.js:97:5) zigbee.0 2021-03-24 11:40:29.953 error at StatesController.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:213:14) zigbee.0 2021-03-24 11:40:29.953 error at StatesController.emit (events.js:314:20) zigbee.0 2021-03-24 11:40:29.953 error at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:443:48) zigbee.0 2021-03-24 11:40:29.953 error at ZigbeeController.resolveEntity (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:239:52) zigbee.0 2021-03-24 11:40:29.953 error at Controller.getDeviceByIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:301:31) zigbee.0 2021-03-24 11:40:29.953 error at Function.byIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:228:16) zigbee.0 2021-03-24 11:40:29.953 error at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55) zigbee.0 2021-03-24 11:40:29.953 error (5544) TypeError: Cannot read property 'getEntries' of null zigbee.0 2021-03-24 11:40:29.951 error (5544) unhandled promise rejection: Cannot read property 'getEntries' of null zigbee.0 2021-03-24 11:40:29.950 error (5544) 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 2021-03-24 11:40:27.458 info (5544) Installed Version: ioBroker/ioBroker.zigbee#master zigbee.0 2021-03-24 11:40:27.100 info (5544) Starting Zigbee npm ... zigbee.0 2021-03-24 11:40:26.978 info (5544) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.20.1, js-controller: 3.2.16 host.raspberrypi 2021-03-24 11:40:23.543 info instance system.adapter.zigbee.0 started with pid 5544 host.raspberrypi 2021-03-24 11:40:23.487 info "system.adapter.zigbee.0" enabled tr-064.0 2021-03-24 11:40:19.728 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReque coronavirus-statistics.0 2021-03-24 11:40:19.255 info (4862) starting. Version 0.7.0-1 in /opt/iobroker/node_modules/iobroker.coronavirus-statistics, node: v12.20.1, js-controller: 3.2.16 tr-064.0 2021-03-24 11:40:18.388 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 11:40:18.337 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 11:40:18.287 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action= host.raspberrypi 2021-03-24 11:40:16.374 info instance system.adapter.dwd.3 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.raspberrypi 2021-03-24 11:40:16.227 info instance system.adapter.coronavirus-statistics.0 started with pid 4862 dwd.3 2021-03-24 11:40:15.826 info (4499) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason dwd.3 2021-03-24 11:40:14.639 info (4499) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.20.1, js-controller: 3.2.16 host.raspberrypi 2021-03-24 11:40:12.193 info instance system.adapter.dwd.3 started with pid 4499 host.raspberrypi 2021-03-24 11:40:11.956 info instance system.adapter.dwd.2 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) dwd.2 2021-03-24 11:40:11.429 info (4133) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason dwd.2 2021-03-24 11:40:10.679 info (4133) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.20.1, js-controller: 3.2.16 host.raspberrypi 2021-03-24 11:40:08.572 info instance system.adapter.dwd.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.raspberrypi 2021-03-24 11:40:08.157 info instance system.adapter.dwd.2 started with pid 4133 host.raspberrypi 2021-03-24 11:40:08.096 info instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) dwd.1 2021-03-24 11:40:07.988 info (3674) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason dwd.0 2021-03-24 11:40:07.563 info (3305) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason dwd.1 2021-03-24 11:40:07.103 info (3674) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v12.20.1, js-controller: 3.2.16 tr-064.0 2021-03-24 11:40:06.244 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReque tr-064.0 2021-03-24 11:40:04.924 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 11:40:04.873 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 11:40:04.824 info (13687) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action= host.raspberrypi 2021-03-24 11:40:04.114 info instance system.adapter.dwd.1 started with pid 3674hoffe das hilft jetzt besser
-
@frankthegreat sagte in ZigBee neue Version 1.4.4:
@kueppert sagte in ZigBee neue Version 1.4.4:
@klassisch habs geschafft...hab einfach nach meinen Versuchen die Teile am Strom gelassen und 1h später nochmal versucht...NACHEINANDER. Gleichzeitig 2 Repeater wollte der Stick nicht.
Vorgehen:
Im Adapter den Suchvorgang/Anlernprozess gestartet
am Repeater das Knöpchen 5 Sekunden gehalten => blinkt
WARTEN und nicht ungeduldig sein (hab 120 Sekunden eingestellt)Moin, wie bist du mit den Zigbee Verstärkern zufrieden? Bin auch gerade auf der Suche und noch etwas unschlüssig
Ich hatte zunächst OSRAM Plugs genutzt, die waren aber irgendwann zickig (unter anderem funktioniert mit denen die MAP im Adapter nicht richtig in Verbindung mit einem Conbee 2 Stick).
Jetzt habe ich auf jeder Etage so einen in einer Steckdose stecken:Der USB Stick hängt im Keller unter der Decke (per 2m USB Kabel am Server)
Bin sehr zufrieden damit. Beim Anlernen stoße ich das dann immer über dem SmartPlug in der Nähe an (mit dem 120 Sekunden Timer)
-
@asgothian habe jetzt bei meinen Raspi einen Neustart gemacht. Danach erhielt ich jetzt dieses Log:
host.raspberrypi 2021-03-24 15:08:02.242 info instance system.adapter.zigbee.0 started with pid 24411 host.raspberrypi 2021-03-24 15:07:59.936 info instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zigbee.0 2021-03-24 15:07:59.181 error (3691) Cannot read property 'getEntries' of null zigbee.0 2021-03-24 15:07:59.180 error (3691) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55) at Funct zigbee.0 2021-03-24 15:07:59.175 error (3691) unhandled promise rejection: Cannot read property 'getEntries' of null zigbee.0 2021-03-24 15:07:59.174 error (3691) 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 2021-03-24 15:07:59.173 info (3691) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2021-03-24 15:07:59.170 info (3691) terminating zigbee.0 2021-03-24 15:07:59.169 warn (3691) Failed to stop zigbee during startup zigbee.0 2021-03-24 15:07:59.166 info (3691) Zigbee: disabling joining new devices. zigbee.0 2021-03-24 15:07:59.159 info (3691) cleaned everything up... zigbee.0 2021-03-24 15:07:59.157 info (3691) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-03-24 15:07:59.162 info stopInstance system.adapter.zigbee.0 send kill signal host.raspberrypi 2021-03-24 15:07:59.144 info stopInstance system.adapter.zigbee.0 (force=false, process=true) tr-064.0 2021-03-24 15:07:54.627 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques tr-064.0 2021-03-24 15:07:53.474 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:07:53.349 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:07:53.292 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:07:53.230 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G tr-064.0 2021-03-24 15:07:41.016 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques tr-064.0 2021-03-24 15:07:39.737 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:07:39.607 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:07:39.555 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:07:39.495 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G tr-064.0 2021-03-24 15:07:27.536 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques tr-064.0 2021-03-24 15:07:25.473 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:07:25.348 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:07:25.293 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:07:25.238 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G host.raspberrypi 2021-03-24 15:07:15.332 info instance system.adapter.daswetter.0 terminated with code 0 (NO_ERROR) daswetter.0 2021-03-24 15:07:14.741 info (16101) Terminated (NO_ERROR): Without reason tr-064.0 2021-03-24 15:07:13.354 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques tr-064.0 2021-03-24 15:07:12.208 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:07:12.094 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:07:12.028 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:07:11.961 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G daswetter.0 2021-03-24 15:07:02.708 info (16101) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.daswetter, node: v12.20.1, js-controller: 3.2.16 tr-064.0 2021-03-24 15:07:00.094 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques host.raspberrypi 2021-03-24 15:07:00.056 info instance system.adapter.daswetter.0 started with pid 16101 tr-064.0 2021-03-24 15:06:58.918 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:06:58.797 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:58.747 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:58.693 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G zigbee.0 2021-03-24 15:06:55.093 error (3691) Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port' at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/zn zigbee.0 2021-03-24 15:06:55.091 error (3691) Failed to start Zigbee zigbee.0 2021-03-24 15:06:54.831 info (3691) Installed Version: ioBroker/ioBroker.zigbee#master zigbee.0 2021-03-24 15:06:54.808 info (3691) Starting Zigbee npm ... zigbee.0 2021-03-24 15:06:54.806 info (3691) Try to reconnect. 1 attempts left tr-064.0 2021-03-24 15:06:45.255 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques zigbee.0 2021-03-24 15:06:44.805 error (3691) Error: Coordinator failed to start, probably the panID is already in use, try a different panID or channel at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/startZn zigbee.0 2021-03-24 15:06:44.802 error (3691) Failed to start Zigbee tr-064.0 2021-03-24 15:06:44.126 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:06:44.009 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:43.953 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:43.893 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G tr-064.0 2021-03-24 15:06:32.107 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques tr-064.0 2021-03-24 15:06:30.940 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:06:30.796 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:30.738 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:30.645 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G tr-064.0 2021-03-24 15:06:18.634 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques tr-064.0 2021-03-24 15:06:17.453 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:06:17.329 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:17.271 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:15.088 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G tr-064.0 2021-03-24 15:06:03.278 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques tr-064.0 2021-03-24 15:06:02.148 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:06:02.028 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:01.956 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:06:01.899 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G tr-064.0 2021-03-24 15:05:49.821 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques tr-064.0 2021-03-24 15:05:48.608 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:05:48.496 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:05:48.437 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:05:48.387 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G tr-064.0 2021-03-24 15:05:36.293 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 40(WLAN-Repeater-Spielezimmer/E8:DE:27:C8:F6:00) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionReques zigbee.0 2021-03-24 15:05:36.204 info (3691) Installed Version: ioBroker/ioBroker.zigbee#master zigbee.0 2021-03-24 15:05:35.825 info (3691) Starting Zigbee npm ... zigbee.0 2021-03-24 15:05:35.681 info (3691) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.20.1, js-controller: 3.2.16 tr-064.0 2021-03-24 15:05:34.282 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 25(Petras-Tablet/3E:8B:0D:90:45:96) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error actio tr-064.0 2021-03-24 15:05:34.148 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 23(LED-Schrank2/60:01:94:A2:E4:1F) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:05:34.082 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 22(LED-Schrank1/60:01:94:AA:60:7C) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action tr-064.0 2021-03-24 15:05:34.009 info (17055) forEachConfiguredDevice: in GetSpecificHostEntry 21(LED-Balkon/DC:4F:22:C2:87:14) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=G host.raspberrypi 2021-03-24 15:05:31.932 info instance system.adapter.zigbee.0 started with pid 3691 host.raspberrypi 2021-03-24 15:05:31.843 info "system.adapter.zigbee.0" enabledAufgrund der Meldungen in Zeile 50 habe ich mal die ID um eins erhöht von 6754 auf 6755. Daraufhin lässt sich der Adapter wieder starten und ich konnte auch wieder einen Teilnehmer verbinden. Hoffe das es jetzt läuft und keine weiteren Probleme auftauchen. Solltet Ihr etwas finden was ich verkehrt gemacht habe könnt Ihr mir das gerne mitteilen.
-
@massenbach na ja alle Geräte die du vorher im Netz hattest sind durch die PANID wechsel wech
-
Hallo zusammen
Ich wollte mal den Zigbee Adapter löschen und alles neu anlernen.
Ich habe im iobroker den Adapter gelöscht und folgende Dateien:zigbee-herdsman
zigbee-herdsman-converters
iobroker.zigbeeNun wen ich den Adapter von Github neu installiere werden die alle Geräte wieder angezeigt.
Den Zigbee Stick habe ich auch schon Hard resetet nach neu start des Adapter sind wieder alle Geräte da.
Wie muss ich vorgehen? Und was empfehlt ihr mich und alle Geräte ordentlich anzulernen, zuerst alles Plugs, Lampen usw.,was muss ich weiteres noch beachten? Wen ich jetzt schon alle Geräte neu anlerne, möchte ich dieses mal alles richtig machen -
- adapter anhalten
- Datei /opt/iobroker/iobroker-data/zigbee_0/shepherd.db löschen
- adapter neu starten
- als erstes die Router (fest am Strom hängenden Geräte anlernen, dann die anderen
A.
-
Hallo @arteck und @Asgothian ,
ich hätte da mal wieder ein erneutes Gerät was noch nicht vom Adapter unterstützt wird. Es handelt sich dabei um den Danfoss Icon Hauptregler 24V OTA für Fußbodenheizungen in kombination mit deren Zigbee Modul. Der Regler steuert Stellantriebe für die Heizungsventile an, welcher den Sollwert über Raumthermostate via Funk oder Power Line Communication übermittelt bekommt. Nachfolgend ein Bild:
Soweit ich weiß können bislang auch nur Danfoss und Somfy Gateways mit dem Gerät vernünftig kommunizieren. Spielt zwar keine Rolle aber naja
Außerdem hier auch nochmal die Geräteinformationen vom unbekannten Zigbee Teilnehmer.
und auch die erweiterten Informationen.
Abschließend auch nochmal von mir ein großes Lob für eure tolle Arbeit, ihr macht einen super Job. Macht weiter so. Vielen Dank schonmal vorab für die Integration. Wenn ich noch etwas vergessen habe oder ihr noch mehr informationen braucht dann besorge ich euch die auch noch gerne.
-
@asgothian
Ist es möglich wen ich die Geräte in dieser Reihenfolge anlerne , das netz sich anders aufbaut als ich bis jetzt gehabt habe, oder wird es später genau gleich aussehen? -
@locito09
Auf lange Sicht wird es genau so sein wie es jetzt ist, es sei denn du positionierst dinge um.A.
-
@asgothian Moin, das System läuft wieder, jetzt auf Zigbee Kanal 15. Die Probleme weswegen der Adapter abgestürzt war sind wohl auf fehlerhaftes pairen von TS0503B-Geräten zurückzuführen, allerdings erst wenn sie angesteuert wurden. Nachdem ich dann wieder mal die PanID erhöht hatte, konnte ich erst einmal alle TS0503B zum laufen bringen und dann den gesamten Rest, gesamt jetzt 55 Teilnehmer. Aber leider habe ich noch immer Probleme mit der Erreichbarkeit, habe jetzt herausgefunden das es sich durchweg um Osram Smart+ Leuchtmittel und Steckdosen handelt die sich immer wieder für mehrere Minuten abmelden. Versuche da gerade ein System zu ermitteln. Möchte mich schon mal für die Hilfe von Dir und @BananaJoe bedanken.
-
@frankthegreat bin mir noch nicht so sicher...hab mir noch ne Mi-Steckdose mit Strommessfunktion dazu gekauft bei Amazon. Habe ne FBH, die stört, wenn sie läuft, ganz schön die Signale (Wohnung hat 2 Etagen).
In den Jahren wo ich den Adapter jetzt nutze hab ich für mich auf jeden Fall herausgefunden, dass die Osram-Teile - egal ob Leuchtmittel, STeckdose oder Stripe - ne miese Funkqualität haben...die werd ich nach und nach rausschmeißen.
Die MI Steckdose funktioniert top. Hätte ich das vorher gewusst, hätte ich die IKEA Repeater nicht gekauft. Mit den Repeatern verbindet sich fast kein Gerät, mit der MI Steckdose jedoch einige auf Anhieb.
Und: auch wenn mein STripe nur 2% WLAN-Verbindung anzeigt, kann ich ihn trotzdem problemlos steuern, daher traue ich der Anzeige nicht so recht...
-
@kueppert Ok, danke für die Info. Die Mi Plug hatte ich noch nicht aufm Schirm. Kommt schonmal in die engere Auswahl.
Hab heute früh ein 4-er Pack Ledvance (ja ich weis...is eigentlich Osram
) bei der Amazone geordert. Bei 8 Euronen das Stück konnte ich nicht widerstehen 
Vor allen Dingen gehen die beim ersten Anzeichen von Rumgezicke auch wieder ohne schlechtes Gewissen zurück
-
Bin durch Zufall auf folgendes github issue gestoßen. Vielleicht macht das die Implementierung in den Zigbee adapter einfacher.
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4273
Würde mich über Feedback freuen ob das euch weiterhilft oder nicht.
closed Danfoss icon master controller with zigbee modul #4273
-
So habe Heute meinen cc1352p-2 (das ding eine einen super empfang auch ohne Antenne) erhalten und sofort an die Arbeit.
Adapter komplett gelöscht und alle Geräte neu angelernt.
Zuerst Router/Geräte am Strom danach die Batterie betriebenen.
In der Hoffnung das die Netzwerkkarte schöner aussieht, wie bei @ilovegym aber leider bekomme ich das nicht hin.Bei mir hängen 13 Geräte in der Luft, habe die auch versucht zu Löschen und nochmals anlernen ,aber die Dinger bleiben immer noch in der Luft.
@ilovegym
Wie hast du das geschafft? hast du die Netzwerkkarte mit Photoshop gezeichnet?
-
@locito09 mal dir paar linien dazu.... wenn die Geräte gehen ... ist die Karte egal
-
@locito09 ist bei mir nicht anders, auch nachdem ich das zigbee neu gemacht habe. Solange alles funktioniert, ist das egal
-
@locito09 sieht bei mir seit Jahren so aus...lüpp aber. Hätte auch gern nur fürs Auge ne schöne Karte, aber die Funktion stört das ganze nicht
