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. ioBroker Allgemein
  4. Adapter WM-Bus / Kampstrup Multical 21

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.0k

Adapter WM-Bus / Kampstrup Multical 21

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
153 Beiträge 12 Kommentatoren 22.4k Aufrufe 13 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.
  • M matze-dev

    @wolfgangfb würde vorschlagen, den Stick einmal ziehen und dann wieder stecken. Dabei dmesg laufen lassen. Was erzeugt er für Meldungen?

    W Offline
    W Offline
    WolfgangFB
    schrieb am zuletzt editiert von
    #56

    @matze-dev

    [208168.253155] usb 1-1.1: USB disconnect, device number 3
    [208168.253617] cp210x ttyUSB0: failed set request 0x12 status: -19
    [208168.253640] cp210x ttyUSB0: failed set request 0x0 status: -19
    [208168.254215] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
    [208168.254736] cp210x 1-1.1:1.0: device disconnected
    [208168.408590] Bluetooth: hci0: Frame reassembly failed (-84)
    [208168.426653] Bluetooth: hci0: Frame reassembly failed (-84)
    [208169.204104] Bluetooth: hci0: Frame reassembly failed (-84)
    [208170.015942] Bluetooth: hci0: Frame reassembly failed (-84)
    [208170.212190] Bluetooth: hci0: Frame reassembly failed (-84)
    [208170.281565] Bluetooth: hci0: Frame reassembly failed (-84)
    [208170.603152] usb 1-1.1: new full-speed USB device number 7 using xhci_hcd
    [208170.612186] Bluetooth: hci0: Frame reassembly failed (-84)
    [208170.741010] usb 1-1.1: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
    [208170.741028] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [208170.741041] usb 1-1.1: Product: WiMOD iM871A-usb
    [208170.741053] usb 1-1.1: Manufacturer: Silicon Labs
    [208170.741065] usb 1-1.1: SerialNumber: 00919907
    [208170.747222] cp210x 1-1.1:1.0: cp210x converter detected
    [208170.755693] usb 1-1.1: cp210x converter now attached to ttyUSB0
    [
    
    [2021-07-14_20:48:38] Lost /dev/ttyUSB0 closing im871a[00100776]
    No wmbus device detected, waiting for a device to be plugged in.
    [2021-07-14_20:48:38] [ALARM SpecifiedDeviceNotFound] the device /dev/ttyUSB0:im871a:t1 is not working
    [2021-07-14_20:48:38] (shell) /bin/sh exited with non-zero return code: 127
    [2021-07-14_20:48:40] Started config im871a[00100776] on /dev/ttyUSB0 listening on t1
    (wmbusmeters) shutting down
    (wmbusmeters) logging started 2021-07-14 20:50:06 using _
    [2021-07-14_20:50:06] Started config im871a[00100776] on /dev/ttyUSB0 listening on t1
    (wmbusmeters) waiting for telegrams
    [2021-07-14_20:50:08] (memory) rss 1929216 peak 1.83 MiB
    
    M 1 Antwort Letzte Antwort
    0
    • W WolfgangFB

      @matze-dev

      [208168.253155] usb 1-1.1: USB disconnect, device number 3
      [208168.253617] cp210x ttyUSB0: failed set request 0x12 status: -19
      [208168.253640] cp210x ttyUSB0: failed set request 0x0 status: -19
      [208168.254215] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
      [208168.254736] cp210x 1-1.1:1.0: device disconnected
      [208168.408590] Bluetooth: hci0: Frame reassembly failed (-84)
      [208168.426653] Bluetooth: hci0: Frame reassembly failed (-84)
      [208169.204104] Bluetooth: hci0: Frame reassembly failed (-84)
      [208170.015942] Bluetooth: hci0: Frame reassembly failed (-84)
      [208170.212190] Bluetooth: hci0: Frame reassembly failed (-84)
      [208170.281565] Bluetooth: hci0: Frame reassembly failed (-84)
      [208170.603152] usb 1-1.1: new full-speed USB device number 7 using xhci_hcd
      [208170.612186] Bluetooth: hci0: Frame reassembly failed (-84)
      [208170.741010] usb 1-1.1: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
      [208170.741028] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [208170.741041] usb 1-1.1: Product: WiMOD iM871A-usb
      [208170.741053] usb 1-1.1: Manufacturer: Silicon Labs
      [208170.741065] usb 1-1.1: SerialNumber: 00919907
      [208170.747222] cp210x 1-1.1:1.0: cp210x converter detected
      [208170.755693] usb 1-1.1: cp210x converter now attached to ttyUSB0
      [
      
      [2021-07-14_20:48:38] Lost /dev/ttyUSB0 closing im871a[00100776]
      No wmbus device detected, waiting for a device to be plugged in.
      [2021-07-14_20:48:38] [ALARM SpecifiedDeviceNotFound] the device /dev/ttyUSB0:im871a:t1 is not working
      [2021-07-14_20:48:38] (shell) /bin/sh exited with non-zero return code: 127
      [2021-07-14_20:48:40] Started config im871a[00100776] on /dev/ttyUSB0 listening on t1
      (wmbusmeters) shutting down
      (wmbusmeters) logging started 2021-07-14 20:50:06 using _
      [2021-07-14_20:50:06] Started config im871a[00100776] on /dev/ttyUSB0 listening on t1
      (wmbusmeters) waiting for telegrams
      [2021-07-14_20:50:08] (memory) rss 1929216 peak 1.83 MiB
      
      M Offline
      M Offline
      matze-dev
      schrieb am zuletzt editiert von matze-dev
      #57

      @wolfgangfb bei mir sieht dmesg so aus:
      6b3ba7c2-fdd2-4a78-b6f6-9a6ab1e39438-grafik.png
      und beim journalctl:
      f83db667-4fb7-49fd-97d5-045141d66179-grafik.png

      W 1 Antwort Letzte Antwort
      0
      • M matze-dev

        @wolfgangfb bei mir sieht dmesg so aus:
        6b3ba7c2-fdd2-4a78-b6f6-9a6ab1e39438-grafik.png
        und beim journalctl:
        f83db667-4fb7-49fd-97d5-045141d66179-grafik.png

        W Offline
        W Offline
        WolfgangFB
        schrieb am zuletzt editiert von
        #58

        @matze-dev

        Ich habe jetzt nochmal eine jungfräuliche SD Karte genommen, ein neues Image installiert

        pi@raspberrypi:~ $ lsb_release -a
        No LSB modules are available.
        Distributor ID: Raspbian
        Description:    Raspbian GNU/Linux 10 (buster)
        Release:        10
        Codename:       buster
        

        mosqutto installiert

        sudo apt-get install mosquitto
        
        pi@raspberrypi:~ $ apt policy mosquitto
        mosquitto:
          Installiert:           1.5.7-1+deb10u1
          Installationskandidat: 1.5.7-1+deb10u1
          Versionstabelle:
         *** 1.5.7-1+deb10u1 500
                500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
                100 /var/lib/dpkg/status
        

        und den wmbusmeters aus den Quellen installiert

        pi@raspberrypi:~ $ more /etc/wmbusmeters.conf
        loglevel=debug
        device=/dev/ttyUSB0:im871a:t1
        logtelegrams=true
        format=json
        meterfiles=/var/log/wmbusmeters/meter_readings
        meterfilesaction=append
        meterfilesnaming=name
        meterfilestimestamp=day
        logfile=/var/log/wmbusmeters/wmbusmeters.log
        shell=/usr/local/bin/mosquitto_pub -d -h localhost -t wmbusmeters/$METER_ID -m "$METER_JSON"
        alarmshell=/usr/local/bin/mosquitto_pub -d -h localhost -t wmbusmeters_alarm -m "$ALARM_TYPE $ALARM_MESSAGE"
        alarmtimeout=1h
        alarmexpectedactivity=mon-sun(00-23)
        
        pi@raspberrypi:~ $ more /etc/wmbusmeters.d/MyTapWater
        name=MyTapWater
        type=multical21
        id=57813696
        key=E4E7EAF6FD17EAFB9587BC2996783C63
        
        pi@raspberrypi:~ $ sudo systemctl status wmbusmeters
        ● wmbusmeters.service - "wmbusmeters service"
           Loaded: loaded (/lib/systemd/system/wmbusmeters.service; disabled; vendor preset: enabled)
           Active: active (running) since Sat 2021-07-17 16:14:49 CEST; 9min ago
             Docs: https://github.com/weetmuts/wmbusmeters
                   man:wmbusmeters(1)
          Process: 2774 ExecStartPre=/bin/mkdir -p /var/log/wmbusmeters/meter_readings (code=exited, status=0/SUCCESS)
          Process: 2775 ExecStartPre=/bin/chown -R wmbusmeters:wmbusmeters /var/log/wmbusmeters (code=exited, status=0/SUCCESS)
          Process: 2776 ExecStartPre=/bin/mkdir -p /run/wmbusmeters (code=exited, status=0/SUCCESS)
          Process: 2777 ExecStartPre=/bin/chown -R wmbusmeters:wmbusmeters /run/wmbusmeters (code=exited, status=0/SUCCESS)
          Process: 2778 ExecStart=/usr/sbin/wmbusmetersd /run/wmbusmeters/wmbusmeters.pid (code=exited, status=0/SUCCESS)
         Main PID: 2779 (wmbusmetersd)
            Tasks: 3 (limit: 4915)
           CGroup: /system.slice/wmbusmeters.service
                   └─2779 /usr/sbin/wmbusmetersd /run/wmbusmeters/wmbusmeters.pid
        
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) "alarmshell" "/usr/local/bin/mosquitto_pub -d -h localhost -t w
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) "alarmtimeout" "1h"
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) "alarmexpectedactivity" "mon-sun(00-23)"
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) "" ""
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) loading meter file /etc/wmbusmeters.d/MyTapWater
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) name=MyTapWater
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) type=multical21
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) id=57813696
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) key=<notprinted>
        Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (wmbusmeters) using log file /var/log/wmbusmeters/wmbusmeters.log
        pi@raspberrypi:~ $                                                                                   
        
        pi@raspberrypi:~ $ more /var/log/wmbusmeters/wmbusmeters.log
        (serial) stopping manager
        (serial) EVENT thread interrupted
        (serial) event loop stopped!
        (serial) TIMER thread interrupted
        (wmbusmeters) shutting down
        (wmbusmeters) logging started 2021-07-17 16:31:43 using _
        (wmbusmeters) version: _
        (config) store meter files in: "/var/log/wmbusmeters/meter_readings"
        (config) using device: /dev/ttyUSB0:im871a:t1
        (config) number of meters: 1
        [2021-07-17_16:31:43] [ALARM SpecifiedDeviceNotFound] the device /dev/ttyUSB0:im871a:t1 is not working
        (shell) exec "/bin/sh"
        (shell) arg "-c"
        (shell) arg "/usr/local/bin/mosquitto_pub -d -h localhost -t wmbusmeters_alarm -m "$ALARM_TYPE $ALARM_MESSAGE""
        (shell) env "ALARM_TYPE=SpecifiedDeviceNotFound"
        (shell) env "ALARM_MESSAGE=[ALARM SpecifiedDeviceNotFound] the device /dev/ttyUSB0:im871a:t1 is not working"
        (shell) waiting for child 7033 to complete.
        (shell) /bin/sh: return code 127
        [2021-07-17_16:31:44] (shell) /bin/sh exited with non-zero return code: 127
        (serial) EVENT thread interrupted
        No wmbus device detected, waiting for a device to be plugged in.
        (shell) exec (capture output) "/bin/pidof"
        (shell) arg "wmbusmetersd"
        (shell) output: >>>7030
        <<<
        (serial) EVENT thread interrupted
        (shell) return code 0
        (shell) 7035 exited
        (shell) exec (capture output) "/bin/pidof"
        (shell) arg "wmbusmeters"
        (shell) output: >>>652
        <<<
        (serial) EVENT thread interrupted
        (shell) return code 0
        (shell) 7036 exited
        Notice! Other wmbusmeters (pid 652) is running and it might hog any wmbus devices.
        (serial) registered regular callback HOT_PLUG_DETECTOR(0) every 2 seconds
        (wmbusmeters) waiting for telegrams
        (serial) waiting for stop
        (serial) EVENT thread interrupted
        (serial) TIMER thread interrupted
        [2021-07-17_16:31:46] (memory) rss 2818048 peak 2.68 MiB
        pi@raspberrypi:~ $
        

        Hier sieht es für mich so aus, als ob der USB Stick nicht erkannt wird. Muss man da evtl. einen Treiber installieren?

        pi@raspberrypi:~ $ lsusb
        Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
        Bus 001 Device 003: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109 UART Bridge Controller [CP210x family]
        Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
        Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
        pi@raspberrypi:~ $ ls -l /dev/serial/by-id
        insgesamt 0
        lrwxrwxrwx 1 root root 13 Jul 17 16:06 usb-Silicon_Labs_WiMOD_iM871A-usb_00919907-if00-port0 -> ../../ttyUSB0
        pi@raspberrypi:~ $
        
        M 1 Antwort Letzte Antwort
        0
        • W WolfgangFB

          @matze-dev

          Ich habe jetzt nochmal eine jungfräuliche SD Karte genommen, ein neues Image installiert

          pi@raspberrypi:~ $ lsb_release -a
          No LSB modules are available.
          Distributor ID: Raspbian
          Description:    Raspbian GNU/Linux 10 (buster)
          Release:        10
          Codename:       buster
          

          mosqutto installiert

          sudo apt-get install mosquitto
          
          pi@raspberrypi:~ $ apt policy mosquitto
          mosquitto:
            Installiert:           1.5.7-1+deb10u1
            Installationskandidat: 1.5.7-1+deb10u1
            Versionstabelle:
           *** 1.5.7-1+deb10u1 500
                  500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
                  100 /var/lib/dpkg/status
          

          und den wmbusmeters aus den Quellen installiert

          pi@raspberrypi:~ $ more /etc/wmbusmeters.conf
          loglevel=debug
          device=/dev/ttyUSB0:im871a:t1
          logtelegrams=true
          format=json
          meterfiles=/var/log/wmbusmeters/meter_readings
          meterfilesaction=append
          meterfilesnaming=name
          meterfilestimestamp=day
          logfile=/var/log/wmbusmeters/wmbusmeters.log
          shell=/usr/local/bin/mosquitto_pub -d -h localhost -t wmbusmeters/$METER_ID -m "$METER_JSON"
          alarmshell=/usr/local/bin/mosquitto_pub -d -h localhost -t wmbusmeters_alarm -m "$ALARM_TYPE $ALARM_MESSAGE"
          alarmtimeout=1h
          alarmexpectedactivity=mon-sun(00-23)
          
          pi@raspberrypi:~ $ more /etc/wmbusmeters.d/MyTapWater
          name=MyTapWater
          type=multical21
          id=57813696
          key=E4E7EAF6FD17EAFB9587BC2996783C63
          
          pi@raspberrypi:~ $ sudo systemctl status wmbusmeters
          ● wmbusmeters.service - "wmbusmeters service"
             Loaded: loaded (/lib/systemd/system/wmbusmeters.service; disabled; vendor preset: enabled)
             Active: active (running) since Sat 2021-07-17 16:14:49 CEST; 9min ago
               Docs: https://github.com/weetmuts/wmbusmeters
                     man:wmbusmeters(1)
            Process: 2774 ExecStartPre=/bin/mkdir -p /var/log/wmbusmeters/meter_readings (code=exited, status=0/SUCCESS)
            Process: 2775 ExecStartPre=/bin/chown -R wmbusmeters:wmbusmeters /var/log/wmbusmeters (code=exited, status=0/SUCCESS)
            Process: 2776 ExecStartPre=/bin/mkdir -p /run/wmbusmeters (code=exited, status=0/SUCCESS)
            Process: 2777 ExecStartPre=/bin/chown -R wmbusmeters:wmbusmeters /run/wmbusmeters (code=exited, status=0/SUCCESS)
            Process: 2778 ExecStart=/usr/sbin/wmbusmetersd /run/wmbusmeters/wmbusmeters.pid (code=exited, status=0/SUCCESS)
           Main PID: 2779 (wmbusmetersd)
              Tasks: 3 (limit: 4915)
             CGroup: /system.slice/wmbusmeters.service
                     └─2779 /usr/sbin/wmbusmetersd /run/wmbusmeters/wmbusmeters.pid
          
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) "alarmshell" "/usr/local/bin/mosquitto_pub -d -h localhost -t w
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) "alarmtimeout" "1h"
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) "alarmexpectedactivity" "mon-sun(00-23)"
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) "" ""
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) loading meter file /etc/wmbusmeters.d/MyTapWater
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) name=MyTapWater
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) type=multical21
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) id=57813696
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (config) key=<notprinted>
          Jul 17 16:14:49 raspberrypi wmbusmetersd[2779]: (wmbusmeters) using log file /var/log/wmbusmeters/wmbusmeters.log
          pi@raspberrypi:~ $                                                                                   
          
          pi@raspberrypi:~ $ more /var/log/wmbusmeters/wmbusmeters.log
          (serial) stopping manager
          (serial) EVENT thread interrupted
          (serial) event loop stopped!
          (serial) TIMER thread interrupted
          (wmbusmeters) shutting down
          (wmbusmeters) logging started 2021-07-17 16:31:43 using _
          (wmbusmeters) version: _
          (config) store meter files in: "/var/log/wmbusmeters/meter_readings"
          (config) using device: /dev/ttyUSB0:im871a:t1
          (config) number of meters: 1
          [2021-07-17_16:31:43] [ALARM SpecifiedDeviceNotFound] the device /dev/ttyUSB0:im871a:t1 is not working
          (shell) exec "/bin/sh"
          (shell) arg "-c"
          (shell) arg "/usr/local/bin/mosquitto_pub -d -h localhost -t wmbusmeters_alarm -m "$ALARM_TYPE $ALARM_MESSAGE""
          (shell) env "ALARM_TYPE=SpecifiedDeviceNotFound"
          (shell) env "ALARM_MESSAGE=[ALARM SpecifiedDeviceNotFound] the device /dev/ttyUSB0:im871a:t1 is not working"
          (shell) waiting for child 7033 to complete.
          (shell) /bin/sh: return code 127
          [2021-07-17_16:31:44] (shell) /bin/sh exited with non-zero return code: 127
          (serial) EVENT thread interrupted
          No wmbus device detected, waiting for a device to be plugged in.
          (shell) exec (capture output) "/bin/pidof"
          (shell) arg "wmbusmetersd"
          (shell) output: >>>7030
          <<<
          (serial) EVENT thread interrupted
          (shell) return code 0
          (shell) 7035 exited
          (shell) exec (capture output) "/bin/pidof"
          (shell) arg "wmbusmeters"
          (shell) output: >>>652
          <<<
          (serial) EVENT thread interrupted
          (shell) return code 0
          (shell) 7036 exited
          Notice! Other wmbusmeters (pid 652) is running and it might hog any wmbus devices.
          (serial) registered regular callback HOT_PLUG_DETECTOR(0) every 2 seconds
          (wmbusmeters) waiting for telegrams
          (serial) waiting for stop
          (serial) EVENT thread interrupted
          (serial) TIMER thread interrupted
          [2021-07-17_16:31:46] (memory) rss 2818048 peak 2.68 MiB
          pi@raspberrypi:~ $
          

          Hier sieht es für mich so aus, als ob der USB Stick nicht erkannt wird. Muss man da evtl. einen Treiber installieren?

          pi@raspberrypi:~ $ lsusb
          Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
          Bus 001 Device 003: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109 UART Bridge Controller [CP210x family]
          Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
          Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          pi@raspberrypi:~ $ ls -l /dev/serial/by-id
          insgesamt 0
          lrwxrwxrwx 1 root root 13 Jul 17 16:06 usb-Silicon_Labs_WiMOD_iM871A-usb_00919907-if00-port0 -> ../../ttyUSB0
          pi@raspberrypi:~ $
          
          M Offline
          M Offline
          matze-dev
          schrieb am zuletzt editiert von
          #59

          @wolfgangfb hallo, gibt's die Datei /etc/wmbusmeters.d/MyTapWater, wie oben beschrieben?

          1 Antwort Letzte Antwort
          0
          • W Offline
            W Offline
            WolfgangFB
            schrieb am zuletzt editiert von
            #60

            @matze-dev

            Ja, habe ich ja mit

             more /etc/wmbusmeters.d/MyTapWater
            

            angezeigt, dann muss es sie ja auch geben.
            Darin sehe ich aber nichts was mir die Meldung im wmbusmeters.log (DeviceNotFound) erklären würde.

            Wie sieht den Dein wmbusmeters.log aus?

            M 1 Antwort Letzte Antwort
            0
            • W WolfgangFB

              @matze-dev

              Ja, habe ich ja mit

               more /etc/wmbusmeters.d/MyTapWater
              

              angezeigt, dann muss es sie ja auch geben.
              Darin sehe ich aber nichts was mir die Meldung im wmbusmeters.log (DeviceNotFound) erklären würde.

              Wie sieht den Dein wmbusmeters.log aus?

              M Offline
              M Offline
              matze-dev
              schrieb am zuletzt editiert von
              #61

              @wolfgangfb sind da auch der Key drin und die Zähler ID?

              M W 2 Antworten Letzte Antwort
              0
              • M matze-dev

                @wolfgangfb sind da auch der Key drin und die Zähler ID?

                M Offline
                M Offline
                matze-dev
                schrieb am zuletzt editiert von
                #62

                @matze-dev
                Das muss in der MyTapWater stehen

                name=MyTapWater
                type=multical21
                id=##der Name/ID des Zaehlers ##
                key=##hier den Key eintragen - kommt aus der zugeschickten XML-Datei des Wasserversorgers##

                1 Antwort Letzte Antwort
                0
                • M matze-dev

                  @wolfgangfb sind da auch der Key drin und die Zähler ID?

                  W Offline
                  W Offline
                  WolfgangFB
                  schrieb am zuletzt editiert von
                  #63

                  @matze-dev

                  Ja, habe ich doch in meinem Beitrag alles gequoted (incl. Key weil ich nicht denke, dass damit irgend jemand etwas anfangen kann). Fünfter Codeblock.

                  M 1 Antwort Letzte Antwort
                  0
                  • W WolfgangFB

                    @matze-dev

                    Ja, habe ich doch in meinem Beitrag alles gequoted (incl. Key weil ich nicht denke, dass damit irgend jemand etwas anfangen kann). Fünfter Codeblock.

                    M Offline
                    M Offline
                    matze-dev
                    schrieb am zuletzt editiert von
                    #64

                    @wolfgangfb ok, habe es gesehen.

                    W 1 Antwort Letzte Antwort
                    0
                    • M matze-dev

                      @wolfgangfb ok, habe es gesehen.

                      W Offline
                      W Offline
                      WolfgangFB
                      schrieb am zuletzt editiert von
                      #65

                      @matze-dev

                      Ich denke das Entscheidende ist die Zeile

                      [2021-07-17_16:31:43] [ALARM SpecifiedDeviceNotFound] the device /dev/ttyUSB0:im871a:t1 is not working
                      

                      aus

                       more /var/log/wmbusmeters/wmbusmeters.log
                      

                      Codeblock 7

                      M 1 Antwort Letzte Antwort
                      0
                      • W WolfgangFB

                        @matze-dev

                        Ich denke das Entscheidende ist die Zeile

                        [2021-07-17_16:31:43] [ALARM SpecifiedDeviceNotFound] the device /dev/ttyUSB0:im871a:t1 is not working
                        

                        aus

                         more /var/log/wmbusmeters/wmbusmeters.log
                        

                        Codeblock 7

                        M Offline
                        M Offline
                        matze-dev
                        schrieb am zuletzt editiert von
                        #66

                        @wolfgangfb ja, das hätte ich auch als nächstes angemerkt.

                        W 1 Antwort Letzte Antwort
                        0
                        • M matze-dev

                          @wolfgangfb ja, das hätte ich auch als nächstes angemerkt.

                          W Offline
                          W Offline
                          WolfgangFB
                          schrieb am zuletzt editiert von
                          #67

                          @matze-dev
                          Muss man da irgendeinen Treiber installieren?

                          M 1 Antwort Letzte Antwort
                          0
                          • W WolfgangFB

                            @matze-dev
                            Muss man da irgendeinen Treiber installieren?

                            M Offline
                            M Offline
                            matze-dev
                            schrieb am zuletzt editiert von
                            #68

                            @wolfgangfb nein, das macht der wmbusmeters. D.h. der ist der Treiber für das Device.

                            M 1 Antwort Letzte Antwort
                            0
                            • M matze-dev

                              @wolfgangfb nein, das macht der wmbusmeters. D.h. der ist der Treiber für das Device.

                              M Offline
                              M Offline
                              matze-dev
                              schrieb am zuletzt editiert von
                              #69

                              @matze-dev gibt's in dem Verzeichnis auch noch Dateien /var/log/wmbusmeters/meter_readings?

                              W 1 Antwort Letzte Antwort
                              0
                              • M matze-dev

                                @matze-dev gibt's in dem Verzeichnis auch noch Dateien /var/log/wmbusmeters/meter_readings?

                                W Offline
                                W Offline
                                WolfgangFB
                                schrieb am zuletzt editiert von
                                #70

                                @matze-dev

                                Das Verzeichnis existiert ist aber leer (was ja auch logisch ist, wenn nichts gelesen werden kann).

                                M 1 Antwort Letzte Antwort
                                0
                                • W WolfgangFB

                                  @matze-dev

                                  Das Verzeichnis existiert ist aber leer (was ja auch logisch ist, wenn nichts gelesen werden kann).

                                  M Offline
                                  M Offline
                                  matze-dev
                                  schrieb am zuletzt editiert von
                                  #71

                                  @wolfgangfb hier gibt's einen Threat
                                  https://github.com/weetmuts/wmbusmeters/issues/286
                                  Ich würde mal in Richtung udev schauen, in meiner alten Version musste ich da noch was machen, die neue Software braucht das wohl nicht mehr.

                                  M 1 Antwort Letzte Antwort
                                  0
                                  • M matze-dev

                                    @wolfgangfb hier gibt's einen Threat
                                    https://github.com/weetmuts/wmbusmeters/issues/286
                                    Ich würde mal in Richtung udev schauen, in meiner alten Version musste ich da noch was machen, die neue Software braucht das wohl nicht mehr.

                                    M Offline
                                    M Offline
                                    matze-dev
                                    schrieb am zuletzt editiert von
                                    #72

                                    @matze-dev Was sagt denn der Befehl:
                                    wmbusmeters --debug auto:t1 MyTapWater auto 57813696 E4E7EAF6FD17EAFB9587BC2996783C63

                                    M 1 Antwort Letzte Antwort
                                    0
                                    • M matze-dev

                                      @matze-dev Was sagt denn der Befehl:
                                      wmbusmeters --debug auto:t1 MyTapWater auto 57813696 E4E7EAF6FD17EAFB9587BC2996783C63

                                      M Offline
                                      M Offline
                                      matze-dev
                                      schrieb am zuletzt editiert von matze-dev
                                      #73

                                      @matze-dev Änderung, die vorher hier abgelegte Installationsanleitung ist heraus genommen, die komplette Doku findet sich weiter unten.

                                      W 1 Antwort Letzte Antwort
                                      0
                                      • M matze-dev

                                        @matze-dev Änderung, die vorher hier abgelegte Installationsanleitung ist heraus genommen, die komplette Doku findet sich weiter unten.

                                        W Offline
                                        W Offline
                                        WolfgangFB
                                        schrieb am zuletzt editiert von
                                        #74

                                        @matze-dev

                                        pi@raspberrypi:~ $ wmbusmeters --debug auto:t1 MyTapWater auto 57813696 E4E7EAF6FD17EAFB9587BC2996783C63
                                        (wmbusmeters) version: _
                                        (config) number of meters: 1
                                        (main) device /dev/ttyAMA0 not currently used, detect contents...
                                        (serial) EVENT thread interrupted
                                        (serial) before config: /dev/ttyAMA0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                        (serial) after config:  /dev/ttyAMA0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                        (serialtty) opened /dev/ttyAMA0 fd 3 (detect amb8465)
                                        (serial) received binary ""
                                        (serial /dev/ttyAMA0) sent "FF0A02008077"
                                        (serial /dev/ttyAMA0) sent "FF0A02008077"
                                        (serial) EVENT thread interrupted
                                        (serial) received binary ""
                                        (serial) received binary ""
                                        (serialtty) closed /dev/ttyAMA0 (detect amb8465)
                                        (amb8465) are you there? no.
                                        (serial) EVENT thread interrupted
                                        (serial) EVENT thread interrupted
                                        (serial) before config: /dev/ttyAMA0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                        (serial) after config:  /dev/ttyAMA0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                        (serialtty) opened /dev/ttyAMA0 fd 3 (detect im871a)
                                        (serial) received binary ""
                                        (serial /dev/ttyAMA0) sent "A5010F00"
                                        (serial) EVENT thread interrupted
                                        (serial) received binary ""
                                        (im871a/im170a) are you there? no.
                                        (serialtty) closed /dev/ttyAMA0 (detect im871a)
                                        (serial) EVENT thread interrupted
                                        (serial) before config: /dev/ttyAMA0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                        (serial) after config:  /dev/ttyAMA0 speed(B19200) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                        (serialtty) opened /dev/ttyAMA0 fd 3 (detect rc1180)
                                        (serial /dev/ttyAMA0) sent "00"
                                        (serial) EVENT thread interrupted
                                        (serial) received binary ""
                                        (serial /dev/ttyAMA0) sent "30"
                                        (serial) EVENT thread interrupted
                                        (serial) received binary ""
                                        (serialtty) closed /dev/ttyAMA0 (detect rc1180)
                                        (rc1180) are you there? no.
                                        (serial) EVENT thread interrupted
                                        (serial) EVENT thread interrupted
                                        (serial) before config: /dev/ttyAMA0 speed(B19200) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                        (serial) after config:  /dev/ttyAMA0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                        (serialtty) opened /dev/ttyAMA0 fd 3 (detect cul)
                                        (serial /dev/ttyAMA0) sent "560A0D"
                                        (serial) EVENT thread interrupted
                                        (serial) received binary ""
                                        (cul) probe response ""
                                        (serial /dev/ttyAMA0) sent "560A0D"
                                        (serial) EVENT thread interrupted
                                        (serial) received binary ""
                                        (cul) probe response ""
                                        (serial /dev/ttyAMA0) sent "560A0D"
                                        (serial) EVENT thread interrupted
                                        (serial) received binary ""
                                        (cul) probe response ""
                                        (serialtty) closed /dev/ttyAMA0 (detect cul)
                                        (cul) are you there? no
                                        (serial) EVENT thread interrupted
                                        (main) ignoring /dev/ttyAMA0, it does not respond as any of the supported wmbus devices.
                                        (main) device /dev/ttyUSB0 not currently used, detect contents...
                                        (serial) EVENT thread interrupted
                                        (serial) EVENT thread interrupted
                                        (serial) EVENT thread interrupted
                                        (serial) EVENT thread interrupted
                                        (main) ignoring /dev/ttyUSB0, it does not respond as any of the supported wmbus devices.
                                        No wmbus device detected, waiting for a device to be plugged in.
                                        (shell) exec (capture output) "/bin/pidof"
                                        (shell) arg "wmbusmetersd"
                                        (serial) EVENT thread interrupted
                                        (shell) return code 1
                                        (shell) 1824 exited
                                        (shell) exec (capture output) "/bin/pidof"
                                        (shell) arg "wmbusmeters"
                                        (serial) EVENT thread interrupted
                                        (shell) return code 0
                                        (shell) 1825 exited
                                        Notice! Other wmbusmeters (pid 673) is running and it might hog any wmbus devices.
                                        (serial) registered regular callback HOT_PLUG_DETECTOR(0) every 2 seconds
                                        (serial) waiting for stop
                                        
                                        M Thomas BraunT 2 Antworten Letzte Antwort
                                        0
                                        • W WolfgangFB

                                          @matze-dev

                                          pi@raspberrypi:~ $ wmbusmeters --debug auto:t1 MyTapWater auto 57813696 E4E7EAF6FD17EAFB9587BC2996783C63
                                          (wmbusmeters) version: _
                                          (config) number of meters: 1
                                          (main) device /dev/ttyAMA0 not currently used, detect contents...
                                          (serial) EVENT thread interrupted
                                          (serial) before config: /dev/ttyAMA0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                          (serial) after config:  /dev/ttyAMA0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                          (serialtty) opened /dev/ttyAMA0 fd 3 (detect amb8465)
                                          (serial) received binary ""
                                          (serial /dev/ttyAMA0) sent "FF0A02008077"
                                          (serial /dev/ttyAMA0) sent "FF0A02008077"
                                          (serial) EVENT thread interrupted
                                          (serial) received binary ""
                                          (serial) received binary ""
                                          (serialtty) closed /dev/ttyAMA0 (detect amb8465)
                                          (amb8465) are you there? no.
                                          (serial) EVENT thread interrupted
                                          (serial) EVENT thread interrupted
                                          (serial) before config: /dev/ttyAMA0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                          (serial) after config:  /dev/ttyAMA0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                          (serialtty) opened /dev/ttyAMA0 fd 3 (detect im871a)
                                          (serial) received binary ""
                                          (serial /dev/ttyAMA0) sent "A5010F00"
                                          (serial) EVENT thread interrupted
                                          (serial) received binary ""
                                          (im871a/im170a) are you there? no.
                                          (serialtty) closed /dev/ttyAMA0 (detect im871a)
                                          (serial) EVENT thread interrupted
                                          (serial) before config: /dev/ttyAMA0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                          (serial) after config:  /dev/ttyAMA0 speed(B19200) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                          (serialtty) opened /dev/ttyAMA0 fd 3 (detect rc1180)
                                          (serial /dev/ttyAMA0) sent "00"
                                          (serial) EVENT thread interrupted
                                          (serial) received binary ""
                                          (serial /dev/ttyAMA0) sent "30"
                                          (serial) EVENT thread interrupted
                                          (serial) received binary ""
                                          (serialtty) closed /dev/ttyAMA0 (detect rc1180)
                                          (rc1180) are you there? no.
                                          (serial) EVENT thread interrupted
                                          (serial) EVENT thread interrupted
                                          (serial) before config: /dev/ttyAMA0 speed(B19200) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                          (serial) after config:  /dev/ttyAMA0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS|CTS)
                                          (serialtty) opened /dev/ttyAMA0 fd 3 (detect cul)
                                          (serial /dev/ttyAMA0) sent "560A0D"
                                          (serial) EVENT thread interrupted
                                          (serial) received binary ""
                                          (cul) probe response ""
                                          (serial /dev/ttyAMA0) sent "560A0D"
                                          (serial) EVENT thread interrupted
                                          (serial) received binary ""
                                          (cul) probe response ""
                                          (serial /dev/ttyAMA0) sent "560A0D"
                                          (serial) EVENT thread interrupted
                                          (serial) received binary ""
                                          (cul) probe response ""
                                          (serialtty) closed /dev/ttyAMA0 (detect cul)
                                          (cul) are you there? no
                                          (serial) EVENT thread interrupted
                                          (main) ignoring /dev/ttyAMA0, it does not respond as any of the supported wmbus devices.
                                          (main) device /dev/ttyUSB0 not currently used, detect contents...
                                          (serial) EVENT thread interrupted
                                          (serial) EVENT thread interrupted
                                          (serial) EVENT thread interrupted
                                          (serial) EVENT thread interrupted
                                          (main) ignoring /dev/ttyUSB0, it does not respond as any of the supported wmbus devices.
                                          No wmbus device detected, waiting for a device to be plugged in.
                                          (shell) exec (capture output) "/bin/pidof"
                                          (shell) arg "wmbusmetersd"
                                          (serial) EVENT thread interrupted
                                          (shell) return code 1
                                          (shell) 1824 exited
                                          (shell) exec (capture output) "/bin/pidof"
                                          (shell) arg "wmbusmeters"
                                          (serial) EVENT thread interrupted
                                          (shell) return code 0
                                          (shell) 1825 exited
                                          Notice! Other wmbusmeters (pid 673) is running and it might hog any wmbus devices.
                                          (serial) registered regular callback HOT_PLUG_DETECTOR(0) every 2 seconds
                                          (serial) waiting for stop
                                          
                                          M Offline
                                          M Offline
                                          matze-dev
                                          schrieb am zuletzt editiert von matze-dev
                                          #75

                                          @wolfgangfb schau Dir mal meine hochgeladene Install-Doku an. Vielleicht kommst Du damit weiter.

                                          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
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          818

                                          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