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@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 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

      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 Reply Last reply Reply Quote 0
      • M
        matze-dev @WolfgangFB last edited by

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

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

          @matze-dev
          Muss man da irgendeinen Treiber installieren?

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

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

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

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

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

                @matze-dev

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

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

                  @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.

                  pswiatki created this issue in weetmuts/wmbusmeters

                  closed is my RTL-SDR dying, or something is wrong with wmbusmeters? #286

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

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

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

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

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

                        @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 Braun 2 Replies Last reply Reply Quote 0
                        • M
                          matze-dev @WolfgangFB last edited by matze-dev

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

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

                            @wolfgangfb

                            Notice! Other wmbusmeters (pid 673) is running and it might hog any wmbus devices.
                            W 1 Reply Last reply Reply Quote 0
                            • W
                              WolfgangFB @Thomas Braun last edited by

                              @thomas-braun

                              In wmbusmeters.log steht nichts.
                              Ich frage mich allerdings, wie ich den "Other wmbusmeters" in den Griff bekommen kann. Da start ständig eine neue Instanz.

                              pi@raspberrypi:/var/log/wmbusmeters/meter_readings $ sudo systemctl stop wmbusmeters
pi@raspberrypi:/var/log/wmbusmeters/meter_readings $ ps -aux | grep wmbus
root     16817  0.2  0.0   1468   392 ?        Ss   21:28   0:00 /snap/wmbusmeters/596/bin/sh /snap/wmbusmeters/596/launcher.sh
root     16841  0.2  0.0  23032  1448 ?        Sl   21:28   0:00 /snap/wmbusmeters/596/usr/bin/wmbusmeters --useconfig=/var/snap/wmbusmeters/common
pi       17054  0.0  0.0   7360   492 pts/0    S+   21:29   0:00 grep --color=auto wmbus
pi@raspberrypi:/var/log/wmbusmeters/meter_readings $ sudo kill -9 16817
pi@raspberrypi:/var/log/wmbusmeters/meter_readings $ ps -aux | grep wmbus
root     17125  2.6  0.0   1468   388 ?        Ss   21:29   0:00 /snap/wmbusmeters/596/bin/sh /snap/wmbusmeters/596/launcher.sh
root     17154  0.5  0.0  22008  1464 ?        Sl   21:29   0:00 /snap/wmbusmeters/596/usr/bin/wmbusmeters --useconfig=/var/snap/wmbusmeters/common
pi       17170  0.0  0.0   7360   496 pts/0    S+   21:29   0:00 grep --color=auto wmbus
pi@raspberrypi:/var/log/wmbusmeters/meter_readings $ 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 "0984488448844884"
(im871a) checkIM871AFrame "0984488448844884"
(im871a) frame does not start with a5 "0984488448844884"
(im871a) no a5 found at all, drop frame packet.
(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) 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 "540442205404E2"
(cul) probe response "T<04>B T<04><E2>"
(serial /dev/ttyAMA0) sent "560A0D"
(serial) EVENT thread interrupted
(serial) received binary "540442205404E2"
(cul) probe response "T<04>B T<04><E2>"
(serial /dev/ttyAMA0) sent "560A0D"
(serial) EVENT thread interrupted
(serial) received binary "540442205404E2"
(cul) probe response "T<04>B T<04><E2>"
(serialtty) closed /dev/ttyAMA0 (detect cul)
(cul) are you there? no
(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"
(shell) output: >>><<<
(serial) EVENT thread interrupted
(shell) return code 1
(shell) 17248 exited
(shell) exec (capture output) "/bin/pidof"
(shell) arg "wmbusmeters"
(serial) EVENT thread interrupted
(shell) return code 0
(shell) 17249 exited
Notice! Other wmbusmeters (pid 17154) 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 1 Reply Last reply Reply Quote 0
                              • M
                                matze-dev @WolfgangFB last edited by

                                @wolfgangfb morgen müsste ich die komplette Doku fertig haben - dann kann man das komplette System von Scratch aufsetzen und hat dann alles beisammen. Ich stelle die Anleitung + Skripte dann hier ein.

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

                                  @matze-dev

                                  Super, ich hoffe, Du hast das dann auch mal mit einer echt blanken Raspberry Installation getestet.

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

                                    @wolfgangfb in der Tat, das wird parallel mit einer neuen Karte aufgesetzt und gleich mitdokumentiert 🙂

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

                                      @matze-dev Kamstrup/Multical 21 realisiert mit Rasperry Pi, iM871A und iobroker zum Auslesen des Wasserzählers
                                      Nun ist es soweit.
                                      Anbei die Doku

                                      Installationsbeschreibung-ioBroker-Rasp-PI+IMST871A.pdf

                                      hier sind noch die erforderlichen Skripten -sind in der Doku beschrieben, wie man diese verwendet und einbaut.

                                      extract_watermeters-values.js: das wird vom MQTT-Broker getriggert und liest die Werte aus, die im Datagramm stehen
                                      extract_watermeters-values.js

                                      calculate_average_new.js: das läuft einmal die Nacht und berechnet den Jahresgesamtverbrauch
                                      calculate_average_new.js

                                      hier sind noch 2 Hilfsscripten, wenn man die States neu anlegen oder löschen möchte - braucht man fürs erste nicht.
                                      zum Löschen aller states: delete_states.js

                                      zum Setzen aller states: create_states.js

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

                                        @matze-dev

                                        Hi

                                        Erstmal vielen Dank für die ausführliche Anleitung.
                                        Ich kann einen großen Erfolg melden: Ich kann meinen Wasserzähler auslesen!!!

                                        pi@raspberrypi:/var/log/wmbusmeters/meter_readings $ more MyTapWater_2021-07-21
{"media":"cold water","meter":"multical21","name":"MyTapWater","id":"57813696","total_m3":0.668,"target_m3":0.668,"max_flow_m3h":0,"f
low_temperature_c":127,"external_temperature_c":18,"current_status":"DRY","time_dry":"22-31 days","time_reversed":"","time_leaking":"
","time_bursting":"","timestamp":"2021-07-21T21:59:54Z","device":"im871a[00100776]","rssi_dbm":0}

                                        Was es jetzt genau war kann ich noch nicht sage, aber in dieser Anleitung waren ein paar Installationen mehr vorhanden als ich bisher gemacht habe. Ich glaube der Hauptpunkt ist, dass mein Zähler im C1 Mode sendet.
                                        Was noch nicht klappt ist der mqtt Adapter, der bleibt einfach bei gelb hängen. "Verbunden mit mqtt: falsch"

                                        Wo kann ich da ansetzen? (Zur Not schreibe ich mir aber selbst ein Skript, dass die täglichen meter_readings auswertet, das würde ich hinbekommen 🙂 )

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

                                          @wolfgangfb Hallo, schön zu hören. Mein MQTT ist auch gelb. Das ist OK. Wenn Du auf den gelben Punkt gehst, dann zeigt er Dir die Zustände an. Die ersten müssten grün sein. Wichtig ist, ob in den Objekten die Variablen angelegt sind und diese ab und zu grün werden, dann läuft alles. Der Broker wacht nur kurz auf, wenn Daten rein kommen, darum denke ich, dass das so Ok ist. Das mit den verschiedenen Versionen des Zählers ist in der Tat etwas tricky. Hast es aber rausgefunden! Viel Glück.

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

                                            @matze-dev

                                            Hi

                                            Das Problem ist, dass die Datenpunkte nicht angelegt werden.
                                            Wenn ich auf den gelben Punkt klicke sehe ich, dass die Verbindung mit Host Ok ist, Lebenszeichen da ist, aber Verbindung mit MQTT nicht OK ist.
                                            Die Frage ist jetzt, ob der mkosquitto richtig läuft oder der Adapter ein Problem hat, wo setze ich da mit der Fehlersuche an?

                                            Gruß und Dank

                                            Wolfgang

                                            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

                                            748
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            12
                                            151
                                            17581
                                            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