Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Probleme mit Serialport bei zwave2

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.7k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.1k

Probleme mit Serialport bei zwave2

Geplant Angeheftet Gesperrt Verschoben Tester
118 Beiträge 5 Kommentatoren 10.4k Aufrufe 2 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • Thomas BraunT Thomas Braun

    @esmax666 Der Stick liegt auf dem device node /dev/ttyAMA0

    E Offline
    E Offline
    Esmax666
    schrieb am zuletzt editiert von
    #27

    @thomas-braun

    Soll ich noch das machen?

    https://medium.com/@thedyslexiccoder/how-to-update-nodejs-npm-on-a-raspberry-pi-4-da75cad4148c

    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • E Esmax666

      @thomas-braun

      Soll ich noch das machen?

      https://medium.com/@thedyslexiccoder/how-to-update-nodejs-npm-on-a-raspberry-pi-4-da75cad4148c

      Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      schrieb am zuletzt editiert von Thomas Braun
      #28

      @esmax666 Nein.

      Die Anleitung wird so ohnehin nicht funktionieren, da fehlt noch Zeug davor.

      Linux-Werkzeugkasten:
      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
      NodeJS Fixer Skript:
      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

      E 1 Antwort Letzte Antwort
      0
      • Thomas BraunT Thomas Braun

        @esmax666 Nein.

        Die Anleitung wird so ohnehin nicht funktionieren, da fehlt noch Zeug davor.

        E Offline
        E Offline
        Esmax666
        schrieb am zuletzt editiert von
        #29

        @thomas-braun was meinst was feht

        Sonst fur die zwave0 version gab das:

        Raspberry Pi3 only: Activate GPIO UART
        On Raspberry Pi 3, the UART is by default occupied by the bluetooth module. To activate it for use with a GPIO module, follow these steps:

        sudo nano /boot/cmdline.txt

        remove console=serial0,115200
        save the file and close it
        sudo nano /boot/config.txt
        Look for each of the following lines. If they are commented out with a #, remove that. If they don't exist, add them to the end of the file:

        dtoverlay=pi3-miniuart-bt
        enable_uart=1
        force_turbo=1
        reboot

        Aber das brauchen wir nicht mehr oder ? Hab nicht gesehen fur zwave2

        AlCalzoneA 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          schrieb am zuletzt editiert von
          #30

          @esmax666 Ich kenn den Adapter nicht. Mal in die readme geschaut? Da steht vielleicht was drin.

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          1 Antwort Letzte Antwort
          0
          • E Esmax666

            @thomas-braun was meinst was feht

            Sonst fur die zwave0 version gab das:

            Raspberry Pi3 only: Activate GPIO UART
            On Raspberry Pi 3, the UART is by default occupied by the bluetooth module. To activate it for use with a GPIO module, follow these steps:

            sudo nano /boot/cmdline.txt

            remove console=serial0,115200
            save the file and close it
            sudo nano /boot/config.txt
            Look for each of the following lines. If they are commented out with a #, remove that. If they don't exist, add them to the end of the file:

            dtoverlay=pi3-miniuart-bt
            enable_uart=1
            force_turbo=1
            reboot

            Aber das brauchen wir nicht mehr oder ? Hab nicht gesehen fur zwave2

            AlCalzoneA Offline
            AlCalzoneA Offline
            AlCalzone
            Developer
            schrieb am zuletzt editiert von
            #31

            @esmax666 Probier mal /dev/serial0, da bin ich beim Raspberry Pi 4 auch schon drüber gestolpert.

            Ansonsten: ist das wirklich ein Z-Stick Gen5 oder doch ein Z-Stick Gen5 + ? Ich hab grob im Hinterkopf dass ersterer Probleme mit neueren USB-Schnittstellen macht.

            Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

            E 5 Antworten Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @esmax666 Der Stick liegt auf dem device node /dev/ttyAMA0

              E Offline
              E Offline
              Esmax666
              schrieb am zuletzt editiert von
              #32

              @thomas-braun

              Hab gerade geprüft auf raspi3 hatte ich eher /dev/ttyACM0

              1 Antwort Letzte Antwort
              0
              • AlCalzoneA AlCalzone

                @esmax666 Probier mal /dev/serial0, da bin ich beim Raspberry Pi 4 auch schon drüber gestolpert.

                Ansonsten: ist das wirklich ein Z-Stick Gen5 oder doch ein Z-Stick Gen5 + ? Ich hab grob im Hinterkopf dass ersterer Probleme mit neueren USB-Schnittstellen macht.

                E Offline
                E Offline
                Esmax666
                schrieb am zuletzt editiert von Esmax666
                #33

                @alcalzone Z-Stick Gen5 + mit raspu hat das funktioniert mit acm0

                AlCalzoneA 1 Antwort Letzte Antwort
                0
                • AlCalzoneA AlCalzone

                  @esmax666 Probier mal /dev/serial0, da bin ich beim Raspberry Pi 4 auch schon drüber gestolpert.

                  Ansonsten: ist das wirklich ein Z-Stick Gen5 oder doch ein Z-Stick Gen5 + ? Ich hab grob im Hinterkopf dass ersterer Probleme mit neueren USB-Schnittstellen macht.

                  E Offline
                  E Offline
                  Esmax666
                  schrieb am zuletzt editiert von
                  #34

                  @alcalzone

                  zwave2.0	2021-05-16 00:24:27.762	error	(23524) The Z-Wave driver could not be started: Error: No such file or directory, cannot open /dev/serial0
                  zwave2.0	2021-05-16 00:24:27.604	info	(23524) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                  host.raspberrypi	2021-05-16 00:24:25.121	info	instance system.adapter.zwave2.0 started with pid 23524
                  host.raspberrypi	2021-05-16 00:24:22.595	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  zwave2.0	2021-05-16 00:24:21.999	info	(13067) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  zwave2.0	2021-05-16 00:24:21.998	info	(13067) terminating
                  zwave2.0	2021-05-16 00:24:21.996	info	(13067) Shutting down driver...
                  host.raspberrypi	2021-05-16 00:24:21.997	info	stopInstance system.adapter.zwave2.0 send kill signal
                  zwave2.0	2021-05-16 00:24:21.994	info	(13067) Got terminate signal TERMINATE_YOURSELF
                  host.raspberrypi	2021-05-16 00:24:21.989	info	stopInstance system.adapter.zwave2.0 (force=false, process=true)
                  zwave2.0	2021-05-16 00:21:58.507	error	(13067) The Z-Wave driver could not be started: Error: No such file or directory, cannot open /dev/ttyACM0
                  zwave2.0	2021-05-16 00:21:58.367	info	(13067) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                  host.raspberrypi	2021-05-16 00:21:56.051	info	instance system.adapter.zwave2.0 started with pid 13067
                  host.raspberrypi	2021-05-16 00:21:53.467	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  host.raspberrypi	2021-05-16 00:21:52.921	info	stopInstance system.adapter.zwave2.0 send kill signal
                  zwave2.0	2021-05-16 00:21:52.882	info	(12357) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  zwave2.0	2021-05-16 00:21:52.880	info	(12357) terminating
                  zwave2.0	2021-05-16 00:21:52.879	info	(12357) Shutting down driver...
                  zwave2.0	2021-05-16 00:21:52.877	info	(12357) Got terminate signal TERMINATE_YOURSELF
                  host.raspberrypi	2021-05-16 00:21:52.859	info	stopInstance system.adapter.zwave2.0 (force=false, process=true)
                  zwave2.0	2021-05-16 00:21:49.469	error	(12357) The Z-Wave driver could not be started: Error: No such file or directory, c
                  
                  1 Antwort Letzte Antwort
                  0
                  • AlCalzoneA AlCalzone

                    @esmax666 Probier mal /dev/serial0, da bin ich beim Raspberry Pi 4 auch schon drüber gestolpert.

                    Ansonsten: ist das wirklich ein Z-Stick Gen5 oder doch ein Z-Stick Gen5 + ? Ich hab grob im Hinterkopf dass ersterer Probleme mit neueren USB-Schnittstellen macht.

                    E Offline
                    E Offline
                    Esmax666
                    schrieb am zuletzt editiert von
                    #35

                    @alcalzone

                    Soll ich das machen

                    https://forum.iobroker.net/post/629693

                    1 Antwort Letzte Antwort
                    0
                    • AlCalzoneA AlCalzone

                      @esmax666 Probier mal /dev/serial0, da bin ich beim Raspberry Pi 4 auch schon drüber gestolpert.

                      Ansonsten: ist das wirklich ein Z-Stick Gen5 oder doch ein Z-Stick Gen5 + ? Ich hab grob im Hinterkopf dass ersterer Probleme mit neueren USB-Schnittstellen macht.

                      E Offline
                      E Offline
                      Esmax666
                      schrieb am zuletzt editiert von
                      #36

                      @alcalzone

                      Jetzt

                      e5641fac-a0f0-43ca-b606-a3ae96dde7f6-grafik.png

                      7f17eb78-2670-41d4-b57b-356938c75595-grafik.png

                      zwave2.0	2021-05-16 07:55:56.747	error	(12308) The Z-Wave driver could not be started: Error: Is a directory, cannot open /dev/
                      zwave2.0	2021-05-16 07:55:56.584	info	(12308) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                      host.raspberrypi	2021-05-16 07:55:54.148	info	instance system.adapter.zwave2.0 started with pid 12308
                      host.raspberrypi	2021-05-16 07:55:51.659	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      zwave2.0	2021-05-16 07:55:51.028	info	(6004) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                      zwave2.0	2021-05-16 07:55:51.026	info	(6004) terminating
                      zwave2.0	2021-05-16 07:55:51.025	info	(6004) Shutting down driver...
                      zwave2.0	2021-05-16 07:55:51.023	info	(6004) Got terminate signal TERMINATE_YOURSELF
                      host.raspberrypi	2021-05-16 07:55:51.022	info	stopInstance system.adapter.zwave2.0 send kill signal
                      host.raspberrypi	2021-05-16 07:55:51.014	info	stopInstance system.adapter.zwave2.0 (force=false, process=true)
                      zwave2.0	2021-05-16 07:54:38.393	info	(6004) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                      host.raspberrypi	2021-05-16 07:54:35.967	info	instance system.adapter.zwave2.0 started with pid 6004
                      host.raspberrypi	2021-05-16 07:54:33.559	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      zwave2.0	2021-05-16 07:54:32.824	info	(21886) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                      zwave2.0	2021-05-16 07:54:32.822	info	(21886) terminating
                      zwave2.0	2021-05-16 07:54:32.820	info	(21886) Shutting down driver...
                      zwave2.0	2021-05-16 07:54:32.812	info	(21886) Got terminate signal TERMINATE_YOURSELF
                      host.raspberrypi	2021-05-16 07:54:32.796	info	stopInstance system.adapter.zwave2.0 send kill signal
                      host.raspberrypi	2021-05-16 07:54:32.776	info	stopInstance system.adapter.zwave2.0 (force=false, process=true)
                      info.0	2021-05-16 07:49:56.003	warn	(2765) State "info.0.uuid" has no existing object, this might lead to an error in future versions
                      zwave2.0	2021-05-16 07:44:28.868	info	(21886) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                      host.raspberrypi	2021-05-16 07:44:26.457	info	instance system.adapter.zwave2.0 started with pid 21886
                      host.raspberrypi	2021-05-16 07:44:24.074	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      zwave2.0	2021-05-16 07:44:23.304	info	(4553) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                      zwave2.0	2021-05-16 07:44:23.303	info	(4553) terminating
                      zwave2.0	2021-05-16 07:44:23.301	info	(4553) Shutting down driver...
                      zwave2.0	2021-05-16 07:44:23.294	info	(4553) Got terminate signal TERMINATE_YOURSELF
                      host.raspberrypi	2021-05-16 07:44:23.292	info	stopInstance system.adapter.zwave2.0 send kill signal
                      

                      Version

                      0bd94168-d821-4138-bf35-2fec01787a10-grafik.png

                      9242b2f7-5e14-4f3f-ac8c-c0a298d8b652-grafik.png

                      E 1 Antwort Letzte Antwort
                      0
                      • E Esmax666

                        @alcalzone

                        Jetzt

                        e5641fac-a0f0-43ca-b606-a3ae96dde7f6-grafik.png

                        7f17eb78-2670-41d4-b57b-356938c75595-grafik.png

                        zwave2.0	2021-05-16 07:55:56.747	error	(12308) The Z-Wave driver could not be started: Error: Is a directory, cannot open /dev/
                        zwave2.0	2021-05-16 07:55:56.584	info	(12308) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                        host.raspberrypi	2021-05-16 07:55:54.148	info	instance system.adapter.zwave2.0 started with pid 12308
                        host.raspberrypi	2021-05-16 07:55:51.659	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        zwave2.0	2021-05-16 07:55:51.028	info	(6004) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        zwave2.0	2021-05-16 07:55:51.026	info	(6004) terminating
                        zwave2.0	2021-05-16 07:55:51.025	info	(6004) Shutting down driver...
                        zwave2.0	2021-05-16 07:55:51.023	info	(6004) Got terminate signal TERMINATE_YOURSELF
                        host.raspberrypi	2021-05-16 07:55:51.022	info	stopInstance system.adapter.zwave2.0 send kill signal
                        host.raspberrypi	2021-05-16 07:55:51.014	info	stopInstance system.adapter.zwave2.0 (force=false, process=true)
                        zwave2.0	2021-05-16 07:54:38.393	info	(6004) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                        host.raspberrypi	2021-05-16 07:54:35.967	info	instance system.adapter.zwave2.0 started with pid 6004
                        host.raspberrypi	2021-05-16 07:54:33.559	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        zwave2.0	2021-05-16 07:54:32.824	info	(21886) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        zwave2.0	2021-05-16 07:54:32.822	info	(21886) terminating
                        zwave2.0	2021-05-16 07:54:32.820	info	(21886) Shutting down driver...
                        zwave2.0	2021-05-16 07:54:32.812	info	(21886) Got terminate signal TERMINATE_YOURSELF
                        host.raspberrypi	2021-05-16 07:54:32.796	info	stopInstance system.adapter.zwave2.0 send kill signal
                        host.raspberrypi	2021-05-16 07:54:32.776	info	stopInstance system.adapter.zwave2.0 (force=false, process=true)
                        info.0	2021-05-16 07:49:56.003	warn	(2765) State "info.0.uuid" has no existing object, this might lead to an error in future versions
                        zwave2.0	2021-05-16 07:44:28.868	info	(21886) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                        host.raspberrypi	2021-05-16 07:44:26.457	info	instance system.adapter.zwave2.0 started with pid 21886
                        host.raspberrypi	2021-05-16 07:44:24.074	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        zwave2.0	2021-05-16 07:44:23.304	info	(4553) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        zwave2.0	2021-05-16 07:44:23.303	info	(4553) terminating
                        zwave2.0	2021-05-16 07:44:23.301	info	(4553) Shutting down driver...
                        zwave2.0	2021-05-16 07:44:23.294	info	(4553) Got terminate signal TERMINATE_YOURSELF
                        host.raspberrypi	2021-05-16 07:44:23.292	info	stopInstance system.adapter.zwave2.0 send kill signal
                        

                        Version

                        0bd94168-d821-4138-bf35-2fec01787a10-grafik.png

                        9242b2f7-5e14-4f3f-ac8c-c0a298d8b652-grafik.png

                        E Offline
                        E Offline
                        Esmax666
                        schrieb am zuletzt editiert von
                        #37

                        @thomas-braun said in Test Adapter Z-Wave 2 v1.10.x:

                        Windows User, oder? Der Treiber ist im Linux-Kernel schon drin.

                        warum windows User ?
                        steht sogar in log

                        host.raspberrypi	2021-05-16 08:00:00.072	info	instance system.adapter.ical.0 started with pid 29746
                        zwave2.0	2021-05-16 07:55:56.747	error	(12308) The Z-Wave driver could not be started: Error: Is a directory, cannot open /dev/
                        zwave2.0	2021-05-16 07:55:56.584	info	(12308) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                        host.raspberrypi	2021-05-16 07:55:54.148	info	instance system.adapter.zwave2.0 started with pid 12308
                        host.raspberrypi	2021-05-16 07:55:51.659	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        zwave2.0	2021-05-16 07:55:51.028	info	(6004) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        zwave2.0	2021-05-16 07:55:51.026	info	(6004) terminating
                        
                        E Thomas BraunT 2 Antworten Letzte Antwort
                        0
                        • E Esmax666

                          @thomas-braun said in Test Adapter Z-Wave 2 v1.10.x:

                          Windows User, oder? Der Treiber ist im Linux-Kernel schon drin.

                          warum windows User ?
                          steht sogar in log

                          host.raspberrypi	2021-05-16 08:00:00.072	info	instance system.adapter.ical.0 started with pid 29746
                          zwave2.0	2021-05-16 07:55:56.747	error	(12308) The Z-Wave driver could not be started: Error: Is a directory, cannot open /dev/
                          zwave2.0	2021-05-16 07:55:56.584	info	(12308) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                          host.raspberrypi	2021-05-16 07:55:54.148	info	instance system.adapter.zwave2.0 started with pid 12308
                          host.raspberrypi	2021-05-16 07:55:51.659	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                          zwave2.0	2021-05-16 07:55:51.028	info	(6004) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          zwave2.0	2021-05-16 07:55:51.026	info	(6004) terminating
                          
                          E Offline
                          E Offline
                          Esmax666
                          schrieb am zuletzt editiert von
                          #38
                          Linux raspberrypi 5.10.17-v7l+ #1414 SMP Fri Apr 30 13:20:47 BST 2021 armv7l
                          
                          The programs included with the Debian GNU/Linux system are free software;
                          the exact distribution terms for each program are described in the
                          individual files in /usr/share/doc/*/copyright.
                          
                          Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
                          permitted by applicable law.
                          Last login: Sun May 16 00:06:39 2021
                          pi@raspberrypi:~ $ npm i iobroker.zwave2
                          
                          > @serialport/bindings@9.0.7 install /home/pi/node_modules/@serialport/bindings
                          > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
                          
                          prebuild-install WARN install No prebuilt binaries found (target=12.22.1 runtime=node arch=arm libc= platform=linux)
                          make: Verzeichnis „/home/pi/node_modules/@serialport/bindings/build“ wird betreten
                            CXX(target) Release/obj.target/bindings/src/serialport.o
                          ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
                          ../src/serialport.cpp:78:69: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                             uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);
                                                                                               ^~~~~~~~~~~~~
                          ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
                          ../src/serialport.cpp:135:71: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                             uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);
                                                                                                 ^~~~~~~~~~~~~~~
                          ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
                          ../src/serialport.cpp:175:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                             uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);
                                                                                                ^~~~~~~~~~~~~~
                          ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
                          ../src/serialport.cpp:215:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                             uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);
                                                                                                ^~~~~~~~~~~~~~
                          ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
                          ../src/serialport.cpp:271:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                             uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);
                                                                                              ^~~~~~~~~~~~
                          ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:
                          ../src/serialport.cpp:316:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                             uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);
                                                                                              ^~~~~~~~~~~~
                          ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:
                          ../src/serialport.cpp:366:76: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                           _queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);
                                                                                                  ^~~~~~~~~~~~~~~~~~~~
                          
                          ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
                          ../src/serialport.cpp:412:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                             uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
                                                                                                ^~~~~~~~~~~~~~
                          ../src/serialport.cpp: At global scope:
                          ../src/serialport.cpp:433:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses]
                           SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
                                                      ^
                          ../src/serialport.cpp:452:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]
                           SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
                                                        ^
                          In file included from ../../../nan/nan.h:56,
                                           from ../src/./serialport.h:6,
                                           from ../src/serialport.cpp:1:
                          /home/pi/.cache/node-gyp/12.22.1/include/node/node.h:736:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                 (node::addon_register_func) (regfunc),                          \
                                                                     ^
                          /home/pi/.cache/node-gyp/12.22.1/include/node/node.h:770:3: note: in expansion of macro ‘NODE_MODULE_X’
                             NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                             ^~~~~~~~~~~~~
                          ../src/serialport.cpp:486:1: note: in expansion of macro ‘NODE_MODULE’
                           NODE_MODULE(serialport, init);
                           ^~~~~~~~~~~
                            CXX(target) Release/obj.target/bindings/src/serialport_unix.o
                          ../src/serialport_unix.cpp: In function ‘int setup(int, OpenBaton*)’:
                          ../src/serialport_unix.cpp:176:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=]
                               snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path);
                                                                                      ^~~~~~~~~~~~~~~~~~~~~~~~~
                          ../src/serialport_unix.cpp:176:13: note: ‘snprintf’ output 20 or more bytes (assuming 1043) into a destination of size 1024
                               snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path);
                               ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          ../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’:
                          ../src/serialport_unix.cpp:86:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=]
                               snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);
                                                                                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~
                          ../src/serialport_unix.cpp:86:13: note: ‘snprintf’ output 22 or more bytes (assuming 1045) into a destination of size 1024
                               snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);
                               ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                            CXX(target) Release/obj.target/bindings/src/poller.o
                            CXX(target) Release/obj.target/bindings/src/serialport_linux.o
                            SOLINK_MODULE(target) Release/obj.target/bindings.node
                            COPY Release/bindings.node
                          make: Verzeichnis „/home/pi/node_modules/@serialport/bindings/build“ wird verlassennpm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
                          npm notice created a lockfile as package-lock.json. You should commit this file.
                          npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
                          npm WARN pi No description
                          npm WARN pi No repository field.
                          npm WARN pi No README data
                          npm WARN pi No license field.
                          
                          + iobroker.zwave2@1.10.0
                          added 168 packages from 189 contributors and audited 168 packages in 41.299s
                          
                          29 packages are looking for funding
                            run `npm fund` for details
                          
                          found 0 vulnerabilities
                          
                          pi@raspberrypi:~ $ npm i zwave-js
                          npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
                          npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
                          npm WARN pi No description
                          npm WARN pi No repository field.
                          npm WARN pi No README data
                          npm WARN pi No license field.
                          
                          + zwave-js@7.4.0
                          updated 1 package and audited 309 packages in 6.047s
                          
                          29 packages are looking for funding
                            run `npm fund` for details
                          
                          found 0 vulnerabilities
                          
                          pi@raspberrypi:~ $
                          
                          1 Antwort Letzte Antwort
                          0
                          • AlCalzoneA AlCalzone

                            @esmax666 Probier mal /dev/serial0, da bin ich beim Raspberry Pi 4 auch schon drüber gestolpert.

                            Ansonsten: ist das wirklich ein Z-Stick Gen5 oder doch ein Z-Stick Gen5 + ? Ich hab grob im Hinterkopf dass ersterer Probleme mit neueren USB-Schnittstellen macht.

                            E Offline
                            E Offline
                            Esmax666
                            schrieb am zuletzt editiert von
                            #39

                            @alcalzone

                            Das ist die Raspi3 die die funktionniert (npm version vielleicht passt nicht)
                            (hier ist ACM0) auf raspi4 geht auch nicht fehlt etwas ?

                            f15c72c5-f222-46a5-ae40-d96d1c38d305-image.png

                            693b4353-a7c5-4398-89a5-675c380dd261-image.png

                            d59c5429-2815-4df9-9ff5-703cd1056e12-image.png

                            7fc17ee8-9d43-4245-8c9e-1f50ec444094-image.png

                            1 Antwort Letzte Antwort
                            0
                            • E Esmax666

                              @thomas-braun said in Test Adapter Z-Wave 2 v1.10.x:

                              Windows User, oder? Der Treiber ist im Linux-Kernel schon drin.

                              warum windows User ?
                              steht sogar in log

                              host.raspberrypi	2021-05-16 08:00:00.072	info	instance system.adapter.ical.0 started with pid 29746
                              zwave2.0	2021-05-16 07:55:56.747	error	(12308) The Z-Wave driver could not be started: Error: Is a directory, cannot open /dev/
                              zwave2.0	2021-05-16 07:55:56.584	info	(12308) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                              host.raspberrypi	2021-05-16 07:55:54.148	info	instance system.adapter.zwave2.0 started with pid 12308
                              host.raspberrypi	2021-05-16 07:55:51.659	info	instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                              zwave2.0	2021-05-16 07:55:51.028	info	(6004) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              zwave2.0	2021-05-16 07:55:51.026	info	(6004) terminating
                              
                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von Thomas Braun
                              #40

                              @esmax666 sagte in Test Adapter Z-Wave 2 v1.10.x:

                              steht sogar in log

                              Da steht, dass /dev kein device node ist sondern ein Verzeichnis. Vermutlich hast du /dev in den Einstellungen des Adapters drin.

                              pi@raspberrypi:~ $ npm i iobroker.zwave2

                              Ist falsch. Jetzt hast du das im /home-Verzeichnis von pi installiert.
                              Nimm den Adapter aus der Adapterliste im Admin.

                              Aus deinem dmesg:

                              [Sa Mai 15 21:06:15 2021] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2
                              

                              Das ist der für das Gerät geladene Treiber. Und da sieht man auch, dass das Device auf ttyAMA0 liegt.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              E 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @esmax666 sagte in Test Adapter Z-Wave 2 v1.10.x:

                                steht sogar in log

                                Da steht, dass /dev kein device node ist sondern ein Verzeichnis. Vermutlich hast du /dev in den Einstellungen des Adapters drin.

                                pi@raspberrypi:~ $ npm i iobroker.zwave2

                                Ist falsch. Jetzt hast du das im /home-Verzeichnis von pi installiert.
                                Nimm den Adapter aus der Adapterliste im Admin.

                                Aus deinem dmesg:

                                [Sa Mai 15 21:06:15 2021] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2
                                

                                Das ist der für das Gerät geladene Treiber. Und da sieht man auch, dass das Device auf ttyAMA0 liegt.

                                E Offline
                                E Offline
                                Esmax666
                                schrieb am zuletzt editiert von
                                #41

                                @thomas-braun said in Test Adapter Z-Wave 2 v1.10.x:

                                Nimm den Adapter aus der Adapterliste im Admin.

                                Hatte ich schon gemacht.

                                sogar sogar instance weg gemacht und neu gemacht

                                leider geht es nicht mehr

                                Thomas BraunT 1 Antwort Letzte Antwort
                                0
                                • E Esmax666

                                  @thomas-braun said in Test Adapter Z-Wave 2 v1.10.x:

                                  Nimm den Adapter aus der Adapterliste im Admin.

                                  Hatte ich schon gemacht.

                                  sogar sogar instance weg gemacht und neu gemacht

                                  leider geht es nicht mehr

                                  Thomas BraunT Online
                                  Thomas BraunT Online
                                  Thomas Braun
                                  Most Active
                                  schrieb am zuletzt editiert von
                                  #42

                                  @esmax666 sagte in Test Adapter Z-Wave 2 v1.10.x:

                                  leider geht es nicht mehr

                                  Stimmt dann wohl.
                                  Leider kann man aus deiner 'Fehlerbeschreibung' nichts herauslesen.

                                  Linux-Werkzeugkasten:
                                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                  NodeJS Fixer Skript:
                                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                  E 1 Antwort Letzte Antwort
                                  0
                                  • Thomas BraunT Thomas Braun

                                    @esmax666 sagte in Test Adapter Z-Wave 2 v1.10.x:

                                    leider geht es nicht mehr

                                    Stimmt dann wohl.
                                    Leider kann man aus deiner 'Fehlerbeschreibung' nichts herauslesen.

                                    E Offline
                                    E Offline
                                    Esmax666
                                    schrieb am zuletzt editiert von
                                    #43

                                    @thomas-braun was kann ich sonst noch als info geben ?

                                    sonst habe ich noch 2 warn und 1 error

                                    info.0	2021-05-16 13:07:15.628	warn	(2791) State "info.0.uuid" has no existing object, this might lead to an error in future versions
                                    host.raspberrypi	2021-05-16 13:00:08.345	info	instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                    host.raspberrypi	2021-05-16 13:00:00.042	info	instance system.adapter.ical.0 started with pid 5361
                                    zwave2.0	2021-05-16 12:59:53.829	info	(5346) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                                    host.raspberrypi	2021-05-16 12:59:51.487	info	instance system.adapter.zwave2.0 started with pid 5346
                                    host.raspberrypi	2021-05-16 12:59:21.429	info	Restart adapter system.adapter.zwave2.0 because enabled
                                    host.raspberrypi	2021-05-16 12:59:21.428	info	instance system.adapter.zwave2.0 terminated with code NaN ()
                                    host.raspberrypi	2021-05-16 12:59:21.427	warn	instance system.adapter.zwave2.0 terminated due to SIGABRT
                                    host.raspberrypi	2021-05-16 12:59:21.422	error	Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
                                    zwave2.0	2021-05-16 12:45:57.264	info	(5176) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                                    host.raspberrypi	2021-05-16 12:45:55.024	info	instance system.adapter.zwave2.0 started with pid 5176
                                    host.raspberrypi	2021-05-16 12:45:24.958	info	Restart adapter system.adapter.zwave2.0 because enabled
                                    host.raspberrypi	2021-05-16 12:45:24.957	info	instance system.adapter.zwave2.0 terminated with code NaN ()
                                    host.raspberrypi	2021-05-16 12:45:24.956	warn	instance system.adapter.zwave2.0 terminated due to SIGABRT
                                    host.raspberrypi	2021-05-16 12:45:24.950	error	Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
                                    info.0	2021-05-16 12:37:15.604	warn	(2791) State "info.0.uuid" has no existing object, this might lead to an error in future versions
                                    zwave2.0	2021-05-16 12:32:01.208	info	(5010) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                                    host.raspberrypi	2021-05-16 12:31:58.911	info	instance system.adapter.zwave2.0 started with pid 5010
                                    host.raspberrypi	2021-05-16 12:31:28.859	info	Restart adapter system.adapter.zwave2.0 because enabled
                                    host.raspberrypi	2021-05-16 12:31:28.859	info	instance system.adapter.zwave2.0 terminated with code NaN ()
                                    host.raspberrypi	2021-05-16 12:31:28.858	warn	instance system.adapter.zwave2.0 terminated due to SIGABRT
                                    host.raspberrypi	2021-05-16 12:31:28.857	error	Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
                                    
                                    Thomas BraunT 1 Antwort Letzte Antwort
                                    0
                                    • E Esmax666

                                      @thomas-braun was kann ich sonst noch als info geben ?

                                      sonst habe ich noch 2 warn und 1 error

                                      info.0	2021-05-16 13:07:15.628	warn	(2791) State "info.0.uuid" has no existing object, this might lead to an error in future versions
                                      host.raspberrypi	2021-05-16 13:00:08.345	info	instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                      host.raspberrypi	2021-05-16 13:00:00.042	info	instance system.adapter.ical.0 started with pid 5361
                                      zwave2.0	2021-05-16 12:59:53.829	info	(5346) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                                      host.raspberrypi	2021-05-16 12:59:51.487	info	instance system.adapter.zwave2.0 started with pid 5346
                                      host.raspberrypi	2021-05-16 12:59:21.429	info	Restart adapter system.adapter.zwave2.0 because enabled
                                      host.raspberrypi	2021-05-16 12:59:21.428	info	instance system.adapter.zwave2.0 terminated with code NaN ()
                                      host.raspberrypi	2021-05-16 12:59:21.427	warn	instance system.adapter.zwave2.0 terminated due to SIGABRT
                                      host.raspberrypi	2021-05-16 12:59:21.422	error	Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
                                      zwave2.0	2021-05-16 12:45:57.264	info	(5176) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                                      host.raspberrypi	2021-05-16 12:45:55.024	info	instance system.adapter.zwave2.0 started with pid 5176
                                      host.raspberrypi	2021-05-16 12:45:24.958	info	Restart adapter system.adapter.zwave2.0 because enabled
                                      host.raspberrypi	2021-05-16 12:45:24.957	info	instance system.adapter.zwave2.0 terminated with code NaN ()
                                      host.raspberrypi	2021-05-16 12:45:24.956	warn	instance system.adapter.zwave2.0 terminated due to SIGABRT
                                      host.raspberrypi	2021-05-16 12:45:24.950	error	Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
                                      info.0	2021-05-16 12:37:15.604	warn	(2791) State "info.0.uuid" has no existing object, this might lead to an error in future versions
                                      zwave2.0	2021-05-16 12:32:01.208	info	(5010) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16
                                      host.raspberrypi	2021-05-16 12:31:58.911	info	instance system.adapter.zwave2.0 started with pid 5010
                                      host.raspberrypi	2021-05-16 12:31:28.859	info	Restart adapter system.adapter.zwave2.0 because enabled
                                      host.raspberrypi	2021-05-16 12:31:28.859	info	instance system.adapter.zwave2.0 terminated with code NaN ()
                                      host.raspberrypi	2021-05-16 12:31:28.858	warn	instance system.adapter.zwave2.0 terminated due to SIGABRT
                                      host.raspberrypi	2021-05-16 12:31:28.857	error	Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
                                      
                                      Thomas BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      schrieb am zuletzt editiert von
                                      #44

                                      @esmax666
                                      Speicher dicht?

                                      free -ht
                                      

                                      anschauen.

                                      Linux-Werkzeugkasten:
                                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                      NodeJS Fixer Skript:
                                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                      E 1 Antwort Letzte Antwort
                                      0
                                      • Thomas BraunT Thomas Braun

                                        @esmax666
                                        Speicher dicht?

                                        free -ht
                                        

                                        anschauen.

                                        E Offline
                                        E Offline
                                        Esmax666
                                        schrieb am zuletzt editiert von
                                        #45

                                        @thomas-braun e6761199-eed2-4a16-9ee1-e9ac22718005-image.png

                                        Thomas BraunT 1 Antwort Letzte Antwort
                                        0
                                        • E Esmax666

                                          @thomas-braun e6761199-eed2-4a16-9ee1-e9ac22718005-image.png

                                          Thomas BraunT Online
                                          Thomas BraunT Online
                                          Thomas Braun
                                          Most Active
                                          schrieb am zuletzt editiert von
                                          #46

                                          @esmax666
                                          Bitte keine Bilderchen posten, KonsolenTEXT in CodeTags eingebettet hier rein.

                                          Linux-Werkzeugkasten:
                                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                          NodeJS Fixer Skript:
                                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                          1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          988

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe