Code: Select all
pi@raspberrypi:/etc/wmbusmeters.d $ ls
wodomierz
a zawartość wygląda tak
no nie tworzy mi żadnego pliku nie mam już pomysłów może.... bo oryginalnie ścieżka wygląda tak /var/lib/wmbusmeters/meter_readings zamiast /var/log/w......
Code: Select all
pi@raspberrypi:/var/lib/wmbusmeters/meter_readings $ ls
pi@raspberrypi:/var/lib/wmbusmeters/meter_readings $
Code: Select all
pi@raspberrypi:/var/log $ ls
alternatives.log auth.log btmp debug faillog kern.log messages runit syslog wtmp
apt bootstrap.log daemon.log dpkg.log journal lastlog private supervisor user.log
pi@raspberrypi:/var/log $
Code: Select all
pi@raspberrypi:~/wmbusmeters $ make test
Building 1.7.0-69-g6fdc6d2
ERROR expected "ALL_ACCESS UNKNOWN_ACCESS_BITS(0x80) ACCESSOR_RED" but got "ALL_ ACCESS UNKNOWN_ACCESS_BITS(0x0) ACCESSOR_RED"
ERROR expected "NO_ACCESS ALL_ACCESS UNKNOWN_ACCESSOR_TYPE(0x5)" but got "NO_ACC ESS ALL_ACCESS UNKNOWN_ACCESSOR_TYPE(0x7ebb42b8)"
ERROR expected "DRY BAD_RULE_ERROR_FLAGS(from=0x12 mask=0xf)" but got "DRY BAD_R ULE_ERROR_FLAGS(from=0x0 mask=0x12)"
OK: test internals
OK: Test C1 meters
OK json: Test T1 meters
OK fields: Test T1 meters
OK json: Test S1 meters
OK fields: Test S1 meters
OK json: Test electricity meters with radio converter plugins
OK fields: Test electricity meters with radio converter plugins
OK: Test mbus
OK: Test ANYID
OK: Test list-envs and list-fields
OK: Test list-envs and list-fields
OK json: Test non-compliant apator162 meters
OK fields: Test non-compliant apator162 meters
OK json: Test Izars meters
OK: Test listen to all izars
OK: Test aes encrypted telegrams
OK: Test that telegram really is encrypted
OK: Test that failed decryption warning only prints once.
OK: Test shell invocation
OK: Test shell in config file
OK: Test that normal meterfiles are written
OK: Test that meterfiles with name-id are written
OK: Test that meterfiles with id are written
OK: Test that meterfiles with timestamps are written
OK: Test that meterfiles with timestamps are written
OK: Test normal config files with C1 meters
OK: Test logfile
OK: Test single meter conf file matches any id
OK: Test listen and print any meter heard in logfile
OK: Test listen and print any meter heard on stdout
OK: Test detection of drivers for all telegrams
OK: Test listen to wildcard * id
OK: Test listen to wildcard suffix 8856* id
OK: Test listen to two comma separted ids
OK: Test listen to three comma separted ids
OK: Test listen with negated ids
OK: Test listen with wrong driver and wildcard
OK: Test conversions of units
OK: Test selected fields
OK: Test oneshot
OK: Test wrong keys
OK: Test config4 with added conversions
OK: Test additional json from cmdline
OK: Test additional shell envs from cmdline
OK: Test additional json from wmbusmeters.conf and from meter file
OK: Test rtlwmbus starting background script to produce telegrams
OK: Reading binary telegram from stdin
OK: Reading binary telegram from file
OK: Reading rtlwmbus formatted telegrams from stdin
OK: Reading rtlwmbus formatted telegrams from file
OK: Reading rtl433 formatted telegrams from stdin
OK: Reading rtl433 formatted telegrams from file
OK: Test ok serial rawtty telegram on stdin
OK: Test bad serial rawtty telegram with interspersed noise, on stdin
OK: Test duplicates are ignored
OK: Test duplicates are left alone
OK: Test match on dll id
OK: Test match on tpl id
OK fields: Test unix timestamp in fields
OK: Test log timestamps
OK: Test meter driver extra settings
OK: Test hex on commandline
OK: Test hex on commandline with meter
OK: Test invalid hex on commandline
OK: Test hex on stdin
OK: Test auto removal of dll crcs in simulated telegrams
OK: Test broken telegrams
OK: Test rtlwmbus with crc errors
Testing drivers
OK json: driver_amiplus.cc
OK fields: driver_amiplus.cc
OK json: driver_apator08.cc
OK fields: driver_apator08.cc
OK json: driver_aventieshca.cc
OK fields: driver_aventieshca.cc
2c2
< {"media":"water","meter":"aventieswm","name":"Vatten","id":"61070072","total_m 3":466.472,"consumption_at_set_date_1_m3":465.96,"consumption_at_set_date_2_m3": 458.88,"consumption_at_set_date_3_m3":449.65,"consumption_at_set_date_4_m3":442. 35,"consumption_at_set_date_5_m3":431.07,"consumption_at_set_date_6_m3":423.98," consumption_at_set_date_7_m3":415.23,"consumption_at_set_date_8_m3":409.03,"cons umption_at_set_date_9_m3":400.79,"consumption_at_set_date_10_m3":393.2,"consumpt ion_at_set_date_11_m3":388.63,"consumption_at_set_date_12_m3":379.26,"consumptio n_at_set_date_13_m3":371.26,"consumption_at_set_date_14_m3":357.84,"error_flags" :"MEASUREMENT HF UNKNOWN_ERROR_FLAGS(0x1100)","timestamp":"1111-11-11T11:11:11Z" }
---
> {"media":"water","meter":"aventieswm","name":"Vatten","id":"61070072","total_m 3":466.472,"consumption_at_set_date_1_m3":465.96,"consumption_at_set_date_2_m3": 458.88,"consumption_at_set_date_3_m3":449.65,"consumption_at_set_date_4_m3":442. 35,"consumption_at_set_date_5_m3":431.07,"consumption_at_set_date_6_m3":423.98," consumption_at_set_date_7_m3":415.23,"consumption_at_set_date_8_m3":409.03,"cons umption_at_set_date_9_m3":400.79,"consumption_at_set_date_10_m3":393.2,"consumpt ion_at_set_date_11_m3":388.63,"consumption_at_set_date_12_m3":379.26,"consumptio n_at_set_date_13_m3":371.26,"consumption_at_set_date_14_m3":357.84,"error_flags" :"MEASUREMENT HF UNKNOWN_ERROR_FLAGS(0x0)","timestamp":"1111-11-11T11:11:11Z"}
2c2
< Vatten;61070072;466.472000;MEASUREMENT HF UNKNOWN_ERROR_FLAGS(0x1100);1111-11- 11 11:11.11
---
> Vatten;61070072;466.472000;MEASUREMENT HF UNKNOWN_ERROR_FLAGS(0x0);1111-11-11 11:11.11
ERROR: driver_aventieswm.cc
OK: Test analyze encrypted (no-key) ctr full telegram
OK: Test analyze encrypted (no-key) ctr compact telegram
OK: Test analyze encrypted (with-key) ctr full telegram
OK: Test analyze encrypted (no-key) ctr compact telegram
OK: Test analyze CBC IV (no-key)
Slower tests...
OK: reading all stdin before closing down
OK: Test config with oneshot
OK: Test config with exitafter
OK: Test config override with oneshot
OK: Test config override with exitafter
RUNNING Test alarms ...
STDERR---------------------------------
[ALARM DeviceInactivity] 4 seconds of inactivity resetting simulations/simulatio n_alarm.txt simulation (timeout 4s expected mon-sun(00-23) now 2022-05-08 10:12)
(wmbus) successfully reset wmbus device
STDOUT---------------------------------
TMP/OUTPUT-----------------------------
METER =={"media":"cold water","meter":"multical21","name":"Water","id":"76348799 ","total_m3":6.408,"target_m3":6.408,"max_flow_m3h":0,"flow_temperature_c":127," external_temperature_c":19,"current_status":"DRY","time_dry":"22-31 days","time_ reversed":"","time_leaking":"","time_bursting":"","timestamp":"2022-05-08T08:12: 04Z"}==
METER =={"media":"cold water","meter":"multical21","name":"Water","id":"76348799 ","total_m3":6.408,"target_m3":6.408,"max_flow_m3h":0,"flow_temperature_c":127," external_temperature_c":19,"current_status":"DRY","time_dry":"22-31 days","time_ reversed":"","time_leaking":"","time_bursting":"","timestamp":"2022-05-08T08:12: 10Z"}==
TMP/ALARM------------------------------
ALARM_SHELL DeviceInactivity [ALARM DeviceInactivity] 4 seconds of inactivity re setting simulations/simulation_alarm.txt simulation (timeout 4s expected mon-sun (00-23) now 2022-05-08 10:12)
---------------------------------------
OK: Test alarms
Some tests failed!
make: *** [Makefile:267: test] Error 1
Code: Select all
pi@raspberrypi:~ $ supervisorctl status wmbusmeters/
wmbusmeters/: ERROR (no such process)
może to coś pomoże
Edit
coś poprzestawiałem i działa
