From 5c870f240c06fe498d0b3912347f9ba2c768221c Mon Sep 17 00:00:00 2001 From: Legolas-2025 Date: Wed, 1 Apr 2026 21:42:40 +0200 Subject: [PATCH] Add changelog entry for v6.2.4 bug fix Documented the fix for the auto display refresh glitch that showed previous hour's data at the top of the hour. Updated the changelog with details about the problem and solution. --- CHANGELOG.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 22ec8b8..93fcdf5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,20 @@ All notable changes to this project are documented here. +## v6.2.4 - Exact-boundary display refresh bug (2026-04-01): + +**Summary** + +Top of the hour auto display refresh glitch fix where display automatically refreshed but showed the PREVIOUS hour's data. + +### Problem: +- At the exact top of the hour (e.g., 20:00:00), the display automatically refreshed but showed the PREVIOUS hour's data (19:00). This happened because the "next-boundary" rounding logic in findCurrentPriceIndex() incorrectly excluded the current interval if the time was exactly on the boundary. + +### Solution: +- Simplified findCurrentPriceIndex() to use a robust "last entry <= now" comparison. This ensures the display transitions to the new hour instantaneously at XX:00:00. + +--- + ## v6.2.3 - State-based display refresh logic fix (2026-04-01): **Summary**