Switch Two Monitors Between Windows PCs Without a KVM
A reliable DDC/CI handoff must coordinate monitor inputs with Windows display topology, taskbar placement, control loss, and rollback.
All articles
News analysis, operating lessons, home automation, and guides grounded in systems I run or can inspect closely.
A reliable DDC/CI handoff must coordinate monitor inputs with Windows display topology, taskbar placement, control loss, and rollback.
A recursive close handler and stale client session IDs show why transport lifecycle needs explicit states and failure-focused tests.
Read-only defaults, separate identities, bounded context, session cleanup, and honest health checks matter more than exposing more tools.
Measured latency, model sizing, availability, entity exposure, false action claims, memory, and the boundary between language and deterministic code.
Model soft-off and hard-off separately, restore power before sending a scene, wait for availability, and keep startup logic in one helper.
Room cleaning works locally through Matter, but room identifiers, error handling, charging data, and battery reporting still need careful treatment.
Six WLED controllers, mixed white channels, and one Home Assistant light group. Includes YAML, a read-only inspector, and checks for inconsistent lighting.
One-way RF control fails when an upstream wall switch removes power. Continuous power and a clear control boundary fix the architecture.
Shared HTTP transports expose identity, session, context-budget, health-check, and cleanup problems that local tool calls can hide.
Three failures from my house: an unpowered RF receiver, a WLED controller still booting, and an S2 vacuum that needed to complain when it got stuck.