<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Notes on HomeOxy API</title>
		<link>https://homeoxyapi.duckdns.org/blog/</link>
		<description>Recent content in Notes 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/blog/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>
	</channel>
</rss>
