C Martin

I see that this thermostat is not supported yet. Any idea when it will be officially supported? The ISY # is: 2491T1E Clarence

H2R, Thanks for the info. I was actually able to restore a 3.1.5 Backup but my programs are not loaded. All of my devices are present and my variables also. I suspect that there are some other issues at play here also. Michel, I want to thank Ran and Darell for all of their support today. They both worked a long time trying to resolve my problem. it is this dedication that makes UDI the company that we users want to support. There seem to be links still in my PLM. Too bad I didn't use more scenes. Again, thanks. Clarence

I did that once more. No Dice. The results are the same. Clarence

I just tried re-setting my PLM. No Dice either. Clarence

at first, 3.1.6 I then tried 3.1.5 No Dice on either? Could this be a hardware problem? Clarence

I was doing some programming and finally had to reload my ISY with a previous backup. That didn't work so I had to re-set my ISY. My opening window came out all messed up. You can see that all of my devices show up in a messed up order and I can't seem to fix the problem. Any help would be appreciated. By the way the unit came up in "Safe Mode" several times. The devices don't show status either. It's weird, because the links seem to be enabled.

OK, I am stupid. I actually caused this problem. I toggled the auto write update off. The problem turns out to be operator error. But, I will check the wiring -- or retest the non-write errors if the companion switch is turned on problem I apologize for creating my own problem. Thanks, Clarence

I am switching a incandescent flood. the number is 2474D

LeeG, can you please explain what you mean by wired correctly? Michel and LeeG, I have had my in-linlink in service for more than 6 months. It worked without exception for most of that time. I only started having problems recently with the versions starting 3.1.5. I had another event this morning and I did right click and it was able to update the device. My in-linelinc has 2 program changes per day and that is where the problem is coming up. If I didn't need to use this device, I wouldn't. But I have to because of the "No Hot wire" situation in my closet area. The other problem occurs if the companion switch is turned on. It won't allow updates in any case (manually or automatic), unless the switch is turned off. I hope that someone else can verify or confirm this scenario with the updates. Clarence

There are rumors that there will be a Venstar Touch Screen with an Insteon module, available soon. I hope that they unlock more capabilities with that unit. I have decided to wait for now. I still want to hear about any Venstar issues or comments. Clarence

Michel, I did some testing today. It seems that I need to make sure that the Companion Switch is in the off State for the updates to take place. If the Companion Switch isnot off (Verified by the LED) then the updates don't seem to happen. This is not very consistent. I will monitor events and update any other problems that I might have with these. FYI, I have a program that changes the dim values for the in-linelink, depending on the time of day. So there are updates that are sent to the in-linelink device. My example shows the Scenes that get changed by my program. Clarence

Thanks Michel. Clarence

I have been experiencing the following problems since version 3.1.5 (see picture). I am using a remote 2475D in-linelinc . If I go to the closet area and activate the companion switch, then I can trigger the write to the device. is anyone else using any devices like these and having similar problems? Clarence

I know that the Venstar thermostat has had issues in the past. I am in need of a new thermostat and I need to find the latest info on how the new venstar thermostats are performing with the ISY. Exactly what are the features that are available with the newest upgrade of 3.16? As a wrap up: can a program or variable be triggered by a venstar stat value? can we read remote temps via the venstar? are there any venstar values that can be changed remotely? Clarence

sanders2222, I am truly relieved that someone else has seen this problem. I was beginning to question my sanity. The problem that I found is that this is a situation that is not consistent. It seems to come and go randomly. Chris at ISY addressed this problem once but I think with the randomness or inconsistency of the problem the investigation may have been dropped. Clarence

I just ran another test and the results don't match my previous post. I set up several variables for this test. If $State_16 is 1 And $State_17 is 0 And $State_18 is 1 Then $State_19 = 1 Else $State_19 = 0 This test actually works - contrary to my previous example. I am still trying to figure this one out. I still stand by my previous posted example.

I found this anomaly again. It appears as though you need to put multiple if statements into Parentheses. I had a program that checked the status of three conditions that failed after upgrading to 3.1.5, and it fails when you don't enclose all of the statements in Parenthesis. Michel, I don't know if you remember that I mentioned this recently with a previous 3.1x update. It's back in a big way - and I was baffled for a while until I finally enclosed all of the if conditions in one Parenthesis. This is what I had to do: If ( X10 'M9/On (3)' is Received And $sDaytime is 1 And $sClosetOveride is 0 ) Then Set Scene 'Scenes / Closet Motion' On Wait 60 seconds Set Scene 'Scenes / Closet Motion' Off Else - No Actions - (To add one, press 'Action') This program is used to over ride the Clost Motion program and will run for the time in the "Wait" Line. The "Closet Motion Program" is also stopped and the "Closet Overide On - Day" program is also reset to a False status. Clarence

I have not had to make additions to my system for a while. I was in the process of adding some new devices when I noticed the Zigbee Options. Can you expand on what they are or will be used for and what devices are being supported?

FYI -- my experience so far... I like some of you, use my ISY to save resources. I just tried some Dimmable LED replacement lamps. I tried both a PAR 38 and a PAR 30 Feit Flood Lamp. I must say, the results are not working for my application. I tried using Dimmable lamps because of the application they are in. I use these lights in a closet area and at night they come on at 25%, just enough to see to pass through the area and not wake anyone up, even the person passing through. Results: Using the LampLinc Dimmable switches - They flicker at the levels between 60% to 15% dim levels. Odd though, at 13% they don't flicker. Their Flood characteristics are too narrow, even though they a classified as flood lamps. I also use them in a kitchen area (over the sink) and the PAR 38 works well for that application - no ISY control there, although I could. They do not have a warm color. I guess I will, have to wait for the LED technology to catch up with us in the world of Home Automation. Has anyone had a better or any other experience with these devices?

Sorry, I assumed the Latest Version. My Bad. Using variables has enhanced the ISY platform immensely. Clarence

The $State_1 is a variable that you need to create under the "Variables Tab", and that would be a state Variable. Clarence

Hi Chris, I forgot to include the version number: 3.1.2. Clarence

Hi Chris, I thought so too. But from what I saw it is not consistent. It works sometimes and other times, it doesn't. It had me very perplexed for a while, until I re-looked at my code and added the Parentheses. It acts like it evaluates the first two and then nothing more. But again, it's not consistent. Clarence

I've never had that happen. The re-evaluation of the "OFF" state does not re-trigger the program to start again, and if it does, the motion sensor is not triggered "On" again. The program actually works well. The only problem I had was when there was no Parenthesis. The evaluation did not take into consideration all of the "AND" Statements.

I've never had that happen. The re-evaluation of the off state does not re-trigger the program to start again, and if it does, the motion sensor is not triggered "On" again. The program actually works well. The only problem I had was when there was no Parenthesis. The evaluation did not take into consideration all of the "AND" Statements.