hadsync 0.2.2__tar.gz → 0.2.3__tar.gz

{hadsync-0.2.2 → hadsync-0.2.3}/.gitignore

@@ -3,6 +3,7 @@
 uv.lock
 .python-version
 __pycache__/
+dist/
 *.py[cod]
 *.egg-info/
 dist/

{hadsync-0.2.2 → hadsync-0.2.3}/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## [v0.2.3] — 2026-05-11
+
+### Fixed
+
+- **False-positive "modified" in `hadsync status` after a clean pull** — macOS APFS can commit a file's mtime a few microseconds after Python records `last_pull`, making `mtime > last_pull` by a sub-second amount even though the pull itself wrote the file. Fixed by comparing timestamps at whole-second granularity: a difference of less than one second means the pull wrote the file, not a user edit. Applied in `hadsync status`, `hadsync diff` conflict detection, and the VS Code status bar.
+
+[v0.2.3]: https://github.com/gevgev/hadsync/releases/tag/v0.2.3
+
+---
+
 ## [v0.2.2] — 2026-05-10
 
 ### Fixed — VS Code Extension

{hadsync-0.2.2 → hadsync-0.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hadsync
-Version: 0.2.2
+Version: 0.2.3
 Summary: Home Assistant Dashboard Sync — pull, edit, and push Lovelace dashboards as code
 Project-URL: Homepage, https://github.com/gevgev/hadsync
 Project-URL: Repository, https://github.com/gevgev/hadsync
@@ -93,29 +93,32 @@ HA stores Lovelace dashboard configs in its internal storage layer. There is no
 ## Installation
 
 ```bash
-pip install hadsync          # once published to PyPI
+pip install hadsync
 ```
 
 Requires Python 3.11+.
 
-### Install from source
-
-**With uv — installs `hadsync` globally so it works from any directory:**
+**With uv (recommended — installs globally so `hadsync` works from any directory):**
 
 ```bash
-# production install (run from anywhere after this)
-uv tool install /path/to/hadsync
+uv tool install hadsync
+```
 
-# editable install — code changes take effect immediately, no reinstall needed
-uv tool install --editable /path/to/hadsync
+After installation, `hadsync` is available system-wide. Upgrade to a newer release with:
 
-# update after pulling new commits (non-editable)
-uv tool install --reinstall /path/to/hadsync
+```bash
+pip install --upgrade hadsync
+# or
+uv tool upgrade hadsync
 ```
 
-**With pip:**
+### Install from source
 
 ```bash
+# editable install — code changes take effect immediately
+uv tool install --editable /path/to/hadsync
+
+# or with pip
 pip install -e ".[dev]"
 ```
 
@@ -258,6 +261,36 @@ battery-status
 
 ## In Action
 
+### `hadsync validate` — issues found
+
+![hadsync validate climate-overview showing 2 warnings: unknown entity on line 192 and a card missing its entity field on line 227](docs/cli-validate-warnings.jpg)
+
+*Validation catches two problems before anything reaches HA: an entity ID that no longer exists in the registry, and a `sensor` card missing its required `entity` field. Both are reported with exact line numbers.*
+
+### `hadsync validate` — all clear
+
+![hadsync validate climate-overview showing PASS after the issues were fixed](docs/cli-validate-pass.jpg)
+
+*After fixing the two issues the dashboard passes cleanly. The same command validates all dashboards at once when run without an ID argument.*
+
+### `hadsync validate` — full suite
+
+![hadsync validate showing all 13 dashboards with PASS](docs/cli-validate-all-pass.jpg)
+
+*All 13 storage-mode dashboards pass in a single run — safe to use in CI pipelines since the command exits non-zero on any error.*
+
+### `hadsync status` — sync overview
+
+![hadsync status table showing 13 dashboards with last pull and push timestamps; climate-overview highlighted as modified](docs/cli-status.jpg)
+
+*A quick at-a-glance table showing when each dashboard was last pulled, when it was last pushed, and whether the local file has been modified since the pull. `climate-overview` shows as `modified` — a local edit is pending.*
+
+### `hadsync push` — safe confirmation
+
+![hadsync push climate-overview showing the view and card counts for HA vs local before asking for confirmation](docs/cli-push.jpg)
+
+*Before pushing, hadsync shows the current HA state alongside what would be sent — 6 views, 32 cards on both sides here — and requires an explicit `y` to proceed. A `--dry-run` flag shows this summary without connecting to HA at all.*
+
 ### `hadsync diff` — conflict summary
 
 ![hadsync diff showing a CONFLICT: HA has 6 views 33 cards, local has 6 views 32 cards, both changed since last pull](docs/diff-conflict-summary.jpg)

{hadsync-0.2.2 → hadsync-0.2.3}/README.md

@@ -36,29 +36,32 @@ HA stores Lovelace dashboard configs in its internal storage layer. There is no
 ## Installation
 
 ```bash
-pip install hadsync          # once published to PyPI
+pip install hadsync
 ```
 
 Requires Python 3.11+.
 
-### Install from source
-
-**With uv — installs `hadsync` globally so it works from any directory:**
+**With uv (recommended — installs globally so `hadsync` works from any directory):**
 
 ```bash
-# production install (run from anywhere after this)
-uv tool install /path/to/hadsync
+uv tool install hadsync
+```
 
-# editable install — code changes take effect immediately, no reinstall needed
-uv tool install --editable /path/to/hadsync
+After installation, `hadsync` is available system-wide. Upgrade to a newer release with:
 
-# update after pulling new commits (non-editable)
-uv tool install --reinstall /path/to/hadsync
+```bash
+pip install --upgrade hadsync
+# or
+uv tool upgrade hadsync
 ```
 
-**With pip:**
+### Install from source
 
 ```bash
+# editable install — code changes take effect immediately
+uv tool install --editable /path/to/hadsync
+
+# or with pip
 pip install -e ".[dev]"
 ```
 
@@ -201,6 +204,36 @@ battery-status
 
 ## In Action
 
+### `hadsync validate` — issues found
+
+![hadsync validate climate-overview showing 2 warnings: unknown entity on line 192 and a card missing its entity field on line 227](docs/cli-validate-warnings.jpg)
+
+*Validation catches two problems before anything reaches HA: an entity ID that no longer exists in the registry, and a `sensor` card missing its required `entity` field. Both are reported with exact line numbers.*
+
+### `hadsync validate` — all clear
+
+![hadsync validate climate-overview showing PASS after the issues were fixed](docs/cli-validate-pass.jpg)
+
+*After fixing the two issues the dashboard passes cleanly. The same command validates all dashboards at once when run without an ID argument.*
+
+### `hadsync validate` — full suite
+
+![hadsync validate showing all 13 dashboards with PASS](docs/cli-validate-all-pass.jpg)
+
+*All 13 storage-mode dashboards pass in a single run — safe to use in CI pipelines since the command exits non-zero on any error.*
+
+### `hadsync status` — sync overview
+
+![hadsync status table showing 13 dashboards with last pull and push timestamps; climate-overview highlighted as modified](docs/cli-status.jpg)
+
+*A quick at-a-glance table showing when each dashboard was last pulled, when it was last pushed, and whether the local file has been modified since the pull. `climate-overview` shows as `modified` — a local edit is pending.*
+
+### `hadsync push` — safe confirmation
+
+![hadsync push climate-overview showing the view and card counts for HA vs local before asking for confirmation](docs/cli-push.jpg)
+
+*Before pushing, hadsync shows the current HA state alongside what would be sent — 6 views, 32 cards on both sides here — and requires an explicit `y` to proceed. A `--dry-run` flag shows this summary without connecting to HA at all.*
+
 ### `hadsync diff` — conflict summary
 
 ![hadsync diff showing a CONFLICT: HA has 6 views 33 cards, local has 6 views 32 cards, both changed since last pull](docs/diff-conflict-summary.jpg)

hadsync-0.2.3/hadsync/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.2.3"

{hadsync-0.2.2 → hadsync-0.2.3}/hadsync/cli.py

@@ -578,7 +578,9 @@ async def _diff_async(dashboard_id: Optional[str], show: bool) -> None:
                         mtime = datetime.fromtimestamp(
                             yaml_path.stat().st_mtime, tz=timezone.utc
                         )
-                        local_modified = mtime > pull_dt
+                        local_modified = (
+                            mtime.replace(microsecond=0) > pull_dt.replace(microsecond=0)
+                        )
                     except Exception:
                         pass
 
@@ -843,7 +845,12 @@ def status() -> None:
             if pull_dt.tzinfo is None:
                 pull_dt = pull_dt.replace(tzinfo=timezone.utc)
             mtime = datetime.fromtimestamp(yaml_path.stat().st_mtime, tz=timezone.utc)
-            return "[yellow]modified[/yellow]" if mtime > pull_dt else "[green]clean[/green]"
+            # Compare at whole-second granularity. macOS APFS can commit the
+            # file mtime a few microseconds after Python records last_pull,
+            # causing a false-positive "modified" on freshly-pulled files.
+            # A sub-second difference means the pull itself wrote the file.
+            modified = mtime.replace(microsecond=0) > pull_dt.replace(microsecond=0)
+            return "[yellow]modified[/yellow]" if modified else "[green]clean[/green]"
         except Exception:
             return "[dim]unknown[/dim]"
 

{hadsync-0.2.2 → hadsync-0.2.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "hadsync"
-version = "0.2.2"
+version = "0.2.3"
 description = "Home Assistant Dashboard Sync — pull, edit, and push Lovelace dashboards as code"
 readme = "README.md"
 license = { file = "LICENSE" }

{hadsync-0.2.2 → hadsync-0.2.3}/vscode-hadsync/src/statusBar.ts

@@ -40,7 +40,12 @@ function isLocallyModified(cwd: string, urlPath: string, lastPull: string): bool
     const yamlPath = path.join(cwd, urlPath, 'lovelace.yaml');
     const stat = fs.statSync(yamlPath);
     const pullTime = new Date(lastPull).getTime();
-    return stat.mtimeMs > pullTime;
+    // Compare at whole-second granularity to avoid a false-positive on freshly
+    // pulled files: macOS APFS can commit the mtime a few microseconds after
+    // the pull records last_pull, making mtime > pullTime by a tiny amount.
+    const mtimeSec = Math.floor(stat.mtimeMs / 1000);
+    const pullSec = Math.floor(pullTime / 1000);
+    return mtimeSec > pullSec;
   } catch {
     return false;
   }

hadsync-0.2.2/hadsync/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.2.2"