Robert Raszuk

Thank you for looking at this issue. Below is the output requested: robert@nuc1eo:~/wmbus/wmbusmeters$ robert@nuc1eo:~/wmbus/wmbusmeters$ sudo wmbusmeters --debug auto:t1 (wmbusmeters) version: 1.5.0-3-g02e8404 (config) number of meters: 0 (main) device /dev/ttyUSB0 not...

I am testing this is residential building where there is about 100 of meters present which do transmit on t1. Those are known as BMeters meters. Yes those should all...

That was really helpful !!!! Huge thx ... now I am getting first telegram - at least from one device - heat meters. Water meters radios are still dead :(...

Hello Fredrik, Fantastic ! I recompiled it just adding the detection part. It works !!!! I am not worried about GJ vs kWh as heat meter can be configured to...

Yes they are supposed to send between 7:00 am and 18:00 local time. I was trying earlier during the day - nothing was received. Another interesting observation ... after wmbusmeters...

Actually I mean only for not decoded ones. See the situation today if I have no meter defined it is logging all telegrams and decoding the header. That is cool...

The telegrams in question come from a different building so I can not make a picture of it. The reason I am asking is that they have very good radios...

I am logging it already :) ***@***.***:/etc$ more wmbusmeters.conf loglevel=debug #loglevel=normal #device=cul:868.95M:t1 device=rtlwmbus:868.95M:t1 #device=auto:t1 #device=/dev/ttyUSB0:38400 logtelegrams=true format=json meterfiles=/var/log/wmbusmeters/meter_readings #meterfilesaction=overwrite meterfilesaction=append logfile=/var/log/wmbusmeters/wmbusmeters.log ***@***.***:/etc$ Here is a pointer to recent logfile with...

Anyone ? I tested this on a new ISP ... Identical issue. 

Annoying bug :( Perhaps the script launch params should self reload/refresh after execution is complete.