<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>HomeOxy API Platform on HomeOxy API</title>
		<link>https://homeoxyapi.duckdns.org/</link>
		<description>Recent content in HomeOxy API Platform on HomeOxy API</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 28 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://homeoxyapi.duckdns.org/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Retention tiers without rewriting storage</title>
				<link>https://homeoxyapi.duckdns.org/blog/retention-tiers/</link>
				<pubDate>Wed, 28 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://homeoxyapi.duckdns.org/blog/retention-tiers/</guid>
				<description>&lt;p&gt;Retention is usually implemented as deletion, which is both expensive and&#xA;destructive. We downsample instead: data younger than 30 days keeps full&#xA;resolution, older data collapses into 5-minute buckets with min, max, mean and&#xA;count preserved.&lt;/p&gt;&#xA;&lt;p&gt;Queries that need raw resolution are answered only for the full-resolution&#xA;window, and the API returns an explicit resolution field so clients never&#xA;silently receive aggregated numbers where they expected raw ones.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Handling clock skew in field devices</title>
				<link>https://homeoxyapi.duckdns.org/blog/clock-skew/</link>
				<pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://homeoxyapi.duckdns.org/blog/clock-skew/</guid>
				<description>&lt;p&gt;Field devices drift. Cheap RTCs lose minutes per month, and devices that lose&#xA;power frequently come back with wildly wrong time. Trusting device timestamps&#xA;makes time-series queries lie.&lt;/p&gt;&#xA;&lt;p&gt;We correct at ingest: each batch carries a device sequence number, and we&#xA;estimate offset against a monotonic counter. Measurements keep their relative&#xA;ordering, and the corrected offset is stored alongside the raw value so the&#xA;original is never lost.&lt;/p&gt;</description>
			</item>
			<item>
				<title>About</title>
				<link>https://homeoxyapi.duckdns.org/about/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://homeoxyapi.duckdns.org/about/</guid>
				<description>&lt;p&gt;HomeOxy is a small engineering team building infrastructure for remote monitoring.&#xA;We started in 2019 as a field-instrumentation contractor and moved into managed&#xA;telemetry after customers kept asking for the same data pipeline.&lt;/p&gt;&#xA;&lt;h2 id=&#34;how-the-platform-is-built&#34;&gt;How the platform is built&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Ingest&lt;/strong&gt; — regional edge nodes accept batched measurements over HTTPS.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Storage&lt;/strong&gt; — append-only time-series store with 13-month retention.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Access&lt;/strong&gt; — versioned REST and streaming endpoints, per-tenant rate limits.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;principles&#34;&gt;Principles&lt;/h2&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Boring, well-understood technology over novelty.&lt;/li&gt;&#xA;&lt;li&gt;Every endpoint documented and versioned before it ships.&lt;/li&gt;&#xA;&lt;li&gt;No silent data loss — rejected payloads are always explained.&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
			</item>
			<item>
				<title>Contact</title>
				<link>https://homeoxyapi.duckdns.org/contact/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://homeoxyapi.duckdns.org/contact/</guid>
				<description>&lt;p&gt;&lt;strong&gt;Support:&lt;/strong&gt; &lt;a href=&#34;mailto:support@homeoxyapi.duckdns.org&#34;&gt;support@homeoxyapi.duckdns.org&lt;/a&gt;&#xA;&lt;strong&gt;Security:&lt;/strong&gt; &lt;a href=&#34;mailto:security@homeoxyapi.duckdns.org&#34;&gt;security@homeoxyapi.duckdns.org&lt;/a&gt;&#xA;&lt;strong&gt;Business:&lt;/strong&gt; &lt;a href=&#34;mailto:sales@homeoxyapi.duckdns.org&#34;&gt;sales@homeoxyapi.duckdns.org&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;We answer support requests within one business day. For incidents affecting&#xA;production ingest, include your tenant ID and the affected time window.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Services</title>
				<link>https://homeoxyapi.duckdns.org/services/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://homeoxyapi.duckdns.org/services/</guid>
				<description>&lt;h2 id=&#34;telemetry-ingest&#34;&gt;Telemetry ingest&lt;/h2&gt;&#xA;&lt;p&gt;Batched HTTPS ingest with idempotency keys, automatic clock-skew correction and&#xA;per-device quotas.&lt;/p&gt;&#xA;&lt;h2 id=&#34;query-api&#34;&gt;Query API&lt;/h2&gt;&#xA;&lt;p&gt;Aggregations over arbitrary windows, downsampling, and cursor-based pagination.&#xA;Responses are cached at the edge for repeat reads.&lt;/p&gt;&#xA;&lt;h2 id=&#34;alerting&#34;&gt;Alerting&lt;/h2&gt;&#xA;&lt;p&gt;Threshold and rate-of-change rules evaluated server-side. Webhook delivery with&#xA;exponential backoff and signed payloads.&lt;/p&gt;&#xA;&lt;h2 id=&#34;managed-gateway&#34;&gt;Managed gateway&lt;/h2&gt;&#xA;&lt;p&gt;Optional on-site gateway for fleets behind restrictive networks. Buffers up to&#xA;30 days of measurements locally.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
