Stowaway

I use option #2 (EagleEyes) with an EZX10RF to receive/distribute the signals. However, I do not link the sensor to any devices, I use trigger programs in my ISY to start a timed response to the "on" signal. I ignore the off signal. I have found this works well for me and I don't have to tap-tap anything! I am currently testing the 2420M.

Michel Now on the next morning, the time on the log and viewer are synchronized. I did not save the log or viewer files as I should have for you. I know this all seems pretty suspect and I did check back and forth a number of times yesterday to confirm what I saw! I am not crying wolf, and I don't expect you guys to do anything until somebody else reports this or until I can recreate and get you the files....

Yesterday I updated my 99pro to 2.6.8 without any issues as far as I could tell. However I have had some events executing at incorrect times. I usually wait for 24 hours to ensure that everything has been updated and synchronzed before I try to adjust anything! It has now been 24 hours and I just found something odd that I hope someone else has found and resolved... When I look at the time on events using the diagnostic event viewer and compare the time to the log it shows the same events executing at times two hours apart! The time on the configuration page is correct and synchronized via NTP. The DST box is checked and I have tried unchecking it as well. I have not determined which time is being used for event execution but I clearly have some confusion.... Any solutions or Comments?

I have not had a problem since the NTP sync was built in! Using the default pool.ntp.org my isy is always within a second or so of my PCs using the windows NTP server

Hi Mke As i noted in my previous post my install was locked up initially. This apparently was related to the ISY going through all of the programs after the install before "releasing" the admin console to any new input. The console is now working and since one of my early AM programs was a QueryAll the status of all my devices has been updated. this was probably my big start up issue after the update was completed.

I installed 2.6.7 with no apparent issues after backing up my previous set up etc. I cleared my java cache and restarted the admin console. All looks OK but when I attempt to make any changes or do anything within the console it locks up and the cursor hourglass indicates it is working. This continues until I exit the console and empty the java cache and restart - then it does it again. I have sent some screen pixs separately to Michel on this, I cannot tell if the other programs are running since the console is effectively incapacitated! Any comments or recommendations accepted!!

I would like to reiterate what Mike said about the junk in old links, Having gone through the same process of saving old HL created links and then piece-by-piece cleaning out devices, I finally had to follow the original advice of all the veterans here. I was tired of the false signals etc. In other words, I started from scratch with a complete clean ISY and did a complete clean of all devices and setup new links. Since I was feeling more comfortable with the ISY and with how I wanted to lay out my scenes and programs I found it went very easily. One valuable tool I used from my first ISY install was the Topology. It provided me a checklist of devices and locations so that I could just sit at my console and get it done! The end result is a much cleaner setup and operation, you can forget spurious X-10 signals or other conflicts. JIM

Hi Rand. Not sure what you are asking... I'm OK - just needed to do another time sync after I installed. No Issue.

I just did another sync with the ntp and it is okay now. I am on east coast DST time as well. I guess this was just related to the installation but not actual problem (just needed to run another time sync)!

Loaded fine but the daylight savings setting appears to be disabled. My ISY 99ir/pro immediately lost an hour when started up. I have tried to click and unclick the daylight savings box with no impact.

This may relate to your problem - my RLs have had issues that are caused by the SwitchLincs air gap buttons. I know this will seem strange! Observation: one of the biggest problem I have had with switchlincs is the air gab button can become slightly depressed. This commonly occurs when someone turns off a load using the switchlinc! (Usually done by the wife but I can't fix her heavy hand!) When it occurs, lights may or may not respond, I will usually see communication issues (evidenced by ISY communication errors) when a query is run. I have also seen flashing RL leds occur at the same time (as comm errors). The switchlinc led may also be off due to the air gap button contact problem. Cause: The air gap button has been depressed just enough to either disconect or short out some contacts and cause communication issues (evidenced by the ISY communication errors). Solution (short term): I find that the button needs to be pulled back out - not enough to air gap or cycle the switch! Just enough to see the led properly glow on the switch itself. Then run an ISY query on the device to confirm communication. Let us know if you find this on any of your Switchlincs. I would like to get SH to address this issue.