Jimbo.Automates

For me, disabling the device stops the ISY from querying them. Also for programs I just create an s.Christmas variable which changes how my programs work when the Christmas lights are all plugged in. Sent from my Nexus 7 using Tapatalk

For control you do need both, for status you do not. This has a good explanation a few posts down http://forum.universal-devices.com/topic/4376-wrapping-my-head-around-how-the-isys-else-works/ that post is linked thru the wiki http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:How-To_Guide Sent from my Nexus 7 using Tapatalk

There have been a lot of posts related to this for foscam. Search for set_alarm.cgi

Sorry I don't know. I leave the tiny door screw out of mine so I can slide off the door without pulling it off the mount until I am completely satisfied with the configuration. And to configure with the ISY one of the default jumpers have to be changed, or you can change the settings by changing other jumpers or adjusting the pots. Sent from my Nexus 7 using Tapatalk

That depends how the MS is configured. Put the MS in linking mode, select it in the ISY admin and select options. Using a MS seems simple, but there are a alot of different ways to control things with them. Search the forum or twiki and you'll see a lot of discussions. Sent from my Nexus 7 using Tapatalk

The adjust scene settings used when the scene is controlled by the ISY are what you have changed in your program above. To change how the controllers affect the scene you have to add adjust scene settings for each controller in that scene. Sent from my Nexus 7 using Tapatalk

Go back to post #3. You shouldn't have the control checks in the program, just a program that runs to change the scene settings at the specified times.

I changed one to 2 scene mode, and it only sends a control on for the open (1) when opened and control on for closed (2) when closed. Status never changes to off for either... Guess I have to decide which is more important, seeing the devices in the door open scene, or fast turn on for the light...

Thanks, I'm going to change one of mine and recheck.

Sounds like the hidden sensor works different than a TriggerLinc, when I change the mode they only send an on, never an off. Sent from my Nexus 7 using Tapatalk

I want to do this as well, but I also use the door sensor (triggerlinc not the hidden one) to show the status of doors. I have a scene DoorOpen and all the triggerlincs are in the scene which also has a KPL button as a responder so I can see if a left a sliding door is open. I haven't figured out a way to do both without a program. I don't use this a security system, I know an ELK is the right way to do that, but haven't moved to that yet... That's next on the list after I'm done with all my insteon & z-wave installs...

Right click on the program and select copy to clipboard, then paste into a post so we can see what you have.

Yes, thanks for pointing out that last paragraph! Sent from my Nexus 7 using Tapatalk

I'm using this http://www.smarthome.com/i-o-linc-insteon-freezer-failure-sensor-kit.html It doesn't monitor temperature, just notifies me if above 39 degrees. Sent from my Nexus 7 using Tapatalk

Thanks everyone. Will be buying them today

Mrbudin, thanks I meant to ask that as well, and specifically the Android Mobilinc. Sent from my Nexus 7 using Tapatalk

Thanks everyone for responding with your experience. I was thinking about getting these locks and now I definitely will. Amazon has them for $172, with prime shipping which looks like a great price. Sent from my Nexus 7 using Tapatalk

That was meant for the OP eyost, not me

Right click on the program and select "Copy to clipboard" Sent from my Nexus 7 using Tapatalk

I can't give an answer why disabling that program would cause a problem, but everytime I think I want a KPL to flash by toggling a scene on and off in a loop I have issues similar to what you describe and have never been able to figure it out. As to the preference for using a variable or run a program, I usually find I need a variable since I might want to break out of the second program example that oberkc showed. Like if the switch was manually pressed... But that is one of the many reasons I love the ISY, different ways to solve the same thing... Sent from my Nexus 7 using Tapatalk

To answer the last question, yes it does look good and I typically write programs using that state machine style. But I would move turning the light on to the second program, or even make it 3 states where 1=light turned on, and 2=waiting. This makes it easier to add other states and triggers later, like motion detection or a manual light control change. Sent from my Nexus 7 using Tapatalk

Also if you push the button on the MS 7 times quickly they send the current duskdawn status if it's different than the previous status so you don't have to wait the 3.5 minutes. I wish the ISY would automatically remember the last reported status of wireless devices so I don't have to create variables and programs for all of them... Sent from my Nexus 7 using Tapatalk

This should be posted in the third party/mobilinc forum or in MobiLinc's own forum Sent from my Nexus 5 using Tapatalk

OK, makes sense. I guess I was assuming that I would add them so their communication status could be seen. Thanks! Sent from my Nexus 5 using Tapatalk

I am trying to add a new Range Extender 2992-222 device, but I get an error "Unsupported Device:0.29". I tried adding it manually but that fails as well. I did search the forums and didn't see anyone mention trying to actually add this device. I am using the latest 4.2.10 Firmware and UI. Is there anything I can do until it's officially supported? Thanks, Jim