My Smart Home
Smart homes are fantastic, have an old fan with a light kit, but want it to dim? You’re either pulling an extra conductor and expanding the switch box, or you’re going to burn up the motor by throwing the fan on a dimmer. There does exist a third option — smart bulbs. You can throw these in a standard E27/A19 socket and dim them from your smart home!
Anything from detecting break-ins, playing music, to controlling your HVAC equipment can be done with this technology.
Without open standards, APIs, and people to integrate these technologies, the smart home will continue to exist as a heavily segmented (and thus broken) paradigm for the luxury segment.
My experience is with the Wink Hub (original one), a Emerson Sensi Thermostat, and an old Vivint panel.
Emerson Sensi Thermostat
Overall, the thermostat is great. Installation was a breeze, the power consumption is low enough where a C-wire isn’t required, and setting it up with the app was easy. It also integrates with my Wink app. Downside is that the protocol is closed and secured, and there’s no option for local network control. The Wink app allows control apparently by scraping the Sensi website and sending commands to that. As is standard on a lot of these major manufacturer ‘stats, a disclaimer reads something to the effect of “there is no charge for the online service … this can be changed at any time with or without notice to you.”
A coworker, and also a friend of mine (due to my recommendation) have both bought the Ecobee 4, which seems to not only provide a robust API, but has a very attractive web interface and logging capabilities. As a matter of fact, it was this thermostat that had me forego my ThermoPi project (a Raspberry Pi-based smart thermostat). It had everything I wanted to build!
Another downside of the Sensi thermostat is that the app does have issues logging in occasionally, and changing the setpoint seems laggy. Setting up schedules is really easy though, and for a cost, you can whitelabel the thermostat for integrators, installers, and HVAC technicians.
CREE Connected Bulbs
I have over ten of these CREE bulbs, mostly the warm white color. I’ve had no issues with them once they’re paired (the pairing process is a pain as the Wink App seems as if it stopped responding). The only downside is that they are not outdoor rated, so I cannot use them in my sconces and dim them later at night, or turn up brightness on command. The open design would seem to invite moisture and insects. I’d purchase an outdoor variant if they’d make it. The quality of the light they give off and the brightness range is fantastic.
Kiddie Smart Smoke & C02 Detectors
These units seem great and work very well as networked smoke/C02 detectors. Setting off one will cause any of the other units with the same ID to alarm as well. Unfortunately, you cannot uniquely enumerate what device is going off, so any notifications sent to your phone will have the same name despite the individual device alarming. These do integrate with Wink and seem to work quite well (the networking radio portion seems independent of Wink — which is fantastic as it should work in times when your internet is down, Wink is down, or your power is out.) I have my system to automatically switch on all fixtures, and shut off all HVAC equipment (fan, AC, furnace) to stop blowing oxygen to a fire or stop C02 from being circulated.
TCP Connected Bulbs (5-6″ retrofit Can Lights)
These are both color temperature and brightness variable, which are fantastic. I had envisioned my home theater system — turn on the movie, these smart Wink shades automatically drop down… my lights in the room fade to a 2700K warm glow before fading into darkness just as the movie starts. I could make this happen, I know I can. I used their original API and I know I can send the commands. The problem exists that there is sometimes a few MS delay… up to 10 or more minute delay before commanding a bulb to go off, and the wink hub executing it. I can only imagine this is due to the routing delays of sending these commands out of my network, to theirs, and back again. Even though they have released local control a while ago, it seems flaky at best. Perhaps a Z-Wave dongle would do the trick better.
Samsung 7-Series 55-inch UHD Smart TV
I had a Note 7, I loved it. Best device I ever touched, even now. The thing made my love of technology flourish. It was the “bomb.”
Sadly, I evangelized Samsung products before the recall, had bought a new refrigerator that makes small gunshot sounds. I’ve reported the issue to Samsung who confirmed I was within the warranty period, but insisted that I video the fridge making the sound. They refused to reimburse my costs to tape the intermittent sound.
Anyway — the TV, the reason you’re here. It has a “Smart Hub”, which basically means they made a really shitty Roku clone and glued it to one of the HDMI ports. The thing freezes, and if Netflix’s terrible “original” content wasn’t bad enough, I can’t watch half of it as it refuses to load. What inflames me the most is when it says it cannot connect to the internet, but my extremely sexy Ubiquiti radios tell me exactly when it connected last. Below, you’ll see I bought a Leviton outlet to powercycle this piece of crap each night to see if it helps. So far, only “kinda.”
Yahama RX-V479 Receiver
This thing seems to work pretty well, it has a decent mobile app to control it, and a nice local web interface for doing just about anything else you’d want to.
Wink’s Awful App Layout
I’ve never been an iPhone user, however the Wink App may follow their “we only have one little circle button” paradigm, but it doesn’t work for everybody on Android. If I hit back, I don’t want the application to disappear, I want to go back.
Wink’s App – No Confirmation of Signals
If you turn on a light in the app, the icon will turn orange/blue (depending on the color temperature of the bulb). If it is off, then it is gray. The status on the app will change and does not necessarily reflect the status of the bulb.
Completely Awful API / Integrator Support
I had a Wink API key a few years back, I used it, it was a pain, but I was able to use it. It took days after requesting it to do anything with it, and at that, the disclaimer was pretty much “if you do anything cool with this, we can take your idea and give you nothing.” Well, that API key disappeared. No announcement of EOL for developers consuming their API. They did make a new one, and it still took days for them to manually e-mail out a key to me. I’ve done nothing with it, I can’t justify spending time building for a platform like this.
Leviton Smart Outlet
I’ve installed one of the 15-amp smart outlets to enable remote power-cycling of my terrible Samsung television I bought. The outlet seems to work great, turning on and off. Wink, on the other hand, sees this as a “light” item, and therefore when you toggle the “All Lights” group, it includes this outlet. It’s a bit loud too, the contacts sound pretty hefty. I guess they’d have to if you were saturating the 15A limit. The issue comes down to IFTTT, or the Wink term “Robots.”
I have a Robot shut off my “All Lights” group at 12AM and 8AM, which trips the TV. I do this for electricity savings, however the TV was never supposed to be a part of this. The Samsung TV turns on, as does my PS3 when the power gets restored, so my 12:01AM robot turning just the outlet back on ends up costing me money as I turn off a bunch of lights, but effectively turn on a 55″ LED panel with a computer strapped to the back.
I’ve asked @WinkSupport for a resolution date, but they replied that they have logged it as a “feature request.” Any developer can tell you that means the issue was interpreted as a “lowest possible priority bugfix”, e.g. never.
Most of my smart home technologies are fantastic independently, and the folks over at Quirky/Wink have the hard job of integrating all of these technologies. That said, they haven’t integrated any of them well since they are trying to perpetuate a closed ecosystem and are disinterested in improving their product or enabling developers to do so themselves.