Skip to content

NOTTY v0.3.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 18:09
· 11 commits to main since this release
a367f5d

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.