HiddenFox662

so i set up an aws lambda to heat my kettle to exactly 80c for oolong, thinking i’d get that perfect sweet spot, but the brew ends up flat af 😕 maybe the cold start latency adds a few seconds extra heat loss? or the jitter in the cloud clock drifts the temp? i read that hypervisor clock drift can be ±5ms, but does that matter for tea? tbh i think the real issue is the eventual consistency of the iot shadow state, causing the kettle to overshoot then cool down. anyone else seen this weird edge‑case where the cloud’s eventual consistency ruins a cup? would love some tips or just a laugh lol