Illusion

Confirmed using the UI from the link provided.

When adjusting a device level in a scene, I am unable to get the value to take if I want it to be 0% (off). I have found if I adjust the slider to some arbitrary level other than 0% and then adjust the setting it works. It appears that I have to get the ISY to write a level other than 0% first. Then I can set any level I like including 0%

3 more months. No ghosting on with just the switch in a scene as a controller with no responders. (Other than the PLM I which I assume is considered a responder, even though we do not see it) This brings me to another question. Even without this controller in a scene there is still a link to the PLM right? I am going to now remove the scene from the ISY. So I am going back to the condition that existed when this problem first manifested itself. How is having this device as a controller of a scene with no other devices any different than not having the controller in a scene? In both cases the device has a link to the PLM that does not show up in the GUI, right? When I first add a new device to the ISY a link is setup. If I do nothing else with this device, isn't that the same thing as adding the device as a controller of a scene with nothing else in it? In both cases the device has "scene" links to the PLM that the ISY does not show. Am I understanding this correctly?

since it was the central theme of your first response post?

I am doing highly reliable multi-stage 3-Heat 2-Cool zoning with my ISY. I do not think I am going to be able to help much as I ponied up the $$. Venstar Stats with adapters, Honeywell HZ 432 zone controller (the best there is), and a few I/O links to run a special de-humidify mode and also to disable aux heat based on ISY condition monitoring. I carefully considered other control options, but ultimately decided that going all the way was the best solution. I have seen HZ series of zone control boards going for as little as $55 new on eBay. I would not try to skip this part. A dedicated purpose built zone controller is essential for equipment safety. This includes monitoring of discharge air temperature with de-staging control.

Just another suggestion: I always use fixed waits in conjunction with random waits to ensure enough "on" time as random 30 minutes could be 1 minute. If From Sunset To 1:30:00AM (next day) And Folder 'Security' is True Then Repeat Every 0 seconds Wait 20 minutes Wait 20 minutes (Random) Set 'Livingroom / Livingroom Lamp' On Wait 20 minutes Wait 20 minutes (Random) Set 'Livingroom / Livingroom Lamp' Off Else Wait 30 minutes (Random) Set 'Livingroom / Livingroom Lamp' Off Also, since I do not have my motion detectors directly linked to anything but the ISY I can also do conditional control of lights based on motion plus other event. So when I am in away mode, the security folder will be true. Now if my motion detector outside by the bedroom triggers, and it is night the flood lights near that corner of the house will turn on. This sequence of events will cause this program to run, making it look like I am moving around in the house near that area. If Status 'Front Yard / Floods - Bedroom' is On Then Wait 5 seconds Wait 5 seconds (Random) Set 'Bathroom / Bathroom Vanity' On Wait 10 seconds Wait 15 seconds (Random) Set 'Livingroom / Livingroom Lamp' On Wait 10 seconds Wait 20 seconds (Random) Set Scene 'Garage Flos' On Else Wait 10 seconds Wait 30 seconds (Random) Set Scene 'Garage Flos' Off Wait 10 seconds Wait 30 seconds (Random) Set 'Bathroom / Bathroom Vanity' Off Wait 10 seconds Wait 30 seconds (Random) Set 'Livingroom / Livingroom Lamp' Off

Thanks for yet another clarification. Good to understand the subtleties of the situation.

I get it. The ISY is not treating the relay of an I/O Linc like it is treating the relay inside of an ApplianceLinc. Thanks for the explanation.

I understand. Then allow me to amend my concern to the UI defaulting to setting the level of the relay to 0% when adding to scenes. If we are going to do something that messes up statuses it would be nice if it were something in which we had to actively participate. I know I assumed that adding the relay to the scene would have the relay turn on when the scene were turned on, and off when the scene was turned off. It was indeed an easy fix, but I think the default is counter-intuitive. I was shocked when my system woke me up in the early am due to an alarm because the HVAC system was running when it should not have been. I had not paid attention to the on level the relay defaulted to when adding to the scene. I assumed it would add at 100% like other devices. Edit: Wait. Lee, I added a lamp to a scene. I adjusted its scene level to 0%. I turned the lamp on. Status shows 100%. I turn the scene on, status changes to off as the lamp turns off. Why would not the same logic work and make sense for a relay?

When I add an I/O Linc Relay to a scene, it adds it at 0% reversing the logic. I think it should be added at 100% like other devices but that is not my core concern. The main problem is that now the ISY status of the device is always wrong until a query. I do not have trigger reverse selected. I add the relay node to a scene. It is in at 0% by default. If I turn the scene on, the ISY will report the status of the device as on, when in fact it is off. If I turn the scene off the relay will turn on, but the ISY will report the device as off. In either case when I manually query or the nightly query takes place, the status of the device will change to its actual condition, running any programs that look to this device for conditions. I do not have a concern with the flipping of the conditions, just with the ISY being incorrect about the status of the device.

viewtopic.php?t=3193

I have 3 t-stats with 1st gen dongles. All three show 'Fan State' as "ON" when all three are in fact "Auto"

I have a Mac running off an airport extreme. The only time I have any issue with the admin console is if the computer is allowed to sleep. Then the subscription expires and the admin console no longer works. I have to close it and re-open and re-sign it. As for you other concerns. UD agrees that they need more work on their documentation. Unfortunately for novices they seem to spend almost all their resources on advancement of the platform. This makes the documentation problem even worse as the information is constantly changing. You are into very advanced automation. It is going to take some patience. I had similar feelings when first working with the ISY. After understanding why things are the way they are and what capabilities this allows for I love this device. I am sorry you are frustrated. I am sorry that you have to post here to understand even the simplest concepts. I agree that a 10 page intro to ISY programming would be good. I like the video idea as well. But until we get something like this do not hesitate to post even the simplest questions here when you cannot find the answer on the wiki. Even the most skillful expert programmers will answer rapidly. This is a tight community interested in helping each other and not about flaming.

Thanks for the tough editing work. Through this post I finally understand State Machine programming. Now I will read the post that modifies it using variables with an actual understanding of the basic concept. One edit for the original post: I think this should be KPL-D not KPL-A based on the text in the rest of the post.

I do not think I can help by giving you my programs. As I have over 200 interrelated folder/programs just dealing with the temperature control in my house I think it would confuse things. Even with me having written them it can take me some time to understand their interrelationship to make changes. I have had to make flow charts for portions of it. That said, I would say start simple. Build a set of programs that set temperature based on conditions. Include ability to override these in the conditions and when the override is removed the conditions will have changed and the temps will go back to desired settings. At the core of my system are just a few enabled programs like: Away Temperature: If Program 'Away Flag' is True Then Wait 30 seconds Run Program 'Away Temperature Set Liv Cool' (If) Run Program 'Away Temperature Set Liv Heat ' (If) Wait 6 seconds Run Program 'Away Temperature Set Bedroom Cool' (If) Run Program 'Away Temperature Set Bedroom Heat' (If) Wait 6 seconds Run Program 'Away Temperature Set Office Cool' (If) Run Program 'Away Temperature Set Office Heat' (If) Else - No Actions - (To add one, press 'Action') Daytime Temperature: If From 8:00:00AM To 10:00:00PM (same day) And Program 'Away Flag' is False And Program 'Suspend Temp Programs' is False Then Wait 10 seconds Run Program 'Daytime Temperature Set Liv Cool' (If) Run Program 'Daytime Temperature Set Liv Heat' (If) Wait 6 seconds Run Program 'Daytime Temperature Set Bedroom Cool' (If) Run Program 'Bedroom Mode Check' (If) Else - No Actions - (To add one, press 'Action') Office Occupied: If Program 'Away Flag' is False And Program 'Suspend Temp Programs' is False And ( Status 'Office / Office Fan' is On Or Status 'Office / Office Hutch Lights' is not Off ) Then Run Program 'Occupied Temperature Set Office Cool' (If) Run Program 'Occupied Temperature Set Office Heat' (If) Else - No Actions - (To add one, press 'Action') Office Un-Occupied: If Program 'Away Flag' is False And Program 'Suspend Temp Programs' is False And ( Status 'Office / Office Fan' is Off Or Status 'Office / Office Hutch Lights' is Off ) Then Run Program 'Un-Occupied Temperature Set Office Cool' (If) Run Program 'Un-Occupied Temperature Set Office Heat' (If) Else - No Actions - (To add one, press 'Action') Sleep Temperature: If From 10:01:00PM To 7:59:59AM (next day) And Program 'Away Flag' is False And Program 'Suspend Temp Programs' is False Then Wait 10 seconds Run Program 'Sleep Temperature Set Bedroom Cool' (If) Run Program 'Sleep Temperature Set Bedroom Heat' (If) Wait 6 seconds Run Program 'Sleep Temperature Set Liv Cool' (If) Run Program 'Sleep Temperature Set Liv Heat' (If) Else - No Actions - (To add one, press 'Action') 'Away Flag' is an empty program controlled by my Home/Away KPL button. 'Suspend Temp Programs' is an empty program controlled by a KPL button. You could set a different one for each area. Temperature control is such a personal thing I think it would be tough to have one persons programs work for all. I just list these as ideas to get you started. I do not think my methods of programming are as skillful as more advanced members of this forum. I am reasonably certain that using a different approach like Orest's machine states would greatly simplify things, it is just beyond my capability. So I take a much more blunt force approach. I write some schedule based programs, and then keep adding parameters and other interrelated snippets as situations come up that I wish were accounted for. Years go by and I end up with literately hundreds of programs to adjust my temperature. Messy, but it does work flawlessly and nearly every possible desired operating parameter has been addressed. The one nice thing about this approach is that you can have basic scheduling and/or occupancy with some overrides and away settings operational in 30m of programming or less.

Yes. Admin console self closed as expected as I remember it. Not 100% sure as this was some time ago. I did not know the programs did not get changed till today when I noticed the events caused by conditions that included the switch did not run.

Replaced a switchlinc relay using "replace device with". It does not appear to have saved the programs this device was a participant in. All show as 'not specified'. No time avail for additional testing but wanted to report. Posted with tapatalk

Test complete. The only battery to survive all the test contamination over the years gave up the ghost today. While it was still detecting motion, the liquid electrical tape I put over the light sensor apparently degraded to the point it had been allowing dusk dawn triggers of 10 per day for some time. I brought the unit in to add more liquid tape to the sensor and as a rule I require seeing the MD send an on and off in response to set button presses before I will put the cover back on. She gave me an on, but the battery could not muster up enough energy for the off. I am calling Time of death 7-19-11 for a battery that was put in service 9-27-09. This is in a heavy use area with 15-40 triggers per day. This also had a PLM replace and restore in there which takes extra power. Further, for some time this MD has been sending Dusk/Dawn triggers many times per day. And it was still working when I pulled it down to try to stop the Dusk/Dawn commands. Almost two years. Not bad. Temperature range 8Ëš-109Ëš.

Smooth upgrade. Fixed event viewer level selection for me Fixed Switchlinc Relay LED Backlight issue. BTW. There appears to be two identical "Release 3.1.5 (Beta) Is Now Available" topics with different replies. Forum Bug?

Sorry for the false lead johnnyt, I realized moments after submitting that link and post that it only applies to users of the Pro version. I should have asked before sending you to a topic that does not help.

Please read viewtopic.php?t=536#p3401 in its entirety. This exact issue is addressed in the last few posts.

Thanks for the answer on the errors. Yeah, I can make that switch beep just fine: Wed 07/13/2011 09:39:09 AM : [ Time] 09:39:09 2(0) Wed 07/13/2011 09:39:09 AM : [iNST-ACK ] 02 62 18.32.DE 0F 30 BE 06 BEEP (BE) Wed 07/13/2011 09:39:09 AM : [iNST-ACK ] 02 62 18.32.DE 0F 30 BE 06 BEEP (BE): Process ACK: duplicate ignored Wed 07/13/2011 09:39:09 AM : [ Time] 09:39:10 2(0) Wed 07/13/2011 09:39:09 AM : [iNST-SRX ] 02 50 18.32.DE 13.24.AA 2B 30 BE BEEP (BE) Wed 07/13/2011 09:39:09 AM : [standard-Direct Ack][18.32.DE-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Wed 07/13/2011 09:39:09 AM : Duplicate: ignored Wed 07/13/2011 09:39:09 AM : [iNST-SRX ] 02 50 18.32.DE 13.24.AA 2B 30 BE BEEP (BE): Process Message: failed Wed 07/13/2011 09:39:09 AM : [standard-Direct Ack][18.32.DE-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Michel, I can assure you that both the unit I am replacing and the the unit I am replacing it with do indeed have beep. The title I used in my post is from the description the ISY places on these devices. I do not know why it says beep for the dimmer version but not for the relay version. And the errors I see in the event viewer... are those anything to be concerned about?

And while doing all this trouble-shooting I have noticed lots of instances of these errors in my event viewer: Mon 07/11/2011 03:19:18 PM : [FileOpen ] Open failed for [/CONF/ELECMTR.CFG] (r) Mon 07/11/2011 03:19:18 PM : [FileOpen ] Open failed for [/CONF/ELEC.CFG] (r) Mon 07/11/2011 03:17:00 PM : [FileOpen ] Open failed for [/CONF/IR.CFG] (r) Is this anything to be concerned about?

I have a 2476S that I use a program to adjust the back-light of each day. This used to work flawlessly around 2.8.16 but no longer functions in 3.1.3 or 3.1.4. I am replacing the 2476S (Hardware V5.5) due to failure to respond to local control but before this local control issue appeared the back-light had stopped responding to the program. I chalked it up to device failure but that does not appear to be the case. I received my replacement 2476 and added it and did the "replace device with function" under 3.1.3 but was unable to control the back-light from the ISY. Seeing that 3.1.4 specifically addresses the 2476s I re-added it after upgrading to 3.1.4. With just adding the device but before adding it to scenes or programs I attempted to adjust its back-light. No good. Here is the level 3 event trace: (2476S) SwitchLinc Relay - Remote Control On/Off Switch v.3A Hardware v5.8 Mon 07/11/2011 03:31:54 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:31:54 PM : [18 32 DE 1 ] Memory : Write dbAddr=0x0264 [FF] Mon 07/11/2011 03:31:55 PM : [iNST-ACK ] 02 62 18.32.DE 1F 2E 00 00 07 FF 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:31:55 PM : [iNST-SRX ] 02 50 18.32.DE 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:31:55 PM : [standard-Direct Ack][18.32.DE-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 07/11/2011 03:32:05 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:32:05 PM : [18 32 DE 1 ] Memory : Write dbAddr=0x0264 [01] Mon 07/11/2011 03:32:06 PM : [iNST-ACK ] 02 62 18.32.DE 1F 2E 00 00 07 01 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:32:06 PM : [iNST-SRX ] 02 50 18.32.DE 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:32:06 PM : [standard-Direct Ack][18.32.DE-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 It appears to communicate alright, but the back-light does not change intensity. Next I factory reset the old switch (the one I am replacing) and added it back to the ISY. I then tried to change its back-light using the LED brightness button. This very switch used to respond to back-light intensity changes. Level 3 Event Trace: (2476S) SwitchLinc Relay - Remote Control On/Off Switch v.3A Hardware v5.5 Mon 07/11/2011 03:32:55 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:32:55 PM : [14 E5 FF 1 ] Memory : Write dbAddr=0x0264 [FF] Mon 07/11/2011 03:32:55 PM : [iNST-ACK ] 02 62 14.E5.FF 1F 2E 00 00 07 FF 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:32:55 PM : [iNST-SRX ] 02 50 14.E5.FF 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:32:55 PM : [standard-Direct Ack][14.E5.FF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 07/11/2011 03:33:04 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:33:04 PM : [14 E5 FF 1 ] Memory : Write dbAddr=0x0264 [01] Mon 07/11/2011 03:33:04 PM : [iNST-ACK ] 02 62 14.E5.FF 1F 2E 00 00 07 01 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:33:04 PM : [iNST-SRX ] 02 50 14.E5.FF 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:33:04 PM : [standard-Direct Ack][14.E5.FF-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 And here is the level 3 Event trace from another switch that still responds to LED commands correctly: (2476D) SwitchLinc Dimmer W/Beeper v.38 Mon 07/11/2011 03:33:45 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:33:45 PM : [16 3A 15 1 ] Memory : Write dbAddr=0x0264 [FF] Mon 07/11/2011 03:33:45 PM : [iNST-ACK ] 02 62 16.3A.15 1F 2E 00 00 03 FF 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:33:45 PM : [iNST-SRX ] 02 50 16.3A.15 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:33:45 PM : [standard-Direct Ack][16.3A.15-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 07/11/2011 03:33:58 PM : [All ] Writing 1 bytes to devices Mon 07/11/2011 03:33:58 PM : [16 3A 15 1 ] Memory : Write dbAddr=0x0264 [01] Mon 07/11/2011 03:33:58 PM : [iNST-ACK ] 02 62 16.3A.15 1F 2E 00 00 03 01 00 00 00 00 00 00 00 00 00 00 00 06 (00) Mon 07/11/2011 03:33:58 PM : [iNST-SRX ] 02 50 16.3A.15 13.24.AA 2B 2E 00 (00) Mon 07/11/2011 03:33:58 PM : [standard-Direct Ack][16.3A.15-->ISY/PLM Group=0] Max Hops=3, Hops Left=2