Open slemke76 opened 6 months ago
i never used mbus so i can't comment much.
the mbus code: https://github.com/volkszaehler/vzlogger/blob/master/src/protocols/MeterOMS.cpp
has lots of debug output, so if you set loglevel to 15 and maybe also mbus_debug
in the meter config you should get some output. (you did not include a log, so i assume you did not get any in your attempts do far?)
it seems there's a conversion of mbus-specific indentifiers to OBIS,
so you probably will have to add whatever your meter is sending there:
https://github.com/volkszaehler/vzlogger/blob/master/src/protocols/MeterOMS.cpp#L349
Be aware that our deb packages are unfortunately currently not build with mbus support.
Hello,
so i assume you did not get any in your attempts do far?
Yes, I didn´t get anything so far. I will take a closer look the next days - actually it is unclear to me, if the code is generally compatible with my meter. E.g. I do not need a key for communication.
Be aware that our deb packages are unfortunately currently not build with mbus support.
Thanks for the hint - I compiled vzlogger on my own, "oms" is listed as supported protocol type.
Sebastian
Hallo,
I have an M-Bus Water Mereting installed on my site (https://process.honeywell.com/us/en/products/utilities/water/digital-metering/mbus/falcon-mj-pulse-mbus).
I guess the "OBIS Value Group A = 8: Water" is actually not implemented? Or is this wrong?
I already payed around a bit - with the libmbus tools I get the water consumtion corretly:
`root@raspberrypi:/var/log/vzlogger# mbus-serial-request-data -d -b 2400 /dev/ttyAMA3 1 init_slaves: debug: sending init frame #1 [2024-05-09 21:30:06Z] SEND (005): 10 40 FD 3D 16 [2024-05-09 21:30:06Z] RECV (001): E5 init_slaves: debug: sending init frame #2 [2024-05-09 21:30:06Z] SEND (005): 10 40 FD 3D 16 [2024-05-09 21:30:06Z] SEND (005): 10 5B 01 5C 16 [2024-05-09 21:30:07Z] RECV (087): [...] mbus_frame_print: Dumping M-Bus frame [type 4, 87 bytes]: [...] <?xml version="1.0" encoding="ISO-8859-1"?>