• Content count

  • Joined

  • Last visited

  • Days Won


IrisUsers last won the day on April 25 2019

IrisUsers had the most liked content!

About IrisUsers

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

4,244 profile views
  1. IrisUsers

    Gen 1 device limit?

    The best way to map your Zigbee mesh is to pick up an Xbee X2C for about $30 and use XCTU to create a true map. Of course, with any mesh network, this is eye candy and to ensure that routers are routing. It can also be useful to know the preferred neighbor that a SED is using, but it’s virtually impossible to determine the actual route messages are taking.
  2. IrisUsers

    Podcast with Hubitat on Thursday Night the 18th

    I heard an “accidental“ plug for HubConnect a few minutes into the interview. 😇
  3. IrisUsers

    Podcast with Hubitat on Thursday Night the 18th

    Wink is dead. Iris was never mainstream. Thats a claim that cannot simply be made because Lowe's sold their own system in their stores. That does not make it mainstream. Consumer adoption is what determines whether a product is mass market or not. Tech media seldom wrote or blogged about Iris, which was always overshadowed by the larger players. Thats a fact. All published accounts of market penetration estimate there were less than 20k Iris hubs activated. Hubitat is estimated to be around 5k right now. By comparison, SmartThings has over a million, HomeKit, tens of million, same for Google Home and Alexa. Those are true mainstream systems. Iris, like Hubitat, was a niche product. The same will be true for Arcus & Systronics too. And that's not necessarily a bad thing.
  4. IrisUsers

    Podcast with Hubitat on Thursday Night the 18th

    You guys crack me up. There are several women in the Hubitat community who actively participate and wear the HA pants in their households. For them, it is all about HAF. But the reality is that Hubitat isn’t going to fold just because you think the documentation is bad or because they don’t have a mobile app. They have found an audience that can work through those things and are focusing on that group at the moment and doing very well in the process.
  5. IrisUsers

    Kwikset 910 not pairing

    Some locks, especially Z-Wave plus locks have what's called "whisper" pairing, meaning that they transmit at a lower power level during pairing so that they only can talk with the hub. It's a security feature. Relocation after pairing is not an issue with locks that are Z-Wave plus since the spec supports explorer frames for route discovery. That means that the lock can be physically moved without ever having to have a repair run. The 910 is not Z-Wave plus, and it "appears" to require Whisper pairing although Kwikset doesn't directly specify, meaning it probably has to be close to the hub. That also means that a Z-Wave repair is absolutely required after reinstalling the lock so it's knows what its neighbors are. This is true even if you move the hub to be close to the lock. In fact, it's recommended to run 2-3 Z-Wave repairs in sequence to ensure that all devices respond with their neighbor tables. The Hubitat devs recommend pairing locks in place that do not require whisper pairing. It avoids the aforementioned issues with relocation.
  6. IrisUsers

    Kwikset 910 not pairing

    I've never had to remove a lock and bring it close to the hub to pair. In fact, they actually recommend against that. Have you run a Z-Wave repair since pairing the lock? When Z-Wave locks are paried they learn only one parent, and it is usually NOT the closest device. This may come to be surprising, but is intentionally done as part of the algorithm that is used to determine routing. The purpose for this is to extend the range between devices as much as possible, thus maximizing the potential coverage of the Z-Wave mesh since unlike Zigbee it's limited to just 4 hops. Even if that isn't the case, the nearest device could have been busy when the lock sent its discovery message and a device further away answered causing the lock to use it as its upstream router. For this reason, it's always good practice to run a Z-Wave repair anytime a battery-powered device is connected. I would do three things before trying to set codes... Remove ALL codes from the lock either by removing them using the driver page. Pull the batteries from the lock for a few seconds to reset it. Then run a Z-Wave repair.
  7. IrisUsers

    Realistic ETA for a functional Arcus

    That’s where my interest lies as well. The architecture of the platform is built well, but it’s so massive that building in support for new devices proved to be a challenge even for Lowe’s. I am the author of HubConnect which is an app for the Hubitat platform. HubConnect currently has a client for SmartThings which allowed devices on either platform to exist in real-time on both. Another member of the Hubitat community has just released a HubConnect Remote Client for HomeBridge (Home Kit) enabling Hubitat and SmartThings devices to be seen as Apple Homekit devices (and vice-versa). It would be great to see a client built into Arcus. It would immediately open Arcus to virtually any device that can be connected to Hubitat, SmartThings, and HomeKit. If that’s something of interest let me know.
  8. IrisUsers

    Not ready for prime time

    To be clear, your statement of "Hubitat is not ready for primetime" false. It is dubious and misleading as it is based on your own experience and admitted lack of patience. WIth that criteria, that statement could easily apply to SmartThings, Home Assistant, and pretty much every system out there. With SmartThings it would probably be more true than ever since much of the documentation available, but much of it out of date, or specific to one of the two SmartThings apps. Things have changed in the Home Automation space. The herd is being thinned and weaker players are starting to go away. The future is starting to emerge, and in it users will have two options; consumer DIY (Hubitat, SmarThings, Home Assistant, etc) with require some skills to get working, or go with a managed platform (HomeKit, Amazon, Google Home). The problem with managed platforms is that they are closed or limited access ecosystems. You get whatever devices and services the company chooses to offer and usually competitors are shut out. You cited a lack of Nest support. Guess what? Nest declared a few month ago that they were going to stop accepting developer applications for companies looking to integrate ecosystems. That effectively shut out Hubitat, and anyone else after them (i.e Systronics). You cannot use Arlo as an example of a negative. Arlo has a full integration with just three HA platforms; Google, Amazon, and SmartThings. They will not play in the sandbox with anyone else. Their API precludes others from creating unauthorized integrations? How do I know this? I wrote one for SmartThings. Their API kicks all logins out whenever an API call is made under an acccount. Bottom line.. It's going to be hard to beat Iris's out of box experience and conveninece factor. However, when it comes to reliability, flexibility, and expandability, Iris was left in the dust when V2 launched in its partially built state.
  9. IrisUsers

    Tips for migrating to Hubitat

    No argument there from pretty much anyone, including the Hubitat team. They are right now, highly focused in building out the platform and expanding device support, which is no simple task! The one thing Iris did fairly well was to simplify home automation so that the average user didn’t have to be an IT expert. The best thing you can do for Hubitat, SmartThings, or any other system, is to forget how you did things in Iris! As far as the lamp goes, install the native Simple Lighting app and create a new lighting automation. I can give you a screenshot of one of my Simple Lighting automations.
  10. IrisUsers

    NOTICE! for V1 Iris wifi smart plugs

    The warning is because the plug can exhibit undesired behavior during reboot that may affect anything plugged into it.
  11. IrisUsers

    Hubitat V1 Motion Sensor support is flaky

    Been away at a conference for a few days. If you are still having issues, turn your hub off (completely power down) for 15-20 minutes. This will cause all of your zigbee to go into a "paic mode" and try to seek out their coordinator. Unlike Z-Wave, this is how you rebuild a Zigbee network. After 15 miutes power the hub back up. Your Xigbee mesh will begin to rebuild itself. Depending on how many devices you have, this could take an hour, or a day. Everything will be operational during this time, but performance may appear to be sluggish due to all of the stack-related traffic (route discovery messages, requests, etc)
  12. IrisUsers

    Hubitat V1 Motion Sensor support is flaky

    I’ve currently got three V1 motions connected. They’ve all been stable and they all report when expected. I have got two really dense Zigbee meshes with almost 100 devices in each so my environment probably is not similar to yours. do know that there are some V1 driver improvements coming out in the next release targeting battery powered device since there have been some reports of devices going offline.
  13. IrisUsers

    SystronicsRF vs Hubitat

    Good question. I think I have one somewhere. I’ll see if I can find it next week when I’m back home.
  14. IrisUsers

    HubConnect 1.0 is Released!

    HubConnect 1.2 has been released! Whats New? SmartThings Arrival Sensor Driver. This native driver supports all of the functionality of the SmartThings arrival sensors including tone (beep) capability. Native SmartThings DeviceTypes. This release offers 13 drivers with a functional tiles user interface. These drivers can be imported right over existing Universal Drivers on the SmartThings platform to give connected devices functionality in the Classic app. BETA: Hubitat Eventsocket support for remote hubs on local LAN. This provides a significant boost in the speed at which events from remote hubs are delivered to the server hub. By using a persistent socket the burden of subscribing to hundreds of individual device/attribute events as well as the overhead of using https to transport data is eliminated. Asynchronous HTTP. For HTTP oAuth communications (Hubitat hub connected via internet an SmartThings hubs), asynchronous http transactions are now being used to improve performance of parallel event delivery. BETA: Button Translation for SmartThings. SmartThings and Hubitat have different button implementation. This release adds a translation layer for physical buttons connected to SmartThings and linked to Hubitat to ensure that they will trigger automations correctly. Currently only push and held are supported. There is currently no translation to connect physical buttons in Hubitat to SmartThings.
  15. IrisUsers

    That’s all she wrote...

    Looks like it’s been shut down. App no longer loads.