One of the most popular smart home controllers is SmartThings, especially the company's newest hub, SmartThings V2. Interest in the hub was sufficient to attract the attention of Samsung, who bought SmartThings in August, 2014. Samsung recently touted SmartThings as the hub controller for many of its new smart home endeavors.

Unlike *other smart home hubs, SmartThings controls ZigBee as well as Z-Wave devices, meaning that smart home consumers don't have to choose devices of one standard over the other—opening the door to seemingly twice as many devices. It was the dual support, as well as the Samsung patronage that made me decide to invest in SmartThings.

I have a SmartThings V2 hub, as well a Z-Wave and ZigBee devices from SmartThings and other vendors. In the beginning, I was very happy with the hub, and delighted at what I could control with it. I used it to turn on and off groups of lights, set lights to come on at certain times, or based on motion or a door opening. I also used it for home security. When the outside lights came on at sunshine, the hub would also ensure my door locks were locked. Movement in certain areas at certain times would not only turn on all the house lights, it would also trigger two very loud, very irritating sirens.

All was well, until after Christmas. In January, my SmartThings experience began to go south. It started with a false alarm one night, waking the household up, and generating a frantic check of house cameras to ensure there was no intruder. Over the next month, we suffered three more false alarms, but only some of the lights would come on, and siren support was sporadic. As thankful as we were that the sirens weren't triggering with the false alarm, we contemplated what would happen if the alarm was real, and we slept through it because neither lights nor siren came on.

About a month ago, we found that the nighttime routine that was supposed to set the Smart Home Monitor application's state to armed wasn't running most of the time. When it did run, it frequently wouldn't change the armed status. Then it  became an esoteric exercise to change the application's armed state. We'd have to, first, set the device to Armed (Away), then back to Disarmed, then to Armed (Stay), to get the system to arm the home for the night.

In addition, the morning routine to disarm the routine wouldn't fire, or if it did, wouldn't disarm the home. When a House Hold Member would leave for work, the lights would come on, the alarms would sometimes go off—all of which made for a stressful morning routine. When the disarm procedure did work, it started turning on a small group of lights, for no reason. The same group, each time, including the light that shown directly in my face. There was nothing I could do to stop it.

After months of increasing aggravation, I finally followed the advice of many, and uninstalled SmartThing's Smart Home Monitor application. Now I'm using the Smart Lighting application to trigger lights and alarms, though the routine isn't as sophisticated, and doesn't send out notifications. However, it turns on lights and the alarms when motion occurs in certain areas at certain times, and it does so reliably. That's enough.

In the SmartThings community forum, the complaints about the routines not running on time, and the Smart Home Monitor failing to arm or disarm have taken over, with many customers vowing to dropkick the hub out the window.

Rather than the fix we desperately needed, a month later, a whole new set of problems are surfacing.  Cree bulbs—those lovely, affordable, reliable ZigBee gems—started failing. They still showed as active in the SmartThings Hub, but if you looked at another controller, such as Amazon's Echo, it would show the bulbs as inactive. And the routine to fix the dropped Cree bulb is bizarre: rename the device, several times if you must, and this, somehow, magically reconnect SmartThings to the bulb.

The Cree bulb issues join with problems with several other (primarily Z-Wave) devices, and the answer is typically the same: you have to remove the batteries, or reset the devices, or rename them, or some other process that more closely resembles "sacrifice a chicken at midnight" voodoo than tech troubleshooting.

The Smart Home Monitor wasn't the only application that  began to fail. Others, including one very popular community member-provided application known as Rule Machine, also began to have problems. Because of the problems, the Rule Machine author has pulled the application for now, until the SmartThings infrastructure problems are resolved.

(And how do you get access to these community-provided smart apps? First, you have to have a GitHub account. Yes, not a first step I would recommend if you want widespread adoption of your products. Reliability isn't the only functionality that SmartThings needs to improve.)

The SmartThings status page has noted the problems for several weeks, and we're assured, both in the forum and in the status page, that engineers are working on solutions that they hope to roll out. Soon. Soon. Soon.

The problems that SmartThings faces are the problems many smart home technologies face: dependence on a cloud, increasing numbers of users, and a massive number of device events. Infrastructures that worked for a small number of diehard fans don't scale for larger numbers of people, many of whom are not techs or geeks, just people trying out the new technology; people who will quickly abandon the new technology when they hit problems, rather than persevere like the earlier adopters.

I watched the events for my devices one night, using the web UI that SmartThings provides. My motion detectors not only signal activity, they also signal the room temperature every 10 minutes. So do my sensors that check whether a door is opened or closed. My Netatmo indoor and outdoor temperature sensors also update every ten minutes. When I set one of my Hue bulbs to a different brightness level, it triggered over twenty log entries, as SmartThings reviewed illumination levels, current color setting, current on/off state, and then seemingly did it again and again, several times in a row. When I turned it off, the same twenty-plus log entries were displayed.

After an hour I had to turn off the log: it was so long, I could no longer scroll to the end.

We know that many functions are handled at the device level, and don't require the internet. But when you have coordinated mobile and desktop applications, then you require the cloud. The concern then becomes: what's handled in the device? What's handled in the cloud? And what happens when you magnify all of this by several thousand or tens-of-thousands users, each with many different devices?

What happens is what we're seeing: incomplete or out-of-sync device states, orphaned devices, phantom device activation, slow responses, or non-existent and unreliable responses.

I'm not ready to dropkick my SmartThings Hub V2 out the window, yet. I have both Z-Wave devices and ZigBee, and most hubs support one or the other but not both. When I avoid routines for important functionality, use IFTTT to schedule events, and limit my smart applications to the few that show themselves to be reasonably stable, the system does work. But the functionality is severely limited—a ghost of our glorious expectations.

However, for all the technical problems the company has, it is making some good organizational decisions. SmartThings does stay connected with the users. True, support may not answer your questions for a few days, and the answers not what we'd want, but they do respond. I've found that most of the smart home technology companies have appalling support—I'm been waiting for a response from Netatmo for five months now, and don't even start me on Google's OnHub or Nest support.

In addition, SmartThings employees do respond in the community forum, even though for the most part, they're responding to increasingly irate customers. Not just customer support employees, either: company engineers have communicated from time to time, giving us glimpses into the technology that powers the SmartThings cloud (Groovy, a Java dialect from Apache, and Cassandra for event management).

Amazingly enough, the company also lets the customers vent. And vent. Not many companies would allow customers to discuss the relative merits of competitor products and jumping ships in the product's community forums. I hesitate to say such openness is unique, but it is very unusual. And, frankly, another smart organization decision.

So, I stay with SmartThings. For now. However, I don't recommend buying a SmartThings Hub until the infrastructure problems are fixed.  If this happens, I'll post an update.

* Newer hubs do have support for both ZigBee and Z-Wave. Harmony Home Hub Extender supports both, as does the new VeraPlus Advanced Home Controller.