blueman2

My integrated Venstar (2491T1E, firmware v2.4) is working flawlessly with 3.2.4.

Thanks! I will check tonight!

I had something similar happen with a particular brand of CFL bulbs.

The humidity on this unit always reads about 85%. All the time. No way my house is that high for humidity during the winter. Anyone else seeing this type of high reading?

OK, I am home and able to do more testing. I can confirm that all the "set options" check boxes work exactly as labeled. If i check 'LED on' it switches the LED on the SWL Timer. If I switch "LED on TX", I can see the LED flash off/on when it is communicating. These values also survive closing the "set options" box and re-opening. So all good there. The only thing not working is the Default Timeout. It keeps going back to 255. As I open the set options box, it first starts at 0, then reads from the switch (I see the switch LED flash), and it goes to 255. I set it to 5, see the LED flash indicating it is getting communicaiton. I close the set options box, then open it again. I see the LED flash when I open the box, indicating I guess reading the values. But the value is back to 255. Because the switch is linked to my whole house fan, I cannot actually turn it on to see if it is perhaps responding to the Default Timout value, but perhaps just not reading it back correctly when reopening. Maybe this weekend I can disconnect from the fan and test it fully.

I have not done this myself on the 2476ST, but are you saying the following (from the manual) does not work? Ugh if so!

My 2476ST is v.40. Teken, I am curious, have you tried to do a factory reset on your SWL Timer? Maybe they need to be unlinked from ISY, factory reset, then relinked. A factory reset should return everything to the original settings for 15 minute based and 1 hour per paddle click, for example. Here is my log when I try to update the SWL Timer 'timer' option to 5 minutes from the 255 value it shows: Tue 04/10/2012 10:53:26 AM : [All ] Writing 0 bytes to devices Tue 04/10/2012 10:53:32 AM : [All ] Writing 0 bytes to devices

- Installed 3.2.4 no problems. Upgraded from 3.2.3. - Got ability to edit folders back (great!) - Initially, got "request failed" on setting options for SWL Timer. But I removed the device and re-added it manually. It then worked!!! Has a weird 255 value in timer, but I will play with it to see what it does. edit: everything works with SWL Timer except the timer value always reverts to 255. Frankly, I am not sure this switch will even support changing the value, so we may be chasing our tails on this one. But thanks so much for the effort on this legacy module (no longer being sold). I will play with this more tonight to see what impact the timer setting has, if any.

Upgraded to 3.2.3 from 3.2.2 no problem. But I continue to get the same "Request Failed" when setting options on my timer switch (2476ST), same as Teken.

I have had a recurring problem for the past 4 months since I got my ISY-99i. About 1/2 the time I launch the Admin Console, the 'current state' of devices does not display. I close the console and my browser, clear the java cache, and about 1/2 the time the current state shows up again. When it still does not, I just wait a couple ours and clear cache again and try again. Mostly will work then. This is happening on all 4 of my computers. None of them have firewall turned on. None of them have any avast type software that messes with ports. I do have McAfee Anti Virus installed. But even when I turn that off, the problems remain. Any ideas what is going on? Very frustrating to take 5-10 minutes or longer to finally get the Admin Console working.

I have the Venstar with v2.4. I upgraded to the 3.2.2 firmware on my ISY-99i. Finally got everything working both as a responder and controller. By the way, my Venstar shows up as v.95 in the ISY screen.

That is what I thought. Thanks for the great help!!!!

That explains it! Now another question. How bad is it to set up a daemon program to constantly query status of these devices as a way to keep them up to date? I assume this is not a good thing to do.

Lamplinc is 2856D2 (Icon) 2 pin v.38. It is Blue in the My Lighting tree. I will check the device communication log and post in a bit. Thanks

I am using several lamplincs. One of the nice features of these is that even when turned off via a controller, you can still turn the lamp on by just using the lamp switch. The lampliinc senses when you turn the lamp off then on again, and turns the lamplinc on. However, the lamplinc does not send a signal back to the ISY-99i saying it is now on. ISY shows it as off. Of course, I could constantly query the device, but that would waste a lot of cycles on the ISY, right? Is there a better way to ensure the ISY knows what the status of the lamplinc is? The reason I need this is that I want to have an LED on my keypadlinc light up if ANY interior light is on. Lamplincs that are turned on my switching the lamp itself are making this hard to do.

Thanks for the reply. I think I solved the issue. I turns out my 99i was linking to the wrong gateway address. For some reason it chose a gateway address of one of my WAPs. I manually set the IP, mask and gateway addresses, and it now is working as it should. Thanks!

I am a new user here. Just got my ISY 99i/IR yesterday and have been trying to set it up with a single device to learn how to use it. I have it connected to the 2413S using ethernet cable to port A. Power supplied to the ISY unit. ALso have a 2450 relay plugged in as a test unit. I was able to get the system to see the 2450 and control it (yea!). However, whenever I open up the Admin console, it goes into an infinite loop with a pop up box labeled "Linking" which says in the box "Please do not power off/unplug the system or make adjustments to the linked/attached devices". This box ran all night long and it still running, going from 0 to 100% again and again and again and again. Running the latest non-beta firmware (I think 3.1.15). Any guidance? I also did update to latest Java.