Navigation

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

    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 startet nicht mehr

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @bishop last edited by Thomas Braun

      @bishop sagte in Zigbee startet nicht mehr:

      [    1.092327] mmc0: host does not support reading read-only switch, assuming write-enable
      [    1.099771] mmc0: new high speed SDHC card at address b368
      [    1.103915] mmcblk0: mmc0:b368       7.46 GiB
      [    1.108652] Indeed it is in host mode hprt0 = 00021501
      [    1.171432]  mmcblk0: p1 p2
      [    1.198485] random: fast init done
      [    1.203964] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
      [    1.209170] VFS: Mounted root (ext4 filesystem) readonly on device 179:2..426793] new mount options do not match the existing superblock, will be ignored
      

      Sieht ein wenig verdächtig aus, imho.
      Insbesondere, dass / nur ro gemounted wird.

      Schau mal mit

      mount | grep ^/dev
      

      danach.

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

        @Thomas-Braun

        /dev/mmcblk0p2 on / type ext4 (rw,noatime)
        /dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
        
        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @bishop last edited by

          @bishop

          which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
          
          B 1 Reply Last reply Reply Quote 0
          • B
            bishop @Thomas Braun last edited by bishop

            @Thomas-Braun

            pi@raspberrypi:~ $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
            /usr/bin/nodejs
            v10.21.0
            /usr/bin/node
            v10.21.0
            /usr/bin/npm
            6.14.4
            nodejs:
              Installiert:           10.21.0-1nodesource1
              Installationskandidat: 10.21.0-1nodesource1
              Versionstabelle:
             *** 10.21.0-1nodesource1 500
                    500 https://deb.nodesource.com/node_10.x buster/main armhf Packages
                    100 /var/lib/dpkg/status
                 10.21.0~dfsg-1~deb10u1+rpi1 500
                    500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
            

            hab mal eine andere Sd Karte benutzt aber leider das gleiche!

            host.raspberrypi	2020-06-28 13:21:51.274	info	"system.adapter.zigbee.0" disabled
            zigbee.0	2020-06-28 13:21:21.452	error	at process._tickCallback (internal/process/next_tick.js:68:7)
            zigbee.0	2020-06-28 13:21:21.452	error	at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:5:58)
            zigbee.0	2020-06-28 13:21:21.452	error	at Generator.next (<anonymous>)
            zigbee.0	2020-06-28 13:21:21.452	error	at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:91:48)
            zigbee.0	2020-06-28 13:21:21.452	error	at Function.open (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/database.js:17:35)
            zigbee.0	2020-06-28 13:21:21.452	error	at JSON.parse (<anonymous>)
            zigbee.0	2020-06-28 13:21:21.452	error	(1898) SyntaxError: Unexpected token in JSON at position 895
            zigbee.0	2020-06-28 13:21:21.449	error	(1898) Failed to start Zigbee
            zigbee.0	2020-06-28 13:21:21.014	info	(1898) Starting Zigbee...
            zigbee.0	2020-06-28 13:21:21.012	info	(1898) Try to reconnect. 1 attempts left
            zigbee.0	2020-06-28 13:21:11.008	error	at process._tickCallback (internal/process/next_tick.js:68:7)
            zigbee.0	2020-06-28 13:21:11.008	error	at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:5:58)
            zigbee.0	2020-06-28 13:21:11.008	error	at Generator.next (<anonymous>)
            zigbee.0	2020-06-28 13:21:11.008	error	at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:91:48)
            zigbee.0	2020-06-28 13:21:11.008	error	at Function.open (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/database.js:17:35)
            zigbee.0	2020-06-28 13:21:11.008	error	at JSON.parse (<anonymous>)
            zigbee.0	2020-06-28 13:21:11.008	error	(1898) SyntaxError: Unexpected token in JSON at position 895
            zigbee.0	2020-06-28 13:21:11.005	error	(1898) Failed to start Zigbee
            zigbee.0	2020-06-28 13:21:09.960	info	(1898) Starting Zigbee...
            zigbee.0	2020-06-28 13:21:09.838	info	(1898) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v10.21.0, js-controller: 3.1.5
            

            ohne den Stick wird der Adapter auch nicht Grün, also kann es wohl nicht am Stick liegen oder?
            Ein komplettes löschen des ZigbeeAdapters habe ich auch schon versucht.

            1 Reply Last reply Reply Quote 0
            • D
              dimaiv @Malz1902 last edited by dimaiv

              @Malz1902 sagte in Zigbee startet nicht mehr:

              Habe bevor ich hier den Thread aufgemacht schon alles gemacht und jetzt auch nochmal.

              /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.07__Embed_with_CMSIS-DAP_L4300302-if00
              

              isgt der COM Port

              über USB ist nur der Zigbee Stick dran

              Das ist aber kein Stick, oder hast du den umgeflasht?

              M 1 Reply Last reply Reply Quote 0
              • M
                Malz1902 @dimaiv last edited by

                @dimaiv
                Nutze einen CC1352R1

                Hab die Firmware nochmal neugeflasht, daanch ging wieder alles

                1 Reply Last reply Reply Quote 0
                • B
                  bishop last edited by

                  hat vielleicht noch jemand ein Tip für mich das ich tun kann?

                  D 1 Reply Last reply Reply Quote 0
                  • D
                    dimaiv @bishop last edited by

                    @bishop
                    Hi, hast du das schon mal gemacht:
                    ls -la /dev/serial/by-id
                    ?

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      bishop @dimaiv last edited by bishop

                      @dimaiv
                      ja

                      pi@raspberrypi:~ $ ls -la /dev/serial/by-id
                      insgesamt 0
                      drwxr-xr-x 2 root root 60 Jun 29 18:21 .
                      drwxr-xr-x 4 root root 80 Jun 29 18:21 ..
                      lrwxrwxrwx 1 root root 13 Jun 29 18:21 usb-Texas_Instruments_CC2538_USB_CDC-if00 -> ../../ttyACM0
                      

                      ich habe pivccu3 noch auf dem Raspberry laufen mit den dementsprechenden Adapter, kann das ein Problem sein?
                      Lief jetzt alles Monate lang ohne Probleme...

                      2020_06_29_19_59_59_Slave.jpg

                      D 1 Reply Last reply Reply Quote 0
                      • D
                        dimaiv @bishop last edited by

                        @bishop
                        Also, der Stick funktioniert.
                        Mit pivccu3 kenne mich nicht aus.

                        B 1 Reply Last reply Reply Quote 0
                        • B
                          bishop @dimaiv last edited by bishop

                          @dimaiv

                          mittlerweile kommt:

                          pi@raspberrypi:~ $ ls -la /dev/serial/by-path/
                          insgesamt 0
                          drwxr-xr-x 2 root root 60 Jun 30 16:36 .
                          drwxr-xr-x 4 root root 80 Jun 30 16:36 ..
                          lrwxrwxrwx 1 root root 13 Jun 30 16:36 platform-3f980000.usb-usb-0:1.5:1.0 -> ../../ttyACM0
                          

                          ah falsch von mir

                          pi@raspberrypi:~ $ ls -la /dev/serial/by-id
                          insgesamt 0
                          drwxr-xr-x 2 root root 60 Jun 30 16:36 .
                          drwxr-xr-x 4 root root 80 Jun 30 16:36 ..
                          lrwxrwxrwx 1 root root 13 Jun 30 16:36 usb-Texas_Instruments_CC2538_USB_CDC-if00 -> ../../ttyACM0
                          
                          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

                          460
                          Online

                          31.9k
                          Users

                          80.2k
                          Topics

                          1.3m
                          Posts

                          zigbee
                          5
                          30
                          1506
                          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