IrisUsers

Members
  • Content count

    839
  • Joined

  • Last visited

  • Days Won

    40

Everything posted by IrisUsers

  1. IrisUsers

    What Platform Should I Migrate To

    If you use modes have a look at the SmartApp I wrote a few years ago to turn off the indicators when night mode is selected and restore them when it’s switched away from.
  2. Just so I am clear, I am speaking in terms of SmartThings v2 vs v3 hubs.. Not Iris. I know nothing about the differences between the Iris hubs as I've never owned a v3 hub.
  3. There is no difference in core capabilities between the two, however there are some nuances.. The v3 hub can connect on wired Ethernet or wireless and is capable of switching between the two automatically. The v2 hub is wired Ethernet only. The v3 hub is Zigbee 3.0 compatible out of the box. The v2 hub will be software upgrade able. None of this means anything now as the SmartThings app doesn’t support QR code pairing yet. The v2 hub has the option for battery backup (4 AA). The v3 hubs does not. The v2 hub has a faster processor and more memory than the v3 hub. This is only a benefit for local processing and probably not noticeable until you have a couple hundred devices. Those are all of the differences that I know of.
  4. I do not think CoRE works any longer. I had heard that SmartThings disabled parts of it due to performance reasons. I would only use WebCoRE, the GUI is much more intuitive to use.
  5. IrisUsers

    Looking for V2 devices

    If you want a SmartPlug that can dim, check these out. CentraLite made lamp dimmers that look just like the V2 SmartPlugs. There aren't many around as they were made only for SmartThings.
  6. IrisUsers

    Arlo Pro 2 Cameras vs Iris Cameras

    The Arlo Pro 2 and Arlo 4k cameras have exterior power cables and even solar panels available. If you power those cameras you can enable video zone motion detection. The side benefit is that it keeps the batteries fully charged, yet when the power goes out the cameras will continue to run on their batteries for weeks.
  7. IrisUsers

    Pairing Iris V2 smart plug with Smart things.

    Anyone having issue with the SmartPlus, there's a good discussion on the ST forum in this thread.
  8. IrisUsers

    My migration experience from Iris to Hubitat

    You can do it out of the box in Hubitat using the built in Hublink app. Love the thread title btw.
  9. IrisUsers

    What will happen to this forum?

    If Arcus should be released in a truly viable form, I see no reason why it cannot continue on as a place to discuss that. I already like the fact that its starting to diversify into other platforms, so there's also a possible future in that direction too.
  10. IrisUsers

    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.
  11. IrisUsers

    Anyone want to donate their V1 devices?

    That's perfect. Thanks for the donation!
  12. One of the Hubitat developers has offered to investigate the possibility of supporting Iris V1 devices. To do that, he's going to need some donations of each of the V1 devices to test. If anyone is interested, please check out this thread and contact Mike Maxwell;
  13. IrisUsers

    My migration experience from Iris to Hubitat

    The unintuitive design on each of those apps was intentional as to follow their SmartThings counterparts. The idea is that it eases the transition from SmartThings to Hubitat, which was their original target market. Welcome to the club! My experience with Hubitat has been good overall too. The first few weeks were terrible, but that was due to their Zigbee stack not being optimized for the number of Zigbee devices (~180) I have. Their devs created some special hub builds for me to help tweak the stack and I split my 400+ device meshes across two Hubitat hubs, all linked together to a third hub acting as a controller. I've never had a faster or more stable home automation platform. Ever.
  14. IrisUsers

    Hubitat

    Welcome aboard! If you haven't already, I recommend registering on their forum. The community is really pitching in to help displaced Iris users with their transition.
  15. IrisUsers

    Anyone want to donate their V1 devices?

    Go register on their forum and PM Mike Maxwell... If you don't want to sign up for an account, drop me a PM and I will be happy to moderate.
  16. IrisUsers

    Iris is Officially Done

    You just touched upon one of the side effects of having a lot of flexibility... With Iris, rules were centralized which made it convenient, albeit limited. With ST, Hubitat, and other platforms, you can have multiple apps all acting on different events and conditions. It's a bit more to keep track of, but does get easier as you become more accustomed to that way of doing things. Glad you got it figured out!!
  17. IrisUsers

    Hubitat

    Keypads are naively supported in Hubitat. No need to load any drivers. Since they’re treated just like locks any automation that can be triggered by a lock event will work. You can also arm from the keypad as well. Truthfully I don’t need to use the keypads much. Mainly to disarm from a glass break or water event. For normal operation, I use combined presence (SmartThings fob, SmartThings app geolocation, and Life360 geolocation) to arm and disarm the system with near perfect results. Since I still have the Arlo cameras on SmartThings, I keep the ST phone presence working and have it linked to my primary Hubitat hub. Now that everything runs local, I do find that the security part of Hubitat exceeds SmartThings.
  18. IrisUsers

    Anyone want to donate their V1 devices?

    There are no guarantees, but several people have reporting that the V1 sensors will at least go into an initializing state on the hub. I do not have any to test with or I would myself.
  19. IrisUsers

    Hubitat

    Yes, it has a security component. You can sign up for Noonlight for professional monitoring for $10 a month.
  20. IrisUsers

    Automation first, Security not so much.

    Its also available in either the new or classic apps.
  21. IrisUsers

    Arcus Smart Home

    They could have licensed it. More likely they reversed engineered the Zigbee cluster/attribute profile by sniffing the zigbee messages. That’s not something overly difficult to do. One of the Hubitat devs has offered to have a look to see if they can reverse engineer it enough to make it work.... Provided someone can donate some devices.
  22. IrisUsers

    Iris is Officially Done

    Unless something changes in 3 months, yes. I got tired of using them because they're crap IMO so I eventually went with the buttonless fobs which suck a but less. Your trigger is a routine, that itself is triggered by a fixed time. Therefore, you're relying on two separate automation to occur, the first a timed event to run the routine, then the routine to run the disarming action. You can set up a direct arm/disarm rule in the new SmartThings app without using a routine, which at least cuts out the chaining of automations.
  23. IrisUsers

    Fatal Habitat bug with iris sensor

    How long are you waiting to see if the sensor is being reported as inactive. It's not instant, nor was it in Iris either.. Zigbee devices go to sleep for a long period of time, only waking up periodically to check in. In SmartThings the interval is about 32 minutes for a check-in. And device has to miss 4 check-ins or become unresponsive for 2 1/2 hours before being declared inactive. I do not know the exact interval Hubitat uses, but they do have that functionality.. Here is what you will see when a device goes offline. This particular sensor fell off the door during the extreme cold last week and no longer works. You can get push notifications for low batteries using Hubitat Safety Monitor. There are two community supplied apps that improve upon offline device reporting. Device Watchdog and Device Monitor. I used Device Monitor in SmartThings and found it to be very useful. Both of those apps go beyond the standard "ping" tests, and actually look to see that the device has reported any kind of events over a period of time. They're planning to release similar functionality to what Iris has. I'm willing to bet it will be released at the same time the mobile app is comes out this spring. In the meantime, have a look at the solutions provided by the community. They'll do exactly what you're looking for.
  24. IrisUsers

    Iris is Officially Done

    There are a couple modifications for your sheet... Iris keypads are supported in SmartThings using the RBoy app/driver. Iris key fobs are supported natively in SmartThings. Homekit is supported via HomeBridge using a community supplied integration. I am not aware of a native capability within SHM disarm at a specific time. You can do it via a Routine with a timed trigger which may be the approach you are taking. I always tied SHM to modes. Switch switching away from Iris 3 years ago, I've built my system this way... When we wake up in the morning, there's a bedside button that we press that puts the house in "Morning" mode. At night we press it again and the house goes into "Night" mode. SHM arming states are very reliable using this method, and that's usually the limit of my manual interaction with the system. I've easily replicated that behavior with Hubitat. I suggest trying a different trigger method. If you've not looked at RBoy's keypad integration you should do so now. It's handles the keypads as if they were locks, thus allows them to be integrated into any automation that supports locks.
  25. IrisUsers

    Iris is Officially Done

    The SmartThings/ADT hub has three significant limitations. First, for the ADT monitoring you MUST use ADT sensors. ADT will not allow you to use non-ADT sensors for the security portion. Second, it is not a full SmartThings hub. The ADT/SmartThings hub also does not support local execution of device or rules either. And lastly, you cannot arm/disarm the ADT portion outside of the app or the keyboard on the hub. You cannot use presence for arming or disarming the system. I’m with scunny, I’d pass.