My Time With The Pixel Watch

When it comes to new devices, the norm for many years now has been for Content Creators (whether well-known or up and coming) to rush to get reviews out as soon as possible. Nearly everyone in the content creation space desperately craves to receive the oh-so-coveted Review Units that device makers release in wild in the hopes of to not only gain some real world usage data, but to also drum up some buzz about their devices. Content Creators not only have the opportunity to score some free new tech, but they also get a chance to claim the “hashtag FIRST crown” which helps develop their reputation of always being in touch with what’s new and hot.

I’m not necessarily criticizing any of this. In fact, I’ve always been a lover of beta testing software and gadgets – mostly because of my love of tinkering in general. And let’s face it, who doesn’t like free stuff? Also, having Content Creators get reviews out early enough can help consumers decide on purchases – especially if the creators have developed trustworthy track records.

But there are times when I wish that some reviews could be held off for a bit longer. I feel sometimes that some device reviews would be better served after a few months of usage, as opposed to several weeks, considering some of the changes that impact many of today’s devices primarily thanks to software updates and security patches, as well as things such as the availability of accessories that tend to be made available months after a device’s release. Often when a device maker has a launch event, many of the features and/or accessories are tagged as “coming soon”. Thus many of the “cool” and “oooh-ahh” things that we see onstage won’t be available for months to come.

Aside from those reasons, I feel that sometimes a few weeks of living with a device simply might not be enough time to truly gauge the value of the device. For example, some devices can be quick and snappy early on, but as more time goes by that may no longer be the case. In which case if Content Creators talk about how fast and responsive a device may be early on, there may be no indication of device sluggishness after a couple of months. Thankfully there are many Content Creators and media outlets who in fact provide followup reviews later down the line, but oftentimes many consumers only look at announcements that are new. Finally I’m willing to concede that much of this is based on my personal preferences, so a lot of what I’m saying here may seem to be much to do about nothing to many of you reading. However I just wanted to voice my opinion about the device review cycle as well as offer some context as to why I waited from the date I received my Pixel Watch (October 17th, 2022) until now (I’m writing this on February 11th, 2023) to give my impressions of it.

The Band Had To Go

Speaking of content norms, it’s typical for reviews like this to start with tech specs. Rather than list them all individually here, I’ll instead point you to Google’s Specs Page. There you’ll find everything you need to know from connectivity, glass type, and battery size.

But from the day the Pixel Watch was officially announced and revealed, I know my biggest issue would have nothing to do with the tech specs. Instead it would be with the included watch band. Specifically, the material that it’s made from. This would not be the first time I’ve had contact with this type of band (made from fluoroelastomer), so even though I knew I wanted the watch I also knew one of the first things I would have to do is replace the band as soon as possible. Simply put, I can’t wear these types of bands for prolonged periods as they cause skin irritation and sometimes discoloration, especially during summer months. Since the Pixel Watch was launched in October, I had plenty of time to grab a replacement band. But with that I ran into a slight hiccup.

The good news is that Google also announced alternative watch bands available in the Google Store. The bad news, in my opinion, is that they are all a bit pricey. So I did what many would do – I turned to Amazon. Going in, I knew specifically what I was looking for. I prefer more traditional metal watch bands, and found this $17 band from E ECSEM. This band is easily adjustable and can easily be attached and detached thanks to the Pixel Watch attachment design. You can view my full Amazon review here. Also, at time of this writing, the price has been reduced to $11.18! And yes – I’m still wearing this band daily.

What’s Not To Like

No beating around the bush here – simply put, the battery. Back when the first Apple Watch became widespread, I chuckled at the iOS faithful who complained about the battery life. After all, what good is a watch that requires you to charge it every night, and sometimes in the middle of the day? (Bear in mind, Apple claimed the watch could achieve 18 hours). As newer models were released, I still heard the same grumblings. In fact, it made me wonder if the whole “smart watch” craze was truly worth it. Sure – there are lots of cool features, sleep tracking, health tracking, etc. But was it all truly worth it if you have to charge them every night?

I began to wonder if there would ever be a worthy offering in the world of Android. Samsung began boasting 40 – 50 hours of battery life with the Galaxy Watch line, which is pretty impressive indeed. But I was already loyal to Google’s Pixel line (not just the phones, but I also owned the Pixel C as well as a Pixelbook), so I was hopeful a watch was son on the way. As it turns out, I had to wait a few more years for this to become a reality but I was hopeful to try a smartwatch just to get a feel for things.

I had read about the Amazfit Bip and gave it a shot. It was an interesting watch that sported a 14 -16 day battery life. It didn’t have any WearOS functionality – it was merely a bluetooth watch that could be used with either Android or iOS. It included it’s own proprietary app for sleep tracking, step tracking, even mobile payments. And above all else, it cost me a mere $35 at the time.

But I then discovered the Amazfit GTR-2 , pictured here to the right of the Pixel Watch. As you see, it has a large, beautiful display, integrates with Alexa, bluetooth calling, Blood Oxygen and Heart Rate tracking, and so on. But most importantly, it also features the impressive 14 – 16 day battery life that I can only WISH the Pixel Watch could achieve.

It is, in my opinion, one of the best smartwatch values for Android users. In fact, be sure to check out Amazfit’s entire line because I’m quite sure you’ll find something to fit your style and needs.

That being said, I was a bit disappointed when the Pixel Watch specs began rolling out, and it became known that it would have a 24-hour battery life. Yes, I still went ahead with it. I, like some reviewers I’ve read, have learned to schedule charging times during less impactful times of the day, which is typically first thing in the morning as I’m getting ready for work. The good news is that it does truly get a full 24 hours, so once I have it fully charged by 7:45AM I don’t have to worry about it again until 7:45AM the next morning. And it charges pretty quickly – in about an hour and a half it can go from about 26% to 100% easily.

Aside from the battery life, I was also a bit confused by Google somewhat ignoring Google Fit in favor of pushing a Fitbit Premium . Look, I get it – Google bought Fitbit so of course they’re going to market it as best they can. But I’ve been using Google Fit since its inception, and I personally have no reason to want to switch. Also, I like the Google Fit interface because it’s clean and simple. Thankfully there’s Health Connect , so I can have Fitbit running and collecting the data I want but I can view it all in Google Fit.

The Final Verdict

Overall, I truly love the Pixel Watch. I love the style, the customization options, and all of the general Googliness! I think there’s room for some improvements that can hopefully be done with software updates (case in point, Bedtime Mode should enable automatically like it does on the Pixel Phone). I think it’s a great value at its price point, and other than the battery life I think did a great job with this latest induction into the Pixel family.

Google Home and Roku TV – Together in Harmony…

If you’re a Cord Cutter like myelf and happen to own a Roku TV, you’re probably wonder how you can control it with Google Home. 

No worries! In this quick demonstration, I show you how I used Logitech Harmony Hub along with a few applets from IFTTT for some basic controls. Up next, I’ll detail the steps I took to tie them all together.

Error
This video doesn’t exist

There’s No Place Like Home

Part 1 – The Basics

As of now there are many reviews out there about Google home.  There are also lots and lots and lots and lots (did I mention LOTS?) of  Amazon Echo vs. Google home videos and reviews. Well rest assured – this isn’t one of them. Rather, much like I did with my Cord Cutting series, I’m going to share with you my experiences and my setup of Google home and all of the gadgets that I have interacting with it to hopefully help you get a few ideas of how you would like to interact with Google home.

As of now there are at least a handful of devices at that effectively interact with Google home, and there are surely more to follow as we go forward. As such, the following is my initial setup. This is surely going to change and evolve over time, and as these changes and evolution happen I will share with you what I have found to be some exciting, and effective ways to enhance my Google home experience. Maybe this will be helpful and exciting for you as well. As usual, I’m not saying my setup is the best setup and it’s the only setup. One of the most exciting things about this sort of Technology is the fact that there are so many different ways that you could set this up and there are more ways coming!

So, what can it do?

This of course is usually the first, and most obvious question. If you go by what you see on commercials, it would appear that there is a lot that Google Home can do. However, it must be understood that it cannot do most of these things out of the box – especially things such as controlling lights.  On its on, it can do “typical” Google things we’ve all come to know and love, such as answer questions or tell us the weather. It can play music and tell us our calendar entries (more on those two things later). Essentially, it’s like having Google packed in a stylish little speaker!

As many of you may know, I’m not one to typically rattle off specs. So for all of you spec junkies, that info can be found here.

Why do the commercials show it dimming lights if it actually can’t do that?

It may seem like a bit of false advertising, but the truth is Google Home can actually control the dimming and on/off functions of lights. But chances are, not the lights you already have (at least not without a little help). For that, you’re going to need to purchase a Hub. The Hub basically acts as the go-between interpreter for Home and Smart Devices. Without a Hub, Home has no way to communicate with these devices.

I decided to go with the well-known Samsung SmartThings. This hub is very easy to setup, and there is wealth of Smart Devices (or as Samsung refers to them as, – “Things”) that work with it. Simply download the SmartThings app for Android or iOS, power up the hub, launch the app and follow the onscreen directions. Quick and easy!

Once you have your SmartThings hub setup, you’re going to need to add some “things” – in this case, some lights. One of the cool things you will learn quickly is that the market already has some good options to choose from, and SmartThings works with most (if not all) of them. But some require extra purchases. Perhaps the most popular name you’ve heard kicked around is Philips Hue. Most of the time, you will see and/or hear about the multi-colored versions. I personally have no use for such bulbs, but you may want to consider them. Philips of course has a line of simple white LED bulbs as well that are also Smart Devices.

However, if you have decided to go with the SmartThings hub and want to use Philips Hue bulbs, you will also have to purchase a Philips Hue Bridge to do so. This bridge is the only way that Google Home can “talk to” Philips Hue bulbs by first sending commands to the SmartThings hub, which then sends to the Philips bridge, and then on to the Hue bulbs themselves.

But, fear not Nerds! With a visit to the “Works with SmartThings” section of the SmartThings website, you will find other options that don’t require a bridge.

Since I recently replaced all the bulbs in my house with LED bulbs, I had no plans to go through and replace them all again just for the sake of Google Home. As such, for the 2 lamps that are in my family room, I decided to grab a couple of SmartThings outlets.

wp-image-810713472jpg.jpg

These little guys would give me the ability to turn the lights on and off via Home, as well as schedule certain tasks through the SmartThings Hub to turn them on and off.

But alas, we were talking about the ability to dim the lights, weren’t we? To do that without a bridge, I picked up a couple of these OSRAM Lightify LED bulbs. Not only do these bulbs provide the ability to dim, they also allow you to adjust the light temperature. So, you can go from Warm White to Cool White, and a few stops in between.

 

 

 

Side note:

Since I decided to use the OSRAM bulbs in these two lamps, the SmartThings outlets currently serve as on/off timers for our Christmas tree and mantle lights!

 

 

And last, but most certainly not least, what good would Google Home be for me if it has no way to communicate with my beloved TCL Roku TV? Thanks to a tip from a user in a Google Home community on Google Plus, I have  the Logitech Harmony Hub to facilitate!

Though maybe not as robust as the SmartThings Hub, this hub fills in the gaps (by way of applets configured via IFTTT – more on that later as well!); specifically, controlling my TV as well as my Yamaha sound bar. I have it configured to turn the TV on and off, as well as launch Plex, Netflix, or regular broadcast TV all through Google Home.

One final thing (more of an honorable mention): there are also wall switches available for those of you who would rather not swap out bulbs. This was my initial intention with my kitchen lights, so I purchased these GE In-Wall Smart Switches. The one pictured here is the “main” switch – if you have 3-way switch connections (as do I), you will also have to purchase the Add-On switch. Unfortunately in my case, the switches are too far away from my SmartThings hub to work. The directions included with the switches point out one major short-coming: the main switch may have to be within 10 feet of the hub in order to connect. In my case, the hub is in the second story master bedroom, and the location of the switches for kitchen lighting is downstairs and on the opposite side of the house. Bummer.  The good news is that with z-wave, the more devices you add the more the signal can daisy chain off of each of them, thus increasing the range. Hopefully, in the near future, I will be adding other devices to get these to work. In the meantime, you may want to go pick them up for yourself – perhaps you’ll have better luck with initial installation.


So there you have it! My basic Google Home setup thus far. Next, I will cover come configuration settings as well as IFTTT applets that I use. Hope you find this info helpful thus far, and please feel free to fire any questions or suggestions my way! Or, share some tips and tricks about your setup. Talk to ya’ soon!