Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[e-i-k-e]

Hallo zusammen,
ich bin am Wochenende von einem Proxmox Container auf eine VM umgezogen.
In der VM läuft Ubuntu-server 22.04, neu aufgesetzt. IoBroker habe ich über ein Backup wieder herstellen lassen. Soweit so gut, es läuft alles bis auf Zigbee.

Ich habe massive Probleme den Port meins TI LAUNCHXL-CC1352P-2 zu öffnen.
Dies klappt nur sporadisch und ich kann keinen Fehler finden und wenn es doch läuft, ist es stabil. Aber sobald ich einen Neustart durchführe, lässt sich der Port nicht mehr öffnen.

Was habe ich bisher unternommen.

• COM-Anschlussnamen im Adapter von "/dev/ttyACM0" auf "/dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.22__Embed_with_CMSIS-DAP_L1100L7S-if00" geändert. Aber auch hin und her. Beide Varianten haben bereits funktioniert.

• Den Adapter über die Katze neu installiert.

• Die Firmware des Board aktualisiert

• Proxmox komplett heruntergefahren, vom Strom getrennt und erneut gestartet.

• ioBroker neu gestartet

• Zigbee Adapter beendet, USB- Kabel für eine Minute gezogen und wieder gestarte.

• Den Rest-Button am Board gedrückt

• Im ursprünglichen Container war der Port durchgereicht. Den Container habe ich komplett entfern. Auch die damaligen Dateien wurden gelöscht (https://monach.us/automation/connecting-zwave-stick-under-lxc/)

Ich weiß momentan nicht weiter.

zigbee.0
2023-03-07 18:11:48.778	info	debug devices set to []

zigbee.0
2023-03-07 18:11:48.705	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

zigbee.0
2023-03-07 18:11:48.701	info	terminating

zigbee.0
2023-03-07 18:11:48.697	warn	Failed to stop zigbee during startup

zigbee.0
2023-03-07 18:11:48.648	info	Zigbee: disabling joining new devices.

zigbee.0
2023-03-07 18:11:48.075	info	cleaned everything up...

zigbee.0
2023-03-07 18:11:48.072	info	Got terminate signal TERMINATE_YOURSELF

zigbee.0
2023-03-07 18:09:28.840	error	Error herdsman start

zigbee.0
2023-03-07 18:09:28.839	error	Failed to start Zigbee

zigbee.0
2023-03-07 18:09:28.837	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"

zigbee.0
2023-03-07 18:09:28.477	info	Installed Version: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba

zigbee.0
2023-03-07 18:09:28.451	info	Starting Zigbee npm ...

zigbee.0
2023-03-07 18:09:28.449	info	Try to reconnect. 1 attempts left

zigbee.0
2023-03-07 18:09:18.445	error	Error herdsman start

zigbee.0
2023-03-07 18:09:18.444	error	Failed to start Zigbee

zigbee.0
2023-03-07 18:09:18.443	error	Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"

zigbee.0
2023-03-07 18:08:58.265	info	Installed Version: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba

zigbee.0
2023-03-07 18:08:57.458	info	Starting Zigbee npm ...

zigbee.0
2023-03-07 18:08:57.455	info	delete old Backup files. keep only last 10

zigbee.0
2023-03-07 18:08:57.303	info	starting. Version 1.8.11 (non-npm: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.1, js-controller: 4.0.24

zigbee.0
2023-03-07 18:08:49.751	info	debug devices set to []

zigbee.0
2023-03-07 18:08:49.676	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

zigbee.0
2023-03-07 18:08:49.674	info	terminating

zigbee.0
2023-03-07 18:08:49.673	warn	Failed to stop zigbee during startup

zigbee.0
2023-03-07 18:08:49.629	info	Zigbee: disabling joining new devices.

zigbee.0
2023-03-07 18:08:49.157	info	cleaned everything up...

zigbee.0
2023-03-07 18:08:49.155	info	Got terminate signal TERMINATE_YOURSELF

zigbee.0
2023-03-07 17:58:22.668	error	Error herdsman start

zigbee.0
2023-03-07 17:58:22.667	error	Failed to start Zigbee

zigbee.0
2023-03-07 17:58:22.665	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"

zigbee.0
2023-03-07 17:58:22.269	info	Installed Version: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba

zigbee.0
2023-03-07 17:58:22.234	info	Starting Zigbee npm ...

zigbee.0
2023-03-07 17:58:22.232	info	Try to reconnect. 1 attempts left

zigbee.0
2023-03-07 17:58:12.227	error	Error herdsman start

zigbee.0
2023-03-07 17:58:12.226	error	Failed to start Zigbee

zigbee.0
2023-03-07 17:58:12.225	error	Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"

zigbee.0
2023-03-07 17:57:52.114	info	Installed Version: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba

zigbee.0
2023-03-07 17:57:51.352	info	Starting Zigbee npm ...

zigbee.0
2023-03-07 17:57:51.349	info	delete old Backup files. keep only last 10

zigbee.0
2023-03-07 17:57:51.204	info	starting. Version 1.8.11 (non-npm: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.1, js-controller: 4.0.24

zigbee.0
2023-03-07 17:57:43.608	info	debug devices set to []

zigbee.0
2023-03-07 17:57:43.532	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

zigbee.0
2023-03-07 17:57:43.530	info	terminating

zigbee.0
2023-03-07 17:57:43.529	warn	Failed to stop zigbee during startup

zigbee.0
2023-03-07 17:57:43.468	info	Zigbee: disabling joining new devices.

zigbee.0
2023-03-07 17:57:43.023	info	cleaned everything up...

zigbee.0
2023-03-07 17:57:43.021	info	Got terminate signal TERMINATE_YOURSELF

zigbee.0
2023-03-07 17:54:57.837	error	Error herdsman start

zigbee.0
2023-03-07 17:54:57.837	error	Failed to start Zigbee

zigbee.0
2023-03-07 17:54:57.835	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"

zigbee.0
2023-03-07 17:54:57.507	info	Installed Version: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba

zigbee.0
2023-03-07 17:54:57.483	info	Starting Zigbee npm ...

zigbee.0
2023-03-07 17:54:57.482	info	Try to reconnect. 1 attempts left

zigbee.0
2023-03-07 17:54:47.476	error	Error herdsman start

zigbee.0
2023-03-07 17:54:47.476	error	Failed to start Zigbee

zigbee.0
2023-03-07 17:54:47.475	error	Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"

zigbee.0
2023-03-07 17:54:27.340	info	Installed Version: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba

zigbee.0
2023-03-07 17:54:26.590	info	Starting Zigbee npm ...

zigbee.0
2023-03-07 17:54:26.587	info	delete old Backup files. keep only last 10

zigbee.0
2023-03-07 17:54:26.348	info	starting. Version 1.8.11 (non-npm: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.1, js-controller: 4.0.24

zigbee.0
2023-03-07 17:54:19.036	info	debug devices set to []

zigbee.0
2023-03-07 17:54:19.002	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

zigbee.0
2023-03-07 17:54:19.000	info	terminating

zigbee.0
2023-03-07 17:54:18.999	warn	Failed to stop zigbee during startup

zigbee.0
2023-03-07 17:54:18.950	info	Zigbee: disabling joining new devices.

zigbee.0
2023-03-07 17:54:18.271	info	cleaned everything up...

zigbee.0
2023-03-07 17:54:18.268	info	Got terminate signal TERMINATE_YOURSELF

zigbee.0
2023-03-07 17:52:42.408	info	List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100L7S","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.22__Embed_with_CMSIS-DAP_L1100L7S-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100L7S","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.22__Embed_with_CMSIS-DAP_L1100L7S-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyUSB0","manufacturer":"Silicon Labs","serialNumber":"0021","pnpId":"usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0021-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS10"},{"path":"/dev/ttyS11"},{"path":"/dev/ttyS12"},{"path":"/dev/ttyS13"},{"path":"/dev/ttyS14"},{"path":"/dev/ttyS15"},{"path":"/dev/ttyS16"},{"path":"/dev/ttyS17"},{"path":"/dev/ttyS18"},{"path":"/dev/ttyS19"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS20"},{"path":"/dev/ttyS21"},{"path":"/dev/ttyS22"},{"path":"/dev/ttyS23"},{"path":"/dev/ttyS24"},{"path":"/dev/ttyS25"},{"path":"/dev/ttyS26"},{"path":"/dev/ttyS27"},{"path":"/dev/ttyS28"},{"path":"/dev/ttyS29"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS30"},{"path":"/dev/ttyS31"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyS8"},{"path":"/dev/ttyS9"}]

zigbee.0
2023-03-07 17:52:41.975	error	getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')

Edit: Und jetzt ging es wieder. Habe den Adapter deaktiviert, USB-Stecker gezogen, gewartet, den Rest Knopf gedruckt und den Adapter gestartet.
Ich verstehe es nicht

zigbee.0
2023-03-07 18:19:10.617	info	Currently 79 devices are joined:

zigbee.0
2023-03-07 18:19:10.597	info	--> transmitPower : high

zigbee.0
2023-03-07 18:19:10.568	info	Unable to disable LED, unsupported function.

zigbee.0
2023-03-07 18:19:10.521	info	Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20221226}}

zigbee.0
2023-03-07 18:19:06.322	info	Installed Version: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba

zigbee.0
2023-03-07 18:19:05.546	info	Starting Zigbee npm ...

zigbee.0
2023-03-07 18:19:05.543	info	delete old Backup files. keep only last 10

zigbee.0
2023-03-07 18:19:05.378	info	starting. Version 1.8.11 (non-npm: ioBroker/ioBroker.zigbee#9c8dd93cc65398d766a01ce7d5bea3777e0be5ba) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.1, js-controller: 4.0.24

[e-i-k-e]

Keiner eine Idee?

Das Problem tritt bei jedem Neustart auf.
Durch: Adapter Stop, USB-Kabel entfernen, Rest-Button drucken lässt sich das Problem, bis zum nächsten Neustart, beheben.

[Thomas Braun]

@e-i-k-e

ls -lAh /dev/serial/by-id/

sagt? Ich glaube die Dinger haben zwei Interfaces. Mal das andere probiert?

[e-i-k-e]

@thomas-braun

pi@ioBroker:~$ ls -lAh /dev/serial/by-id/
total 0
lrwxrwxrwx 1 root root 13 Mär  9 20:48 usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0021-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Mär  9 20:48 usb-Texas_Instruments_XDS110__03.00.00.22__Embed_with_CMSIS-DAP_L1100L7S-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Mär  9 20:48 usb-Texas_Instruments_XDS110__03.00.00.22__Embed_with_CMSIS-DAP_L1100L7S-if03 -> ../../ttyACM1
pi@ioBroker:~$

Ich habe beide versucht, oder auch direkt die ID-Verwendet.

[e-i-k-e]

Ich kann das Problem nicht lokalisieren. Was kann ich noch versuchen?