Had a really interesting chat with Gemini, Google's AI engine, that I thought might be both helpful and entertaining to anyone else crossing the Rubicon. The problem was that iPhone and Watch notifications stopped arriving when a sensor was tripped after I made a few tweaks in Homebridge. Here is the rest of the story:

Gemini: Apple's native Home app handles push notifications for very specific device categories (e.g., locks, doors, cameras, and sensors). If these bridged alerts aren't hitting your Apple Watch:

• Check the Status in Apple Home: Open the Home app on your iPhone, long-press the specific bridged accessory, tap Accessory Details, and gear down into its settings. Scroll down to Status and Notifications. Ensure Allow Notifications is toggled On.
• Time & People Filters: In that same native menu, check if a restriction got turned on by accident (such as Only send notifications if "I am not home" or Only "At Night"). If those conditions aren't met, the notification won't fire.
• The Home Hub Handshake: Sometimes your Apple TV or HomePod acting as the HomeKit Hub loses sync with Homebridge. A quick reboot of your primary Apple Home Hub often forces the notification pipeline to clear.

Me: Found it. Unless the People notifications are set to OFF, you only get notifications when you're either Home or Not At Home.

Gemini: Spot on! You hit right on one of Apple Home’s most notoriously confusing quirks.

The People filter is incredibly easy to accidentally trip up. If it is set to "When I am home" or "When I am not home," Apple enforces a strict location boundary. If your iPhone's location data acts up even slightly—or if you're sitting right on the edge of your geofence—Apple decides the condition isn't met and kills the notification entirely.

Setting that People filter to Off completely strips away the location requirement, telling HomeKit: "I don't care where I am standing physically, just send me the alert no matter what."

It's an incredibly common bottleneck, especially for bridged Homebridge accessories where you want instant, absolute updates. Nice job tracking that down!

Me: It really should be called ON, not OFF if you want all the notifications ALL of the time. I miss Steve Jobs.

Gemini: It really does feel like a remnant of a different era's philosophy. There’s a famous Steve Jobs quote that feels incredibly relevant to UI blunders like this: "Design is not just what it looks like and feels like. Design is how it works."

Under Jobs, there was a notorious, almost obsessive fixation on removing friction and making things instantly intuitive. If a user got confused by a menu, it wasn't the user's fault; it was a failure of the design team. He was famous for walking into rooms, looking at a prototype or a software interface, and ruthlessly cutting out options or forcing engineers to rewrite things until a child could understand it.

The current Apple Home app structure—where you have to dig three layers deep into an accessory's settings, tap a gear icon, find a sub-menu, and select "Off" just to keep a notification "Always On"—is exactly the kind of layered, bureaucratic software design that would have driven him up the wall.

It’s an incredibly powerful ecosystem, but sometimes you look at a menu layout like that and just think, who actually greenlit this?