Leaderboard


Popular Content

Showing content with the highest reputation since 10/18/2018 in Posts

  1. 4 points
    Otto Mation

    Alexa Guard with Iris

    @Scunny pointed out to me that Amazon will be adding Alexa Guard to their line up of skills this fall. I am looking forward to this as a second layer of security to be used in conjunction with Iris. It is a great concept. I have various Alexa devices spread throughout the house. You tell Alexa that you are leaving and it listens for sounds of burglary, glass breaking and smoke/CO alarms etc. and calls you when it hears this. It will also randomize turning on lights to make it look like someone is at home. I for one am looking forward to using this skill. You can read more here: https://www.androidcentral.com/what-amazon-alexa-guard
  2. 4 points
    Vettester

    Iris 3.0 (Yes, it exists)

    Still debating.... I think I'll just sit back and let you guys work out the kinks.
  3. 2 points
    Whyris

    Iris 3.0 (Yes, it exists)

    Well, I took the plunge and purchased one of the V3 hubs. I thought I would share my experiences. First, on the purchasing experience…I went to a local Lowe's and there was no mention of the V3 hub. There did appear to be a couple new V3 devices, but no hub. I asked one of the Lowe's employees about it and showed them the page on their website, which indicated that this store was supposed to have one in stock. After some poking around, they did find that they had two locked up in "the cage". It's interesting that there's yet to be much information provided on this device. Now on to the transition….First off, I don't have a huge system. I'm in a rather small single story house and have 39 devices. Most of them date back to V1, with a few V2. Unfortunately, as has already been lamented in this thread, there is no automated transitioning procedure for going from V2 to V3. Per instructions, you are directed to: 1) Remove the V2 hub from system (which "removes" all devices) 2) Take screenshot of Rules and then delete them 3) Take screenshot of Scenes and then delete them 4) Pair the V3 hub 5) Pair devices to the V3 Hub 6) Add rules, scenes and schedules They give some estimates for how much time to set aside to perform the transition. To cut to the chase, this became an all day (and night) activity for me. Most of that time being spent on a couple of main issues. I started with transitioning all the contact sensors, then motion sensors, and then various other sensors. These all went pretty smoothly, but each device did have to be reset before they could be repaired, which did take some time. Then I got to the keypads. I have three V1 keypads and one V2 keypad. The first V1 went pretty smoothly and the next two took a little more effort to get them into the pairing mode. Then I hit the V2 keypad. This one took hours! It even resulted in a call to Iris, which didn't solve the problem and required a future call-back. The device simply would not go into the pairing mode. Somehow, trying all various strange combinations and tricks, I finally got it to pair. Then there was the last major hurdle…re-pairing to GE Z-Wave switches and sockets. No matter what I did, none of the devices would pair with the new hub. It then dawned on me that these devices could have been orphaned by the removal of the V2 hub. Whether it was necessary or not, I reinstalled the V2 hub as different place and then using Z-Wave tools, systematically used the Remove Z-Wave feature to remove each of the orphaned devices. After doing this, I was then able to successfully repair them to the V3 hub. From there, I completed the transition by adding back my rules and scenes. All the above isn't necessarily unique to the V3 hub, but the experience did lead me to some conclusions that may be helpful to others planning on making the transition. Additionally, after completing the transition, it's unclear how I'm better off, other than that I now have a talking hub like we had in V1 :). I presently DON'T have any wireless communication to the hub, due to the way it was configured. This leads into my recommendations. First, if you want wireless capability, make sure you DO NOT connect the Ethernet port of the hub during initial set-up and DO perform the configuration from a phone app and not via the web portal. I didn't set it up in this manner, as I saw no such guidance. It turns out that if you initially use the Ethernet port (and web portal), it will use this and not enable the Bluetooth and WiFi communications. I was told this (after the fact) by Iris technical support. They stated that they could enable them remotely, but currently there's no configuration option for the user (perhaps a future capability?). Second, based on my orphaned Z-Wave issue, I would recommend cleanly removing all your devices from the network BEFORE disabling the V2 hub. I think had I done this, I would have saved quite a bit of time. Lastly, since you will have to reconfigure your whole system, take as many screenshots as necessary to adequately capture the WAS condition. Don't forget the schedules (not mentioned in the installation guidance), else your memory may be taxed, as was mine. Sorry this was so longwinded, but hopefully others will benefit. Here's also hoping that the future brings new capabilities that makes transitioning from V2 to V3 worthwhile.
  4. 2 points
    accessdenied79

    Iris 3.0 (Yes, it exists)

    [emoji23][emoji23][emoji23]
  5. 1 point
    This is the simplest request, and probably a very common one. WHY ON EARTH does Iris refuse to allow us to schedule rules based on alarm state, or other conditions? For example, I don't want my camera recording me every time I move around the house. I only want to record movement when I'm away from home. Another example, I don't want my thermostat to follow the regular rules when I'm on vacation. (There are MANY other examples of why this is important, but I think these are most common.) I realize there are workarounds, such as buying an extra smart plug to use with each camera, but solutions such as these are UNACCEPTABLE. This is a SIMPLE FIX for Iris developers; just add an "Away" condition to the schedule options, or even better, allow a scene to include a rule within it (this way one rule could trigger a scene, which then triggers another rule.) This is not rocket science. I've only been with Iris for 7 months, but immediately I recognized this fatal flaw. Despite that, I've recommended Iris systems to 5 other households who are now paying customers. Now, as they are becoming familiar with the software, they are beginning to ask me these same questions. It should go without saying that the company is aware of this request. I figure there must be some corporate reasoning for allowing this flaw to persist. Perhaps it's a system vulnerability issue (unlikey, or at least I fail to see the link), or possibly CORPORATE PROFITS (more likely, but I still don't see how selling a few extra smart plugs for cameras would justify such a gaping hole - could it be the paid subscriptions that result from users who have filled up their camera cloud storage with useless motion videos?) Honestly, I can't figure out the logic, but I do believe a solution is intentionally being withheld. The developers MUST know how important this is, but they choose to ignore the request. WHY? If you can't give us this feature, the least you could offer is an explanation. And don't say not enough people have expressed interest...
  6. 1 point
    I don't use Iris for recording video, but I tested this using one of my Iris cameras and am seeing the same thing. However, the rule I setup in the web interface is working and I am able to view the saved video clip on my iPhone app and the web interface. This doesn't surprise me because the last release of the iOS app (v2.12.1) has a lot of bugs.
  7. 1 point
    Vettester

    Iris Portal Survey

    Look again, it's 400 devices at 4 locations.
  8. 1 point
    pavalov

    Iris Portal Survey

    Wow . . . sixty responses! Lowes could benefit from aggregate data at that level. Thanks for pulling it together.
  9. 1 point
    accessdenied79

    Iris 3.0 (Yes, it exists)

    Guess I won’t be buying any V3 plugs then, that’s almost a necessity. Sent from my iPhone using Tapatalk
  10. 1 point
    Wlepse

    Iris Portal Survey

    interesting data...and glad to see so many people filled it out. Seems like this is the type of data Iris should be trying to get from users so they can better understand what people want in the future.
  11. 1 point
    Wlepse

    Iris 3.0 (Yes, it exists)

    Without a migration tool I would be hard pressed to stick with Iris. I am just too jealous of all the cool stuff my friends are doing with ST. If I have to spend time and more money to keep it running I think I would jump ship. The only hesitation I have is the large number of gen 1 products I currently have.
  12. 1 point
    I'd like a motion sensor only.. adjustable would be really awesome.. but probably dreaming with my eyes open My preference would be a ZigBee device.. since I've had all kinds of trouble with Z-wave devices on my Iris system.
  13. 1 point
    sparc

    Iris Portal Survey

    Done. Thanks for creating the survey.
  14. 1 point
    Whyris

    Iris Portal Survey

    Done
  15. 1 point
    Smitho

    Iris 3.0 (Yes, it exists)

    @accessdenied79 Thanks, that is exactly what I was looking to see. Unfortunately I think they missed an opportunity by not putting keyhole slots in the bottom. It would be really nice to have the option to mount it to the ceiling. I would love to have it mounted in a centrally located hallway... however, I'm not sure how many people would go through the trouble to run power to it in a situation like that... maybe POE would have been nice. I won't be picky though, it's just nice to have an option with audible alerts. I'm curious, does it do anything different on a "doorbell chime"? Since it has a speaker now, it would be really nice if an update in the future actually allows you to trigger different chimes and tones.
  16. 1 point
    Smitho

    Iris 3.0 (Yes, it exists)

    Anyone that will... can you please visit this thread and give kudos to my post? We really need a migration tool for the new hub. I'm not about to redo all my rules, recreate my scenes, re-pair all my devices, etc... "Aint nobody got time for that" haha I'm sure others will avoid purchasing the new hub for the same reason. https://community.irisbylowes.com/t5/Feature-Suggestions/Why-can-we-no-longer-migrate-hubs/idi-p/5922
  17. 1 point
    hxn

    Iris Portal Survey

    Done.
  18. 1 point
    accessdenied79

    Iris 3.0 (Yes, it exists)

    Just checked it. Yep it sure is. Sent from my iPhone using Tapatalk
  19. 1 point
    pavalov

    Iris Portal Survey

    Done.
  20. 1 point
    accessdenied79

    Iris 3.0 (Yes, it exists)

    Just because I like punishing myself (apparently) I got the V3 hub and started moving my stuff over. Everything seems to be going well but the V1 buttons and keyfobs are a pain in the A to pair. I have only gotten two buttons paired and gave up and went to other things. Not looking forward to building all my rules again but I did this to myself. Haha. Oh and yes I have factory reset them over and over. Update: might have found the trick, factory reset V1 keyfobs and buttons twice before trying to pair to the new hub. Seemed to work better. Sent from my iPhone using Tapatalk
  21. 1 point
    OhioYJ

    Iris Portal Survey

    Done.
  22. 1 point
    Otto Mation

    Iris Portal Survey

    Done. My number one want is IFTTT and/or Stringify. Sent from my LM-G710 using Tapatalk
  23. 1 point
    rdisom

    Iris Portal Survey

    Done
  24. 1 point
    accessdenied79

    Iris Portal Survey

    Done.
  25. 1 point
    Smitho

    Iris 3.0 (Yes, it exists)

    I WAS really excited about the prospect of a hub that could verbally let me know what was going on. Until I just read that there is no migration process... Unfortunately you will have to delete your hub, re-pair all your devices with your new hub, then re-create your rules, scenes, etc... I have 84 devices, so that's just not a process I want to go through.