Techman

This usually indicates a communication issue between the device and the PLM Take a look at these troubleshooting tips https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors

Additionally, make sure that the battery operated device is within RF range of either the PLM or a dual band device so it can communicate with the PLM in order to have its link tables updated/written to.

Anytime you make a change to a device which is also linked to a battery operated device you need to put the battery operated device into the linking mode in order for the changes to be written to the battery operated device. You can only have one battery operated device in the linking mode at any one time otherwise the link tables can get corrupted/cross written.

You have a communications problem between the PLM and your Lamplinc. Take a look at this troubleshooting guide https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors&redirect=no

I'm assuming that you're running 4.6.2 (or earlier) ISY firmware. If so the firmware does not fully support the motion sensor options. This sensor was recently released and replaced the previous motion sensor which the ISY fully supported. The ISY only recognizes a timeout of 30 seconds (on the current MS), thus the need for programs 1 and 2. If the light is turned on from a scene then have program 2 turn on the scene rather than the light.

You'll need two programs Being that the default on time is 30 seconds The first program should call the "then" statement in the second program which will turn on the light. When the motion sensor turns off the 2nd program will continue to run until completion Program 1 IF Control Motion sensor is ON and Dusk is ON THEN Run THEN statement in program 2 ELSE (blank) Program 2 IF (blank) THEN turn on light wait 5 minutes turn off light ELSE (blank)

I'm not sure if 5.0.10 treats the ISY link tables differently or if it's a bug in 5.0.10 I'm running 4.6.2 and the only mismatch I've come across is EA, which shows up on the device link table and can be ignored..

The mismatched link usually shows up in the device link table not the ISY link table. Doing a restore device rewrites the link table stored in the ISY to the device. The ISY link tables shouldn't change unless you reprogramed a device from within the ISY. What version of the ISY firmware and UI are you running?

That seems to make sense for the AA link to appear in the device link table but why would the AA show up in the ISY link table?

I'm not aware of an option to disable the "flash". I believe it's an indicator that the button action was processed.

I've never come across a device with an AA link. It's possible the link was left over from a previous use or a factory test. You could always try a factory reset / restore device to see if that eliminates it. Not sure why it would show up on the ISY link table. Did you buy the device new from Smarthome or from a 3rd party?

Try doing a factory reset then restore device on a device with an AA link table. Let me know if that clears up the mismatch. What type of device is it. What's the 4 digit date code on the device?

Can you take a screen shot of the link with AA in it and post it on the forum

Take a look at the attached Insteon White Paper, it has a detailed explanation of the link tables. AA appears to be used for RF packets (see page 31 of the white paper) If all you devices are working correctly after you installed the new modem then you can probably ignore the "approximate" link count from the calculator. Insteon white paper.pdf

Yes, UUID is the ISY's MAC address

How many devices do you have installed? That link count sounds very low and usually indicates a failing PLM.

The manufacture date is the 31st week of 2009. Do a PLM link count during a period when the ISY is not busy. If the link count is low then it's time to replace the PLM. The new PLM's have updated hardware and firmware.

In the option menu for the KPL set the button to Non Toggle (off)

The Siren is not supported in 4.6.2 firmware. Not sure if its supported in the 5.x.x alpha release.

I'm running 4.6.2 which works with the motion sensor node, but only the MS default options are available.

The motion node is supported, the other nodes are not. Add it to the ISY using the previous motion sensor ID (2842-222) Yes it can be added to a scene or a program

Having dual band devices within close proximity to the motion sensor may help. There will always be a slight delay when turning on a scene.

K3RMB I have my ISY sitting within 10 inches from a 2 meter radio. I don't hear any signal in the 146 Mhz range coming from the ISY. You may have either a bad piece of coax, or a bad Ethernet cable connected to the ISY.

CFL bulbs can be problematic. They have a built-in ballast which can sometimes create noise on the powerline which interferes with the Insteon signal.

What type of bulbs are you using in the exterior fixtures? What type of switches are you using for the exterior lights, dual band or single band? Here's some troubleshooting steps that may help http://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors