elvisimprsntr

D'oh! I added my 2.0 adapter using the new insteon device method and manually entered the particulars. Now that I used the start linking method, I also see the four entries. Ugh! Now I need to retest everything! Elvis

A significant improvement in the tstat inteface! Just completed an extensive matrix of tstat 2.0 adapter testing with 2.7.8a. I did not create programs that use tstat state values. I will email the complete results/artifacts to UDI support. Summary of significant findings as follows: 1. fan mode not correctly reported and never queried. 2. Setting fan mode removes heat/cool set points from interface. Fan turns on as expected, but changes tstat to auto mode. Manual query of tstat reports heat/cool set points and mode as auto. Humidity is incorrectly reported as cool set point value. Second and subsequent manual query humidity reported as correct value. Manually set mode to off. Subsequent manual query reported mode as fan mode. Confirmed tstat in off mode and fan running. 3. Manually changed mode and fan state, then rebooted ISY after last test. Current temp, humidity, and mode are correctly reported. Fan mode is incorrectly reported as ON. Set points are zero. Switching to auto mode then back to program auto mode, set points are properly reported. Questions/Observations. 1. The failure to report set points affects applications like iLink Pro and eKeypad ISY from properly reporting set points. It seems like there are three different set points CLISP, CLISPH, CLISPC which contain stale values depending on which mode the tstat is in. This results in confusing and misleading information being displayed in iLinc Pro and eKeypad ISY. Perhaps the stale and/or inappropriate information should be cleared based on which mode the tstat is actually in. 2. I did see intermittant incorrectly reported humidity values, but problem does not repeat consistantly only in program auto mode as with 2.7.7a. (Read TStat 2.0 Adapter - Humidity Problem thread.) Not sure if this eliminates the 2.0 adapter as a suspect or not. 3. Can CLIFS be queried? 4. Can the stale CLISP, CLISPH and CLISPC be cleared when not values not appropriate based on mode? 5. I thought I read somewhere the fan mode option was planned to be removed. Elvis.

You need to send a note to be added to the alpha release notices. Read release notice at top of this thread. I think I read that you need to remove and re-link the tstat adapter. Elvis

OK I stand corrected. I can no longer use the ElkRP applicaiton to log into my ELk M1 Gold. I have had no problems until I upgraded to 2.7.7. The error message i get is "Cound not initialize secure connection." Once this error occurs, the only way i can clear it is to reboot my Elk. I am reverting back to 2.7.6 which I have not have any of these problems before. UPDATE: Well it appears to be a conflict between Windows MCE (and no I don't have the MCE plug in installed) and the ElkRP application. When I an watching TV via MCE and trying to run the ElkRP applicaiton, I get the error message mentioned above. I'm going back to 2.7.7 to re-produce the problem. UPDATE2: Problem duplicated with 2.7.7 and conflict with MCE running. Don't run MCE when trying to run ElkRP application.

I'm trying to download the weather module and keep getting kicked out of the checkout process. It's not a problem with my account. I have had no problems using google checkout before. I give up! Oops! You are currently signed in to a Google Checkout account that does not have permission to perform the specified action. Please sign out of all Google Accounts, and then sign in to the appropriate Google Checkout account before retrying the desired action.

in my isy99i the version number is 2.7.7

Been running 2.7.7 alpha for a couple of days, interfacing using iLinc Pro and eKeypad ISY. Also acceing via the admin console. Once significant change I have noticed is the Controller/Responder and Manages/ManagedBy associations tree make a lot more logical sense now. Keep up the good work! Elvis