funktioniert einwandfrei. habe bei einem gerät eingestellt dass es gleich auf mehreren wiedergibt.
über iot -> text2command -> multiroom
einfach geil
funktioniert einwandfrei. habe bei einem gerät eingestellt dass es gleich auf mehreren wiedergibt.
über iot -> text2command -> multiroom
einfach geil
EDIT: ok moment habe nach erneutem Interview jetzt die Config Datenpunkte erhalten. Namen zeigt es auch korrekt an. Sorry ich dachte ich hätte das beim ersten Gerät bereits einmal gemacht. Danke für Deine Unterstützung
@apollon77 ok issue erstellt. teste es via cloud heute abend. Danke
Sorry nein bitte löschen war der brainbug leider
@varg OK hab's gefunden.dank des Forums hier. Serielle Schnittstelle in der raspi config aktivieren ohh man
Versuche gerade die Razberry2 Zwave Aufsteckplatine vom Pi4 auf den Pi5(Bookworm)(Node18) umzusiedeln.
Klappt natürlich leider nicht.
Folgendes habe ich bereits versucht.
sudo nano /boot/cmdline.txt
remove console=serial0,115200
save the file and close it
sudo nano /boot/config.txt
Look for each of the following lines. If they are commented out with a #, remove that. If they don't exist, add them to the end of the file:
dtoverlay=pi3-miniuart-bt
enable_uart=1
force_turbo=1
reboot
pi@iobroker:~ $ ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Jan 6 12:41 usb-Texas_Instruments_CC2538_USB_CDC-if00 -> ../../ttyACM0
pi@iobroker:~ $
Gefunden wird aber nur Zigbee
Hat die Platine jemand bereits am Pi5 getestet oder weiss wo hier das Problem liegen könnte ?
zwave2.0
2024-01-06 12:44:16.599 error Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:4360:23) at ZWaveController.identify (/opt/iobroker/node_modules/zwave-js/src/lib/controller/Controller.ts:915:33) at Driver.initializeControllerAndNodes (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:1365:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:1171:16) (ZW0100)
dtoverlay=disable-bt
dtoverlay=disable-wifi
enable_uart=1
force_turbo=1
hilft auch nicht, die config ist gleich wie beim Pi4, das teil wird aber einfach nicht erkannt.
Hat noch jemand eine Idee ?
Ich hab das System nochmal komplett neu mit nodejs18 aufgesetzt und den alten Stick in Betrieb genommen.
Vielleicht hat noch jemand die neuere ti Platine mit der config und kann was dazu sagen.
Ich teste das Teil die Tage mal an einem PI4 mit buster und schau ob's damit läuft
Würde mich dann nochmal melden. Danke Euch
ich sag einfach mal ja hab aber wenig ahnung.
vor 2 Jahren konnte ich die platine noch in nem anderen system ohne probleme einbinden.
die neuere revision eben nicht
Ich vermute es hat was mit der neuen TI Platine zu tun.
Wenn ich den alten Stick von Arteck anschliesse funzt es auch nach Neustart.
@arteck hast Du eine Idee wie ich das Board richtig einbinde. Geflasht wurde es wie oben beschrieben
Ich kann nur so viel sagen dass ich mit dem TI Board nach jedem neustart ein port problem bekomme
Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
will leider nicht
zigbee.0
2024-01-05 12:32:22.961 error Error herdsman start
zigbee.0
2024-01-05 12:32:22.961 error Failed to start Zigbee
zigbee.0
2024-01-05 12:32:22.961 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
zigbee.0
2024-01-05 12:32:22.824 info Installed Version: iobroker.zigbee@1.9.5
zigbee.0
2024-01-05 12:32:22.816 info Starting Zigbee npm ...
zigbee.0
2024-01-05 12:32:22.815 info Try to reconnect. 1 attempts left
admin.0
2024-01-05 12:32:18.198 info <== Disconnect system.user.admin from ::ffff:192.168.178.55
admin.0
2024-01-05 12:32:18.198 info <== Disconnect system.user.admin from ::ffff:192.168.178.55
zigbee.0
2024-01-05 12:32:12.812 error Error herdsman start
zigbee.0
2024-01-05 12:32:12.812 error Failed to start Zigbee
zigbee.0
2024-01-05 12:32:12.812 error Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
zigbee.0
2024-01-05 12:32:05.356 info List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100VGY","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100VGY-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100VGY","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100VGY-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyAMA10"}]
zigbee.0
2024-01-05 12:32:05.235 error getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
zigbee.0
2024-01-05 12:17:42.424 error Error herdsman start
zigbee.0
2024-01-05 12:17:42.423 error Failed to start Zigbee
zigbee.0
2024-01-05 12:17:42.423 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
zigbee.0
2024-01-05 12:17:42.303 info Installed Version: iobroker.zigbee@1.9.5
zigbee.0
2024-01-05 12:17:42.297 info Starting Zigbee npm ...
zigbee.0
2024-01-05 12:17:42.297 info Try to reconnect. 1 attempts left
zigbee.0
2024-01-05 12:17:32.294 error Error herdsman start
zigbee.0
2024-01-05 12:17:32.293 error Failed to start Zigbee
zigbee.0
2024-01-05 12:17:32.293 error Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
pi@iobrokerpi5:~ $ ls -ls /dev/serial/by-id/
total 0
0 lrwxrwxrwx 1 root root 13 Jan 5 12:15 usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100VGY-if00 -> ../../ttyACM0
0 lrwxrwxrwx 1 root root 13 Jan 5 12:15 usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100VGY-if03 -> ../../ttyACM1
zigbee.0
2024-01-05 12:19:29.585 error Error herdsman start
zigbee.0
2024-01-05 12:19:29.584 error Failed to start Zigbee
zigbee.0
2024-01-05 12:19:29.584 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
zigbee.0
2024-01-05 12:19:29.459 info Installed Version: iobroker.zigbee@1.9.5
zigbee.0
2024-01-05 12:19:29.451 info Starting Zigbee npm ...
zigbee.0
2024-01-05 12:19:29.450 info Try to reconnect. 1 attempts left
zigbee.0
2024-01-05 12:19:19.447 error Error herdsman start
zigbee.0
2024-01-05 12:19:19.447 error Failed to start Zigbee
zigbee.0
2024-01-05 12:19:19.447 error Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
zigbee.0
2024-01-05 12:19:19.376 error Re-commissioning your network will require re-pairing of all devices!
zigbee.0
2024-01-05 12:19:19.375 error If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
zigbee.0
2024-01-05 12:19:19.375 error Please update configuration to prevent further issues.
zigbee.0
2024-01-05 12:19:19.375 error - Channel List: configured=11, adapter=11
zigbee.0
2024-01-05 12:19:19.374 error - Network Key: configured=ffffffffffffffffaaaaaaaaaaaaaaaa, adapter=ffffffffffffffffbbbbbbbbbbbbbbbb
zigbee.0
2024-01-05 12:19:19.374 error - Extended PAN ID: configured=ffffffffaaaaaaaa, adapter=ddddddddaaaaaaaa
zigbee.0
2024-01-05 12:19:19.374 error - PAN ID: configured=6754, adapter=6754
zigbee.0
2024-01-05 12:19:19.373 error Configuration is not consistent with adapter state/backup!
1
Zeit
debug
Nachricht
zigbee.0
2024-01-05 12:22:15.518 error Error herdsman start
zigbee.0
2024-01-05 12:22:15.518 error Failed to start Zigbee
zigbee.0
2024-01-05 12:22:15.517 error Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby"
admin.0
2024-01-05 12:22:13.107 info <== Disconnect system.user.admin from ::ffff:192.168.178.55
admin.0
2024-01-05 12:22:13.107 info <== Disconnect system.user.admin from ::ffff:192.168.178.55
zigbee.0
2024-01-05 12:22:04.147 info List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100VGY","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100VGY-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100VGY","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100VGY-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyAMA10"}]
zigbee.0
2024-01-05 12:22:04.051 error getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
admin.0
2024-01-05 12:22:03.973 info ==> Connected system.user.admin from ::ffff:192.168.178.55
admin.0
2024-01-05 12:22:02.099 info <== Disconnect system.user.admin from ::ffff:192.168.178.55
zigbee.0
2024-01-05 12:21:58.972 info List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100VGY","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100VGY-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100VGY","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100VGY-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyAMA10"}]
zigbee.0
2024-01-05 12:21:58.878 error getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
ich installier den adapter mal neu
@thomas-braun said in Error herdsman start Failed to start Zigbee:
iob nodejs-update 18
ioBroker nodejs updater 2023-10-13
You requested to intall latest version from nodejs v18 tree.
Your current setup is:
/usr/bin/nodejs v20.10.0
/usr/bin/node v20.10.0
/usr/bin/npm 10.2.3
/usr/bin/npx 10.2.3
/usr/bin/corepack 0.22.0
We found these nodejs versions available for installation:
nodejs:
Installed: 20.10.0-1nodesource1
Candidate: 20.10.0-1nodesource1
Version table:
*** 20.10.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
100 /var/lib/dpkg/status
20.9.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.8.1-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.8.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.7.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.6.1-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.6.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.5.1-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.5.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.4.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.3.1-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.3.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.2.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.1.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
20.0.0-1nodesource1 600
500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
18.19.0+dfsg-6~deb12u1 500
500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages
18.13.0+dfsg1-1 500
500 http://deb.debian.org/debian bookworm/main arm64 Packages
Nothing to do - Your installation is using the correct paths.
You are running nodejs v20.10.0. Do you want to install latest version from nodejs v.18 tree?
Press <y> to continue or any other key to quit
Trying to update your installation now. Please be patient.
Waiting for ioBroker to shut down - Give me a minute...
############################################################
*** These repos are active on your system:
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
Reading package lists... Done
*** Installing ca-certificates, curl and gnupg, just in case they are missing.
*** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source
deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main
Package: nodejs
Pin: origin deb.nodesource.com
Pin-Priority: 1001
*** These repos are active after the adjustments:
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
Get:5 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB]
Get:6 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages [6656 B]
Get:7 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages [6613 B]
Fetched 25.4 kB in 1s (45.4 kB/s)
Reading package lists... Done
Installing the recommended nodejs version now!
Exact recommended version unknown, installing a fallback!
dpkg: warning: downgrading nodejs from 20.10.0-1nodesource1 to 18.0.0-1nodesource1
(Reading database ... 68077 files and directories currently installed.)
Preparing to unpack .../nodejs_18.0.0-1nodesource1_arm64.deb ...
Detected old npm client, removing...
Unpacking nodejs (18.0.0-1nodesource1) over (20.10.0-1nodesource1) ...
Setting up nodejs (18.0.0-1nodesource1) ...
Processing triggers for man-db (2.11.2-2) ...
Updating fallback to latest nodejs v18 release
(Reading database ... 68299 files and directories currently installed.)
Preparing to unpack .../nodejs_18.19.0-1nodesource1_arm64.deb ...
Detected old npm client, removing...
Unpacking nodejs (18.19.0-1nodesource1) over (18.0.0-1nodesource1) ...
Setting up nodejs (18.19.0-1nodesource1) ...
Processing triggers for man-db (2.11.2-2) ...
v18.19.0 has been installed! You are using the latest version now!
Installing the recommended nodejs version!
We tried our best to update or fix your nodejs. Please run iob diag again to verify.
*** RESTARTING ioBroker NOW! ***
Please refresh or restart your browser in a few moments.
pi@iobrokerpi5:~ $
moment ich check ob sich was geändert hat und danke schonmal für den Beistand
Node.js v18.19.0
pi@iobrokerpi5:~ $ nodejs -v
v18.19.0
pi@iobrokerpi5:~ $ node -v
v18.19.0
pi@iobrokerpi5:~ $ npm -v
10.2.3
pi@iobrokerpi5:~ $