Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Installation
    5. ioBroker android, slzb-06 LAN coordinator installation

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    ioBroker android, slzb-06 LAN coordinator installation

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      thaiyoda @Asgothian last edited by

      @asgothian ls /opt/iobroker/iobroker-data/zigbee_0 zeigt mir > LocalOverrides.json

      Asgothian 1 Reply Last reply Reply Quote 0
      • Asgothian
        Asgothian Developer @thaiyoda last edited by

        @thaiyoda sagte in ioBroker android, slzb-06 LAN coordinator installation:

        @asgothian ls /opt/iobroker/iobroker-data/zigbee_0 zeigt mir > LocalOverrides.json

        Bist du der Anleitung aus der im Readme zur 3.0 verlinkten Doku gefolgt ?

        T 1 Reply Last reply Reply Quote 0
        • T
          thaiyoda @Asgothian last edited by

          @asgothian said in ioBroker android, slzb-06 LAN coordinator installation:

          Bist du der Anleitung aus der im Readme zur 3.0 verlinkten Doku gefolgt ?

          ja, und jetzt haenge ich hier:
          'Find out the path of the coordinator : ls -la /dev/serial/by-id/
          ioBroker -> install ZigBee adapter, here Version 1.8.10
          This will install all the necessary software parts (converter and adapter).
          Open adapter -> -> Enter the previously determined path of the coordinator with the addition /dev/serial/by-id/:'

          Mein slzb-06 haengt am LAN und hat eine eigene IP
          '# Pay attention, if you use the Z2M addon for HA, it is better to edit Z2M addon yaml configuration file directly (Select the 3 dot menu in the upper right corner → "Edit in YAML")
          serial:

          Location of SLZB-06

          port: tcp://192.168.0.114:6638
          baudrate: 115200
          adapter: zstack

          Disable green led?

          disable_led: false

          Set output power to max 20

          advanced:
          transmit_power: 20
          '

          T 1 Reply Last reply Reply Quote 0
          • T
            thaiyoda @thaiyoda last edited by

            @thaiyoda
            Hab mal bei comport das hier eingetragen: tcp://192.168.0.114:6638

            Und dann auf den Startbutton gedrueckt.

            Protokoll;
            overriding zigbee options with:
            extPanID : 6a4cb2abde9638b6
            panID : 5262
            channel : 15
            port : tcp://192.168.0.114:6638
            adapterType : zstack
            baudRate : 115200
            precfgkey : 01030507090B0D0F00020406080A0C0D
            flowCTRL : false
            Starting Adapter npm ...
            Installed Version: iobroker.zigbee@3.0.0 (Converters 23.25.0 Herdsman 3.5.1)
            Starting zigbee-herdsman...
            Zigbee-Herdsman started successfully with Coordinator firmware version: zStack3x0 : 20221226 (2-1.2.7.1)
            Network parameters: panID=5262 channel=15 extendedPanID=f734df31004b1200
            Unable to disable LED, unsupported function.
            No devices are currently joined.
            Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms
            Closing network.

            T 1 Reply Last reply Reply Quote 0
            • T
              thaiyoda @thaiyoda last edited by Homoran

              @thaiyoda und @asgothian
              scheint weiter nicht zu funktionioeren.
              Sollte ich alles noch mal neu installieren?
              Alledings komme ich mit der Doku fuer den slzb-06 bzw. ZigBee Adapter fuer ioBroker nicht klar. Mein slzb-06 laeuft ueber LAN und nicht USB am Raspi. Die Doku scheint fuer USB?

              Hier mal das Lopgf v

              zigbee.0
2025-04-12 18:13:05.180	debug	Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2025_04_12-18_13_05.tar.gz success

zigbee.0
2025-04-12 18:13:05.147	info	--- creating device debug ---

zigbee.0
2025-04-12 18:13:05.073	info	--> transmitPower : normal

zigbee.0
2025-04-12 18:13:05.065	info	init localConfig

zigbee.0
2025-04-12 18:13:05.063	info	Adapter ready - starting subsystems. Adapter is running in debug mode.

zigbee.0
2025-04-12 18:13:05.012	info	starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6

zigbee.0
2025-04-12 18:13:04.788	debug	Plugin sentry Do not initialize Plugin (enabled=false)

zigbee.0
2025-04-12 18:13:04.752	debug	States connected to redis: 127.0.0.1:9000

zigbee.0
2025-04-12 18:13:04.740	debug	States create User PubSub Client

zigbee.0
2025-04-12 18:13:04.738	debug	States create System PubSub Client

zigbee.0
2025-04-12 18:13:04.712	debug	Redis States: Use Redis connection: 127.0.0.1:9000

zigbee.0
2025-04-12 18:13:04.694	debug	Objects connected to redis: 127.0.0.1:9001

zigbee.0
2025-04-12 18:13:04.684	debug	Objects client initialize lua scripts

zigbee.0
2025-04-12 18:13:04.658	debug	Objects create User PubSub Client

zigbee.0
2025-04-12 18:13:04.656	debug	Objects create System PubSub Client

zigbee.0
2025-04-12 18:13:04.653	debug	Objects client ready ... initialize now

zigbee.0
2025-04-12 18:13:04.623	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001

host.raspberrypi
2025-04-12 18:13:01.379	info	instance system.adapter.zigbee.0 in version "3.0.0" started with pid 4915

host.raspberrypi
2025-04-12 18:13:00.259	info	"system.adapter.zigbee.0" enabled

host.raspberrypi
2025-04-12 18:12:45.150	info	instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

zigbee.0
2025-04-12 18:12:45.056	info	terminating

host.raspberrypi
2025-04-12 18:12:44.587	info	stopInstance system.adapter.zigbee.0 send kill signal

zigbee.0
2025-04-12 18:12:44.563	info	terminating

zigbee.0
2025-04-12 18:12:44.562	warn	Failed to stop zigbee during startup

zigbee.0
2025-04-12 18:12:44.552	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reasonom letzten Start.

zigbee.0
2025-04-12 18:13:05.180	debug	Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2025_04_12-18_13_05.tar.gz success

zigbee.0
2025-04-12 18:13:05.147	info	--- creating device debug ---

zigbee.0
2025-04-12 18:13:05.073	info	--> transmitPower : normal

zigbee.0
2025-04-12 18:13:05.065	info	init localConfig

zigbee.0
2025-04-12 18:13:05.063	info	Adapter ready - starting subsystems. Adapter is running in debug mode.

zigbee.0
2025-04-12 18:13:05.012	info	starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6

zigbee.0
2025-04-12 18:13:04.788	debug	Plugin sentry Do not initialize Plugin (enabled=false)

zigbee.0
2025-04-12 18:13:04.752	debug	States connected to redis: 127.0.0.1:9000

zigbee.0
2025-04-12 18:13:04.740	debug	States create User PubSub Client

zigbee.0
2025-04-12 18:13:04.738	debug	States create System PubSub Client

zigbee.0
2025-04-12 18:13:04.712	debug	Redis States: Use Redis connection: 127.0.0.1:9000

zigbee.0
2025-04-12 18:13:04.694	debug	Objects connected to redis: 127.0.0.1:9001

zigbee.0
2025-04-12 18:13:04.684	debug	Objects client initialize lua scripts

zigbee.0
2025-04-12 18:13:04.658	debug	Objects create User PubSub Client

zigbee.0
2025-04-12 18:13:04.656	debug	Objects create System PubSub Client

zigbee.0
2025-04-12 18:13:04.653	debug	Objects client ready ... initialize now

zigbee.0
2025-04-12 18:13:04.623	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001

host.raspberrypi
2025-04-12 18:13:01.379	info	instance system.adapter.zigbee.0 in version "3.0.0" started with pid 4915

host.raspberrypi
2025-04-12 18:13:00.259	info	"system.adapter.zigbee.0" enabled

host.raspberrypi
2025-04-12 18:12:45.150	info	instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

zigbee.0
2025-04-12 18:12:45.056	info	terminating

host.raspberrypi
2025-04-12 18:12:44.587	info	stopInstance system.adapter.zigbee.0 send kill signal

zigbee.0
2025-04-12 18:12:44.563	info	terminating

zigbee.0
2025-04-12 18:12:44.562	warn	Failed to stop zigbee during startup

zigbee.0
2025-04-12 18:12:44.552	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

              MOD-EDIT: Code in code-tags gesetzt!

              Asgothian 1 Reply Last reply Reply Quote 0
              • Asgothian
                Asgothian Developer @thaiyoda last edited by

                @thaiyoda

                • logs immer in code tags posten
                • Start Versuche in debug bringen nicht mehr info als die Ausgaben aus dem vorherigen Post.
                • Bitte im UI das nvbackup löschen und erneut versuchen das zigbee subsystem zu starten.

                A.

                T 1 Reply Last reply Reply Quote 0
                • T
                  thaiyoda @Asgothian last edited by thaiyoda

                  @asgothian
                  nvbackup geloescht. Das hier ist log. so correct mit code tag?
                  der Zigbee sieht jetzt im Instance Menu gruen aus.

                  • Connected to host (gruen)
                  • Heartbeat (gruen)
                  • Connected to device or service (gruen)

                  und unter Zigbee > Devices ist der slzb-06 mit seiner IP zu sehen

                  2025-04-12 20:12:26.421 - info: admin.0 (3355) ==> Connected system.user.admin from ::ffff:192.168.0.113
2025-04-12 20:12:27.010 - warn: zigbee.0 (4915) readNvBackup called
2025-04-12 20:12:27.013 - warn: zigbee.0 (4915) readNvBackup returns {"channel":15,"precfgkey":"01030507090b0d0f00020406080a0c0d","extPanID":"f734df31004b1200","panID":5262}
2025-04-12 20:12:27.017 - debug: zigbee.0 (4915) get groupes called with {"command":"getGroups","message":{},"from":"system.adapter.admin.0","callback":{"message":{},"id":129,"ack":false,"time":1744463546851},"_id":75546415}
2025-04-12 20:12:27.131 - debug: zigbee.0 (4915) get groupes called with {"command":"getGroups","message":{},"from":"system.adapter.admin.0","callback":{"message":{},"id":129,"ack":false,"time":1744463546851},"_id":75546415} disconnected
2025-04-12 20:12:27.330 - info: zigbee.0 (4915) List of port: []
2025-04-12 20:12:56.694 - info: zigbee.0 (4915) --> transmitPower : normal
2025-04-12 20:12:56.705 - info: zigbee.0 (4915) Starting Adapter npm ...
2025-04-12 20:12:56.734 - info: zigbee.0 (4915) Installed Version: iobroker.zigbee@3.0.0 (Converters 23.25.0 Herdsman 3.5.1)
2025-04-12 20:12:56.737 - debug: zigbee.0 (4915) Starting zigbee-herdsman...
2025-04-12 20:12:56.738 - info: zigbee.0 (4915) Starting Zigbee-Herdsman
2025-04-12 20:13:36.007 - info: zigbee.0 (4915) Zigbee-Herdsman started successfully with Coordinator firmware version: zStack3x0 : 20221226 (2-1.2.7.1)
2025-04-12 20:13:36.031 - debug: zigbee.0 (4915) Network parameters: panID=5262 channel=15 extendedPanID=6a4cb2abde9638b6
2025-04-12 20:13:36.033 - info: zigbee.0 (4915) Unable to disable LED, unsupported function.
2025-04-12 20:13:36.035 - info: zigbee.0 (4915) No devices are currently joined.
2025-04-12 20:13:36.040 - info: zigbee.0 (4915) Zigbee started
2025-04-12 20:13:36.150 - debug: zigbee.0 (4915) get groupes called with undefined
2025-04-12 20:13:36.202 - debug: zigbee.0 (4915) get groupes called with no object connected
2025-04-12 20:13:36.203 - debug: zigbee.0 (4915) getGroups result: {} ( [])
2025-04-12 20:13:36.203 - debug: zigbee.0 (4915) sync Groups called: groups is {}
2025-04-12 20:13:55.223 - info: admin.0 (3355) <== Disconnect system.user.admin from ::ffff:192.168.0.113
                  Asgothian 1 Reply Last reply Reply Quote 0
                  • Asgothian
                    Asgothian Developer @thaiyoda last edited by

                    @thaiyoda sagte in ioBroker android, slzb-06 LAN coordinator installation:

                    nvbackup geloescht. Das hier ist log. so correct mit code tag?
                    der Zigbee sieht jetzt im Instance Menu gruen aus.

                    So ist es lesbar.

                    Jetzt wo der Adapter grün wird solltest du noch den Haken bei 'start the zigbee network automatically' setzen.

                    A.

                    T 1 Reply Last reply Reply Quote 0
                    • Samson71
                      Samson71 Global Moderator last edited by

                      @thaiyoda
                      Würdest Du Dir bitte das Benutzen von Code-Tags angewöhnen für Logs etc.? Das Mitlesen ist ja gruselig so.

                      T 1 Reply Last reply Reply Quote 0
                      • T
                        thaiyoda @Asgothian last edited by

                        @asgothian Danke für deine Hilfe.
                        Wenn die ersten Smart Switch hier ankommen, hoffe ich, dass diese auch schnell erkannt werden.
                        Sorry für das nicht code tagen. War mir nicht bewusst, dass es diese Funktion gibt.

                        1 Reply Last reply Reply Quote 0
                        • T
                          thaiyoda @Samson71 last edited by

                          @samson71 danke fuer deinen extra Hinweis.

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

                          Support us

                          ioBroker
                          Community Adapters
                          Donate

                          946
                          Online

                          31.7k
                          Users

                          79.7k
                          Topics

                          1.3m
                          Posts

                          4
                          36
                          1269
                          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