LeeG

If the Program was written with the assumption the KPL button was non-toggle mode there would be no need for And Control 'KPL Button' is not Switched Off

Try running a Show PLM Links Table followed by Count to determine how many link records actually exist in the PLM. It looks like the PLM was "Deleted" somewhere in the process which erases the PLM link record references. If the PLM was Deleted either an earlier ISY backup needs to be restored followed by another Restore Modem (PLM) or the system has to be rebuilt.

The Scene has been lost for some reason. The 15 on the end of the Scene request indicates the Scene definition no longer exists in the PLM. Tue 05/21/2013 06:56:16 AM : [GRP-RX ] 02 61 16 13 00 15 Was the PLM Deleted during the process of moving from the 99i to the 994i? Is the 994i using the same PLM as was used on the 99i?

Thanks for the additional information. When I installed my security system long ago monitored versus unmonitored device referred to how the security panel interfaced with the device, not whether a device was not connected to the security system. It makes more sense know that I understand unmonitored refers to devices the security system is not aware of at all. I did not realize wired smoke detectors were no longer available.

The Program example assumes the KeypadLinc button is operating in toggle mode. The same would apply to a RemoteLinc Mini (RemoteLinc2) operating in toggle mode.

By arithmetic you mean more than Assign $x = a Add $x += a Subtract $x -= a Multiply $x *= a Divide $x /= a Remainder $x %= a And (binary) $x &= a Or (binary) $x |= a Xor (binary) $x ^= a

Insteon is not rated for such duty. It should not be used as any part of a primary notification system. Nothing wrong with using the Smoke Bridge as an additional means of notification but the primary smoke detection and notification must be though the Ademco Vista system.

whywork What is the firmware level of the 2441ZTH? I have one at v.0B which does report temperature changes while in Off mode after an ISY reboot. Since yours does report when in Off mode after going to some mode other than Off and then back to Off I am wondering what was different about the initial Off mode. Had the batteries just been inserted? The ISY reports temp message received regardless of thermostat mode. The thermostat mode was Off before reboot and Off after reboot. As soon as I raised the ambient temp of the 2441ZTH it sent a temp message which the ISY immediately displayed. Perhaps a difference in how the 2441ZTH firmware works? Of course the 2441ZTH would not report temp changes in the freezer as RF messages could not travel out of a metal box but I would have expected it to report temp changes as it warmed up assuming the 2441ZTH was in range of a Dual Band device as it warmed up. I am running 4.0.4

Thanks for the information and trace data. The PLM does not have the link records for the Scene being tested. Do another Restore Modem (PLM). Then run the same Scene Test again with the Event Viewer running as before.

What does Help | About show for Firmware and UI? From what level ISY was the backup that was restored? Run Tools | Diagnostics | Event Viewer at LEVEL 3. Right click Scene name, select Diagnostics | Scene Test. Post event trace.

"My question is - will this show up as an Insteon device?" No. The ISY has no awareness of the rain sensor. "I have an existing rain sensor - when that signals the EZFlora how can I detect that on the ISY 994 to take whatever action I want to take?" It cannot be detected in the ISY.

What actual command(s) do you want to execute? A direct path through the PLM is not available in the ISY.

The post by Xathros has the answer. Use Variables to note and remember what the FanLinc Motor speed is and what the next should be. Example Variable X represents current FanLinc Motor speed. 0 = Off 1 = Low 2 = Med 3 = High The If AC On Ands a check of variable X greater than 0 Then X -= 1 (to reduce motor speed one level) Run Program2 The If AC Off Ands a check of variable X greater than 0 And not greater than 2 Then X += 1 (to increase motor speed one level) Run Program2 Program2 If X = 1 Then Set FanLinc Motor to Low Else Run Program3 Program 3 If X = 2 Then Set FanLinc Motor to Med Else Run Program 4 Program 4 If X = 3 Then Set FanLinc Motor to High Else Null This is a rough concept but should convey one way to accomplish task. Xathros may well have a better approach since using Variables is his idea to begin with

Nothing that I am aware of as far as connecting Port A to anything but another PLM. If you have a Serial port the PLM can be connected to a PC. The HouseLinc software is now free. It can be downloaded from Smarthome and have it connect to the PLM. I would expect HouseLinc to have PLM issues if the PLM is not working.

Are you looking for someone to write the Programs for you?

Clearing the old links was exactly the right thing to do. Now that you have done linking outside of the ISY the KeypadLinc and the I/O Linc should have a Restore Device done to get rid of the manual links. The ISY is not aware of them and will eventually cause problems later. Define an ISY Scene with the I/O Linc Sensor as Controller and the KeypadLinc button as Responder. This will allow the KeypadLinc button to show if the door is open or closed. Define an ISY Scene with the KeypadLinc button as Controller and the I/O Linc Relay as Responder. This will allow the KeypadLinc button to control the I/O Linc Relay. Set the I/O Linc Relay to Momentary B mode. This will allow the KeypadLinc button to turn the Relay On and move the door whether the KeypadLinc button LED is On or Off.

"Are you guys saying I stead of directly turning the device on at the relay, I turn it on in the scene instead?" Yes, exactly. "The fifth line was just for the status of the relay and the 2 second delay was just to prevent to much traffic at once" Not necessary to delay as both devices (Relay and KPL button) react at the same time to the Set Scene statement. You can turn the Relay on directly as you are doing now and define an additional ISY Scene that has the KPL button as a Responder and turn the new Scene On/Off to control KPL button LED but it is not necessary since you already have a Scene defined that includes the Relay and the KPL button.

The Adjust Scene statement after the Wait 2 seconds is changing a Responder On Level, it does not directly affect the device. Use the 'Insteon' Action statement that specifies the ISY Scene name 'swamp cooler relay'. Turn the Scene name On and Off. When using the Scene name a separate Direct command to control the Relay is not necessary. Example: Set Scene 'swamp cooler / swamp cooler relay' On

A Secondary KeypadLinc button cannot be turned On or Off with a Direct Insteon command. A Direct command does not have a placeholder for a button number. Define an ISY Scene with the Secondary KeypadLinc button as a Responder. Have the Program turn the ISY Scene Off to turn the Secondary KeypadLinc button LED On or Off. If there is already an ISY Scene with the KeypadLinc button and Relay in the Scene, use that Scene to turn the KeypadLinc button LED and Relay On and Off together.

jmed999 Would the irrigation requirement not be expected to change over time? An irrigation requirement at 12:01 AM would seem to have to be different from a requirement taken at 6 PM the same day. There have been 18 hours of heat, sun, wind, etc which logically would affect the irrigation requirement. Would one not use the current values at 6 PM (assuming irrigation is done at 6 PM) rather than a requirement pulled 18 hours before.

It sounds like the Motion Sensor either timed out of manual linking mode which is started by pressing Motion Sensor Set button until the Red LED blinks continuously or the Motion Sensor is not in reliable RF range of a Dual Band device. Put the Motion Sensor into manual linking mode. The Motion Sensor will stay in manual linking mode for approx 4 minutes so do the next step immediately. Right click Motion Sensor - Motion node, select Write Updates to Device. This will direct the ISY to write any pending updates. If the Motion Sensor goes back to a Red ! move the Motion Sensor closer to a Dual Band device that has communication with the ISY PLM. Be sure the devices that are acting as phase couplers pass the 4 tap Set button test for phase coupling.

This is only a guess since the content of the variable is not described. If $OCCUPIED is 0 And ( or Status 'Motion Sensors / Laundry Motion Sensors-Sensor' is On or Control 'Backyard1' is switched On or Control 'Backyard1' is switched Off or Control 'Backyard2' is switched On or Control 'Backyard2' is switched Off or Control 'Front Door' is switched On or Control 'Front Door' is switched Off or Control 'Master Bath Room' is switched On or Control 'Master Bath Room' is switched Off ) Then Send Notification to 'TXT MSG All' content 'home is OCCUPIED '

You are correct in that 'is Responding' will not work. However, it is because it will always be 'is Responding' unless the ISY has had problems writing updates to the thermostat. I think your Program is being triggered because of the check of temperature from the climate module. Every time the climate temp changes, which would be many times over a 24 hour period, the Program is triggered. The specific check itself of below 0 does not drive the Then clause but because the 2441ZTH temp is ORed the compare of a blank value causes the Then clause to run. I don't see any real difference between 0 and 1 degree in this situation so if Module 'Climate' Temperature < 0 °F Or { Status 'Thermostat - Main' >= 1° (Temperature) And Status 'Thermostat - Main' <= 45° (Temperature) } Then Send Notification to 'Default' will probably prevent the false emails. Once the 2441ZTH sends a temperature message the ISY will remember that temperature until the ISY is rebooted. Remember though that being a battery device the 2441ZTH sends a message far less frequently than if it was under line power. EDIT: you got there first this time

"The problem is about 30 min into this program my sprinklers on zone 3 stopped" The default Timeout for a Zone is 30 minutes. Change the Timeout value for Zones that need to run more than 30 minutes.

The status of each node has to be tested individually.