Adapter WM-Bus / Kampstrup Multical 21
-
@cbmod Hallo nochmal - Achtung, ich verwende nicht den WMBUS-Adapter des iobrokers, sondern realisiere das mit dem MQTT-Broker. Das Auslesen macht die Software wmbusmeters. Daher braucht man den Adapter im iobroker nicht.
Wenn das Auslesen mit der Software soweit läuft, können wir uns an die Konfig des iobrokers machen. Viel Glück. -
Hi @cbmod,
mit Interesse habe ich deinen Beitrag gelesen. Ich habe mir einen Sprengzähler von Zenner zugelegt. Minomess wM-Bus C1 Mode. Den Adapter findet iobroker ohne Probleme eigentlich (obwohl Win Treiber nicht installiert sind), dennoch bekomme ich scheinbar keinen Connect zum Zähler hin. Weiß jemand wie man das ganze Setup in Betrieb nimmt? Wann weiß ich, wann das Gerät über aktiv ist? Das wireless m-bus Studio nimmt nicht mal Kontakt zum Stick auf: failed: WMBUS_INVALID_HANDLE schmeißt mir das Studio aus.
Wie hast du bei dir herausgefunden, wann der Wasserzähler aktiv ist und wann eine Verbindung zum Stick geklappt hat? Ich schätze danach läuft auch die Werteabfrage bei iobroker. -
@mwolle so ich habe es auch zum Laufen bekommen unter Windows. Essentiell ist erst mal den Windowstreiber zu installieren für den iM871A-USB Stick. Ich habe diesen hier genommen: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
Danach kann man den korrekten COM Port auswählen und die korrekten Einstellungen übernehmen. (Also 57600 Baud, ich habe einen Zenner Minomess C1 Wasserzähler, somit C Type A auswählen). Danach hat er bei mit den Wasserzähler gefunden und in die Geräteliste eingetragen. Danach AES Schlüssel eingeben und danach gibt es die Werte.
Ich habe von Zenner noch eine Doku bekommen, wo genau die Parameter erklärt werden. (Insbesondere VIF 4-8 und VIF 5-8) -
@matze-dev
HalloIch habe genau die gleiche Hardware (Multical 21 und iM871A - USB) habe alles nach der Anleitung gemacht, nach etlichen Nachinstallationen lief auch der letzte Befehl
sudo systemctl start wmbusmetersAber das Verzeichnis
/var/log/wmbusmeters/meter_readings/Bleibt leer. Wo kann ich mit der Suche anfangen (bin eher Linux Anfänger).
Wie überprüfe ich, ob bisher sonst alles richtig installiert ist?Gruß Wolfgang
-
@wolfgangfb sagte in Adapter WM-Bus / Kampstrup Multical 21:
systemctl status wmbusmeters -
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 Sun 2021-06-27 22:47:02 CEST; 12h ago Docs: https://github.com/weetmuts/wmbusmeters man:wmbusmeters(1) Process: 12243 ExecStartPre=/bin/mkdir -p /var/log/wmbusmeters/meter_readings (code=exited, status=0/SUCCESS) Process: 12244 ExecStartPre=/bin/chown -R wmbusmeters:wmbusmeters /var/log/wmbusmeters (code=exited, status=0/SUCCESS) Process: 12245 ExecStartPre=/bin/mkdir -p /run/wmbusmeters (code=exited, status=0/SUCCESS) Process: 12246 ExecStartPre=/bin/chown -R wmbusmeters:wmbusmeters /run/wmbusmeters (code=exited, status=0/SUCCESS) Process: 12247 ExecStart=/usr/sbin/wmbusmetersd /run/wmbusmeters/wmbusmeters.pid (code=exited, status=0/SUCCESS) Main PID: 12248 (wmbusmetersd) Tasks: 3 (limit: 4915) CGroup: /system.slice/wmbusmeters.service └─12248 /usr/sbin/wmbusmetersd /run/wmbusmeters/wmbusmeters.pid Jun 27 22:47:02 raspberrypi4 wmbusmetersd[12248]: (config) "alarmexpectedactivity" "mon-sun(00-23)" Jun 27 22:47:02 raspberrypi4 wmbusmetersd[12247]: (wmbusmeters) started /run/wmbusmeters/wmbusmeters.pid Jun 27 22:47:02 raspberrypi4 wmbusmetersd[12248]: (config) "" "" Jun 27 22:47:02 raspberrypi4 wmbusmetersd[12248]: (config) loading meter file /etc/wmbusmeters.d/MyTapWater Jun 27 22:47:02 raspberrypi4 wmbusmetersd[12248]: (config) name=MyTapWater Jun 27 22:47:02 raspberrypi4 wmbusmetersd[12248]: (config) type=multical21 Jun 27 22:47:02 raspberrypi4 wmbusmetersd[12248]: (config) id=57813696 Jun 27 22:47:02 raspberrypi4 wmbusmetersd[12248]: (config) key=<notprinted> Jun 27 22:47:02 raspberrypi4 wmbusmetersd[12248]: (wmbusmeters) using log file /var/log/wmbusmeters/wmbusmeters.log Jun 27 22:47:02 raspberrypi4 systemd[1]: Started "wmbusmeters service". pi@raspberrypi4:/var/log/wmbusmeters/meter_readings $und (ich glaube kaum dass jemand mit den Daten meines Wasserzählers irgendwelchen Unfug anstellen kann)
pi@raspberrypi4:/var/log/wmbusmeters $ more wmbusmeters.log (wmbusmeters) logging started 2021-06-27 22:42:35 using 1.3.0-29-g3ee42c6 Wmbus devices found but no meters supplied. You must supply which link modes to listen to. Eg. auto:c1 (wmbusmeters) logging started 2021-06-27 22:42:37 using 1.3.0-29-g3ee42c6 Wmbus devices found but no meters supplied. You must supply which link modes to listen to. Eg. auto:c1 (wmbusmeters) logging started 2021-06-27 22:42:38 using 1.3.0-29-g3ee42c6 Wmbus devices found but no meters supplied. You must supply which link modes to listen to. Eg. auto:c1 (wmbusmeters) logging started 2021-06-27 22:42:39 using 1.3.0-29-g3ee42c6 Wmbus devices found but no meters supplied. You must supply which link modes to listen to. Eg. auto:c1 (wmbusmeters) logging started 2021-06-27 22:42:40 using 1.3.0-29-g3ee42c6 Wmbus devices found but no meters supplied. You must supply which link modes to listen to. Eg. auto:c1 (wmbusmeters) logging started 2021-06-27 22:47:02 using 1.3.0-29-g3ee42c6 (wmbusmeters) version: 1.3.0-29-g3ee42c6 (config) store meter files in: "/var/log/wmbusmeters/meter_readings" (config) using device: /dev/ttyUSB0:im871a (config) number of meters: 1 (lookup) with file "/dev/ttyUSB0" (serial) before config: /dev/ttyUSB0 speed(B115200) input(ICRNL|IXON) output(ONLCR|OPOST) control(CLOCAL|CREAD|CSIZE|HUP CL) local(ECHO|ECHOCTL|ECHOE|ECHOK|ECHOKE|ICANON|IEXTEN|ISIG) special_chars(3,28,127,21,4,1,17,19,26,18,15,23,22) modem( DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() m odem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (detect amb8465) (serial) received binary "" (serial /dev/ttyUSB0) sent "FF0A02008077" (serial) EVENT thread interrupted (serial /dev/ttyUSB0) sent "FF0A02008077" (serial) received binary "" (serial) received binary "" (serialtty) closed /dev/ttyUSB0 (detect amb8465) (serial) EVENT thread interrupted (amb8465) are you there? no. (serial) EVENT thread interrupted (serial) before config: /dev/ttyUSB0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() m odem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (detect im871a) (serial) received binary "" (serial /dev/ttyUSB0) sent "A5010F00" (serial) EVENT thread interrupted (serial) received binary "A58110083300130107220000B5A6" (im871a) checkIM871AFrame "A58110083300130107220000B5A6" (im871a) has_timestamp=0 has_rssi=0 has_crc16=1 (im871a) endpoint 1 (im871a) msgid 16 (im871a) got crc16 a6b5 expected a6b5 (im871a) received full frame (device info bytes) "3300130107220000" (im871a/im170a) info: im871a other firmware=13 hci=01 uid=00002207 (serial /dev/ttyUSB0) sent "A5010500" (serial) EVENT thread interrupted (serial) received binary "A5810617FF000200B32576071000010001FF07023200000000000039A4" (im871a) checkIM871AFrame "A5810617FF000200B32576071000010001FF07023200000000000039A4" (im871a) has_timestamp=0 has_rssi=0 has_crc16=1 (im871a) endpoint 1 (im871a) msgid 6 (im871a) got crc16 a439 expected a439 (im871a) received full frame (serialtty) closed /dev/ttyUSB0 (detect im871a) (serial) EVENT thread interrupted (device config bytes) "FF000200B32576071000010001FF070232000000000000" (im871a/im170a) config: other link_mode=s2 id=00100776 media=00 version=01 c_field=00 auto_rssi=00 (im871a/im170a) are you there? yes 00100776 im871a firmware: 13 (main) opening auto [2021-06-27_22:47:02] Started config im871a[00100776] on /dev/ttyUSB0 listening on none (im871a) on /dev/ttyUSB0 (serial) EVENT thread interrupted (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (im871a) get config (serial /dev/ttyUSB0) sent "A5010500" (serial) EVENT thread interrupted (serial) received binary "A5810617FF000200B32576071000010001FF07023200000000000039A4" (im871a) checkIM871AFrame "A5810617FF000200B32576071000010001FF07023200000000000039A4" (im871a) has_timestamp=0 has_rssi=0 has_crc16=1 (im871a) endpoint 1 (im871a) msgid 6 (im871a) got crc16 a439 expected a439 (im871a) received full frame (im871a) get config completed (im871a) got device id 00100776 (main) regular reset of im871a on /dev/ttyUSB0 will happen every 82800 seconds [2021-06-27_22:47:02] Warning! Desired link modes none cannot be set for device /dev/ttyUSB0:im871a[00100776] (wmbus) set timeout im871a to "3600" with expected activity "mon-sun(00-23)" (serial) registered regular callback HOT_PLUG_DETECTOR(0) every 2 seconds (wmbusmeters) waiting for telegrams (serial) waiting for stop [2021-06-27_22:47:04] (memory) rss 1921024 peak 1.83 MiB (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-27_23:47:02] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-27 23:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-27 23:47)" (shell) waiting for child 16832 to complete. (shell) /bin/sh: return code 127 (serial) EVENT thread interrupted [2021-06-27_23:47:02] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-27_23:47:02] (wmbus) resetting /dev/ttyUSB0 (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-27_23:47:05] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_00:47:02] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s expected mon-sun(00-23) now 2021-06-28 00:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s expected mon-sun(00-23) now 2021-06-28 00:47)" (shell) waiting for child 21517 to complete. (shell) /bin/sh: return code 127 (serial) EVENT thread interrupted [2021-06-28_00:47:02] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_00:47:02] (wmbus) resetting /dev/ttyUSB0 (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_00:47:05] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_01:47:02] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s expected mon-sun(00-23) now 2021-06-28 01:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s expected mon-sun(00-23) now 2021-06-28 01:47)" (shell) waiting for child 26093 to complete. (shell) /bin/sh: return code 127 (serial) EVENT thread interrupted [2021-06-28_01:47:02] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_01:47:02] (wmbus) resetting /dev/ttyUSB0 (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_01:47:05] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_02:47:02] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-28 02:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-28 02:47)" (shell) waiting for child 30676 to complete. (shell) /bin/sh: return code 127 [2021-06-28_02:47:02] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_02:47:05] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_03:47:02] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-28 03:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-28 03:47)" (shell) waiting for child 3173 to complete. (shell) /bin/sh: return code 127 (serial) EVENT thread interrupted [2021-06-28_03:47:02] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_03:47:02] (wmbus) resetting /dev/ttyUSB0 (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_03:47:05] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_04:47:02] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-28 04:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-28 04:47)" (shell) waiting for child 7739 to complete. (shell) /bin/sh: return code 127 (serial) EVENT thread interrupted [2021-06-28_04:47:02] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_04:47:02] (wmbus) resetting /dev/ttyUSB0 (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_04:47:05] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_05:47:02] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-28 05:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-28 05:47)" (shell) waiting for child 12304 to complete. (shell) /bin/sh: return code 127 [2021-06-28_05:47:02] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_05:47:02] (wmbus) resetting /dev/ttyUSB0 (serial) EVENT thread interrupted (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_05:47:05] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_06:47:03] [ALARM DeviceInactivity] 3601 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-28 06:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3601 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-28 06:47)" (shell) waiting for child 17017 to complete. (serial) EVENT thread interrupted (shell) /bin/sh: return code 127 [2021-06-28_06:47:03] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_06:47:03] (wmbus) resetting /dev/ttyUSB0 (serial) EVENT thread interrupted (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_06:47:06] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_07:47:03] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-28 07:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-28 07:47)" (shell) waiting for child 21569 to complete. (shell) /bin/sh: return code 127 (serial) EVENT thread interrupted [2021-06-28_07:47:03] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_07:47:03] (wmbus) resetting /dev/ttyUSB0 (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_07:47:08] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_08:47:03] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-28 08:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-28 08:47)" (shell) waiting for child 26137 to complete. (shell) /bin/sh: return code 127 (serial) EVENT thread interrupted [2021-06-28_08:47:03] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_08:47:03] (wmbus) resetting /dev/ttyUSB0 (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_08:47:06] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_09:47:03] [ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-28 09:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3600 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-28 09:47)" (shell) waiting for child 30713 to complete. (shell) /bin/sh: return code 127 (serial) EVENT thread interrupted [2021-06-28_09:47:03] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_09:47:03] (wmbus) resetting /dev/ttyUSB0 (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_09:47:06] (wmbus) successfully reset wmbus device (wmbus) updated_last received for im871a (/dev/ttyUSB0) [2021-06-28_10:47:04] [ALARM DeviceInactivity] 3601 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 3600s e xpected mon-sun(00-23) now 2021-06-28 10:47) (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=DeviceInactivity" (shell) env "ALARM_MESSAGE=[ALARM DeviceInactivity] 3601 seconds of inactivity resetting /dev/ttyUSB0 im871a (timeout 36 00s expected mon-sun(00-23) now 2021-06-28 10:47)" (shell) waiting for child 3194 to complete. (shell) /bin/sh: return code 127 [2021-06-28_10:47:04] (shell) /bin/sh exited with non-zero return code: 127 (serial) initiate reset (serialtty) closed /dev/ttyUSB0 (im871a) [2021-06-28_10:47:04] (wmbus) resetting /dev/ttyUSB0 (serial) EVENT thread interrupted (serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serial) after config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars() modem(DTR|RTS) (serialtty) opened /dev/ttyUSB0 fd 4 (im871a) (serial) reset completed [2021-06-28_10:47:07] (wmbus) successfully reset wmbus deviceEs scheint also, dass irgendwas empfangen wird, aber es wird nichts gespeichert. Nächste Frage: Wie bekomme ich das ganze jetzt noch in IO Broker (MQTT), gibt es hier eine dummysichere Anleitung?
Gruß Wolfgang
-
@wolfgangfb Hallo Wolfgang, ich kann es leider nicht so ganz vergleichen, bei mir läuft das nicht als Service und ich habe noch die Vorgängerversion des Treibers. Es sieht so aus, dass er die Telegramme nicht korrekt bekommt (macht reset).
Mein Logoutput sieht aber eher so aus:
(meter) MyTapWater: not for me: not my id
(wmbus) telegram ignored by all configured meters!
(serial) not starting timer thread since it is already running.
(serial) received binary "A5E2032E442D2C80xxxxxxxxxxxxxxxxxxxx"
(im871a) checkIM871AFrame "A5E2032E442D2C802780741B167A6xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
(im871a) has_timestamp=1 has_rssi=1 has_crc16=1
(im871a) endpoint 2
(im871a) msgid 3
(im871a) timestamp 00000000
(im871a) rssi 64
(im871a) got crc16 66ff expected 66ff
(im871a) received full frame
(wmbus) parseDLL @0 47 -
@matze-dev
HiKannst Du mir (als Linux Nicht Profi) genau verraten, was Du gemacht hast und welche Software Du installierst hast?
-
@wolfgangfb Hallo Wolfgang, gemaess Zeile 42 Deines Logs muessten Daten gekommen sein, später erscheinen die nicht mehr. Aktualisiert das Logfile um die Eintraege weiterhin?
(serial) received binary "A5E2032E442D2C80xxxxxxxxxxxxxxxxxxxx"
(im871a) checkIM871AFrame "A5E2032E442D2C802780741B167A6xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"Wenn ja, sieht es gut aus.
Das nächste waere, den MQTT (mosquitto_pub) zu installieren - ist der auch schon auf dem System?
Installationsanleitung liegt hierunter:
https://mosquitto.org/blog/2013/01/mosquitto-debian-repository/Viel Glueck.
-
@matze-dev
HalloDas ganze ist für mich als Nicht-Linuxianer etwas frustrierend.
Das fängt damit an, dass Du schreibst "bei mir läuft das nicht als Service". Was habe ich denn falsch gemacht, dass es scheinbar bei mir als Service läuft. Ich habe mich meiner Meinung nach genau an die Anleitung gehalten. Ich stoße aber immer wieder auf Punkte bei denen ich den Eindruck habe, dass erfahrene Linuxianer genau wissen, was da gemeint ist, ich aber nur raten kann und irgendwas eingebe und wahrscheinlich etwas falsches.
Ich konnte immer noch keinerlei Daten der Wasseruhr auf meinem Raspberry finden
Mosquitto habe ich vielleicht erfolgreich installiert.
pi@raspberrypi4:/etc/apt/sources.list.d $ sudo apt-get install mosquitto Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig mosquitto ist schon die neueste Version (2.0.11-0mosquitto1~stretch1).verstehe ich so, dass ich das vorhanden ist.
In der Anleitung bin ich an dieser Stelle gestolpert:
Then one of the following, depending on which version of debian you are using:An der Stelle frage ich mich, wie ich herausfinden kann, welche "version of debian" ich benutze. Erfahren User denken bestimmt "das ist doch ganz klar", mir ist das aber nicht klar.
Der aktuelle Status des wmbusmasters sieht wie folgt aus:
pi@raspberrypi4:/etc/apt/sources.list.d $ systemctl status wmbusmeters ● wmbusmeters.service - "wmbusmeters service" Loaded: loaded (/lib/systemd/system/wmbusmeters.service; disabled; vendor preset: enabled) Active: active (running) since Sun 2021-06-27 22:47:02 CEST; 1 weeks 3 days ago Docs: https://github.com/weetmuts/wmbusmeters man:wmbusmeters(1) Main PID: 12248 (wmbusmetersd) Tasks: 3 (limit: 4915) CGroup: /system.slice/wmbusmeters.service └─12248 /usr/sbin/wmbusmetersd /run/wmbusmeters/wmbusmeters.pid Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.Also irgendwas scheint da immer noch nicht zu stimmen. Nur wo setze ich jetzt an?
Frustrierte Grüße
Wolfgang
-
@wolfgangfb sagte in Adapter WM-Bus / Kampstrup Multical 21:
An der Stelle frage ich mich, wie ich herausfinden kann, welche "version of debian" ich benutze.
Das Paket mosquito kommt für Debian Stretch. Das ist aber eine Version die ihr Lebensende seit einem Jahr überschritten hat. Vielleicht falsche Quelle angelegt, vielleicht das Ableben verpasst... Jedenfalls sollte man Stretch beerdigen.
Die installierte Version sieht man u.a. mit
lsb_release -aFür aktuelle Releases kommt mosquito aber ohnehin aus den Standard-Repos:
echad@chet:~ $ apt policy mosquitto mosquitto: Installiert: (keine) Installationskandidat: 2.0.11-1 Versionstabelle: 2.0.11-1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages echad@chet:~ $Die ganze Anleitung zur Installation (aus dem Jahre des Herren 2013?) sollte also ohnehin nicht mehr erforderlich sein.
-
OK, ich habe also
pi@raspberrypi4:~ $ lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: busterwas wohl der Nachfolger von stretch ist.
pi@raspberrypi4:~ $ apt policy mosquitto mosquitto: Installiert: 2.0.11-0mosquitto1~stretch1 Installationskandidat: 2.0.11-0mosquitto1~stretch1 Versionstabelle: *** 2.0.11-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 100 /var/lib/dpkg/status 2.0.11-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 2.0.10-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 2.0.10-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 2.0.9-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 2.0.9-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 2.0.8-0mosquitto2~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 2.0.8-0mosquitto2~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 2.0.8-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 2.0.8-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.12-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.12-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.12-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.11-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.11-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.11-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.10-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.10-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.10-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.8-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.8-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.8-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.7-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.7-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.7-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.6-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.6-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.6-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.4-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.4-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.4-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.3-0mosquitto1~stretch1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.3-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.3-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.2-0mosquitto1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.2-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.2-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.1-0mosquitto1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.6.1-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.6.1-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.5.8-0mosquitto1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.5.8-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.5.7-1+deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages 1.5.6-0mosquitto1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.5.6-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.5.5-0mosquitto1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.5.5-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.5.4-0mosquitto2 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.5.4-0mosquitto2~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.5.4-0mosquitto1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.5.4-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.5.3-0mosquitto1 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.5.3-0mosquitto1~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.5-0mosquitto2 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.5-0mosquitto2~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages 1.4.15-0mosquitto4 500 500 https://repo.mosquitto.org/debian stretch/main armhf Packages 1.4.15-0mosquitto4~jessie1 500 500 https://repo.mosquitto.org/debian jessie/main armhf Packages N: Datei »mosquitto-stretch.list.2« in Verzeichnis »/etc/apt/sources.list.d/« wird ignoriert, da sie eine ungültige Dateinamen-Erweiterung hat. N: Datei »mosquitto-jessie.list.1« in Verzeichnis »/etc/apt/sources.list.d/« wird ignoriert, da sie eine ungültige Dateinamen-Erweiterung hat. N: Datei »mosquitto-stretch.list.1« in Verzeichnis »/etc/apt/sources.list.d/« wird ignoriert, da sie eine ungültige Dateinamen-Erweiterung hat. pIst das jetzt gut oder schlecht?
Bleibt aber immer noch die frage, warum ich absolut keine Daten von der Wasseruhr sehe (darum geht es mir ja im Endeffekt).
Gruß Wolfgang
-
@wolfgangfb
Die Quelle zu Stretch muss entfernt werden.Vermutlich so:
sudo rm /etc/apt/sources.list.d/mosquitto-stretch.list sudo apt update sudo apt install mosquitto=2.0.11-0mosquitto1~buster1 -
pi@raspberrypi4:/etc/apt/sources.list.d $ sudo apt install mosquitto=2.0.11-0mosquitto1~buster1 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Die folgenden zusätzlichen Pakete werden installiert: libcjson1 libmosquitto1 Die folgenden NEUEN Pakete werden installiert: libcjson1 libmosquitto1 Die folgenden Pakete werden durch eine ÄLTERE VERSION ERSETZT (Downgrade): mosquitto 0 aktualisiert, 2 neu installiert, 1 durch eine ältere Version ersetzt, 0 zu entfernen und 84 nicht aktualisiert. Es müssen 331 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 350 kB Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren? [J/n] J Holen:1 https://repo.mosquitto.org/debian buster/main armhf libmosquitto1 armhf 2.0.11-0mosquitto1~buster1 [81,0 kB] Holen:2 https://repo.mosquitto.org/debian buster/main armhf mosquitto armhf 2.0.11-0mosquitto1~buster1 [232 kB] Holen:3 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian buster/main armhf libcjson1 armhf 1.7.10-1.1+deb10u1 [18,6 kB] Es wurden 331 kB in 1 s geholt (271 kB/s). Vormals nicht ausgewähltes Paket libcjson1:armhf wird gewählt. (Lese Datenbank ... 107608 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../libcjson1_1.7.10-1.1+deb10u1_armhf.deb ... Entpacken von libcjson1:armhf (1.7.10-1.1+deb10u1) ... Vormals nicht ausgewähltes Paket libmosquitto1:armhf wird gewählt. Vorbereitung zum Entpacken von .../libmosquitto1_2.0.11-0mosquitto1~buster1_armhf.deb ... Entpacken von libmosquitto1:armhf (2.0.11-0mosquitto1~buster1) ... dpkg: Warnung: Version 2.0.11-0mosquitto1~stretch1 des Paketes mosquitto wird durch ältere Version 2.0.11-0mosquitto1~buster1 ersetzt Vorbereitung zum Entpacken von .../mosquitto_2.0.11-0mosquitto1~buster1_armhf.deb ... Entpacken von mosquitto (2.0.11-0mosquitto1~buster1) über (2.0.11-0mosquitto1~stretch1) ... libmosquitto1:armhf (2.0.11-0mosquitto1~buster1) wird eingerichtet ... libcjson1:armhf (1.7.10-1.1+deb10u1) wird eingerichtet ... mosquitto (2.0.11-0mosquitto1~buster1) wird eingerichtet ... Trigger für systemd (241-7~deb10u7+rpi1) werden verarbeitet ... Trigger für man-db (2.8.5-2) werden verarbeitet ... Trigger für libc-bin (2.28-10+rpi1) werden verarbeitet ... pi@raspberrypi4:/etc/apt/sources.list.d $pi@raspberrypi4:/etc/apt/sources.list.d $ apt policy mosquitto mosquitto: Installiert: 2.0.11-0mosquitto1~buster1 Installationskandidat: 2.0.11-0mosquitto1~buster1 Versionstabelle: *** 2.0.11-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 100 /var/lib/dpkg/status 2.0.10-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 2.0.9-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 2.0.8-0mosquitto2~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 2.0.8-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.12-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.11-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.10-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.8-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.7-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.6-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.4-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.3-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.2-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.6.1-0mosquitto1~buster1 500 500 https://repo.mosquitto.org/debian buster/main armhf Packages 1.5.7-1+deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@raspberrypi4:/etc/apt/sources.list.d $sieht zumindest mal "grüner" aus. Was kommt als nächstes?
-
@wolfgangfb
Mal neu gestartet?
Ich bin aber im Weiteren raus, von mosquito hab ich keine Ahnung.
Jedenfalls ist die Installation jetzt sauber. -
@wolfgangfb Hallo Wolfgang,
wenn jetzt mosquitto läuft, übergibt der Treiber mittels des konfigurierten Befehls:
in der Datei /etc/wmbusmeters.conf
...
shell=/usr/local/bin/mosquitto_pub -d -h localhost -t wmbusmeters/$METER_ID -m "$METER_JSON"
....
die Daten an den mosquitto.
Jetzt muss im iobroker der MQTT Broker/Client installiert werden.- die Webseite des iobroker öffnen (ist auf Port 8081).
- dann auf Adapter gehen
- MQTT Broker/Client auswählen und dann auf das +-Zeichen den Adapter hinzufügen.
- Adapter-Konfiguration (der muss jetzt als Server/Broker laufen):
Danach braucht es noch folgende Adapter:
History
JS Script Engine
BackITUp
Flot Charts
Visualisation
Die einfach auch so, wie oben beschrieben, als Adapter dazufügen. -
@matze-dev sagte in Adapter WM-Bus / Kampstrup Multical 21:
shell=/usr/local/bin/mosquitto_pub
Höchstwahrscheinlich der falsche Pfad. In /usr/local/bin sollte das nicht liegen
-
@thomas-braun
Bei mir ist der Wurm drinZuerst habe ich den MQTT Broker/Clinet installiert. Die Bilder sahen bei mir genauso aus wie bei matze-dev, aber der Adapter blieb auf gelb und es wurden keine Datenpunkte angelegt.
Ich habe den Raspberry neu gestartet (Thomas Braun: Mal neu gestartet?)
sudo rebootdanach (wie immer nach einem reboot) " Cannot find view "system" for search "host".
Gemäß Anleitung den letzten regulären Zustand aus den Backups wiederhergestellt.pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ iobroker start pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ iobroker status iobroker is running on this host. Objects type: file States type: file pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ iobroker status No connection to databases possible ... pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ iobroker stop pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ iobroker status iobroker is not running on this host. Objects type: file States type: file pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ iobroker start pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ iobroker status /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2674 res.forEach(aliveState => { ^ TypeError: Cannot read property 'forEach' of undefined at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2674:21) at processImmediate (internal/timers.js:463:21)Was habe ich jetzt schon wieder falsch gemacht?
-
Nach diversen Neustarts läuft der IO-Broker (zum Glück) wieder).
Was mich stutzig macht ist:pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ mosquitto 1626002431: mosquitto version 2.0.11 starting 1626002431: Using default config. 1626002431: Starting in local only mode. Connections will only be possible from clients running on this machine. 1626002431: Create a configuration file which defines a listener to allow remote access. 1626002431: For more details see https://mosquitto.org/documentation/authentication-methods/ 1626002431: Opening ipv4 listen socket on port 1883. 1626002431: Error: Address already in use 1626002431: Opening ipv6 listen socket on port 1883. 1626002431: Error: Address already in useDas klingt für mich als ob ein anderer Dienst auf dem gleichen Rechner auf Port 1883 etwas macht.
pi@raspberrypi4:/opt/iobroker/iobroker-data/backup-objects $ netstat -a | grep 1883 tcp 0 0 localhost:1883 0.0.0.0:* LISTEN tcp6 0 0 localhost:1883 [::]:* LISTENaußerdem sieht für mich
sudo systemctl start wmbusmeters more /var/log/wmbusmeters/wmbusmeters.log [2021-07-11_13:27:40] Started config im871a[00100776] on /dev/ttyUSB0 listening on none (im871a) on /dev/ttyUSB0 (serial) EVENT thread interrupted (im871a) get config (im871a) got device id 00000000 [2021-07-11_13:27:51] Not the expected dongle (dongle said 00000000, you said 00100776! (wmbus) deleted im871a No wmbus device detected, waiting for a device to be plugged in. (shell) exec (capture output) "/bin/pidof" (shell) arg "wmbusmetersd" (shell) output: >>>5672 <<< (serial) EVENT thread interrupted (shell) return code 0 (shell) 5728 exited (shell) exec (capture output) "/bin/pidof" (shell) arg "wmbusmeters" (shell) output: >>><<< (serial) EVENT thread interrupted (shell) return code 1 (shell) 5729 exited (serial) registered regular callback HOT_PLUG_DETECTOR(0) every 2 seconds (wmbusmeters) waiting for telegrams (serial) waiting for stop (serial) TIMER thread interrupted (serial) EVENT thread interrupted [2021-07-11_13:27:53] (memory) rss 2924544 peak 2.78 MiB (lookup) with file "/dev/ttyUSB0" (serial) EVENT thread interrupted (serial) EVENT thread interrupted (serial) EVENT thread interrupted [2021-07-11_13:28:37] Expected im871a on /dev/ttyUSB0 but found unknown instead, ignoring it! (verbose) ignoring device autonicht gut aus. (ich verstehe das so, dass der Dongle garnicht erkannt wird)
-
@wolfgangfb Hallo Wolfgang, in der Tat, da sieht nicht so gut aus. Was sagt das Logfile, in das die Werte geschrieben werden? "cat /var/log/wmbusmeters/wmbusmeters.log" - sind die Werte darin OK?
