Repository navigation
NOTTY v0.4.2
Fix device timezone changes after live testing showed that the APK's Windows-name
payload corrupts the backend's IANA field and shifts DND clocks. Changes now require
an explicit valid iana_time_zone, validate the chosen server catalog ID, and check
both reported encodings. Existing change automations must add the new field.
Optional preserve_dnd_local_times keeps the original local interval, switch and LED
with one additional write. Partial failures are reported without replaying requests.
A live Amsterdam/London roundtrip restored all original settings and cleaning plans.
Persist pending firmware tasks before confirmation so Home Assistant reloads/restarts
and uncertain transport failures do not resend installation requests. Track the exact
task, reject unrelated failures and stale pre-retry failure states, and require
installed-version readback for completion. Tracking remains polling-based: the APK's
native Android JPush channel is not a verified HA-compatible stream. Hardware update
validation still awaits an available firmware offer.
Correct weight source precedence, kg/lb handling and profile-edit unit validation.
Fresh daily values take precedence over discovery summaries; missing/invalid readings
stay unknown. Daily cloud weight sensors retain stable IDs and use kilograms for HA
statistics. They identify their source and explicitly report unknown measurement time
and freshness. No per-visit weigh-in history or correction of NOTTY's upstream cat
attribution is claimed.
Add an offline schedule-observation validator which distinguishes DST gaps, repeated
clocks and UTC date boundaries. Live cleaning and leveling were physically confirmed
by the owner. See docs/remaining-validation.md for completed and pending acceptance.
Emptying remains blocked in validation tools; no statistics history is deleted.
Update through HACS and restart Home Assistant.