Diehl IZAR RC 868 i W R4

[scroatamus]

I receive this telegram info when i run
wmbusmeters --nodeviceexit auto:c1
Started auto rtlwmbus[00000001] listening on c1
No meters configured. Printing id:s of all telegrams heard!
Received telegram from: a132257d
manufacturer: (SAP) Sappel (0x4c30)
type: Water meter (0x07)
ver: 0x00
device: rtlwmbus[00000001]
rssi: 24 dBm
driver: izar

If I try reading to screen i get,
wmbusmeters auto:c1 MyTapWater auto a132257d 00112233445566778899AABBCCDDEEFF
Started auto rtlwmbus[00000001] listening on c1
(izar) Decoding PRIOS data failed. Ignoring telegram.
MyTapWater a132257d 000000 0 m3 0 m3 0-00-00 0 y no_alarm no_alarm 0 s 0 2021-03-10 16:56.21
(izar) Decoding PRIOS data failed. Ignoring telegram.
MyTapWater a132257d 000000 0 m3 0 m3 0-00-00 0 y no_alarm no_alarm 0 s 0 2021-03-10 16:56.46

Is my key wrong, or is my meter unsupported.?

says no meters configured though I have a definition
/etc/wmbusmeters.d/SWWMeter

name=SouthWestWater
id=a132257d
key=00112233445566778899AABBCCDDEEFF

packets from rtl-wmbus (oddly I only see T1)
T1;1;1;2021-03-06 15:05:59.000;21;20;A132257D;0x1944304c7d2532a1b201a2111d001314c2f17ad726f0ea24f41d

[weetmuts]

Try the latest version of wmbusmeters from github.
Then check if the serial id is better. Then run with NOKEY.

wmbusmeters auto:c1 MyTapWater auto 12345678 NOKEY

[scroatamus]

thanks NOKEY works.
think the serial id is right, though I cant relate that to anything on meter.
How do I put NOKEY in a meter file & why isn't mine picked up?

wmbusmeters auto:c1 MyTapWater auto a132257d NOKEY
Started auto rtlwmbus[00000001] listening on c1
MyTapWater a132257d C20LU 063613 35.262 m3 33.623 m3 2021-02-28 14.5 y no_alarm no_alarm 8 s 2020 2021-03-10 17:40.18
MyTapWater a132257d C20LU 063613 35.262 m3 33.623 m3 2021-02-28 14.5 y no_alarm no_alarm 8 s 2020 2021-03-10 17:40.26

[weetmuts]

Use --format=json and you should see fields that show the serial nrs that are printed on your meter.
Use: key=
to set an empty key (ie NOKEY) in the meter file.

[pswiatki]

Look for prefix and serial_number fields in JSON. They match the physical numbers on the meter. See #271

[scroatamus]

still don't see a match. but as meter is 6 months old & reading about right, I'm confident its mine.
"prefix":"C20LU","serial_number":"063613"
Meter s/n 04511048 this is writen on the clipon. cant see the meter underneath. wonder what the QR is? ( its just all the numbers on label)

[scroatamus]

I'm now struggling to get the config files to be read. so I can move on to run a daemon & publish MQTT to node red.
I have /etc/wmbusmeters.conf
loglevel=normal
device=auto:c1
logtelegrams=false
format=json
meterfiles=/var/log/wmbusmeters/meter_readings
meterfilesaction=overwrite
logfile=/var/log/wmbusmeters/wmbusmeters.log
shell=/usr/bin/mosquitto_pub -h 192.168.1.119 -t wmbusmeters/$METER_ID -m "$MET$
AND
/etc/wmbusmeters.d/MyTapWater
name=MyTapWater
id=a132257d
key=

When I run command line
wmbusmeters auto
Started auto rtlwmbus[00000001] listening on none
No meters configured. Printing id:s of all telegrams heard!
Received telegram from: a132257d
...etc

does not pickup at least the meter config.
permissions issue? running as sudo makes no difference.
I will look again this afternoon, to see if I am doing something stupid.
I am a linux novice.

[scroatamus]

Still no further on sadly.
Permissions...
I think this is the Realtek RTL28
ls -l /dev/bus/usb/001/006
crw-rw---- 1 root plugdev 189, 5 Mar 12 09:34 /dev/bus/usb/001/006

I've added myself to wmbusmeters group
groups
pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi wmbusmeters

when I run this something is still not right.
sudo wmbusmeters --verbose --useconfig=/ --meterfiles=/
Warning: Unable to locate configuration directory, default config not loaded.
Warning: Unable to locate configuration directory, default config not loaded.

a verbose log
sudo wmbusmeters --logtelegrams --debug --verbose --format=json rtlwmbus MyTapWater izar:t1 a132257d NOKEY
(wmbusmeters) version: 1.2.0-10-g948064a
(config) using device: rtlwmbus
(config) number of meters: 1
(shell) exec (capture output) "/bin/sh"
(shell) arg "-c"
(shell) arg "rtl_sdr < /dev/null"
(shell) output: >>>rtl_sdr, an I/Q recorder for RTL2832 based DVB-T receivers

Usage: -f frequency_to_tune_to [Hz]
[-s samplerate (default: 2048000 Hz)]
[-d device_index (default: 0)]
[-g gain (default: 0 for auto)]
[-p ppm_error (default: 0)]
[-b output_block_size (default: 16 * 16384)]
[-n number of samples to read (default: 0, infinite)]
[-S force sync output (default: async)]
filename (a '-' dumps samples to stdout)

<<<
(serial) EVENT thread interrupted
(shell) return code 1
(shell) 13295 exited
(main) rtl_srd found in path
(shell) exec (capture output) "/bin/sh"
(shell) arg "-c"
(shell) arg "rtl_wmbus < /dev/null"
(shell) output: >>><<<
(shell) return code 0
(shell) 13297 exited
(main) rtl_wmbus found in path
(serial) EVENT thread interrupted
(main) rtlsdr device 00000001 not currently used.
(main) found specified device (rtlwmbus) that matches detected device (:rtlwmbus[00000001]:0/0)
(main) opening rtlwmbus
Started config rtlwmbus[00000001] listening on none
(rtlwmbus) using command: /usr/bin/rtl_sdr -d 0 -f 868.625M -s 1.6e6 - 2>/dev/null | /usr/bin/rtl_wmbus -s
(rtlwmbus) opening 00000001
(bgshell) exec background "/bin/sh"
(bgshell) arg "-c"
(bgshell) arg "/usr/bin/rtl_sdr -d 0 -f 868.625M -s 1.6e6 - 2>/dev/null | /usr/bin/rtl_wmbus -s"
(serial) EVENT thread interrupted
(serialcmd) opened /bin/sh pid 13303 fd 5 (rtlwmbus)
(main) regular reset of rtlwmbus will happen every 82800 seconds
(wmbus) no alarm (expected activity) for rtlwmbus
(serial) registered regular callback HOT_PLUG_DETECTOR(0) every 2 seconds
(serial) waiting for stop
(serial) received ascii "T1;1;1;2021-03-12 09:21:03.000;20;17;A132257D;0x1944304c7d2532a1b201a2211d001314708da02a44848049df1a<0A>"
(rtlwmbus) checkRTLWMBusFrame "T1;1;1;2021-03-12 09:21:03.000;20;17;A132257D;0x1944304c7d2532a1b201a2211d001314708da02a44848049df1a<0A>"
(rtlwmbus) received full frame
(meter) no meter handled checking 1 templates.
(diehl) Pre-processing: setting device type to water meter for SAP PRIOS
(wmbus) parseDLL @0 26
(wmbus) parseELL @10 16
(wmbus) parseAFL @10 16
(wmbus) parseTPL @10 16
(meter) MyTapWater: for me? a132257d
(meter) MyTapWater: yes for me
(meter) created "MyTapWater" "izar" "a132257d" not-encrypted
(meter) used meter template MyTapWater a132257d izar to match a132257d
(meter) started meter 1 (MyTapWater a132257d izar)
(diehl) Pre-processing: setting device type to water meter for SAP PRIOS
(wmbus) parseDLL @0 26
(wmbus) parseELL @10 16
(wmbus) parseAFL @10 16
(wmbus) parseTPL @10 16
(meter) MyTapWater: for me? a132257d
(meter) MyTapWater: yes for me
(meter) MyTapWater izar handling telegram from a132257d
(meter) MyTapWater a132257d "1944304C7D2532A1B201A2211D001314708DA02A44848049DF1A"
(diehl) Pre-processing: setting device type to water meter for SAP PRIOS
(wmbus) parseDLL @0 26
(telegram) DLL L=19 C=44 (from meter SND_NR) M=4c30 (SAP) A=a132257d VER=00 TYPE=07 (Water meter) (driver izar) DEV=rtlwmbus[00000001] RSSI=20
(wmbus) parseELL @10 16
(wmbus) parseAFL @10 16
(wmbus) parseTPL @10 16
(telegram) TPL CI=a2
telegram=|1944304C7D2532A1B201A2|211D001314708DA02A44848049DF1A|+20
(izar) Decoded PRIOS data: 4BA78A000057830000BC22
(izar) 00: 19 length (25 bytes)
(izar) 01: 44 dll-c (from meter SND_NR)
(izar) 02: 304c dll-mfct (SAP)
(izar) 04: 7d2532a1 dll-id (a132257d)
(izar) 08: 00 dll-version
(izar) 09: 07 dll-type (Water meter)
(izar) 0a: a2 tpl-ci-field (Mfct specific)
{"media":"water","meter":"izar","name":"MyTapWater","id":"a132257d","prefix":"C20LU","serial_number":"063613","total_m3":35.495,"last_month_total_m3":33.623,"last_month_measure_date":"2021-02-28","remaining_battery_life_y":14.5,"current_alarms":"no_alarm","previous_alarms":"no_alarm","transmit_period_s":8,"manufacture_year":"2020","timestamp":"2021-03-12T09:21:03Z","device":"rtlwmbus[00000001]","rssi_dbm":20}

[pswiatki]

The log indicates you are getting some telegrams, does it not?

[scroatamus]

oh yes I get telegrams & decoded readings. If I run on the command line in test mode.
I cant run using configs, or as a daemon.
wmbusmeters --verbose --useconfig=/ --meterfiles=/
Could not open log file.

[scroatamus]

Why do I get this error?
wmbusmeters --verbose --useconfig=/ --meterfiles=/
Could not open log file.

[weetmuts]

How have you installed wmbusmeters?

You /etc/wmbusmeters.conf contains the setting:
logfile=/var/log/wmbusmeters/wmbusmeters.log
And the directory /var/log/wmbusmeters does not exist or is not writeable.

[scroatamus]

git clone https://github.com/weetmuts/wmbusmeters
cd wmbusmeters/
sudo make install

yes config has
logfile=/var/log/wmbusmeters/wmbusmeters.log

ls -l /var/log/wmbusmeters
total 8
drwxr-xr-x 2 wmbusmeters wmbusmeters 4096 Mar 10 19:17 meter_readings
-rw-r--r-- 1 wmbusmeters wmbusmeters 2103 Mar 12 09:30 wmbusmeters.log

[scroatamus]

that is the first time I have seen a log file & meter reading file. so maybe I am getting close.
but i run & get error
wmbusmeters --verbose --debug --useconfig=/ --meterfiles=/
Could not open log file.

[weetmuts]

The "sudo make install" should have added your user to the wmbusmeters group.
Run "groups" does it say wmbusmeters?
If not, add your user to the wmbusmeters group, like this:
sudo usermod -a -G wmbusmeters yourusername

[weetmuts]

You might have to logout and login again to have the group setup properly.