UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[DerRoch]

Hallo,

ich habe gestern Abend festgestellt, das die SD-Karte meines OrangePi scheinbar "gestorben" ist.
Der OrangePi Zero ist nur die Slaveinstanz an dem ein Conbee2 angeschlossen ist für meine Zigbee Devices. Hat bisher die letzten vier Monate relativ gut funktioniert (in Betrieb seit September; Seit Oktober mit Conbee2).

Jetzt habe ich eine andere SDKarte eingebaut, Armbian darauf neu installiert, iobroker vom Script neu installiert und neu mit dem Master gekoppelt. Die Neuinstallation hat denselben Hostnamen wie der alte Host.

Zuerst hatte ich das Problem, dass die ZigBee Instanz garnicht auf dem Slave starten wollte. Nach einigen Versuchen scheint es nun zu starten. Zweites Problem war, dass das Update der ZigBee-Instanz von 1.7.5 auf 1.8.10 laut Log klappte, aber effektiv nicht aktualisiert wurde (Updatehinweis bei den Adaptern blieb bestehen und die Version war effektiv noch die alte). Ich habe das auf dem Slave mit "iobroker fix" und "iobroker upgrade" lösen können.

Das Hauptproblem aktuell ist aber, dass ein Steuern oder Abfragen der Geräte nicht möglich ist, die Instanz scheinbar ständig abstürzt. In den Einstellungen wurde auch der Pfad zum USB-Gerät geprüft und neu gesetzt. Im Zuge der Fehlersuche wurde auch der js-controller auf beiden Hosts von 4.0.23 auf 4.0.24 aktualisiert.

Folgendes wirft das Log des ZigBee aktuell aus:

2023-01-07 21:08:06.304  - info: zigbee.0 (1112) Zigbee started
2023-01-07 21:10:15.668  - error: zigbee.0 (1112) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-01-07 21:10:15.676  - error: zigbee.0 (1112) unhandled promise rejection: Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:10:15.691  - error: zigbee.0 (1112) TypeError: Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:10:15.694  - error: zigbee.0 (1112) Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:10:15.724  - info: zigbee.0 (1112) cleaned everything up...
2023-01-07 21:10:15.736  - info: zigbee.0 (1112) Zigbee: disabling joining new devices.
2023-01-07 21:10:16.230  - info: zigbee.0 (1112) terminating
2023-01-07 21:10:16.244  - warn: zigbee.0 (1112) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-01-07 21:11:02.837  - info: zigbee.0 (1134) starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-07 21:11:03.329  - info: zigbee.0 (1134) Starting Zigbee  npm ...
2023-01-07 21:11:05.272  - info: zigbee.0 (1134) Installed Version: iobroker.zigbee@1.8.10
2023-01-07 21:11:05.373  - info: zigbee.0 (1134) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-07 21:11:05.424  - info: zigbee.0 (1134) Unable to disable LED, unsupported function.
2023-01-07 21:11:05.520  - info: zigbee.0 (1134)   --> transmitPower : normal
2023-01-07 21:11:06.170  - info: zigbee.0 (1134) Unable to set transmit power, unsupported function.
2023-01-07 21:11:06.178  - info: zigbee.0 (1134) Currently no devices.
2023-01-07 21:11:06.183  - info: zigbee.0 (1134) Zigbee started
2023-01-07 21:12:39.732  - error: zigbee.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-01-07 21:12:39.735  - error: zigbee.0 (1134) unhandled promise rejection: Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:12:39.745  - error: zigbee.0 (1134) TypeError: Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:12:39.748  - error: zigbee.0 (1134) Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:12:39.774  - info: zigbee.0 (1134) cleaned everything up...
2023-01-07 21:12:39.783  - info: zigbee.0 (1134) Zigbee: disabling joining new devices.
2023-01-07 21:12:40.281  - info: zigbee.0 (1134) terminating
2023-01-07 21:12:40.289  - warn: zigbee.0 (1134) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-01-07 21:13:27.087  - info: zigbee.0 (1154) starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-07 21:13:27.521  - info: zigbee.0 (1154) Starting Zigbee  npm ...
2023-01-07 21:13:29.429  - info: zigbee.0 (1154) Installed Version: iobroker.zigbee@1.8.10
2023-01-07 21:13:29.532  - info: zigbee.0 (1154) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-07 21:13:29.584  - info: zigbee.0 (1154) Unable to disable LED, unsupported function.
2023-01-07 21:13:29.671  - info: zigbee.0 (1154)   --> transmitPower : normal
2023-01-07 21:13:30.273  - info: zigbee.0 (1154) Unable to set transmit power, unsupported function.
2023-01-07 21:13:30.280  - info: zigbee.0 (1154) Currently no devices.
2023-01-07 21:13:30.285  - info: zigbee.0 (1154) Zigbee started
2023-01-07 21:26:36.093  - info: zigbee.0 (1154) Got terminate signal TERMINATE_YOURSELF
2023-01-07 21:26:36.100  - info: zigbee.0 (1154) cleaned everything up...
2023-01-07 21:26:36.111  - info: zigbee.0 (1154) Zigbee: disabling joining new devices.
2023-01-07 21:26:36.309  - info: zigbee.0 (1154) terminating
2023-01-07 21:26:36.316  - info: zigbee.0 (1154) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-07 21:27:37.858  - info: zigbee.0 (1469) starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-07 21:27:38.344  - info: zigbee.0 (1469) Starting Zigbee  npm ...
2023-01-07 21:27:40.332  - info: zigbee.0 (1469) Installed Version: iobroker.zigbee@1.8.10
2023-01-07 21:27:40.478  - info: zigbee.0 (1469) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-07 21:27:40.560  - info: zigbee.0 (1469) Unable to disable LED, unsupported function.
2023-01-07 21:27:40.655  - info: zigbee.0 (1469)   --> transmitPower : normal
2023-01-07 21:27:41.297  - info: zigbee.0 (1469) Unable to set transmit power, unsupported function.
2023-01-07 21:27:41.305  - info: zigbee.0 (1469) Currently no devices.
2023-01-07 21:27:41.311  - info: zigbee.0 (1469) Zigbee started
2023-01-07 21:32:55.481  - info: zigbee.0 (1469) cleaned everything up...
2023-01-07 21:32:55.512  - info: zigbee.0 (1469) Zigbee: disabling joining new devices.
2023-01-07 21:32:55.555  - info: zigbee.0 (1469) Got terminate signal TERMINATE_YOURSELF
2023-01-07 21:32:56.029  - info: zigbee.0 (1469) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-01-07 21:35:45.813  - info: zigbee.0 (2564) starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-07 21:35:46.274  - info: zigbee.0 (2564) delete old Backup files. keep only last 10
2023-01-07 21:35:46.283  - info: zigbee.0 (2564) Starting Zigbee  npm ...
2023-01-07 21:35:48.207  - info: zigbee.0 (2564) Installed Version: iobroker.zigbee@1.8.10
2023-01-07 21:35:48.310  - info: zigbee.0 (2564) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-07 21:35:48.362  - info: zigbee.0 (2564) Unable to disable LED, unsupported function.
2023-01-07 21:35:48.459  - info: zigbee.0 (2564)   --> transmitPower : normal
2023-01-07 21:35:49.125  - info: zigbee.0 (2564) Unable to set transmit power, unsupported function.
2023-01-07 21:35:49.132  - info: zigbee.0 (2564) Currently no devices.
2023-01-07 21:35:49.138  - info: zigbee.0 (2564) Zigbee started
2023-01-07 21:36:07.320  - info: zigbee.0 (2564) Got terminate signal TERMINATE_YOURSELF
2023-01-07 21:36:07.333  - info: zigbee.0 (2564) cleaned everything up...
2023-01-07 21:36:07.346  - info: zigbee.0 (2564) Zigbee: disabling joining new devices.
2023-01-07 21:36:07.558  - info: zigbee.0 (2564) terminating
2023-01-07 21:36:07.566  - info: zigbee.0 (2564) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-07 21:37:39.352  - info: zigbee.0 (2647) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-07 21:37:39.837  - info: zigbee.0 (2647) delete old Backup files. keep only last 10
2023-01-07 21:37:39.846  - info: zigbee.0 (2647) Starting Zigbee  npm ...
2023-01-07 21:38:22.097  - info: zigbee.0 (2647) Installed Version: iobroker.zigbee@1.8.10
2023-01-07 21:38:22.273  - info: zigbee.0 (2647) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-07 21:38:22.341  - info: zigbee.0 (2647) Unable to disable LED, unsupported function.
2023-01-07 21:38:22.428  - info: zigbee.0 (2647)   --> transmitPower : normal
2023-01-07 21:38:23.044  - info: zigbee.0 (2647) Unable to set transmit power, unsupported function.
2023-01-07 21:38:23.052  - info: zigbee.0 (2647) Currently no devices.
2023-01-07 21:38:23.057  - info: zigbee.0 (2647) Zigbee started
2023-01-07 21:38:56.365  - info: zigbee.0 (2647) List of port: [{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyACM0","manufacturer":"dresden elektronik ingenieurtechnik GmbH","serialNumber":"DE2661519","pnpId":"usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2661519-if00","vendorId":"1cf1","productId":"0030"},{"path":"/dev/ttyS0"}]
2023-01-07 21:38:56.543  - info: zigbee.0 (2647) List of port: [{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyACM0","manufacturer":"dresden elektronik ingenieurtechnik GmbH","serialNumber":"DE2661519","pnpId":"usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2661519-if00","vendorId":"1cf1","productId":"0030"},{"path":"/dev/ttyS0"}]
2023-01-07 21:39:07.259  - error: zigbee.0 (2647) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-01-07 21:39:07.261  - error: zigbee.0 (2647) unhandled promise rejection: Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:39:07.270  - error: zigbee.0 (2647) TypeError: Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:39:07.272  - error: zigbee.0 (2647) Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:39:07.304  - info: zigbee.0 (2647) cleaned everything up...
2023-01-07 21:39:07.314  - info: zigbee.0 (2647) Zigbee: disabling joining new devices.
2023-01-07 21:39:09.880  - info: zigbee.0 (2647) terminating
2023-01-07 21:39:09.885  - warn: zigbee.0 (2647) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-01-07 21:39:57.409  - info: zigbee.0 (2687) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-07 21:39:57.899  - info: zigbee.0 (2687) delete old Backup files. keep only last 10
2023-01-07 21:39:57.909  - info: zigbee.0 (2687) Starting Zigbee  npm ...
2023-01-07 21:40:00.269  - warn: zigbee.0 (2687) States system pmessage io.messagebox.system.adapter.zigbee.0 {"command":"setState","message":{"id":"zigbee.0.e0798dfffec6c464.state","val":false},"from":"system.adapter.admin.0","callback":{"message":{"id":"zigbee.0.e0798dfffec6c464.state","val":false},"id":244,"ack":false,"time":1673123999809},"_id":73636325} Cannot read properties of undefined (reading 'setState_typed')
2023-01-07 21:40:01.593  - warn: zigbee.0 (2687) TypeError: Cannot read properties of undefined (reading 'setState_typed')
2023-01-07 21:40:02.550  - info: zigbee.0 (2687) Installed Version: iobroker.zigbee@1.8.10
2023-01-07 21:40:02.558  - warn: zigbee.0 (2687) States system pmessage io.messagebox.system.adapter.zigbee.0 {"command":"setState","message":{"id":"zigbee.0.e0798dfffec6c464.state","val":true},"from":"system.adapter.admin.0","callback":{"message":{"id":"zigbee.0.e0798dfffec6c464.state","val":true},"id":245,"ack":false,"time":1673124001461},"_id":73636326} Cannot read properties of undefined (reading 'setState_typed')
2023-01-07 21:40:02.567  - warn: zigbee.0 (2687) TypeError: Cannot read properties of undefined (reading 'setState_typed')
2023-01-07 21:40:02.667  - info: zigbee.0 (2687) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-07 21:40:02.723  - info: zigbee.0 (2687) Unable to disable LED, unsupported function.
2023-01-07 21:40:02.781  - info: zigbee.0 (2687)   --> transmitPower : normal
2023-01-07 21:40:03.249  - info: zigbee.0 (2687) Unable to set transmit power, unsupported function.
2023-01-07 21:40:03.257  - info: zigbee.0 (2687) Currently no devices.
2023-01-07 21:40:03.261  - info: zigbee.0 (2687) Zigbee started
2023-01-07 21:40:34.325  - info: zigbee.0 (2687) List of port: [{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyACM0","manufacturer":"dresden elektronik ingenieurtechnik GmbH","serialNumber":"DE2661519","pnpId":"usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2661519-if00","vendorId":"1cf1","productId":"0030"},{"path":"/dev/ttyS0"}]
2023-01-07 21:40:43.700  - error: zigbee.0 (2687) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-01-07 21:40:43.702  - error: zigbee.0 (2687) unhandled promise rejection: Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:40:43.705  - error: zigbee.0 (2687) TypeError: Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:40:43.711  - error: zigbee.0 (2687) Cannot read properties of undefined (reading 'mapped')
2023-01-07 21:40:43.785  - info: zigbee.0 (2687) cleaned everything up...
2023-01-07 21:40:43.794  - info: zigbee.0 (2687) Zigbee: disabling joining new devices.
2023-01-07 21:40:45.427  - warn: zigbee.0 (2687) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-01-07 21:41:32.391  - info: zigbee.0 (2722) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-07 21:41:32.821  - info: zigbee.0 (2722) delete old Backup files. keep only last 10
2023-01-07 21:41:32.830  - info: zigbee.0 (2722) Starting Zigbee  npm ...
2023-01-07 21:41:36.036  - info: zigbee.0 (2722) Installed Version: iobroker.zigbee@1.8.10
2023-01-07 21:41:36.208  - info: zigbee.0 (2722) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-07 21:41:36.332  - info: zigbee.0 (2722) Unable to disable LED, unsupported function.
2023-01-07 21:41:36.410  - info: zigbee.0 (2722)   --> transmitPower : normal
2023-01-07 21:41:37.035  - info: zigbee.0 (2722) Unable to set transmit power, unsupported function.
2023-01-07 21:41:37.042  - info: zigbee.0 (2722) Currently no devices.
2023-01-07 21:41:37.048  - info: zigbee.0 (2722) Zigbee started

Hab schon anhand der Fehlermeldungen mein Glück versucht, aber bin bisher nicht weiter gekommen. Würde mich freuen wenn Ihr Tipps, Ideen oder "die Lösung" habt.

Vielen Dank euch schonmal!

Systemdata	Master	Slave
Hardwaresystem:	VM auf einer QNAP	OrangePi Zero
Arbeitsspeicher:	4GB	0.5GB
Festplattenart:	SSD	4GB microSD
Betriebssystem:	Ubuntu 22.04 LTS	Armbian Bullseye 22.11.1
Nodejs-Version:	16.19.0	16.19.0
NPM-Version:	8.19.2	8.19.2
Installationsart:	Skript	Skript

[Thomas Braun]

@derroch sagte in Probleme mit Zigbee auf Slave:

2023-01-07 21:11:02.837  - info: zigbee.0 (1134) starting. Version 1.7.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-07 21:11:03.329  - info: zigbee.0 (1134) Starting Zigbee  npm ...
2023-01-07 21:11:05.272  - info: zigbee.0 (1134) Installed Version: iobroker.zigbee@1.8.10

Das sieht aber irgendwie komisch aus.

iobroker update
cd /opt/iobroker
npm ls

sagt?

[DerRoch]

Hi Thomas,

danke für deine schnelle Rückmeldung. ich hab mir das mal angeschaut und ausgeführt:

@thomas-braun sagte in Probleme mit Zigbee auf Slave:

iobroker update
cd /opt/iobroker
npm ls

sagt?

user@iobroker-orangepi:~$ iobroker update
Used repository: stable
Adapter    "admin"        : 6.3.5    , installed 6.3.5
Adapter    "backitup"     : 2.5.9    , installed 2.5.9
Adapter    "discovery"    : 3.1.0    , installed 3.1.0
Controller "js-controller": 4.0.24   , installed 4.0.24
Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
Adapter    "zigbee"       : 1.8.10   , installed 1.8.10
user@iobroker-orangepi:~$ 
user@iobroker-orangepi:~$ cd /opt/iobroker
user@iobroker-orangepi:/opt/iobroker$ npm ls
[sudo] Passwort für user: 
iobroker.inst@3.0.0 /opt/iobroker
├── iobroker.admin@6.3.5
├── iobroker.backitup@2.5.9
├── iobroker.discovery@3.1.0
├── iobroker.js-controller@4.0.24
├── iobroker.rpi2@1.3.2
└── iobroker.zigbee@1.8.10

das kommt dabei raus (auf dem OrangePi Slave)

das mit den Meldungen und der angezeigten Version 1.7.5 fand ich auch seltsam...

ich hab jetzt mal wieder versucht ein paar Zigbee-Geräte zu schalten und mal ein aktuelles Log erstellt. Hier siehts nun "besser" aus. Das Fehlerbild ist allerdings das selbe.

2023-01-08 10:18:22.245  - info: zigbee.0 (1022) Zigbee started
2023-01-08 19:33:12.127  - info: zigbee.0 (1022) List of port: [{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyACM0","manufacturer":"dresden elektronik ingenieurtechnik GmbH","serialNumber":"DE2661519","pnpId":"usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2661519-if00","vendorId":"1cf1","productId":"0030"},{"path":"/dev/ttyS0"}]
2023-01-08 19:33:21.190  - error: zigbee.0 (1022) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-01-08 19:33:21.195  - error: zigbee.0 (1022) unhandled promise rejection: Cannot read properties of undefined (reading 'mapped')
2023-01-08 19:33:21.203  - error: zigbee.0 (1022) TypeError: Cannot read properties of undefined (reading 'mapped')
2023-01-08 19:33:21.205  - error: zigbee.0 (1022) Cannot read properties of undefined (reading 'mapped')
2023-01-08 19:33:21.230  - info: zigbee.0 (1022) cleaned everything up...
2023-01-08 19:33:21.241  - info: zigbee.0 (1022) Zigbee: disabling joining new devices.
2023-01-08 19:33:22.120  - info: zigbee.0 (1022) terminating
2023-01-08 19:33:22.126  - warn: zigbee.0 (1022) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-01-08 19:34:09.563  - info: zigbee.0 (1232) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-08 19:34:10.009  - info: zigbee.0 (1232) delete old Backup files. keep only last 10
2023-01-08 19:34:10.018  - info: zigbee.0 (1232) Starting Zigbee  npm ...
2023-01-08 19:34:12.964  - info: zigbee.0 (1232) Installed Version: iobroker.zigbee@1.8.10
2023-01-08 19:34:13.126  - info: zigbee.0 (1232) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-08 19:34:13.201  - info: zigbee.0 (1232) Unable to disable LED, unsupported function.
2023-01-08 19:34:13.284  - info: zigbee.0 (1232)   --> transmitPower : normal
2023-01-08 19:34:13.964  - info: zigbee.0 (1232) Unable to set transmit power, unsupported function.
2023-01-08 19:34:13.972  - info: zigbee.0 (1232) Currently no devices.
2023-01-08 19:34:13.977  - info: zigbee.0 (1232) Zigbee started
2023-01-08 19:34:19.440  - error: zigbee.0 (1232) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-01-08 19:34:19.444  - error: zigbee.0 (1232) unhandled promise rejection: Cannot read properties of undefined (reading 'mapped')
2023-01-08 19:34:19.447  - error: zigbee.0 (1232) TypeError: Cannot read properties of undefined (reading 'mapped')
2023-01-08 19:34:19.450  - error: zigbee.0 (1232) Cannot read properties of undefined (reading 'mapped')
2023-01-08 19:34:19.498  - info: zigbee.0 (1232) cleaned everything up...
2023-01-08 19:34:19.505  - info: zigbee.0 (1232) Zigbee: disabling joining new devices.
2023-01-08 19:34:20.314  - info: zigbee.0 (1232) terminating
2023-01-08 19:34:20.321  - warn: zigbee.0 (1232) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-01-08 19:34:21.675  - info: zigbee.0 (1232) terminating with timeout

Was hab ich denn für Möglichkeiten das wieder lauffähig zu bekommen? bis zum ausfall der SD-Card lief es ja eigentlich

Gruß Christian

[Asgothian]

@derroch Zeig mal bitte was als adapter auf dem Master angezeigt wird.

Auch: wie genau hast du das Update der Zigbee-Instanz durchgeführt ?

A.

[DerRoch]

@asgothian sagte in Probleme mit Zigbee auf Slave:

@derroch Zeig mal bitte was als adapter auf dem Master angezeigt wird.

meinst du das hier?

user@iobroker:/opt/iobroker$ npm ls
iobroker.inst@3.0.0 /opt/iobroker
├── iobroker.admin@6.3.5
├── iobroker.alexa2@3.23.2
├── iobroker.backitup@2.5.9
├── iobroker.daswetter@3.1.4
├── iobroker.discovery@3.1.0
├── iobroker.dwd@2.8.3
├── iobroker.firetv@1.0.0
├── iobroker.heatingcontrol@2.9.3
├── iobroker.ical@1.13.2
├── iobroker.influxdb@3.2.0
├── iobroker.info@1.9.19
├── iobroker.iot@1.11.9
├── iobroker.jarvis@3.1.2
├── iobroker.javascript@6.1.4
├── iobroker.js-controller@4.0.24
├── iobroker.net-tools@0.2.0
├── iobroker.opi@0.1.1
├── iobroker.rpi2@1.3.2
├── iobroker.smartcontrol@1.2.1
├── iobroker.trashschedule@2.0.3
├── iobroker.vis-icontwo@0.90.0
├── iobroker.vis-timeandweather@1.2.2
├── iobroker.vis@1.4.15
├── iobroker.web@4.3.0
├── iobroker.whatsapp-cmb@0.2.3
└── iobroker.zigbee@1.8.10

Auch: wie genau hast du das Update der Zigbee-Instanz durchgeführt ?

Ich wollte das Update eigentlich übers Admin-Interface durchführen. Das hab ich 2 mal versucht. Jedesmal war es immer noch Version 1.7.5... dann hab ichs über die CLI auf dem Slave durchgeführt mit "iobroker update/upgrade".

Gruß Christian

[Asgothian]

@derroch hast du die Datei shepherd.db im Verzeichnis /opt/iobroker/iobroker-data/zigbee_0 auf dem Slave von der defekten Karte auf die neue übertragen ?

A.

[DerRoch]

@asgothian sagte in Probleme mit Zigbee auf Slave:

@derroch hast du die Datei shepherd.db im Verzeichnis /opt/iobroker/iobroker-data/zigbee_0 auf dem Slave von der defekten Karte auf die neue übertragen ?

Guten Morgen,

Ne, ist bisher nicht passiert. sollte ich das mal tun? Ist auf Grund der defekten Karte evtl schwierig.
Ach, ich hab ein Backup mit backitup eingerichtet und hier scheint in der Backup-Datei die besagte shepherd.db vorhanden zu sein.

[arteck]

@derroch dann nimm die aus der Sicherung ..egal welche du nimmt.. die wird gebraucht

[DerRoch]

@arteck

Besten dank, das hat super geklappt. iobroker gestoppt, shepherd.db an die angegebene Position kopiert und wieder gestartet. läuft. Geräte lassen sich wieder schalten. oh wunder ;-).
Ich bin irgendwie davon ausgegangen, da die Adapter alle durch den Master gesteuert/übertragen werden, dass das auch für die Datenbank vom Master übertragen wird.

Aber zum Glück gibts Backups und zum Glück hab ichs auch funktionsfähig eingerichtet ;-).

Allerdings hab ich im Log noch ganz viele "spannende" Meldungen die ich euch nicht vorenthalten möchte:

2023-01-09 19:15:27.318  - info: zigbee.0 (4151) cleaned everything up...
2023-01-09 19:15:27.334  - info: zigbee.0 (4151) Zigbee: disabling joining new devices.
2023-01-09 19:15:27.994  - info: zigbee.0 (4151) Got terminate signal TERMINATE_YOURSELF
2023-01-09 19:15:28.065  - info: zigbee.0 (4151) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-01-09 19:18:08.458  - info: zigbee.0 (5024) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-09 19:18:08.905  - info: zigbee.0 (5024) delete old Backup files. keep only last 10
2023-01-09 19:18:08.914  - info: zigbee.0 (5024) Starting Zigbee  npm ...
2023-01-09 19:18:11.901  - info: zigbee.0 (5024) Installed Version: iobroker.zigbee@1.8.10
2023-01-09 19:18:12.060  - info: zigbee.0 (5024) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-09 19:18:12.182  - info: zigbee.0 (5024) Unable to disable LED, unsupported function.
2023-01-09 19:18:12.265  - info: zigbee.0 (5024)   --> transmitPower : normal
2023-01-09 19:18:12.884  - info: zigbee.0 (5024) Unable to set transmit power, unsupported function.
2023-01-09 19:18:12.946  - info: zigbee.0 (5024) Currently 37 devices are joined:
2023-01-09 19:18:13.469  - info: zigbee.0 (5024) Configuring 0x2c1165fffe99b52f TS004F
2023-01-09 19:18:13.483  - info: zigbee.0 (5024) 0x2c1165fffe99b52f (addr 2710): HG08164 - Lidl Silvercrest smart button (EndDevice)
2023-01-09 19:18:13.529  - info: zigbee.0 (5024) 0x5c0272fffe8c7426 (addr 58801): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
.
. (gekürzt)
.
2023-01-09 19:18:13.829  - info: zigbee.0 (5024) Zigbee started
2023-01-09 19:18:14.278  - warn: zigbee.0 (5024) download icon from https://www.zigbee2mqtt.io/images/devices/HG08164.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/HG08164.png
.
. (gekürzt)
.
2023-01-09 19:18:19.438  - warn: zigbee.0 (5024) Object 5c0272fffe8c7426.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.440  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.443  - warn: zigbee.0 (5024) Object 842e14fffe5a22f6.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.445  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.452  - warn: zigbee.0 (5024) Object 00124b0026b6f49d.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.454  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.460  - warn: zigbee.0 (5024) Object 842e14fffeefe9d2.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.463  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.466  - warn: zigbee.0 (5024) Object e0798dfffe886e8e.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.468  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.472  - warn: zigbee.0 (5024) Object e0798dfffec6c464.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.474  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.480  - warn: zigbee.0 (5024) Object 04cd15fffe9628f3.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.482  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.486  - warn: zigbee.0 (5024) Object b4e3f9fffec516f6.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.488  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.491  - warn: zigbee.0 (5024) Object b4e3f9fffecb1d1b.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.493  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.590  - warn: zigbee.0 (5024) Object zigbee.0.5c0272fffe8c7426.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.592  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.648  - warn: zigbee.0 (5024) Object zigbee.0.842e14fffe5a22f6.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.655  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.658  - warn: zigbee.0 (5024) Object zigbee.0.00124b0026b6f49d.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.659  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.661  - warn: zigbee.0 (5024) Object zigbee.0.842e14fffeefe9d2.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.662  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.663  - warn: zigbee.0 (5024) Object zigbee.0.e0798dfffe886e8e.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.665  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.667  - warn: zigbee.0 (5024) Object zigbee.0.e0798dfffec6c464.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.668  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:54.242  - info: zigbee.0 (5024) List of port: [{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyACM0","manufacturer":"dresden elektronik ingenieurtechnik GmbH","serialNumber":"DE2661519","pnpId":"usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2661519-if00","vendorId":"1cf1","productId":"0030"},{"path":"/dev/ttyS0"}]
2023-01-09 19:19:14.163  - error: zigbee.0 (5024) DeviceConfigure:Failed to DeviceConfigure.configure 0x2c1165fffe99b52f TS004F (Error: Bind 0x2c1165fffe99b52f/1 genPowerCfg from '0x00212effff095f03/1' failed (waiting for response TIMEOUT)
2023-01-09 19:20:00.235  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:01.238  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:03.575  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:04.898  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:07.252  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:08.753  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:18.256  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-01-09 19:20:20.256  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-01-09 19:20:20.259  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0xe0798dfffec6c464 A10
2023-01-09 19:20:20.262  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-01-09 19:20:20.264  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F
2023-01-09 19:20:30.896  - error: zigbee.0 (5024) Send command to 0x847127fffe75db97 failed with no error code (undefined)
2023-01-09 19:20:30.978  - error: zigbee.0 (5024) Send command to 0x847127fffe75db97 failed with no error code (undefined)
2023-01-09 19:20:31.378  - error: zigbee.0 (5024) Send command to 0x847127fffe75db97 failed with no error code (undefined)
2023-01-09 19:20:31.450  - error: zigbee.0 (5024) Send command to 0x847127fffe75db97 failed with no error code (undefined)
2023-01-09 19:21:31.585  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)

Spannend fand ich die Meldung This object will not be created in future versions. Please report this to the developer.

Vielen Dank nochmal für eure Unterstützung

[DerRoch]

Was ich jetzt grad im Moment noch komisch finde sind meine Temperatur-Sensoren (SNZB-02 - SONOFF Temperature and humidity sensor). Hab ich aktuell 4 funktionierende im Einsatz. Bei bei zwei Sensoren wird die Humidity nicht übertragen/angezeigt (im Objekt-Browser kann man ja auch im Mouseover sehen wann der Wert zuletzt aktualisiert wurde).

Die Batterie-Werte der Sensoren wurde bisher auch noch nicht wieder aktualisiert (bei keinem) - Letztes Update am 06.01.2023 - kurz vor dem Kartenausfall.

Nachtrag: nach rund 30-45 min kommen auch die anderen Humi-Werte. Die Batterie-Werte wurden aber noch nicht auf Stand gebracht. Ich geh mal davon aus, dass das Verhalten normal ist