Google Home adds real-time triggers

Smart home news usually sounds smaller than it is. A new trigger here, a new sensor there. But this week’s Google Home update is one of those changes that quietly moves the whole category forward. The gap has been obvious for years — smart homes could do scheduled tricks and voice commands, but they were bad at reacting to what was actually happening in a room. Google is now adding more real-world triggers to Home automations, while Aqara is pushing a sensor that can tell the difference between motion and actual presence. ### What did Google actually add? Google’s spring 2026 Home update expands the automation editor with new starters, conditions, and actions. In plain English, your home can now react to things like temperature, humidity, appliance status, and more device states instead of just time of day or a spoken command. Google is also adding actions like setting light color and arming security systems, plus quicker device access from phone home screens. ### Why is humidity a big deal? Humidity is one of those boring signals that turns out to be incredibly useful. If a bathroom spikes above a threshold, you can run a fan. If a nursery gets too dry, you can kick on a humidifier. If a laundry room stays damp, you can trigger alerts before the room feels gross. Google already had thermostat humidity features in parts of Nest, but bringing humidity into general home automations makes that data usable across the whole house. ### What’s different about presence sensors? Aqara’s FP300 is a good example of where sensors are heading. It combines mmWave, PIR, light, temperature, and humidity into one battery-powered device, and it supports both Thread and Zigbee. The important bit is mmWave — it can detect a person who is sitting still, which old motion sensors often miss. That means fewer “lights off while I’m still here” moments and much better room-by-room automation. ### Why do these two updates fit together? Because Google’s new automation logic needs better inputs. More triggers are only useful if the sensors feeding them are trustworthy. A humidity trigger gets better when a sensor is already in the room for presence. A presence sensor gets more valuable when the platform can use that signal for more than turning lights on. Basically, the platform and the hardware are finally meeting in the middle. ### So is the smart home finally “smart”? Closer, but not fully. Google has also been layering Gemini into Home for camera search, alerts, and natural-language control, which helps people create automations without learning a scripting tool. That lowers the skill barrier a lot. But smarter interfaces do not fix brittle plumbing underneath. Devices and local control are still messy in the real world. A How-To Geek piece published today walks through a local hub setup that became unreliable after the hub was moved, because discovery and pairing depend on network details most people never see. That’s the catch with the local-first promise — it can be faster and more private, but it still asks regular people to debug invisible infrastructure. ### Why does that matter right now? Because the next wave of smart home products will win or lose on reliability, not just features. Presence-aware automations are getting good enough to feel magical. But if moving a hub across a room can break pairing, the magic collapses fast. The companies that solve recovery, setup, and local resilience will have the real advantage. ### Bottom line The story this week is not just that Google added more triggers. It’s that smart homes are becoming state-aware at the exact moment sensors are getting better at reading a room. That is the good news. The bad news is the foundation still needs work.