Water Meter Reading/Integration with Itron EverBlu Cyble Enhanced

Third party integrations
145

EverBlu Meters v3.1.0 - What's New

v3.1.0 is out! Here are the changes that matter for day-to-day use.

The Big One: No More Frequency Scanning on First Boot

The CC1101 radio bandwidth has been widened from 58 kHz to 270 kHz, giving the chip ±67 kHz of automatic carrier-offset correction. For most installs this means the device locks onto your meter at the default 433.82 MHz without any manual scan. The startup Deep Scan is now disabled by default - you probably won't need it.

What Changed

Frequency / Radio

  • Startup auto-scan is now opt-in (auto_scan: true or #define AUTO_SCAN_ENABLED 1). Most users won't need it.

  • New Auto-Scan on Failure option (auto_scan_on_failure: true): runs a narrow re-tune automatically if the device hits MAX_RETRIES. Disabled by default (blocks ~1–2 min while scanning).

  • Deep Scan is smarter: two-phase sweep + zoom, plus a post-lock quality check that won't overwrite a good calibration with a worse one.

  • New rx_attenuation option (0 / 6 / 12 / 18 dB) for devices mounted very close to the meter - fixes front-end overload. Related: the firmware now logs a clear NEAR-FIELD SATURATION DETECTED warning instead of a generic error when RSSI is too strong.

Sensors & MQTT

  • tuned_frequency and frequency_estimate sensors now appear in MQTT Home Assistant discovery (they were ESPHome-only before).

  • New Reset Frequency Offset MQTT button in the standalone build.

  • Serial log lines now include a [HH:MM:SS] UTC timestamp.

Data Quality

  • Reading plausibility guard: rejects a reading if its implied monthly usage is 100× larger than historical normal - catches corrupted decodes before they pollute your history.

  • Monthly usage history no longer includes the oldest month (no prior baseline for delta), so the numbers are now correct.

  • LQI percentage was wrong - the CRC bit was included in the value (inflating it by 128) and the percentage mapping was inverted. Both are fixed; LQI now reads correctly in both builds.

ESPHome

  • Config validation catches mistakes early: invalid reading_schedule, mismatched GDO0/GDO2 pins, and ESP32 non-Arduino framework all now fail esphome config with a clear message instead of a cryptic compile error.

  • reading_schedule is now case-insensitive (monday-friday works).

Breaking Changes

If you're upgrading, update these YAML / MQTT references:

| Old | New |

|---|---|

| frequency_scan_button / wide_frequency_scan_button | deep_scan_button |

| MQTT topic freq_scan | deep_scan |

| fast_scan_button / fast_scan | Removed |

auto_scan now defaults to false - set it to true if you want the old startup-scan behaviour.

Upgrading From Before v3.0.0?

Also review the v3.0.0 breaking change: gdo2_pin / GDO2 must be wired and declared (or explicitly opted out), and the v2.3.0 strict meter-code format (YY-SSSSSSS).

Full details: CHANGELOG.md | RELEASE_NOTES_v3.1.0.md