Crusty

Sorry it took me a few days to come back to this and provide the info about how to adjust Avast to fix this problem. For definition's sake, I'll summarize the issue: a recent update (early Sept, 2011) of Avast anti-virus has created a port problem in accessing the ISY's functions. You can log in - sort of - but are unable to see the current status of any devices and the authentication window keeps popping back up over and over. Here's the fix... -- Open the main Avast program window -- Click on "Settings" in the upper right to bring up that window -- Click on "Troubleshooting" (last item in the list), and open the "Redirect Settings" area -- Delete any port numbers or addresses in both the "Web" and "Mail" sections of the window. All areas should be blank and nothing checked. -- In the same "Settings" window, click on the "Update" option -- Open the "Proxy Settings" portion of the window -- Select the "Direct Connection (no proxy)" radio button -- Click "Ok" That should fix it. If by chance you notice that the main window tells you your system is now un-secure after making these changes, you can turn security back on from that same main window (look in the "Summary" section). Doing so won't un-do the port changes you just made. Now obviously, if someone has any of these specific options set to something important for their system for whatever purpose, you should be careful about using these instructions as it might harm other functions. In my case, I had never touched these things in the past, and they were set to whatever Avast had set them to. If you've done something different, you mileage may vary - a lot. Good luck with this. It worked for me and I hope it does for you.

BINGO! That's the winner. Credit to TJF1960 for suggesting antivirus as well. As it turns out, Avast had an update a few days ago, and something in that created a port problem that was the root of all this. I got on with their tech folks and clear it up. So Java update 27 seems fine - it was all the anti-virus' fault If anyone needs an explanation of the steps required to fix this, I'd be happy to provide.

Sorry to be continuing this issue, but an update... I uninstalled and then re-installed Java. Still have the same problem. I note that my older computer is running version 6 update 26, while my newer PC is running update 27. Any known issues with update 27? Or should I look elsewhere to fix this?

Looks like I've discovered the problem - it's obviously a Java issue on one of my PC's. I fired up an old notebook I rarely use this morning to check this issue, and sure enough, on that platform everything looks fine. No issue with the ISY. So now on to figuring out how to solve the Java problem. Oh joy!

I have to modify what I said above after playing with it for a bit more. It seems that I'm logging in just fine. After the ID and password window clears, the normal screen starts to load, and I see all my devices. But there is nothing listed for any of them under current status. Then, about 15-20 seconds passes, and the authentication window pops up again. I don't have to re-enter my ID and password, as they are already there. If I click "Ok" on that window, it clears, nothing changes regarding the current status column, and the authentication window comes back again in another 15-20 seconds. I can never get past that. I tried re-loading Java to see if it might be that - no joy there. Any other ideas?

I've had it up and running for just a few months, and frankly have only done a minimal amount with it. A couple of basic programs - that's it. Last night, I wanted to log in to check why a specific light didn't come on. I'm not sure what happened, but it kept asking me for the log in authentication over and over. I got distracted by something else and just closed it out. Never did log in successfully. Tonight, I notice that one of the nightly programs did not run properly. One did, another didn't. I tried to log in again to see what's happened. I can't log in. I've never changed the default log-in, but now it won't take it. Keeps coming back and asking for authentication over and over. I also note that in seeing the screen display of the program, there is no status noted for any of my devices. Maybe it has to see a correct log-in before posting that. I never paid attention to that detail before. Anyway, I can't log in and it's driving me nuts. I tried pulling the power for a few seconds and re-booting. Seemed to come back normally. I know I must have the right ID and password, because if I intentionally put the wrong one in, I get a failure notice. Any idea what's going on?

Thanks so much for the reply and ideas. I just ran a scene test four times. On the first instance, two devices failed, with one of them being the same one I received the communication error about the day before. The next three instances of the test found all devices successfully. And to the access point question; I do have two of them. And; aren't the new dual-band LampLincs supposed to serve the same purpose in regard to propagating the signal and even bridging the phases?

I recently installed a group of LampLincs and two ToggleLincs in a three-way configuration to set up a scene unifying the control of a bunch of lights inside my home. Once that was done, I set up a simple program on my ISY to turn these on at sunset and off 30 minutes before sunrise. Pretty simple stuff. And it seems to work fine. I noted this evening that these lights did not come on at sunset. Logging into my ISY, I noted a message about communication problems with one of the LampLincs in this group. I tested the device in question a few different ways - from the ToggleLincs, from the RemoteLinc that also part of this, and from within the ISY admin - and it seems to be working and responding fine. So the question is: if the ISY sees a device and detects a communication problem, does it not run a program that includes that device, thus affecting all devices grouped together in that program? Thanks in advance for any insights and help!

Thanks so much for the ideas Lee. The floods are the Insteon 2494MSWH, and yes, the keypads do manually control the on/off of the floods in the event that's desired. But what occurred after my post last night is what has me scratching my head. About two hours after giving up on this for the night, I was taking the garbage out, and the front floods worked just fine. So; earlier, they wouldn't work, later, they did. These floods seem to be a bit touchy - but it's probably just me, learning how things work. Crazy as this sounds, is it possible that having the ISY software open while testing earlier somehow affected this? That's the only difference I can see between the earlier/later scenarios.

Hi folks - newbie question here... I had a scene comprised of a sensor flood lamp, two LampLincs, two keypads, and a switch. When the sensor detected movement, all would go on, when it timed out, all would go off. Simple. Because I didn't want the switch controlled any longer by the sensor, I removed it from the scene. Tonight I notice that the sensor no longer trips when movement is very obviously passing in front of it. So did my removal of the switch from the scene create this problem? If so, how to best remedy?

I'm new to the forum and to Insteon and to using the ISY. A few months back I had a local electrician/Insteon installer put in a security light system around my home with Insteon flood lights, controlled by two keypads, linked to two LampLinc modules, and incorporating my front entry lights by replacing the regular switch there with an Insteon switch. I've been thrilled with the products and the system. For what I consider a reasonable expense, I now have a world-class security lighting system. I didn't opt for a controller at the outset, but have since bought, installed, and played a little with the ISY. There's not a lot of programing I want to do with it just yet, but there are one or two improvements that I want make to how the system works which I believe can only be done via programing. Problem is; I don't really understand the process of programing yet. I have years of creating Excel IF/THEN formulas, but this is something different. I hope that maybe I can get a little help to start. Here's the first thing I want to do... I have the following scene - FrontFloods_On/Off_Sensor 18.73.50.1 18.77.28.1 1stFlr_ExtFloods_Keypad 1stFlr_ExtFloods_Keypad.A 2ndFlr_ExtFloods_Keypad 2ndFlr_ExtFloods_Keypad.A Front_EntryLights_Switch Front_ExtFlood This links the two LampLincs, the front entry light switch, and the keypads to the front flood light sensor. Here's the problem: when that sensor is tripped, it turns on the all the associated lights, and keeps them on for 5 minutes after the last movement is detected (as set from the flood lamp control). I control my entry lights manually at present, even though they are on an Insteon switch. The problem is that if the entry light switch is already on and the flood sensor detects something, when the floods switch off after their 5 minute run, so do the entry lights. I want them to stay on until I manually trip the switch when I retire for the evening. So as simply as I can put this, I want to program the following... If the entry light switch is on AND the flood light sensor comes on, THEN keep the entry light switch on after the floods time out. If the entry light switch is off AND the flood light sensor comes on, THEN turn off the entry light switch after the flood lights time out. Make sense? (the second statement would seem to be unnecessary, as that's it's normal state) I'm betting this is all quite simple and has been dealt with here before. I'll just say thanks in advance to anyone who can help point me in the right direction.