LeeG

A simple EZFlora Program.. If On Mon, Wed, Fri Time is 6:00:00AM Then Set 'EZFlora' On Wait 40 minutes Set 'EZFlora / EZFlora - 2' On Wait 25 minutes Set 'EZFlora / EZFlora - 3' On Wait 30 minutes Set 'EZFlora / EZFlora - 4' On Wait 20 minutes Set 'EZFlora / EZFlora - 5' On Wait 30 minutes Set 'EZFlora / EZFlora - 6' On Wait 20 minutes Set 'EZFlora / EZFlora - 6' Off Else - No Actions - (To add one, press 'Action')

apostolakisl Have/can you run an event trace to see if two Off messages are flowing.

According to the Last Run Time it was triggered yesterday which also seems odd since there would have been no change in battery status. With it being a simple Program I would delete the Program and see what happens tomorrow morning.

You can delete the other duplicate post. Suggest you post the Program and explain what is not working relative to the specific Program. There are no rules per see except maybe common sense which could mean something different for each Program.

Thanks for the time information. The Motion Sensor has no real time clock, no perception of long periods of time. To have an email sent at 1 AM each day the Program is still running the Repeat every 24 hours. Check the Next Scheduled Run column of the email Program. Then Right click the Program name and select Stop.

The ISY does not communicate with the Motion Sensor when Query is selected. It is used only to change the Low Bat node from On to Off. Is the timestamp on the very first Low Bat email the same as the time of the additional emails? If so that would indicate the Program did not come out of the Repeat loop when the Low Bat node was reset to Off with Query. If different times then something is triggering the Program each time rather than just repeating every 24 hours.

Reboot the ISY to get it out of linking mode. May take twice. Then resolve the router/AV issue that created the situation to begin with. That is only one of various symptoms that will be seen if the blocking issue is not resolved. Kaspersky and Avast are common sources of interfernce. There are posts on the forum that discuss possible solutions when using these products.

As you say, not as elegant but using Scenes to shut off the KPL buttons has been the solution for all these years. Not sure why SmartLabs decided to add the function to KPLs now. It will be very useful when multiple KPLs are controlling a FanLinc, perhaps that was the driving force.

That message often appears when Start Linking has been selected and the Start Linking Popup does not display because of a router/AV issue blocking the push of data from the ISY to the Admin Console. If the popup had displayed there would be a Finish button on the popup and it would be impossible to interact with any other ISY function until the Finish button is pressed. Without the Popup other ISY functions can be accessed resulting in that message because the ISY and the PLM are still in linking mode looking for device identification messages from Set button presses.

You are not seeing the sliders when something other than the KeypadLinc buttons themselves are selected. Selecting one of the RemoteLinc2 buttons will not show sliders for the Secondary KPL buttons. Yes. When the ISY supports turning Off a Secondary KPL button with an On command from another Controller the sliders will be there and all but the object Secondary KPL button can be set to 0% On Level to turn the other buttons Off.

Does the Programs | Summary tab show the Program as running since it would be in an endless repeat loop until the low bat Status changes.

dstanley Yes to running Restore Device on all the SwitchLincs one at a time. Probably a good idea to run on all the devices. A trace of one of my KeypadLincs shows the same situation. As it turns out the old Peek/Poke method continues to work on the one KeypadLinc I tested but it should be using the later I2 method. At this point there is not a good list of all the symptoms that are possible using Peek/Poke so running a Restore Device on each device, one at a time is a good thing to do IMO. The RF only devices such as Motion Sensors and TriggerLincs should not need a Restore Device as they never have supported I1.

bdw72 The FanLinc is supported starting in 3.2.0. 3.2.1 is latest beta and the one that should be installed.

dstanley The solution for now is to Restore Device. You can confirm this by running Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Make an adjustment to the LED Brightness through the Admin Console. If the commands in the event trace are Set MSB,Peek,Poke run Restore Device. Then repeat the LED Brightness change and see if the commands have changed. This is what the commands probably look like now ..... Wed 03/21/2012 03:05:53 PM : [iNST-TX-I1 ] 02 62 16 3F 93 0F 28 02 Wed 03/21/2012 03:05:53 PM : [iNST-ACK ] 02 62 16.3F.93 0F 28 02 06 SET-MSB(02) Wed 03/21/2012 03:05:53 PM : [iNST-SRX ] 02 50 16.3F.93 19.70.06 2B 28 02 SET-MSB(02) Wed 03/21/2012 03:05:53 PM : [standard-Direct Ack][16.3F.93-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Wed 03/21/2012 03:05:53 PM : [iNST-TX-I1 ] 02 62 16 3F 93 0F 2B 64 Wed 03/21/2012 03:05:53 PM : [iNST-ACK ] 02 62 16.3F.93 0F 2B 64 06 PEEK (64) Wed 03/21/2012 03:05:53 PM : [iNST-SRX ] 02 50 16.3F.93 19.70.06 2B 2B FF PEEK (FF) Wed 03/21/2012 03:05:53 PM : [standard-Direct Ack][16.3F.93-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Wed 03/21/2012 03:05:53 PM : [iNST-TX-I1 ] 02 62 16 3F 93 0F 29 80 Wed 03/21/2012 03:05:54 PM : [iNST-ACK ] 02 62 16.3F.93 0F 29 80 06 POKE (80) Wed 03/21/2012 03:05:54 PM : [iNST-SRX ] 02 50 16.3F.93 19.70.06 2B 29 80 POKE (80) This is what they should look like .... Wed 03/21/2012 03:07:57 PM : [INST-TX-I2 ] 02 62 16 3F 93 1F 2E 00 00 03 C8 00 00 00 00 00 00 00 00 00 00 07 Wed 03/21/2012 03:07:57 PM : [iNST-ACK ] 02 62 16.3F.93 1F 2E 00 00 03 C8 00 00 00 00 00 00 00 00 00 00 07 06 (00) Wed 03/21/2012 03:07:57 PM : [iNST-SRX ] 02 50 16.3F.93 19.70.06 2B 2E 00 (00)

"Does initiating a Status, Responding in a program actually trigger the program to check on that device?" If Status does not generate communication with the device. If Status causes a Program to trigger when Status changes. This is true for all If Status, not just Responding option. A Program with an If Status is Responding would trigger when the device goes from not responding to responding.

"Is there a list of new items included since 3.17?" In addition to the links Andy posted the link below goes to the 3.2.1/3.2.0 topic which covers the new function, device support and fixes. viewtopic.php?f=25&t=8309

Michel Only 1100xx messages are these two when adding a non-I2CS FanLinc Sun 2012/03/18 09:11:28 AM System -110022 /CONF/149CE9.REC Sun 2012/03/18 09:11:28 AM System -110012 /CONF/149CE9.REC

In addition to needing V.40 firmware, ISY has to be updated to support the capability. The screen capture below from 3.2.1 shows a Scene with some KPL Secondary buttons and a RemoteLinc2 button as a Controller (highlighted on left as the selected Controller). Note that when the RemoteLinc2 button is selected as the Controller there are no Secondary buttons in the right pane. This is because up until the just released v.40 KPL firmware the KPL did not support turning a Secondary button Off (0% On Level) with an On command so there was no reason to list the Secondary buttons. I did mention in a previous post that the ISY did not yet support turning a Secondary button Off with an On command but want to repeat it so my previous post that said v.40 firmware was needed was not understood as the only thing needed. You would need a KPL with v.40 firmware and some future ISY image that supports that capability. EDIT: when ISY supports turning Off a Secondary KPL button with Scene On the Secondary buttons C,D,E will have sliders displayed so the On Level can be set to 0%. That way when the RemoteLinc2 (or any other Controller) button is pressed On one Secondary button can be turned On and the other Secondary buttons can be turned Off ( with 0% On Level). .

"Shouldn't the 3 other buttons turn off when I set each of them to 0 in the buttons configuration within the scene?" Only if you have KPL v.40 firmware.

All the button grouping and non-toggle mode applies when the KPL button(s) are pressed locally. Those have no control of the button LEDs when the buttons are controlled from another Controller. Until the very latest v.40 KPL firmware a Secondary KPL button could not be turned Off from another Controller with an On command. Most devices can be turned Off with an On command when the responder On level is set to 0%. Secondary KPL buttons were one of the few exceptions often requiring a separate Scene that is used to send an Off command to turn the Secondary button(s) Off. With v.40 firmware it is now possible to turn a Secondary KPL button Off with an On command from another Controller. The ISY does not have support to utilize this feature as yet.

Skripo If all worked that is great. UDI could not recreate what TJF1960 and I were seeing. At the recommendation of UDI I did a Restore Device. That resolved the problem here. Now the Restored device uses I2 as it did under 3.1.17. TJF1960 Suggest trying a Restore Device. That restored the use of I2 for the device in 3.2.1.

bdw72 There is another approach that would not have the potential conflict of the door moving open at the same time the every hour Program is trying to close. During the night time hours trigger a Program when the I/O Linc Sensor turns On and Wait for 1 hour. If the door is closed within that hour the program will trigger again, effectively cancelling the Wait and subsequent close request. If the door remains open for an hour the Wait completes and issues an I/O Linc Relay On to close the door. If From Sunset For 10 hours And Status 'IO Linc1-Sensor' is On Then Wait 1 hour Set 'IO Linc1-Sensor / IO Linc1-Relay' On Else - No Actions - (To add one, press 'Action')

It sounds like there is a pending update to the MS which the ISY tries to do any time it does an update to another device. Put the MS in linking mode, right click the MS node and select Write Updates to Device. That should clear it if it is a pending update.

Change the Program Then statement to some other %. The ISY will not write a value to a device it thinks is already set in the device. I loaded 3.1.17 and it works changing the Local On Level of a SwitchLinc Dimmer.

What ISY firmware is being used? I ran a test on a SwitchLinc Dimmer on 3.2.1. It did not work but there is an issue that was uncovered setting LED Brightness and I think it is affecting setting the Local On Level as well. If on 3.1.17 I would expect it to work. Run Tools | Diagnostics | Event Viewer with Level 3-Device communications event selected. Right click the Program name and select Run Then. Post the event trace which will show the commands executed to change the Local On Level.