Tmc

@Techman Hadn't tried rebooting, don't know why I didn't think of that. Since I have the Serial PLM that powers the ISY I figured I could reboot by unplugging the PLM, wait a little while, then plug it back in. OMG!! That fixed it! Now I'm getting tons of stuff in my Event Viewer. My IOLincs are working right! My Motion Detectors are working! THANKYOU! THANKYOU! THANKYOU!!! Seriously, Thank you for the help. All of you! -Tmc

*hear the relay

@Techman I have the IOLinc Option set for the Relay to track the contact state. I can here the relay toggle with opening and closing the door. In the ISY console neither the IOLinc Sensor or Relay show any change of state. Having said that, my Event Viewer doesn't seem to show any communications from any device in my house. Standard SwitchLinc Dimmers don't show up when activated. Is there some setting In the ISY firmware that got changed when I upgraded?

@Brian H Thanks for the suggestion, but I can see the LED turn on and off with closure and Opening of the contacts. The Mag Contact sensor wired to the IOLinc is on the door so easy to open/close door to test. The IOLinc was reporting status just fine for years until I upgraded from firmware 4.9 to 5.3.4 yesterday.

IOLincs are plug-in Modules. Did the Restore and it seemed to work as shown in the Event Viewer. But activation of the contacts afterward did not produce any captured events. Matter of fact, no events show up unless they're ISY sourced.

MrBill: Open the event viewer to level 3, and then cause motion. What's in the event viewer? On a quick test nothing appeared in the event viewer. Unfortunately I have to set this aside for a while. Will try that some more later today hopefully. Thanks!

This morning I followed the instructions in: 5.3.4 (Update) for ISY994 (July 30, 2021) By Chris Jahn, July 30, 2021 in Current Release Announcements to perform the manual upgrade again. Cleared Java cache and Apps and all that stuff. Didn't seem to change anything. Only difference was my userid and password were not reset and my programs were intact. Performed a factory reset on the Motion Detector, removed from ISY, reinstalled, did Write to device. I'm exhausted. Issues are: 1. IOLinc Status not reported (ie no change on ISY console Status even though device LED follows contact physical open/close). IOLinc #2450. 2. Motion Detector Status not reported (ie blank Status on ISY console even though LED on sensor blinks with motion). Motion Sensor 2842-222. Any ideas would be appreciated. Thanks in advance, Tmc

Thank you both. Yes, I deleted Java cache and Apps and downloaded the latest Start JNLP file. So my Console and firmware match, 5.3.4. For the motion sensors, they didn't have the green 1011 icons, but I put them in set mode and did Write Updates. Didn't help. Even put them in set mode, deleted them from ISY, reinstalled them, wrote updates, etc. etc. All with no effect. What's odd is the status page is blank, doesn't show any status at all. I wonder if I don't have the correct firmware? From the forum ISY 994i Current Release Thread I downloaded "ISY 994i Series including Z-Wave support". I don't have Z-wave, but the only other choice says for non PLM. I have a PLM. I didn't unzip the file to install, just selected the .zip file. Maybe I'll try downloading again and install again. Thanks for your help!

Sorry I didn't help. There's a "My ISY" button on the UDI Home page. Maybe that would get you a matching version of the Admin Console. Otherwise hopefully someone more experienced can help you. Good luck!

Did you delete Java Apps too? Doing that dumps the ISY Finder App so you have to download a new one that matches your updated firmware.

Yesterday I upgraded my ISY 994i Pro from firmware 4.9 to 5.3.4. Mostly it went okay. I had to disable programs that were previously disabled as noted in other threads. But programs using my motion sensors and IOLincs stopped working. Haven't worked on the motion sensors yet, but their sensed motion doesn't seem to show up. The IOLincs I can't get to work. I've deleted them from my devices, factory reset them, and added them back. They appeared to link fine. From the console I can talk to them as I've tied the relay to the contact sensor, reversed the trigger, and monitoring the LED on the device that all seems to work. What doesn't work is the contact status of the sensor doesn't appear in the ISY Console. This all worked fine before I upgraded. These autodiscovered very quickly. They are (2450) IOLinc v.36. I've searched the forum and haven't found discussions of similar loss of IOLinc sensor status. So I'm stumped. Does anyone have any suggestions? Thanks,

WOW! That explains almost everything! Even the problems I had back at item 5. in my original post list. Is this documented somewhere? At my work we'd call this "Tribal Knowledge." So yes, I was able to program other controllers and get Ramp Rates I wanted. Using the ISY Console doesn't trigger the changed Ramp Rate. It won't surprise you that MobiLinc won't trigger it either, since it uses the console control. Okay, so I moved the FanLinc Light Ramp Rate slider from about 26 seconds to 1 minute. Here is the Event Log: Tue 05/07/2013 09:16:02 PM : [ 21 D8 26 1] RR 12 Tue 05/07/2013 09:16:02 PM : [iNST-TX-I2CS] 02 62 21 D8 26 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 05/07/2013 09:16:02 PM : [iNST-ACK ] 02 62 21.D8.26 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 05/07/2013 09:16:03 PM : [iNST-SRX ] 02 50 21.D8.26 11.D0.DD 23 2F 00 (00) Tue 05/07/2013 09:16:03 PM : [std-Direct Ack] 21.D8.26-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 05/07/2013 09:16:04 PM : [iNST-ERX ] 02 51 21 D8 26 11 D0 DD 17 2F 00 00 01 0F FF 00 A2 00 11 D0 DD FF 1F 01 43 Tue 05/07/2013 09:16:04 PM : [Ext-Direct ] 21.D8.26-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 05/07/2013 09:16:04 PM : [iNST-TX-I2CS] 02 62 21 D8 26 1F 2E 00 01 05 0C 00 00 00 00 00 00 00 00 00 00 C0 Tue 05/07/2013 09:16:04 PM : [iNST-ACK ] 02 62 21.D8.26 1F 2E 00 01 05 0C 00 00 00 00 00 00 00 00 00 00 C0 06 (00) Tue 05/07/2013 09:16:05 PM : [iNST-SRX ] 02 50 21.D8.26 11.D0.DD 27 2E 00 (00) Tue 05/07/2013 09:16:05 PM : [std-Direct Ack] 21.D8.26-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 I have no idea what that means. Hope you do. After I did that, I unpluged the fanLinc and plugged it back in within 3 seconds. As you suggested, the 1 minute Ramp Rate is now effective from both the ISY console and MobiLinc. I've been using ISY-99 for about 4 years. I have never run in to this until after I upgraded the firmware to 3.3.10. I'm not sure what I was running before that. Think I upgraded about a year earlier, so not real old. Do you have a fix in mind for this? I saw you don't intend to provide any more updates for -99 units. Too bad. If I can run any more tests for you, let me know. I have a workaround now, just cycle power on units. For the InlineLincs I have installed, guess I can just cycle the circuit breaker. Thanks for pointing me in the right direction. -Tim

Lee, I have not been using a separate controller, just the ISY console to set the FanLinc Local Lamp Ramp Rate, and using the console to turn the FanLinc Lamp on and off after each attempt to change the rate. After attempts to set multiple different rates I used Tools and looked at the Device Table and Compared it to the ISY table many times. The tables always matched, and they never changed from one rate to another. When attempts to change the FanLinc local value appeared not to work, I also did a "Restore Device" a number of times, to no avail. I have not used the Event Viewer. I will do that, hopefully tonight, and post my results. I'll post the links tables too. Thank you for the suggestions, -Tim

Background; may or maynot be relevant: 1. Fall 2012 some major transient fried 25% of my controllers, most on same circuit. 2. Winter 2012 installed Leviton 51120-3 whole house transient protection. 3. January 2013 updated ISY-99 Firmware to version 3.3.10. 4. Started perodically replacing fried controllers. 5. Had trouble programming Ramp Rates on some devices, but didn't investigate. This weekend Prepared to install a brand new FanLinc. I have it mounted on a test board where it is powered and attached to 110 vac lights representing the motor and light. I do this so I'm not running up and down a ladder while programming, and if any problems. ISY discovered the FanLinc with no problem. Motor control works with no problem. The light will turn On and Off from ISY okay. The problem is changing the Ramp time from ISY has no effect. I use the ISY Admin Console from 2 different computers, one direct LAN and the other Wifi. Both seem to work okay, but just to be careful I cleared the Java cache again on both PCs. No improvement. From another post suggestion I did the "Query Insteon Engine" for the FanLinc. It is v.41 I believe. That had no effect. The most surprising effect is that if I unplug the FanLinc from house power, then plug it back in again, it magically uses the most recent Ramp Rate that I tried to program. Even though that rate was not working before I unplugged the FanLinc. Do you have any thoughts on what might be going on here, and what I can do to fix it? Thanks, -Tim Carlson