Relay state change on time logging

[sjefferson99]

Accept inbound payload of relay state on state change from smibhid and include payload of total relay on time since reset. Good for filters on fans driven by relay etc.

[samcorky]

picturing something like this

{"timestamp": "2026-07-08-10:00:00Z", "relay_open": true, "seconds_on_since_reset": 3600}

[sjefferson99]

Would be relay active as we have a toggle for active_high/low to abstract from what the relay is physically doing, so active/inactive or on/off would be the terminology.

[samcorky]

{
  "timestamp": "2026-07-08T10:00:00Z",
  "active": true,
  "active_seconds_since_reset": 3600
}

[samcorky]

Relates to somakeit/smibhid#130 and somakeit/smibhid#134

[samcorky]

Relay On-Time Tracking — SMIB Integration Spec
What SMIBHID now does
SMIBHID drives a relay based on space state (and optionally light sensor state). It now tracks how long that relay has been active locally (for a filter/consumable-replacement use case), persisting a single small state file on-device, and pushes two events to SMIB.
Both calls go through SMIBHID's existing outbound API wrapper — same headers, same base URL pattern, same request machinery as the existing space/state, space/light/state calls SMIB already receives. Base URL is SMIBHID's configured webserver host/port + /api/, with headers Content-Type: application/json and x-smibhid-hostname: .
Endpoint 1 — relay state transition
Fired every time the relay actually changes state (on→off or off→on) — not polled, not periodic.

POST /api/relay/state
{
"active": true,
"timestamp": "2026-07-23T10:00:00Z",
"total_active_seconds": 123456
}active

—trueif the relay just turned on,falseif it just turned off.
timestamp— UTC, ISO 8601,Z-suffixed.
total_active_seconds— SMIBHID's own running cumulative on-time totalat the moment of this transition(includes all time up to and including this event).
Endpoint 2 — on-time counter reset
Fired when a human resets the on-time counter via the SMIBHID web UI or its local API (e.g. after replacing a filter).

POST /api/relay/reset
{
"timestamp": "2026-07-23T10:00:00Z",
"previous_total_active_seconds": 123456
}previous_total_active_seconds

— the total that was just zeroed out on SMIBHID's side. This is context forwhySMIB will start seeing a smaller running total from SMIBHID from now on — it's not an instruction for SMIB to reset anything itself.
Design intent / reconciliation model

SMIB is the system of record for history.SMIBHID doesnotsend a history array or log — just the current event plus its own running total. SMIB is expected to build up its own history from the sequence ofPOST /api/relay/statecalls it receives (its own DB, e.g. Mongo).
total_active_seconds is a cross-check, not authoritative.SMIBHID keeps its own local running total (in a single JSON state file, not an event log) and reports it on every transition. If SMIB's own summed total and SMIBHID's reported total drift apart, that's a signal to investigate — not a hard failure. This isn't safety-critical, so "pretty close" is fine; exact reconciliation is a manual/observability concern, not something either side auto-corrects at call time.
No delivery guarantee yet.If a push fails (SMIB unreachable, network down), the event is currently just logged and dropped on SMIBHID's side — there's no retry queue yet. This is a known gap; a follow-up (buffering failed pushes locally and retrying, similar to how SMIBHID already caches failed sensor-reading pushes) is written up as a future enhancement but not built. So SMIB-side totals can permanently miss events during outages — worth being aware of.
[3:37 PM]Assume the paths above are corrected, will do this now.
[3:41 PM]smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Received POST request to /api/space/relay/state from 192.168.12.105
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Request Headers [('host', '192.168.12.51'),
smib  |  ('user-agent', 'compat'),
smib  |  ('content-length', '80'),
smib  |  ('content-type', 'application/json'),
smib  |  ('x-forwarded-for', '192.168.12.105'),
smib  |  ('x-forwarded-host', '192.168.12.51'),
smib  |  ('x-forwarded-port', '80'),
smib  |  ('x-forwarded-prefix', '/'),
smib  |  ('x-forwarded-proto', 'http'),
smib  |  ('x-forwarded-server', 'smib-proxy'),
smib  |  ('x-real-ip', '192.168.12.105'),
smib  |  ('x-smibhid-hostname', 'SMIBHID-DEV'),
smib  |  ('accept-encoding', 'gzip')]
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Request Body {'active': True, 'timestamp': '2026-07-23T14:41:07Z', 'total_active_seconds': 0}
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Returning 404 response to /api/space/relay/state
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Response Headers [('content-length', '22'), ('content-type', 'application/json')]
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Request processing time: 0.0021 seconds
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Response Body: '{"detail":"Not Found"}'[3:42 PM]smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Received POST request to /api/space/relay/reset from 192.168.12.105
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Request Headers [('host', '192.168.12.51'),
smib  |  ('user-agent', 'compat'),
smib  |  ('content-length', '74'),
smib  |  ('content-type', 'application/json'),
smib  |  ('x-forwarded-for', '192.168.12.105'),
smib  |  ('x-forwarded-host', '192.168.12.51'),
smib  |  ('x-forwarded-port', '80'),
smib  |  ('x-forwarded-prefix', '/'),
smib  |  ('x-forwarded-proto', 'http'),
smib  |  ('x-forwarded-server', 'smib-proxy'),
smib  |  ('x-real-ip', '192.168.12.105'),
smib  |  ('x-smibhid-hostname', 'SMIBHID-DEV'),
smib  |  ('accept-encoding', 'gzip')]
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Request Body {'previous_total_active_seconds': 82, 'timestamp': '2026-07-23T14:42:29Z'}
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Returning 404 response to /api/space/relay/reset
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Response Headers [('content-length', '22'), ('content-type', 'application/json')]
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Request processing time: 0.0067 seconds
smib  | [DEBUG] [HttpRequestLoggingMiddleware]: Response Body: '{"detail":"Not Found"}'