rlanza1054

That's why I originally asked for the proper way to set up the crosslinking between two devices. Even though it works as it should, I was afraid at first to make two different devices the controller of each other. Like you said if A turns on B (A is controller) and if B turns on A (B is the controller). That should create the loop you taked about, but it doesn't? I have device A turn on device B (A is the controller of , but I have B a controller of A to make sure the LED is in sync with the LED of B (A just happens to be a button on a Keypadlinc). I used a scene and is only in one scene where when I added the devices they were set as both controllers. So way does this end up being not a loop? I am glad its not and is working as it should. Rob But tha

Thanks guys, I 'think' I get what you two are trying to say. A flow based program just goes from line to line until it reaches an end. A event based r triggered based program, will run the program but if a trigger or event happens the program can take a different direction. Also, there is no real end of program (unless programmed to actually end) in a event based program because the program is continuallywaiting for an an event to happen or not to happen. Sort of link the task scheduler in a Windows OS. Am I close in getting it? Rob

Thanks, that will make it easier than going through the gyrations. Rob PS Steve did talk to me the other day and gave me some insights to try and write the program, lets see if I csan actually do it. LOL!

Hi all, Ok, I'm a newbie, so I will get that outof the way. Second, I know from reading all the threads about the iMeter Solo that it has been a flop and Universal-Devices does not want to waste development time on a product that Smarthome/Insteon seem to have abandom themselves. With that in mind,I am not asking for anything crazy. I did get one Energy Display units to see what it wa sall aboutm, nothing great in my opinion. I hate that it goes to sleep, a real waste of money. Since its been recommended that I do not run Houselinc or the HUB (although the HUB doesn't really even support the iMeter Solo except for linking with it). ​ All I want the ISY to do is get the kilowatt usage, which it actually does! Wow, it does that at least! But there is a field when looking at the iMeter from the Mobilinc Pro app on Android that I'm interested in getting to work. Actually, I would like it to work on the ISY first. I want the Total Usage 'Cost' calculated? Is it possible to get the ISY to perform the calculation of the power consumption? It is able to read the kilowatt, its doing that now. So is the a pre-written program that already does this, if not, is it possible to write a program to do the calculation. Bear in mind, that being a newbie, my ISY programming skills are limited right now. I've only been able to do very simple things so far, not much to speak of. Or is there some add-on module that I would need to purchase to do the calculation. Nothing that costs me more than the ISY. LOL! No, really nothing more than a few bucks. Could maybe I setup the Houselinc to see just the iMeter Solo and since the docs say that Houselinc has the ability to do the calculations maybe I set that up and have the ISY import that function of how its done? Or do I give up and sell the two iMeters I inverted in and get something else. I read that Z-wave has something that works much better. I do have a top-of-line ISY994, I have the ISY994iZW-Pro with IR! Thank you! Rob

Yes, thank you! I did indeed use method one, its simple to do. But I can see a reason in some circumstances to use method two, using two scenes to link each to the other. I did find that whejn bhuilding a program, that I had to use a scene, not the device itself to either turn on a device or turn a device off, beacuse a scene is able to turn on the LED's correctly and in sync. If I turn on write a program to turn on a device using the actual device, if that device is crosslinked to a Keypadlnc, the LED on the Keypadlinc does not light up with the device's LED. I thought that was strange, one would think it they were crosslinked the LED's on both the devicfe and the Keypadlinc would remainj sync'd but apparently that's not the case, as I discovered the hard way. Thanks again! Rob

I am not a programmer, so I don't exactly know what you mean by your statement "ISY does not use flow based if-then-else logic. It's event based."? What is event based mean? I'll google the term, but I talked to Steve today aboit something else I want to do and he too said to break it down into multiple programs, because it can't do the logic of normal or regular programming that I learned in school. He said the ELSE is not using as one would think its used. As I said I'm a newbie trying to get used to the interface to be able to design and actually write the programs. I will be trying to find as many examples as I could to help me learn how to do the actual writing. I did watcfh all the YouTube videos that I was able to find. ISY has a total of 3: 1) basic setup 2) adding devices, linking and troubleshooting 3) variables That's it! I am a visual learner, so the videos help me greatly understand actually using the interface to do the composing. I'll get there but in the meantime, I will just depend on everyone's help. I thank you all greatly! Rob

Thank you, that's exactly whatI enfed up figuring out and doing. I is only 4 lines as you have suggested.

Hi all, I did try looking to this but can't find the answer I'm looking for. I did study pogramming basics way back in the day, but programming wasn't for me. So I do have a basic undestand of programming concepts. The concept of logic in using 'IF', 'THEN' and 'ELSE'. I don't seem to be able to make what I want to do inside the Programming area of the ISY. It could be either that I just know how to enter it or my program is not logical. Here is what is inside my head. I just want to do a simple Sunrise Sunset of a Plant Light attached to an Insteon ON-Off Module. ========================================== IF Sunrise AND Plant Light is=Off Then Set Plant Light = ON Else 'If' Sunset AND Plant Light = On THEN Set Plant Light = OFF END ========================================== Without giving me the answer: How do you enter this into the ISY. Do I need to have two separate programs, one for 'sunrise' and the second for 'sunset'? Or can this all be accomplished inside one program as I am having a hard time doing? Everytime I try to enter the Sunset schedule into the ELSE area it ends up in he first IF at the top of the program. Thank you! Rob PS UPDATE: Does the ISY have the ability to do NESTED IF's THEN's ELSE's? How does one get something nested. If there any video that showsd programming the ISY as a tutorial that would be great, so far I haven't found any programming examples on YouTube.

Hi, I am just starting out and did not want to start a new thread. I have 3 Keypadlinc's. But to keep this simple I just want to deal with one particular Keypadlinc. So I have a Keypadlinc setup as 8 button. With any controller to properly setup the buttons so they light up correctly from either using a button on the Keypadlinc or the switch itself, you crosslink them. In the end the assigned Keypadlinc button should light up whether the device is activated at the switch or the Keypadlinc or even anything else that turns the device on. To crosslink manually, you press the set button on the Keypadlinc and the button you want assigned (until it flashes to let you know its in linking mode) and then press the device's set button until it flashes. Its now linked from the Keypadlinc to the switch, the Keypadlinc is the controller. Just doing this, the switch is not really crosslinked, so if you turn the device on from the actual switch, the LED on the assigned button on Keypadlinc will NOT light up. Its a simple one way link. Now to get the real full crosslinking done, you now need to press the set button at the device until it flashes and then tap the set button and the assigned button on the Keypadlinc just until it flashes to acknowledge it took. So now you have true crosslinking, both are considered 'controllers'. If I have this all correct, here is my question when setting up crosslinking (crosslinking is not really explained in the documentation of the ISY) using the ISY994: Should you setup crosslinking using one scene or two scenes. What is the proper method or maybe it doesn't matter and both (which I will explain) are OK to use. Method One: Is to create one scence and when adding the device, ISY will ask you if its going to be a 'controller or a responder', You say 'controller'! Then you add to the same scence the Keypadlinc and when it asks you the question of 'controller or a responder', You say 'controller' as well. So they are both controllers. Method Two: Is to create two scenes, the first scene you would add the device and allow that to be the 'responder' and when you add the Keypadlinc button you make that the 'controller'. Then you create the second scene and you add the device and allow that to be the 'controller' this time and the Keypadlinc button you make the responder' Method One, they are set as both controllers in the same scene Method Two, They each get assigned as controller and responder but each in two different scenes. Which is the proper method to use. Or are both methods equally ok to use. One or the other! And of course, only setup method one or method two, don't use both. Maybe both can be use but one method might provide more flexibility over the oher method? This is what I'm try to find out to complete my setup of these Keypadlinc. I want it to be correct. Thank you. Rob