LeeG

Two FanLincs are not failing the same way (lets hope). Does/did the Fan have some control over the bright level of the lights before moving to the FanLinc?

Now we know what has been keeping ELA off the forums for so long.

The Group Cleanup Direct message provides a backup to the initial Group Broadcast message. The initial Group Broadcast message is not ACKed so the sending device does not know if the Responder(s) received the Group Broadcast message. The Group Cleanup Direct message is sent to each Responder and is ACKed so the sender can retry this message. The Group Broadcast, Group Cleanup Direct message sequence has been part of the Insteon protocol forever. The lack of a Group Cleanup Direct message could reduce reliability in a marginal Insteon network. My testing of this option shows no affect on two Hidden Door Sensors with v.43 firmware. The two devices send a Group Cleanup Direct message regardless of how this option is set.

Hidden Door Sensor Options HeartBeat interval changes do work. Current Heartbeat interval must expire before new Heartbeat interval takes affect.

Think of what a house would feel like at 104. That is the problem of using a device for a purpose other than what it was designed for.

As an FYI, a Direct Relay On always turns the Relay On. If in any of the Momentary modes, the Momentary timeout will turn the Relay Off. The various Momentary rules about which command will operate the Relay do not apply to a Direct command but the Momentary mode timeout does apply.

Define an ISY Scene. Add the KPL Main button and LampLinc as Controllers. Scene xxxx KPL - Main - as Controller LampLinc - as Controller Just below the ISY Scene name "xxxx' are the Red Controller nodes. Click on the Red KPL Main button and set the Local On Level for the KPL button to 35%. Set the LampLinc On Level to 35%. Click on the LampLinc Red node and set the same values, Local On Level for LampLinc to 35%, KPL button On level to 35%. When the KPL Main button is pressed On the KPL load and LampLinc turn On to 35%

saphotoexpress A good program check is for both Heartbeat On and Heartbeat Off as the command depends on the Wet/Dry state of the Leak Sensor. HeartBeat - [iD 0044][Parent 0001] If Control 'Leak Sensor-Dry / Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Dry / Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours Send X10 'A10/All Lights On (5)' Else - No Actions - (To add one, press 'Action') The Heartbeat message should occur every 24 hours (approx). The test Program Waits for 25 hours, expecting a new Heartbeat message at the 24 hour point. This test Program is turning on an X10 device. Most likely sending an email would be the normal response rather than the X10 message.

Davonavo One of the Hidden Door Sensors produced a heartbeat message at the end of its 24 hour period. Now it is sending a Heartbeat message every 10 minutes which is the heartbeat interval I set. Have received several heartbeat messages spaced 10 minutes apart.

UI level is Admin Console level Firmware is ISY level As I remember the device has to timeout the current heartbeat interval before switching to a new value so it may take up to 24 hours to see if Hidden Door Sensor heartbeat interval can actually be changed. I have changed two Hidden Door Sensors to 10 minute heartbeat interval with programs tracking heartbeat messages. It may take up to 24 hours before you see a heartbeat message. Does your Open/Close Sensor have a Heartbeat node?

Davonavo Are you on 4.2.21? The Leak Sensor, which does have a heartbeat feature, no longer has an option to set heartbeat interval on 4.2.21. I did some tests long ago and think setting the heartbeat interval had no affect on the Leak Sensor. That memory combined with the option no longer being available on 4.2.21 makes me think the Leak Sensor did not support changing the heartbeat interval. The heartbeat node is there and will receive a heartbeat message whenever the Leak Sensor sends it. I suspect changing the heartbeat interval on the Open/Close Sensor may also not be supported. The heartbeat interval is still shown on the Hidden Door Sensor. I am testing that now.

Does the LampLinc show being on the opposite 120v leg as the PLM?

The 2406H is passively coupling the powerline only. It has no RF capability so no affect on RF test.

4.2.21 was posted about a week ago. Not long enough to know if it is stable enough to be an Official release.

"now the MS just turns them off while they are on and will not turn them on with motion." This does not make sense. If the motion sensor turns the devices Off it will/should turn them On. There is no option for Off commands only. Without an ISY Scene all lights are being controlled from programs and the light devices themselves.

The feature is in 4.2.21.

That question is best answered by doing the 4 tap Set button test which will show what devices are receiving the RF test message and whether they are on the same or opposite 120v leg.

Linking manually, which should never be done when using an ISY, is creating an Insteon Scene.

The ISY accepts Heartbeat message whenever it occurs. Before 4.2.21 all battery devices must be put into linking mode manually. That means no Remote update without someone locally putting the device into linking mode. Does your Open Close Sensor have a Heartbeat message. User Manual does not discuss that feature.

In addition to oberkc comments about being in a Scene which I completely agree with, two additional items. The On Only mode: check box should be "unchecked" for the motion sensor to send On Only commands. This Program is missing parens. ===TriggerLights====(ENABLED) If From Sunset To Sunrise + 6 hours (next day) And $Manual.Lights is 0 And ( Control 'Driveway-Sensor' is switched On Or Control 'FrontPorch-Sensor' is switched On ) Then Run Program 'FrontLightsManual' (Then Path) Else Set 'Front Yard Lawn' Off Set 'Front Yard Driveway’ Off

This looks like something is causing interference. Some of the commands have Hops Left=2 which is as good as it gets. A few seconds later the device does not respond at all. Sat 12/27/2014 08:40:56 PM : [iNST-TX-I1 ] 02 62 1F 1D 28 0F 11 FF Sat 12/27/2014 08:40:56 PM : [iNST-ACK ] 02 62 1F.1D.28 0F 11 FF 06 LTONRR (FF) Sat 12/27/2014 08:40:56 PM : [iNST-SRX ] 02 50 1F.1D.28 30.6B.18 2B 11 FF LTONRR (FF) Sat 12/27/2014 08:40:56 PM : [std-Direct Ack] 1F.1D.28-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/27/2014 08:40:56 PM : [D2D EVENT ] Event [1F 1D 28 1] [sT] [255] uom=0 prec=-1 Sat 12/27/2014 08:40:56 PM : [ 1F 1D 28 1] ST 255 Sat 12/27/2014 08:40:56 PM : [D2D-CMP 015F] STS [1F 1D 28 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Sat 12/27/2014 08:40:59 PM : [iNST-TX-I1 ] 02 62 1F 1D 28 0F 13 00 Sat 12/27/2014 08:40:59 PM : [iNST-ACK ] 02 62 1F.1D.28 0F 13 00 06 LTOFFRR(00) Sat 12/27/2014 08:41:03 PM : [D2D EVENT ] Event [1F 1D 28 1] [ERR] [1] uom=0 prec=-1 Sat 12/27/2014 08:41:03 PM : [ 1F 1D 28 1] ERR 1 - no response from device Has a new piece of electronics appeared over the holiday? Perhaps a Dual Band device was unplugged, making coupling dependent on 240v appliances, which could make comm poor when the 240v appliance turns off. These are Direct commands which have retry. Easy to see why Scene commands are having difficulty.

There are no device responses to ISY Scene commands issued by the PLM. The ISY marks the Scene devices as the way they should have responded, not as they actually did/did not respond. Scenes have a way of showing marginal comm. Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Use Direct commands to turn the Scene devices On and Off a few times each and post the event trace. The Hops Left count being low and changing from command to command would indicate marginal comm.

The Event Viewer must run at LEVEL 3 to evaluate device comm quality. There is a Level pulldown at the bottom of the event viewer window.

See my post just before your last post regarding Relay On/Off state.

ISY Scenes can be less reliable if comm to the particular device is marginal. Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Issue a few Direct On commands and post the event trace. The Hops Left count in the 1 and 0 range, particularly if the Hops Left count changes over a few Direct On commands indicates questionable comm with the Relay. The state of the Relay is not helpful (using Scene or Direct commands) as it will be On all the time as Momentary mode is turning the Relay off which the I/O Linc DOES NOT report back to the ISY.