iobroker-community-adapters / iobroker.wm-bus-community

WM-Bus Adapter for ioBroker

Deprecated: This adapter was replaced by https://github.com/lvogt/ioBroker.wireless-mbus

ioBroker.wm-bus

This adapter requires at least Node 4.4

Description

Adapter for Wireless M-Bus

Info

Supported USB Adapters:

• iM871A
• CUL

Initial Creation

This adapter was initialy created by @soef at https://github.com/soef/ioBroker.wm-bus but not maintained any more, so we moved it to iobroker-community so that bugs could be fixed. thanks @soef for his work.

Configuration

If used, an AES key to decrypt the message. Manufacture ID, type and version will be determined after the first received message

Installation

Execute the following command in the iobroker root directory (e.g. in /opt/iobroker)

npm install iobroker.wm-bus

Requirements

• an iM871A USB Stick
• or a CUL USB Stick
• a WM-Bus Device e.g. EasyMeter

Changelog

0.3.0 (2018-01-23)

• (Apollon77) Upgrade Serialport Library

iobroker.wm-bus-community's Issues

Add Support for Compact mode (js-Controller 2.0 Feature)

From @ldittmar81 on January 20, 2019 13:5

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

Copied from original issue: soef/ioBroker.wm-bus#24

Installation of wm-bus adapter not possible

I installed an IO broker from scratch (Node.js: v12.22.1 NPM: 6.14.12) and tried to install wm-bus adapter. Neiter "+" in the adapter tab nor
npm install iobroker.wm-bus
works.
`

npm ERR! code ELIFECYCLE

  | npm ERR! errno 1
  | npm ERR! [email protected] install: prebuild-install \|\| node-gyp rebuild
  | npm ERR! Exit status 1
  | npm ERR!
  | npm ERR! Failed at the [email protected] install script.
  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  |  
  | npm ERR! A complete log of this run can be found in:
  | npm ERR! /home/iobroker/.npm/_logs/2021-06-16T14_12_52_424Z-debug.log

Please fix`

Adapter WM-Bus / Kampstrup Multical 21

From @CBMOD on February 25, 2018 9:27

Hallo soef,
habe versucht den Wasserzaehler Kampstrup Multical 21 via wM-Bus zu connecten.
Der USB Stick iM871A-USB wird erkannt.
Jetzt wuerde ich weitere Infos benoetigen um das Problem zu loesen.
Habe meine Fragen im Forum unter "Adapter WM-Bus / Kampstrup Multical 21" erfasst.
http://forum.iobroker.net/viewtopic.php?f=20&t=12045

Copied from original issue: soef/ioBroker.wm-bus#16

Please check ioBroker.wm-bus-community with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

Think about to fix the issues found by adapter checker

From @ioBrokerChecker on February 3, 2019 16:8

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/soef/ioBroker.wm-bus

• [E019] Invalid repository URL: https://github.com/soef/iobroker.wm-bus. Expected: git+https://github.com/soef/ioBroker.wm-bus.git
• [E114] No adapter are allowed in the repo without admin3 support
• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.wm-bus"

ERR:["E019","E114","E201"]:ERR

Thanks,
your automatic adapter checker.

Copied from original issue: soef/ioBroker.wm-bus#25

after update node.js and js.controller wm-bus adapter don't start.

node.js -v v12.16.3
js-controller 3.1.4
host.SmartHomeCenter | 2020-05-10 09:28:01.788 | error | Caught by controller[0]: }
host.SmartHomeCenter | 2020-05-10 09:28:01.788 | error | Caught by controller[0]: ]
host.SmartHomeCenter | 2020-05-10 09:28:01.788 | error | Caught by controller[0]: '/opt/iobroker/node_modules/serialport/compiled/12.16.3/linux/arm/serialport.node'
host.SmartHomeCenter | 2020-05-10 09:28:01.787 | error | Caught by controller[0]: '/opt/iobroker/node_modules/serialport/build/default/serialport.node',
host.SmartHomeCenter | 2020-05-10 09:28:01.787 | error | Caught by controller[0]: '/opt/iobroker/node_modules/serialport/Release/serialport.node',
host.SmartHomeCenter | 2020-05-10 09:28:01.787 | error | Caught by controller[0]: '/opt/iobroker/node_modules/serialport/out/Release/serialport.node',
host.SmartHomeCenter | 2020-05-10 09:28:01.787 | error | Caught by controller[0]: '/opt/iobroker/node_modules/serialport/Debug/serialport.node',
host.SmartHomeCenter | 2020-05-10 09:28:01.787 | error | Caught by controller[0]: '/opt/iobroker/node_modules/serialport/out/Debug/serialport.node',
host.SmartHomeCenter | 2020-05-10 09:28:01.786 | error | Caught by controller[0]: '/opt/iobroker/node_modules/serialport/build/Release/serialport.node',
host.SmartHomeCenter | 2020-05-10 09:28:01.786 | error | Caught by controller[0]: '/opt/iobroker/node_modules/serialport/build/Debug/serialport.node',
host.SmartHomeCenter | 2020-05-10 09:28:01.786 | error | Caught by controller[0]: '/opt/iobroker/node_modules/serialport/build/serialport.node',
host.SmartHomeCenter | 2020-05-10 09:28:01.786 | error | Caught by controller[0]: tries: [
host.SmartHomeCenter | 2020-05-10 09:28:01.786 | error | Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1133:30) {
host.SmartHomeCenter | 2020-05-10 09:28:01.785 | error | Caught by controller[0]: at Object. (/opt/iobroker/node_modules/serialport/lib/bindings/auto-detect.js:16:22)
host.SmartHomeCenter | 2020-05-10 09:28:01.785 | error | Caught by controller[0]: at require (internal/modules/cjs/helpers.js:77:18)
host.SmartHomeCenter | 2020-05-10 09:28:01.785 | error | Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:1019:19)
host.SmartHomeCenter | 2020-05-10 09:28:01.785 | error | Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:877:14)
host.SmartHomeCenter | 2020-05-10 09:28:01.785 | error | Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:977:32)
host.SmartHomeCenter | 2020-05-10 09:28:01.784 | error | Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
host.SmartHomeCenter | 2020-05-10 09:28:01.784 | error | Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1133:30)
host.SmartHomeCenter | 2020-05-10 09:28:01.784 | error | Caught by controller[0]: at Object. (/opt/iobroker/node_modules/serialport/lib/bindings/linux.js:2:36)
host.SmartHomeCenter | 2020-05-10 09:28:01.784 | error | Caught by controller[0]: at bindings (/opt/iobroker/node_modules/serialport/node_modules/bindings/bindings.js:93:9)
host.SmartHomeCenter | 2020-05-10 09:28:01.783 | error | Caught by controller[0]: → /opt/iobroker/node_modules/serialport/compiled/12.16.3/linux/arm/serialport.node
host.SmartHomeCenter | 2020-05-10 09:28:01.783 | error | Caught by controller[0]: → /opt/iobroker/node_modules/serialport/build/default/serialport.node
host.SmartHomeCenter | 2020-05-10 09:28:01.783 | error | Caught by controller[0]: → /opt/iobroker/node_modules/serialport/Release/serialport.node
host.SmartHomeCenter | 2020-05-10 09:28:01.783 | error | Caught by controller[0]: → /opt/iobroker/node_modules/serialport/out/Release/serialport.node
host.SmartHomeCenter | 2020-05-10 09:28:01.782 | error | Caught by controller[0]: → /opt/iobroker/node_modules/serialport/Debug/serialport.node
host.SmartHomeCenter | 2020-05-10 09:28:01.782 | error | Caught by controller[0]: → /opt/iobroker/node_modules/serialport/out/Debug/serialport.node
host.SmartHomeCenter | 2020-05-10 09:28:01.782 | error | Caught by controller[0]: → /opt/iobroker/node_modules/serialport/build/Release/serialport.node
host.SmartHomeCenter | 2020-05-10 09:28:01.782 | error | Caught by controller[0]: → /opt/iobroker/node_modules/serialport/build/Debug/serialport.node
host.SmartHomeCenter | 2020-05-10 09:28:01.781 | error | Caught by controller[0]: → /opt/iobroker/node_modules/serialport/build/serialport.node
host.SmartHomeCenter | 2020-05-10 09:28:01.781 | error | Caught by controller[0]: Error: Could not locate the bindings file. Tried:
host.SmartHomeCenter | 2020-05-10 09:28:01.781 | error | Caught by controller[0]: ^
host.SmartHomeCenter | 2020-05-10 09:28:01.780 | error | Caught by controller[0]: throw err
host.SmartHomeCenter | 2020-05-10 09:28:01.780 | error | Caught by controller[0]: /opt/iobroker/node_modules/serialport/node_modules/bindings/bindings.js:96
host.SmartHomeCenter | 2020-05-10 09:28:01.353 | info | instance system.adapter.wm-bus.0 started with pid 1185

it seems that for node.js serialport version 8.x is necessary - current is 7.x

rtl_sdr

Please make support for rtlsdr

Please add NPM package to iobroker-community-adapters:developers team

verifying all repos and NPM ownership we noticed the NPM package of this repo is not part of our team.

please execute :

npm access grant read-write iobroker-community-adapters:developers iobroker.<adaptername>

or add the package by web :

https://www.npmjs.com/settings/iobroker-community-adapters/teams/team/developers/access

Compatibility check and testing for Node.js 14 and 16

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Make adapter ready for Admin v3

From @Apollon77 on January 3, 2018 14:14

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

Copied from original issue: soef/ioBroker.wm-bus#12

Auswertung bleibt beim Empfang von einem Zählertyp stehen?

From @chr-be on November 24, 2018 16:20

Hallo Soef,

bei zwei WM-Bus Geräten werden RAW-Daten richtig ausgewertet. Also grundsätzlich läuft der Adapter bei mir.
Aber eine Zähler-Typ, ähnlich wie hier:
soef/ioBroker.wm-bus#9 wird nicht ausgewertet bzw. stoppt den weiteren Empfang von den anderen Zählern.

wm-bus.0	2018-11-24 16:49:02.119	debug	Long header
wm-bus.0	2018-11-24 16:49:02.118	debug	7297004071210455081e006005d215873540ffc95cf3cb838a6e2f19af09d1151d69a1a20bb31c510f2054a5f88ec7e1643362dcd0b39cf35e70773e253615c4fdc7c24af367f7dffc969fda559ad58d6ace467016ae94dbdede63dee1adc8bfcc695a1
wm-bus.0	2018-11-24 16:49:02.113	debug	calc len 135, actual 122
wm-bus.0	2018-11-24 16:49:02.112	debug	lfield 118
wm-bus.0	2018-11-24 16:49:02.105	debug	raw: a5c203764621049700407155087297004071210455081e006005d215873540ffc95cf3cb838a6e2f19af09d1151d69a1a20bb31c510f2054a5f88ec7e1643362dcd0b39cf35e70773e253615c4fdc7c24af367f7dffc969fda559ad58d6ace4670
wm-bus.0	2018-11-24 16:48:45.815	debug	system.adapter.admin.0: logging false
wm-bus.0	2018-11-24 16:48:45.807	debug	redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1543074525802,"q":0,"from":"system.adapter.admin.0","lc":1543074525802}
wm-bus.0	2018-11-24 16:48:45.380	debug	raw: a58112260000ae0006003afda007000000000000000000000000a9000000000000009700000005000700579d
wm-bus.0	2018-11-24 16:48:45.354	debug	raw: a5811008330013012b1e0000df9d
wm-bus.0	2018-11-24 16:48:43.330	debug	raw: `a5810617ff000300b32578563412010001ff0702320001000201db8c4b

<
Nach dem Empfang bleibt der Adapter stehen. Zumindest kommen dann erstmal keine RAW-Daten von den anderen Zählern mehr. Nach dem Neustart des Adapter empfängt er gleich wieder RAW und wertet diese auch aus.

Es handelt sich hie rum einen Wämemengenzähler.
T1
ID 71400097
AES Key 4DF2F0365F95CFFC35F70352E5D2F633

Host ist 1.4.2
WM-Busadapter die Version 0.3.1.
USB-Stick ist iM871A

Viele Grüße
chr-be

`

Copied from original issue: soef/ioBroker.wm-bus#22

im871a no data

Hi,
I'm trying to get iobroker to include data from my im871a using wm-bus.
When I use https://github.com/weetmuts/wmbusmeters everything works fine - but I'm not sure how I setup iobroker.wm-bus to get similar data.
If I just set the ttyUSB0 and save - are the found devices supposed to pop-up in the config page - or do I need to add them my self?
I have tried to leave just the ttyUSB0, but no devices are added.

wmbusmeters have support for my iperl water meter - how do I add that to iobroker?

(wmbus) received telegram 20222542 C-field=44 M-field=4cae (SEN) A-field-version=68 A-field-dev-type=07 (Water meter) Ci-field=7a (EN 13757-3 Application Layer with short Transport Layer) CC-field=00 (slow_resp) ACC=67
(wmbus) frame "1844AE4C4225222068077A670000000413CFE20100023B0000"
(wmbus) payload "0413CFE20100023B0000"
(wmbus) 00: 18 length (24 bytes)
(wmbus) 01: 44 c-field (SND_NR)
(wmbus) 02: ae4c m-field (4cae=SEN)
(wmbus) 04: 42252220 a-field-addr (20222542)
(wmbus) 08: 68 a-field-version
(wmbus) 09: 07 a-field-type (Water meter)
(wmbus) 0a: 7a ci-field (EN 13757-3 Application Layer with short Transport Layer)
(wmbus) 0b: 67 acc
(wmbus) 0c: 00 status ()
(wmbus) 0d: 0000 configuration ()
(wmbus) 1844AE4C4225222068077A67000000
(meter) iperl: for me? 20222542
(meter) iperl: yes for me
(iperl) telegram for iperl 20222542
(iperl) log "telegram=|1844AE4C4225222068077A67000000|0413CFE20100023B0000|+300"
(dvparser) found new format "0413023B" with hash c944, remembering!
(iperl) 0f: 04 dif (32 Bit Integer/Binary Instantaneous value)
(iperl) 10: 13 vif (Volume l)
(iperl) 11: * CFE20100 total consumption (123.599000 m3)
(iperl) 15: 02 dif (16 Bit Integer/Binary Instantaneous value)
(iperl) 16: 3B vif (Volume flow l/h)
(iperl) 17: 0000
(iperl) 1844AE4C4225222068077A670000000413CFE20100023B0000
iperl 20222542 123.599 m3 2019-03-12 07:41.29

Hope someone can help!
Thanks

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

WM-bus liest keine Daten von CUL

From @Smarthome199 on November 11, 2018 8:40

Hallo,

ich versuche vergeblich über den CUL-Stick WM-Bus daten in ioBroker zu empfangen.
Es ist die Version 0.3.1 installiert. Das Suchen des COM Port funktiniert noch. Der Anschluss /dev/ttyACM0 busware.de wird gefunden. Die Instanz verbindet sich und die Ampel zeigt grün.
Das Log habe ich bereits auf debug gestellt.

Hier die Einträge.
wm-bus.0 | 2018-11-11 09:15:46.395 | debug | TMODE detected and tmode set to true
wm-bus.0 | 2018-11-11 09:15:46.319 | info | starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.wm-bus, node: v8.12.0
wm-bus.0 | 2018-11-11 09:15:46.170 | info | States connected to redis: 127.0.0.1:6379
wm-bus.0 | 2018-11-11 09:15:46.163 | debug | statesDB connected
wm-bus.0 | 2018-11-11 09:15:46.121 | debug | objectDB connected
host.All-In-One_RasPi | 2018-11-11 09:15:44.930 | info | instance system.adapter.wm-bus.0 started with pid 27395

Der TMODE wird anscheinend erkannt und gesetz. Mehr passiert aber nicht. Die instanz läuft schon 2 Tage ohne eine RAW-Meldung.

Mein ioBroker läuft auf einem RaspberryPi 3 mit dem All-In-One_RasPi image. Alle verfügbaren updates wurden eingespielt. Die Version ist jetzt ioBroker.js-controller 1.4.2, ioBroker.admin 3.5.10

Wenn ich die WM-Bus instanz beende, und mich mit Screen direkt auf die Konsole des CUL verbinde sehe ich jede Stunde ein Paket meines Wasserzählers (sensus iperl)
Der Stick funktioniert also, und empfängt auch daten.
Hier ein Datenpaket aus Screen. Die Daten sind verschlüsselt.
b1E44AE4C0560032068070BD87A770010054E96106EEB9268962BA75BF3F35B21262659FCA48023

Ich habe auch zum Testen den Adapter CUL/culfw installiert. Hier werden auch RAW daten empfangen.

Es scheint als ob die Daten empfangen werden, aber nicht ausgelesen werden.
Bitte um Hilfe.

Copied from original issue: soef/ioBroker.wm-bus#21

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.wm-bus-community

• [E019] Invalid repository URL: https://github.com/soef/iobroker.wm-bus. Expected: git+https://github.com/iobroker-community-adapters/ioBroker.wm-bus-community.git
• [E114] No adapter are allowed in the repo without admin3 support
• [E130] No news found in io-package.json
• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [E200] Not found on npm. Please publish
• [E301] Tests on Travis-ci.org are broken. Please fix.
• [E802] No topics found in the repository. Please go to "https://github.com/iobroker-community-adapters/ioBroker.wm-bus-community", press the settings button beside the about title and add some topics.
• [E604] No "## License" found in README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2015-2021 soef [email protected]" at the start of LICENSE

I have also found warnings that may be fixed if possible.

• [W113] Adapter should support compact mode
• [W400] Cannot find "wm-bus-community" in latest repository

Thanks,
your automatic adapter checker.

Add raw data field to manually parse data

From @systemofapwne on December 16, 2018 21:59

Hi,
I already wrote an issue on your "wm-bus" library. There, I asked for "Techem HKV data II" support, which seems to use a proprietary format. I suggested to either incorporate that meter or to make the raw data-stream usable in ioBroker.
I forked your project and realized exactly the later one: Every datagram received is now pushed forward to "wm-bus.0.raw", which allows to externally parse the received data (which for me is the quickest solution right now).
Feel free to implement my changes to your project.

Cheers,
Klaus

Copied from original issue: soef/ioBroker.wm-bus#23