matapan

I was able to access my ISY-26 without resorting to brute force methods. Here's what I did: 1. Plug in the PLM with the PLM connected to the ISY-26. 2. Power up the ISY-26. 3. Once the boot sequence is complete, unplug the PLM from ISY. 4. telnet into the ISY-26. 5. Copy and paste the MAC address returned from the URL: http://your.isy.address/desc for the user name and password. 6. For me, ISY-26 appeared to hang. After a few minutes, I plugged the PLM back in. 7. Open a new terminal session and start a telnet session. Login as admin/admin. This appeared to have worked for me. YMMV. But it is different enough from the wiki notes to worth mentioning here. The key seems to be related to starting up ISY-26 with the PLM plugged in, then unplugging the connection to the PLM just prior to the login via telnet using your ISY's MAC address.

So the MAC address I obtained from Wireshark matches the one I obtained from the ISY-26 itself, using the following URL: http://your.isy.ip.address/desc It's in the format: 00:03:f4:02:nn:nn I'm wondering if UDI has a list of the serial numbers for ISY-26 and the MAC address associated with each unit.

Thanks for the suggestion. I have the PLM disconnected while attempting the telnet session. I've entered the MAC address in the following formats as userid and password: xxxxxxxxxxxx xx:xx:xx:xx:xx:xx xx-xx-xx-xx-xx-xx No joy so far. Anything else to try?

Well, I was able to get the IP address and the MAC address of my ISY using Wireshark and performing a capture off my Macbook's ethernet port with the ISY connected directly to it. Unfortunately, the MAC address I entered as the username and password did not allow me to access the ISY via Telnet. Keep getting an "authentication failed" error. Any suggestions on how to proceed further?

For this particular unit, I do not know its IP address.

No ISY finder comes up when I load the Admin Console. I cannot login, so the Help/About dialog cannot be accessed.

Hi, I have an ISY-26 device I cannot access via Admin Console. I do not know the device's admin account name or password. The factory reset procedure described on the wiki describes how to obtain the MAC address of the ISY so that you can telnet in to the device and perform a factory reset. What I haven't been able to figure out is how to obtain the ISY's IP address. My router's connected devices table doesn't appear to list the ISY; the count of connected devices doesn't change when the ISY is connected or disconnected from the LAN. Does anyone have any suggestions on obtaining the ISY's IP address?

Can anyone with one of these devices confirm whether or not this device works with the current firmware version for ISY-99i (3.3.10)?

I have a mix of v.1.0, v.1.3, v. 2.x, v.4.x, v.5.x devices, with a PLM v.63. Does the capability to support extended messages allow any such devices to repeat messages the device itself doesn't support?

For those with a mix of old and new Insteon devices, which support the ever-evolving Insteon protocol, how does one know if one has a configuration which supports the mix of devices? Is this a function of the PLM version one is using?

What steps does one need to follow when setting up ISY to run on a home network with internet service subscription? Can anyone speak to how a router should be set up to run in this environement, if it even works? Thanks.

I've been considering purchasing SHN EZX10RF device to use with X10 remotes and motion sensors. Any comments on how well this is supported with ISY99? Also, how reliable are X10 Rf only signals on an otherwise Insteon only network? Do motion sensors work well under this arrangement? How about keychain remotes?

Received the following errors during upgrade of ISY99i IR/PRO from firmware version 3.2.6 on a Macbook 5.1 2008 version running OSX 10.7.5 and the latest Java version using Safari or Firefox: Upgrade failed: Failed uploading file (reported written size is invalid Socket Open failed. java.io.IOException: Broken pipe Progress status for upgrade went to 2% before failing. Socket open error also came up during a lengthly backup process. Looks like the session timed out. Any suggestions? All the Java related issues are really getting old.

Is there any consideration given to developing an Admin Console which does not use Java? Given the recent news related to Java and the security issues related to it, and the trouble Mac users have using Java in general, would it be better to migrate the application to something else?

I found the original posting to be correct when fabricating this cable: RJ45 RS232 DB9 1 ------2 8 ------3 7 ------5

Thanks Xathros. I was originally opening with Safari. Firefox formats it as you described.

The ISY994i product page on the UDI site describes it as extending the capabilities of ISY99i. Are there any Zigbee products currently supported by the controller? The Insteon lock exist, but I'm looking for a lock which reports back actual lock status. I assume there are some Zigbee based locks which would be supported by the new controller. Is this the case?

Thanks for the tip, Xathros. The page returned by the link is raw, unformatted data. No ID number appears to be associated with each program. Are the program ID's implied, meaning they start at 1 and increment from there in the order the programs are listed in?

I began using an iOS program called "Roomie Remote". This universal remote application supports the ISY-99. In addition to toggling lights and devices, it's supposedly possible to run programs, provided you know the program's "number". Is there an easy way to expose the ID number associated with any ISY program?

I'm sure this question will come up. What happens if one attempts to replace a 2476D or S with a 2477D or S? Will the replacement device just show up as an unknown device type? Will the basic on/off commands work? If not, what is the upgrade path here, as the ecosystem of devices evolve? There will be people who will look for replacement 2476x's to repair/maintain their existing systems, but I have to wonder how many people will try taking the path of replacing their old device with a new one when their switches fail.

Would UDI consider updating the firmware for ISY26 to support some of the most basic dual band products? Smarthome is discontinuing its powerline only Switchlinc Dimmer and Relay models and replacing them with the dual band products.

Thanks, LeeG. Replacing the battery was indeed all that was required to restore the device's functionality. Would it be helpful to add this info to the 2420M ISY-99 wiki page?

What is the best way to restore a motion sensor device whose battery went completely flat? Is the best practice to replace the battery, then restore the device? If so, what is the restore procedure for this battery operated device? Do you put the device in a specific mode? Or, is it best to delete the existing reference to the device from the device list, then add it back? That seems to me to be a big hassle, since all the existing reference to the device in programs and other things would all have to be recreated. Any opinions?

Isn't the path of least resistance and greatest ROI for Smarthome or a vendor supporting Insteon to design and release a two way door lock? Personally, I don't quite understand why Smarthome would use resources to develop a Fanlinc and not a door lock. Door locks are really the big hole in the range of Insteon devices supported. I purchased a Morninglinc to try it out with the Morning Industries lock. The Morninglinc's one way communication design doesn't lend itself to using it in high security applications. I have also had some issues with the deadbolt on the lock fully retracting consistently.

I think a lot more devices that don't use a serial port or IP can be controlled this way, using gateway devices like IRTrans.