Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Zigbee Adapter nach Stromausfall keine Verbindung (gelöst)

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Zigbee Adapter nach Stromausfall keine Verbindung (gelöst)

    This topic has been deleted. Only users with topic management privileges can see it.
    • crunchip
      crunchip Forum Testing Most Active @Homoran last edited by

      @homoran sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

      dann braucht man nichts anzupassen

      ja doch, das entsprechende Gerät muss doch in der LXC-config hinterlegt werden

      S 1 Reply Last reply Reply Quote 0
      • S
        stefu87_CH @crunchip last edited by

        @crunchip sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

        @homoran sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

        dann braucht man nichts anzupassen

        ja doch, das entsprechende Gerät muss doch in der LXC-config hinterlegt werden

        Habe ich so drin:
        421c4640-9267-4aed-825b-dd999b21bc86-grafik.png

        DJMarc75 crunchip 2 Replies Last reply Reply Quote 0
        • DJMarc75
          DJMarc75 @stefu87_CH last edited by

          @stefu87_ch

          Falls das 1 bei "unpriviliged" in Deinem Screenshot bedeutet dass der LXC "priviligiert" ist dann klappt das mit dem ganzen Durchreichen eh nicht.

          Homoran S 2 Replies Last reply Reply Quote 0
          • Homoran
            Homoran Global Moderator Administrators @DJMarc75 last edited by

            @djmarc75 1 ist üblicherweise true

            1 Reply Last reply Reply Quote 0
            • S
              stefu87_CH @DJMarc75 last edited by

              @djmarc75 sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

              @stefu87_ch

              Falls das 1 bei "unpriviliged" in Deinem Screenshot bedeutet dass der LXC "priviligiert" ist dann klappt das mit dem ganzen Durchreichen eh nicht.

              a1f9bfae-526f-428d-8137-dbca7ce946f3-grafik.png

              DJMarc75 1 Reply Last reply Reply Quote 0
              • DJMarc75
                DJMarc75 @stefu87_CH last edited by DJMarc75

                @stefu87_ch na dann 🙂

                edit: ist unpreviligiert

                1 Reply Last reply Reply Quote 0
                • crunchip
                  crunchip Forum Testing Most Active @stefu87_CH last edited by

                  @stefu87_ch was zeigt dann im LXC

                  lsusb
&
ls -l /dev
                  S 1 Reply Last reply Reply Quote 0
                  • S
                    stefu87_CH @crunchip last edited by

                    @crunchip sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

                    admin@Iobroker:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
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 004: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth
Bus 001 Device 010: ID 1a86:55d4 QinHeng Electronics SONOFF Zigbee 3.0 USB Dongle Plus V2
Bus 001 Device 008: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
admin@Iobroker:~$ ls -l /dev
total 0
crw--w---- 1 root   tty     136, 0 Jul  2 20:13 console
lrwxrwxrwx 1 root   root        11 Jul  2 20:13 core -> /proc/kcore
lrwxrwxrwx 1 root   root        13 Jul  2 20:13 fd -> /proc/self/fd
crw-rw-rw- 1 nobody nogroup   1, 7 Jun 28 19:56 full
lrwxrwxrwx 1 root   root        12 Jul  2 20:13 initctl -> /run/initctl
lrwxrwxrwx 1 root   root        28 Jul  2 20:13 log -> /run/systemd/journal/dev-log
drwxrwxrwt 2 nobody nogroup     40 Jul  2 20:13 mqueue
crw-rw-rw- 1 nobody nogroup   1, 3 Jun 28 19:56 null
crw-rw-rw- 1 root   root      5, 2 Jul  3 17:51 ptmx
drwxr-xr-x 2 root   root         0 Jul  2 20:13 pts
crw-rw-rw- 1 nobody nogroup   1, 8 Jun 28 19:56 random
drwxr-xr-x 3 root   root        60 Jul  2 20:13 serial
drwxrwxrwt 2 root   root        40 Jul  2 20:13 shm
lrwxrwxrwx 1 root   root        15 Jul  2 20:13 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root   root        15 Jul  2 20:13 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root   root        15 Jul  2 20:13 stdout -> /proc/self/fd/1
crw-rw-rw- 1 nobody nogroup   5, 0 Jul  2 20:01 tty
crw------- 1 admin  tty     136, 1 Jul  3 17:51 tty1
crw--w---- 1 root   tty     136, 2 Jul  2 20:13 tty2
crw-rw-rw- 1 nobody nogroup 166, 0 Jul  2 20:21 ttyACM0
crw-rw-rw- 1 nobody nogroup   1, 9 Jun 28 19:56 urandom
crw-rw-rw- 1 nobody nogroup   1, 5 Jun 28 19:56 zero
admin@Iobroker:~$
                    crunchip 1 Reply Last reply Reply Quote 0
                    • crunchip
                      crunchip Forum Testing Most Active @stefu87_CH last edited by

                      @stefu87_ch sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

                      ttyACM0

                      Wähle das doch mal im Zigbee Adapter aus und guck was passiert

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        stefu87_CH @crunchip last edited by

                        @crunchip sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

                        @stefu87_ch sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

                        ttyACM0

                        Wähle das doch mal im Zigbee Adapter aus und guck was passiert

                        Fehler im Log:

                        024-07-03 18:35:36.622 - error: zigbee.0 (220819) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
2024-07-03 18:35:36.715 - info: zigbee.0 (220819) List of port: [{"path":"/dev/ttyACM0"},{"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"}]
2024-07-03 18:35:48.500 - error: zigbee.0 (220819) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
2024-07-03 18:35:48.500 - error: zigbee.0 (220819) Failed to start Zigbee
2024-07-03 18:35:48.500 - error: zigbee.0 (220819) Error herdsman start
2024-07-03 18:35:58.502 - info: zigbee.0 (220819) Try to reconnect. 1 attempts left
2024-07-03 18:35:58.502 - info: zigbee.0 (220819) Starting Zigbee npm ...
2024-07-03 18:35:58.506 - info: zigbee.0 (220819) Installed Version: iobroker.zigbee@1.10.3
2024-07-03 18:35:58.596 - error: zigbee.0 (220819) Starting zigbee-herdsman problem : "Error Resource temporarily unavailable Cannot lock port"
2024-07-03 18:35:58.597 - error: zigbee.0 (220819) Failed to start Zigbee
2024-07-03 18:35:58.597 - error: zigbee.0 (220819) Error herdsman start

                        Einstellungen im Adapter:
                        669d90d3-2eba-4c7d-aedd-d1e5b94be1c2-grafik.png

                        crunchip Thomas Braun 2 Replies Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @stefu87_CH last edited by

                          @stefu87_ch sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

                          "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"

                          ist da nicht der falsche Typ angewählt?

                          1 Reply Last reply Reply Quote 1
                          • Thomas Braun
                            Thomas Braun Most Active @stefu87_CH last edited by

                            @stefu87_ch

                            Der QinHeng Electronics SONOFF Zigbee 3.0 USB Dongle Plus V2
                            läuft mit großer Sicherheit mit dem Silicon Labs EZSP-Stack.

                            S 1 Reply Last reply Reply Quote 0
                            • S
                              stefu87_CH @Thomas Braun last edited by

                              @thomas-braun sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

                              @stefu87_ch

                              Der QinHeng Electronics SONOFF Zigbee 3.0 USB Dongle Plus V2
                              läuft mit großer Sicherheit mit dem Silicon Labs EZSP-Stack.

                              Habe jetzt mal geändert und erhalte nun diese Meldungen:

                              2024-07-04 17:15:48.503 - info: zigbee.0 (443010) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.15.0, js-controller: 5.0.19
2024-07-04 17:15:48.528 - info: zigbee.0 (443010) delete old Backup files. keep only last 10
2024-07-04 17:15:48.529 - info: zigbee.0 (443010) Starting Zigbee npm ...
2024-07-04 17:15:48.684 - info: zigbee.0 (443010) Installed Version: iobroker.zigbee@1.10.3
2024-07-04 17:15:56.205 - info: host.Iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
2024-07-04 17:15:56.207 - info: zigbee.0 (443010) Got terminate signal TERMINATE_YOURSELF
2024-07-04 17:15:56.207 - info: zigbee.0 (443010) cleaned everything up...
2024-07-04 17:15:56.208 - info: zigbee.0 (443010) Zigbee: disabling joining new devices.
2024-07-04 17:15:56.256 - warn: zigbee.0 (443010) Failed to stop zigbee during startup
2024-07-04 17:15:56.256 - info: zigbee.0 (443010) terminating
2024-07-04 17:15:56.257 - info: zigbee.0 (443010) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-04 17:15:56.319 - info: host.Iobroker stopInstance system.adapter.zigbee.0 send kill signal
2024-07-04 17:15:56.708 - info: zigbee.0 (443010) terminating
2024-07-04 17:15:56.813 - info: host.Iobroker instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-07-04 17:15:59.367 - info: host.Iobroker instance system.adapter.zigbee.0 started with pid 443104
2024-07-04 17:16:00.660 - info: zigbee.0 (443104) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.15.0, js-controller: 5.0.19
2024-07-04 17:16:00.683 - info: zigbee.0 (443104) delete old Backup files. keep only last 10
2024-07-04 17:16:00.683 - info: zigbee.0 (443104) Starting Zigbee npm ...
2024-07-04 17:16:00.827 - info: zigbee.0 (443104) Installed Version: iobroker.zigbee@1.10.3
2024-07-04 17:16:00.854 - info: admin.0 (436) <== Disconnect system.user.admin from ::ffff:192.168.0.20
2024-07-04 17:16:04.259 - error: zigbee.0 (443104) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-04 17:16:04.260 - error: zigbee.0 (443104) Failed to start Zigbee
2024-07-04 17:16:04.260 - error: zigbee.0 (443104) Error herdsman start
2024-07-04 17:16:14.261 - info: zigbee.0 (443104) Try to reconnect. 1 attempts left
2024-07-04 17:16:14.261 - info: zigbee.0 (443104) Starting Zigbee npm ...
2024-07-04 17:16:14.265 - info: zigbee.0 (443104) Installed Version: iobroker.zigbee@1.10.3
2024-07-04 17:16:44.375 - error: zigbee.0 (443104) Starting zigbee-herdsman problem : "Failure to connect"
2024-07-04 17:16:44.376 - error: zigbee.0 (443104) Failed to start Zigbee
2024-07-04 17:16:44.376 - error: zigbee.0 (443104) Error herdsman start
2024-07-04 17:18:52.678 - info: host.Iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
2024-07-04 17:18:52.680 - info: zigbee.0 (443104) Got terminate signal TERMINATE_YOURSELF
2024-07-04 17:18:52.680 - info: zigbee.0 (443104) cleaned everything up...
2024-07-04 17:18:52.681 - info: zigbee.0 (443104) Zigbee: disabling joining new devices.
2024-07-04 17:18:52.689 - warn: zigbee.0 (443104) Failed to stop zigbee during startup
2024-07-04 17:18:52.689 - info: zigbee.0 (443104) terminating
2024-07-04 17:18:52.689 - info: zigbee.0 (443104) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-04 17:18:52.719 - info: host.Iobroker stopInstance system.adapter.zigbee.0 send kill signal
2024-07-04 17:18:53.182 - info: zigbee.0 (443104) terminating
2024-07-04 17:18:53.243 - info: host.Iobroker instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-07-04 17:18:55.777 - info: host.Iobroker instance system.adapter.zigbee.0 started with pid 443511
2024-07-04 17:18:57.105 - info: zigbee.0 (443511) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.15.0, js-controller: 5.0.19
2024-07-04 17:18:57.129 - info: zigbee.0 (443511) delete old Backup files. keep only last 10
2024-07-04 17:18:57.129 - info: zigbee.0 (443511) Starting Zigbee npm ...
2024-07-04 17:18:57.269 - info: zigbee.0 (443511) Installed Version: iobroker.zigbee@1.10.3
2024-07-04 17:19:00.704 - error: zigbee.0 (443511) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-04 17:19:00.704 - error: zigbee.0 (443511) Failed to start Zigbee
2024-07-04 17:19:00.705 - error: zigbee.0 (443511) Error herdsman start

                              Ich vermute, die PID stimmt nicht, aber woher weiss ich welche das gebraucht wird?

                              Thomas Braun 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @stefu87_CH last edited by

                                @stefu87_ch

                                Früher standen mal beide IDs im Log.
                                Ich weiß nicht warum und wann die rausgeflogen wurden.
                                Du kannst aber hilfsweise mal die 'falschen' Einstellungen in den Einstellungen der Instanz erzwingen.

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  stefu87_CH @Thomas Braun last edited by

                                  @thomas-braun sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

                                  @stefu87_ch

                                  Du kannst aber hilfsweise mal die 'falschen' Einstellungen in den Einstellungen der Instanz erzwingen.

                                  Also du meinst eine falsche Pan ID eintragen?
                                  3bbe7c99-acd4-477c-ae44-e229290ef370-grafik.png

                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @stefu87_CH last edited by

                                    @stefu87_ch

                                    Ich meinte eher die Einstellung in der letzten Zeile:

                                    a4ded092-dd09-4c1a-b513-549b39c58329-grafik.png

                                    S 1 Reply Last reply Reply Quote 0
                                    • S
                                      stefu87_CH @Thomas Braun last edited by

                                      @thomas-braun sagte in Zigbee Adapter nach Stromausfall keine Verbindung:

                                      @stefu87_ch

                                      Ich meinte eher die Einstellung in der letzten Zeile:

                                      a4ded092-dd09-4c1a-b513-549b39c58329-grafik.png

                                      2024-07-04 18:02:03.015 - info: zigbee.0 (450060) Got terminate signal TERMINATE_YOURSELF
2024-07-04 18:02:03.015 - info: zigbee.0 (450060) cleaned everything up...
2024-07-04 18:02:03.017 - info: zigbee.0 (450060) Zigbee: disabling joining new devices.
2024-07-04 18:02:03.024 - warn: zigbee.0 (450060) Failed to stop zigbee during startup
2024-07-04 18:02:03.025 - info: zigbee.0 (450060) terminating
2024-07-04 18:02:03.025 - info: zigbee.0 (450060) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-04 18:02:03.081 - info: host.Iobroker stopInstance system.adapter.zigbee.0 send kill signal
2024-07-04 18:02:03.516 - info: zigbee.0 (450060) terminating
2024-07-04 18:02:03.577 - info: host.Iobroker instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-07-04 18:02:06.143 - info: host.Iobroker instance system.adapter.zigbee.0 started with pid 450620
2024-07-04 18:02:07.742 - info: zigbee.0 (450620) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.15.0, js-controller: 5.0.19
2024-07-04 18:02:07.765 - info: zigbee.0 (450620) delete old Backup files. keep only last 10
2024-07-04 18:02:07.766 - info: zigbee.0 (450620) Starting Zigbee npm ...
2024-07-04 18:02:07.915 - info: zigbee.0 (450620) Installed Version: iobroker.zigbee@1.10.3
2024-07-04 18:02:11.344 - error: zigbee.0 (450620) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-04 18:02:11.344 - error: zigbee.0 (450620) Failed to start Zigbee
2024-07-04 18:02:11.344 - error: zigbee.0 (450620) Error herdsman start
2024-07-04 18:02:21.346 - info: zigbee.0 (450620) Try to reconnect. 1 attempts left
2024-07-04 18:02:21.346 - info: zigbee.0 (450620) Starting Zigbee npm ...
2024-07-04 18:02:21.352 - info: zigbee.0 (450620) Installed Version: iobroker.zigbee@1.10.3
                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        stefu87_CH last edited by

                                        Habe mir jetzt nochmals die Zeit genommen, und wirklich alles neu eingestellt.
                                        Jetzt plötzlich hat die Verbindung einwandfrei geklappt.
                                        Habe den Adapter mit den Grundeinstellungen belassen und auf einmal ist er grün geworden.

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

                                        Support us

                                        ioBroker
                                        Community Adapters
                                        Donate

                                        890
                                        Online

                                        31.9k
                                        Users

                                        80.2k
                                        Topics

                                        1.3m
                                        Posts

                                        9
                                        148
                                        10826
                                        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