qapu-cli 0.7.3__tar.gz → 0.7.4__tar.gz

{qapu_cli-0.7.3/qapu_cli.egg-info → qapu_cli-0.7.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: qapu-cli
-Version: 0.7.3
+Version: 0.7.4
 Summary: CLI client for the Qapu API - built for the Hermes agent, but usable by anyone talking to api.ovoo.com.tr from outside the Swarm.
 Author: OVOO Technology
 Classifier: Programming Language :: Python :: 3
@@ -56,7 +56,7 @@ Either way installs a `qapu` command (see `pyproject.toml`'s `[project.scripts]`
 |---|---|
 | `qapu ct-check` | Diagnose CT (current transformer) wiring per phase - reversed polarity vs. wrong phase order - from live PF_R/S/T/AE_R/S/T (GET /hermes/data/{device_id}). |
 | `qapu current` | Current synthesis parameters, grouped (RMS, imbalance, THD, crest factor, fundamental component) (GET /hermes/data/{device_id}). |
-| `qapu data` | Readings per variable for a device - latest value, last N buffered readings (--last), daily min/avg/max (--days), or an explicit --start/--end range (GET /hermes/data/{device_id}). |
+| `qapu data` | Readings per variable for a device - latest value, last N buffered readings (--last), daily min/avg/max (--days), an explicit --start/--end range, or a live-refreshed view (--watch) (GET /hermes/data/{device_id}). |
 | `qapu energy` | One day's active/reactive energy breakdown per phase (GET /hermes/energy/{device_id}). |
 | `qapu health` | Check CLI/server version, connectivity, and server status (GET /health, no auth required). |
 | `qapu pipeline` | Fleet-wide pipeline throughput for a time window - ingest/data/rule/blockchain packet+event counts (GET /hermes/pipeline/stats). `--watch` live-refreshes in place. |
@@ -319,6 +319,14 @@ qapu data <device_id> --start 2026-08-30 --end 2026-08-31 --days 5    # daily mi
 
 **Refined again same day, per three more rounds of direct feedback**: (1) `--last`'s TIME column showed a coarse relative bucket ("1 gün önce") for every one of the N readings - useless once several readings from the same day all collapse to the same bucket. Added a new `_format_time()` helper (`tools/cli/qapu_cli/main.py`, next to the existing `_relative_time()`) that renders the actual data timestamp as `YYYY-MM-DD HH:MM:SS` instead - used only where each row needs its own real time (this per-reading table); `_relative_time()` itself (SIM last-connection, timeline, etc.) is untouched, still relative, since "how long ago" is the right framing there. (2) The per-variable group tables were initially borderless (`box=None`) for a lighter look - reverted to the same bordered `Table()` style every other CLI table already uses ("görsel kısmı güzelleştir tablolu yap"), since the borderless version read as less like a real table, not more. `--json` output is untouched either way ("--json diyince ai kendine göre okur onu" - raw JSON is for machine consumption, formatting choices don't need to accommodate it). (3) The `VARIABLE_ID — Description (Unit)` heading was originally a plain `console.print()` line sitting above each group's table, not visually part of it - moved onto the `Table` itself via Rich's `title=`/`title_justify="left"`/`title_style="bold"` params, so it now renders attached to the table's own border ("kısmını da tabloya dahil edelim tablo yapısı ile görünsün"). Live-tested against real prod data: `qapu data <id> --search VRMS --last 5` now shows 5 grouped, bordered, titled tables with real per-reading timestamps (e.g. `2026-09-01 03:12:14`).
 
+**`qapu data --watch`/`-w` (added 2026-09-04)** - the same live-refresh idea `qapu pipeline --watch` uses (see that command's own entry further down for the underlying pattern), applied to a single device's latest readings instead of the fleet-wide pipeline summary, per a same-day follow-up ("aynı şekilde data izlerken de bir canlı uç açabilirmiyiz"):
+```bash
+qapu data <device_id> --watch                    # every variable, live
+qapu data <device_id> --watch --search VRMS       # combine with family/search filters, same as normal mode
+qapu data <device_id> --watch --interval 2        # poll every 2s instead of the default 5s
+```
+Only valid for the default latest-value mode - refuses clearly if combined with `--last`/`--days`/`--start`/`--end`/`--json`. Filtering logic (`--energy`/`--gsm`/`--voltage`/`--current`/`--battery`/`--search`) was extracted into a shared `_apply_data_filters()` so the watch loop and the normal path can't drift apart. Each poll after the first shows a `DEĞİŞİM` column - green `▲ <diff>` if a variable rose since the last poll, red `▼ <diff>` if it fell, `·` if unchanged - and `ZAMAN` shows the absolute reading timestamp (`_format_time()`, not `_relative_time()` - a 5-second poll loop would show "0 dk önce" for every row regardless of whether it just changed, same reasoning already applied to `--last`'s per-reading table above). Verified the same way as `pipeline --watch`'s delta logic: `_build_data_watch_table()` called directly with two synthetic consecutive polls (one variable rising, one falling, one flat), confirmed correct `▲`/`▼`/`·` rendering - `rich.Live`'s actual screen-redraw behavior wasn't separately re-verified end to end here either, for the same non-TTY sandbox reason noted under `pipeline --watch`.
+
 ```bash
 qapu trend <device_id> <variable_id>            # GET /hermes/trend/{device_id}/{variable_id} - last 20 raw readings + trend
 qapu trend <device_id> <variable_id> --last 50  # last N raw readings instead of the default 20

qapu_cli-0.7.3/PKG-INFO → qapu_cli-0.7.4/README.md

@@ -1,15 +1,3 @@
-Metadata-Version: 2.4
-Name: qapu-cli
-Version: 0.7.3
-Summary: CLI client for the Qapu API - built for the Hermes agent, but usable by anyone talking to api.ovoo.com.tr from outside the Swarm.
-Author: OVOO Technology
-Classifier: Programming Language :: Python :: 3
-Requires-Python: >=3.10
-Description-Content-Type: text/markdown
-Requires-Dist: typer<1.0,>=0.12
-Requires-Dist: httpx<1.0,>=0.27
-Requires-Dist: rich<16.0,>=13.0
-
 # Qapu CLI
 
 A thin command-line client for the Qapu API (`api.ovoo.com.tr`), built for the Hermes agent (runs outside this Swarm, in a separate datacenter, and only ever talks to Qapu through this public API) - but usable by anything else that needs to script against Qapu from outside the private network.
@@ -56,7 +44,7 @@ Either way installs a `qapu` command (see `pyproject.toml`'s `[project.scripts]`
 |---|---|
 | `qapu ct-check` | Diagnose CT (current transformer) wiring per phase - reversed polarity vs. wrong phase order - from live PF_R/S/T/AE_R/S/T (GET /hermes/data/{device_id}). |
 | `qapu current` | Current synthesis parameters, grouped (RMS, imbalance, THD, crest factor, fundamental component) (GET /hermes/data/{device_id}). |
-| `qapu data` | Readings per variable for a device - latest value, last N buffered readings (--last), daily min/avg/max (--days), or an explicit --start/--end range (GET /hermes/data/{device_id}). |
+| `qapu data` | Readings per variable for a device - latest value, last N buffered readings (--last), daily min/avg/max (--days), an explicit --start/--end range, or a live-refreshed view (--watch) (GET /hermes/data/{device_id}). |
 | `qapu energy` | One day's active/reactive energy breakdown per phase (GET /hermes/energy/{device_id}). |
 | `qapu health` | Check CLI/server version, connectivity, and server status (GET /health, no auth required). |
 | `qapu pipeline` | Fleet-wide pipeline throughput for a time window - ingest/data/rule/blockchain packet+event counts (GET /hermes/pipeline/stats). `--watch` live-refreshes in place. |
@@ -319,6 +307,14 @@ qapu data <device_id> --start 2026-08-30 --end 2026-08-31 --days 5    # daily mi
 
 **Refined again same day, per three more rounds of direct feedback**: (1) `--last`'s TIME column showed a coarse relative bucket ("1 gün önce") for every one of the N readings - useless once several readings from the same day all collapse to the same bucket. Added a new `_format_time()` helper (`tools/cli/qapu_cli/main.py`, next to the existing `_relative_time()`) that renders the actual data timestamp as `YYYY-MM-DD HH:MM:SS` instead - used only where each row needs its own real time (this per-reading table); `_relative_time()` itself (SIM last-connection, timeline, etc.) is untouched, still relative, since "how long ago" is the right framing there. (2) The per-variable group tables were initially borderless (`box=None`) for a lighter look - reverted to the same bordered `Table()` style every other CLI table already uses ("görsel kısmı güzelleştir tablolu yap"), since the borderless version read as less like a real table, not more. `--json` output is untouched either way ("--json diyince ai kendine göre okur onu" - raw JSON is for machine consumption, formatting choices don't need to accommodate it). (3) The `VARIABLE_ID — Description (Unit)` heading was originally a plain `console.print()` line sitting above each group's table, not visually part of it - moved onto the `Table` itself via Rich's `title=`/`title_justify="left"`/`title_style="bold"` params, so it now renders attached to the table's own border ("kısmını da tabloya dahil edelim tablo yapısı ile görünsün"). Live-tested against real prod data: `qapu data <id> --search VRMS --last 5` now shows 5 grouped, bordered, titled tables with real per-reading timestamps (e.g. `2026-09-01 03:12:14`).
 
+**`qapu data --watch`/`-w` (added 2026-09-04)** - the same live-refresh idea `qapu pipeline --watch` uses (see that command's own entry further down for the underlying pattern), applied to a single device's latest readings instead of the fleet-wide pipeline summary, per a same-day follow-up ("aynı şekilde data izlerken de bir canlı uç açabilirmiyiz"):
+```bash
+qapu data <device_id> --watch                    # every variable, live
+qapu data <device_id> --watch --search VRMS       # combine with family/search filters, same as normal mode
+qapu data <device_id> --watch --interval 2        # poll every 2s instead of the default 5s
+```
+Only valid for the default latest-value mode - refuses clearly if combined with `--last`/`--days`/`--start`/`--end`/`--json`. Filtering logic (`--energy`/`--gsm`/`--voltage`/`--current`/`--battery`/`--search`) was extracted into a shared `_apply_data_filters()` so the watch loop and the normal path can't drift apart. Each poll after the first shows a `DEĞİŞİM` column - green `▲ <diff>` if a variable rose since the last poll, red `▼ <diff>` if it fell, `·` if unchanged - and `ZAMAN` shows the absolute reading timestamp (`_format_time()`, not `_relative_time()` - a 5-second poll loop would show "0 dk önce" for every row regardless of whether it just changed, same reasoning already applied to `--last`'s per-reading table above). Verified the same way as `pipeline --watch`'s delta logic: `_build_data_watch_table()` called directly with two synthetic consecutive polls (one variable rising, one falling, one flat), confirmed correct `▲`/`▼`/`·` rendering - `rich.Live`'s actual screen-redraw behavior wasn't separately re-verified end to end here either, for the same non-TTY sandbox reason noted under `pipeline --watch`.
+
 ```bash
 qapu trend <device_id> <variable_id>            # GET /hermes/trend/{device_id}/{variable_id} - last 20 raw readings + trend
 qapu trend <device_id> <variable_id> --last 50  # last N raw readings instead of the default 20

{qapu_cli-0.7.3 → qapu_cli-0.7.4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "qapu-cli"
-version = "0.7.3"
+version = "0.7.4"
 description = "CLI client for the Qapu API - built for the Hermes agent, but usable by anyone talking to api.ovoo.com.tr from outside the Swarm."
 readme = "README.md"
 requires-python = ">=3.10"

{qapu_cli-0.7.3 → qapu_cli-0.7.4}/qapu_cli/main.py

@@ -804,42 +804,16 @@ def _print_data_daily_grouped(readings: list[dict[str, Any]]) -> None:
 		console.print(table)
 
 
-# Get a Device's Readings per Variable, Optionally Filtered by Family/Time Window
-@app.command("data")
-def device_data(
-	device_id: str = typer.Argument(..., help="Device ID."),
-	energy: bool = typer.Option(False, "--energy", help="Only Energy segment variables."),
-	gsm: bool = typer.Option(False, "--gsm", help="Only GSM segment variables (signal, network, etc)."),
-	voltage: bool = typer.Option(False, "--voltage", help="Only voltage variables (Unit == V - includes battery voltage)."),
-	current: bool = typer.Option(False, "--current", help="Only current variables (Unit == A)."),
-	battery: bool = typer.Option(False, "--battery", help="Only battery variables (Variable ID starting with B_)."),
-	search: Optional[str] = typer.Option(None, "--search", help="Case-insensitive substring match on the variable ID (e.g. --search vrms for VRMS_R/S/T, or --search AE for AE_R/AE_S/AE_T/AE_L/AE_G - drop the phase/direction suffix to pull the whole family)."),
-	last: Optional[int] = typer.Option(None, "--last", help="Show the last N buffered readings per variable instead of just the latest. Bounded by the buffer's own depth (~50 most recent packets) - not a time window."),
-	days: Optional[int] = typer.Option(None, "--days", help="Show daily min/avg/max over the last N days per variable instead of the latest value. Ignored if --start/--end is also given (the range wins)."),
-	start: Optional[str] = typer.Option(None, "--start", help="ISO date/datetime lower bound, inclusive (e.g. 2026-08-30 or 2026-08-30T14:00:00). Combine with --end for an explicit range - takes priority over --last/--days. Daily min/avg/max narrowed to the range if --days was also given, raw readings otherwise."),
-	end: Optional[str] = typer.Option(None, "--end", help="ISO date/datetime upper bound, inclusive."),
-	as_json: bool = typer.Option(False, "--json", help="Print raw JSON instead of a table."),
-):
-	"""Readings per variable for a device - latest value, last N buffered readings (--last), daily min/avg/max (--days), or an explicit --start/--end range (GET /hermes/data/{device_id})."""
-
-	# Fetch the Readings - Mode Depends on --last/--days/--start/--end,
-	# Already Enriched with Description/Unit/Segment Regardless of Mode
-	params: dict[str, Any] = {}
-	if days is not None:
-		params["days"] = days
-	elif last is not None:
-		params["last"] = last
-	if start is not None:
-		params["start"] = start
-	if end is not None:
-		params["end"] = end
-	readings: list[dict[str, Any]] = client.get(f"/hermes/data/{device_id}", params=params or None)
+# Apply --energy/--gsm/--voltage/--current/--battery/--search Filters to a
+# Readings List - Extracted 2026-09-04 So `data --watch`'s Poll Loop Can
+# Reuse the Exact Same Filter Logic as the One-Shot Path, Rather Than
+# Drifting into a Second Copy.
+def _apply_data_filters(readings: list[dict[str, Any]], energy: bool, gsm: bool, voltage: bool, current: bool, battery: bool, search: Optional[str]) -> list[dict[str, Any]]:
 
 	# Apply Family Filters, if Any - Union (OR) Across Whichever Were Given -
 	# Same Filter Logic Regardless of Mode, Since Variable_ID/Unit/Segment
 	# are Present on Every Row in Every Mode
-	filters_selected = energy or gsm or voltage or current or battery
-	if filters_selected:
+	if energy or gsm or voltage or current or battery:
 
 		# Filter In Place
 		filtered: list[dict[str, Any]] = []
@@ -874,6 +848,112 @@ def device_data(
 		needle = search.strip().lower()
 		readings = [r for r in readings if needle in (r.get("Variable_ID") or "").lower()]
 
+	# Return the Filtered List, Sorted for Stable Output
+	return sorted(readings, key=lambda r: r.get("Variable_ID") or "")
+
+
+# Build a Live-Watch Table for `data --watch` - VARIABLE/VALUE/UNIT/
+# DEĞİŞİM (Changed-Since-Last-Poll Indicator)/TIME, Grouped Neither by
+# Variable (There's Only Ever One Reading per Variable in "Latest" Mode,
+# Unlike --last's Multi-Reading Groups) - Absolute Time (_format_time),
+# not Relative, Since a 5-Second Poll Loop Would Show "0 dk önce" for
+# Every Row Regardless of Whether it Actually Just Changed.
+def _build_data_watch_table(device_id: str, readings: list[dict[str, Any]], previous: Optional[dict[str, Any]], as_of: str) -> Group:
+
+	header = f"[bold]{device_id}[/bold] - Canlı Veri  [dim](güncellendi: {as_of})[/dim]"
+
+	table = Table(show_header=True, header_style="bold")
+	table.add_column("DEĞİŞKEN")
+	table.add_column("DEĞER", justify="right")
+	table.add_column("BİRİM")
+	if previous is not None:
+		table.add_column("DEĞİŞİM")
+	table.add_column("ZAMAN")
+
+	for r in readings:
+		variable_id = r.get("Variable_ID") or "-"
+		value = r.get("Value")
+		value_str = f"{value:g}" if isinstance(value, (int, float)) else "-"
+		unit = r.get("Unit") or "-"
+		reading_time = _format_time(r.get("Time"))
+
+		row = [variable_id, value_str, unit]
+		if previous is not None:
+			prev_value = previous.get(variable_id, {}).get("Value") if isinstance(previous.get(variable_id), dict) else None
+			if prev_value is None or not isinstance(value, (int, float)):
+				row.append("")
+			elif value > prev_value:
+				row.append(f"[green]▲ {value - prev_value:g}[/green]")
+			elif value < prev_value:
+				row.append(f"[red]▼ {prev_value - value:g}[/red]")
+			else:
+				row.append("·")
+		row.append(reading_time)
+		table.add_row(*row)
+
+	return Group(header, table)
+
+
+# Get a Device's Readings per Variable, Optionally Filtered by Family/Time Window
+@app.command("data")
+def device_data(
+	device_id: str = typer.Argument(..., help="Device ID."),
+	energy: bool = typer.Option(False, "--energy", help="Only Energy segment variables."),
+	gsm: bool = typer.Option(False, "--gsm", help="Only GSM segment variables (signal, network, etc)."),
+	voltage: bool = typer.Option(False, "--voltage", help="Only voltage variables (Unit == V - includes battery voltage)."),
+	current: bool = typer.Option(False, "--current", help="Only current variables (Unit == A)."),
+	battery: bool = typer.Option(False, "--battery", help="Only battery variables (Variable ID starting with B_)."),
+	search: Optional[str] = typer.Option(None, "--search", help="Case-insensitive substring match on the variable ID (e.g. --search vrms for VRMS_R/S/T, or --search AE for AE_R/AE_S/AE_T/AE_L/AE_G - drop the phase/direction suffix to pull the whole family)."),
+	last: Optional[int] = typer.Option(None, "--last", help="Show the last N buffered readings per variable instead of just the latest. Bounded by the buffer's own depth (~50 most recent packets) - not a time window."),
+	days: Optional[int] = typer.Option(None, "--days", help="Show daily min/avg/max over the last N days per variable instead of the latest value. Ignored if --start/--end is also given (the range wins)."),
+	start: Optional[str] = typer.Option(None, "--start", help="ISO date/datetime lower bound, inclusive (e.g. 2026-08-30 or 2026-08-30T14:00:00). Combine with --end for an explicit range - takes priority over --last/--days. Daily min/avg/max narrowed to the range if --days was also given, raw readings otherwise."),
+	end: Optional[str] = typer.Option(None, "--end", help="ISO date/datetime upper bound, inclusive."),
+	watch: bool = typer.Option(False, "--watch", "-w", help="Live-refresh the latest-value table in place every --interval seconds (Ctrl+C to stop). Only compatible with the default latest-value mode - not combinable with --last/--days/--start/--end/--json."),
+	interval: float = typer.Option(5.0, "--interval", help="Seconds between refreshes in --watch mode."),
+	as_json: bool = typer.Option(False, "--json", help="Print raw JSON instead of a table."),
+):
+	"""Readings per variable for a device - latest value, last N buffered readings (--last), daily min/avg/max (--days), an explicit --start/--end range, or a live-refreshed view (--watch) (GET /hermes/data/{device_id})."""
+
+	# --watch: Only Meaningful for the Latest-Value Mode - Refuse Clearly
+	# Rather than Silently Ignoring --last/--days/--start/--end/--json
+	if watch:
+		if last is not None or days is not None or start is not None or end is not None or as_json:
+			typer.echo("Error: --watch sadece varsayılan (son değer) modla kullanılabilir, --last/--days/--start/--end/--json ile birlikte kullanılamaz.", err=True)
+			raise typer.Exit(code=1)
+
+		previous: Optional[dict[str, dict[str, Any]]] = None
+		try:
+			with Live(console=console, refresh_per_second=4) as live:
+				while True:
+					readings = client.get(f"/hermes/data/{device_id}")
+					readings = _apply_data_filters(readings, energy, gsm, voltage, current, battery, search)
+					as_of = datetime.now().strftime("%H:%M:%S")
+					if not readings:
+						live.update(Group(f"[bold]{device_id}[/bold] - Canlı Veri  [dim](güncellendi: {as_of})[/dim]", "\n[yellow]Filtreye uyan veri yok.[/yellow]"))
+					else:
+						live.update(_build_data_watch_table(device_id, readings, previous, as_of))
+						previous = {r.get("Variable_ID"): r for r in readings if r.get("Variable_ID")}
+					time.sleep(interval)
+		except KeyboardInterrupt:
+			return
+
+	# Fetch the Readings - Mode Depends on --last/--days/--start/--end,
+	# Already Enriched with Description/Unit/Segment Regardless of Mode
+	params: dict[str, Any] = {}
+	if days is not None:
+		params["days"] = days
+	elif last is not None:
+		params["last"] = last
+	if start is not None:
+		params["start"] = start
+	if end is not None:
+		params["end"] = end
+	readings: list[dict[str, Any]] = client.get(f"/hermes/data/{device_id}", params=params or None)
+
+	# Apply Family/Search Filters, if Any
+	filters_selected = energy or gsm or voltage or current or battery
+	readings = _apply_data_filters(readings, energy, gsm, voltage, current, battery, search)
+
 	# JSON Output - Everything at Once, Never Paginated
 	if as_json:
 
@@ -886,11 +966,10 @@ def device_data(
 		typer.echo("Bu cihaz için henüz veri yok." if not (filters_selected or search) else "Filtreye uyan veri bulunamadı.")
 		return
 
-	# Sort for Stable Output, then Print with the Table Shape the Mode Needs -
-	# the Response Shape (Daily/History/Value Keys) is What Actually Decides
-	# This, not the Request Params Directly, Since --start/--end Alone (no
-	# --days) Comes Back in the Same "History" Shape --last Uses
-	readings = sorted(readings, key=lambda r: r.get("Variable_ID") or "")
+	# Print with the Table Shape the Mode Needs - the Response Shape
+	# (Daily/History/Value Keys) is What Actually Decides This, not the
+	# Request Params Directly, Since --start/--end Alone (no --days) Comes
+	# Back in the Same "History" Shape --last Uses
 	if days is not None:
 		_print_data_daily_grouped(readings)
 	elif last is not None or start is not None or end is not None:

qapu_cli-0.7.3/README.md → qapu_cli-0.7.4/qapu_cli.egg-info/PKG-INFO

@@ -1,3 +1,15 @@
+Metadata-Version: 2.4
+Name: qapu-cli
+Version: 0.7.4
+Summary: CLI client for the Qapu API - built for the Hermes agent, but usable by anyone talking to api.ovoo.com.tr from outside the Swarm.
+Author: OVOO Technology
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: typer<1.0,>=0.12
+Requires-Dist: httpx<1.0,>=0.27
+Requires-Dist: rich<16.0,>=13.0
+
 # Qapu CLI
 
 A thin command-line client for the Qapu API (`api.ovoo.com.tr`), built for the Hermes agent (runs outside this Swarm, in a separate datacenter, and only ever talks to Qapu through this public API) - but usable by anything else that needs to script against Qapu from outside the private network.
@@ -44,7 +56,7 @@ Either way installs a `qapu` command (see `pyproject.toml`'s `[project.scripts]`
 |---|---|
 | `qapu ct-check` | Diagnose CT (current transformer) wiring per phase - reversed polarity vs. wrong phase order - from live PF_R/S/T/AE_R/S/T (GET /hermes/data/{device_id}). |
 | `qapu current` | Current synthesis parameters, grouped (RMS, imbalance, THD, crest factor, fundamental component) (GET /hermes/data/{device_id}). |
-| `qapu data` | Readings per variable for a device - latest value, last N buffered readings (--last), daily min/avg/max (--days), or an explicit --start/--end range (GET /hermes/data/{device_id}). |
+| `qapu data` | Readings per variable for a device - latest value, last N buffered readings (--last), daily min/avg/max (--days), an explicit --start/--end range, or a live-refreshed view (--watch) (GET /hermes/data/{device_id}). |
 | `qapu energy` | One day's active/reactive energy breakdown per phase (GET /hermes/energy/{device_id}). |
 | `qapu health` | Check CLI/server version, connectivity, and server status (GET /health, no auth required). |
 | `qapu pipeline` | Fleet-wide pipeline throughput for a time window - ingest/data/rule/blockchain packet+event counts (GET /hermes/pipeline/stats). `--watch` live-refreshes in place. |
@@ -307,6 +319,14 @@ qapu data <device_id> --start 2026-08-30 --end 2026-08-31 --days 5    # daily mi
 
 **Refined again same day, per three more rounds of direct feedback**: (1) `--last`'s TIME column showed a coarse relative bucket ("1 gün önce") for every one of the N readings - useless once several readings from the same day all collapse to the same bucket. Added a new `_format_time()` helper (`tools/cli/qapu_cli/main.py`, next to the existing `_relative_time()`) that renders the actual data timestamp as `YYYY-MM-DD HH:MM:SS` instead - used only where each row needs its own real time (this per-reading table); `_relative_time()` itself (SIM last-connection, timeline, etc.) is untouched, still relative, since "how long ago" is the right framing there. (2) The per-variable group tables were initially borderless (`box=None`) for a lighter look - reverted to the same bordered `Table()` style every other CLI table already uses ("görsel kısmı güzelleştir tablolu yap"), since the borderless version read as less like a real table, not more. `--json` output is untouched either way ("--json diyince ai kendine göre okur onu" - raw JSON is for machine consumption, formatting choices don't need to accommodate it). (3) The `VARIABLE_ID — Description (Unit)` heading was originally a plain `console.print()` line sitting above each group's table, not visually part of it - moved onto the `Table` itself via Rich's `title=`/`title_justify="left"`/`title_style="bold"` params, so it now renders attached to the table's own border ("kısmını da tabloya dahil edelim tablo yapısı ile görünsün"). Live-tested against real prod data: `qapu data <id> --search VRMS --last 5` now shows 5 grouped, bordered, titled tables with real per-reading timestamps (e.g. `2026-09-01 03:12:14`).
 
+**`qapu data --watch`/`-w` (added 2026-09-04)** - the same live-refresh idea `qapu pipeline --watch` uses (see that command's own entry further down for the underlying pattern), applied to a single device's latest readings instead of the fleet-wide pipeline summary, per a same-day follow-up ("aynı şekilde data izlerken de bir canlı uç açabilirmiyiz"):
+```bash
+qapu data <device_id> --watch                    # every variable, live
+qapu data <device_id> --watch --search VRMS       # combine with family/search filters, same as normal mode
+qapu data <device_id> --watch --interval 2        # poll every 2s instead of the default 5s
+```
+Only valid for the default latest-value mode - refuses clearly if combined with `--last`/`--days`/`--start`/`--end`/`--json`. Filtering logic (`--energy`/`--gsm`/`--voltage`/`--current`/`--battery`/`--search`) was extracted into a shared `_apply_data_filters()` so the watch loop and the normal path can't drift apart. Each poll after the first shows a `DEĞİŞİM` column - green `▲ <diff>` if a variable rose since the last poll, red `▼ <diff>` if it fell, `·` if unchanged - and `ZAMAN` shows the absolute reading timestamp (`_format_time()`, not `_relative_time()` - a 5-second poll loop would show "0 dk önce" for every row regardless of whether it just changed, same reasoning already applied to `--last`'s per-reading table above). Verified the same way as `pipeline --watch`'s delta logic: `_build_data_watch_table()` called directly with two synthetic consecutive polls (one variable rising, one falling, one flat), confirmed correct `▲`/`▼`/`·` rendering - `rich.Live`'s actual screen-redraw behavior wasn't separately re-verified end to end here either, for the same non-TTY sandbox reason noted under `pipeline --watch`.
+
 ```bash
 qapu trend <device_id> <variable_id>            # GET /hermes/trend/{device_id}/{variable_id} - last 20 raw readings + trend
 qapu trend <device_id> <variable_id> --last 50  # last N raw readings instead of the default 20