kfrazack

Thanks for the help. I did use the logs. That pointed me to the gate sensor. When I disabled it, everything worked. Then everything fell into place.

Well took me forever to figure this out. Bought a new IO linc, thought everything was working and then same issue. Problem happened when I updated my ISY firmware from 4.x.x to 5.x.x. Some key programs that were disabled, became enabled. I had a series of programs (all disabled) to open and close the gate that would trigger only when invoked by Alexa. Some of them became enabled. Two of the programs monitored the gate status and if it was closed would open the gate and vice versa. But they enabled and always on. Everytime I would open the gate, one of the programs would see it open and then close it and vice versa. All I had to do was disable the programs. What a headache. But if this helps anyone else at least it was worth it. And now I have an extra IO Linc

Well happened again. Guess that means the unit is done.

Thanks for the info. Hopefully it's a one time problem. I've some modules for 10+ years and only now starting to have some minor issues. These things are built like tanks.

I played with it a bunch. Couldn't get it to work. Ultimately just reset the device to factory settings, deleted it from the ISY, added it back to the ISY and now working. Thanks for the prompt reply though.

I recently put a new battery in my gate sensor. Since then the IO linc that controls the gate double triggers. For example when I trigger it in the ISY control panel, two signals are sent about 7-8 seconds apart. This causes my gate to stop about half open. I can’t imagine that the gate sensor had anything to do with this. Might have been coincidental. But I can’t figure it out.

I've had similar issues. I was having all sorts of connectivity issues. I did a factory reset on my PLM and got a "Safe Mode" warning. Later it started working but intermittently. I figured it was done so I replaced it. When I installed the new PLM and did the restore PLM it didn't quite work. I had to right click on each device, do a restore and then a write. Then the device red exclamations all resolved. But when I check PLM links there are only 28 whereas the old PLM had over 300. I've tried to do another PLM restore. It lasted less than one minute but didn't increase the links. It seems like I might be missing all the scene links. I'm kinda stuck.

I just finished doing this exact thing. You could use state variables but the problem is that if someone opens the door with a remote or the wired button in the garage it throws off the state variable. I used the sensor built into the Insteon IOLinc to determine garage state. I have a set of programs that make this all work. I can give details after work when I can look at my ISY. But this is the gist: program 1 (called by Alexa routine) If nothing then run open garage else run close garage program 2 (open garage) if garage sensor is open then do nothing else turn garage on program 3 (close garage) if garage sensor is closed then do nothing else turn garage on Then in the ISY portal add program 1 as a scene. In the Alexa app discover the scene. Add a routine that triggers on the voice command “open the garage” to turn scene “program 1” on (this calls the “then” portion of the program). Add another routine that triggers on “close the garage” to turn scene “program 1” off (this call the “else” portion of the program). All of the above programs must be “disabled”. This basically makes them subroutines that activate only when called.

I think I see why having separate programs is needed. It has to do with the states of variables and devices. I made a program that would open the garage door if you told it to, but would do nothing if the door was already opened. Same for close. But it didn't work properly until I disabled all the programs. Otherwise they were always looking for a true clause. I never understood the point of disabling a program until now. It basically makes the program a subroutine that runs only when called. TomL, I'm the same way. I've combed through these posts to set up my ISY and some basic programs. But when I got the Alexa it opened up a whole new world. Definitely having fun figuring this stuff out. Thanks for all of your help.

I misspoke. My trigger reverse is not checked.

TomL I just ran across this: An Alexa contact sensor can be queried this way: Alexa, is <device> opened? Alexa, is <device> closed? This works for ISY devices, ELK zones, or state variables. If Alexa responds with an error message, please try a different spoken. Alexa is a bit picky on the spoken used, especially for querying the contact sensor. For motion sensors, it seems that there is no way to query by voice. You can however query the state in the Alexa app. However, you're programming examples helped me better understand the whole state variable thing.

Larry thanks for clarifying.

TomL This is genius! Took awhile to figure out how it's working. But if you don't mind me picking your brain... why not build it all into one program? The query program is simply running the open program and the open program else clause is calling the closed program. Why not just call the open program and have it as this? window open - [ID 00A9][Parent 00A3][Not Enabled] If 'Security / Windows / KR Side Window-Opened' Status is On Then $s.KR_Window_Open = 1 Wait 30 seconds $s.KR_Window_Open -= 1 Else $s.KR_Window_Closed = 1 Wait 30 seconds $s.KR_Window_Closed -= 1

I have a newly purchased (from Amazon) 2843-222 rev 3.0 and the heartbeat status is simply blank. No on or off. Am I missing something?

But wait, I can’t see a way for an Alexa voice prompt to trigger a program.