NOTTY v0.4.2

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.

NOTTY v0.4.1

NOTTY v0.4.1

Fix litter-box schedule editing: live plans report plan_type_id 2 and omit
quantity. The previous type-1 assumption rejected those plans. Keep unknown
plan types/quantities blocked while sending the app's quantity-1 edit payload.

Fix the child-lock request to send only the APK's integer physical
user_device_id and integer switch fields. Legacy target aliases, extra fields
and loosely coerced switch values are rejected. A live lock transition and
restoration matched fresh readback after two seconds.

Validation scripts now wait for bounded GET readback after a single write and
again after restoring a setting. Add DND switch-only and scoped association roundtrips, a read-only
firmware lifecycle monitor and a private-evidence coverage audit for all
in-scope issues. Empty-litter commands remain prohibited in validation tools.

Live DND, screen-language, association and all three cleaning-mode changes were
restored. Temporary schedule CRUD/toggle validation restored every original plan; raw
DND clocks/LED stayed unchanged. Actual scheduled firing/DST, fresh login-code
exchange, a future firmware offer and independently observed cat weigh-ins still
need their own acceptance evidence. Feeders and water dispensers remain deferred.

Update through HACS and restart Home Assistant. Existing entity IDs are retained.

NOTTY v0.4.0

NOTTY v0.4.0

Existing pets now have Home Assistant controls for name, sex, neutered state and
birthday. Actions support breed edits, pet-to-litter-box associations, text memo
listing/detail/create/edit, account notification preferences and explicitly
confirmed irreversible device-statistics deletion. Profile saves preserve fresh
weight/unit, image metadata and every existing device binding. Shared pets cannot
be edited; HA name overrides and entity identities are retained.

Litter-box mode selection supports Auto, Scheduled and Soft stool, with fresh
identity/current-state validation and an enabled-plan prerequisite for Scheduled.
Both reminder reset buttons use the APK's action 3 and preserve the configured
cycle. Trash-bag interval changes and all four screen-language values are exposed.
Firmware update entities support explicit confirmation of a fresh eligible offer,
full notes and Boolean pending-target tracking. No measured percentage or
restart-persistent firmware progress is claimed.

Adds English/Dutch names, action selectors and icons. Fixes minimum-version
binary-sensor imports and pet device linking; CI now exercises Home Assistant
2026.3.0 as well as the locked development version. The timezone probe also runs
without Home Assistant installed. Feeders and water dispensers remain excluded.

The integration is experimental. New write contracts are traced from the APK
and tested with synthetic responses. Read-only live checks verified breed,
owner-profile and notification-category schemas. New pet/memo/notification/mode
writes, same-cycle resets, trash-bag interval changes, firmware installation and
statistics deletion still need owner validation; no such operations were run
for this release. Memo dates retain the NOTTY wall clock without inferred timezone.

After updating through HACS, restart Home Assistant. Existing entity unique IDs
and integration credentials are retained. Review action field descriptions before
using new writes in automations; statistics deletion requires
confirm_irreversible: true and cannot be undone.

NOTTY v0.3.0

First GitHub release for installation and versioned updates through HACS.

Added

• Fixed-clock cleaning schedule listing, creation, editing, enable/disable and deletion.
• Read-only firmware update information, including installed/offered versions and release notes.
• A Cloud name text entity that preserves Home Assistant name overrides and entity IDs.
• Device timezone diagnostics, catalog inspection and an explicit timezone configuration action with before/after scheduling readback.
• Verified reminder controls, automatic cleaning delay selection, and broader API/Home Assistant regression coverage.

Changed

• Email verification codes are the supported login method; expired sessions require reauthentication. Stored prototype passwords and consumed codes are removed during migration.
• Review existing command automations: the APK-backed litter-box codes are now clean=1, empty=2, level=3. The former clean=0 mapping and unsupported sterilize action were removed. Numeric commands and stale sterilize entities need review.
• Corrected DND clock conversion and strengthened validation of settings, device targeting and sensor types.

Installation and updates

Add https://github.com/Repsay/notty to HACS custom repositories as an Integration, download this release and restart Home Assistant. Existing HACS users can update through Home Assistant's Updates view once HACS refreshes repository information. If installed from the default branch, select this numbered release in HACS once to move to release tracking. Manual installations must first be managed by HACS to receive HACS updates.

Requires Home Assistant 2026.3 or later. This remains an experimental, unofficial cloud integration. Read-only production probes confirmed device discovery, Auto mode, three cleaning plans, firmware 0.9.8 with no offered update, cloud alias readback and the timezone catalog. Motor effects, new schedule writes, cloud rename persistence and timezone changes/schedule preservation still need owner-observed validation. Firmware installation and mode changes remain unavailable. Automated tests never operate hardware.