zeax Posted July 26, 2015 Posted July 26, 2015 I was wondering if anyone had success in getting the Lowe's Iris Garage Door Opener for work? I read from the beta forum that people were able to get it to recognize the Zwave device, but was anyone able to get it to work properly? I have an ISY 994IR Pro with Zwave module added. My firmware is 4.2.30 and Zwave version is 4.55. When I link the Iris Garage door opener it seems to add it ok. But initially I had communication error and it would frequently loose contact when I was like 30 feet away. I'm not sure what the distance for the Zwave for the ISY is but that seems kind of short. But I moved the Iris garage module to about 10 feet from the isy and communication was stable for testing. Has anyone had issue with range or do I need to get a repeater? I guess for insteon, they have the PLM which can really extend the range and I have no issues with my light switches being 60+ feet away. But then I wanted to make sure I can get status of the garage door and make sure everything works before I install everything. They have a tilt sensor which should sense if the garage door is open or close. I would assume the status of the device would be "OPEN" or "CLOSE". No instead it says "STOPPED". I've tried healing, repairing, synchronizing the link but to no avail. I think once I was able get to get it to say "OPEN" or "CLOSE" by moving the tilt sensor, but most of the time it says "STOPPED" This is the device communication events when I hit "query" Sun 07/26/2015 12:32:05 AM : [ZWAVE-TX ZW002_1] ... Sun 07/26/2015 12:32:05 AM : [ZWAVE-RX ] ACK Sun 07/26/2015 12:32:05 AM : [ZWAVE-RX ] [0104011301E8] Sun 07/26/2015 12:32:05 AM : [ZWAVE-TX ] ACK Sun 07/26/2015 12:32:05 AM : [ZWAVE-RX ] [01050013EC0005] Sun 07/26/2015 12:32:05 AM : [ZWAVE-TX ] ACK Sun 07/26/2015 12:32:05 AM : [ZWAVE-RX ZW002_1] ... Sun 07/26/2015 12:32:05 AM : [ZWAVE-TX ] ACK Sun 07/26/2015 12:32:05 AM : [ZWAVE-TX ZW002_1] ... Sun 07/26/2015 12:32:05 AM : [ZWAVE-RX ] ACK Sun 07/26/2015 12:32:05 AM : [ZWAVE-RX ] [0104011301E8] Sun 07/26/2015 12:32:05 AM : [ZWAVE-TX ] ACK Sun 07/26/2015 12:32:05 AM : [ZWAVE-RX ] [01050013ED0004] Sun 07/26/2015 12:32:05 AM : [ZWAVE-TX ] ACK Sun 07/26/2015 12:32:05 AM : [ZWAVE-RX ZW002_1] ... Sun 07/26/2015 12:32:05 AM : [ZWAVE-TX ] ACK Sun 07/26/2015 12:32:05 AM : [ZWAVE-TX ] ... Sun 07/26/2015 12:32:06 AM : [ZWAVE-RX ] ACK Sun 07/26/2015 12:32:06 AM : [ZWAVE-RX ] [0104011301E8] Sun 07/26/2015 12:32:06 AM : [ZWAVE-TX ] ACK Sun 07/26/2015 12:32:06 AM : [ZWAVE-RX ] [01050013EE0007] Sun 07/26/2015 12:32:06 AM : [ZWAVE-TX ] ACK Sun 07/26/2015 12:32:06 AM : [ZWAVE-RX ZW002_1] ... Sun 07/26/2015 12:32:06 AM : [ZWAVE-TX ] ACK Anyone have any idea or suggestion? I like this Zwave garage door opener rather than the Insteon garage door opener because they use a wireless tilt sensor instead of a wired magnet sensor for insteon.
stusviews Posted July 26, 2015 Posted July 26, 2015 I had terrible communication with a Z-Wave lock that was only 20' from the ISY. A simple range extender didn't help. The Aeon Gen 5 siren provided solid communication. BTW, I don't use the siren at all, only its range extender capability.
bernieb Posted July 27, 2015 Posted July 27, 2015 Hi Zeax, I have one of those IRIS Garage Door Controller and it's working fine. I decided to go that route even though I had an Insteon garage door kit, just because of the "All On" issues going on and surely didn't want to have my garage door open in the middle of the night. So I thought that switching protocol (to Z-Wave) would take this our of the equation and it does. I do have to say that it took me quite a bit of time to get it going, out of the box, it seems to look for an IRIS controller. I did stumble on a thread by doing a google search that mentions doing a factory reset of the unit first. It took me a few tries, but finally my ISY was able to discover it. I did loose connectivity right after a fimware upgrade a couple of months back, but it came back on after a couple of days. I've had no issues since.
Michel Kohanim Posted July 28, 2015 Posted July 28, 2015 Hello zeax, If you have other Z-Wave devices, please do make sure that you do a Z-Wave | Tools | Heal Network after you move them around. This includes range extenders. With kind regards, Michel
mikeorst Posted April 11, 2016 Posted April 11, 2016 Any updates on this issue... I just installed the Iris Garage Door Opener yesterday, and my status says Stopped right now and not closed. I've done a heal and everything succeeded. Doing a query doesn't help either right now. I had seen closed and open status message yesterday (and opening and closing) during some testing. but this morning.... it was reporting "stopped". Update: Well might have lost all communication with the garage door controller, as I just tried to open the garage door and nothing happened.
bernieb Posted April 11, 2016 Posted April 11, 2016 I had a frustrating issue a while back that coincided with a firmware upgrade. Not sure if it was really related, but that was the only thing that had changed. I lost communication with all of my Z-wave items except the 2 thermostats. For the Iris garage door, since I wanted to rule out any other issues, I decided to change the battery in the door sensor. I then started to delete/exclude all of my devices that were not communicating and then re-added them. It was a pain. Sure hope that I don't have to go through this again. But it may be your best bet.
mikeorst Posted April 13, 2016 Posted April 13, 2016 Ok... Another quick question I'm hoping someone can help with. I have the garage door reporting proper status however, I see the status as closed... but the HTML UI, shows the device as "Unlocked". Since the door was closed, I would expect it to report "Locked". I use Mobilink to control my devices remotely and wondering if it will send a "Lock" or "Unlock" command to open my door. Also will the status correctly update the Lock/Unlock state if I use my physical garage door button (or normal remote) to open/close the door? Thanks, Mike
Michel Kohanim Posted April 13, 2016 Posted April 13, 2016 Hi Mike, Which interface are you referring to? MobiLinc or default ISY HTML page? With kind regards, Michel
mikeorst Posted April 13, 2016 Posted April 13, 2016 The HTLM UI i see the device marked as Closed, but with the Highlighed "Unlocked" option is with the Default ISY HTML. What I noticed on Mobilinc is I have to use the "reverse" Garage door symbol (also instead of saying Locked/Unlocked or Open/Close it shows 0 for closed, 100 for open, and 103 opening and maybe closing). Didn't know if they were related. Also seems when trying to use Mobilinc to trigger the garage door to open and close its sometimes take a couple presses (which I don't have issues when using Mobilinc with my z-wave kwikset door looks). Again since this device is new to me, not sure what should be "expected" or considered "normal" behavior. Thanks again! Mike
Michel Kohanim Posted April 13, 2016 Posted April 13, 2016 Hi Mike, You can assign different labels in MobiLinc for each state. Would you please send a screenshot of ISY HTML to support@universal-devices.com? With kind regards, Michel
mikeorst Posted April 13, 2016 Posted April 13, 2016 Here is the quick picture of the HTML UI for the IRIS Garage Door Opener.
Chris Jahn Posted April 13, 2016 Posted April 13, 2016 The HTLM UI i see the device marked as Closed, but with the Highlighed "Unlocked" option is with the Default ISY HTML. What I noticed on Mobilinc is I have to use the "reverse" Garage door symbol (also instead of saying Locked/Unlocked or Open/Close it shows 0 for closed, 100 for open, and 103 opening and maybe closing). Didn't know if they were related. Also seems when trying to use Mobilinc to trigger the garage door to open and close its sometimes take a couple presses (which I don't have issues when using Mobilinc with my z-wave kwikset door looks). Again since this device is new to me, not sure what should be "expected" or considered "normal" behavior. Thanks again! Mike Hi Mike, For some reason, the status codes reported to us from Z-Wave door locks is unlocked = 0, locked = 100, but for the garage door (barrier) status we receive closed = 0 and open = 100. You would think that unlocked/open would share the same value but for whatever reasons they are the opposite. Therefore if I read your post correctly, to the degree that you are seeing unlocked/locked instead of closed/open, things are behaving as expected but of course the UI's should be updated to always show closed/open for the garage door status (not locked/unlocked).
mikeorst Posted April 13, 2016 Posted April 13, 2016 Hi Mike, For some reason, the status codes reported to us from Z-Wave door locks is unlocked = 0, locked = 100, but for the garage door (barrier) status we receive closed = 0 and open = 100. You would think that unlocked/open would share the same value but for whatever reasons they are the opposite. Therefore if I read your post correctly, to the degree that you are seeing unlocked/locked instead of closed/open, things are behaving as expected but of course the UI's should be updated to always show closed/open for the garage door status (not locked/unlocked). Yes, I believe things are working as expected, but would like the UI updated so it is clearer. Thanks! Mike
mikeorst Posted April 13, 2016 Posted April 13, 2016 Also one more question... Mobilic get's the #'s for status Hi Mike, For some reason, the status codes reported to us from Z-Wave door locks is unlocked = 0, locked = 100, but for the garage door (barrier) status we receive closed = 0 and open = 100. You would think that unlocked/open would share the same value but for whatever reasons they are the opposite. Therefore if I read your post correctly, to the degree that you are seeing unlocked/locked instead of closed/open, things are behaving as expected but of course the UI's should be updated to always show closed/open for the garage door status (not locked/unlocked). One more question... Mobilinc receives the status codes 0, 100, 103 and reports/displays this in their UI. Other devices show up with status as On/Off, etc... I can change Mobilinc to use custom labels but only changes the On label to a Open or Close, etc... i have no way of telling Mobilinc that "0" = "closed". Is the status of the garage door reported differently to Mobilinc then the way Door Lock Status is reported (besides the value)? Trying to determine if this could be a Mobilinc Bug or ISY issue reporting the status to Mobilinc. In the Java UI, I see the status reported as Text. (Open, Closed, Stopped, Opening, Closing)... This is what I would expect Mobilinc to report... just not sure what value ISY should report to them. I've attached 2 pic's from Mobilinc if that helps explain what I see. Again thanks for your help! Mike
Chris Jahn Posted April 13, 2016 Posted April 13, 2016 Is the status of the garage door reported differently to Mobilinc then the way Door Lock Status is reported (besides the value)? Yes, it is reported in the same way door lock status is reported (different values though). Based on the images, it looks like you just need to update custom names for the status values. Here is a description of the possible values: Closed 0Open 100Unknown 101Stopped 102Closing 103Opening 104
mikeorst Posted April 13, 2016 Posted April 13, 2016 Yes, it is reported in the same way door lock status is reported (different values though). Based on the images, it looks like you just need to update custom names for the status values. Here is a description of the possible values: Closed 0Open 100Unknown 101Stopped 102Closing 103Opening 104 Thanks... My problem is I can only see how to add custom names for 2 states (see previous attached pictures). I can add custom names for On or Off only.
Michel Kohanim Posted April 13, 2016 Posted April 13, 2016 Hi mikeorst, We cannot do anything about MobiLinc. This said, we should be able to fix the Ajax code. Can you please go to http://isy-ip-address/rest/nodes, search for this device, and then copy and paste the associated (and enclosing) information. With kind regards, Michel
mikeorst Posted April 13, 2016 Posted April 13, 2016 Figured that about Mobilinc... just didn't know if anyone here had any experience or tips. Here you go... <node flag="128"> <address>ZW027_1</address> <name>Garage - Wendi</name> <family>4</family> <parent type="3">24059</parent> <type>4.64.7.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <pnode>ZW027_1</pnode> <sgid>1</sgid> <devtype> <gen>4.64.7</gen> <mfg>335.18244.12336</mfg> <cat>184</cat> </devtype> <property id="ST" value="0" formatted="Closed" uom="97"/> </node>
Michel Kohanim Posted April 14, 2016 Posted April 14, 2016 Hi mikeorst, We'll definitely look into it. With kind regards, Michel
Michel Kohanim Posted May 12, 2016 Posted May 12, 2016 Hello mikeorst, We spent a lot of time trying to figure out the best way to do this and we might have a solution. If you have ISY Portal, then you can test it using ISY Web Access from the Portal. If not, please contact me so that we can have you test it: support@universal-devices.com . With kind regards, Michel
Michel Kohanim Posted May 13, 2016 Posted May 13, 2016 Hi mikeorst, Thanks so very much for testing! With kind regards, Michel
Recommended Posts
Archived
This topic is now archived and is closed to further replies.