ELA

I am getting a red LED on the ISY99I about every 15 seconds. The error log reads like this: In the configuration screen it has a red asterisk in front of the NTP server "pool.ntp.org" With all this it seems it should be obvious what is wrong but it is not to me? I suspect that when we had to replace our wireless router a few weeks back is when this started. Please let me know how I can fix this? The ISY99I seems to be operating fine otherwise.

Thanks Michel, 1)The address had remained the same. 2) I was not running the old Console - the new one shows the correct version once open. (after satisfying the ISY finder) 3) I stopped using the .jnlp and instead used the http://isy/admin and that works fine. Thanks for your help

Hello Michel and thank you for your kind reply, During the upgrade it failed and I used the line below to make it pass - even though I am on a pc. So I am for sure using the original address that was used previous to the upgrade. Are you saying that the ISY might have automatically been assgined a new address at boot and that is now different then the original I had used before the upgrade? If so then why would it work when I select the old address? I will check the ISY to see what address it is now at vs. old address. I am very confused by the constant recommendations to clear the java cache? As far as I know- I have been doing that constantly without a positive result. Can you explain or point me to an explanation since I am not familiar at all with java? Why so many options to reconnect as posted in the first post? Are they all created equal?

I upgraded from 2.7.15 to this version. This is the first update I have done and felt a little lost as to what I was doing but followed the directions and it seemed to go ok. I did have an issue of having to point it to my http address. Now when I start up using the last option in this list: *********************** . IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. http://isy/admin - applet (Windows only) b. http://isy/admin.jnlp - Java application (Windows only) c. http://your.isy.ip.address/admin - applet d. http://your.isy.ip.address/admin.jnlp - Java application e. http://www.universal-devices.com/99i/2.8.13 - applet f. http://www.universal-devices.com/99i/2.8.13/admin.jnlp - Java application ******************** if says not found and presents a table of available HTTP addresses with mine as the only available. If I double click on my address it loads and all is fine. I have to do this each time I start up so I feel something is a miss?

Lee, Would it be worthwhile to then run individual on/off commands direct from the ISY to only the devices in question and record using the Event Viewer (set at level 3)?

I am slowly getting familiar with the communication protocol (with a long way to go). When I looked at the log I saw a msg. fail each time that did not apprear to have anything to do with the lights that failed the scene test. I also thought that there was no response from the lights that the op. said did fail the scene. This much seemed to make sense to me. What I do not understand is why the scene test states that it passes [suceeded] on the two lights that are failing??

Thank you both for your responses. I read the manual yesterday right after I posted and now understand that scene test only sends off. NONE of the scenes that I replaced the switchlinc dimmer into worked. None of the lights in the scenes turned on. (When activating each scene "on" from within the ISY.) That particular switch was in 4 different scenes and none of them worked (activated via the ISY). Yet the scene test reported a positive result! Apparently the "replace with" did not work very well I removed the new switchlinc from one scene and manually relinked it from within the ISY and that scene then worked fine. I then removed the switch all together and used auto detect to reinstall. Now I had a v3.8 for the switch. I then manually relinked this to all the scenes one at a time. Now they all work fine. I am not very happy with Insteon at this point. Lots of pretty iffy stuff going on here. I am sure some of it can be put down to my being a roukie but this system is definitely not for anyone not will to spend a lot of time once issues rear their head.

Thanks for your response sub-routine, No green arrows (all updates were done). I would not care if all I missed was features such as beep. I also posted in the Smarhome Channel - adding to an old post of mine. The problem is that this new switch is having issues with Scenes now. From the event view I posted over there it looks like it is sending an "OFF" command where it should be sending an "ON"?

Hi, I have gotten so used to working with motion sensors and adding them manually that I did the same when adding a replacement Switchlinc dimmer. It now shows as a v.00. Can this have a negative affect on its ability to work in a scene? I wanted to replace an existing switchlinc with a new one. Now that I have done that it no longer works with the scenes it was associated with previously. I have manually adjusted its scene levels and Ramp rates via the ISY99 to attempt to fix but it continues to fail to respond when the scene is operated. Now I am wondering if it is the ver 0.0? If so will can I restore it using the autodetect somehow?

Hi realhavok, I recently encountered a communications issue and feel that I now have a more reliable setup. The reason I am responding is because you asked about moving your Access Points. Keep in mind I am a rookie As part of my troubleshooting I diagrammed all the circuits in my Insteon circuits. I included all device locations (what phase they are on) and Access Points (or Dual Band devices) in particular. This allowed me to see where the RF coupling might not be optimum (even though the built-in Access point test worked). It also allowed me to see where the powerline signal may have to travel a long distance without encountering another device (or repeater). I feel that relocating my Access Points based on what I saw on the diagram was helpful. Pay attention to whether there are any large metal objects between the Access points.

I realize this tread is a little old but I had some information to add and also to ask a question about the battery low threshold value. First a real world data set: I have just had to replace a battery in one 2420M (ver 2.0). The ISY99i running version 2.7.15 reported the battery low. I noticed the double blink on the units LED for a day or so before measuring the battery voltage at 7.2Volts. I have read IndyMikes tests on battery thresholds. Very interesting. It sounds like there is no defined low battery battery threshold value when testing at the battery leads? IndyMike indicated power source impedance variances affected his test results. Surely there is a defined threshold internal to the unit that the microcontroller is set to activate a low battery warning at. It would be nice if we knew this threshold. We should then be able to define a test condition under which to test at the battery terminals (or externally). - With the 2420M in a known condition - or at known current demand value.