larryllix

Sorry. I missed the alternative shut the sequence off properly. Here is the correction Front Door - Chandelier - [iD 000C][Parent 0001] If $sAlarmZ01_FrontDoor is 1 Then Resource 'Centralite-EntryChandelierOn' Enable Program 'Front Door-Chandelier Off' Run Program 'Front Door-Chandelier Off' (Then) Else - No Actions - (To add one, press 'Action') Front Door-Chandelier Off - [iD 000D][Parent 0001][Not Enabled] If $sAlarmZ17_FrontEntryMotion is Not 1 Then Wait 15 seconds <--- you may want to extend this if you don't move fast enough Resource 'Centralite-EntryChandelierOff' Wait 1 second Disable Program 'Front Door-Chandelier Off' Else Wait 1 second <--- add these lines to reset the sequence after motion Disable Program 'Front Door-Chandelier Off'

This sounds like a case of bad SH capacitors again. My guess is, if you have noisy power it accelerates the capacitor aging and the cheap ones they use don't stand up to absorbing more spurious waveforms. If you are handy with a soldering iron it would be worth a try replacing the caps for the cost of these things.

Thanks Stu! I have seen this tooted many times but never at the stage where I am ready to install a GDO kit. Before I get into all the logic what is the better contact to use for the I/O Link. The one that doesn't get flipped in the middle of the night query?

Just got one for Christmas and the contact supplied was N/O. Rev 2.3 #2866-392 When activated by the magnet the contact closes. This should show as an On in ISY, meaning the garage door is closed. The labelling of the point will have to have the word "closed" in it. The software reversal is too dangerous and from reading about it for two years will be avoided at all costs.

IIRC the LED is not reversible and always tells the truth. ie On = closed contact, Off = open contact. My feeling is that you have a different polarity of contact NO vs. NC and you will not be able to correct for it and you will have to replace it or live with the negative logic indication (not reverse it). I have an HRV contact doing this and I named it HRV.inverted so I never forget and start fixing programs.

What are you sensing? What state are the device when you indicated 'On'? Do you understand what N.O. means?

There was a huge discussion of this hoping v5 would pan out some construct changes almost exactly as you indicated. Some thought it would be better to just have a checkbox next to each If line that could disable triggers individually. The When section could make old programs forward compatible easily. I thought the whole syntax should leave the old syntactically incorrect constructs and old programs behind and clean it up but a lot of barking ensued. (not a legal term ) Just a javascript cross compiler on a Win 10 machine could convert anything to anything and restore it back in.

Better your head than ours! Glad to see you figured it out. We keep learning the hard way sometimes but we remember better then.

My newer LeakLincs send different commands from a long tap and a short tap. IIRC one is a Wet On and the other is Dry On. Yeah. I triggered my pump shut off, send notification to my wife out shopping, and flashed my lights and doorbell again until I figured it out. Moral? Tapping the link button does not always reset the programs. Now I send a piece of text with my notifications: "To restore the water pressure press "AAAA" on the KPL" My multi code combination program can decode many codes and reset things. http://forum.universal-devices.com/topic/16135-using-keypad-triggers-for-a-multiple-combination-locks/

Try this one Front Door - Chandelier - [iD 000C][Parent 0001] If $sAlarmZ01_FrontDoor is 1 Then Resource 'Centralite-EntryChandelierOn' Enable Program 'Front Door-Chandelier Off' Run Program 'Front Door-Chandelier Off' (Then) Else - No Actions - (To add one, press 'Action') Front Door-Chandelier Off - [iD 000D][Parent 0001][Not Enabled] If $sAlarmZ17_FrontEntryMotion is Not 1 Then Wait 15 seconds <--- you may want to extend this if you don't move fast enough Resource 'Centralite-EntryChandelierOff' Wait 1 second Disable Program 'Front Door-Chandelier Off' Else ----- EDIT: Some last minute corrections

LOL. Simply put the "Executive" would be a supervising program that has to dispatch to that point in the program. This would usually be some multitasking "overview" program that dispatches to, and makes sure all programs, are run when needed. ISY has a trigger based event processing executive so the user doesn't have to write complex job handlers and be where and when CPU attention is needed. I worked on a large real-time executive software program that did electrical grid protection handling as well as SCADA function reporting and control. It's system just scanned through lines of code top to bottom and repeated at high speed. From a user's view it worked very similar to ISY but there was no broader If constructs, only inline If/then/else that would do similar to ISY's variable substitution. Anyway from the code writer's view ISY does things as if by magic. You just say when and it happens. In linear programming you have to continually "test the waters" on each program to even make things work.

CALL checkmotion <--- linear programming has to have an executive to make this happen, ISY does surprise magic If Motion = true Then if (Time > sunrise) and (time < sunset) then <--- sunrise/sunset never do anything. They are just condition filters do something do something else Else <-----nested If/Then/Else has to be done with programs in ISY Else print "nothing is happening" Gosub somewhere else <-----linear programming will wait for the subroutine to finish before continuing, ISY spawns multitasking and order or operation can be a surprise Next line is always in order.

It definitely isn't the usual top down inline program execution code. I think what you are saying is a training document for newbie users with step by step, do this, do that examples. This type of document could be used for sales promotion materials also. One of the problems is demonstration of execution. Every new user has a few different Insteon devices. If I told you to define a variable and write a short program example that is triggered when the variable is changed, would you be confused when you susbstitute a motion sensor or a hidden door sender? It could be done with a few different angles and probably should be done. Perhaps UDI could provide a user space in Wikipedia for users to write and polish such a thing before launch. I wrote for Wikipedia, for a few years, and suspect the same executive system is in use for UDI's wiki. EDIT: I have a copy of an "ISY User Guide v4.2.8.pdf" somebody directed me to bout a month ago. It does provide some basic programming examples that may be just what we are talking about. Perhaps somebody could provide a link to it as I have the doc and lost any link to where I got it from.

Wait does not cause re-evaluation of the If logic. Wait allows the ISY PLC processing to run other tasks (gives up it's time slice control for the Wait time) which may include evaluating the If in the same program if a trigger element changes. It may only be ISY sending out an Insteon command.

How about any boxes using the Rest interface or Kodi app?

Either it is licenced or, if it ever becomes anything, it will disappear or else pay the $2 Million law suit, and then disappear.

Yes. Having a common variable for inside darkness has it's advantages, including adjusting sunset for a darker or lighter house construction, tree leaves in the summer vs winter, etc,,

Yes, post program so we can view it. Use "copy to clipboard and paste here. You cannot check an MS battery. You wait patiently for a one time LowBatt signal and it is transient. I send notification and then record all my LowBatts in a variable list to keep a record of which ones reported in.

They have knowingly put out so much crap for so long now and with the HA boom going on without them? If I was SmartyHome I would be shaking in my boots and starting to sell other brands and lines of equipment. Oh wait! They already have.... They have one supporting control intelligence company that wants to support them and what do they do? Not allow them to promote their products by refusing them any rights to their technology but get in bed with other companies to support a cloud based logic home controller. I guess in this day and age of CPU's in every toaster and walwart they don't want another one in a HA controller! The extra $0.30 cost would cut into their intelligence. (sarc) When will they learn Mandarin so they can understand what is being designed for them?

I use an All Off program at 4:00 AM every night but not in a scene. I switch every light off one at a time with a few seconds delay between each just to help any Insteon traffic jams I would cause and be more sure they all work. Also outside observers would see a progression for a more human action look if everything was on for some reason. I also do have an ALL Lights and Front Doorbell scene for intruder repulsion.

I think I have it. It's late and I am having trouble focusing so nothing guaranteed, Cody Bath Manual Switch - [iD 0023][Parent 002A] If Control 'Shower Bath - Room' is switched On Or Control 'Shower Bath - Room' is switched Fast On <--- I would save Fast On for other functions <---no condition needed as far as I can tell Then Set Scene 'Shower Bath Motion Light' Fast On <---- just set the light on without the scene. Disable Cody Bath Motion Disable Program Cody Level Ramp Rate In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 100% (On Level) In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 0.1 Sec (Ramp Rate) Wait 2 hours Run Cody Bath Switched Off (Then path) <---- use other program to restore everything Cody Bath Switched Off - [ID 0056][Parent 002A] If Control 'Shower Bath - Room' is switched Off Or Control 'Shower Bath - Room' is switched Fast Off <----could be used for other functions Then Set 'Shower Bath - Room' Off Run Program Cody Level Ramp Rate (If) Wait 1 second Enable Program Cody Level ramp Rate (If) Enable Program 'Cody Bath Motion' Else - No Actions - (To add one, press 'Action')

No "delete direct link". Delete the line, there is already a direct link. sorry for the shorthand.

Motion Program Cody Bath Motion - [iD 0049][Parent 002A] If Control 'Cody Bath-Sensor' is switched On Then Set Scene 'Shower Bath Motion Light' On <---Delete = direct link between devices Wait 1 minute Set Scene 'Shower Bath Motion Light' Off Else - No Actions - (To add one, press 'Action') --------------------------- Night Ramp Program <---looks good Cody Bath Ramp Rate - [iD 0044][Parent 002A] If From 10:00:00PM To Sunrise (next day) Then In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 30% (On Level) In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 4.5 Sec (Ramp Rate) In Scene 'Shower Bath - Room' Set 'Shower Bath - Room' 30% (On Level) <----Delete, wrong scene In Scene 'Shower Bath - Room' Set 'Shower Bath - Room' 4.5 Sec (Ramp Rate) <----delete, wrong scene Else In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 100% (On Level) In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 0.1 Sec (Ramp Rate) -------------------------------------------------- The rest of this confuses me. I started to renovate it but it got too confusing with this small editing page. It doesn't look anything like my original and I do not understand what you are trying to do with different logic. You have attempted to split the one program into two also. That can work but isn't necessary. It does make the compound If conditions easier to understand though. Here is my original program that does both. Some disables need to be done and calls to the resstting of the levels program needs to be done and have been attempted to shortcut. I suggest you copy Then and Else into your individual programs changing devices and program names, to suit, as you copy over each line. MBR Lamp.manual - [iD 0038][Parent 0017] If 'Master Bedroom / MBR KeyPad.A' is switched On And 'Master Bedroom / MBR KeyPad.A' is not switched Off Then Set 'Master Bedroom / MBR Wall Lamp' Fast On Disable Program 'MBR Lamp.auto' Disable Program 'MBR Lamp Level.adjust' In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 100% (On Level) Wait 2 hours Run Program 'MBR Lamp.manual' (Else Path) Else Set 'Master Bedroom / MBR Wall Lamp' Off Run Program 'MBR Lamp Level.adjust' (If) Wait 1 second Enable Program 'MBR Lamp Level.adjust' Enable Program 'MBR Lamp.auto' Lamp will get direct hit by MS so adjusted scene level so it can't be noticed. 

It would seem you are thinking of X10 signals where All Lights On would only affect units on that housecode. In Insteon this would turn everything On/Off, including furnace fans, heaters and bathroom exhaust fans etc,,, The toggle mode is only preference but I set mine up to non-toggle. Each button sends a distinct On command only. In toggle mode each button alternately sends out an On and then an Off command. So a receiving program might look something like this. If control KPL.botton.A is switched 'On' Then set Light A off set scene GroupOfLights off Else -- making sense?

Where are you trying to send an All Off command from? This is a usually avoided command that most of us never use. If you have the six button KPL then the two larger buttons at the top and bottom control the attached load. The rest only send Insteon signals. There is no All Off/On on a KPL.