According to a Google Product Expert on Google’s support forums, this is how it should work. Noting “This is working as intended. The watch is separate from the phone when it comes to alarms.” But it gets better, as this same “product expert” believes that other Wear OS 3.x watches should sync, but the Pixel Watch shouldn’t. Wait what? Other Wear OS smartwatches and even the Apple Watch will sync alarms between the phone and the watch. So why can’t the Pixel Watch and whatever phone it is connected to? This seems like a huge oversight for Google, and hopefully something they’ll fix in a future update. Remember, the Pixel Watch is getting feature drops like Pixel phones do.
For now, you’ll have to set alarms independently
This makes the Pixel Watch not very “smart”. Which is kind of ironic. But this is also typical Google. Launch a new product, and forget to add simple features that should be there at launch. YouTube Music is a prime example of this, where it was set to replace Google Play Music, but left out a lot of simple features, even after Google Play Music was finally killed off. As much as I like the Pixel Watch, Google is making it harder and harder to actually recommend. Not only because of this, but also the poor battery life, even without AOD even being on. But I do have high hopes for a second generation Pixel Watch to be pretty impressive. Let’s hope they can fix the battery life, as these other issues are software fixes.
