You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v0.5.15: add AI & Automation docs, bump manifest, update roadmap
- Bump manifest.json version to 0.5.15
- Add CHANGELOG entry for get_drive_data service (PR #38, @nsleigh)
- Add AI-ready drive analysis feature bullet to README
- Add AI & Automation section to README
- Mark multi-variant diagnostic split as shipped in roadmap
- Add get_drive_data service to roadmap as shipped
Copy file name to clipboardExpand all lines: CHANGELOG.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,17 @@
2
2
3
3
All notable changes to SMART Sniffer are documented here.
4
4
5
+
## v0.5.15 -- 2026-06-09
6
+
7
+
Integration-only release. No agent or installer changes. Community contribution by @nsleigh.
8
+
9
+
### Added
10
+
-**`smart_sniffer.get_drive_data` service call** -- returns the full cached SMART dataset for any agent, including raw attributes, our attention evaluation (state, severity, reasons), filesystem usage, and agent metadata. Designed for automation workflows that pipe drive data to an AI for analysis. Call it from an automation, pass the JSON to a conversation agent (Google AI, OpenAI, Claude, Ollama), and get back a plain-English health report. Also works from Developer Tools > Services for manual inspection. Implements #37, contributed by @nsleigh in PR #38.
11
+
12
+
### Upgrade Notes
13
+
-**Integration-only update.** Update via HACS or manually replace `custom_components/smart_sniffer/`. No agent update needed.
14
+
-**New service:** after updating, the `smart_sniffer.get_drive_data` service appears in Developer Tools > Services. Select your agent from the dropdown and call it to see the full response.
15
+
5
16
## v0.5.14 -- 2026-05-30
6
17
7
18
Integration-only release. No agent or installer changes.
Copy file name to clipboardExpand all lines: README.md
+24-1Lines changed: 24 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,8 @@ SMART Sniffer follows the trail, sniffing out the [early warning signs](https://
34
34
35
35
**Auto-discovery** — Agents advertise themselves on the local network via mDNS/Zeroconf. Home Assistant discovers them automatically — no manual IP entry needed.
36
36
37
+
**AI-ready drive analysis** -- A service call returns full SMART data, health assessments, and storage metrics for any agent. Pipe it to Google AI, ChatGPT, Claude, or Ollama for automated drive health reports with zero parsing.
38
+
37
39
**Secure by default** — Optional bearer token authentication between agent and integration. SHA256-verified binary downloads.
38
40
39
41
<br>
@@ -368,6 +370,26 @@ The agent requires smartmontools **7.0+** for JSON output support. Most current
368
370
369
371
<br>
370
372
373
+
## AI & Automation
374
+
375
+
SMART Sniffer includes a `smart_sniffer.get_drive_data` service call that returns the complete cached SMART dataset for any agent. The response includes raw SMART attributes, our attention evaluation (state, severity, and reasons), filesystem usage, and agent metadata -- everything an LLM needs to produce a meaningful health assessment.
| `filesystems` | Per-mount: mountpoint, total bytes, used bytes, percentage |
384
+
385
+
**Example use case: automated weekly health report.** Create an HA automation that runs every Monday morning, calls `smart_sniffer.get_drive_data` for each agent, passes the JSON to a conversation agent (Google AI, OpenAI, Claude, Ollama) with a prompt like "Analyze these SMART readings and flag anything concerning," then emails you the AI's response. The AI can catch patterns like rising reallocated sector counts, aging drives approaching end-of-life, or storage filling up -- things the raw sensor values alone don't always make obvious.
386
+
387
+
The service uses `supports_response: only`, so it also works from **Developer Tools > Services** for manual inspection of the full response payload.
388
+
389
+
For one-off analysis without automation, use **Download Diagnostics** (Settings > Devices & Services > SMART Sniffer > three-dot menu). The downloaded JSON contains the same raw SMART data and can be pasted directly into any AI chat interface. See [Raw SMART data](#raw-smart-data) above.
390
+
391
+
<br>
392
+
371
393
## Screenshots
372
394
373
395
<table>
@@ -505,7 +527,8 @@ Drive-specific `smartctl -a --json` output samples are especially welcome — th
0 commit comments