Brian H

Installed fine this morning.

OK thanks for the update. I can now allow Java to update and tell Avast to hold off. Until data on how to correct it is avilable. Yes please share. Maybe in the Avast Thread as it relates to the problem.

Update 27 must be very recent. On 09/09/2011 my check for Java updates didn't find 27 and said 26 was the latest. So no one else may have tried 27 yet. I have 26 and as you found. Working OK. Gee in another thread someone found the newest Avast Update, released recently, also was causing problems.

Much information in the wiki. http://www.universal-devices.com/mwiki/ ... =Main_Page http://www.universal-devices.com/docs/i ... rguide.pdf

Isaac on the Smarthome Forums. Posted what was fixed in V2.2. http://www.smarthome.com/forum/topic.asp?TOPIC_ID=8552

Updated with no major problems. I am getting a failed to retrieve product update information warning when I start the Administration Console. Actually that message started to show earlier today. Maybe while you where getting 3.1.6 ready to be downloaded.

I would also say Factory Reset and start new. There have been some rare cases where they shipped with some test links and X10 addresses in them. Upgrading to the Pro Version is not hard at all. As Tim mentioned. Just purchase the Pro Module and UDI does their thing. Some on line magic happens and the ISY99i reboots. You then have the Pro Version.

There is also a warning on the MorningLinc's sales page. Basically it converts a Insteon command to an RF command the lock understands. It is a one way command and the MorningLinc has no way to verify if the lock received and processed the command. Also local locking and unlocking will not be sent back from the lock. http://www.smarthome.com/2458A1/Morning ... ler/p.aspx

No official time tests. My 2413S processes the ISY99is commands faster, than my older 2412S did.

Do you know the Hardware Revision from the sticker for the ApplianceLinc's or the firmware as reported in ISY Device list? Only a guess. Someone thought a module turning back On after a power loss. Could be a safety issue. All of mine HW 4.1 or below revert to last known state at power loss. My 4.2 reverts to Off. I believe I saw a chart saying 4.15 also reverted to Off.

I will have to keep an eye on it as the Log was turned off. The lease time was set to 60 minutes. I now see the default is one day.

I am seeing lots of network errors again with 3.1.5. Sat 2011/07/23 07:11:21 PM System -5 Start Sat 2011/07/23 07:11:31 PM System -60001 pool.ntp.org Sun 2011/07/24 07:11:42 AM System -60001 pool.ntp.org Sun 2011/07/24 07:11:57 AM System -60001 pool.ntp.org Sun 2011/07/24 07:12:13 AM System -60001 pool.ntp.org Sun 2011/07/24 07:12:30 AM System -60001 pool.ntp.org Sun 2011/07/24 07:12:48 AM System -60001 pool.ntp.org Sun 2011/07/24 07:13:06 AM System -60001 pool.ntp.org Sun 2011/07/24 07:13:24 AM System -60001 pool.ntp.org Sun 2011/07/24 07:13:42 AM System -60001 pool.ntp.org Sun 2011/07/24 07:14:00 AM System -60001 pool.ntp.org Sun 2011/07/24 07:14:18 AM System -60001 pool.ntp.org Sun 2011/07/24 07:14:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:48 AM System -100 [DHCP] state=FAILED Sun 2011/07/24 07:18:48 AM System -100 [DHCP] Timed out; Restarting Sun 2011/07/24 07:23:27 AM System -100 No network connection Sun 2011/07/24 07:24:51 AM System -100 No network connection Sun 2011/07/24 07:26:16 AM System -100 No network connection Sun 2011/07/24 07:47:31 AM System -100 No network connection Sun 2011/07/24 08:02:56 AM System -100 No network connection Sun 2011/07/24 08:34:11 AM System -100 No network connection Sun 2011/07/24 08:57:25 AM System -100 No network connection Sun 2011/07/24 08:58:10 AM System -100 No network connection Sun 2011/07/24 09:15:26 AM System -100 No network connection Sun 2011/07/24 09:17:01 AM System -100 No network connection Sun 2011/07/24 09:21:06 AM System -100 No network connection Sun 2011/07/24 09:24:41 AM System -100 No network connection

It is just a icon representing a responder. On or Off the icon does not change.

Are you sill going to make announcements here. I do not twitter and don't want to start now.

I don't think there is an easy way to fix a 2412S. There was a schematic of the PLM in the Developers Guide and I have tried to look at a few revisions myself. Not sure if it would verify much, but I guess you could use a program like Busy Rats PLM Test program to send it a serial command and see if it responds. http://busyrat.com/plmtest/ If it is in warranty. Smarthome may replace it. I believe I saw reports of the 2413S being offered with the $10 price difference between the 2412S and 2413S being paid.

The only other thing that could make the 2412S LED blink would be random power line noise, but I doubt noise would prevent a connection with the ISY99i. I does sound like it may have failed. Since the 2412S is now discontinued. The 2413S Dual Band maybe what you would need to get and it does not provide power for the ISY99i. So if you go that route. There is an optional power supply also avilable from Smarthome.

The 2414S is a PLC and not a PLM. I have a 2412S PLM marked 2414S. Smartlabs reprogrammed a PLC to work like a PLM. What does the Tools, Diagnostics, PLM Info/Status test show? Since the 2412S is on the AC power I would think it would be the more likely candidate to have a problem. When no actions are happening. The Power LED is the only one illuminated along with the LED glowing dimly on the PLM.

Well I have no modules new enough to have the beep features. I understand a wiring problem or incorrect load will make them sound a warning. So rechecking everything can't hurt.

The latest KPL has a beeper in it. According to the sales page. I believe the SwitchLincs may also have beepers now. I wounder if maybe they beep on power up.

Loss of communications to the device. http://www.universal-devices.com/mwiki/ ... ation_Mark http://www.universal-devices.com/mwiki/ ... User_Guide

You could factory reset everything and go from scratch. Any preexisting links not done by the iSY99i will not show up in My Lighting. When adding devices in link management. There is a choice to remove existing links in a device as it is added. There is also a choice to keep existing links but that may also add the problem controllers links also if they are in the devices. http://www.universal-devices.com/docs/i ... rguide.pdf http://www.universal-devices.com/mwiki/ ... =Main_Page

Installed fine with no hitches.

http://www.universal-devices.com/tools/ ... _links.htm

That is what I thought. Thanks for the confirmation.

Do you have a 2412S PLM or a 2413S PLM? The original 2412S PLM had a 417 link database. Newer ones a >2000 link database. The Quick Users Guide just says >2000. The sales page for the 2413S now says >800 2412S implied here and 1023 for the 2413S? 2413S 1023 link database. 2065 sounds strange and is too big for even the later 2412S PLM that could be no larger than 2048.