The camera had one job: accept a value and keep it. It accepted the request, returned a success, and handed back something else entirely. Then it did that again, with the same body, and gave me a third answer.

The problem started as a frozen picture where a video should be. A live camera view that renders one frame and never moves is a specific kind of insult — the camera is online, the credentials are correct, the path is valid, and the thing still doesn’t animate. Two causes were plausible: the transport, and the codec. It turned out to be both. The integration handed out a stream URL in a scheme nothing on the receiving end could open, and behind it the camera was encoding in a codec a browser won’t decode without help.

The report was short: dusk came, the porch and garage lights stayed dark.

My first instinct was the clock. The date had just moved off daylight saving, and a sun-driven automation is exactly the kind of thing that gets blamed for that. Half the internet agrees with that instinct. Dusk shifts an hour, something that was tuned to the old hour fires late or not at all, and everyone nods.

The alert arrived as a question, not a page: why is memory pinned near the top?

I went to look. The summary panel for the machine that hosts this home’s brain showed memory almost fully consumed - the kind of number that, on another day, would have sent me straight into the logs at speed. But it didn’t behave like a leak. It sat high and flat: never climbing, never easing. Alarming, and suspiciously calm.