thruster999

Anything new? We gonna get a UD PLM?

Hello Below are the programs I wrote to deal with my Bathroom Light and different length timeouts to deal with specific situtations. I also use a Motion Sensor and a Triggerlinc. NOTE: My Motion Sensor is setup to be always ON (ON Commands only), to detect as Motion is Sensed. IOW I have programed timers. I use the Motion Sensor to detect initial presence in the room and the TriggerLinc to determine if the Bathroom Door has been closed at some point. The Motion Detection programs are also used for FAN timers in the Bathroom as well. So - this is what it does 1. If the Batroom door is not closed (detected w Triggerlinc) a variable short timer is tiggered on movement. So if you walk in and out quick, ie you took a leak and left - the timer is short 2. If the door is closed after exiting, the timer remains short 3. If there is motion in the bathroom and the door is closed, you are taking a dump or putting on makup, a long timer is activated 4. The long timer is deactivated when you leave the room, regardless of the length of time you are in the bathroom, and a short timer is reactivated ie You open the door and leave. First Setup an "empty" program call 'Motion Bathroom' which will be set to True when there is motion sensed in the bathroom Setup a State variable called Door_Closed_Bathroom which is set to 1 when Triggerlinc is Closed, and 0 when Open (you have to write this program) Motion Detected Program: If Control 'Bathroom-Sensor' is switched On And Program 'Motion Bathroom' is False Then Run Program 'Motion Bathroom' (Then Path) Else - No Actions - (To add one, press 'Action') ============================ Reset Bathroom Motion Program: (All timers are FALSE ie have timed out because there is no more motion - Set Motion Bathroom to False) If Program 'Timer Motion Bathroom Default' is False And Program 'Timer Motion Bathroom Overide' is False Then Wait 10 seconds Set 'Bathroom Light' Off Run Program 'Motion Bathroom' (Else Path) Else - No Actions - (To add one, press 'Action') ================================= Timer Programs Timer Motion Bathroom Default: Overide is Off, iow Door is not closed, short timer If ( $Door_Closed_Bathroom is 0 And ( Control 'Bathroom-Sensor' is switched On Or Status 'Bathroom Light' is not Off ) ) Or ( Status 'Bathroom Light' is not Off And $Door_Closed_Bathroom is 1 ) Then Wait 2 minutes and 15 seconds Run Program 'Timer Motion Bathroom Default' (Else Path) Else - No Actions - (To add one, press 'Action') =========================================== Timer Motion Bathroom Overide: Motion is detected while you are in the bathroom after the door has been closed - turn the long timer on If $Door_Closed_Bathroom is 1 And Control 'Bathroom-Sensor' is switched On Then Stop program 'Timer Motion Bathroom Default' Run Program 'Timer Motion Bathroom Default' (Else Path) Wait 1 hour Run Program 'Timer Motion Bathroom Overide' (Else Path) Else - No Actions - (To add one, press 'Action') BTW with these programs its easy to add Fan Timers and an Overide (ie I double tap the lights) keeping the lights on whether the door is open or not. Also I kept this example simple with only two timers. I actually have 4 for different times of the day. For example I have a slightly longer timer than the Default timer for morning prep. Just make sure to make sure these are aslo False when resetting the Motion Detection programs.

Hey guys I've decided to move on. Physically rebuilding these scenes each week doesn't work for our purposes. However I did want to write and say that I think I've received excellent excellent support from you guys and the forum, especially from Lee (and I hope I've been able to contribute as well). You guys have always been very responsive and very helpful. Thank you very much

Hi IOStream These are programs I've been using in my house - for a couple of years now. The examples I'm giving you are for my On Suite Bathroom where the light is a Dimmer controlled by a Motion Sensor. IOW I've set up a scene where the Motion Sensor is the Controller and the Dimmer is the Responder. And based on the time of Day or specific events the Light's Brightness Level and Ramp Rate are modified. For Instance: While the house is sleeping the light level is low and the ramp rate is slow - for those late night bathroom trips - easy on the eyes. During Breakfast, or after the house wakes up, the brightness level is back to normal(100%) but the ramp rate is slow - since your're still waking up. At night, after sunset, bring up the lights to 100% immediately - until the house goes to sleep. Program: Bathroom - House Asleep. So basically, everyone has gone to sleep an there has been no motion in the house for a few hours. So the House goes to 'Sleep'. In my case 'VAR Bedtime-Main Floor' is a program set to TRUE when these things occur. Or just go by time. ie 12am The light is set to a low brightness level and slower ramp rate. For those "midnight runs" If Program 'VAR Bedtime-Main Floor' is True Then In Scene '05.MB.Master.Bedroom / MB Toilet-Sensor' Set '05.MB.Master.Bedroom / MB Toilet Main' 6.5 Sec (Ramp Rate) In Scene '05.MB.Master.Bedroom / MB Toilet-Sensor' Set '05.MB.Master.Bedroom / MB Toilet Main' 25% (On Level) Else - No Actions - (To add one, press 'Action') ========= Program: Bathroom - Breakfast In my case 'VAR Breakfast' is set to true when people wake-up in the morning and set off certain sensors. Or just set a time: ie 7am - 9am You get ready for work, or whatever now, but you are still waking up. That's why I decided to turn the lights on full but slowly. If Program 'VAR Breakfast' is True Then In Scene '05.MB.Master.Bedroom / MB Toilet-Sensor' Set '05.MB.Master.Bedroom / MB Toilet Main' 8.5 Sec (Ramp Rate) In Scene '05.MB.Master.Bedroom / MB Toilet-Sensor' Set '05.MB.Master.Bedroom / MB Toilet Main' 100% (On Level) Else - No Actions - (To add one, press 'Action') ===== Here it's during the day and since I do have some sunlight coming into the onsuite next to the bathroom I don't have the light coming on to 100% btw 'VAR Night Time' is TRUE between sunset and sunrise If Program 'VAR Breakfast' is False And Program 'VAR Night Time' is False Then In Scene '05.MB.Master.Bedroom / MB Toilet-Sensor' Set '05.MB.Master.Bedroom / MB Toilet Main' 4.5 Sec (Ramp Rate) In Scene '05.MB.Master.Bedroom / MB Toilet-Sensor' Set '05.MB.Master.Bedroom / MB Toilet Main' 75% (On Level) Else - No Actions - (To add one, press 'Action') ====== Program Bathroom - Evening It's after sunset and everyone is up If Program 'VAR Night Time' is True And Program 'VAR Bedtime-Main Floor' is False Then In Scene '05.MB.Master.Bedroom / MB Toilet-Sensor' Set '05.MB.Master.Bedroom / MB Toilet Main' 0.1 Sec (Ramp Rate) In Scene '05.MB.Master.Bedroom / MB Toilet-Sensor' Set '05.MB.Master.Bedroom / MB Toilet Main' 100% (On Level) Else - No Actions - (To add one, press 'Action')

Hello Below are the programs I wrote to deal with my Bathroom Fan. 1. The Fan does not come on unless the Bathroom Door has been closed at some point (it does not have to stay closed) 2. The Fan only comes on if you've spent enough time in the bathroom to justify it (if you know what I mean 3. If you've been in there for a long time (ie bathing or showering) the fan stays on an extra amount of time. 4. The Fan will remain on for a variable time, after you've exited, based on the amount of time you spent in there. I use a Motion Sensor to detect initial presence and a TriggerLinc to determine if the Bathroom Door has been closed at some point. The Motion Sensor is also the Controller for a light scene in the Bathroom. Program: Bathroom Fan Triggered So with this program someone has triggerred the motion sensor and shut the door. If they are in there longer than 2min 45secs the Fan is turned on. Why turn it on if you're in there for a quick pee? 'SF Bath Door Closed Trigger' is a Boolean trigger (TRUE/FALSE) based on the TriggerLinc Note: If the Door is not shut, ie your wife is putting on makeup, the light comes on but the Fan does not. If Status '06.SF.Beds.Bath / SF Bathroom Main' > 10% And Program 'SF Bath Door Closed Trigger' is True Then Wait 2 minutes and 45 seconds Set '06.SF.Beds.Bath / SF Bathroom Fan' On Else - No Actions - (To add one, press 'Action') Program Bathroom Fan On After Exit So now that the Fan is on, leave it on until the person leaves plus add an additional 6 minutes (or whatever you want) and give it a chance to simmer down in there Note: 'VAR Shower Fan Triggered' is another Boolean Program that is set to TRUE only is you've spent an extra long time in the bathroom (ie a shower) and is used in the 2 last programs below to run the Fan even longer. Longer, for steam etc If Status '06.SF.Beds.Bath / SF Bathroom Main' is Off And Status '06.SF.Beds.Bath / SF Bathroom Fan' is On And Program 'VAR Shower Fan Triggered' is False Then Wait 6 minutes Set '06.SF.Beds.Bath / SF Bathroom Fan' Off Else - No Actions - (To add one, press 'Action') These programs below are pretty much identical as the ones above however they determine if a longer fan on duration is required because of a shower or bath etc Program: Shower Fan Triggerred This program will be triggrred at the same time as the program 'Bathroom Fan Triggered'. However it doesn't turn on the Fan. It only determines if the Fan should be left on longer based on the amount of time spent in the bathroom. So, if you've been in the bathroom, with the door closed, for at least 11min trigger the Shower duration. If Status '06.SF.Beds.Bath / SF Bathroom Fan' is On And Program 'SF Bath Door Closed Trigger' is True Then Wait 11 minutes Run Program 'VAR Nicks Shower Fan Triggered' (Then Path) Else - No Actions - (To add one, press 'Action') Program: Shower Fan On After Exit Ok - the fan is already on and there's been a presence in the bathroom for at least 11min. Run the fan for 13 min instead of 6, but after the person has left. Again Note: You don't need to be present the entire time for the fan to come on or stay on. All the triggers have to be triggerred. If Status '06.SF.Beds.Bath / SF Bathroom Main' is Off And Status '06.SF.Beds.Bath / SF Bathroom Fan' is On And Program 'VAR Shower Fan Triggered' is True Then Wait 13 minutes Set '06.SF.Beds.Bath / SF Bathroom Fan' Off Run Program 'VAR Nicks Shower Fan Triggered' (Else Path) Else - No Actions - (To add one, press 'Action')

Hi Michel and Lee The firmware I'm using is 3.1.12 and the backups I've restored were also using 3.1.12. To answer your questions Michel 1) The On and Off status is reported correctly after the issue occurs. 2) I have experienced the green icon (and did the restore or write updates to device) but most of the time this has occurred there is no green icon. Everything appears normal until I click on the Motion Sensor within the scene (as the controller), the responder always shows 0% brightness level and a 9m ramp rate. This always happens when the issue occurs. Thanks again

Hi Michel I haven't been restoring the all my devices. Only those effected. The problem is though this issue occurs weekly, and a different motion scene is involved every week. So basically, I have to restore at least one different motion scene every week - which is frustrating. I took LeeGs advice. Since just restoring either the Controller or the Responder or Both does not work I Delete the Controller and Responder altogether, and then re-add the device to the ISY and then setup the scene again (big pain!). However, now restoring an old back appears to fix the issue. More importantly, I provided ISY links table data in my previous posts and it appears that the table data gets messed up somehow. After I do a restore the links table data is back to the way it should be and the scene works again. That's why I think this is an ISY issue. Maybe I'm describing it incorrectly when using the word "link" but it it looks like something is happening where the ISY cannot communicate properly with the devices in the scene anymore and instead of changing ramp speed and brightness levels it errors out - at least until a backup is restored or I go thru the process I described above. Another reason I think it's the ISY is because it only occurs in notion scenes where I adjust the brightness levels. 2/3 of my setup are lights and scenes that do not involve adjusting the brightness level and I don't experience any issues with any of those scenes or devices (which includes thermostats, dimmers, dual band dimmers, relays, remote sensors, appliance lincs, lamplincs, remote lincs etc) Thanks

Hi Michel I think there was some confusion after my last post. I haven't had issues with KPLs. The thread was about lost links with Dimmers and Relay switches within a scene that also contains a motion sensor. Also, whenever I've experienced the issue, the switch still turns off and on based on activation or de-activation of the motion sensor, it's just that the light level and ramp rates are lost and can't be reset. I experience the lost link error messages described in the thread. So just to confirm this thread has nothing to do with KPLs. Anyway, I've again experienced this issue again today. I ran "Restore Device" which appeared to run all the way through, properly. However this did not fix the issue. Then, based on an earlier post, I ran a Restore of one of my backups. This fixed the issue. So based on this and the fact that the Motion Sensors still turn the lights on and off - wouldn't this suggest the issue is with the ISY and not the switches? As soon as I restore a known good backup the links are restored and again programs setting the ramp rate and brightness levels are succesful. I can also set them manually. Thanks

when you say "restore" do you mean just to run *restore device* or remove the KPL altogether and then add it back to the ISY and the scene? Thanks

Hi Michel A couple of things I thought were relevant I've never had any issues (programs, setting etc) with my thermostats. The only issue has been with the lost links in the motion scenes. Today I restored my ISY with a backup I made a few weeks ago. After I did that, all of the motion scenes with the issues I've been describing were restored to the original state and working properly. To confirm this I'll try it again when the issue occurs again and report back to you. Thanks

They are all V2 Thanks

Hi Michel Yes I do. I have 4 Thermostats. 2 1900s and 2 1800s The 2 1900s are used to to set and track ambient heat. One on my first floor and one on the second floor. The 2 1800s are used for infloor heating. This is important because both of these each use a remote battery operated heat sensor to track the heat on my floors. btw I have never experienced any issues with my thermostats Thanks

Hey guys Any word about this issue? Have you been able to replicate it? I'm still having to restore a set of links at least once a week and its getting to be very tiresome . I believe the only things that might not be typical about my setup is that I have quite a few scenes with a motion sensor as a controller and that I modify these scenes (brightness level) 3 or 4 times throughout the day - Actually I'm only assuming that this is not typical. Thanks in advance.

Hello Michel Yes it does has BEEP support Thanks

Hello ISY Team I can confirm that with 3.1.2 you can now adjust LED brightness on Dimmers and Relays - but not with Dual Band Dimmers thanks

Wow! Great catch The first address, 13.EF.5A, is my Dining Room Sensor which is used in a different motion scene altogether. 13.ED.96 is the correct address for the correct sensor, my laundry room sensor. This reminds me of an earlier post I made a few months ago where I described spontaneous linking that was being done - ie all of a sudden my hallway sensor would trigger on my dining room lights (and hallway lights) when I never linked them etc. This issue was fixed with new firmware releases. Anyway, to answer your question the only system I have is the ISY-99i. I don't have anything else at all that would be modifying devices or scenes. I've attached (below) the only ISY Programs that adjust my Laundry motion scene - remember there are two responders. If Program 'VAR Breakfast' is True And Program 'VAR Sunlight in Laundry' is False Then Set '01.MF.Den.Front / Laundry' Query Wait 1 minute (Random) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry' 4.5 Sec (Ramp Rate) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry' 100% (On Level) Wait 1 minute (Random) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry Entrance AP' 4.5 Sec (Ramp Rate) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry Entrance AP' 70% (On Level) Else - No Actions - (To add one, press 'Action') ++++++++++++++++++++++++ If Program 'VAR Breakfast' is False And Program 'VAR Night Time' is False And Program 'VAR Sunlight in Laundry' is False Then Set '01.MF.Den.Front / Laundry' Query Wait 1 minute (Random) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry' 4.5 Sec (Ramp Rate) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry' 100% (On Level) Wait 1 minute (Random) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry Entrance AP' 0% (On Level) Else - No Actions - (To add one, press 'Action') ++++++++++++++++++++++++ If Program 'VAR Breakfast' is False And Program 'VAR Night Time' is False And Program 'VAR Sunlight in Laundry' is True Then Set '01.MF.Den.Front / Laundry' Query Wait 1 minute (Random) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry' 0% (On Level) Wait 1 minute (Random) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry Entrance AP' 0% (On Level) Else - No Actions - (To add one, press 'Action') ++++++++++++++++++++++++ If Program 'VAR Night Time' is True And Program 'VAR Late Evening' is False Then Set '01.MF.Den.Front / Laundry' Query Wait 1 minute (Random) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry' 0.1 Sec (Ramp Rate) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry' 100% (On Level) Wait 1 minute (Random) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry Entrance AP' 0.1 Sec (Ramp Rate) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry Entrance AP' 100% (On Level) Else - No Actions - (To add one, press 'Action') ++++++++++++++++++++++++ If Program 'VAR Late Evening' is True Then Set '01.MF.Den.Front / Laundry' Query Wait 1 minute (Random) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry' 4.5 Sec (Ramp Rate) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry' 35% (On Level) Wait 1 minute In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry Entrance AP' 4.5 Sec (Ramp Rate) In Scene '01.MF.Den.Front / Laundry-Sensor' Set '01.MF.Den.Front / Laundry Entrance AP' 30% (On Level) Else - No Actions - (To add one, press 'Action')

Hello Lee and Michel Thank you very much for your help Just to clarify Michel - this scene has two Responders. And only one of the links was blown away. When I went to restore the device, in my last description, it wasn't the Controller with the issue, it was the Dual Band Dimmer Responder. When I had to rebuild the scene I'm forced to do it manually (by pressing the set button on the Sensor) by removing the Controller and Responders from the scene and then re-adding them. Huge pain in the a$$ doing this weekly. Also, it is a Program that is adjusting the brightness level on the Responders based on the status of DUSK/DAWN on the Controller - Motion Sensor. Anyway, I've run the tests again (below) and as you can see all the links are there again. My question was why? Why are these links to Controllers that are to Motion Sensors blown away by my ISY? If there is an issue writing to the responder then why not just abandon the write instead of blowing the link away? btw I have 3 Dual Band Dimmers and 2 Access points on this floor including the Dual Band Dimmer that had the issue in the data I've provided. Again, thanks very much for the help guys I ran a program that adjusts the brightness level and ramp rate of the two responders: Fri 04/08/2011 11:47:20 PM : [ Time] 23:47:19 0(0) Fri 04/08/2011 11:47:20 PM : [iNST-ACK ] 02 62 12.53.A8 0F 19 00 06 LTSREQ (LIGHT) Fri 04/08/2011 11:47:20 PM : [iNST-SRX ] 02 50 12.53.A8 13.22.8F 2B 3A 00 (00) Fri 04/08/2011 11:47:20 PM : [standard-Direct Ack][12.53.A8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:47:46 PM : [12 53 A8 1 ] Link 4 : 0FD8 [A20113ED96001A00] Saving [............1A..] Fri 04/08/2011 11:47:46 PM : [All ] Writing 1 bytes to devices Fri 04/08/2011 11:47:46 PM : [12 53 A8 1 ] Using engine version i1 for 'Laundry' Fri 04/08/2011 11:47:46 PM : [12 53 A8 1 ] Link 4 : 0FD8 [A20113ED96001A00] Writing [............1A..] Fri 04/08/2011 11:47:46 PM : [iNST-ACK ] 02 62 12.53.A8 0F 28 0F 06 SET-MSB(0F) Fri 04/08/2011 11:47:47 PM : [iNST-SRX ] 02 50 12.53.A8 13.22.8F 2B 28 0F SET-MSB(0F) Fri 04/08/2011 11:47:47 PM : [standard-Direct Ack][12.53.A8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:47:47 PM : [iNST-ACK ] 02 62 12.53.A8 0F 2B DE 06 PEEK (DE) Fri 04/08/2011 11:47:47 PM : [iNST-SRX ] 02 50 12.53.A8 13.22.8F 2B 2B 1F PEEK (1F) Fri 04/08/2011 11:47:47 PM : [standard-Direct Ack][12.53.A8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:47:47 PM : [iNST-ACK ] 02 62 12.53.A8 0F 29 1A 06 POKE (1A) Fri 04/08/2011 11:47:47 PM : [iNST-SRX ] 02 50 12.53.A8 13.22.8F 2B 29 1A POKE (1A) Fri 04/08/2011 11:47:47 PM : [standard-Direct Ack][12.53.A8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:47:48 PM : [12 53 A8 1 ] Link 4 : 0FD8 [A20113ED96591A00] Saving [..........59....] Fri 04/08/2011 11:47:48 PM : [All ] Writing 1 bytes to devices Fri 04/08/2011 11:47:48 PM : [12 53 A8 1 ] Using engine version i1 for 'Laundry' Fri 04/08/2011 11:47:48 PM : [12 53 A8 1 ] Link 4 : 0FD8 [A20113ED96591A00] Writing [..........59....] Fri 04/08/2011 11:47:48 PM : [iNST-ACK ] 02 62 12.53.A8 0F 28 0F 06 SET-MSB(0F) Fri 04/08/2011 11:47:48 PM : [iNST-SRX ] 02 50 12.53.A8 13.22.8F 27 28 0F SET-MSB(0F) Fri 04/08/2011 11:47:48 PM : [standard-Direct Ack][12.53.A8-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 04/08/2011 11:47:48 PM : [iNST-ACK ] 02 62 12.53.A8 0F 2B DD 06 PEEK (DD) Fri 04/08/2011 11:47:48 PM : [iNST-SRX ] 02 50 12.53.A8 13.22.8F 2B 2B 00 PEEK (00) Fri 04/08/2011 11:47:49 PM : [standard-Direct Ack][12.53.A8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:47:49 PM : [iNST-ACK ] 02 62 12.53.A8 0F 29 59 06 POKE (59) Fri 04/08/2011 11:47:49 PM : [iNST-SRX ] 02 50 12.53.A8 13.22.8F 2B 29 59 POKE (59) Fri 04/08/2011 11:47:49 PM : [standard-Direct Ack][12.53.A8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:48:47 PM : [17 F3 EF 1 ] Link 4 : 0FD8 [A20113ED96001A00] Saving [............1A..] Fri 04/08/2011 11:48:47 PM : [All ] Writing 1 bytes to devices Fri 04/08/2011 11:48:47 PM : [17 F3 EF 1 ] Using engine version i1 for 'Laundry Entrance AP' Fri 04/08/2011 11:48:47 PM : [17 F3 EF 1 ] Link 4 : 0FD8 [A20113ED96001A00] Writing [............1A..] Fri 04/08/2011 11:48:47 PM : [iNST-ACK ] 02 62 17.F3.EF 0F 28 0F 06 SET-MSB(0F) Fri 04/08/2011 11:48:47 PM : [iNST-SRX ] 02 50 17.F3.EF 13.22.8F 2B 28 0F SET-MSB(0F) Fri 04/08/2011 11:48:47 PM : [standard-Direct Ack][17.F3.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:48:47 PM : [iNST-ACK ] 02 62 17.F3.EF 0F 2B DE 06 PEEK (DE) Fri 04/08/2011 11:48:47 PM : [iNST-SRX ] 02 50 17.F3.EF 13.22.8F 2B 2B 1F PEEK (1F) Fri 04/08/2011 11:48:47 PM : [standard-Direct Ack][17.F3.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:48:47 PM : [iNST-ACK ] 02 62 17.F3.EF 0F 29 1A 06 POKE (1A) Fri 04/08/2011 11:48:48 PM : [iNST-SRX ] 02 50 17.F3.EF 13.22.8F 2B 29 1A POKE (1A) Fri 04/08/2011 11:48:48 PM : [standard-Direct Ack][17.F3.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:48:49 PM : [17 F3 EF 1 ] Link 4 : 0FD8 [A20113ED964C1A00] Saving [..........4C....] Fri 04/08/2011 11:48:49 PM : [All ] Writing 1 bytes to devices Fri 04/08/2011 11:48:49 PM : [17 F3 EF 1 ] Using engine version i1 for 'Laundry Entrance AP' Fri 04/08/2011 11:48:49 PM : [17 F3 EF 1 ] Link 4 : 0FD8 [A20113ED964C1A00] Writing [..........4C....] Fri 04/08/2011 11:48:49 PM : [iNST-ACK ] 02 62 17.F3.EF 0F 28 0F 06 SET-MSB(0F) Fri 04/08/2011 11:48:49 PM : [iNST-SRX ] 02 50 17.F3.EF 13.22.8F 2B 28 0F SET-MSB(0F) Fri 04/08/2011 11:48:49 PM : [standard-Direct Ack][17.F3.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:48:49 PM : [iNST-ACK ] 02 62 17.F3.EF 0F 2B DD 06 PEEK (DD) Fri 04/08/2011 11:48:49 PM : [iNST-SRX ] 02 50 17.F3.EF 13.22.8F 2B 2B 00 PEEK (00) Fri 04/08/2011 11:48:49 PM : [standard-Direct Ack][17.F3.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/08/2011 11:48:49 PM : [iNST-ACK ] 02 62 17.F3.EF 0F 29 4C 06 POKE (4C) Fri 04/08/2011 11:48:49 PM : [iNST-SRX ] 02 50 17.F3.EF 13.22.8F 2B 29 4C POKE (4C) Fri 04/08/2011 11:48:49 PM : [standard-Direct Ack][17.F3.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Device Link Table and Compare of the Responder that had issues but after the re-build: 0FF8 : A2 00 13.22.8F FF 1F 00 0FF0 : E2 01 13.22.8F FF 1F 01 0FE8 : A2 11 13.22.8F FF 1F 00 0FE0 : A2 2B 13.22.8F FF 1F 00 0FD8 : A2 01 13.ED.96 4C 1A 00 0FD0 : 00 00 00.00.00 00 00 00 [identical]0FF8 : A2 00 13.22.8F FF 1F 00 [identical]0FF0 : E2 01 13.22.8F FF 1F 01 [identical]0FE8 : A2 11 13.22.8F FF 1F 00 [identical]0FE0 : A2 2B 13.22.8F FF 1F 00 [identical]0FD8 : A2 01 13.ED.96 4C 1A 00 [identical]0FD0 : 00 00 00.00.00 00 00 00

Hi Lee and the ISY team well, this is my weekly device link issue with scenes that have a motion sensor. This time it's with my Laundry room. Again for whatever reason the ISY link between the sensor and the responder is lost or corrupted. As with the last two cases I posted: I get the little green icon next to the responder but cannot manually write updates to the device. When I manually try to adjust the scene I get the following error message: "Failed writing device link (Laundry-Sensor) [-200000/-51] The Scene still works as far as ON/OFF goes however the ramp rate and brightness levels cannot be adjusted In order to get the scene to work again I have to completelty, and manually rebuild the scene with the motion sensor again. IOW the issue is identical to the other two examples I provided earlier. This is the event table I ran after the issue occurred: The Controller is a motion sensor with the address 13 ED 96 The First responder is a regualar dimmer 12 53 A8 - this device did not experience the issue The Second Responder is a Dual Band Dimmer 17 F3 EF 1 (it failed to be changed) Fri 04/08/2011 01:06:17 PM : [All ] Writing 1 bytes to devices Fri 04/08/2011 01:06:17 PM : [12 53 A8 1 ] Link 1 : 0FF0 [A20113ED96001A00] Writing [..........00....] Fri 04/08/2011 01:06:21 PM : [ 13 EF 5A 1] DON 1 This is what I got when I ran the Device Links Table for the device that failed 0FF8 : A2 00 13.22.8F FF 1F 00 0FF0 : A2 01 13.EF.5A 51 0A 00 0FE8 : A2 14 13.22.8F FF 1F 00 0FE0 : A2 3B 13.22.8F 51 0A 00 0FD8 : 00 01 13.22.8F FF 1F 01 This is when I ran Compare [identical] 0FF8 : A2 00 13.22.8F FF 1F 00

Hello Lee You're correct on all counts. The SF Pool Table AP is a Dual Band Dimmer and is the Responder. And the program that is run reduces the Light Level from 100% to 30%. The Dimmer was set by another program to 100%, successfully, at Sunset a number of hours earlier. And also, because the new light level didn't take, the earlier settings of 100% light level were still the effect with the current ON/OFF. This afternoon I ran the Device Link Table again. This is what I got: 0FF8 : A2 00 13.22.8F FF 1F 00 0FF0 : E2 01 13.22.8F FF 1F 01 0FE8 : A2 19 13.22.8F 00 1F 00 0FE0 : A2 01 13.F8.CC 00 1F 00 0FD8 : A2 1A 13.22.8F FF 1F 00 0FD0 : A2 26 13.22.8F FF 1F 00 0FC8 : A2 02 11.AC.0D FF 1F 00 0FC0 : 00 00 00.00.00 00 00 00 Then I ran the Compare [identical] 0FF8 : A2 00 13.22.8F FF 1F 00 [identical] 0FF0 : E2 01 13.22.8F FF 1F 01 [identical] 0FE8 : A2 19 13.22.8F 00 1F 00 [identical] 0FE0 : A2 01 13.F8.CC 00 1F 00 [identical] 0FD8 : A2 1A 13.22.8F FF 1F 00 [identical] 0FD0 : A2 26 13.22.8F FF 1F 00 [identical] 0FC8 : A2 02 11.AC.0D FF 1F 00 [ignore] 0FC0 : 00 00 00.00.00 00 00 00 So today it's running perfectly - it's already done a few scene adjustments today with no issues. In fact today ALL of my sensor based scenes are having no issues (as I mentioned earlier, this happens once a week with random sensor scenes). So, it looks likes, as with last nights post re-build links data, the PLM is there, as also the sensor and remotelinc. So wouldn't this suggest that somehow the ISY data is corrupting? As always, thanks again Lee

Hi LeeG Thanks again for your help! Well luckily (actually unluckily) I've experirnced another failure tonight. My Pool Table Room - It has not experienced this issue since December. So it's been a while for this one. All the same issues as with my On-suite Motion Scene. The light level is at 0% and the ramp rate is displayed as 9min. ON/OFF still works but the scene can't be adjusted. To answer your first question there was an icon beside the failed switch. A small green arrow with binary code in it. I did a Query and the icon was cleared after the Query was complete. I then went to manually adjust the Scenes light level via the Sensor Scene and received the following error message - same as before. Failed reading device link (SF Pool Table) [-200000/-5] Subscriber didn't reply to event:1 I made several attempts and either got the above message or 'Failed Request' and the switch does not adjust. BTW the devices in the Motion Scene are called and addressed: SF Pool Table AP 18.03.EF SF Pool Table-Sensor 13.F8.CC (Second Floor Pool Table Room) The Responder is a Dual Band Dimmer. My Second floor, 1500 sq ft, has 2 dual band dimmers and an additional 2 access points installed. 2 on each phase. Anyway it appears to have failed when a program that runs at 10:00PM adjusts the dimmers light level and ramp rate via an "Adjust Scene" via the Motion Sensor (just like the earlier issue). I ran the tests you said I should run while the scene was still broken and this is what I got: The Event Log Post Fail: Thu 03/31/2011 10:56:28 PM : [ Time] 22:56:32 0(0) Thu 03/31/2011 10:56:28 PM : [iNST-ACK ] 02 62 18.03.EF 0F 19 00 06 LTSREQ (LIGHT) Thu 03/31/2011 10:56:29 PM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B CA 66 (66) Thu 03/31/2011 10:56:29 PM : [standard-Direct Ack][18.03.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/31/2011 10:57:03 PM : [All ] Writing 0 bytes to devices Thu 03/31/2011 10:57:03 PM : [All ] Writing 0 bytes to devices Thu 03/31/2011 10:57:03 PM : [All ] Writing 0 bytes to devices Thu 03/31/2011 10:57:03 PM : [All ] Writing 0 bytes to devices The Device Links Table Post Fail Device Links Table : SF Pool Table AP / 18 3 EF 1 0FF8 : A2 00 13.22.8F FF 1F 00 0FF0 : A2 01 13.F8.CC FF 1F 00 0FE8 : A2 02 11.AC.0D FF 1F 00 0FE0 : A2 19 13.22.8F FF 1F 00 0FD8 : A2 1A 13.22.8F FF 1F 00 0FD0 : A2 26 13.22.8F FF 1F 00 0FC8 : E2 01 13.22.8F FF 1F 01 0FC0 : 00 00 00.00.00 00 00 00 11.AC.0D is a RemoteLinc and I'm assuming that 13.22.8F is my PLM because I don't have any devices with that address in my device list. I tried to run Compare (twice) but the UI hung. So I rebuilt the scene - removed both devices from the scene, "Restore"d them, and put them back in. I ran the program again and it worked perfect. Here's the log from the event viewer after running the same program but this time after I did the re-build. The Event Log Post Re-build Fri 04/01/2011 12:51:28 AM : [ Time] 00:51:29 1(0) Fri 04/01/2011 12:51:29 AM : [iNST-ACK ] 02 62 18.03.EF 0F 19 00 06 LTSREQ (LIGHT) Fri 04/01/2011 12:51:29 AM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B E6 00 (00) Fri 04/01/2011 12:51:29 AM : [standard-Direct Ack][18.03.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/01/2011 12:52:18 AM : [18 3 EF 1 ] Link 2 : 0FE8 [A20113F8CC4C1A00] Saving [............1A..] Fri 04/01/2011 12:52:18 AM : [All ] Writing 1 bytes to devices Fri 04/01/2011 12:52:18 AM : [18 3 EF 1 ] Using engine version i1 for 'SF Pool Table AP' Fri 04/01/2011 12:52:18 AM : [18 3 EF 1 ] Link 2 : 0FE8 [A20113F8CC4C1A00] Writing [............1A..] Fri 04/01/2011 12:52:18 AM : [iNST-ACK ] 02 62 18.03.EF 0F 28 0F 06 SET-MSB(0F) Fri 04/01/2011 12:52:18 AM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B 28 0F SET-MSB(0F) Fri 04/01/2011 12:52:18 AM : [standard-Direct Ack][18.03.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/01/2011 12:52:18 AM : [iNST-ACK ] 02 62 18.03.EF 0F 2B EE 06 PEEK (EE) Fri 04/01/2011 12:52:19 AM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B 2B 1A PEEK (1A) Fri 04/01/2011 12:52:19 AM : [standard-Direct Ack][18.03.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/01/2011 12:52:19 AM : [18 3 EF 1 ] Link 2 : 0FE8 [A20113F8CC4C1A00] Saving [..........4C....] Fri 04/01/2011 12:52:19 AM : [All ] Writing 1 bytes to devices Fri 04/01/2011 12:52:19 AM : [18 3 EF 1 ] Using engine version i1 for 'SF Pool Table AP' Fri 04/01/2011 12:52:19 AM : [18 3 EF 1 ] Link 2 : 0FE8 [A20113F8CC4C1A00] Writing [..........4C....] Fri 04/01/2011 12:52:19 AM : [iNST-ACK ] 02 62 18.03.EF 0F 28 0F 06 SET-MSB(0F) Fri 04/01/2011 12:52:19 AM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B 28 0F SET-MSB(0F) Fri 04/01/2011 12:52:19 AM : [standard-Direct Ack][18.03.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/01/2011 12:52:19 AM : [iNST-ACK ] 02 62 18.03.EF 0F 2B ED 06 PEEK (ED) Fri 04/01/2011 12:52:20 AM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B 2B 4C PEEK (4C) Fri 04/01/2011 12:52:20 AM : [standard-Direct Ack][18.03.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/01/2011 12:52:20 AM : [18 3 EF 1 ] Link 1 : 0FF0 [A21913228F4C1A00] Saving [............1A..] Fri 04/01/2011 12:52:20 AM : [All ] Writing 1 bytes to devices Fri 04/01/2011 12:52:20 AM : [18 3 EF 1 ] Using engine version i1 for 'SF Pool Table AP' Fri 04/01/2011 12:52:20 AM : [18 3 EF 1 ] Link 1 : 0FF0 [A21913228F4C1A00] Writing [............1A..] Fri 04/01/2011 12:52:20 AM : [iNST-ACK ] 02 62 18.03.EF 0F 28 0F 06 SET-MSB(0F) Fri 04/01/2011 12:52:20 AM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B 28 0F SET-MSB(0F) Fri 04/01/2011 12:52:20 AM : [standard-Direct Ack][18.03.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/01/2011 12:52:20 AM : [iNST-ACK ] 02 62 18.03.EF 0F 2B F6 06 PEEK (F6) Fri 04/01/2011 12:52:21 AM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B 2B 1A PEEK (1A) Fri 04/01/2011 12:52:21 AM : [standard-Direct Ack][18.03.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/01/2011 12:52:21 AM : [18 3 EF 1 ] Link 1 : 0FF0 [A21913228F4C1A00] Saving [..........4C....] Fri 04/01/2011 12:52:21 AM : [All ] Writing 1 bytes to devices Fri 04/01/2011 12:52:21 AM : [18 3 EF 1 ] Using engine version i1 for 'SF Pool Table AP' Fri 04/01/2011 12:52:21 AM : [18 3 EF 1 ] Link 1 : 0FF0 [A21913228F4C1A00] Writing [..........4C....] Fri 04/01/2011 12:52:21 AM : [iNST-ACK ] 02 62 18.03.EF 0F 28 0F 06 SET-MSB(0F) Fri 04/01/2011 12:52:21 AM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B 28 0F SET-MSB(0F) Fri 04/01/2011 12:52:21 AM : [standard-Direct Ack][18.03.EF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 04/01/2011 12:52:21 AM : [iNST-ACK ] 02 62 18.03.EF 0F 2B F5 06 PEEK (F5) Fri 04/01/2011 12:52:22 AM : [iNST-SRX ] 02 50 18.03.EF 13.22.8F 2B 2B 4C PEEK (4C) The Device Links Post Re-build 0FF8 : A2 00 13.22.8F FF 1F 00 0FF0 : A2 19 13.22.8F 4C 1A 00 0FE8 : A2 01 13.F8.CC 4C 1A 00 0FE0 : A2 1A 13.22.8F FF 1F 00 0FD8 : A2 26 13.22.8F FF 1F 00 0FD0 : A2 02 11.AC.0D FF 1F 00 0FC8 : 00 01 13.22.8F FF 1F 01 I noticed the last line of all 00's is not there this time And the Compare worked this time: 0FF8 : A2 00 13.22.8F FF 1F 00 0FF0 : A2 19 13.22.8F 4C 1A 00 0FE8 : A2 01 13.F8.CC 4C 1A 00 0FE0 : A2 1A 13.22.8F FF 1F 00 0FD8 : A2 26 13.22.8F FF 1F 00 0FD0 : A2 02 11.AC.0D FF 1F 00 Reported all Identical except the last line was ignored (the PLM I think). Thanks again LeeG!

Hi LeeG I might of made it sound as if this happens often on the same device. It doesn't. This issue occurs once per week, but with different random scenes that have a motion sensor as a Controller. I have 11 scenes with Motion Sensors as the Controller. So today it was my on-suite scene but last week it was my Den and the week before that my Laundry Room. This is the primary reason I don't think its this specific Responder. To answer your questions (btw thanks for your help!) I'm currently using 3.1.1. BUT this issue has been occurring since I purchased my ISY-99i. With so many Motion Sensors now, it's getting onerous rebuilding at least one scene per week. I also want to set up a similar system for my parents and there's no way I can manage this remotely with an issue that demands a manual fix. I'm hoping this is an issue where its info stored with the ISY - and therefore is a bug that can be fixed. Anyway, It's happened with every firmware version I've used. But recently I've noticed the issue only occurs with scenes that have a Motion Sensor as a Controller AND where I adjust scenes (with programs) via the Sensor rather than the Scene. The Switch in question is in the same gang box as a Dual Band Switch and is also 12 feet away from the adjoining closet dual band dimmer - and two additional access points within 40 feet, plus two additional Dual Band Switches within 40 feet all located on the same floor. On this floor I have 3 dual band dimmers and 2 plug in access points and the floor is 1450 sq ft. Since I rebuilt the scene this morning, and ran the diagnostic tools - it runs perfectly (and very quickly) with no errors. In fact all of the scenes do. But for whatever reason, the program that adjusts my on-suite motion scene to a 25% light level / 4.5 second ramp rate (for bedtime so when my wife has to get up and take a pee in the middle of the night ) it crapped out. The on/off continued to work but the scene wasn't adjusted. A program runs in the morning to setup the scene back to 100% light level, it ran when it was supposed to, but the scene wasn't adjusted. So I manually went to adjust them and got the error messages I reported earlier. If I were to guess (dangerous I know) the link between the Responder in the scene is lost and is gone until rebuilt. Thanks

I'm poting here because, rather than in the Communication Issues forum, because I'm hoping there is a simple solution for this issue. From the details below I think you'll agree this cannot be a communication issue but is more likely an issue with my ISY-99i. The issue: In Scenes that only include a Motion Sensor as a Controller and a switch (either a dimmer or relay) as a Responder, the ability to Adjust Scenes errors, is broken, and the scene has to be rebuilt manually to correct the issue. Symtoms: The ON and OFF functionality of the scene still works. However, when a program is run to adjust the scene (ie change the ramp rate and light level of the Responder) nothing occurs, no error is reported. and the scene fails to be adjusted. Ultimately, even though no error is reported the light level and ramp rate are not adjusted. And the scene cannot ever be adjusted again. BTW the program adjusts the scene using the Sensor (ie 'Adjust Scene' Bath-Sensor/Bath Potts Ramp Rate 4.5 second') and not the Scene. If I go to the ISY UI, goto to Motion Scene and click on the Sensor (controller), it reports the responder as having a 9min ramp rate and a 0% light level. This happens every time this issue occurs, regardless of the different motion scenes. Normally I can adjust the scene manually by clicking on the motion sensor Controller in the scene and manually adjust the ramp rate or light level of the Responder. Normally, after the manual adjustment, you can see the Responder being written to and everything works perfect. However, after this issue occurs where the links are lost and the Controller reports 9min/0%, and I manually adjust the ramp rate or light level, one of two errors occur: 1) Failed Request 2) Error - Link cannot be found. Attempted fixes and solution 1) I reboot ISY. This does not correct the Issue. 2) I "Restore Device", separately, the Motion Sensor and the Responder. This also does not fix the issue. 3) I use the drop down menu option 'Restore Link between "Responder" and "Controller". This appears to do something in that the Responder and Controller are being written to however after this occurs the issue still persists. BTW this is a pain in the A$$ because you have to press the set button on the motion sensor to put it into setup mode. 4) I rebuild the link by removing the Controller and Responder from the Scene, "Restore" each device, then setup the scene again with the Motion Sensor as the Controller and the switch as the Responder - This is the only thing I found to work. This is also a pain in the A$$ because you again have to manually put the Sensor into setup mode. Why do I beleive this is an ISY issue and not an INSTEON issue? 1) The error messages I describe above. 2) The ON/OFF functionality still works - IOW that link is still there even after this issue has occured and even when the ISY is turned off. 3) The issue seems to occur only after a program runs to adjust the scene. An attempt is made to write to the Responder and then you can't adjust the scene anymore until the scene is rebuilt. 4) This cannot be a communication issue because it's random. This does not occur repeatedly on any single scene but rather has occurred on most of my motion scenes - it happens overall once per week. Also, 5) The issue that occured that prompted this diatribe was my Onsuite motion scene. There is a Dual Band Switch literally 3 feet away from the Sensor. Another Dual Band Switch 12 feet away in the adjoining closet and two additional access points within 40 feet, plus two additional Dual Band Switches within 40 feet all located on the same floor. 6) Motion Scenes that do not have the Motion Sensor as a Controller (ON OFF run by programs/ Ramp Rate and Light levels adjusted by programs in the Scene rather than motion sensor) this issue has never occured. BUT this is not a preferable setup because program run ON/OFF is slow compared to when using the Motion Sensor to control ON/OFF. So ... Am I correct? Is this a known ISY issue? Or can I do anything to prevent this issue? Thanks very much in advance

Hi Michel Basically all my devices Dimmers Dual Band dimmers And toggles Thanks

Since upgrading I have not been able to adjust LED Brightness Levels. I tried re-installing, and the issue still persists

Hi I noticed that both of these are listed in the hardware list What's the difference?