Added the watertech meter. George Hopkins improved the fhkvdataiii driver to infer the current year and the rtlwmbus driver to propagate the timestamp from rtlwmbus input into the final json timestamp. Thanks George! Rob Peters fixed a missing log output for ell_type. Thanks Rob! Added the GWF water meter. Zleba improved the qwater driver! Thanks Zleba! The option --logfile=syslog now works. ATTENTION! The hydrus driver has been rewritten from scratch! current_date is now meter_datetime Several fields were printed with value 0 even if the telegram did not contain the actual zero, such fields are no longer printed. Also the third text field has changed from max_flow_m3h to total_at_date_m3. Use --selectfields=... if you are affected. ATTENTION! The microclima driver has been refactored. The field device_date_time has been renamed to meter_datetime. Also two fields related to tariffs do not occur in the actual telegrams so these fields have been removed. The fields output has therefore been drastically changed. Use --selectfields= to reset your setup. Historical data is now decoded and added to the json. ATTENTION! The qwater driver has been refactored. The field device_date_time has been renamed to meter_datetime also the due 17 date fields have been renamed. The error_code field has disappeared since it was broken anyway and replaced with status. ATTENTION! The sharky774 driver had a bug that triggered when the meter used Joules instead of kWh. Also the calculated temperature difference had to be removed. You can re-add the temperature difference by using --calculate_temperature_difference_c=flow_temperature_c-return_temperature_c Since a field disappeared the default fields were disrupted and a shorter list of fields have now been picked for the default fields. Please use --selectedfields=... to recreate your previous fields. Also the field operating_time_h now prints the proper operating time and the new field operating_time_in_error_h prints the time when in error. ATTENTION! A bug in the hydrocalm3 driver was found. When total_cooling_kwh and other similar values were used as text fields (not a json fields) they were replaced with dates instead. This was due to a bug in the new code handling Quantity::PointInTime. Version 1.11.0 2022-12-29 Version 1.11.0-RC2 2022-12-29 Improve release process. Version 1.11.0-RC1 2022-12-29 Chpego and SzczepanLeon improved the HA-addon. Thanks! Ranma added support for the pollucomf 55 driver. Thanks Ranma! Jacek27 added another Munia temp/hygrometer version. Thanks Jacek27! Version 1.10.2 2022-12-05 Stefan Rado improved the mqtt discovery for HA. Thanks Stefan! Bibo improved the snap build process. Thanks Bibo! Version 1.10.1 2022-12-05 Fix bug that prevented a direct tty link: /dev/ttyUSB0:device:t1 to work. Version 1.10.0 2022-12-05 ╭─────────────────────────────────────────────────────────────────╮ │ │ │ Important change! The old style │ │ of writing drivers is now gone! BUT BUT BUT │ │ the final set of drivers to be converted were │ │ the multical 302/303/403/602/603/803 meters that │ │ were merged into a single kamheat driver. It was not │ │ possible to keep all of them backwards compatible! │ │ │ │ Note that the default fields for these meters are changed! │ │ Please use --selectfields to resolve this. │ │ │ │ I.e. It is a very good idea to check your multical heat │ │ meter values when you upgrade to wmbusmeters 1.10 ! │ │ │ ╰─────────────────────────────────────────────────────────────────╯ Important change! The feature --addconversions=GJ has been removed!!! But there is a replacement! It was used to add conversions to all energy values into gj, eg you have total_kwh and add total_gj. The addconversion feature was too broad and the conversion happened too late in the processing code. You can now achieve the same thing but you have to specify each field you want to convert using the calculation feature. E.g. --calculate_total_gj=total_kwh ATTENTION! The multical 302/303/403/602/603/803 heat meter drivers have been merged into a single kamheat driver. Not all values are backwards compatible! I.e. 302 is very changed, less so for the others. The default fields have changed! ATTENTION! The gransystems driver has been refactored to the new driver format. The field currrent_at_phase_1_a has been renamed to current_at_phase_1_a. The info strings in the "status" field now have underscores instead of spaces within a single string. ATTENTION! The rfmamb driver has been refactored to the new driver format. A bug was found and fixed where min and max relative humidity over 1h and 24h were wrong. The field device_date_time has been renamed to device_datetime. ATTENTION! The hydrocalm3 driver has been refactored to the new driver format. The field device_date_time has been renamed to device_datetime. ATTENTION! The fhkvdataiv driver has been refactored to the new driver format. The field consumption_at_set_date_17 was wrong and has been renamed to field consumption_at_set_date_8. ATTENTION! Bug in historical data for sensostar driver. Only the most recent month was correct. ATTENTION! The topaseskr driver has been refactored to the new driver format. The field "battery_life_days_remaining_remaining" has been changed to "battery_life_y". ATTENTION! When values are missing in the fields output, they were previously reported as "nan" but they are now reported as "null". ATTENTION! The unismart driver has been refactored to the new driver format. Several fields were unknown before and are still unknown and their content have slightly changed: status and version. The field "other_counter" is replaced with just "other" and its content changed. The field "suppler_info" is replaced with "supplier_info". The field "device_date_time" is replaced with "device_timestamp" and now contains seconds and a timezone. ATTENTION! A bug was fixed where the on_time_h and operating_time_h (and related error times) were wrong. ATTENTION! The lansensm driver now prints an extra field with the minutes since the last test was made. The json is improved. ATTENTION! The em24 driver has been refactored to the new driver format and some errors in the fields were discovered! The reactive consumption and production values were negative. This was in error, and due to a missing scale factor for the kvarh unit, they will now be positive. ATTENTION! The q400 driver has been refactored to the new driver format and some errors in the fields were discovered! Since the new driver format cannot generate these wrong json fields, the new q400 driver is not backwards compatible, except for the total_m3 field which is the same. Same fields and same content: total_m3, consumption_at_set_date_m3" Same field different content: meter_datetime now reports a full date time "2019-12-20 13:04" before it reported only the date "2019-12-20". New field new content: set_date is now set_datetime and reports "2019-12-01 00:00" instead of "2019-12-00" For the Axioma version of the q400: Broken fields: forward_flow_m3h, backward_flow_m3h, set_forward_flow_m3h, set_backward_flow_m3h replaced with: total_forward_m3, total_backward_m3, forward_at_set_date_m3, backward_at_set_date_m3 Same fields and same content: flow_temperature_c, flow_m3h --------------------------------------------------------------------------------------------- Karsten Festag added Engelmann FAW Radio transmitter and Engelmann Sensostar U extended with tests for wmbus and mbus. Thanks Karsten! Jannick Fahlbusch, Stefan Rado, Jan jnxxx, Ovettel, Artur Ptaszek, Sergey Melnik, Jan Suchal, Patrick Huesmann improved the HA-addon! Thanks! Steven Cooreman improved the Itron driver. Thanks Steven! Patrick Huesmann improved the qwater driver. Thanks Patrick! Florian Zschetzsche added support for the qheat 55 driver. Thanks Florian! Lasse Bang Mikkelsen added support for flowiq2200 and HA-addon fixes and kem-import fixes. Thanks Lasse! Bibo added support for the abbb23 driver and improved the docker builds and the lansensm driver! Thanks Bibo! Thisandre added support for the mkradio4a and vario511 meters. Thanks Andre! Added the bfw 240 radio heat cost allocator. Kajetan Krykwiński added support for the Apator E-ITN heat cost allocator. Thanks Kajetan! Improved wmbusmeters to gracefully handle bad telegrams with multiple difvif entries matching the same field. This used to trigger an assert, now the first matching field is used. Rename option --device=xyz to --overridedevice=xyz and add better error message if it is used without --useconfig=xyz. --device still works but will eventually be removed. OPTIONAL fields were only printed in the json, if they appeared in the telegram, even if the field had received a value before. Now a field will be printed in the json whenever there is a value stored in the meter object. I.e. an OPTIONAL field that has never received a value will not be printed. A NON-OPTIONAL field that has never received a value will be printed with the value null. Version 1.9.0 2022-09-04 ATTENTION! The multical21 and flowiq drivers have been refactored to the new driver style. Since the multical21 driver was the first driver ever written, it had some idiosynchrasies. The json should be entirely backwards compatible but when format=fields is used, the status field no longer has the days, eg "DRY(22-31 days)" is now just "DRY" use the json or selectfields=time_dry to get how long it has been dry. Added check for existance of difvif varlen length byte before reading it. Found by fuzzing. Thecem added support for the Multical 303 heat meter. Thanks thescem! Improve minomess driver to handle telegrams from wired m-bus module. Added Enercal F2 heat meter. Paulo Rossi added support for the AMB3665-M wmbus dongle for N-mode 169 MHz telegrams. Thanks Paulo! Version 1.8.0 2022-06-25 ATTENTION! Counter suffix _int is changed to _counter. New fields are added to lansendw, lansenpu, qsmoke drivers. Eventually the old fields will go away in drivers. ATTENTION! When a field is not optional in the driver description, but alas, no data has arrived in the telegram, then the json now contains a null for the value! Previousy 0 was used, which was misleading. ATTENTION! The default location of the meter_readings directory has changed from /var/log/wmbusmeters/meter_readings to /var/lib/wmbusmeters/meter_readings This only affects new installations. Existing conf files will use the old location as specified int the conf file. Added apator172 water meter. Added qualcosonic heating/cooling meter. Added ei6500 smoke detector. Added kampress pressure sensor. Added hydroclima HCA. Add detection of bad CUL firmware. Using :mbus as suffix to the meter driver now works to poll a meter of mbus instead of listening to wmbus telegrams. wmbusmeters --pollinterval=1h --format=json MAIN=/dev/ttyUSB0:mbus:2400 MyTemp piigth:MAIN:mbus 12301234 NOKEY Added --pollinterval=