Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Adapter WM-Bus / Kampstrup Multical 21

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    Adapter WM-Bus / Kampstrup Multical 21

    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      WolfgangFB @matze-dev last edited by

      @matze-dev

      Danke für die Hilfe. Klappt aber leider noch nicht ganz

      pi@raspberrypi4:~/wmbusmeters-master $ sudo make DEBUG=true
[viel erfolgreiches gelöscht]
g++ -O0 -ggdb -fsanitize=address -fno-omit-frame-pointer -fprofile-arcs -ftest-coverage -fPIC -std=c++11 -Wall -Werror=format-security -Ibuild_debug src/rtlsdr.cc -c -E > build_debug/rtlsdr.o.src
src/rtlsdr.cc:24:9: fatal error: rtl-sdr.h: Datei oder Verzeichnis nicht gefunden
 #include<rtl-sdr.h>
         ^~~~~~~~~~~
compilation terminated.
make: *** [Makefile:104: build_debug/rtlsdr.o] Fehler 1
      Thomas Braun 1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @WolfgangFB last edited by

        @wolfgangfb

        Da fehlt das Paket librtlsdr-dev

        W 1 Reply Last reply Reply Quote 0
        • W
          WolfgangFB @Thomas Braun last edited by

          @thomas-braun

          Wo bekomme ich das her?

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

            @wolfgangfb

            Wie die meisten Pakete auch:

            sudo apt install <Paketname>

            sudo apt install librtlsdr-dev

            also. Kann aber sein dass da auch noch anderes fehlt.

            W 1 Reply Last reply Reply Quote 0
            • W
              WolfgangFB @Thomas Braun last edited by

              @thomas-braun

              Danke!
              Das sind aber genau die Punkte, an denen ich immer hängen bleibe. Für Leute, die das 1000 mal gemacht haben, ist das klar, mir hilft die Zeile mit dem Befehl aber enorm.

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

                @wolfgangfb

                librtlsdr-dev habe ich noch nie installiert. 😆

                W 1 Reply Last reply Reply Quote 0
                • W
                  WolfgangFB @Thomas Braun last edited by

                  @thomas-braun

                  OK, nächstes Paket das fehlt:

                  g++ -O0 -ggdb -fsanitize=address -fno-omit-frame-pointer -fprofile-arcs -ftest-coverage -fPIC -std=c++11 -Wall -Werror=format-security -Ibuild_debug src/admin.cc -c -E > build_debug/admin.o.src
In file included from src/admin.cc:26:
src/ui.h:22:9: fatal error: curses.h: Datei oder Verzeichnis nicht gefunden
 #include<curses.h>
         ^~~~~~~~~~
compilation terminated.

                  Woher hast Du beim ersten mal gewusst, dass da librtlsdr-dev fehlt und was fehlt diesmal?

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

                    @wolfgangfb

                    libncurses-dev

                    Kann man hier nachschauen:

                    https://www.debian.org/distrib/packages

                    W 1 Reply Last reply Reply Quote 0
                    • W
                      WolfgangFB @Thomas Braun last edited by

                      @thomas-braun

                      Danke!

                      1 Reply Last reply Reply Quote 0
                      • W
                        WolfgangFB @matze-dev last edited by

                        @matze-dev

                        So, ich denke wmbusmeters läuft jetzt (sieht zumindest grün aus).

                        pi@raspberrypi4:/var/log/wmbusmeters/meter_readings $ systemctl status wmbusmeters
● wmbusmeters.service - "wmbusmeters service"
   Loaded: loaded (/lib/systemd/system/wmbusmeters.service; disabled; vendor preset: enabled)
   Active: active (running) since Tue 2021-07-13 23:12:55 CEST; 3s ago
     Docs: https://github.com/weetmuts/wmbusmeters
           man:wmbusmeters(1)
  Process: 12466 ExecStartPre=/bin/mkdir -p /var/log/wmbusmeters/meter_readings (code=exited, status=0/SUCCESS)
  Process: 12467 ExecStartPre=/bin/chown -R wmbusmeters:wmbusmeters /var/log/wmbusmeters (code=exited, status=0/SUCCESS)
  Process: 12468 ExecStartPre=/bin/mkdir -p /run/wmbusmeters (code=exited, status=0/SUCCESS)
  Process: 12469 ExecStartPre=/bin/chown -R wmbusmeters:wmbusmeters /run/wmbusmeters (code=exited, status=0/SUCCESS)
  Process: 12470 ExecStart=/usr/sbin/wmbusmetersd /run/wmbusmeters/wmbusmeters.pid (code=exited, status=0/SUCCESS)
 Main PID: 12471 (wmbusmetersd)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/wmbusmeters.service
           └─12471 /usr/sbin/wmbusmetersd /run/wmbusmeters/wmbusmeters.pid

Jul 13 23:12:55 raspberrypi4 systemd[1]: Starting "wmbusmeters service"...
Jul 13 23:12:55 raspberrypi4 wmbusmetersd[12470]: (wmbusmeters) started /run/wmbusmeters/wmbusmeters.pid
Jul 13 23:12:55 raspberrypi4 systemd[1]: Started "wmbusmeters service".
pi@raspberrypi4:/var/log/wmbusmeters/meter_readings $

                        was mich stört ist

                        pi@raspberrypi4:/var/log/wmbusmeters/meter_readings $
pi@raspberrypi4:/var/log/wmbusmeters/meter_readings $ more /var/log/wmbusmeters/wmbusmeters.log
(wmbusmeters) logging started 2021-07-13 22:40:08 using _
(wmbusmeters) logging started 2021-07-13 23:12:55 using _
[2021-07-13_23:12:56] Started config im871a[00100776] on /dev/ttyUSB0 listening on none
[2021-07-13_23:12:56] Warning! Desired link modes none cannot be set for device /dev/ttyUSB0:im871a[00100776]
(wmbusmeters) waiting for telegrams
[2021-07-13_23:12:58] (memory) rss 2048000 peak 1.95 MiB

                        pi@raspberrypi4:/var/log/wmbusmeters/meter_readings $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0458:0007 KYE Systems Corp. (Mouse Systems)
Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 0451:16a8 Texas Instruments, Inc.
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@raspberrypi4:/var/log/wmbusmeters/meter_readings $ ls -l /dev/serial/by-id
insgesamt 0
lrwxrwxrwx 1 root root 13 Jun 16 14:34 usb-Silicon_Labs_WiMOD_iM871A-usb_00919907-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Jun 16 14:34 usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CD40626-if00 -> ../../ttyACM0

                        mosquitto scheint prinzipiell auch zu laufen:

                        pi@raspberrypi4:/var/log/wmbusmeters/meter_readings $ mosquitto
1626210924: mosquitto version 1.5.7 starting
1626210924: Using default config.
1626210924: Opening ipv4 listen socket on port 1883.
1626210924: Error: Address already in use

                        Aber was ist mit dem Error "Address already in use"? gemeint?

                        Im IO-Broker bleibt der mqtt Adapter rot (im Logfile steht nichts)

                        M 1 Reply Last reply Reply Quote 0
                        • M
                          matze-dev @WolfgangFB last edited by

                          @wolfgangfb: das ist korrekt - die "Fehlermeldung" kommt bei mir auch. Ist aber das "falsche" Kommando, weil der wmbusmeters-Treiber laut Konfig-Zeile das Programm /usr/local/bin/mosquitto_pub aufruft - wenn das bei Dir auch so in der /etc/wmbusmeters.conf steht.
                          Du siehst den Erfolg nur in den Logfiles, wenn da was steht, passt es!

                          W 1 Reply Last reply Reply Quote 0
                          • W
                            WolfgangFB @matze-dev last edited by

                            @matze-dev

                            Hallo

                            In dem Logfile steht leider nichts gutes:

                            pi@raspberrypi4:/var/log/wmbusmeters $ more wmbusmeters.log
(wmbusmeters) logging started 2021-07-13 22:40:08 using _
(wmbusmeters) logging started 2021-07-13 23:12:55 using _
[2021-07-13_23:12:56] Started config im871a[00100776] on /dev/ttyUSB0 listening on none
[2021-07-13_23:12:56] Warning! Desired link modes none cannot be set for device /dev/ttyUSB0:im871a[00100776]
(wmbusmeters) waiting for telegrams
[2021-07-13_23:12:58] (memory) rss 2048000 peak 1.95 MiB
[2021-07-14_00:12:56] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s expected mon-s
un(00-23) now 2021-07-14 00:12)
[2021-07-14_00:12:56] (shell) /bin/sh exited with non-zero return code: 127
[2021-07-14_00:12:56] (wmbus) resetting /dev/ttyUSB0
[2021-07-14_00:12:59] (wmbus) successfully reset wmbus device
[2021-07-14_01:12:56] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s expected mon-s
un(00-23) now 2021-07-14 01:12)
[2021-07-14_01:12:56] (shell) /bin/sh exited with non-zero return code: 127
[2021-07-14_01:12:56] (wmbus) resetting /dev/ttyUSB0
[2021-07-14_01:12:59] (wmbus) successfully reset wmbus device
[2021-07-14_02:12:56] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s expected mon-s
un(00-23) now 2021-07-14 02:12)
                            M 1 Reply Last reply Reply Quote 0
                            • M
                              matze-dev @WolfgangFB last edited by

                              @wolfgangfb said in Adapter WM-Bus / Kampstrup Multical 21:

                              Warning! Desired link modes none cannot be set for device /dev/ttyUSB0:im871a[00100776]

                              Dieses Warning ist komisch!? Ich habe bei mir die Datagramme im T1-Mode.
                              Dann müsste in der /etc/wmbusmeters.conf
                              die Zeile so stehen:
                              device=/dev/ttyUSB0:im871a:t1
                              ggfs. kann man hinten das :t1 weglassen - müsste man versuchen.

                              Dann ist noch wichtig, den AES-Key hier zu hinterlegen:
                              /etc/wmbusmeters.d/MyTapWater
                              key=xxxxxxxxxxxxxxxxxxx

                              Viel Glück

                              W 1 Reply Last reply Reply Quote 0
                              • W
                                WolfgangFB @matze-dev last edited by

                                @matze-dev
                                Die Warning ist jetzt zumindest weg, mal sehn ob innerhalb der nächsten Stunde was ankommt.

                                (wmbusmeters) shutting down
(wmbusmeters) logging started 2021-07-14 16:46:20 using _
[2021-07-14_16:46:20] Started config im871a[00100776] on /dev/ttyUSB0 listening on t1
(wmbusmeters) waiting for telegrams
[2021-07-14_16:46:22] (memory) rss 1953792 peak 1.86 MiB
pi@raspberrypi4:/var/log/wmbusmeters $
                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  matze-dev @WolfgangFB last edited by matze-dev

                                  @wolfgangfb einfach die Daten mitlesen
                                  tail -f /var/log/wmbusmeters/wmbusmeters.log

                                  Viel Glück

                                  W 1 Reply Last reply Reply Quote 0
                                  • W
                                    WolfgangFB @matze-dev last edited by

                                    @matze-dev

                                    da kommt nichts

                                    pi@raspberrypi4:/var/log/wmbusmeters $  tail -f /var/log/wmbusmeters/wmbusmeters.log
[2021-07-14_16:13:00] (wmbus) successfully reset wmbus device
(wmbusmeters) shutting down
(wmbusmeters) logging started 2021-07-14 16:46:20 using _
[2021-07-14_16:46:20] Started config im871a[00100776] on /dev/ttyUSB0 listening on t1
(wmbusmeters) waiting for telegrams
[2021-07-14_16:46:22] (memory) rss 1953792 peak 1.86 MiB
[2021-07-14_17:46:20] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s expected mon-sun(00-23) now 2021-07-14 17:46)
[2021-07-14_17:46:20] (shell) /bin/sh exited with non-zero return code: 127
[2021-07-14_17:46:20] (wmbus) resetting /dev/ttyUSB0
[2021-07-14_17:46:23] (wmbus) successfully reset wmbus device
                                    M 1 Reply Last reply Reply Quote 0
                                    • M
                                      matze-dev @WolfgangFB last edited by

                                      @wolfgangfb ja, da scheint nichts anzukommen. Ausserdem macht er ein Reset. Das ist ungewöhnlich.
                                      Was sagt denn
                                      journalctl -f
                                      dmesg?

                                      W 1 Reply Last reply Reply Quote 0
                                      • W
                                        WolfgangFB @matze-dev last edited by

                                        @matze-dev

                                        pi@raspberrypi4:/var/log/wmbusmeters $   journalctl -f
-- Logs begin at Thu 2019-02-14 11:11:59 CET. --
Jul 14 19:48:06 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:06 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:07 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:07 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:08 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:09 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:10 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:10 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:10 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:12 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:12 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:13 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:13 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:14 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:15 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:16 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:17 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:17 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:18 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:18 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:18 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:19 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Jul 14 19:48:19 raspberrypi4 kernel: Bluetooth: hci0: Frame reassembly failed (-84)

                                        demesg
[204619.514651] Bluetooth: hci0: Frame reassembly failed (-84)
[204620.459730] Bluetooth: hci0: Frame reassembly failed (-84)
[204620.930504] Bluetooth: hci0: Frame reassembly failed (-84)
[204620.953443] Bluetooth: hci0: Frame reassembly failed (-84)
[204621.105377] Bluetooth: hci0: Frame reassembly failed (-84)
[204622.176851] Bluetooth: hci0: Frame reassembly failed (-84)
[204622.275958] Bluetooth: hci0: Frame reassembly failed (-84)
[204622.470953] Bluetooth: hci0: Frame reassembly failed (-84)
[204622.830382] Bluetooth: hci0: Frame reassembly failed (-84)
[204623.600358] Bluetooth: hci0: Frame reassembly failed (-84)
[204624.175987] Bluetooth: hci0: Frame reassembly failed (-84)
[204625.402258] Bluetooth: hci0: Frame reassembly failed (-84)
[204627.417943] Bluetooth: hci0: Frame reassembly failed (-84)
                                        M 1 Reply Last reply Reply Quote 0
                                        • M
                                          matze-dev @WolfgangFB last edited by

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

                                          W 1 Reply Last reply Reply Quote 0
                                          • W
                                            WolfgangFB @matze-dev last edited by

                                            @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 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

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

                                            901
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            12
                                            151
                                            16724
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo