LeeG

The message about not obtaining the Insteon Engine indicates the ISY is not getting any response from the device address. The Query Insteon Engine is the first command issued. Make sure the device is being powered from unswitched 120v AC. Make sure the Insteon address is correct (8 taken as B, etc). The Event Viewer was not run at LEVEL 3. The event trace can be run again at LEVEL 3 to confirm the Query Insteon Engine is not getting a response. .

Folder conditions have been checked including the My Programs Folder at the top of the tree.

With the additional information that other Programs are not being triggered as well suggests something different. What ISY firmware is being used? Does Help | About show the same version for Firmware and UI? The correct Motion Sensor messages are being received. Assuming 14.99.8E is 'backdoor-sensor' the Program should have triggered. With nothing in the Last Run Time column and other Programs not being triggered I suggest rebooting the ISY. If that does not resolve the problem open a Ticket with UDI tech support.

The Program has never been triggered. Otherwise there would be a Last Run Time. Also note that a simple If Control xxx is switched On can only trigger with a True condition. The Program is False because it has never run. Yes, HouseLinc can and does interfere with the ISY. Any time there are multiple HA applications trying to manage the same devices there will be conflicts. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Trigger the Motion Sensor (?) at the back door and post the event trace. The required On command in the proper message is not being received which is why the Program never triggers. oberkc – nice job of covering all the usual causes!

I would think the reversed logic of using Ands would have the same issue. When the first device is marked changed by the Scene the Program is triggered with a False If condition because the other devices have not been set to the Scene values. KPL button C Off turns Off because the other devices have not reached the Scene settings. If it works use it but I cannot explain why it is working. The following should also work. This Program is triggered by the KPL button C being pressed On. It waits 2 seconds and Enables the existing Program with the If Status checks. The existing Program with the If Status checks will be Disabled until KPL button C is pressed On. The If Status Program will remain Enabled until one of the devices changes Status that results in KPL button C being turned Off at which point the If Status Program will be Disabled. This prevents the If Status Program from triggering the next time KPL button C is turned On. I’m estimating that 2 seconds is long enough for the ISY to mark all the device Status changes resulting from turn On button C. If Control 'KeypadLinc 6 Button / KeypadLinc 6 Button - A' is switched On Then Wait 2 seconds Enable Program 'Test2' Else - No Actions - (To add one, press 'Action') This Program is labeled Test2 on my system. The name of the Program has to be changed to match the actual Program name If Status 'Family Room / Family Recessed' is not 30% Or Status 'Hall / Hall' is not 15% Or Status 'Upper Hall / Upper Hall' is not 15% Or Status 'Kitchen / Kitchen Recessed' is not 30% Or Status 'Kitchen / Stairway' is not 15% Or Status 'Kitchen / North Island' is not Off Or Status 'Kitchen / South Island' is not Off Or Status 'Kitchen / Turret' is not Off Or Status 'Kitchen / Table Pendant' is not Off Or Status 'Kitchen / Table Recessed' is not Off Then Set Scene 'MovieKPL' Off Disable Program ‘Test2’ Else - No Actions - (To add one, press 'Action')

I think I understand the issue. When the first device affected by KPL button C On changes Status to its expected On Level defined by the Scene it is very likely at least one of the other devices is at a different level . The change in Status of the first device affected by the Scene causes the Program to trigger. That first device is at the correct level (Off or at some % On Level) but the other devices have not yet been marked to the new Scene established values. Thus the If is True and the button LED is turned Off. The implementation will have to be done with two Programs. I’ll post them as soon as I have tested the new variation.

Click My Lighting at the top of the device node tree and verify that each device being checked by the Program is reporting the expected % On or Off state. Go to Programs | Summary. From a button Off state press KPL button C and look at the Status column for the Program in question. Is it True or False?

The Dakota Alert driveway sensor, the magnetic version, detects a change in the magnetic field. Once stable the sensor no longer trips. I use two of these, one at the mail box and one further down the drive. When the mail is delivered the sensor usually trips twice. Once as the carrier pulls up to the mail box and again when carrier drives away. The sensor is silent for as long as the carrier is stopped at the mail box. There is an IR beam detector (not Dakota Alert) that is active the entire time the beam is broken. Most of the IR detectors trip momentarily when the bean is broken and then reset regardless of IR beam state. I looked into this years ago as I wanted to detect the physical presence of the vehicle in the garage rather than just that the beam tripped on entry or exit. Never did implement as the multi car garage presented problems detecting multiple vehicles.

The ISY marks the device at what will be the final On Level immediately. I have a Scene that turns a Dimmer to 30% over 19 seconds. The Dimmer is marked as 30% when the Scene is executed even though it takes 19 seconds to reach 30% I suspect something else is wrong. Please post the Program that is turning KPL button C Off. Right click the Program name, select Copy to Clipboard and Paste to a forum post.

I'll do some testing with long ramp rates before I suggest the next approach. If the logic is reversed to turn on KPL button C On then there is nothing that turns if Off. I'll post back soon.

“First - somehow I expected all the "slave" dimmers (e.g., FamilyRoomSlave1) to follow status, but clearly they don't. I guess I need to add all those as responders too?†Yes, all the devices that should react must be added to ‘MovieLights’ Scene as Responders with the appropriate Responder On Level and Responder Ramp Rate settings. “Second - my KPL C LED never goes off. I set it to "non-toggle on" thinking that was what I wanted. (I want it to set that scene "on" any time it's pressed.) But now it goes on and never goes off. How do I make it shut off when I turn any of the effected lights off? Do I need to add KPL C as a responder to all the other scenes?†This one is harder to accomplish because of all the variations you want to result in KPL button C turning Off. It cannot be done by assigning KPL button C to any of the Scenes (beyond KPL button C being Controller of ‘MovieLights’). A Program is required that triggers on any of the conditions that should turn Off KPL button C. If Status ‘device1’ is not 30% Or Status ‘device2’ is not Off Or Status ‘device3’ is not Off Or Status ‘device4’ is not 30% Or Status ‘device5’ is not 15% Then Set Scene ‘KPL button C’ Off Else ‘device1’ is load control device for FamilyRoom Scene ‘device2’ is load control device for KitchenIsland Scene ‘device3’ is load control device for Nook Scene ‘device4’ is load control device for KitchenRecessed Scene ‘device5’ is load control device for Hall Scene Any manual action by a Master or Slave device for a particular Scene will change the load control device from its predefined level for that Scene causing the above Program to trigger turning Off KPL button C. Scene ‘KPL button C’ has KPL button C as Responder has to be defined. The only way to control a Secondary KPL button LED is for it to be a Responder in a Scene and control that Scene. “Third - is doing this all with scenes the best way to go, am I approaching it right, or would I be better off doing it with programs?†The reaction by KPL button C cannot be done with Scenes alone. Management of KPL button C is done with a combination of Program and Scene.

This Program assumes the I/O Linc Sensor turns On when the door is opened. Might have to change the If On to If Off when I/O Linc works the other way. If From 11:00:00PM To 6:00:00AM (next day) And Control 'IOLinc-Sensor' is switched On Then Repeat 10 times Set Scene 'Scene KPL Button A' On Wait 1 second Set Scene 'Scene KPL Button A' Off Else - No Actions - (To add one, press 'Action') EDIT: added the time range. Was not sure what aspect of the Program was an unknown

If run in Multi-Scene mode (jumper removed) a Program would react to If Control is switched On for either node. One node gets an On command when the TriggerLinc turns On and the other node gets an On when the TriggerLinc turns Off. I think most users run with the jumper On so that the first node receives On and Off commands that follow the TriggerLinc. Remember if the jumper is changed the battery has to be removed and restored for the jumper change to take affect (also in the user guide on my page .

I did not replicate the If you posted. Was that not what you are using to sync the KPL LED? If Control 'The Boys / Room1' is switched On Or Control 'The Boys / Room1’ is switched Fast On Or Status 'The Boys / Room1’ is not Off The posted If is checking for Room1 being turned on locally (switched On/Fast On). Room1 should be a Controller of the same Scene definition where one of the KPL buttons is a Controller and Room1 is a Responder. With that change the first two lines of the If can be eliminated. The If Status catches the case where Room1 turns On by whatever cause and turns On the KPL button with some number or retries. If something is being missed has it been traced and verified the problem is not with the communication from Room1 rather than to the KPL?

This is an example of a Repeat every 1 minute If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 1 minute Set Scene 'Scene KPL Button A' On Else - No Actions - (To add one, press 'Action') I did not replicate your If section. Using the Program is a bad thing. It introduces a volume of Insteon traffic that could interfere with other things going on. The Dual Band KPL was only released a few days ago. Are you sure you have a Dual Band KPL? This is another example that limits the activity to 10 times. Still not good but better than a Repeat that could run for hours. If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat 10 times Wait 1 minute Set Scene 'Scene KPL Button A' On Else - No Actions - (To add one, press 'Action')

The TriggerLinc has two modes of operation. A single node is used (sending On and Off commands to the single node) unless you pull the jumper on the PC board. When the jumper is pulled both nodes receive On commands Only. The TriggerLinc User Guide (page 8 in my copy) describes Multi Scene operation (jumper removed).

markgam What is the thinking behind the question? Do you want to use an EZIO4O to control irrigation valves or use the EZFlora to control 8 different loads? Another difference is the EZFlora runs only 1 valve at a time. Turn On zone 4 and any other zone that was On is turned off by the EZFlora. The EZIO4O can of course control each relay independently. One relay On, two relays On, all relays On. .

Not the same internally. The EZIO4O uses Relays that can switch AC or DC. The EZFlora is designed as an irrigation controller, thus the additional features specific to an irrigation application. Also the EZFlora uses Triacs to switch the 24v AC that drives the valves..

Either can turn On/Off individual valves. The EZFlora has a pump control function that turns on a pump when any of the other 7 zones is turned on. The EZFlora has max run times for each zone that automatically turns off a zone if the defined max run time for the zone is exceeded. Also, the EZFlora supports a rain sensor that will prevent watering when it is raining..

Add a Wait to the Programs that should run with a delay.

tech_dog Unfortunately no. There are a number of new Insteon things that did not exist when 3.3.10 was released. The Dual Band KPL is one of them. Need to move to a 994i.

If there were other devices in addition to the I/O Lincs that were not showing state changes in the Admin Console my first conclusion would be the PLM lost some or all of its link records. Sometimes a very short power outage (0.5 to 2 second range) can cause havoc with Insteon devices. The power supply starts to bleed off but power is restore before the device completely shuts down. A complete lose of power for a minute or more is much better. Could also be the PLM is near its end of life. If the problem was limited to the I/O Linc sensors I do not have a good explanation. The PLM can fill with duplicate and outdated link records making adding new links impossible but this does not usually affect links which have already been added and working. Something to watch to see if it happens again. If it surfaces again I would look for other devices having similar issues because the PLM is having problems with its link database.

grossmd Is it that the I/O Linc Sensor state changes are sometimes missed or they never change (ignoring Query) when watching them through the Admin Console? Are the I/O Linc Sensors the only thing that does not present state changes to the Admin Console? If they never change in the Admin Console look for a link record problem, most likely in the PLM if all three I/O Lincs have the same situation. The PLM link database can be rebuilt using File | Restore Modem (PLM). There could also be a comm. problem if the Sensor state changes are intermittent. A quick check of comm. quality to the garage is to run Tools | Diagnostics | Event Viewer at LEVEL 3. Issue a Query a few times and watch the Hops Left=x count. Hops Left=2 is best, Hops Left=0 is worst. A consistently changing Hops Left=x count from Query to Query usually means comm. issues.

gviliunas Great point! That is a way to get the On command to turn something Off and the Off command to turn the same thing On.

The KPL is linked to the FanLinc (red wire on KPL is capped), ON/OFF buttons linked to the FanLinc Light node, buttons A,B,C,D linked to the FanLinc Motor node. Assuming the FanLinc is installed in the shroud of the Fan, unswitched power must be connected to the Fanlinc. All power to the Fan Light and Fan Motor come through the FanLinc. The FanLinc is just like a KPL or SwitchLinc, they are supplied with unswitched power (Line and Neutral) all the time. I found it best to never tell the spouse the real story. Facts just get in the way. I have some standard electrical switches that provide power to InLineLincs in outside floods. The standard switches were there controlling the old floods before converting to Insteon. I put a small Red sticker on the up side of the face plate to remind me to never turn the switch Off. The same thing could be done if you want a way to shut off power to the FanLinc. There is no reason to be more concerned about a FanLinc than all the KPLs, SwitchLincs, OutletLincs etc that have unswitched power. That is what circuit breakers are for.