dss

Please add me to the list also. Are there particular brands of Z-wave locks that provide API's that you anticipate support for. I'd like to avoid the ones that don't provide API's like the Zigbee doorlocks? I see Schage: http://www.amazon.com/Schlage-Wireless- ... 175&sr=8-1 and Kwickset ones: http://www.amazon.com/Kwikset-99100-006 ... 175&sr=8-3

That's good to hear. But the 994iZ is already working with Zigbee right? So couldn't the Zigbee Door knobs be supported more quickly than waiting for Zwave? http://www.kwikset.com/Products/Details ... P-SMT.aspx http://www.kwikset.com/SmartSecurity/Wi ... wners.aspx http://www.baldwinhardware.com/products ... Entry.aspx

Yes, I hope they implement it soon. Although I've been happy with ISY and trust their support and updates going forward I've actually been contemplating changing over to a Cortexa CTXA-EZ1 http://www.smarthome.com/12021/Cortexa- ... EZ1/p.aspx to get Z-wave capability in addition to Insteon specifically for automated door locks. Pretty much the only thing Z-wave has that Insteon does not. I'm a little leery as they don't seem to have an established track record and they've abandoned prior product lines before and I would much prefer a 994iZ solution. The customer ratings on the Smarthome website seem to be positive though. So I'm holding off a few months to see if the 994iZ gets ZigBee door lock support and to get more reviews/feedback on Cortexa before deciding.

I for one would vote for adding this capability and would upgrade to a 994iZ for this capability. I think automated door knobs are probably the last major hole in the Insteon ecosystem that Zigbee and Z-wave have that Insteon lacks. If it were publicized that the 994iZ had this capability over the 99i I think it would drive sales of 994iZ's. Even if you don't immediately intend to install automated door knobs you'd probably pay the extra $160 for that future capability. It would be the about the only solution that would give status back to Insteon. The only other alternative that I could see is using a Micasa Verde Vera that is supposed to support Z-wave and Insteon but it seems like the Insteon support for the Vera is weak and I'd much rather stay in the ISY environment.

The problems with the Kwikset solution are that a) you get feedback on the state of the bolt (extended or recessed) but no confirmation that the door is actually locked (if the bolt is extended but the door is open you aren't secure); and the Kwikset solution speaks a different language than the ISY. I actually have an Elk Gold system with the Elk module so I am already getting the status of whether the door is actually opened or shut. It is just that I don't know whether it is locked or not. I had been looking at the ISY994i Z Series with Zigbee support and wondered if it was compatible with the Kwikset Zigbee door lock. If it were I'd consider upgrading my ISY99 to the ISY994i. http://www.universal-devices.com/commer ... i-z-series

The problem with the Morning Industry solution is that it is that communication is only one way. You can send commands to open or shut a lock but can't see the status of whether the lock is open or shut. The Kwickset Zigbee solution does report the status of the lock so if it can work with an ISY it would be a better solution. http://www.kwikset.com/SmartSecurity/Wi ... ology.aspx

The major category of home automation that Insteon still doesn't support are the door knobs. I see from the Universal Devices product page that there is the ISY994i Z that supports Zigbee. Anyone know if it will work with a Kwikset Zigbee door knob?: http://www.kwikset.com/SmartSecurity/Wi ... ology.aspx Any alternative suggestions on getting the door knobs automated in an ISY/Insteon system perhaps with Z-wave doorknobs: Baldwin http://www.baldwinhardware.com/products ... Entry.aspx Schlage http://link.schlage.com/Products/Pages/ ... erKit.aspx

I found the problem, in the Elk RP in the M1XEP Setup I had checked "Enable Non-Secure Port" but hadn't "Send" it to the ELK.

I seem to be having the same problem as FRR. I'm using 3.1.13. I can access the virtual keypad with the pass code through the web browser but cannot arm disarm go to ELK console from ISY. The ISY interface is very slow when I click on an ELK tab. Does nothing and seems like completely froze up for about 1 minute until it refreshes and changes the tab. I can see my alarm sensor zones but it only lists the area and zone status physical status. I don't see the Name nor Type and I cannot manually enter the name. I get these errors in the log: Thu 12/01/2011 01:51:00 AM : [FileOpen ] Open failed for [/CONF/INTEGER.VAR] ® Thu 12/01/2011 01:51:00 AM : [FileOpen ] Open failed for [/CONF/STATE.VAR] ® Thu 12/01/2011 01:51:00 AM : [FileOpen ] Open failed for [/CONF/INTEGER.VAR] ® Thu 12/01/2011 01:51:00 AM : [FileOpen ] Open failed for [/CONF/STATE.VAR] ® Thu 12/01/2011 01:51:04 AM : [ELK-ERR ] Get Topology Thu 12/01/2011 01:51:11 AM : [Elk ] ELK-WAIT Waiting for retry 1 of 2 [0Bsd18001005D\r\n] Thu 12/01/2011 01:51:18 AM : [Elk ] ELK-WAIT Waiting for retry 2 of 2 [0Bsd18001005D\r\n] Thu 12/01/2011 01:51:27 AM : [ELK-ERR ] Get Topology

Has anyone tried using a Mi Casa Verde in combination with ISY to get Z-wave support along with a Insteon installation? Any technical problems such as conflicts between Z-wave devices and Insteon? Z-wave devices dampering powerline signals? I was envisioning using the ISY to manage the Insteon devices, setting up groups mostly for lights. Then using Vera for Z-wave, mostly lock control, camera control, alarm control with DSC. The Vera also has a PLM interface so I would link it with the load Insteon devices so there will be some links between the Vera PLM that the ISY didn't manage. Then using the Vera with an iPad to control the whole thing.

Reviving this topic. Where this issue causes a problem is in the app Conductor for Android. It displays number of devices with ON status in a folder and even though all actual lights are off it is showing a Controlinc as on. Would be great if we can have the option of disabling the status of a Crontrolinc since it doesn't mean anything anyway.

Will the ISY be compatible with the 2413S Dual-Band PLM with the current firmware or should we hold off for a while before buying it?

Or even if there isn't S/N reporting yet if the ISY could monitor 24/7 the network for errors it would alert you to possible problem devices or problems on a circuit. In this post in the Smarthome forum from jeffw he does that with Powerhome: http://www.smarthome.com/forum/topic.asp?TOPIC_ID=6035 Combined error reporting kind of like eventID in Windows and a circuit topography mapping out the devices would be especially valuable for troubleshooting and I would think indispesable for 3rd party installs. If an installer put in an Insteon system and needs to support it and a customer complains that something doesn't work reliably you could remotely connect to the ISY. You'd look at the error log that would be matched to the circuit topography. You could see if errors are on a certain circuit suggesting something on that circuit like a PC power supply, or if only happens only at night perhaps a CFL which is more likely on at night. If only one device on a circuit is having problems it migght suggest a faulty device. It would help the WAF who might know something is flaky but may not be able to tell you which light in particular is acting flaky. Would be nice to have it give you a score on the overall reliability of your system. It could read like 97% reliability if 97% of commands get through on the first try and you could see where the 3% failures are coming from and address them. I don't know how many ISY's are put in 3rd party installs but I could see that if you need to support an installation it would be a nightmare to support if you didn't leave something in place for error monitoring and trouble shooting.

In addition to designating breaker/circuits you could also identify which devices are on the same phase. You could unplug all your signallincs and then the devices that the ISY can still communicate with are all on the same phase as the ISY and those that drop out are on the other phase.

Does the hop count give any indication of whether a device is isolated or weak? Or is it just an indication that there are devices between it and the source of the command? When looking at the hop count is it the hops between two devices or between the ISY and the device? Or perhaps a tool to bombard a device with command's and see what percent of commands are aknowledged vs dropped as and indication of reliability. But I can see how a tree diagram of circuits, what phase their on, and identifying which are weak and then using that as a guide as to where to put signalincs would be great at beefing up the signal reliability.

I would like to see more tools to help with troubleshooting and finding line noise and interference. One suggestion is to have a tool to group devices by circuit. You would turn of one breaker and then it would flag those devices that then no longer communicate. Then you flag those all as circuit #1. Then turn that back on and switch off the next breaker. Those devices that go out are flagged as circuit #2 and so forth. Then you have a map of all the circuits on a certain group. Then have a diagnostic tool that test the signal to devices on a circuit devices between circuits which would help you pinpoint which circuit might have problems. Also could guide you as to where to put signalincs to bridge a week circuit.

Yes, that seems to work. When adding an IRLink button to the ISY I: 1. Did the "Link Management"/"Add button to IRLinc Receiver" command. 2. Clicked the set button on the IRlinc 5 seconds, 3. Issued the IR command from the remote. 4. Clicked the set button once for always on (twice for always off) 5. Then clicked okay in the ISY IRLinc window and it created the always on or off button.

Smarthome doesn't provide this information to their developers? Seems odd. What if it is done manually using the method outlined in the manual and then added to the ISY? Or if I purchased one with the remote and then added it to the ISY would it retain the toggle functionality? For making a theater scene with my Harmony remote to turn the lights off when the movie starts you need a non-toggle off button.

Seems like from the description on this page that the two buttons are paired like in a keypadlinc. Can the same procedure for a keypadlinc work with the IRLinc? http://wiki.smarthome.com/index.php?tit ... ard_Remote

Is there a non-toggle mode functionality for the IRLinc yet?

Still a bit of a kludge but how about connecting an IRLinc trasmitter to an IR receiving fan control: http://www.lightingdesignexperts.com/sh ... =290979009

Could one set up something with 2 inlinelinc relays and resistors linked to mutually exclusive buttons on a KPL? Each button would control a relay that would be connected in series to a resistor or a conventional fan switches set at a different speeds. The local control button on the KPL could be for 100% speed, then if button A is pushed it turns off the local control and turns an inlinlinc relay connected to a manual fan switch set at 66% speed. Then if button B is pushed it turns off button A and it's inlinelinc and turns on an inlinlinc attached to a 33% set switch.

Does the ISY support the IRLinc Transmitter yet? I added it to the ISY but doesn't look like it does anything.

The switch is the existing manual switch. I wired it in series to act as kind of a master switch/emergency kill switch. If the I/O Relay isn't on turning the switch wouldn't turn it on as they both need to be on. Sometimes my wife would forget and still use the manual switch which wont do anything as long as the I/O link is off. but would that effect the I/O linc's status? It is very intermittent though. I'll monitor more closely and look at the logging to see if I can more precisely see when this occurs. Thanks.

Will there be diagnostic functionality to find out how many hops to get to our devices or a network monitoring functionality to see if certain devices are requiring repeated messages or message not able to get through or getting CRC errors? Might help to pinpoint problem or weak areas.