Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Noch ein Zigbee Problem....

    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

    Noch ein Zigbee Problem....

    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      brokeling @crunchip last edited by

      @crunchip
      würde mich auch interessieren...
      wie komme ich an die motioneye benutzeroberfläche?
      bd39c7c8-e421-4f70-8b8b-66d484245137-image.png

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

        @brokeling eigentlich

        http://deine IP:8765

        ansonsten könntest du motioneye auch einfach auschalten ohne zu deinstallieren

        sudo systemctl stop motioneye
sudo systemctl disable motioneye
sudo systemctl daemon-reload
        B 1 Reply Last reply Reply Quote 0
        • B
          brokeling @crunchip last edited by

          @crunchip
          ahem, was ist meine IP???

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

            @brokeling ernsthaft die Frage?
            na deine Ip von deinem Pi

            B 1 Reply Last reply Reply Quote 0
            • B
              brokeling @crunchip last edited by brokeling

              @crunchip
              ich glaube ich habe kein motion...

              pi@raspi:~ $ sudo systemctl stop motioneye
Failed to stop motioneye.service: Unit motioneye.service not loaded.
pi@raspi:~ $ sudo systemctl disable motioneye
Failed to disable unit: Unit file motioneye.service does not exist.
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • B
                brokeling @Thomas Braun last edited by

                @thomas-braun said in Noch ein Zigbee Problem....:

                @brokeling

                motion

                
tcp        0      0 127.0.0.1:8081          0.0.0.0:*               LISTEN      119        15504      393/motion

                wo ist das her und was könnte es sein?

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

                  @brokeling sagte in Noch ein Zigbee Problem....:

                  0.0.0.0:8083 0.0.0.0:* LISTEN 119 18490 568/motion

                  @brokeling sagte in Noch ein Zigbee Problem....:

                  127.0.0.1:8081 0.0.0.0:* LISTEN 119 15504 393/motion

                  keine Ahnung was bei dir da läuft, einmal so einmal so🤔

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

                    @brokeling

                    Der Service dürfte 'motion' heißen.

                    Also

                    sudo systemctl stop motion
sudo systemctl disable motion
sudo systemctl mask motion
                    crunchip B 2 Replies Last reply Reply Quote 0
                    • Ro75
                      Ro75 last edited by

                      Also wenn es ein Backup vom ioBroker gäbe, wäre dann die Kiste neu aufsetzen nicht schneller?

                      Ro75.

                      B 1 Reply Last reply Reply Quote 0
                      • B
                        brokeling @Ro75 last edited by

                        @ro75 said in Noch ein Zigbee Problem....:

                        Also wenn es ein Backup vom ioBroker gäbe, wäre dann die Kiste neu aufsetzen nicht schneller?

                        Ro75.

                        Manno so schlecht ist doch mein System nicht, oder???
                        Dachte immer das ist sauber.

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

                          @thomas-braun eingeschalten und gestartet wird aber eigentlich motioneye, somit bin ich von motioneye zum stoppen und ausschalten, ausgegangen

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Ro75
                            Ro75 @brokeling last edited by

                            @brokeling motioneye, Ports, Beta, Hieroglyphen, nodejs, .......

                            1 Reply Last reply Reply Quote 0
                            • B
                              brokeling @Thomas Braun last edited by brokeling

                              @thomas-braun said in Noch ein Zigbee Problem....:

                              @brokeling

                              Der Service dürfte 'motion' heißen.

                              Also

                              sudo systemctl stop motion
sudo systemctl disable motion
sudo systemctl mask motion

                              Admin läuft wieder :)!!!

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

                                @crunchip

                                Der Server heißt aber 'motion'. Und der sitzt (bzw. saß) auf dem Port.

                                crunchip 1 Reply Last reply Reply Quote 0
                                • B
                                  brokeling @brokeling last edited by

                                  Zigbee macht noch Zicken.

                                  2023-08-17 19:31:16.406  - info: host.raspi stopInstance system.adapter.zigbee.0 (force=false, process=true)
2023-08-17 19:31:16.412  - info: host.raspi stopInstance system.adapter.zigbee.0 send kill signal
2023-08-17 19:31:16.414  - info: zigbee.0 (2106) Got terminate signal TERMINATE_YOURSELF
2023-08-17 19:31:16.418  - info: zigbee.0 (2106) cleaned everything up...
2023-08-17 19:31:17.190  - info: zigbee.0 (2106) Zigbee: disabling joining new devices.
2023-08-17 19:31:17.225  - warn: zigbee.0 (2106) Failed to stop zigbee during startup
2023-08-17 19:31:17.226  - info: zigbee.0 (2106) terminating
2023-08-17 19:31:17.228  - info: zigbee.0 (2106) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-08-17 19:31:17.229  - info: zigbee.0 (2106) terminating
2023-08-17 19:31:17.294  - info: zigbee.0 (2106) debug devices set to []
2023-08-17 19:31:17.418  - info: host.raspi stopInstance system.adapter.zigbee.0 killing pid 2106
2023-08-17 19:31:16.418  - info: zigbee.0 (2106) cleaned everything up...
2023-08-17 19:31:17.190  - info: zigbee.0 (2106) Zigbee: disabling joining new devices.
2023-08-17 19:31:17.225  - warn: zigbee.0 (2106) Failed to stop zigbee during startup
2023-08-17 19:31:17.226  - info: zigbee.0 (2106) terminating
2023-08-17 19:31:17.228  - info: zigbee.0 (2106) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-08-17 19:31:17.229  - info: zigbee.0 (2106) terminating
2023-08-17 19:31:17.294  - info: zigbee.0 (2106) debug devices set to []
2023-08-17 19:31:17.418  - info: host.raspi stopInstance system.adapter.zigbee.0 killing pid 2106
2023-08-17 19:31:17.968  - info: host.raspi instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-08-17 19:31:19.710  - info: host.raspi instance system.adapter.zigbee.0 started with pid 15172
2023-08-17 19:31:25.073  - info: zigbee.0 (15172) starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 5.0.11
2023-08-17 19:31:25.244  - info: zigbee.0 (15172) delete old Backup files. keep only last 10
2023-08-17 19:31:25.247  - info: zigbee.0 (15172) Starting Zigbee  npm ...
2023-08-17 19:31:25.073  - info: zigbee.0 (15172) starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 5.0.11
2023-08-17 19:31:25.244  - info: zigbee.0 (15172) delete old Backup files. keep only last 10
2023-08-17 19:31:25.247  - info: zigbee.0 (15172) Starting Zigbee  npm ...
2023-08-17 19:31:25.995  - error: zigbee.0 (15172) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100GB8-if00'"
2023-08-17 19:31:25.996  - error: zigbee.0 (15172) Failed to start Zigbee
2023-08-17 19:31:25.997  - error: zigbee.0 (15172) Error herdsman start
2023-08-17 19:31:25.999  - info: zigbee.0 (15172) Installed Version: iobroker.zigbee@1.8.23
2023-08-17 19:31:25.995  - error: zigbee.0 (15172) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100GB8-if00'"
2023-08-17 19:31:25.996  - error: zigbee.0 (15172) Failed to start Zigbee
2023-08-17 19:31:25.997  - error: zigbee.0 (15172) Error herdsman start
2023-08-17 19:31:25.999  - info: zigbee.0 (15172) Installed Version: iobroker.zigbee@1.8.23
2023-08-17 19:31:35.999  - info: zigbee.0 (15172) Try to reconnect. 1 attempts left
2023-08-17 19:31:36.000  - info: zigbee.0 (15172) Starting Zigbee  npm ...
2023-08-17 19:31:36.030  - error: zigbee.0 (15172) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100GB8-if00'"
2023-08-17 19:31:36.032  - error: zigbee.0 (15172) Failed to start Zigbee
2023-08-17 19:31:36.034  - error: zigbee.0 (15172) Error herdsman start
2023-08-17 19:31:36.035  - info: zigbee.0 (15172) Installed Version: iobroker.zigbee@1.8.23
2023-08-17 19:31:35.999  - info: zigbee.0 (15172) Try to reconnect. 1 attempts left
2023-08-17 19:31:36.000  - info: zigbee.0 (15172) Starting Zigbee  npm ...
2023-08-17 19:31:36.030  - error: zigbee.0 (15172) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.26__Embed_with_CMSIS-DAP_L1100GB8-if00'"
2023-08-17 19:31:36.032  - error: zigbee.0 (15172) Failed to start Zigbee
2023-08-17 19:31:36.034  - error: zigbee.0 (15172) Error herdsman start
2023-08-17 19:31:36.035  - info: zigbee.0 (15172) Installed Version: iobroker.zigbee@1.8.23
2023-08-17 19:32:05.512  - info: javascript.0 (1204)
                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • crunchip
                                    crunchip Forum Testing Most Active @Thomas Braun last edited by

                                    @thomas-braun sagte in Noch ein Zigbee Problem....:

                                    auf dem Port

                                    besser gesagt seine cam

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

                                      @brokeling

                                      find /dev/serial/by-id/ -maxdepth 1 -mindepth 1

                                      sagt?

                                      B 1 Reply Last reply Reply Quote 0
                                      • B
                                        brokeling @Thomas Braun last edited by brokeling

                                        @thomas-braun

                                        pi@raspi:~ $ find /dev/serial/by-id/ -maxdepth 1 -mindepth 1
find: ‘/dev/serial/by-id/’: Datei oder Verzeichnis nicht gefunden

                                        was ist jetzt mit dem serial port?

                                        pi@raspi:~ $ ls -la /dev/serial/by-id/
ls: Zugriff auf '/dev/serial/by-id/' nicht möglich: Datei oder Verzeichnis nicht gefunden
                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @brokeling last edited by

                                          @brokeling

                                          sudo apt update
apt policy udev
                                          B 1 Reply Last reply Reply Quote 0
                                          • B
                                            brokeling @Thomas Braun last edited by

                                            @thomas-braun

                                            pi@raspi:~ $ sudo apt update
OK:1 http://phoscon.de/apt/deconz bullseye InRelease
Holen:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15,0 kB]
OK:3 https://deb.nodesource.com/node_12.x bullseye InRelease
OK:4 http://archive.raspberrypi.org/debian bullseye InRelease
OK:5 https://deb.nodesource.com/node_14.x bullseye InRelease
OK:6 https://deb.nodesource.com/node_16.x bullseye InRelease
OK:7 https://deb.nodesource.com/node_18.x bullseye InRelease
Es wurden 15,0 kB in 2 s geholt (7.010 B/s).
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.
pi@raspi:~ $ apt policy udev
udev:
  Installiert:           247.3-7+rpi1+deb11u2
  Installationskandidat: 247.3-7+rpi1+deb11u2
  Versionstabelle:
 *** 247.3-7+rpi1+deb11u2 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
        100 /var/lib/dpkg/status
                                            Thomas Braun 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            929
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            7
                                            137
                                            10782
                                            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