LeeG

I would first try a Restore Device. If the ISY thinks the E2 link should exist it will rebuild the link database with that link. If the link does not come back the ISY has lost the information about the PLM and deleting/readding the device is the way to rebuild the device link back to the PLM.

The device will not send messages to the PLM without that link. Is it possible a Delete Modem (PLM) was done?

That is a Responder link. Look for a link that starts with E2 and has the new PLM address. The E2 is a Controller record pointing to the new PLM which is required for the PLM to receive commands from this device.

If that link record starts with an E2 and is pointing to the new PLM the commands from the device should reach the PLM unless there is a comm problem.

The EZFlora will not turn On multiple Zones at once. For example, turning Zone 3 On will automatically turn Off the current Zone.

Pick a device that is not sending commands to the PLM (not triggering a Program) and run Tools | Diagnostics | Show Device Links Table. Do the link record(s) have the old or new PLM address?

Was the Wiki process described in Wiki section 6.1 used to replace PLM?

The If section is being triggered within the 5 second wait, the If is evaluated as False driving the Else. Assuming $i.Refridgerator_Defrost is an Integer variable as the $i. indicates it must the the 460 watt value drops.

If switching to PLM2 it means the "PLM is being replaced". All the devices will still have PLM1 address in all the links back to the ISY PLM. The Wiki section 6.1 has the procedure for "replacing" a PLM (moving from PLM1 to PLM2). The steps in the Wiki must be followed, particularly the power off steps. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_.28PLM.29

"If you want a program to trigger based on the switch changing status by any means (whether by direct action on it or by it responding to some other device's command), then use "status".." The Red part of the explanation does not apply to this situation. The information is fine as a general comment but if the OP decides to use STATUS because of the desire to change the device Status from another device it will not work. A comment to the effect that it does not apply to the OP example would have been helpful.

Keep in mind this is a "temperature sensor". A SwitchLinc or KPL button cannot send a command to the sensor to indicate it is some degree of temp that does not actually exist (the Sensor is a Controller node only). It is great to pass on information about various Insteon device capability and how Programs can be adjusted to handle those capabilities. However, passing on information that is not related and impossible for the current situation without indicating the information cannot be applied to the current environment can confuse a new user.

The I/O Linc Relay connection should be Comm and NO. Using Comm and NC is like pressing the button on the opener and holding it pressed. If the relay is connected to the two wires going to a multi button opener, shorting out power when the relay is turned On usually does not open/close the door. Either use a single button opener or go inside the multi button opener and connect the relay across the Open/Close button. Momentary B is likely a better choice to start with.

So long as the If section is a single item using "If Status" and Else section is fine. The problems arise when additional items are added to the If section such as a Time range. Multiple items in the If section can force a False condition driving the Else when not wanted. The two program approach using "If Control" does not have that issue. As long as the If section remains a single test one Program is fine.

The Else is not driven with the If Control. The Else clause executes when the If is False which does not occur with a simple "If Control xxxx is switched On/Off" If Control 'Attic / Fan Temp Sensor-Sensor' is switched On Then Set 'Attic / Fan Low Speed' On Else If Control 'Attic / Fan Temp Sensor-Sensor' is switched Off Then Wait 20 minutes Set 'Attic / Fan Low Speed' Off Else

Go to the Wiki section 6.1 for sequence. It is not complex but must be followed. Failing to unplug when directed can prevent replace from being successful. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_.28PLM.29

Try unplugging the ISY and then do the ping. Perhaps the router has assigned the IP address to another device.

Hi All I am concerned what some folks are expecting with the UDI PLM. It will certainly be more physically reliable, with a good power supply and not losing the link database when the power supply begins to fail. All really good things! The UDI PLM will not make a difference in how the Insteon powerline/RF function. Of course a failing power supply could impact events but while the SmartLabs PLM power supply works the UDI PLM and the SmartLabs PLM will produce the same results. Does not matter if there are 5 Insteon devices or 100. The UDI PLM and the SmartLabs PLM work the same as SmartLabs manufacturers the PLM chip and related PLM firmware. For better or worse ONLY SmartLabs controls how the Insteon network operates as they produce ALL PLM chips and they produce ALL of the PLM firmware. Smartenit (Simplehomenet) has been selling Insteon devices for many years. All of them use SmartLabs PLMs and SmartLabs PLM firmware. SmartLabs does not license any manufacturer to produce any device that directly interfaces with the powerline and/or RF. The UDI PLM will be a great product because it will be much more physically reliable. It cannot change what happens on the Insteon powerline/RF day to day as that is controlled by the SmartLabs PLM chip and SmartLabs PLM firmware.

Confirm this is the sequence followed ... Added new KPL under a dummy node name Right click on old existing primary node and select Replace With ....... using the new dummy node name Restart Admin Console when Replace With processing is complete

What ISY firmware is being used? What node name was assigned when the KPL was added to the ISY?

Right click on one of the 7 buttons and select Group Devices. The Main-A button will be the first in the list. EDIT: The Main A button does not have - A so the alpha list of node names often separates the first node from the Secondary button nodes.

Need to see the Program that does not start. "Enable" does not make a Program Run, it allows the Program to be triggered. Use "Run (If)" or "Run (Then)" to have this Program actually cause the other Program(s) to execute.

Along with what Techman is discussing, the On/.Off levels for the Responders is unique to each Controller. When the Scene is controlled from the Admin Console the PLM is the Controller and I suspect the Responder On Levels mentioned are when the Scene name was selected with the PLM as Controller. Click on the Red KeypadLinc button node name just below the Scene name. Check the Responder On Level values. These are the values in effect when the KeypadLinc button is the Controller.

The PLM has had a failure. Run File | Restore Modem (PLM) to rebuild the PLM link database.

Absolutely, so long as that temp is in the published specs. The specs do not say the range is 39-104 degrees using the internal temp sensor and some other range when using an external sensor. I have to believe an external sensor is being used now. Who would place a 2441ZTH inside a freezer to begin with. It is RF only so transmission is not likely inside a freezer let alone what that temp would do to the function of a device rated for 39-104 degrees.

The sensor is not the issue. The 2441ZTH is not spec'ed to send negative numbers as it is a room thermostat. It is not even spec'ed to be stored much below 0 degrees let alone functionally produce messages with temps in that range.