Wmbus Binding & Diehl Hydrus 2.0

Add-ons Bindings
1

hello community,

is the WM bus binding still maintained?

I have the problem that when installing the binding (V.3.2.0) with OPENHAB (V3.3.0 under Windows).
inserted CUL is recognized as a WM bus bridge ONLINE.

During a subsequent thing search, my encrypted Hydrus water meter is recognized and installed as “WMBus device: water meter #xxxxxxxx (68DME1187)”. Without an AES key, the device is initially offline, which is certainly normal.

When I enter the AES key into the bridge and the device, the WMBus device appears as UNKNOWN.

In principle, the CUL and AES key are fine, since I can read the device with a Raspberry Pi and “wmbusmeters”.
However, I do not want to run a Raspberry for a counter. The solution would be more elegant
via OPENHAB WMBus binding.

Anyone can help or have tips?

2

Hey Dieter,
Can you attach logs with thing initialization? AFAIR unknown status is shown when thing initialization do not go well.

Best,
Łukasz

3

Hallo Łukasz,

Only Discover, no other Log in openhab.log

2023-03-20 12:29:49.278 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘wmbus:encrypted_meter:3b00d17519:A511920372757607’ to inbox.

Dieter

4

Bridge&Device
Bridge&Device691×83 16.5 KB

Device ohne Key#2
Device ohne Key#2697×808 66.3 KB

Device mit Key
Device mit Key667×703 49.7 KB

5

This are Entrys of Event.log

2023-03-20 13:10:51.906 [INFO ] [openhab.event.InboxAddedEvent ] - Discovery Result with UID ‘wmbus:encrypted_meter:3b00d17519:A511920372757607’ has been added.

2023-03-20 13:43:03.756 [INFO ] [openhab.event.InboxRemovedEvent ] - Discovery Result with UID ‘wmbus:encrypted_meter:3b00d17519:A511920372757607’ has been removed.

2023-03-20 13:43:03.761 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘wmbus:encrypted_meter:3b00d17519:A511920372757607’ changed from UNINITIALIZED to INITIALIZING

2023-03-20 13:43:03.765 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘wmbus:encrypted_meter:3b00d17519:A511920372757607’ changed from INITIALIZING to UNKNOWN

2023-03-20 13:43:03.769 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘wmbus:encrypted_meter:3b00d17519:A511920372757607’ changed from UNKNOWN to OFFLINE (CONFIGURATION_PENDING): Please provide encryption key to read device communication.

2023-03-20 13:43:31.573 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘wmbus:encrypted_meter:3b00d17519:A511920372757607’ changed from OFFLINE (CONFIGURATION_PENDING): Please provide encryption key to read device communication. to UNKNOWN

6

I just had a look on binding code and I think it could be due to fact that OH 3.4 core prohibits bindings from setting certain states on things. Are you on OH 3.4 or 3.3, and if you are not on 3.3 - can you quickly test it?

Cheers,
Łukasz

7

Hello,
thank you very much for the message. I use openhab V3.3.0 with Binding V3.2.0

I enter the keys in the following form:
Stick: “75720392:ABCDABCDABCDABCDABCDABCDABCDABCD” and
device: “ABCDABCDABCDABCDABCDABCDABCDABCD” each without quotation marks.
Is that correct? However, I have tried other variants without success.

Dieter

8

Hello,
thank you very much for the message. I use openhab V3.3.0

I enter the keys in the following form:
Stick: “75720392:ABCDABCDABCDABCDABCDABCDABCDABCD” and
device: “ABCDABCDABCDABCDABCDABCDABCDABCD” each without quotation marks.
Is that correct? However, I have tried other variants without success.

Greetings
Dieter

9

If you are entering encryption key at the device level I think you can skip prefix. They id:key,id2:key2 syntax is there for keys entered at bridge.