Fredrik Öhrström

The N-modes (n1a-n1f modes) are supported by the Amber 3665-M (amb3665) and with a big antenna. The encoding is very different from the other encodings, and so far no-one has...

So wmbusmeters can both send and receive n1a-n1f telegrams if you have the amb3665. (The other modes T1,S1,C1 do not work for 169MHz, but they do work for 433MHz.)

The telegrams are unfortunately encrypted. You can check by pasting them here: https://wmbusmeters.org

Can you switch to the edge of the ha-addon?

From the docker file: `FROM asymworks/multiarch-alpine:${TARGETARCH}${TARGETVARIANT}-latest-stable as scratch` should not -latest-stable be the version of multiarch-alpine that works with the new rtl-sdr?

The latest edge docker should have been built with asymworks multiarch alpine latest, today appros 5 hours ago. https://github.com/wmbusmeters/wmbusmeters-ha-addon/actions/runs/7639570647 The first change was this, supposedly to get the latest rtl-sdr.......

Should work fine with mbus as well. The device must be specified as this: device=MAIN=/dev/ttyUSB1:mbus:2400 Then each meter must have a reference to the bus (ie MAIN or whatever you...

Strange, I am looking at the ./wmbusmeters-ha-addon/mqtt_discovery/qheat.json file. I am not an expert, but it looks ok. Do you have some extra setting in the wmbusmeters.conf or HA-addon. Such a...

I have thought about adding --addheaders to include the lower level headers in the json. Something like this: { "media":"bus/system component", "meter":"water", "name":"", "id":"20221031", "actuality_duration_s":20, "total_m3":0.062, "target_m3":4294967.295, "target_date":"2128-03-31", "status":"BATTERY_LOW POWER_LOW",...

Thanks for your insight in this meter! I had to develop the new dynamically loadable drivers infrastructure before this could be fixed in the proper way. The driver can now...