Help with wmbusmeters add-on needed

Third party integrations
1

Wmbusmeters add-on stopped working about a week ago after update to 1.11.0-2. The changelog says that HA implements the new format, but fails to specify what the changes in 1.11.0-2 actually are. I also looked at the wmbusmeters docs as suggested, but can not find any error from my side.
Attempt to start gives me simply “Invalid dict for option ‘conf’ in Wmbusmeters (W-MBus to MQTT) (cada3e3b_wmbusmeters).” error.
My conf part in HA is an exact copy of docs suggested conf part!
Maybe someone can specify what actually needs to be done to get this in HA to work.
As usual, help from third-party software developers is very lacking, so maybe here is someone who has been able to get it to function.
My new configuration file I try to use is the following. (This results “Failed to save add-on configuration, not a valid value.” error)

data_path: /etc/wmbusmeters.conf
enable_mqtt_discovery: true
conf:
  loglevel: normal
  device: auto:t1
  donotprobe: /dev/ttyAMA0
  logtelegrams: false
  format: json
  logfile: /dev/stdout
  shell: /wmbusmeters/mosquitto_pub.sh "wmbusmeters/$METER_NAME" "$METER_JSON"
meters:
  - name: MyTapWater
    id: 
    key: 
    driver: multical21
mqtt:
  host: 
  port: 1883
  user: 
  password:

thanks

2

I had the same issue. Solved it like this:

conf:

loglevel: normal
device: auto:t1
donotprobe: /dev/ttyAMA0
logtelegrams: false
format: json
logfile: /dev/stdout
shell: /wmbusmeters/mosquitto_pub.sh "wmbusmeters/$METER_NAME" "$METER_JSON"

and in the meters section I put my meters like this:

- name: HKV_EG_Flur
  driver: fhkvdataiii
  id: "30120822"
- name: HKV_DG_BUERO
  driver: fhkvdataiii
  id: "30120826"

Saved config in configuration tab and then started the addon and everything worked fine again…

3

Maybe you can help me with integrating these “fhkvdataiii” thingies into HA.
I have successfully installed the wmbusmeters and getting the data into MQTT,
but I’m lost at the part on HA, where I have to add the sensor.
I only found this example:"

mqtt:
  sensor:
    - state_topic: "wmbusmeters/MainWater"
      json_attributes_topic: "wmbusmeters/MainWater"
      unit_of_measurement: m³
      value_template: "{{ value_json.total_m3 }}"
      name: Water usage
      icon: "mdi:gauge"
      state_class: total_increasing
      device_class: water

Which obviously is for a water meter but not for a heating element.

4

Hello,

It’s the same :slight_smile: just change the device_class and the unit_of_measurement with something that is usable to you:
image

That gives me:

image
image967×599 39.8 KB

the state_topic is what you have configured in wmbusmeter:

image
image1309×733 57.2 KB

I hope that helps

5

Hello

I need help because I’m not very handy with computers and I’m stuck and I can’t move forward on my own.

I have win10 (64bit) installed where I run Hassio 13.2 in virtualbox. Wmbusmeters are causing too many challenges for me now, can someone tell me what I can do to get the water usage to show up.

nimetön
nimetön1063×700 215 KB

6

1
1732×436 27.9 KB

7

21

8

when u use homeassistant u dont need to configure addon within yaml.
addon web UI has all the fields needed to do that. Keep in mind that u probably also need your meter security key to make it work - depends from model. Only sensor u need to create manually in yaml is current month water - it is basically difference between total water and target water.
when u want latest version of addon, I suggest to install “edge” version.

1 Like
9

TNX i try, ihave key and id on my meter… I use edge version