Living In A Smart Home Part 3:

Get Money, Buy Switches:

With big pushes from Google, Amazon, and many 3rd-party companies in the Smart Home realm we’re almost getting to the point where it’s actually useful. The purpose in this series isn’t necessarily a review or a how-to guide and you may certainly take it with a grain of salt. However, I wanted to write about the who, what, where, how and why in my home and maybe you’ll get some ideas of your own. It’s meant for the novice and the curious. It is for someone who is slightly tech-savvy and someone who isn’t tech-savvy. Feel free to use it as a “drunkenly honest” guide but remember that not everyone’s experience is the same and your applications may be different. With that being said, let’s get started with this entry!

Don’t make the same mistakes I did:

Last entry, I brushed upon your choice of Hub and +1. I recommended a hub by Samsung’s SmartThings. I just wanted to start out with a little support as to why. Receiving some criticism it can look like I’m favoring them and it’s pretty much true. I do obviously favor them cause I have them in my home. So far my experience has been generally positive. The devices I purchase for it work either out of the box or the community has written some impressive code to allow it. However, don’t take me as a professional blogger. I just do this in my spare time. I do not have the unlimited funds that CNET has. If I were totally unhappy with it, I’d change but it seems to fit the bill perfectly. Moving on from that choice I also recommended a +1, a smoke detector. Actually, I said to focus on a safety item. You’re more than welcome to purchase whatever you like. The reason I chose a smoke detector was to solve a specific problem, which was to be notified in case of a fire while my wife and I were away. As I said earlier, this blog is more of a journal-style and the things I encountered. Things I have deployed. Problems I have solved.

Dude, these aren’t problems… they’re wants.

A Reddit user stated that in the home automation there aren’t “problems”. I’ll respectfully disagree. It’s probably my mistake for not defining what I mean by problem but I implore you to take a “Problem” then “Solution” frame of mind. I’m referring to problems like in Math. (Boring, I know) “1 + 1 =” isn’t much of a problem, but it does have a solution. Part of my issue was shopping first. I knew I wanted automated lights, security sensors, automatic watering for my plants, automated sentry turrets… ya know the norm. What I should have focused on was solving problems. I would often see “Smart whatever on sale” and think, oh it just integrates into SmartThings, which simply isn’t true. There was a temptation to buy a whole bunch of switches and just change every one to be smart. (And not to mention costly.) There isn’t necessarily a need for that.

Okay, give me an example of a problem.

No problem! (I love puns) My first problem is my wife, (he said jokingly as his wife glances at him) not that she’s terrible person or anything but she’s actually the best case scenario for a good home automation setup and she keeps my grounded before I try anything extravagant. Whatever I do has to pass the “spouse” test, meaning if she can’t figure it out I am the problem. Specifically our front door was the problem. We came home late at night and our house was pitch black. She tripped over a shoe after trying to fumble to find which switch in a 4-way gang was living room light. Spoilers, it’s the one furthest from the door but try remembering that when you’re fumbling around.

Problem:

We come home late at night and it’s dark.

Solution:

Living room lights come on automatically when we enter the door.

Ah, but how to accomplish this? Well, my BIG mistake was going to buy a “Smart” lightbulb by Googling it. While this worked, it wouldn’t work with the light switch turned off. Remember my wife? Yeah, she turns it off and on to turn the light on and off. Guess what? She’s right. Home Automation and Smart devices need to feel natural. We’ve been programmed to turn lights on and off via a switch. We need to integrate our ideas with that. Hence the title of this week’s article.

Switches or bulbs?

In short, I will always recommend a smart switch over a smart bulb. There are a few exceptions though:

  1. You live in an apartment or rental and cannot make modifications.
  2. You do not feel safe or comfortable doing electrical work or do not wish to hire an electrician to do the wiring for you.
  3. You want different colored smart lights/moods.
  4. You have 3-way switches without the necessary connections.

This doesn’t cover everything of course, but those are some show stoppers when it comes to switches. (We’ll address #4 as it’s not always true.) Bulbs are great as well and I have no problems if you’d rather do bulbs just experience with people coming over is they’ll expect switches to turn on and off rooms, not apps or Alexa. There are other applications where bulbs may be a better choice, just not in any of the cases I personally have ran into.

Continuing our example, I ordered a GE-Z-wave On/Off Dimmable Paddle switch.

This was my first mistake and I lucked out. Always check your hub’s native compatibility list FIRST to ensure easy integration. I lucked out as it was supported by SmartThings, but I’ve ran into some trouble before. SmartThings is great cause chances are someone has already ran into the problem and there’s a solution but if you’re new I HIGHLY recommend checking first. When it arrived, I cut the power and took the plate off the wall.

Second mistake: BEFORE YOU ORDER: make sure you read about how they’re installed. In my case, GE’s Smart Switches REQUIRE a common-wire. (Generally white but could be any color). Once again, luckily I had that connection but I’ve got into 3-way switch installations without everything necessary being there. So once again, BEFORE YOU BUY: cut the power and verify you have all the necessary connections in both locations ESPECIALLY for 3-way switches. (I’ll write an article specifically about 3-ways since they’re very common in my home.) I wired it all up (well, I attempted to a few times and then found out what I was doing wrong) and was able to turn it on/off and finally sync it to SmartThings.

Using the Smart Lighting application on SmartThings I was able to tell the switch that anytime the front door was opened, between the hours of 5:30PM and 7:00 AM to turn on the lights. I’ll get into specific guides about this process later but in the main series I just want to address the big picture. We still had some problems based upon if the light was on already, however that came later.

Finally, I’d like to address one specific thing: It doesn’t make sense to automate everything or at least turn everything smart especially all at once. At anywhere from 30-50 dollars a switch that’s costly and you might not really see a benefit. A good example is my half-bathroom light. I COULD put a motion sensor in there and I could replace the switch to have it automatically come on when occupied then turn off. That’ll run me somewhere between $50-75$ dollars for the hardware. Or, I could just turn the light on and off when I go in like I’ve been doing for years. It sounds nice that you’ll save electricity but it’ll probably take a good long while before you see any return on that investment and most people have an instinct to hit the switch before you enter anyways. My recommendation is that you make sure that when you automate it actually makes sense. Use the problem/solution method, do research first, make a flow chart (coming later) on how that automation plays out.

Cool, but how did SmartThings know when the door was opened?

Sorry this one was a bit long but we had a lot to talk about. One thing I didn’t mention is how we got the door to be automated. While you can just buy a z-wave door sensor I went the more advanced route we’ll talk about next time: Your Smart Home Security System. Thanks for reading and see you next time!

 

 

 

 

Advertisements

ManBeerTech – HappyHourLive! Google Announcment

Hi Folks! Welcome to ManBeerTech HappyHourLive! This week Rusty and Dave talk about the latest Google Announcement from October 4th. We go over the new Pixel Phone line-up, Google WiFi, Google Home, and everything. It’s been a long day, so sit back, relax and enjoy some quick banter to get your mind off of work.

 

 

What does End Of Life mean for Nexus?

So recently, this happened: Google posts End-Of-Life time frames for Nexus devices. Of course, the vocal minority is in a rampage. Everyone is very quick to read the headline and automatically hit reply without actually reading the article to see what is actually going on. So, let us stop the quick judgement and really explore both what does End-Of-Life mean, and how it relates to the Nexus program.

What Does End-of-Life Mean?

Well, according to submissions in Wikipedia, they describe “End-of-Life” as the following:

“End-of-life” (EOL) is a term used with respect to a product supplied to customers, indicating that the product is in the end of its useful life (from the vendor’s point of view), and a vendor stops marketing, selling, or rework sustaining it. (The vendor may simply intend to limit or end support for the product.) ”

So, with that in mind, the concept of End-Of-Life is often used in the tech industry for many products you may not realize. Cisco, Microsoft, and yes, even Apple have End-Of-Life dates for many of their products. (Feel free to reference the Windows XP fiasco.) Generally speaking, this is done when a device, such as a router or switch, needs to be phased out and replaced, either to make way for a newer model or a shift in technology. This does not mean that the businesses need to upgrade their hardware, they also implement something called “End-Of-Support”. End-Of-Support is a period of time after EOL has been exceeded that a product will still receive stability updates or parts/service may be still obtained. Eventually, the cost of support those devices will outweigh the benefit of keeping them. At this point, they will only give “best-effort” service. (Otherwise known as, “eh… if we feel like it” service.)

Yeah, don’t care ’bout that, what about Nexus?

Well, directly from their site, (which you read because you’re an intelligent person) they clearly state: “No guaranteed Android version updates after”. Examining that statement, they’re saying, “Hey.. we’re not going say we are or aren’t, but don’t expect them.” This is what we can call setting a standard for your expectations as a consumer. The Nexus program, for some time now, has had this 18-month support timeframe though it was never really quantified until you see the date. However, where most people quit reading was the 3-years of security, bug-fixes and hardware support they offer. To put it to something relate-able, most computers come with a 90-day warranty and 1 year of tech-support. Windows even has dates set that while they’ll still support the product with critical updates, adding new features isn’t in their best interest.

But… Apple always gets the latest version of iOS, why doesn’t Nexus?

Easy, to quote Steve Balmer: “Developers… Developers, Developers, Developers Developers.” Well, really development in general. Apple has a closed ecosystem. Inside their sandbox, they give you all the details for application development and it is either their way or the information-super-highway. This leaves them with fewer and more standardize hardware models. There are 13 iPhones, 7 iPod touches,12 iPads, and a few other devices. Also, Apple’s software updates don’t always include the latest features either.  While Google may only have 8 in the Nexus lineup,  TheNextWeb has an article stating there are 18.796 distinct Android devices. Wow, that’s a lot to keep up to date. Remember though, Google isn’t really a hardware company, it’s a software and services company. Their product, isn’t necessarily the Nexus, it’s Android. This was more clearly defined back in the day when Nexus phones were more-or-less developer phones and reference devices for how “vanilla” Android should look. However, as time rolled on, so did Google. Hardware/software are usually developed hand-in-hand, it doesn’t make sense to revisit older devices every 6 months, especially when that phone didn’t have a large market share to begin with.

There’s a simple fix:

Stop whining. I do apologize for being blunt but we need to take a step back and look at the broad scope of things. We first complained about fragmentation in Android’s early days. OEMs we’re all over the place in Android versioning, there were few if any updates, and support was severely lacking. Now that Google has enforced rules for device certification and moved its proprietary services in a “walled garden” similar to Apple, we complain that it’s not open. The Nexus program has gone from a developer-tool to a fully fledged prime time consumer phone. Google is a company, companies need to make money. Their image is important and in order to keep up with the industry, it has to advance. If you’re concerned about the time frame of support, don’t buy last years model when this year’s has been out for 6 months. (Nexus 6’s are really cheap are great though, especially for the low-prices.) When you bought the phone, you thought it was the greatest thing and it did everything you want it do. Did that somehow change in the new version? Is it worth it to upgrade? Those are the questions you should ask yourself. You can certainly go buy a car, that is “new” but it be a model that’s well over a year old, the trade off is you’ll get a car for cheaper even though next year’s model might have a “killer” feature. Most of the time, you can wait, or if your budget doesn’t allow, just stay N-1 (meaning current revision, minus 1) for awhile. Or simply switch if it means that much to you. Remember, you’re in control of your money and mind, it’s up to you to make informed decisions.

Till next time….