Deconz Adapter stürzt auf Tastendruck ab
-
Hallo zusammen,
bei mir stürzt seit neustem immer der Deconz Adapter ab und ich kann mit der Fehlermeldung nichts anfangen. Ich drücke einen Taster und dann stürzt sofort der Adapter ab. Alles andere funktioniert weiterhin gut.
Raspberry pi 4
Node.js v16.18.1
Adapter: deconz v2.0.5Conbee II
Software 2.12.06 / 19.8.2021
Firmware 26720700Versteht jemand das Problem bzw. wo ich suchen kann?
Danke und Gruß!
Hier ein Auszug aus einer Logdatei:
2022-11-18 18:28:14.998 - info: deconz.0 (3717) State value to set for "deconz.0.groups.24.xy" has to be type "string" but received type "object" 2022-11-18 18:28:15.013 - info: deconz.0 (3717) State value to set for "deconz.0.groups.4545.xy" has to be type "string" but received type "object" 2022-11-18 18:28:15.099 - info: deconz.0 (3717) State value to set for "deconz.0.groups.6661.xy" has to be type "string" but received type "object" 2022-11-18 18:28:15.143 - info: deconz.0 (3717) State value to set for "deconz.0.groups.14083.xy" has to be type "string" but received type "object" 2022-11-18 18:28:20.974 - warn: deconz.0 (3717) {"address":"/lights/12/state","description":"resource, /lights/12/state, is not modifiable. Device is not reachable.","type":202} 2022-11-18 18:28:22.307 - warn: deconz.0 (3717) Object of state "deconz.0.info.connection" is missing the required property "common.type" 2022-11-18 18:28:22.313 - warn: deconz.0 (3717) Object of state "deconz.0.info.connection" is missing the required property "common.type" 2022-11-18 18:28:25.576 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:25.576 - error: deconz.0 (3717) unhandled promise rejection: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.583 - error: deconz.0 (3717) TypeError: Cannot read properties of undefined (reading 'id') at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) at runNextTicks (node:internal/process/task_queues:61:5) at processImmediate (node:internal/timers:437:9) at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:25.583 - error: deconz.0 (3717) Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.673 - info: deconz.0 (3717) cleaned everything up... 2022-11-18 18:28:25.673 - info: deconz.0 (3717) terminating 2022-11-18 18:28:25.675 - warn: deconz.0 (3717) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-11-18 18:28:25.698 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:25.699 - error: deconz.0 (3717) unhandled promise rejection: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.700 - error: deconz.0 (3717) TypeError: Cannot read properties of undefined (reading 'id') at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) at runNextTicks (node:internal/process/task_queues:61:5) at processImmediate (node:internal/timers:437:9) at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:25.700 - error: deconz.0 (3717) Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.725 - warn: deconz.0 (3717) Object of state "deconz.0.info.connection" is missing the required property "common.type" 2022-11-18 18:28:25.746 - warn: javascript.0 (12261) script.js.98_IoBroker.01_Instanzen_Neustarten.Deconz: Deconz ausgefallen. 2022-11-18 18:28:26.105 - info: deconz.0 (3717) State value to set for "deconz.0.lights.0017880106a1e66c.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.122 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00212effff009cac.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.126 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00178801064ffc8b.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.134 - info: deconz.0 (3717) State value to set for "deconz.0.lights.0017880106a1e66c.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.174 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00212effff009cac.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.175 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00178801064ffc8b.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.190 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:26.191 - error: deconz.0 (3717) unhandled promise rejection: DB closed 2022-11-18 18:28:26.193 - error: deconz.0 (3717) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at TCP. (node:net:301:12) 2022-11-18 18:28:26.193 - error: deconz.0 (3717) DB closed 2022-11-18 18:28:26.204 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:26.204 - error: deconz.0 (3717) unhandled promise rejection: DB closed 2022-11-18 18:28:26.205 - error: deconz.0 (3717) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at TCP. (node:net:301:12) 2022-11-18 18:28:26.205 - error: deconz.0 (3717) DB closed 2022-11-18 18:28:26.207 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:26.208 - error: deconz.0 (3717) unhandled promise rejection: DB closed 2022-11-18 18:28:26.209 - error: deconz.0 (3717) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at TCP. (node:net:301:12) 2022-11-18 18:28:26.209 - error: deconz.0 (3717) DB closed 2022-11-18 18:28:26.216 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.219 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.223 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.228 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.228 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.232 - warn: deconz.0 (3717) Could not perform strict object check of state deconz.0.groups.4.sat: DB closed 2022-11-18 18:28:26.233 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.236 - warn: deconz.0 (3717) Could not perform strict object check of state deconz.0.groups.5.sat: DB closed 2022-11-18 18:28:26.236 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.237 - warn: deconz.0 (3717) Could not perform strict object check of state deconz.0.groups.2.sat: DB closed 2022-11-18 18:28:26.237 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.305 - warn: javascript.0 (12261) script.js.98_IoBroker.01_Instanzen_Neustarten.Deconz: Deconz ausgefallen. 2022-11-18 18:28:26.331 - error: host.phoscon 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: 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:61:5) 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at processImmediate (node:internal/timers:437:9) 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[2]: 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: 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at runNextTicks (node:internal/process/task_queues:61:5) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at processImmediate (node:internal/timers:437:9) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[4]: 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: 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: Error: DB closed 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Object.onceWrapper (node:events:628:26) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Socket.emit (node:events:513:28) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Socket.emit (node:domain:489:12) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[5]: at TCP. (node:net:301:12) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[6]: 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: 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: Error: DB closed 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at Object.onceWrapper (node:events:628:26) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at Socket.emit (node:events:513:28) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[7]: at Socket.emit (node:domain:489:12) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[7]: at TCP. (node:net:301:12) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[8]: 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: 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: Error: DB closed 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: at Object.onceWrapper (node:events:628:26) 2022-11-18 18:28:26.337 - error: host.phoscon Caught by controller[9]: at Socket.emit (node:events:513:28) 2022-11-18 18:28:26.337 - error: host.phoscon Caught by controller[9]: at Socket.emit (node:domain:489:12) 2022-11-18 18:28:26.337 - error: host.phoscon Caught by controller[9]: at TCP. (node:net:301:12) 2022-11-18 18:28:26.337 - error: host.phoscon instance system.adapter.deconz.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-11-18 18:28:26.337 - info: host.phoscon Restart adapter system.adapter.deconz.0 because enabled 2022-11-18 18:28:26.338 - warn: host.phoscon Do not restart adapter system.adapter.deconz.0 because restart loop detected@nas007 ich würde an deiner Stelle das System auf Vordermann bringen. ConBee auf 2.19.01
Dann Firmware https://phoscon.de/de/support#update-firmware-conbee2-raspbee2
Grüße -
@nas007 ich würde an deiner Stelle das System auf Vordermann bringen. ConBee auf 2.19.01
Dann Firmware https://phoscon.de/de/support#update-firmware-conbee2-raspbee2
Grüße@fa-bio Auf die aktuelle Software Version bin ich auch schon mal gegangen. Dann ging irgendwie nichts mehr. Ich habe da auch in der Phoscon App einzelne Reiter nicht mehr öffnen könne. Darum wollte ich das erstmal so belassen.
Das muss ja einen Grund haben, warum der bei dem einen Tastendruck immer abstürzt.
-
Hallo zusammen,
bei mir stürzt seit neustem immer der Deconz Adapter ab und ich kann mit der Fehlermeldung nichts anfangen. Ich drücke einen Taster und dann stürzt sofort der Adapter ab. Alles andere funktioniert weiterhin gut.
Raspberry pi 4
Node.js v16.18.1
Adapter: deconz v2.0.5Conbee II
Software 2.12.06 / 19.8.2021
Firmware 26720700Versteht jemand das Problem bzw. wo ich suchen kann?
Danke und Gruß!
Hier ein Auszug aus einer Logdatei:
2022-11-18 18:28:14.998 - info: deconz.0 (3717) State value to set for "deconz.0.groups.24.xy" has to be type "string" but received type "object" 2022-11-18 18:28:15.013 - info: deconz.0 (3717) State value to set for "deconz.0.groups.4545.xy" has to be type "string" but received type "object" 2022-11-18 18:28:15.099 - info: deconz.0 (3717) State value to set for "deconz.0.groups.6661.xy" has to be type "string" but received type "object" 2022-11-18 18:28:15.143 - info: deconz.0 (3717) State value to set for "deconz.0.groups.14083.xy" has to be type "string" but received type "object" 2022-11-18 18:28:20.974 - warn: deconz.0 (3717) {"address":"/lights/12/state","description":"resource, /lights/12/state, is not modifiable. Device is not reachable.","type":202} 2022-11-18 18:28:22.307 - warn: deconz.0 (3717) Object of state "deconz.0.info.connection" is missing the required property "common.type" 2022-11-18 18:28:22.313 - warn: deconz.0 (3717) Object of state "deconz.0.info.connection" is missing the required property "common.type" 2022-11-18 18:28:25.576 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:25.576 - error: deconz.0 (3717) unhandled promise rejection: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.583 - error: deconz.0 (3717) TypeError: Cannot read properties of undefined (reading 'id') at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) at runNextTicks (node:internal/process/task_queues:61:5) at processImmediate (node:internal/timers:437:9) at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:25.583 - error: deconz.0 (3717) Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.673 - info: deconz.0 (3717) cleaned everything up... 2022-11-18 18:28:25.673 - info: deconz.0 (3717) terminating 2022-11-18 18:28:25.675 - warn: deconz.0 (3717) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-11-18 18:28:25.698 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:25.699 - error: deconz.0 (3717) unhandled promise rejection: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.700 - error: deconz.0 (3717) TypeError: Cannot read properties of undefined (reading 'id') at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) at runNextTicks (node:internal/process/task_queues:61:5) at processImmediate (node:internal/timers:437:9) at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:25.700 - error: deconz.0 (3717) Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.725 - warn: deconz.0 (3717) Object of state "deconz.0.info.connection" is missing the required property "common.type" 2022-11-18 18:28:25.746 - warn: javascript.0 (12261) script.js.98_IoBroker.01_Instanzen_Neustarten.Deconz: Deconz ausgefallen. 2022-11-18 18:28:26.105 - info: deconz.0 (3717) State value to set for "deconz.0.lights.0017880106a1e66c.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.122 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00212effff009cac.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.126 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00178801064ffc8b.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.134 - info: deconz.0 (3717) State value to set for "deconz.0.lights.0017880106a1e66c.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.174 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00212effff009cac.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.175 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00178801064ffc8b.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.190 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:26.191 - error: deconz.0 (3717) unhandled promise rejection: DB closed 2022-11-18 18:28:26.193 - error: deconz.0 (3717) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at TCP. (node:net:301:12) 2022-11-18 18:28:26.193 - error: deconz.0 (3717) DB closed 2022-11-18 18:28:26.204 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:26.204 - error: deconz.0 (3717) unhandled promise rejection: DB closed 2022-11-18 18:28:26.205 - error: deconz.0 (3717) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at TCP. (node:net:301:12) 2022-11-18 18:28:26.205 - error: deconz.0 (3717) DB closed 2022-11-18 18:28:26.207 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:26.208 - error: deconz.0 (3717) unhandled promise rejection: DB closed 2022-11-18 18:28:26.209 - error: deconz.0 (3717) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at TCP. (node:net:301:12) 2022-11-18 18:28:26.209 - error: deconz.0 (3717) DB closed 2022-11-18 18:28:26.216 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.219 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.223 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.228 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.228 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.232 - warn: deconz.0 (3717) Could not perform strict object check of state deconz.0.groups.4.sat: DB closed 2022-11-18 18:28:26.233 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.236 - warn: deconz.0 (3717) Could not perform strict object check of state deconz.0.groups.5.sat: DB closed 2022-11-18 18:28:26.236 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.237 - warn: deconz.0 (3717) Could not perform strict object check of state deconz.0.groups.2.sat: DB closed 2022-11-18 18:28:26.237 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.305 - warn: javascript.0 (12261) script.js.98_IoBroker.01_Instanzen_Neustarten.Deconz: Deconz ausgefallen. 2022-11-18 18:28:26.331 - error: host.phoscon 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: 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:61:5) 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at processImmediate (node:internal/timers:437:9) 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[2]: 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: 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at runNextTicks (node:internal/process/task_queues:61:5) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at processImmediate (node:internal/timers:437:9) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[4]: 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: 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: Error: DB closed 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Object.onceWrapper (node:events:628:26) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Socket.emit (node:events:513:28) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Socket.emit (node:domain:489:12) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[5]: at TCP. (node:net:301:12) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[6]: 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: 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: Error: DB closed 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at Object.onceWrapper (node:events:628:26) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at Socket.emit (node:events:513:28) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[7]: at Socket.emit (node:domain:489:12) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[7]: at TCP. (node:net:301:12) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[8]: 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: 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: Error: DB closed 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: at Object.onceWrapper (node:events:628:26) 2022-11-18 18:28:26.337 - error: host.phoscon Caught by controller[9]: at Socket.emit (node:events:513:28) 2022-11-18 18:28:26.337 - error: host.phoscon Caught by controller[9]: at Socket.emit (node:domain:489:12) 2022-11-18 18:28:26.337 - error: host.phoscon Caught by controller[9]: at TCP. (node:net:301:12) 2022-11-18 18:28:26.337 - error: host.phoscon instance system.adapter.deconz.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-11-18 18:28:26.337 - info: host.phoscon Restart adapter system.adapter.deconz.0 because enabled 2022-11-18 18:28:26.338 - warn: host.phoscon Do not restart adapter system.adapter.deconz.0 because restart loop detected@nas007 sagte in Deconz Adapter stürzt auf Tastendruck ab:
Adapter: deconz v2.0.5
Das musste irgendwann passieren. Die 2.0.5 ist mittlerweile 2 Jahre alt und wird nicht weiterentwickelt und bekommt auch keine Fixes mehr.
So leid es mir tut du musst auf die 1.3.21 wechseln. -
@fa-bio Auf die aktuelle Software Version bin ich auch schon mal gegangen. Dann ging irgendwie nichts mehr. Ich habe da auch in der Phoscon App einzelne Reiter nicht mehr öffnen könne. Darum wollte ich das erstmal so belassen.
Das muss ja einen Grund haben, warum der bei dem einen Tastendruck immer abstürzt.
-
@nas007 fa-bio meint, mal die Firmware des Sticks und die Phoscon-Soft auf denneusten Stand zu bringen, vom Deconz-Adapter hat er nicht gesprochen
Aber der läuft dennoch sehr gut! -
@fa-bio Auf die aktuelle Software Version bin ich auch schon mal gegangen. Dann ging irgendwie nichts mehr. Ich habe da auch in der Phoscon App einzelne Reiter nicht mehr öffnen könne. Darum wollte ich das erstmal so belassen.
Das muss ja einen Grund haben, warum der bei dem einen Tastendruck immer abstürzt.
-
Hallo zusammen,
bei mir stürzt seit neustem immer der Deconz Adapter ab und ich kann mit der Fehlermeldung nichts anfangen. Ich drücke einen Taster und dann stürzt sofort der Adapter ab. Alles andere funktioniert weiterhin gut.
Raspberry pi 4
Node.js v16.18.1
Adapter: deconz v2.0.5Conbee II
Software 2.12.06 / 19.8.2021
Firmware 26720700Versteht jemand das Problem bzw. wo ich suchen kann?
Danke und Gruß!
Hier ein Auszug aus einer Logdatei:
2022-11-18 18:28:14.998 - info: deconz.0 (3717) State value to set for "deconz.0.groups.24.xy" has to be type "string" but received type "object" 2022-11-18 18:28:15.013 - info: deconz.0 (3717) State value to set for "deconz.0.groups.4545.xy" has to be type "string" but received type "object" 2022-11-18 18:28:15.099 - info: deconz.0 (3717) State value to set for "deconz.0.groups.6661.xy" has to be type "string" but received type "object" 2022-11-18 18:28:15.143 - info: deconz.0 (3717) State value to set for "deconz.0.groups.14083.xy" has to be type "string" but received type "object" 2022-11-18 18:28:20.974 - warn: deconz.0 (3717) {"address":"/lights/12/state","description":"resource, /lights/12/state, is not modifiable. Device is not reachable.","type":202} 2022-11-18 18:28:22.307 - warn: deconz.0 (3717) Object of state "deconz.0.info.connection" is missing the required property "common.type" 2022-11-18 18:28:22.313 - warn: deconz.0 (3717) Object of state "deconz.0.info.connection" is missing the required property "common.type" 2022-11-18 18:28:25.576 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:25.576 - error: deconz.0 (3717) unhandled promise rejection: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.583 - error: deconz.0 (3717) TypeError: Cannot read properties of undefined (reading 'id') at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) at runNextTicks (node:internal/process/task_queues:61:5) at processImmediate (node:internal/timers:437:9) at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:25.583 - error: deconz.0 (3717) Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.673 - info: deconz.0 (3717) cleaned everything up... 2022-11-18 18:28:25.673 - info: deconz.0 (3717) terminating 2022-11-18 18:28:25.675 - warn: deconz.0 (3717) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-11-18 18:28:25.698 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:25.699 - error: deconz.0 (3717) unhandled promise rejection: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.700 - error: deconz.0 (3717) TypeError: Cannot read properties of undefined (reading 'id') at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) at runNextTicks (node:internal/process/task_queues:61:5) at processImmediate (node:internal/timers:437:9) at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:25.700 - error: deconz.0 (3717) Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:25.725 - warn: deconz.0 (3717) Object of state "deconz.0.info.connection" is missing the required property "common.type" 2022-11-18 18:28:25.746 - warn: javascript.0 (12261) script.js.98_IoBroker.01_Instanzen_Neustarten.Deconz: Deconz ausgefallen. 2022-11-18 18:28:26.105 - info: deconz.0 (3717) State value to set for "deconz.0.lights.0017880106a1e66c.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.122 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00212effff009cac.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.126 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00178801064ffc8b.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.134 - info: deconz.0 (3717) State value to set for "deconz.0.lights.0017880106a1e66c.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.174 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00212effff009cac.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.175 - info: deconz.0 (3717) State value to set for "deconz.0.lights.00178801064ffc8b.xy" has to be type "string" but received type "object" 2022-11-18 18:28:26.190 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:26.191 - error: deconz.0 (3717) unhandled promise rejection: DB closed 2022-11-18 18:28:26.193 - error: deconz.0 (3717) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at TCP. (node:net:301:12) 2022-11-18 18:28:26.193 - error: deconz.0 (3717) DB closed 2022-11-18 18:28:26.204 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:26.204 - error: deconz.0 (3717) unhandled promise rejection: DB closed 2022-11-18 18:28:26.205 - error: deconz.0 (3717) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at TCP. (node:net:301:12) 2022-11-18 18:28:26.205 - error: deconz.0 (3717) DB closed 2022-11-18 18:28:26.207 - error: deconz.0 (3717) 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(). 2022-11-18 18:28:26.208 - error: deconz.0 (3717) unhandled promise rejection: DB closed 2022-11-18 18:28:26.209 - error: deconz.0 (3717) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at TCP. (node:net:301:12) 2022-11-18 18:28:26.209 - error: deconz.0 (3717) DB closed 2022-11-18 18:28:26.216 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.219 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.223 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.228 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.228 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.232 - warn: deconz.0 (3717) Could not perform strict object check of state deconz.0.groups.4.sat: DB closed 2022-11-18 18:28:26.233 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.236 - warn: deconz.0 (3717) Could not perform strict object check of state deconz.0.groups.5.sat: DB closed 2022-11-18 18:28:26.236 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.237 - warn: deconz.0 (3717) Could not perform strict object check of state deconz.0.groups.2.sat: DB closed 2022-11-18 18:28:26.237 - warn: deconz.0 (3717) get state error: Connection is closed. 2022-11-18 18:28:26.305 - warn: javascript.0 (12261) script.js.98_IoBroker.01_Instanzen_Neustarten.Deconz: Deconz ausgefallen. 2022-11-18 18:28:26.331 - error: host.phoscon 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: 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:61:5) 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at processImmediate (node:internal/timers:437:9) 2022-11-18 18:28:26.332 - error: host.phoscon Caught by controller[1]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[2]: 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: 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'id') 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at runNextTicks (node:internal/process/task_queues:61:5) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at processImmediate (node:internal/timers:437:9) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[3]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13) 2022-11-18 18:28:26.333 - error: host.phoscon Caught by controller[4]: 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: 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: Error: DB closed 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Object.onceWrapper (node:events:628:26) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Socket.emit (node:events:513:28) 2022-11-18 18:28:26.334 - error: host.phoscon Caught by controller[5]: at Socket.emit (node:domain:489:12) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[5]: at TCP. (node:net:301:12) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[6]: 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: 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: Error: DB closed 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at Object.onceWrapper (node:events:628:26) 2022-11-18 18:28:26.335 - error: host.phoscon Caught by controller[7]: at Socket.emit (node:events:513:28) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[7]: at Socket.emit (node:domain:489:12) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[7]: at TCP. (node:net:301:12) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[8]: 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: 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: Error: DB closed 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-11-18 18:28:26.336 - error: host.phoscon Caught by controller[9]: at Object.onceWrapper (node:events:628:26) 2022-11-18 18:28:26.337 - error: host.phoscon Caught by controller[9]: at Socket.emit (node:events:513:28) 2022-11-18 18:28:26.337 - error: host.phoscon Caught by controller[9]: at Socket.emit (node:domain:489:12) 2022-11-18 18:28:26.337 - error: host.phoscon Caught by controller[9]: at TCP. (node:net:301:12) 2022-11-18 18:28:26.337 - error: host.phoscon instance system.adapter.deconz.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-11-18 18:28:26.337 - info: host.phoscon Restart adapter system.adapter.deconz.0 because enabled 2022-11-18 18:28:26.338 - warn: host.phoscon Do not restart adapter system.adapter.deconz.0 because restart loop detected@nas007 sagte in Deconz Adapter stürzt auf Tastendruck ab:
Ich drücke einen Taster und dann stürzt sofort der Adapter ab
Da steht doch die Lösung im Log schon drin...
Der XY Parameter ist zur CIE Farb-Steuerung da und erwartet einen String der wie ein Array aussieht.
Gibst du ihm ein Objekt in Form eines Arrays kann der Datenpunkt damit nichts anfangen.
Also... Was wirft der Taster da in den DeConz Datenpunkt rein?...
EDIT: Hat auch nichts mit der Version des DeConz zu tun. Das war schon immer so...
Arbeitet da ein Blockly oder ein JS-Script am Taster, dann entweder das Array [x,y] in String umwandeln oder kurz posten.
-
@guergen Ja, das ist irgendwie komisch. Ich hätte es dann irgendwie bei mehr Schalter erwartet.
@fa-bio Das würde ich mal machen. Muss ich danach alles wieder koppeln? Würde vorher das angebotene Backup von Phoscon machen.
@Armilar Der Taster schickt nichts raus. Wenn der gedrückt ist, dann habe ich in Blockly es so geregelt, dass den pi-Hole deaktiviert wird. Die ganze Kommunikation läuft halt über Deconz, aber damit habe ich nichts zu tun (ich schaue mir nur den Datenpunkt des Tasters in iobroker an).
-
@guergen Ja, das ist irgendwie komisch. Ich hätte es dann irgendwie bei mehr Schalter erwartet.
@fa-bio Das würde ich mal machen. Muss ich danach alles wieder koppeln? Würde vorher das angebotene Backup von Phoscon machen.
@Armilar Der Taster schickt nichts raus. Wenn der gedrückt ist, dann habe ich in Blockly es so geregelt, dass den pi-Hole deaktiviert wird. Die ganze Kommunikation läuft halt über Deconz, aber damit habe ich nichts zu tun (ich schaue mir nur den Datenpunkt des Tasters in iobroker an).
@nas007 als erstes machst du bitte ein Backup in der Phoscon App, dann eine vom ioBroker über BackitUp
Dann aktualisiert du zuerst die Firmware von Phoscon danach machst du einen Neustart über die Phoscon Oberfläche.
Wenn alles glatt läuft verbinden sich fast alle Gerät von alleine. Danach wieder ein Backup in der Phoscon App.Wenn alles geklappt hat, aktualisiert du dann auf die 2.19.01 danach wieder einen Neustart und schauen ob alle Geräte online gehen das kann auch mal paar Minuten dauern.
Achtung: Falls sich einzelne Geräte nicht verbinden, auf keinen Fall löschen sondern versetze die Geräte in den Anlernmodus und dann Sensoren oder Lichter oder Schalter anlernen halt was du gerade brauchst.*
Wichtig zum Schluß auf jeden Fall den Deconz Adapter von @Jey-Cee aktualisieren.
Wenn du das alles gemacht hast hast du ein solides Fundament wo wir dann drauf aufbauen und nach den Fehler forschen können falls er noch da ist.
Mach alles mit Ruhe und nicht zwischendurch. Viel Erfolg.Grüße
FabioPS. Um welchen Taster handelt es sich?
-
@nas007 als erstes machst du bitte ein Backup in der Phoscon App, dann eine vom ioBroker über BackitUp
Dann aktualisiert du zuerst die Firmware von Phoscon danach machst du einen Neustart über die Phoscon Oberfläche.
Wenn alles glatt läuft verbinden sich fast alle Gerät von alleine. Danach wieder ein Backup in der Phoscon App.Wenn alles geklappt hat, aktualisiert du dann auf die 2.19.01 danach wieder einen Neustart und schauen ob alle Geräte online gehen das kann auch mal paar Minuten dauern.
Achtung: Falls sich einzelne Geräte nicht verbinden, auf keinen Fall löschen sondern versetze die Geräte in den Anlernmodus und dann Sensoren oder Lichter oder Schalter anlernen halt was du gerade brauchst.*
Wichtig zum Schluß auf jeden Fall den Deconz Adapter von @Jey-Cee aktualisieren.
Wenn du das alles gemacht hast hast du ein solides Fundament wo wir dann drauf aufbauen und nach den Fehler forschen können falls er noch da ist.
Mach alles mit Ruhe und nicht zwischendurch. Viel Erfolg.Grüße
FabioPS. Um welchen Taster handelt es sich?
@fa-bio Alles klar! Vielen Dank für deine ausführliche Anleitung! Es ist ein Schalter von Ikea, hab davon noch weitere und finde die aufgrund ihrer Größe sehr ansprechend.
An die anderen auch vielen Dank!
Ich werde dann die Tage mein Glück versuchen :) schönes Wochenende!
-
@fa-bio Alles klar! Vielen Dank für deine ausführliche Anleitung! Es ist ein Schalter von Ikea, hab davon noch weitere und finde die aufgrund ihrer Größe sehr ansprechend.
An die anderen auch vielen Dank!
Ich werde dann die Tage mein Glück versuchen :) schönes Wochenende!
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 Anmelden596
Online32.9k
Benutzer83.0k
Themen1.3m
Beiträge