smorgasbord

Also, the reply is often missing. Here's another sample, with the response being 0 (OFF) when the ON was sent. Then I did an OFF then another ON then another OFF, all without any response back from the unit.

I don't know how to restore the EZIO8SA and certainly don't have any configuration file saved. I do have the SHN utility, but I don't think I can use that with the PLM I have. My EZIO8SA does have the wall wart power supply and I'm using that.

So, is the thinking now that my PLM ("EZICOMM #5010k") has gone bad? What should I do to check it out? Buy a dual-band PLM on ebay?

I've never had a setup that worked. That's why I tried resetting the EZIO8SA. My post above shows the Event Viewer in Level 3 for hitting the "ON" button in the console. Here's the PLM-thingie: thanks!

In case it helps, here's the System Viewer after hitting the "ON" button in the console. Note the status is still "OFF."

Just to be clear, here's my (saved) ISY configuration with the EZIOSA8: And here's what I get when I delete and re-add the EZIO8SA: I can go back to the old configuration, no problem, but on the outputs, when I'm in the console and try ON or OFF, they don't change either on the screen or in actuality at the output terminals. Help, please!

I have that guide, which says that it responds to direct Insteon signals. So, how do I get ISY to recognize the EZIO8SA's Insteon's APIs? Apparently I was able to do it years ago since I did have the separate inputs and output in my ISY programming, but re-adding it (probably with new ISY firmware) didn't do the right thing.

I bought my EZIO8SA 9 years ago. Over the years I've tried to get it up and running and never did. Trying one more time. At first, the EZIO8SA was in the system and I could see in the inputs and outputs. But, when I went to turn an output ON or OFF, nothing actually changed. So I decided to reset the EZIO8SA by unplugging, waiting 10 seconds, holding the SET button and plugging in, holding the SET button until the buzzing stopped. Didn't help. Then I read another thread here where it was recommended after a reset to delete and re-add the device. After doing that, however, ISY is reporting it as "Unsupported Device 3.42" It doesn't matter if I let it determine the type or if I manually choose Compacta - EZIO8SA from the list. Ideas on what try next appreciated. Should I get off the ISY since it's outdated? I've been using it for years without any issues, just now trying to expand its use.

BTW, to help other C programmers coming to ISY, I think it would be worthwhile considering the "If-Then-Else" in programs as a "WhenIf-Then-Else." In other words, the program is automatically invoked when any of the "If" statements have changed status. That is, as long as the program is enabled. If you want to have an If-then-else section inside an existing program, then you should put that into a new program, disable that program, and call that program (Program Run (If)) when you want.

I know the rule is to not use surge suppression power strips, but how can one test to see if the power strip you're using is filtering or not? Many devices are dual-band so I don't know if they're using RF instead. It's really hard to find anything that doesn't say "surge protection" on them, even the $6 cheapies advertise it. Maybe the cheapies can't actually protect and so don't actually filter? Can anyone give me an Amazon link to something suitable? I've got about 4 IOLincs that I need to connect (if I have to use small extension cords on them due to outlet spacing, I will). Thanks! EDIT: I found this: https://www.amazon.com/gp/product/B083K4CHPV Can anyone confirm Insteon suitability?

The system I'm using to close and open relays sensed by the IOLinc has 1/10 second (100msec) granularity. It did appear that 100msec was detected, but I didn't need it to be quite that quick so I set it at 200msec. Seems OK so far. EDIT: After a few days, I've found that I needed to increase the time the contact is closed and/or time spacing between the contacts. I'm now at 0.4 seconds close, then 0.4 open, then 0.4 close. I haven't experimented enough to see if I can have different timings for close and open and still detect the double-tap.

OK, so I caved and created the 4 programs as described, adding the dimmer set to low on FirstTap and dimmer set to high on SecondTap, and I also added a DoOff program. Works well! But, I'm still not understanding how the Wait and condition re-evaluation works. I also came across this old post doing something very similar without variables:

OK, I think I see what you mean by "separation of concerns." You're using the 4 programs to set a sTapState variable that is then used by other programs doing the actual On/Off. Separating those makes the logic easier - one set of programs for a variable and then just one program to turn the light on according to the variable. I think you're doing this because ISY doesn't operate like a typical "C" compiler. For instance, calling another program doesn't transfer flow to that program or wait until that program finishes before doing on to the next line after calling the program. I think I got that, but.... I'm also struggling with the "Wait" functionality. The Wiki says (edited for clarity): I assumed that the reevaluation driven by a Wait statement occured after the wait. But, that doesn't appear to be true. This program doesn't work: KitCab FirstTap If Control 'Kitchen Cabinet Pucks / IOL1 Sense from LT KitCabPuck' is switched On And $sTapState is 0 Then $sTapState = 1 Set 'Kitchen Cabinet Pucks / Kitchen Cabinet Pucks Dimmer' 35% Wait 2 seconds $sTapState = 0 Else - No Actions - (To add one, press 'Action') What seems to be happening is that the program terminates at the Wait (or I guess the Else clause is getting executed). So, @jfai's separate routines for seeing the state variable work because the state variable isn't changed until after the Wait. Not sure I'm getting this....

Two of the four programs are based on the iolink.sensor control (sensor status being changed). Since I assume the ISY is single processor/single threaded, only one of those programs can be running at any one time. So, either "First Tap" or "Second Tap" gets run, and then the other program is run. Since the program has a conditional, I imagine they run pretty quickly, though. Can you explain this more? Is it a debugging thing or something else? It seems pretty straightforward to have a program that gets called when the iolinc sensor changes state ("control") and then that program done one thing for first tap and another thing for second tap. I've seen that the kind of programming I'm used to is different than what ISY supports, so perhaps there are considerations of which I'm not aware. thanks again.

@jfai, thanks so much! That's 4 programs, two of which start with the same iolinc.sensor event, which means at best they run sequentially. What about this dual-program: KitCab GetTap If Control 'Kitchen Cabinet Pucks / IOL1 Sense from LT KitCabPuck' is switched On Then Run Program 'KitCab DoTap' (If) Else KitCab DoTap If $sTapState is 0 Then $sTapState = 1 Set 'Kitchen Cabinet Pucks / Kitchen Cabinet Pucks Dimmer' 40% Wait 2 seconds $sTapState = 0 Else Set 'Kitchen Cabinet Pucks / Kitchen Cabinet Pucks Dimmer' 85% $sTapState = 0 I'm assuming that KitCab DoTap can be reentrant. Thoughts?

Frankly, I'm having trouble getting started with the programming. I''ve done a half dozen things in ISY that worked out fine, but I'm used to full-on programming languages like "C" that can have if-then-else's placed anywhere in a routine instead of having to call a program to get and if-then-else clause. And this seems more complicated than the usual. For instance, how do I store Time in a variable so that I can compare the timing of the second tap relative to the first tap? Do I have to manually break down the hours, minutes, seconds into a combined integer? Are there any existing subroutines or code snippets for that? EDIT: I'm running the latest release V4 software. Should I update to V5 to get more functionality?

@lilyoyo1 , I'm not sending the double-tap from the IOLinc, I'm sending it to the IOLinc. @Brian H, what timing is the IOLinc capable of discerning? Since this is system to system, I could have the double-tap be within 2 seconds even and that might work (first tap goes to 35% and second tap within 2 seconds goes to 80%). If I wanted to try this out, what would the program look like? Thanks!

I'm trying to get the most control options out of each IOLinc in the hopes of buying fewer of them. I've got an external system that has contact closure/relay outputs and have connected them to IOLinc Sensor inputs. That works well - the external system closes a relay and the IOLinc senses that and a scene gets run to turn on a light or ISY runs a program in which I write to decide what to do. Cool. Now, the light I want to control is on an Insteon Dimmer (2477D) and depending on what was done on the external system I'd like to have the light go to one of two different levels. Is there a way I can write the ISY program to detect a "double-tap" for instance? That would be the ISY program getting a close/open/close within a second or less (maybe ½ second would be better) from the IOLinc and doing something different. My idea is that on first IOLinc Sense Close the ISY program would turn the light to 35% Dim level (perhaps as programmed in the 2477D itself), and then if a second IOLinc Sense Close came in within a ½ second the ISY program would ramp the light up to an 80% Dim level. I assume to do this I would not use a Scene but instead have the IOLinc sense run a program with something like "Control IOLinc1_Sense is On" and inside the Then have a Wait for ½ second and use the ISY program's reentrant capabilities to capture the second On. I don't know how to write this - can someone help? In thinking about this more, since my external system is programmable as well, could I setup a Morse-code like communication channel? Dots and Dashes to have the other system tell the ISY what to do? I know there would be some delay, but for non-timing important things, that would be really cool (and IOLinc buying reducing!). Or, if there's a better way to do this, I'm totally open. thanks!

Just saw the Insteon 2448A7 USB adapter, which goes on the Insteon wireless signal. Could that be used on the laptop running the utility?

Not sure I'm following all this: To run the utility, I need to get a piece of hardware so my PC can get onto the Insteon "network." The would be something like a USB to serial port (RS-232 I assume) and then a 2412S or 2413S. Do I need to put the EZIO8SA's PLM into "set" mode? Separately, in working out what I need, it's looking like I'm going to need around a dozen relays and sensing units. Maybe more on the sensing side. Should I buy additional EZIO8SA's or is there something better now? 4-8 IOLinc's run more money per sense/relay than a single EXIO8SA and I've read having lots of IOLincs together isn't good. So, what should I buy to expand the number of ISY sensing/relay nodes?

For debugging purposes I've been finding it handy to have the ISY send me a text from inside certain programs. Especially with motion detector type functions that have dependencies to have different things done on motion. It works fine, except that each message I get comes from a different "number." For instance: (410) 200-516 (410) 200-521 (410) 100-017 It means I have to manually delete each one or try to fold them into a single contact. This is probably expected behavior, but it'd be nice if the SMS's were sent from the same number, or small group of numbers. My phone is on the ATT network, and it's an iPhone X.

I got the "kit," which comes with a PLM like thing (EZICOMM #501OK), but I don't know how that works for connecting it to the computer. There's an ethernet cable that goes from the EZICOMM to the EZIO8SA. I recently added a Range Extender, and when I did the 4-button tap on the ISY's PLM the LEDs on both the range extender and the EZIO's PLM were blinking (which means both are on the other leg of the ISY's PLM). I probably don't have 2.02b. My EZIO8SA says "V2 #3011A" on it. Like I said bought in late 2013. I can run SHN Utility on my PC, but since it's not connected to anything it can't see the EZIO8SA. I probably need something to connect via USB to the laptop, but I have no idea what that "something" might be. thanks

I bought an EZIO8SA about 7 years ago, and am just now getting to the project I bought it for, which is to add functionality to my home's existing built-in wired system. I can program that system as well, but it's non-standard and so my only input/output possibilities are contact closure input/output (both ways). I got the EZIO plugged in and added to ISY. Looks like I have 4 inputs and 8 outputs (there are 7 inputs total, but one of those is dedicated for 1-wire thermostats and two of those are analog which I've read should be connected to ground to avoid too much Insteon traffic). Is the rest straightforward? I see there's an SHN Utility, but I'd need some way to connect some PLC type device to my laptop. Do I need the SHN Utility - what does it do? Any other gotchas for me to watch out for? I may need even more contact closure input/outputs - what's my best alternative for new hardware? I also have a few IOLincs that have been working fine. Thanks in advance for any pointers, war stories, advice, etc.

My first ISY project years ago was to hook up a motion sensor to an outlet into which the recirculating pump was plugged. Works well and no remembering to push a button:

Back home - and the ISY/PLM is working (!). Don't know when that started, but now getting to the ISY is problematic via the Dashboard or URL. Here's my about screen: Is there a checklist I can proceed against? thanks