Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Hardware
    4. gelöst: SMLIGHT SLZB-07 mit dem EFR32MG21 Chip einbinden

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    gelöst: SMLIGHT SLZB-07 mit dem EFR32MG21 Chip einbinden

    This topic has been deleted. Only users with topic management privileges can see it.
    • ldittmar
      ldittmar Developer last edited by ldittmar

      Hallo Community,

      ich habe mir den SLZB-07 Stick geholt und versuche es mit dem Zigbee Adapter zu verbinden. Hab die aktuelle Firmware 7.4.1.0 eingespielt.

      Im Zigbee Adapter habe ich als COM-Port "/dev/ttyUSB0" und als Typ "Silicon Labs EZSP/EFR32" ausgewählt. Wenn ich den Adapter dann starte, bekomme ich diese Fehlermeldung:

      2024-06-24 09:03:38.673 - info: host.ioBroker "system.adapter.zigbee.2" enabled
2024-06-24 09:03:39.584 - info: host.ioBroker instance system.adapter.zigbee.2 started with pid 2698136
2024-06-24 09:03:40.500 - debug: zigbee.2 (2698136) Redis Objects: Use Redis connection: 0.0.0.0:9001
2024-06-24 09:03:40.561 - debug: zigbee.2 (2698136) Objects client ready ... initialize now
2024-06-24 09:03:40.562 - debug: zigbee.2 (2698136) Objects create System PubSub Client
2024-06-24 09:03:40.562 - debug: zigbee.2 (2698136) Objects create User PubSub Client
2024-06-24 09:03:40.903 - debug: zigbee.2 (2698136) Objects client initialize lua scripts
2024-06-24 09:03:40.912 - debug: zigbee.2 (2698136) Objects connected to redis: 0.0.0.0:9001
2024-06-24 09:03:40.913 - silly: zigbee.2 (2698136) redis psubscribe cfg.o.system.user.*
2024-06-24 09:03:41.000 - silly: zigbee.2 (2698136) redis psubscribe cfg.o.enum.*
2024-06-24 09:03:41.001 - silly: zigbee.2 (2698136) objectDB connected
2024-06-24 09:03:41.001 - debug: zigbee.2 (2698136) Redis States: Use Redis connection: 0.0.0.0:6379
2024-06-24 09:03:41.003 - debug: zigbee.2 (2698136) States create System PubSub Client
2024-06-24 09:03:41.004 - debug: zigbee.2 (2698136) States create User PubSub Client
2024-06-24 09:03:41.006 - debug: zigbee.2 (2698136) States connected to redis: 0.0.0.0:6379
2024-06-24 09:03:41.006 - silly: zigbee.2 (2698136) statesDB connected
2024-06-24 09:03:41.021 - debug: zigbee.2 (2698136) Plugin sentry Initialize Plugin (enabled=true)
2024-06-24 09:03:41.162 - info: zigbee.2 (2698136) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.13.0, js-controller: 5.0.19
2024-06-24 09:03:41.183 - debug: zigbee.2 (2698136) Using zigbee-herdsman with settings: {"network":{"panID":6759,"extendedPanID":[183,163,134,92,139,122,246,220],"channelList":[25],"networkKey":[1,35,5,7,9,10,13,15,1,2,4,7,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_2/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_2/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyUSB0","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false}
2024-06-24 09:03:41.200 - info: zigbee.2 (2698136) Starting Zigbee npm ...
2024-06-24 09:03:41.267 - silly: zigbee.2 (2698136) States system redis pmessage io.system.adapter.zigbee.2.logLevel/io.system.adapter.zigbee.2.logLevel:{"val":"silly","ack":true,"ts":1719212621201,"q":0,"from":"system.adapter.zigbee.2","lc":1719139097127}
2024-06-24 09:03:41.269 - debug: zigbee.2 (2698136) Starting zigbee-herdsman...
2024-06-24 09:03:41.351 - info: zigbee.2 (2698136) Installed Version: iobroker.zigbee@latest
2024-06-24 09:03:41.351 - debug: zigbee.2 (2698136) Backup /opt/iobroker/iobroker-data/zigbee_2/backup_2024_06_24-09_03_41.tar.gz success
2024-06-24 09:03:41.354 - silly: zigbee.2 (2698136) States user redis pmessage io.zigbee.2.*/io.zigbee.2.info.connection:{"val":false,"ack":true,"ts":1719212621353,"q":0,"from":"system.adapter.zigbee.2","user":"system.user.admin","lc":1719138937320}
2024-06-24 09:03:44.819 - error: zigbee.2 (2698136) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-06-24 09:03:44.820 - error: zigbee.2 (2698136) Failed to start Zigbee
2024-06-24 09:03:44.820 - error: zigbee.2 (2698136) Error herdsman start
2024-06-24 09:03:44.875 - silly: zigbee.2 (2698136) States user redis pmessage io.zigbee.2.*/io.zigbee.2.info.pairingMessage:{"val":"Error: Starting zigbee-herdsman problem : \"startup failed - configuration-adapter mismatch - see logs above for more information\". undefined","ack":true,"ts":1719212624874,"q":0,"from":"system.adapter.zigbee.2","user":"system.user.admin","lc":1719212624874}
2024-06-24 09:03:44.875 - silly: zigbee.2 (2698136) States user redis pmessage io.zigbee.2.*/io.zigbee.2.info.connection:{"val":false,"ack":true,"ts":1719212624875,"q":0,"from":"system.adapter.zigbee.2","user":"system.user.admin","lc":1719138937320}
2024-06-24 09:03:54.821 - info: zigbee.2 (2698136) Try to reconnect. 1 attempts left
2024-06-24 09:03:54.823 - info: zigbee.2 (2698136) Starting Zigbee npm ...
2024-06-24 09:03:54.826 - debug: zigbee.2 (2698136) Starting zigbee-herdsman...
2024-06-24 09:03:54.836 - info: zigbee.2 (2698136) Installed Version: iobroker.zigbee@latest
2024-06-24 09:04:24.923 - error: zigbee.2 (2698136) Starting zigbee-herdsman problem : "Failure to connect"
2024-06-24 09:04:24.923 - error: zigbee.2 (2698136) Failed to start Zigbee
2024-06-24 09:04:24.923 - error: zigbee.2 (2698136) Error herdsman start
2024-06-24 09:04:24.927 - silly: zigbee.2 (2698136) States user redis pmessage io.zigbee.2.*/io.zigbee.2.info.pairingMessage:{"val":"Error: Starting zigbee-herdsman problem : \"Failure to connect\". undefined","ack":true,"ts":1719212664927,"q":0,"from":"system.adapter.zigbee.2","user":"system.user.admin","lc":1719212664927}
2024-06-24 09:04:24.976 - silly: zigbee.2 (2698136) States user redis pmessage io.zigbee.2.*/io.zigbee.2.info.connection:{"val":false,"ack":true,"ts":1719212664975,"q":0,"from":"system.adapter.zigbee.2","user":"system.user.admin","lc":1719138937320}

      Hat jemand eine Idee was ich noch probieren könnte bzw. was ich übersehen habe? Hier noch ein paar Linux Angaben:

      ldittmar@ioBroker:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 008: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 003 Device 026: ID 0451:bef3 Texas Instruments, Inc. CC1352R1 Launchpad
Bus 003 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 003 Device 032: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ldittmar@ioBroker:~$ ls -l /dev/serial/by-id
insgesamt 0
lrwxrwxrwx 1 root root 13 23. Jun 12:32 usb-SMLIGHT_SMLIGHT_SLZB-07_f832a235b373ed1182ee66eefdf7b791-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 19. Jun 20:23 usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L430032P-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 19. Jun 20:23 usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L430032P-if03 -> ../../ttyACM1

      Zigbee-Adapter: 1.10.3
      JS-Controller: 5.0.19
      Admin: 6.13.16
      Node.JS: 18.13.0
      OS: Linux

      arteck 1 Reply Last reply Reply Quote 0
      • arteck
        arteck Developer Most Active @ldittmar last edited by arteck

        @ldittmar sagte in SMLIGHT SLZB-07 mit dem EFR32MG21 Chip einbinden:

        startup failed - configuration-adapter mismatch - see logs above for more information"

        erstmal mach die debug infos aus...
        dann siehst du mehr.. das problem ist .. SLZB-07 probiert die nvbackup einzuspielen was nicht geht.. und schmiesst die MEldung

        configuration-adapter mismatch

        du musst ehh alles neu pairen.. also alles zurück auf initial.. und neu

        ldittmar 1 Reply Last reply Reply Quote 0
        • ldittmar
          ldittmar Developer @arteck last edited by ldittmar

          @arteck es war alles neu. Hab jetzt noch eine Instanz installiert und das gleiche kommt wieder.

          2024-06-24 09:15:54.211 - info: zigbee.3 (2698257) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.13.0, js-controller: 5.0.19
2024-06-24 09:15:54.252 - info: zigbee.3 (2698257) Starting Zigbee npm ...
2024-06-24 09:15:54.417 - info: zigbee.3 (2698257) Installed Version: iobroker.zigbee@latest
2024-06-24 09:16:00.283 - info: zigbee.3 (2698257) Coordinator firmware version: {"type":"EZSP v13","meta":{"product":13,"majorrel":"7","minorrel":"4","maintrel":"1 ","revision":"7.4.1.0 build 0"}}
2024-06-24 09:16:00.285 - info: zigbee.3 (2698257) Unable to disable LED, unsupported function.
2024-06-24 09:16:00.298 - info: zigbee.3 (2698257) --> transmitPower : normal
2024-06-24 09:16:00.353 - info: zigbee.3 (2698257) Currently no devices.
2024-06-24 09:16:00.354 - info: zigbee.3 (2698257) Zigbee started
2024-06-24 09:16:00.361 - info: host.ioBroker stopInstance system.adapter.zigbee.3 (force=false, process=true)
2024-06-24 09:16:00.363 - info: zigbee.3 (2698257) debug devices set to []
2024-06-24 09:16:00.460 - info: host.ioBroker stopInstance system.adapter.zigbee.3 send kill signal
2024-06-24 09:16:00.460 - info: zigbee.3 (2698257) Got terminate signal TERMINATE_YOURSELF
2024-06-24 09:16:00.461 - info: zigbee.3 (2698257) cleaned everything up...
2024-06-24 09:16:00.461 - info: zigbee.3 (2698257) Zigbee: disabling joining new devices.
2024-06-24 09:16:00.774 - info: zigbee.3 (2698257) terminating
2024-06-24 09:16:00.775 - info: zigbee.3 (2698257) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-06-24 09:16:00.962 - info: zigbee.3 (2698257) terminating
2024-06-24 09:16:01.772 - info: host.ioBroker stopInstance system.adapter.zigbee.3 killing pid 2698257
2024-06-24 09:16:02.142 - info: host.ioBroker instance system.adapter.zigbee.3 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-06-24 09:16:03.862 - info: host.ioBroker instance system.adapter.zigbee.3 started with pid 2698273
2024-06-24 09:16:05.229 - info: zigbee.3 (2698273) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.13.0, js-controller: 5.0.19
2024-06-24 09:16:05.268 - info: zigbee.3 (2698273) Starting Zigbee npm ...
2024-06-24 09:16:05.412 - info: zigbee.3 (2698273) Installed Version: iobroker.zigbee@latest
2024-06-24 09:16:08.880 - error: zigbee.3 (2698273) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-06-24 09:16:08.880 - error: zigbee.3 (2698273) Failed to start Zigbee
2024-06-24 09:16:08.880 - error: zigbee.3 (2698273) Error herdsman start
2024-06-24 09:16:18.882 - info: zigbee.3 (2698273) Try to reconnect. 1 attempts left
2024-06-24 09:16:18.883 - info: zigbee.3 (2698273) Starting Zigbee npm ...
2024-06-24 09:16:18.900 - info: zigbee.3 (2698273) Installed Version: iobroker.zigbee@latest
2024-06-24 09:16:48.984 - error: zigbee.3 (2698273) Starting zigbee-herdsman problem : "Failure to connect"
2024-06-24 09:16:48.985 - error: zigbee.3 (2698273) Failed to start Zigbee
2024-06-24 09:16:48.985 - error: zigbee.3 (2698273) Error herdsman start
2024-06-24 09:20:21.820 - info: host.ioBroker stopInstance system.adapter.zigbee.3 (force=false, process=true)
2024-06-24 09:20:21.821 - info: host.ioBroker stopInstance system.adapter.zigbee.3 send kill signal
2024-06-24 09:20:21.821 - info: zigbee.3 (2698273) Got terminate signal TERMINATE_YOURSELF
2024-06-24 09:20:21.822 - info: zigbee.3 (2698273) cleaned everything up...
2024-06-24 09:20:21.827 - info: zigbee.3 (2698273) Zigbee: disabling joining new devices.
2024-06-24 09:20:21.852 - warn: zigbee.3 (2698273) Failed to stop zigbee during startup
2024-06-24 09:20:21.852 - info: zigbee.3 (2698273) terminating
2024-06-24 09:20:21.853 - info: zigbee.3 (2698273) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-06-24 09:20:22.324 - info: zigbee.3 (2698273) terminating
2024-06-24 09:20:22.569 - info: host.ioBroker instance system.adapter.zigbee.3 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-06-24 09:20:25.231 - info: host.ioBroker instance system.adapter.zigbee.3 started with pid 2698316
2024-06-24 09:20:26.700 - info: zigbee.3 (2698316) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.13.0, js-controller: 5.0.19
2024-06-24 09:20:26.745 - info: zigbee.3 (2698316) Starting Zigbee npm ...
2024-06-24 09:20:26.886 - info: zigbee.3 (2698316) Installed Version: iobroker.zigbee@latest
2024-06-24 09:20:30.366 - error: zigbee.3 (2698316) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-06-24 09:20:30.366 - error: zigbee.3 (2698316) Failed to start Zigbee
2024-06-24 09:20:30.366 - error: zigbee.3 (2698316) Error herdsman start
2024-06-24 09:20:40.368 - info: zigbee.3 (2698316) Try to reconnect. 1 attempts left
2024-06-24 09:20:40.369 - info: zigbee.3 (2698316) Starting Zigbee npm ...
2024-06-24 09:20:40.387 - info: zigbee.3 (2698316) Installed Version: iobroker.zigbee@latest
2024-06-24 09:21:10.478 - error: zigbee.3 (2698316) Starting zigbee-herdsman problem : "Failure to connect"
2024-06-24 09:21:10.478 - error: zigbee.3 (2698316) Failed to start Zigbee
2024-06-24 09:21:10.478 - error: zigbee.3 (2698316) Error herdsman start
          arteck 1 Reply Last reply Reply Quote 0
          • arteck
            arteck Developer Most Active @ldittmar last edited by arteck

            @ldittmar zeigmal die adapter Einstellung

            das ist die 3-te instanz.. hast du die Einstellungen auch angepasst.. also unterschiedliche PanID und ExtPan.....

            ldittmar 1 Reply Last reply Reply Quote 0
            • ldittmar
              ldittmar Developer @arteck last edited by

              @arteck Jepp... alles angepasst, damit es keine Konflikte mit zigbee.0 gibt. Die zigbee.1 und zigbee.2 habe ich inzwischen gelöscht.

              einstellung.JPG

              arteck 1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active @ldittmar last edited by arteck

                @ldittmar hmmm.. geh mal mit der baudrate mal runnter.. sonst .. weiss ich auch nicht

                ldittmar 1 Reply Last reply Reply Quote 0
                • ldittmar
                  ldittmar Developer @arteck last edited by

                  @arteck Ich habe auf der zigbee2MQTT Seite das hier gefunden:

                  setting.JPG

                  Aber bei mir ist es auf false eingestellt. Wo kann ich das ändern?

                  Using zigbee-herdsman with settings: {"network":{"panID":6954,"extendedPanID":[73,117,188,10,37,62,139,138],"channelList":[25],"networkKey":[1,3,6,7,9,11,13,15,1,2,4,6,248,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_3/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_3/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyUSB0","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false}

                  arteck 1 Reply Last reply Reply Quote 0
                  • arteck
                    arteck Developer Most Active @ldittmar last edited by

                    @ldittmar garnicht..muss ich erst wenns gebraucht wird programmieren..

                    ich guck mal heute

                    ldittmar 1 Reply Last reply Reply Quote 1
                    • ldittmar
                      ldittmar Developer @arteck last edited by ldittmar

                      @arteck Ach... noch was: als Adapter steht da "ezsp" aber das wurde inzwischen durch "ember" ersetzt. Siehe Anleitung: https://www.zigbee2mqtt.io/guide/adapters/emberznet.html

                      firmware EMBER.JPG

                      Die neueste Version (7.4.1.0 ist EMBER) die alte...

                      firmware EZSP.JPG

                      ... 7.2.2.0 ist EZSP.

                      EDIT: Ich habe die alte Firmware 7.2.2.0 eingespielt und schon funktioniert alles. Es wäre aber trotzdem cool, wenn du "ember" und das mit dem "hardware flow control" true/false hinzufügen könntest. 🙂

                      arteck 1 Reply Last reply Reply Quote 0
                      • arteck
                        arteck Developer Most Active @ldittmar last edited by

                        @ldittmar sagte in SMLIGHT SLZB-07 mit dem EFR32MG21 Chip einbinden:

                        7.4.1.0

                        so hab es angepasst

                        0f85ca85-5699-4c7a-8b93-c4e3304ec555-grafik.png

                        und der wird auch auf true gesetzt bei den
                        beiden ezsp versionen

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post

                        Support us

                        ioBroker
                        Community Adapters
                        Donate

                        749
                        Online

                        31.7k
                        Users

                        79.8k
                        Topics

                        1.3m
                        Posts

                        2
                        10
                        731
                        Loading More Posts
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes
                        Reply
                        • Reply as topic
                        Log in to reply
                        Community
                        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                        The ioBroker Community 2014-2023
                        logo