smurt

Disregard my last post on NEW ISY994ir/PRO and Venstar. I upgraded to v3.3.4 and that seems to have resolved the issue

Just swapped out my ISY99i with a new 994ir/pro. everything is working good except my Venstar t1800 thermostat. I have it linked can see it on the admin console can sent changes to it from my iPhone and directly from the Admin consol but am not able to get the changes made at the thermostat back to the ISY 994. All was working fine prior to the switch, (im pretty sure).... I have removed the T1800 from the controller and re-added it sever times. I am running v 3.2.6 and I have taken my remotelinc around the house, (themostat and beyond) and it works fine. Thoughts? I couldn't find any specific posts related to 994i and Venstar so if this has already been discussed I would appreciate the link

Will you add the new Leak Sensor (2852-222), due out in December, in as a supported device that can be added through link management function?

Thanks for the reply.... Guess I never went in to change mode since earlier version. So it is executing whatever is set in the Thermostat. your right, why would you do that when you have an ISY you can program. Would have been better to leave it out i suppose. FYI, Smarthome sent me an complete setup to replace the existing T1800 and adapter. It gave me hope for a few month then started doing set point resets on it own again. I love this Thermostat but it is not something I would ever recommend. Too dangerous for me to put into someones home who wasn't a tinkerer and did have computer skills.

I installed 3.1.10 and month back and yesterday I went in to change the thermostat mode from Auto to Heat. When I did I noticed the addition of some new selections and wanted to know where they came from and if there was any specific documentation on the settings and how to use them. The original settings were: Off Heat Cool Auto Fan These are the settings documented in the Venstar manual. The newly added setting are: Program Heat Program Cool Program Auto I did set the heat to Programmed heat and when I checked the log saw that the Heat was adjusted up at 6:35 am, down at 8:35am and up again at 6:35pm so the addition of these must be tapping into the programmable thermostat capability. If this is possible then it makes me wonder if these wild swings in set points several of us are encountering are created in some way by confusion between Heat and Program Heat.

Looked through the logs and only found one question on this error code and it was, WHY is this error not in the UD error Log. I have a more basic question.... What is this message and how do I resolve it. I checked the error log and in one house i am getting 4 or 5 a day and in another I am getting 100's per day. The message appeared for the first time in my AZ home after I upgraded to 3.1.10. The other house had been getting some over the last year but with 3.1.10 they have increased. Cant imagine this is good for ISY performance.

good luck. I have been working this problem for over a year. It reared its ugly head in the Summer of 2010 when the system set my Cool setpoint to 16 degrees. this is a second home and we are not around much in the summer. I caught it after 2 days. It was 110 outside and 60 degrees inside. luckily no damage was done to the air conditioner, just my pocket book. I have since created a program that catches these set point changes and resets the Thermostat to acceptable levels. I worked with Smarthome for a number of months and have passed info to the UD team on and off but no one can figure out what is causing this. its still happening and I cannot find any kind of pattern. I have even had conversations with my security company to see when they probe hoping it may occur at the time of a spike.

Lee, Thanks for the post. I followed your "Show Links" suggestions but did not find a compare function in any of the drops downs nor was there one in the SHOW LINK function itself. Given that I went ahead and performed a "Restore Modem PLM". No luck. It surprises me that by deleting all the links from my RemoteLinc then went re-adding a device to a specific button on that Remotelink that the responder/controller relationship would not have been set up at that time. When I set this up llast year that is all I did and linking it this way automatically created the connection and the links. Anytime the motion sensor turn on a light or a button was pushed on the RemoteLinc signals were sent through the ISY and reflected in the logs and status shown on the admin. console itself. I never had to do any other work to create the Controller/Responder relationship. Right now I am thinking that even if I took everything in my home out and re-added it I would not get see a difference. Steve

I had no trouble loading the new release and actually went from 2.7.15 to 2.8.12 then quickly on to 2.8.13. For the 2.8.13 update I had to follow your recommendation for MAC users and add the IP address. EVERYTHING is working.... Motion, RemoteLinc, KeypadLinc, IOLinc, Ezrain/Ezflora, SwitchLinc Dimmers, LampLincs all functions and can be accessed via my programs or a RemoteLinc, Motion Sensor or KeyPadLinc. But not all of them are communicating their actions back to ISY 99pro. Motion Sensors are working and actually seem more responsive than before. they turn on the light but within the ISY admin console the status of the light shows off nd there is absolutely no activity coming across the event viewer. If I walk over to the light switch, turn it off then on again the statius then shows ON in the console and all the associated activity is received by the ISY and displayed in the Event Viewer. This same thing happens with my RemoteLinc. All the linked lights respond as expected but nothing is transmitted back to the ISY. ISY thinks nothing has happened. Suggestions???? I have tried two different AP's v2.1 and v2.0. I have removed my RemoteLinc, factory reset it and reloaded it back using the RemoteLinc method and using the "Start Linking" function. I have cleared java cache I have powered down my ISY Pro...... Im lost. I cant grasp how my finger on the on/off and ramping up a switch is any different than my finger on a remotelinc button which inturn ramps up a switch... < how does it know i didn't turn this on directly. it physically looks the same.

Michel, where should I send the excel spreadsheet? i have gone through my log and captured several instances of the setpoint problem. If you can send me an email I will attach the file and send it to you.

Michele, is there anything in my log that would be of help. Since I posted I have had an occurrence of both the cold and hot setpoints being set to 47 and 214 degrees respectively. Let me know.

Michel, did you ever hear anything back on this from Smarthome? Are we sure this isnt an ISY problem?

My first occurrence took about 3 months which is the situation I refer to in my original post. I replaced the adapter this fall and it has worked fine for about a month and a half now it is happening again. So for some reason it takes time to start fouling up. It is random and does seem to happen at any regular interval. I can go two or three weeks without having the system generated setpoint change.

Just a word of caution. Last year I added the T1800 in a house I have in Arizona. This is not a primary residence for me so I all the Lights, Irrigation and Heating/Cooling automated then manage the house from my primary residence logging into my ISY. I went a few days without monitoring the house and when i finally brought the system up I found the house temp was at 60 degrees. generally not a worry except this was in July and the outside temp was 110 degrees. Upon investigation in the log I found a "Cool Setpoint" for 37 degrees was sent by the T1800. The Air had been running full blast for about 60 hours. I quickly turned the thermostat off and caught a flight to AZ to have the Air conditioner checked out. Everything was Ok but had that Setpoint been HEAT chance are good that the house would have been burned down by the time I found it. After some research I finally figured out how to guard against this programmatically IF (status Thermostat - Main > 89 (Cool Setpoint) or status Thermostat - Main < 84 (Cool Setpoint) THEN Set Thermostat - Main 58 (Heat Setpoint) Set Thermostat - Main 87 (Cool Setpoint) Send notification to MY EMAIL I do the same check for the heat looking for Greater than 65 Less than 58. This has given me some piece of mind but there are still points of failure that worry me. I have had Smarthome send me a new 2441 adapter but that has not solved the problem. Last night I took two more hits. The program worked fine but I would really like to find the cause of this problem and solve it. I have ruled out the 2441 but could it be the Thermostat or worse yet could it be the ISY 99. I am not sure how I am going to isolate and fix this but if I cant I may reach a point where I just take it back to a standard controller.

One more question on communication. I have decided I need to add a couple more access points to improve communication into my garage. Does any one know if I can link them all together as one or do they only link as pairs. Wonder if strengthen the accesss point network will in anyway help my insteon communications.