Mit conbee2 von deconz zu zigbee Adapter wechseln
-
@docsnyder7 sagte in Mit conbee2 von deconz zu zigbee Adapter wechseln:
cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2426882-if00'
vorhin hast du diese ID hier gezeigt:
lrwxrwxrwx 1 root root 13 21. Sep 19:32 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2598659-if00da passt was nicht. DE2426882 oder DE2598659???
-
die 2598659 ist meine ID... das Muster war die 2426882... nach der Vorgabe hab ich dann meine angepasst
-
@docsnyder7 sagte in Mit conbee2 von deconz zu zigbee Adapter wechseln:
die 2598659 ist meine ID... das Muster war die 2426882... nach der Vorgabe hab ich dann meine angepasst
Aber die Fehlermeldung lautet doch, dass er die DE2426882 nicht finden kann. Das ist doch dann die falsche.
-
docsn@evccpi:/opt/zigbee2mqtt $ npm start > zigbee2mqtt@1.33.0 start > node index.js Zigbee2MQTT:info 2023-09-21 21:11:45: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2023-09-21.21-11-45' filename: log.txt Zigbee2MQTT:info 2023-09-21 21:11:45: Starting Zigbee2MQTT version 1.33.0 (commit #f224ef7) Zigbee2MQTT:info 2023-09-21 21:11:45: Starting zigbee-herdsman (0.18.5) Zigbee2MQTT:error 2023-09-21 21:11:46: Error while starting zigbee-herdsman Zigbee2MQTT:error 2023-09-21 21:11:46: Failed to start zigbee Zigbee2MQTT:error 2023-09-21 21:11:46: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions Zigbee2MQTT:error 2023-09-21 21:11:46: Exiting... Zigbee2MQTT:error 2023-09-21 21:11:46: Error: Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2598659-if00' at SerialPort.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:200:28) at SerialPort._error (/opt/zigbee2mqtt/node_modules/@serialport/stream/dist/index.js:75:22) at /opt/zigbee2mqtt/node_modules/@serialport/stream/dist/index.js:111:18homeassistant: false frontend: port: 8080 mqtt: base_topic: zigbee2mqtt server: mqtt://localhost:1883 serial: adapter: deconz port: >- /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2598659-if00 advanced: network_key: - 81 - 57 - 96 - 198 - 234 - 212 - 78 - 33 - 164 - 186 - 34 - 234 - 242 - 153 - 45 - 192 pan_id: 54324 ext_pan_id: - 107 - 4 - 141 - 94 - 182 - 189 - 222 - 1 -
Könnte man das alles mit einem anderen Stick vereinfachen... zb Sonoff
-
@docsnyder7 sagte in Mit conbee2 von deconz zu zigbee Adapter wechseln:
Könnte man das alles mit einem anderen Stick vereinfachen... zb Sonoff
Das funktioniert unabhängig vom verwendeten Stick. Ich lese aus der Fehlermeldung immer noch, dass der Stick schon in Benutzung ist. Könnte es sein, das du Z2M bereits als Service startest und zusätzlich über „npm start“?
-
service ist nicht im autostart, zusätzlich händisch gestopt... Conbee zurückgesetzt.... reboot....
NIX
-
-
======== Start marking the full check here ========= Skript v.2023-06-20 *** BASE SYSTEM *** Static hostname: evccpi Icon name: computer Machine ID: 82971e2b59e04cc6823b9b47e5bb8656 Boot ID: c0d30cedbf3f4ad28aa5deafb466f56d Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 07:53:17 up 1:02, 3 users, load average: 0.58, 0.78, 0.61 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=50.1'C volt=0.9360V *** Time and Time Zones *** Local time: Fri 2023-09-22 07:53:17 CEST Universal time: Fri 2023-09-22 05:53:17 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** docsn /home/docsn docsn adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: true Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 7.8G 1.9G 4.8G 21M 1.1G 5.7G Swap: 99M 0B 99M Total: 7.9G 1.9G 4.9G 7811 M total memory 1919 M used memory 2346 M active memory 497 M inactive memory 4765 M free memory 85 M buffer memory 1040 M swap cache 99 M total swap 0 M used swap 99 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 459G 12G 429G 3% / devtmpfs devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 1.3M 1.6G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 vfat 255M 31M 225M 13% /boot tmpfs tmpfs 782M 20K 782M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Fri Sep 22 06:50:44 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=E4:5F:01:98:BE:6A vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=ttyS0,115200 console=tty1 root=PARTUUID=5f70fa40-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Fri Sep 22 06:50:48 2023] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none. [Fri Sep 22 06:50:48 2023] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. [Fri Sep 22 06:50:50 2023] EXT4-fs (sda2): re-mounted. Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime `-/boot /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 5.2G /var/ 4.4G /var/log 4.1G /var/log/journal/82971e2b59e04cc6823b9b47e5bb8656 4.1G /var/log/journal 539M /var/cache Archived and active journals take up 4.0G in the file system. /opt/iobroker/backups: 196M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 319M /opt/iobroker/iobroker-data/ 254M /opt/iobroker/iobroker-data/files 52M /opt/iobroker/iobroker-data/files/javascript.admin 45M /opt/iobroker/iobroker-data/files/devices.admin/static 45M /opt/iobroker/iobroker-data/files/devices.admin The five largest files in iobroker-data are: 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js.map 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js.map 18M /opt/iobroker/iobroker-data/objects.jsonl 8.6M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js *** NodeJS-Installation *** /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.12~dfsg-1~deb11u3 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: 0 *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl No configuration change needed. Multihost discovery server: disabled Discovery authentication: enabled Persistent activation: disabled Objects: jsonl on 127.0.0.1 States: jsonl on 127.0.0.1 Core adapters versions js-controller: 5.0.12 admin: 6.10.1 javascript: 7.1.4 Adapters from github: 3 Adapter State + system.adapter.admin.0 : admin : evccpi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : evccpi - enabled + system.adapter.backitup.0 : backitup : evccpi - enabled + system.adapter.cloud.0 : cloud : evccpi - enabled system.adapter.daswetter.0 : daswetter : evccpi - enabled system.adapter.devices.0 : devices : evccpi - enabled + system.adapter.discovery.0 : discovery : evccpi - enabled + system.adapter.email.0 : email : evccpi - enabled + system.adapter.evcc.0 : evcc : evccpi - enabled, port: 7070 + system.adapter.fritzdect.0 : fritzdect : evccpi - enabled + system.adapter.geofency.0 : geofency : evccpi - enabled, port: 7999, bind: 0.0.0.0 + system.adapter.history.0 : history : evccpi - enabled + system.adapter.homee.0 : homee : evccpi - enabled system.adapter.ical.0 : ical : evccpi - enabled system.adapter.ical.1 : ical : evccpi - disabled system.adapter.icons-fatcow-hosting.0 : icons-fatcow-hosting : evccpi - enabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : evccpi - enabled system.adapter.influxdb.0 : influxdb : evccpi - disabled, port: 8086 + system.adapter.iot.0 : iot : evccpi - enabled + system.adapter.javascript.0 : javascript : evccpi - enabled + system.adapter.modbus.0 : modbus : evccpi - enabled system.adapter.mqtt.0 : mqtt : evccpi - disabled, port: 1883, bind: 0.0.0.0 system.adapter.net-tools.0 : net-tools : evccpi - disabled + system.adapter.onvif.0 : onvif : evccpi - enabled system.adapter.ping.0 : ping : evccpi - disabled + system.adapter.pushover.0 : pushover : evccpi - enabled + system.adapter.pvforecast.0 : pvforecast : evccpi - enabled + system.adapter.rpi2.0 : rpi2 : evccpi - enabled system.adapter.schoolfree.0 : schoolfree : evccpi - enabled + system.adapter.shelly.0 : shelly : evccpi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : evccpi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shuttercontrol.0 : shuttercontrol : evccpi - enabled + system.adapter.time-switch.0 : time-switch : evccpi - enabled + system.adapter.tr-064.0 : tr-064 : evccpi - enabled + system.adapter.tr-064.1 : tr-064 : evccpi - enabled + system.adapter.tr-064.2 : tr-064 : evccpi - enabled + system.adapter.tr-064.3 : tr-064 : evccpi - enabled + system.adapter.trashschedule.0 : trashschedule : evccpi - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : evccpi - enabled + system.adapter.vis-inventwo.0 : vis-inventwo : evccpi - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : evccpi - enabled system.adapter.vis-weather.0 : vis-weather : evccpi - enabled system.adapter.vis.0 : vis : evccpi - enabled + system.adapter.web.0 : web : evccpi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : evccpi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.evcc.0 : evcc : evccpi - enabled, port: 7070 + system.adapter.geofency.0 : geofency : evccpi - enabled, port: 7999, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : evccpi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : evccpi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.web.0 : web : evccpi - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.10.1 , installed 6.10.1 Adapter "alexa2" : 3.25.2 , installed 3.24.1 [Updatable] Adapter "backitup" : 2.8.1 , installed 2.6.23 [Updatable] Adapter "cloud" : 4.4.1 , installed 4.4.1 Adapter "daswetter" : 3.1.10 , installed 3.1.10 Adapter "devices" : 1.1.5 , installed 1.1.5 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "email" : 1.2.0 , installed 1.2.0 Adapter "evcc" : 0.0.10 , installed 0.0.10 Adapter "fritzdect" : 2.3.1 , installed 2.3.1 Adapter "geofency" : 1.2.4 , installed 1.2.4 Adapter "history" : 2.2.6 , installed 2.2.6 Adapter "homee" : 1.2.0 , installed 1.2.0 Adapter "ical" : 1.13.3 , installed 1.13.3 Adapter "icons-fatcow-hosting": 0.1.0, installed 0.1.0 Adapter "icons-mfd-svg": 1.1.0 , installed 1.1.0 Adapter "influxdb" : 3.2.0 , installed 3.2.0 Adapter "iot" : 1.14.5 , installed 1.14.5 Adapter "javascript" : 7.1.4 , installed 7.1.4 Controller "js-controller": 5.0.12 , installed 5.0.12 Adapter "modbus" : 5.0.11 , installed 5.0.11 Adapter "mqtt" : 4.1.1 , installed 4.1.1 Adapter "net-tools" : 0.2.0 , installed 0.2.0 Adapter "onvif" : 1.0.5 , installed 1.0.5 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "pushover" : 3.0.3 , installed 3.0.3 Adapter "pvforecast" : 2.7.1 , installed 2.7.1 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "schoolfree" : 1.1.2 , installed 1.1.1 [Updatable] Adapter "shelly" : 6.4.1 , installed 6.4.1 Adapter "shuttercontrol": 1.6.2 , installed 1.6.2 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.5.5 , installed 6.5.5 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "trashschedule": 2.2.0 , installed 2.2.0 Adapter "vis" : 1.4.16 , installed 1.4.16 Adapter "vis-hqwidgets": 1.4.0 , installed 1.4.0 Adapter "vis-inventwo" : 3.3.3 , installed 3.3.3 Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "vis-weather" : 2.5.6 , installed 2.5.6 Adapter "web" : 6.1.2 , installed 6.1.2 Adapter "ws" : 2.5.5 , installed 2.5.5 Objects and States Please stand by - This may take a while Objects: 8536 States: 6690 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/oss/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Failed to fetch https://packages.grafana.com/oss/deb/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Some index files failed to download. They have been ignored, or old ones used instead. Hit:1 http://deb.debian.org/debian bullseye InRelease Get:2 https://packages.grafana.com/oss/deb stable InRelease [5984 B] Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://security.debian.org/debian-security bullseye-security InRelease Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease Get:6 https://dl.cloudsmith.io/public/evcc/stable/deb/debian bullseye InRelease [5127 B] Hit:7 https://phoscon.de/apt/deconz bullseye InRelease Get:8 https://deb.nodesource.com/node_18.x bullseye InRelease [4586 B] Err:2 https://packages.grafana.com/oss/deb stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 Fetched 9713 B in 2s (4265 B/s) Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/oss/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Failed to fetch https://packages.grafana.com/oss/deb/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Some index files failed to download. They have been ignored, or old ones used instead. Pending Updates: 5 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 22586 2287/io.shelly.0 tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 0 14064 652/vncserver-x11-c tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 1000 22603 2352/sshd: docsn@pt tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1000 23907 434/deCONZ tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1000 24720 434/deCONZ tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 16390 656/sshd: /usr/sbin tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 14055 638/cupsd tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 16013 839/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 18756 839/iobroker.js-con tcp6 0 0 :::5900 :::* LISTEN 0 14063 652/vncserver-x11-c tcp6 0 0 :::22 :::* LISTEN 0 16392 656/sshd: /usr/sbin tcp6 0 0 :::5021 :::* LISTEN 116 27604 4039/evcc tcp6 0 0 :::8887 :::* LISTEN 116 28720 4039/evcc tcp6 0 0 :::8086 :::* LISTEN 999 15485 650/influxd tcp6 0 0 :::8082 :::* LISTEN 1001 22968 2747/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 19285 1417/io.admin.0 tcp6 0 0 ::1:6010 :::* LISTEN 1000 22602 2352/sshd: docsn@pt tcp6 0 0 ::1:631 :::* LISTEN 0 14054 638/cupsd tcp6 0 0 :::7070 :::* LISTEN 116 31319 4039/evcc udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14107 510/dhcpcd udp 0 0 0.0.0.0:631 0.0.0.0:* 0 16411 666/cups-browsed udp 0 0 0.0.0.0:58081 0.0.0.0:* 108 15257 429/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 116 31317 4039/evcc udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 15255 429/avahi-daemon: r udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 21684 2341/io.shelly.1 udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 23910 434/deCONZ udp6 0 0 :::56841 :::* 108 15258 429/avahi-daemon: r udp6 0 0 :::546 :::* 0 11177 510/dhcpcd udp6 0 0 :::5353 :::* 116 31318 4039/evcc udp6 0 0 :::5353 :::* 108 15256 429/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-09-22 07:47:44.048 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:47:59.069 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:48:44.074 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:48:59.075 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:49:14.074 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:49:29.079 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:49:44.080 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:50:00.046 - debug: shuttercontrol.0 (2814) calculate astrodata ... 2023-09-22 07:50:00.048 - debug: shuttercontrol.0 (2814) Sun Azimut: 97° 2023-09-22 07:50:00.049 - debug: shuttercontrol.0 (2814) Sun Elevation: 6.1° 2023-09-22 07:50:14.094 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:50:29.083 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:50:59.089 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:51:14.094 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:51:29.093 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:51:44.095 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:52:14.093 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:52:29.105 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:52:59.109 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:53:14.119 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:53:29.125 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:53:44.120 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:53:59.127 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:54:14.124 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 2023-09-22 07:54:29.128 - info: shelly.1 (2341) [CoAP Server] Device is blacklisted: SHPLG-S#3CE90EC7EC37#2 ============ Mark until here for C&P ============= iob diag has finished. Copy text starting here ======================= SUMMARY ======================= v.2023-06-20 Static hostname: evccpi Icon name: computer Machine ID: 82971e2b59e04cc6823b9b47e5bb8656 Boot ID: c0d30cedbf3f4ad28aa5deafb466f56d Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: arm64 Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: true Boot Target: graphical.target Pending OS-Updates: 5 Pending iob updates: 3 Nodejs-Installation: /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.8G 1.9G 4.8G 21M 1.1G 5.8G Swap: 99M 0B 99M Total: 7.9G 1.9G 4.9G Active iob-Instances: 30 Active repo(s): stable ioBroker Core: js-controller 5.0.12 admin 6.10.1 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : evccpi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : evccpi - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 8536 States: 6690 Size of iob-Database: 18M /opt/iobroker/iobroker-data/objects.jsonl 5.8M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ==================== === Mark text until here for copying === docsn@evccpi:/opt/zigbee2mqtt $ -
@docsnyder7 sagte in Mit conbee2 von deconz zu zigbee Adapter wechseln:
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1000 23907 434/deCONZ
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1000 24720 434/deCONZdeCONZ ist NICHT beendet.
Abgesehen davon, achte bitte bei solchen Ausgaben darauf, dass die Code-Tags richtig gesetzt werden. Du siehst ja selbst, dass es nicht richtig formatiert ist.
-
-
@docsnyder7 sagte in Mit conbee2 von deconz zu zigbee Adapter wechseln:
damit meinst du die Ausgabe hier im Forum?
ja. Am Anfang des Textes EINMAL die drei Backticks "```" und am Ende nochmals. In der Zeile mit den Backticks darf nichts anderes stehen.
-
@marc-berg
OK beherzige ich! -
@docsnyder7 sagte in Mit conbee2 von deconz zu zigbee Adapter wechseln:
OK beherzige ich!
kannst ja oben noch editieren, damit das nicht wie Kraut und Rüben aussieht.
-
@docsnyder7 sagte in Mit conbee2 von deconz zu zigbee Adapter wechseln:
port: >-
Moin,
da gestern ab 20 Uhr Familienzeit angesagt war, komme ich erst heute dazu alles aufzuholen.
Wieso sind diese Zeichen in der Konfiguration>-, das ist mit Sicherheit falsch.VG
Bernd -
docsn@evccpi:~ $ systemctl status zigbee2mqtt.service * zigbee2mqtt.service - zigbee2mqtt Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2023-09-22 08:26:36 CEST; 7s ago Process: 2231 ExecStart=/usr/bin/npm start (code=exited, status=217/USER) Main PID: 2231 (code=exited, status=217/USER) CPU: 0npm start ist ohne fehler durchgelaufenn
hab jetzt den service in die Autostart gepackt
reboot
-
@dp20eic sagte in Mit conbee2 von deconz zu zigbee Adapter wechseln:
Wieso sind diese Zeichen in der Konfiguration >-, das ist mit Sicherheit falsch.
Im Übrigen kann man Z2M mit völlig leerer configuration.yaml starten. Im Default kommt man per Port 8080 drauf, kann über die Oberfläche alles konfigurieren und das wird dann in die configuration.yaml zurückgeschrieben. So kann man sicher sein, keine Fehler reinzubauen.
-
also könnte man bis auf den frontend eintrag alles rausnehmen?
ich komme nämlich nicht auf die 8080 -
@docsnyder7 sagte in Mit conbee2 von deconz zu zigbee Adapter wechseln:
ich komme nämlich nicht auf die 8080
Oh dear!
- Service beenden
- npm start
- Ausgabe hier posten
- laufen lassen und nochmals iob diag, Langversion
-
Zigbee2MQTT:info 2023-09-22 08:43:52: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2023-09-22.08-43-52' filename: log.txt Zigbee2MQTT:info 2023-09-22 08:43:52: Starting Zigbee2MQTT version 1.33.0 (commit #f224ef7) Zigbee2MQTT:info 2023-09-22 08:43:52: Starting zigbee-herdsman (0.18.5) Zigbee2MQTT:info 2023-09-22 08:43:53: zigbee-herdsman started (resumed) Zigbee2MQTT:info 2023-09-22 08:43:53: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":114,"product":0,"revision":"0x26720700","transportrev":0},"type":"ConBee2/RaspBee2"}' Zigbee2MQTT:info 2023-09-22 08:44:02: Currently 0 devices are joined: Zigbee2MQTT:info 2023-09-22 08:44:02: Zigbee: disabling joining new devices. Zigbee2MQTT:info 2023-09-22 08:44:03: Connecting to MQTT server at mqtt://192.168.178.57:1883 Zigbee2MQTT:info 2023-09-22 08:44:03: Connected to MQTT server Zigbee2MQTT:info 2023-09-22 08:44:03: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online' Zigbee2MQTT:info 2023-09-22 08:44:04: Started frontend on port 0.0.0.0:8080 Zigbee2MQTT:info 2023-09-22 08:44:04: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"f224ef7","coordinator":{"meta":{"maintrel":0,"majorrel":38,"minorrel":114,"product":0,"revision":"0x26720700","transportrev":0},"type":"ConBee2/RaspBee2"},"log_level":"info","network":{"channel":11,"extendedPanID":"0x412b1dae7bdd8bf3","panID":31839},"permit_join":false,"version":"1.33.0"}' Zigbee2MQTT:info 2023-09-22 08:44:04: Zigbee2MQTT started!das schaut gut aus... in dem zustand geht auch die 8080
jetzt STRG C, dann den Service wieder enable
dann start zigbee2mqtt.... korrekt
