Popular Content

Showing content with the highest reputation on 02/11/2019 in all areas

  1. 2 points

    Platform Poll

    I spent a couple of days now messing with openHAB. I used the hardware I bought for the Systronics RF beta. I connected one zigbee, one Z-wave and one wifi device. I went through the whole process up to building a rule. Only took me about 20 hours. I'm going to get a Hubitat for now while SystronicsRF matures.
  2. 1 point

    Groups vs Scenes

    For those who survived the Iris V1 to V2 transition you'll undoubtedly remember that Lowe's took away V1 Device Groups and gave us Scenes instead. Scenes were supposed to be a "functionally equivalent" replacement for groups but they never were, nor could they be. Groups and Scenes are two very different things with some overlap in function, but they are two very different tools with different use cases. For those considering Hubitat as a possible replacement, unlike SmartThings (or Iris) Hubitat actually supports both Group and Scenes. This is accomplished using the built-in "Groups & Scenes" app. Here's a quick look at what each option brings... Groups: Collection of binary-state (on/off) devices (i.e. switches) A common dimmer level for all devices can optionally be set as well. When activated, all member devices within the group are set to the same on/off state. Virtual on/off switch device controls all devices within the group. Group messaging (multicast) is supported. For Zigbee devices, this means that quantity of devices being controlled has no effect on how long it takes for the devices to be controlled. A typical group of Zigbee devices using multicast can be switched in under 1 second, regardless of how many devices are in the group. Scenes: Collection of devices with various attributes (switches, dimmers, RGB bulbs, vents, fans, etc.) Each device can have specific values set to each device attribute. Hubitat has the ability to "capture" a scene by collecting and storing each devices current state. Virtual momentary button is created that can activate the scene. When activated, attributes of member devices within the scene are set to the configured states. No on/off capability. Scenes can only be activated. To have an "off" scene, a separate scene must be created with each device in the desired "off" state. Like Iris, scene commands are executed sequentially. There is a direct correlation between how fast a scene "runs" which decreases as the quantity of devices increases. For those considering SmartThings... SmartThings has only native support for Scenes, however you can easily create something that is functionally equivalent to a device group (but without Zigbee group messaging), but that runs locally. Here's how you do that... Install the Virtual Device Creator (in the Marketplace in the Classic App). Create a virtual switch device. This will serve as the parent for the group, and the means by which the group is to be controlled. Create a SmartLighting rule by selecting the devices you want to control in the "group". Select Switch for "how do you want to control"... And for the action, select "Mirror behavior" Save the rule. Anytime the virtual switch is controlled, the devices specified by the SmartLighing rule will mirror the virtual switches state. If you are concerned with local execution, so long as all of the devices selected in step 3 execute locally, the entire automation will stay local as well.
  3. 1 point
    That's perfect. Thanks for the donation!
  4. 1 point
    So I have made my transition (mostly)...a few stories/observations. 1) I bought a V3 hub. I couldn't get the new app (there are two, Legacy or Classic and new, with the new supposed to be the app to integrate all things Samsung) to even get to the point of scanning the hub QR code or providing the WiFi network info for the hub. The app (iOS) kept erroring on a message about no network access or couldn't access server. Tried my phone on WiFi and cellular. After playing for a while, I tried making a new location and that worked right away. It never asked me about address or proximity circle for the default home location, but it did for the one I created. I don't know if this was just a fluke for me or a bigger bug. 2) I started using the new Smartthings app until I got to the OSRAM light bulb I have out front. It would pair, but it didn't show as a device I could do anything with in the new app. I downloaded and tried the Legacy app and it was there. I was able to create a sunrise/sunset rule with the old app. So it seems that there are some devices that are visible to both apps, but can only be operated on in the old. Weird. 3) As a result, I've been doing all my stuff in the Legacy app, and it seems to work fairly well. The Smart Home Monitor in-app app is a little annoying....I keep going to where I think is the place to setup a rule, but it's the basic config. I have to go over to the dashboard icon for subapp to setup rules. And the subapp for the button controller requires multiple instances if you have multiple button controllers. Unless you have a Smartthings button, in which can you can make automation rules out of it. It all works, but it's a little confusing to me as it's not consistent. 4) I am very appreciative of the thread on this forum about removing devices from Iris before moving to another system. I'm so happy I saw that! I think I wouldn't have realized you could do that and skip the whole device reset. Most of my devices (except of course V1 Iris) unpaired from Iris and re-paired in ST fairly easily. I actually like the ST classic app's way of adding devices... 5) I had a single Iris V2 smart plug and a V2 button fob. I had to get custom code from Github for both and use the ST website and load it in as custom device handlers (or so the ST forum told me). It took a bit of Google-ing to figure that all out, but after the first one, it was easy to do the 2nd. 6) There is an extensive ST Community Forum with lots of good discussions and help, and it seems to be well indexed by Google. I have a few more devices on the way from Amazon to replace Iris V1 stuff. As soon it gets warmer outside, I plan to replace my faulty motion sensing security floodlamp with a ST compatible motion sensor I saw on Amazon.
  5. 1 point
    I sent him a v1 smart plug, motion sensor and key fob. So he'll have something to play with n a few days. That might be enough for proof-of-concept since he thought success would be an all or nothing event.
  6. 1 point


    I've been slowly switching devices over to Wink. Moved Hue bridge and several smart plugs as well as a couple of V2 contact sensors, one of my garage door controllers and my Honeywell wifi thermostat. So far, so good. I am liking the app a little better as I add more stuff. When you add a type of device you don't already have, it adds the appropriate category to the home screen, ie: thermostat, garage door controller, lights, sensors, etc. It makes it easier to find devices, except lights. The app groups bulbs, smart plugs and light switches in one category. I wish there was a way to separate this out. There is a "groups" sub category in the lights main section. I could probably sort here and it would just add one extra screen touch to get to the appropriate device type. I am down to about 100 devices left on Iris, including cameras and all security items. Still researching security systems, but leaning towards Ring since it has most everything I need.
  7. 1 point

    Visa Cards

    It will probably be like the v2 hub roll out.
  8. 1 point
    Thanks, whoever can solve this problem has my business.
  9. 1 point
    Mike, we're currently testing Iris products in house and will have more information on this next week.