Brian H

Well if anyone can get a strange problem it is me. After a power loss or a Reboot. The error happens every time I open My Lighting. The RemoteLinc 2 Button 1 icon is a red !. After I push that button on the RemoteLinc. The error goes away and the red icon changes to what looks like a tiny remote with six LEDs on it. Opening My Lighting from then on does not flag that error; until I do a Reboot as a test. Then it is back.

The range on the Proximity Reader is about 2-4 inches. I also found an error in the Kits Manual. The white wire from the Proximity Reader Module should be insulated and not connected to the +T trigger terminal of the Elk Relay board. If it is connected; the relay stays on all the time. Dakota Alert makes some driveway and motion sensors that maybe could be used. The receiver has some relay contacts that could be connected to an I/OLinc to trigger things. http://www.dakotaalert.com/index.html I know that Simplehomenet makes a Dakota Alert receiver. EZSnsRF but I believe it does not work with the ISY99i.

Today I had a power loss for a few minutes and I got a strange error next time I accessed My Lighting Administration Console. "Device Communications Error RemoteKinc 2 Button #1 (A 39 91 1). Please Check Connections. " In the My Lighting the RemoteLinc #2 Button 1 has a RED ! on it. If I push the button on or off the RED ! goes away and the error no longer happens in the Administration Console. I can also get the same error if I use the RESET ISY box. Firmware 2.7.6

Most CFL's are marked "Not For Dimmer Circuits" The ones that are dimmable have that feature on the box and most times on the lamp itself. I have tried some ULA SDS-23W ones with a LampLinc V2 and found they dim fairly well. Not quite linear and like to be started at 100% and dimmed down; to a point and then just go off. Didn't check for noise on the power lines.

With the set button 2 seconds is the minimum. Through software it can go to 0.2 seconds. If I read the data for the I/OLinc Smartlabs gave us in the SDK correctly, but I see a newer 1.1 rev is mentioned in the wiki so who knows.

The 2414S PLC and 2412S PLM are not even close to being the same. I am surprised at Smarthome's response. Right on the 2412S web page is a chart of differences between them.

Yes I have also seen improved incandescents are in the works and that the law only required a percentage of energy used reduction. I have tried a EarthLED EVOLUX S bulb and was not impressed at all. Their claim of a 13 watt bulb being comparable [didn't say the same (clever marketing ) ] as a 100 watt incandescent a big stretch of the imagination. I actually found a 6500K CFL in my collection.

I have seen CFL lights in different color temperatures. 2700K 4100K 5000K 5700K

Power strips and UPS units can also degrade Insteon signals. Insteon modules can also degrade X10 signals. Since they also have a power line transmitter in them. They absorb signals if not the unit transmitting. Insteon signals are resent, X10 signals are not. Some have reported their X10 systems degrade as they where switching over to Insteon.

The error message data in the wiki. Indicates a -200000 is a driver error. Sounds like someone from UDI may have to give you more assistance.

You are trying to add a device to a scene in the ControLinc using ISY?

Last time the water/leak detector kit was listed. The page basically said on hold for improvements. Then it just disappeared. Maybe it will come back if they can get a more reliable sensor.

Are you following the SD card replacement procedure on page 61 of the ISY99 Users Guide? http://www.universal-devices.com/docs/i ... rguide.pdf

Glad to hear it is now doing what you wanted. I believe I have seen reports that in some cases the motion sensor had to be removed and then added again.

In the tools tab. Diagnostics Section. What does the PLM/Status Test tell you? Should say connected and give the six digit address of the PLM; firmware revision.

http://forum.universal-devices.com/viewtopic.php?t=3007

I believe also if you want an on signal sent when the sensor is grounded. You have to link it with the sensor grounded. If you link it when not grounded. You get an on when open and off when closed.

Jack; That information maybe a help on finding the problem. I was asked if I was using added modules in my 1941 thread. Some with the problem. Also where using added modules.

Do you have any of the optional modules installed? I have Weatherbug and the Network Modules.

OK will keep you informed. Only thing so far was a RED! one time next to the ntp time address area. I looked at the wiki and latest pdf file and didn't see a red! mentioned. I believe it means that it could not get the time data. I believe the log showed something like that also.

Networking Weatherbug. Both Installed 08/17/2009 This was the first time it happend to me. I did notice a log note of: 0 CLI-WBu System -140005 as the last correct dated entry. That said I do see an occasional 0 WBug System -14???? Entry but maybe one a day and I do 60 second updates. I thought that maybe just an error accessing the site from time to time. I am trying 6 hours on 2.north-america.pool.ntp.org right now.

OK will give it a try. I use 24 hour intervals. Do you want more often?

This morning my ISY99i changed its date to Monday 08/25/1941. Sunrise 12:16:12 AM. Sunset 12:07:09 PM. My 4:50 AM program ran at around 9:00 AM and that is how I noticed it. This was at approximately 9:00 AM EDT of Saturday 09/12/2009. I have a custom location matching my towns coordinates. Sync every 24 hours. pool.ntp.org is the address used. The 4:50 AM and 6:40 AM scenes ran normally this morning. So the change must have happened between 6:40 AM and 9:00 AM today. Have turned off auto sync for now and will occasionally just do a sync to computer time. A sync to computer corrected the time; date and Sunrise and Sunset times. 2.7.6 firmware with weather and network plug ins. I did save the LOG in txt form.

Could you give a few details on the hardware being used?

That is good news. Glad you now have lights.