apostolakisl

Thanks, does that mean I need to have it in twice if I want to both use it as a trigger and as something to take action on? @tazman

Trying to trigger an Alexa routine from an Insteon switch in ISY. I have a bunch of devices and some variables on ISY exposed to Alexa. They show up and I can control them from Alexa, even set variables. However, when I try to create a routine, they do not show up as options to trigger the routine (the When section). They do show up as things I can take action on in the "Alexa will" section. I can set a variable in ISY from an Alexa routine or turn on a light switch. I have lots of stuff show up in the "When" but nothing in there is from ISY. Within the "when" section , I am clicking on "smarthome" and find all the things that are linked to Alexa from other plugins, but nothing in there from the ISY plugin. In short, I can send commands to ISY nodes from Alexa using a routine, but I can not use an ISY event to trigger a routine. So, what am I missing here? @bmercier

@srjacob OK, misunderstood what you were asking. I had the native Elk module originally and converted to the Elk node server a couple years ago. The Elk node server does everything the module did plus a bit more. You will have some work to do, however. The nodes don't just convert over. If memory serves, I copied all the programs to clipboard and saved them all in a word document so I had them all written out to use as references when re-doing them.

Not sure what you are currently doing that has 30 programs that "deal with Elk", when it sounds like you do not currently have the Elk module. The Elk module lets ISY pretty much use Elk as a fancy I/O board. You can use all the input status' (the zones) in programs and you can control all the outputs from programs. You can also of course use all the armed states, alarm states, to trigger programs and can control the armed status of Elk directly from ISY programs. However, having ISY trigger Elk rules to run is not so easy. You can not trigger a rule directly from ISY. I have used "phantom" Elk outputs as triggers. If I want ISY to run a rule programmed into Elk, I have to do so by turning one of these phantom outputs on (an output that doesn't have an actual relay board, like output 100 or something) for 1 second and then rule triggers on that output turning on. If I hadn't already written boat loads of rules in my Elk, I probably would have just used ISY programs to do everything the rules are doing. But since I already had a bunch of Elk rules, I did the work around. Also, having Elk rules means I can execute them from Elk keypads using tasks, bypassing any dependence on ISY.

I did this very thing with great success for 10 years. I buried a 120vac wire between the two buildings and put an outlet on the side of the other building where I plugged in an old Insteon hub. The Insteon hub has a very strong radio interface. The powerline carried the signal to the hub and the hub converted it to radio that my insteon devices in building 2 connected to. It worked flawlessly, almost better than in the primary building. My buildings were over 100 feet apart as well. You could potentially only run the buried wire part of the way, just getting it close enough for the radio on the Insteon device to get a good signal in building 2. You can always test things out by just running an extension cord to various locations.

I didn't really check, but is the issue with the nodes connecting to ISY or the nodes connecting to the various 3rd part things they connect to? If the disconnect is to the third party items, I am surprised that they don't reconnect on their own since I can reboot the third party devices or reboot my router and as long as Polisy stays up, the nodes reconnect.

I have seen the same issue with my polisy. After power outages, I have to go through and restart my individual polyglot nodes to get them to connect. From the console, they all report "connected", but they aren't. I have not seen issues connecting to the portal.

I get that, but I find it surprising that UD would not have managed their supply times better knowing all that, unless the manufacturer had supply chain issues, but then I would expect that I wouldn't be able to get it on Amazon. Perhaps there is some unique hardware component the UD wanted that went on backorder.

Curious that it is available overnight on Amazon and UD is backordered.

Steps: 1) In ISY's main page, find the old switch and remove it from any folders it might be in and place it in the root folder. Just the switch itself, not any scenes. 2) Join the new switch to ISY - put ISY in linking mode by hitting the swirly arrow icon and then - press and hold the tab on the new switch for a few seconds until it beeps - the new switch should pop up on the admin console, tell it to go ahead and join ISY and erase any info on it already. You can name the switch if you like, or just leave it with the address. Whatever you do, just make note of the name. 3) Right click on the old switch and select "replace with" and then select your new switch. 4) ISY will automatically go through and write all the info to all the switches involved with that switch. It make take a bit (seconds up to maybe a minute) depending on how many scenes it was in. 5) Restart your admin console 6) The new switch will now have the name of the one it replaced. You can drag and drop it into any folder it might have been in before.

You do have the advantage here that you are wiring just swapping out one device for another where they are basically identical. So there should not be any confusion. Just be certain that you have shut the breaker off, as mentioned. Insteon devices don't like if you wire them hot and get sparks. As an extra precaution, I always pull the hard disconnect on the device while wiring it in.

You would have to have a pretty old device to have the bad tact switches in them. Smarthome replaced every switch in my house under warranty for that like 15 years ago. I haven't had any of the replacements do that. The switches have a date code on them on a sticker that is visible if you take the switchplate cover off. It will be a year and week. I forget what order, but it would be something like 3422 meaning the 34th week of 2022. Ot maybe it would be 2234. As you know, the 2476ST isn't made anymore, but it isn't necessary. Use programs in ISY to do your timing rather than having the switch natively do it. A 2477S is a relay switch (on/off only, no dimming) designed for controlling things that shouldn't have dimming at all (motors/fluorescent lights). 2477S is also a dual band, so it uses radio and power line communication which makes it much more reliable.

Might do it this way depending on your needs. This mod to the program above causes the counter to trigger on you setting the variable to whatever time period you want to wait. Shouldn't need two programs (depending on how you are setting the variable for countdown) as this program won't re-trigger unless you change the value of that variable mid count, in which case I assume you would want it to start over. In summary, the below program runs as soon as you set the variable $chosenvartowait to any positive number. It will then count every second until it reaches that number. Obviously, change your wait time to minutes or hours or whatever if you want to count those instead. Also note, I moved the wait 1 second line up above the add 1 to the variable line. I think it would terminate 1 second too soon otherwise. And I moved the reset of the counter variable to the first line ensuring if you change the variable mid count it will reset it. ID - [ID 0058][Parent 0093] If If $chosenvartowait > 0 (need to setup this variable as a state variable) Then $countervar = 0 Repeat While $countervar < $chosenvartowait Wait 1 second $countervar += 1 Repeat 1 times Set whatever you want to happen Else - No Actions - (To add one, press 'Action')

I don't know of any way to do that directly. The best I can think of is to use "repeat while" as guy mentioned and then set a program to count. Something like ID - [ID 0058][Parent 0093] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then (optional line here to disable triggering program) Repeat While $countervar < $chosenvartowait $countervar += 1 Wait 1 second Repeat 1 times Set whatever you want to happen $countervar = 0 (optional line here to re-enable triggering program) Else - No Actions - (To add one, press 'Action') You just have to make sure whatever you put in your "if" section doesn't re-trigger and cancel the wait midstream leaving the countervar at some counted up value. You may make this two programs and have this program be disabled and have the first program run this program and set this program to disable then re-enable the first program.

did you try a reboot of the whole thing? I usually use putty to login (admin/admin) then enter the command "sudo reboot" Or if you want to really make sure, I believe the command is "sudo shutdown", let the unit shutdown and then pull power for 30 seconds.

If linking mode isn't working, then you either have a faulty switch or a seriously bad communication issue. You can try manually adding as per Paul, but I suspect that won't work. And if it does work, then it means something is wrong with the switch since it isn't declaring itself in linking mode. I assume you are holding the set button in long enough until the switch beeps indicating it entered linking mode.

Switching to a new, dual band, device usually fixes any com issues, especially ones that aren't horrible. My bet though is that the age of that switch is the problem, which of course is also fixed with a new replacement. I have found that the old single band devices seem to become less sensitive to the power line signal as they age. I have some very old devices that monitor power draw (I forget what they are called), but they don't make them anymore so I can't replace them. I use them to tell when the washing machine has finished. Anyway, as they got older, the com failure rate kept climbing until they stopped working altogether, but discovered if I plug it in directly next to the plm, they worked. I ended up using a dual band appliance linc that I plugged it directly into (in series) and that fixed the com issue. But the point is, it needed that strong of a signal, basically a couple inches of wire between it and the appliance linc as a repeater.

That looks like a nice all-in-one package. I could make one that does the same thing for less than $100 including the Insteon switch, but if you don't want to be troubled . .. Of course you still have to install the thing so you kind of are already being troubled. The contactors for HVAC equipment would be perfect for this and are only about $10 and a nice waterproof j-box can be had for about $15. The make these j-box's with mounting plates in the back which is real nice so you can just screw down all your stuff with no fuss and have it look all nice and neat. It wouldn't have the switch on the outside though, you would have to open the door, but they come with hinged doors, so no big deal.

theoretically, at some point we will get a http GUI that runs on the Polisy/Eisy box. Perhaps the Eisy will perform better when this task is layered on top? But I wouldn't think it would matter unless they really do something fantastic with the self-hosted web interface (like video and live action stuff vs just a console similar the java one).

I can't imagine what the mechanism could have been for Eisy to inhibit local manual operation of a switch. It was my understanding the local control of a switch was independent of any Insteon communication. Perhaps some flood of data between eisy and the switch upon pressing the button that swamped the switch cpu. It would have been curious to have watched the traffic on eisy.

I would start with one of your mis-behaving switches. Factory reset it and then restore it from ISY. Pull the tab out, leave it out for 10 seconds, then in one motion, push the tab in, all the way in, and hold it there for a good bit. The device will start to beep, don't let go, keep holding it in until the beep stops. That should factory reset it. Then go to ISY and restore it. I find it easier to use a butter knife to push the tab in and hold it with for the 10 or 15 seconds it takes to factory reset.

Thank you for that. The video only showed webhooks in the protect section, I assume nothing yet in access. I don't use ubiquiti protect, only network and access. EDIT: AS it turns out, I do "use" protect because they have integrated the door card reader cameras into protect.

I'm pretty sure on a 2477s, that if the led goes to the top, the load is on. Also, you would hear the relay inside click if it turns on. If both of those things happen, then I suspect the load is connected to a different switch.

When you manually walk up to the switch and click it. Do the led's on the switch rise up to the top indicating it should be on? Are you sure the load is connected to that switch and not another switch that you have in a scene with it? Certainly Insteon switches can fail and simply don't send power to the load. But if the load turns on when using Alexa, the switch is obviously not failed in that way. Some switches have failed where the tact switch no longer connects and thus when you push the button the computer in the switch doesn't know you pushed it. But that is a problem with much older switches and to my knowledge none of the dual band switches.

How do you transfer your settings from your phone to this? I have exported the ud mobile to my pc, but can't import them from blue stack emulator. EDIT: I figured out an easy way. I installed gmail in the blue stacks emulator and then emailed the file to myself and downloaded it from gmail within the emulator and then it was in the emulator download folder. Trouble is, when I tried to install the backup, it said there was a version conflict. I signed up for the beta version on my phone, I have now signed up for it in the emulator. Waiting to see if that works. EDIT 2: That worked.